Files > RAD/NUC MED DIVISION

name
RAD/NUC MED DIVISION
number
79
location
^RA(79,
description
This file contains, for each division entry, parameters that the module uses during various stages of exam and report processing and inquiring. These parameter switches allow the 'customizing' of the module for each division by the package coordinator. The module is designed to handle multiple divisions within a medical center. While most medical centers only have one division, there are a number that are multi-divisional. As a result, it was necessary to structure the entire system around the division concept. However, single division medical centers will not notice this in the everyday execution of the module. Within a division there may be a number of physical locations where an imaging procedure can be performed. The module is designed to handle multiple locations within a division. However, each location can only be associated with one division. Location data is stored in the 'IMAGING LOCATIONS' file (#79.1). These parameters are loaded into the user's partition once the module determines which division and location the user is currently associated with. This is determined by one of two ways: 1) the device the user is using is an entry in the 'INPUT DEVICES' sub-file of the 'IMAGING LOCATIONS' file or 2) if (1) is not true than the module will simply ask the user what his/her current location is. Method 1 is becoming obsolete; it was used before virtual terminals came into being. Therefore, most systems will ask the user for a sign-on imaging location. Entries in this file should not be deleted. Adding new entries is always allowed. Data Storage ------------ The data for the 'RAD/NUC MED DIVISION' file is stored in the ^RA(79, global. At the present time this file is very static after day-one initialization is complete. However, it still should be journaled. It should also be translated if the operating system supports this function. Input Templates --------------- The following is a list of input templates used by the package and the entry in the OPTIONS file (#19) that uses the template: Compiled Name Routine Description; Option(s) ---- ------- ---------------------- RA DIVISION PARAMETERS Used to enter/edit division parameters that the package coordinator controls; RA SYSDIV If any modifications to these input templates are needed for local purposes, then great care should be taken not to degrade any branching logic in the template. Print Templates --------------- The following is a list of print templates used by the radiology package: Name Description; Option(s) ---- ---------------------- RA IMAGE DIV LIST Prints the division parameters for the entries in this file; RA SYSDIVLIST Sort Templates -------------- The radiology package does not use any sort templates associated with this file.
applicationGroups
RA
Fields
#NameLocationTypeDetailsIndexDescription
.01division(+)0;1POINTER4BThis field contains the name of this division.
.11track exam status changes.1;10BOOLEANY: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.
.111ask exam status time.1;11BOOLEANY: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.)
.112allow standard reports.1;12BOOLEANY: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.
.113allow batching of reports.1;13BOOLEANY: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
.114allow copying of reports.1;14BOOLEANY: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.
.115allow 'released/unverified'.1;15BOOLEANY: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.
.116impression required on reports.1;16BOOLEANY: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'.
.117ask 'requested date'.1;17BOOLEANY:yes
N:no
This 'division' parameter can be set to 'Yes' if the transcriptionist should be prompted for the Desired Date for the exam.
.118allow verifying by residents.1;18BOOLEANY: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.
.119track request status changes.1;19BOOLEANy: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.
.12print flash card for each exam.1;2BOOLEANY: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.
.121ask 'imaging location'.1;21BOOLEANy: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.
.122allow rpts on cancelled cases?.1;22BOOLEANY: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.
.124time limit for future exams.1;24NUMERICThis 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.
.125warning on rpts not yet verif?.1;25BOOLEANY: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.
.126auto e-mail to req. phys?.1;26BOOLEAN1: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.
.127allow e-sig on cots hl7 rpts.1;27BOOLEANY: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.
.128interpreting staff req'd?.1;28BOOLEANY: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.
.129hl7 receiving applicationsHL7;0MULTIPLE79.02This field holds a list of pointers to the HL7 APPLICATIONS file (#771).
.131use site accession number?.1;31BOOLEANY: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.
.16auto user code filing.1;6BOOLEANY: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.
.17detailed procedure required.1;7BOOLEANY: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'.
.18print jacket lbls w/each visit.1;8BOOLEANY: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).
.19ask 'camera/equip/rm'.1;9BOOLEANY:yes
N:no
This 'division' parameter can be set to 'Yes' to indicate that the 'camera/equip/rm' should be asked during exam editing.
25contrast reaction messageCON;1FREE TEXTThis 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.
50imaging locationsL;0MULTIPLE79.01This 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.
75clinical history messageHIS;1FREE TEXTThis 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.
100resource deviceRDEV;1POINTER3.5A 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.
125rpharm dose warning messageRWARN;0WORD-PROCESSINGThis 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.
150user prefers long displayLDIS;0MULTIPLE79.03
175perf indic smtp e-mail address1;0MULTIPLE79.0175
2300.1last dfn converted (75.1)PATCH23;1FREE TEXTThis 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.2conversion start time (75.1)PATCH23;2DATE-TIMEThis field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 75.1 began.
2300.3conversion stop time (75.1)PATCH23;3DATE-TIMEThis field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 75.1 finished.
2300.4last dfn converted (70)PATCH23;4FREE TEXTThis 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.5conversion start time (70)PATCH23;5DATE-TIMEThis field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 70 began.
2300.6conversion stop time (70)PATCH23;6DATE-TIMEThis field was added with Patch 23 (RA*4*23). It contains the date and time the data conversion for File 70 finished.

Referenced by 1 types

  1. IMAGING LOCATIONS (79.1) -- rad/nuc med division