# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | division(+) | 0;1 | POINTER | 4 | B | This field contains the name of this division. |
.11 | track exam status changes | .1;10 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to collect the date and the time of exam status changes. If the data is collected, it is stored with the case in the Activity Log subfile of the Rad/Nuc Med Patient file. | |
.111 | ask exam status time | .1;11 | BOOLEAN | Y:yes N:no | This 'division' parameter is used if the 'Track Exam Status Changes' parameter is set to 'Yes'. This parameter may be set to 'Yes' to indicate that the user should be asked the time of the status change. If this parameter is set to 'No', then the system automatically uses the current date and time. (If exam data is entered significantly later than the patient is actually processed, then this parameter could be set to 'Yes' so that the user can put in the actual time the work was done.) | |
.112 | allow standard reports | .1;12 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if the transcriptionist should be given the opportunity to select a standard report during the report entry/edit process. | |
.113 | allow batching of reports | .1;13 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if the transcriptionist should be given the opportunity to place reports in a batch during report entry. Batching of reports has the following advantages: 1) Reports can be re-printed easily 2) Two or more users are allowed to use the same report printer without interweaving of reports 3) Allows for batch verifying of reports 4) Provides a mechanism for logical grouping of reports | |
.114 | allow copying of reports | .1;14 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if the transcriptionist should be given the opportunity to copy the contents of one report into another. The report text and impression will be copied. | |
.115 | allow 'released/unverified' | .1;15 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to allow reports to have the status 'RELEASED/UNVERIFIED' which permits the displaying of the report to users outside of the Imaging service even if it is unverified. | |
.116 | impression required on reports | .1;16 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to indicate that an impression is required to be given on a report before: 1) the report can be verified and 2) the exam can be considered 'complete'. | |
.117 | ask 'requested date' | .1;17 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if the transcriptionist should be prompted for the Desired Date for the exam. | |
.118 | allow verifying by residents | .1;18 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to allow interpreting residents to verify other interpreting physicians' reports while using the 'On-line Verifying of Reports' option. If the parameter is set to 'Yes' then only those residents whose individual parameter (ALLOW VERIFYING OF OTHERS) in the 'New Person' file is also set to 'Yes' will be allowed to verify other interpreting physicians' reports. If this division parameter is set to 'No' then no residents will be allowed to verify other physicians' reports, regardless of how the individual parameter is set in the 'New Person' file. | |
.119 | track request status changes | .1;19 | BOOLEAN | y:YES n:NO | This 'division' parameter can be set 'Yes' to collect the date and the time of request status changes. If data is collected the new status, computer user, and, sometimes, the reason for the status change, are stored with the order in the Request Status Times subfile of the Rad/Nuc Med Orders file. | |
.12 | print flash card for each exam | .1;2 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if one flash card should be printed for each exam (i.e. case). If this parameter is set to 'Yes', then the 'location' parameter, 'How Many Flashcards Per Visit' is ignored. | |
.121 | ask 'imaging location' | .1;21 | BOOLEAN | y:YES n:NO | This division 'parameter' can be set to 'Yes' to indicate that the user should be asked when requesting an exam, which 'Imaging Location' the request should be forwarded to. It is recommended that this field be set to 'Yes' to facilitate sorting of requests by imaging location for various reports. Answering 'Yes' to this questions causes the 'SUBMIT REQUEST TO:' prompt to appear after a request is created. | |
.122 | allow rpts on cancelled cases? | .1;22 | BOOLEAN | Y:yes N:no | This field will determine if a user who does not have the RA MGR key may enter a report for an exam that has a status of CANCELLED. | |
.124 | time limit for future exams | .1;24 | NUMERIC | This is the maximum number of hours in the future that a user may register a patient for an exam. If this prompt is bypassed, the user may not register a patient at a future date. | ||
.125 | warning on rpts not yet verif? | .1;25 | BOOLEAN | Y:yes N:no | If this field is set to 'Yes' results reports in any status except 'Verified' will print the status surrounded by asterisks under the body of the report. If this field is set to 'No' or left unanswered, the status box will not print on reports not yet verified. This can be used to make sure that hardcopies of unverified results reports are not accidentally placed in patient charts or interpreted as the final results. | |
.126 | auto e-mail to req. phys? | .1;26 | BOOLEAN | 1:yes | Entering 'Y'es will turn on a feature that automatically sends the Radiology/Nuclear Medicine findings report to the Requesting Physician via e-mail at the time it is verified. If this field is left blank, verified reports will not be e-mailed to the requesting physician. | |
.127 | allow e-sig on cots hl7 rpts | .1;27 | BOOLEAN | Y:yes N:no | Entering 'Y' will turn on a feature that automatically adds the Electronic Signature Block printed name of the Verifying Physician that signed the report being transmitted to Rad/Nuc Med via an HL7 interface to a COTS voice reporting system. This parameter is only checked for COTS HL7 interfaces that use the Generate/Process Routine 'RAHLTCPB' in the subscriber protocol. | |
.128 | interpreting staff req'd? | .1;28 | BOOLEAN | Y:YES N:NO | This field should be set to YES if you require entry of 'PRIMARY INTERPRETING STAFF' (file 70, field #15) to be mandatory for this division when entering Diagnostic data or Reports. | |
.129 | hl7 receiving applications | HL7;0 | MULTIPLE | 79.02 | This field holds a list of pointers to the HL7 APPLICATIONS file (#771). | |
.131 | use site accession number? | .1;31 | BOOLEAN | Y:YES N:NO | This parameter will function as a switch to turn on the use of the Site Specific Accession Number. Until this field is set to YES the system will NOT use the Site Specific Accession Number during registration of a new case. Only when all devices are able to handle the Site Specific Accession Number should this field be set to YES, at which point the system will use the Site Specific Accession Number. | |
.16 | auto user code filing | .1;6 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to indicate that the user should be asked for their access code during the processing of exams and reports of which various activity logs are kept. If this parameter is set to 'Yes', then the system automatically uses the user code associated with the initial logon. If this parameter is set to 'No', then the system asks the access code during each process. | |
.17 | detailed procedure required | .1;7 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' if the entry of a 'detailed', 'series' or 'parent' procedure type should be required during the initial exam registration or request. If this parameter is set to 'No', then the user can enter 'broad' procedure type, but this must be changed to 'detailed' or 'series' before the exam status can be changed to 'complete'. | |
.18 | print jacket lbls w/each visit | .1;8 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to indicate that a jacket label should be printed automatically during each visit. If this field is set to YES and the field 'HOW MANY JACKET LABELS PER VISIT' in the IMAGING LOCATIONS (79.1) file is set to zero, then the default will become two (i.e., two jacket labels will print out). | |
.19 | ask 'camera/equip/rm' | .1;9 | BOOLEAN | Y:yes N:no | This 'division' parameter can be set to 'Yes' to indicate that the 'camera/equip/rm' should be asked during exam editing. | |
25 | contrast reaction message | CON;1 | FREE TEXT | This is an optional field that may contain a site-defined message to be displayed with the warning message for patients who have had a reaction to the contrast medium. For example, it may contain a reminder to use a yellow sticker for this patient's films. This field is only used for exams which may involve the use of contrast medium. The message must be 5-70 characters in length. | ||
50 | imaging locations | L;0 | MULTIPLE | 79.01 | This field points to file #79.1 to indicate the name of the Imaging location associated with this division. A location may be associated with only one division. | |
75 | clinical history message | HIS;1 | FREE TEXT | This is an optional field that may contain a site-defined message to be displayed with a warning message which will be displayed in order entry, immediately proceeding the clinical history prompt. The message must be 5-70 characters in length. | ||
100 | resource device | RDEV;1 | POINTER | 3.5 | A Resource device may be entered here if the facility wishes to control the rate at which tasked exam status updates are released to be processed. This is advised if the facility is experiencing drastic system slowdowns due to periodic heavy use of the online report verification and batch verification of reports options, which can queue a large number of tasks at once. However, if the facility chooses to enter a Resource Device in this field, IRM should be careful to completely follow all directions in Kernel documentation after a system crash to bring this Resource Device back up. Failure to follow those directions could result in Rad/Nuc Med tasks being severely delayed, and data corruption. | |
125 | rpharm dose warning message | RWARN;0 | WORD-PROCESSING | This field contains the message displayed to the user when the dose falls outside the range of the 'Low Adult Dose' and the 'High Adult Dose' fields. These fields reside in the Default Radiopharmaceuticals multiple in the Rad/Nuc Med Procedures file. Use the 'Procedure Enter/Edit' option to adjust these values. | ||
150 | user prefers long display | LDIS;0 | MULTIPLE | 79.03 | ||
175 | perf indic smtp e-mail address | 1;0 | MULTIPLE | 79.0175 | ||
2300.1 | last dfn converted (75.1) | PATCH23;1 | FREE TEXT | This field was added with Patch 23 (RA*4*23). The value should be a number or the word 'DONE'. If the value is a number, then the data conversion routine did not complete successfully. | ||
2300.2 | conversion start time (75.1) | PATCH23;2 | DATE-TIME | This field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 75.1 began. | ||
2300.3 | conversion stop time (75.1) | PATCH23;3 | DATE-TIME | This field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 75.1 finished. | ||
2300.4 | last dfn converted (70) | PATCH23;4 | FREE TEXT | This field was added with Patch 23 (RA*4*23). The value should be a series of numbers separated by slashes (e.g., 123/456/789) or the word 'DONE'. If the value is a group of numbers, then the data conversion routine did not complete successfully. | ||
2300.5 | conversion start time (70) | PATCH23;5 | DATE-TIME | This field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 70 began. | ||
2300.6 | conversion stop time (70) | PATCH23;6 | DATE-TIME | This field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 70 finished. |