# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | location(+) | 0;1 | POINTER | 44 | B | This field points to the Hospital Location File, and contains the name of this location. The Hospital Location pointed to should be a COUNT clinic, with a type of 'CLINIC', and should be a clinic that prohibits making appointments or creating appointment patterns. The Stop Code of the clinic in file #44 should be a valid imaging stop code (i.e. an entry in file #71.5) and should match the DSS ID field #22 of the Imaging Location in file #79.1. The Institution of this clinic in file #44 should match the Rad/Nuc Med Division to which this Imaging Location is assigned. Coordination with MAS personnel is necessary to add locations to the Hospital Location file. |
2 | how many flash cards per visit | 0;2 | NUMERIC | This imaging 'locations' parameter is used to set up the number of flash cards to print per patient visit. It must contain a whole number between 0 and 10. If the Division parameter 'Print Flash Card for each exam' is set to 'Yes', this location parameter is ignored. | ||
3 | flash card printer name | 0;3 | POINTER | 3.5 | This 'locations' parameter can contain the device name (1-20 characters) that flash cards and exam labels are to be printed on. If this field is filled in, the system automatically queues the process and the user is not asked the device question. | |
4 | how many jacket lbls per visit | 0;4 | NUMERIC | This 'locations' parameter is used to set up the number of jacket labels to print per patient visit. It must contain a whole number between 0 and 10. | ||
5 | jacket label printer name | 0;5 | POINTER | 3.5 | This 'locations' parameter can contain the device name (1-20 characters) that the jacket labels are to be printed on. If this field is filled in, the system automatically queues the process and the user is not asked the device question. | |
6 | type of imaging(+) | 0;6 | POINTER | 79.2 | BIMG | This 'locations' parameter can contain the name of the type of imaging from the 'Imaging Type' file. If this field is filled in, the system automatically fills in the proper imaging type on the registration record. Assigning an new imaging type (i.e. one not previously selected for any other location) implies that procedures of the new imaging type are performed under a separate service or section at your site, and separate workload report is desired. For instance, at some sites Ultrasound may be done separately from Radiology, and it would be appropriate to assign the 'Ultrasound' imaging type to one or more locations. Once the 'Ultrasound' imaging type is "activated" in this way, and procedures designated as 'Ultrasound' imaging type have been registered, the system will report Ultrasound workload separately from Radiology workload. NOTE: The 'Cardiology Studies' imaging type should NOT be assigned to a location unless nuclear cardiology studies are done under a service other than Nuclear Medicine. |
7 | default flash card format | 0;7 | POINTER | 78.2 | This 'locations' parameter can contain the default format (from the 'Flash Cards Formats' file) to be used when queueing a flash card to print. This format is the default 'flash card' for the current location. | |
8 | how many exam labels per exam | 0;8 | NUMERIC | This imaging location parameter is used to set up the number of exam labels to print per registered case. It must contain a whole number between 0 and 9. | ||
9 | default exam label format | 0;9 | POINTER | 78.2 | This imaging 'locations' parameter can contain the default format (from the 'Flash Cards Formats File') to be used when queueing an exam label to print. This format is the default 'exam label' for the current location. Exam labels always print after flash card labels are printed. | |
10 | report printer name | 0;10 | POINTER | 3.5 | This 'locations' parameter can contain the device name (1-20 characters) that reports are to be printed on. If this field is filled in, the system automatically queues the process and the user is not asked the device question. | |
11 | default jacket label format | 0;11 | POINTER | 78.2 | This 'locations' parameter can contain the default format (from the 'Flash Cards Formats' file) to be used when queueing a jacket label to print. This format is the default 'jacket label' for the current location. | |
12 | default report header format | 0;12 | POINTER | 78.2 | This 'locations' parameter can contain the default format (from the 'Flash Cards Formats' file) to be used when queing a report to print. This format is the default 'header' for the current location. | |
13 | default report footer format | 0;13 | POINTER | 78.2 | This 'locations' parameter can contain the default format (from the 'Flash Cards Formats' file) to be used when queing a report to print. This format is the default 'footer' for the current location. | |
14 | report left margin | 0;14 | NUMERIC | This field indicates which column the text for 'clinical history', 'report' and 'impression' should start at when printing the report. Enter a number between 1 and 20. | ||
15 | report right margin | 0;15 | NUMERIC | This field indicates which column the text for 'clinical history', 'report' and 'impression' should end at when printing the report. Enter a number between 50 and 130. | ||
16 | request printer name | 0;16 | POINTER | 3.5 | This 'locations' parameter can contain the device name (1-20 characters) that requests are to be printed on. If this field is filled in, the system automatically queues the process to the specified device. If this field is not filled in the request is not automatically queued to print to any device. | |
17 | allow 'released/not verified' | 0;17 | BOOLEAN | Y:yes N:no | This Imaging Location parameter can be set to 'Yes' to allow reports to have the status 'RELEASED/NOT VERIFIED' which permits the displaying of the report to users outside of the Imaging service even if it is not yet verified. | |
18 | print dx codes in report? | 0;18 | BOOLEAN | Y:yes N:no | If this field is set to Yes, all primary and secondary diagnostic codes associated with the exam will be printed on the exam report. (Note: Since the primary diagnostic code may be printed in exam report headers and footers, you may also need to change report header and footer set-ups to get the diagnostic codes printed exactly as you wish.) | |
19 | inactive | 0;19 | DATE-TIME | Contains the date the Imaging Location was inactivated. Orders cannot be submitted to an inactive location and cases cannot be registered in an inactive location. | ||
20 | urgent request alerts? | 0;20 | BOOLEAN | Y:yes | This field will determine if alerts will be sent to the Imaging Personnel defined in the STAT REQUEST ALERT RECIPIENTS field. If this field is set to 'Yes', then all the users in the STAT REQUEST ALERT RECIPIENTS field will be sent an alert for urgent requests. To use this feature, the Division parameter 'Ask Imaging Location' must be set to 'YES', and OE/RR Version 3.0 or higher must be installed. | |
21 | credit method | 0;21 | SET OF CODES | 0:Regular Credit 1:Interpretation Only 2:No Credit 3:Technical Component Only | This field indicates the type of credit this location receives for examinations. The default is REGULAR (code 0), which means that for this imaging location both the exam and the interpretation are done at your facility. If this imaging location has been set up to register exams done in another facility, with the imaging interpretation only done at this facility, enter code 1. If exams are done in this location, but interpretation is done elsewhere, enter code 3. If both the exam and the interpretation are done elsewhere, and exams entered for this imaging location are entered only for record-keeping purposes, enter code 2. | |
22 | dss id | 0;22 | POINTER | 40.7 | DSS ID will be used to identify the general outpatient area where an imaging exam was done. It is used only by DSS, and only when processing outpatients. It is roughly equivalent to the "Stop Codes" previously used for crediting outpatient exams. Only entries also in the Imaging Stop Codes file #71.5 (which must be updated yearly by the Radiology/Nuclear Medicine ADPAC) are valid. | |
23 | dosage ticket printer | 0;23 | POINTER | 3.5 | This question only applies to imaging locations with an imaging type where radiopharmaceuticals are used (i.e. nuclear medicine and cardiology studies). If the facility's exam status parameters are configured to print Radiopharmaceutical dosage tickets when exams reach a specified status, and name of the printer device is entered here, then dosage tickets for nuclear medicine procedures registered in this location will print on this device. | |
24 | cancelled request printer | 0;24 | POINTER | 3.5 | This field specifies the device where the cancelled request will be output. | |
25 | rad/nuc med division | DIV;1 | POINTER | 79 | This field contains the name of the Radiology/Nuclear Medicine 'division' that this 'location' is associated with. A 'location' can only be associated with one 'division'. | |
26 | voice dictation auto-print | 0;26 | BOOLEAN | Y:yes | If this field is Y , and voice dictation is used to enter a report, a copy of the report will be automatically printed on the device defined in field REPORT PRINTER NAME. | |
100 | cameras/equip/rms | R;0 | MULTIPLE | 79.12 | This is a multiple field containing the cameras/equip/rms associated with this 'location'. | |
135 | default cpt modifiers(loc) | DCM;0 | MULTIPLE | 79.1135 | ||
150 | stat request alert recipients | REC;0 | MULTIPLE | 79.13 | Names entered here will be used as recipients of an alert when new STAT requests for Imaging exams are submitted to this Imaging Location. To use this feature, the division parameter 'ASK IMAGING LOCATION' must be set to 'Yes', and OE/RR Version 3.0 or higher must be installed. If the URGENT alert is turned on, the recipients entered here will also receive alerts when an URGENT request is entered. |