| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | institution name(+) | 0;1 | POINTER | 4 | B | |
| .02 | current namespace(+) | 0;2 | FREE TEXT | The Image file is 14 characters. Each facility has its own unique namespace (e.g., Washington is WAS, Baltimore is BAL). | ||
| .03 | image network write location | 0;3 | POINTER | 2005.2 | This field identifies the current network share for image file captures and archive retrieval. This field will need to be manually changed when a share reaches low water mark. | |
| .031 | current raid group | 0;10 | POINTER | 2005.2 | This field indicates the RAID group of shares that the system is currently writing to. This group is an entry in the NETWORK LOCATION file and has a GRP storage type. | |
| .04 | associated institutions | INSTS;0 | MULTIPLE | 2006.12 | Through the use of the subfield's whole file cross-reference this set of values will allow a site to make use of the imaging network of a second institution to store and support images. | |
| .07 | gcc export loc | 0;7 | POINTER | 2005.2 | This field identifies the external network share for Generic Carbon Copy (GCC) where image files are copied to. | |
| .08 | image network import location | 0;8 | POINTER | 2005.2 | This field identifies the IMPORT network share where the IMPORT queues are copied to. This share is within the local Imaging Network. | |
| .09 | site code | 0;9 | FREE TEXT | This is a unique identifying string for the site where the Imaging Server is installed. By convention, the abbreviation should correspond to the 3-character string used for the site in naming the file servers. E.g., for Washington, D.C., the code is "WAS", corresponding to vhaWASimm1. | ||
| 1.01 | pacs interface switch | PACS;1 | SET OF CODES | 0:OFF PACS INTERFACE 1:ON PACS INTERFACE | This field is "NULL" if there is no DICOM Gateway interface. If there is a DICOM Gateway, this field serves as a switch to turn the interface ON or OFF. If it is OFF no messages will be transmitted from VistA to the DICOM Gateway; if ON, then the messages will be transmitted. | |
| 1.02 | pacs directory | PACS;2 | POINTER | 2005.2 | This field identifies the DICOM Gateway network location share where PACS images are written by the Commercial PACS SYSTEM, and where VistA first reads them. | |
| 1.03 | pacs image write location | PACS;3 | POINTER | 2005.2 | This field identifies the current write network share for the DICOM Image Gateways. DICOM images are first read from the DICOM directory and later converted and copied to the network location specified by this field. | |
| 2.01 | jukebox write location | 1;6 | POINTER | 2005.2 | This field identifies the JUKEBOX 'current write' network share that will receive the Background Processor JUKEBOX queues for newly acquired Image files. | |
| 3.01 | ihe pacs hl7 interface active | IHE;1 | BOOLEAN | Y:YES N:NO | This field contains a flag that indicates whether HL7 ADT messages should be sent using the IHE-based interface developed in Imaging Patch MAG*3.0*49. | |
| 6 | track abstract accesses | 1;3 | BOOLEAN | 1:YES 0:NO | This field controls whether user access to image abstracts will cause the LAST ACCESS DATE field in the Image file to be updated. The LAST ACCESS DATE field is used to determine when full and abstract images are removed from magnetic disks and become available only from optical disk. | |
| 8 | purge-retention days full file(+) | 1;2 | NUMERIC | This field is used by the Background Processor Purge to determine the number of days to retain full image files. All FULL images that have not been accessed in this many days will be removed from magnetic storage by the Background Processor Purge. | ||
| 9 | retention days hl7 & dicom(+) | 1;5 | NUMERIC | This field is used as the default value, in days, by the DICOM Text Gateway for three different user menu driven purges. 1) This field is used by the Purge Old Modality Worklist Entries menu option to determine the number of retention days from the date of creation of the Modality Worklist Entries. 2) This field is used by the Purge Old DICOM Message Files menu option to determine the number of retention days from the date of creation of the DICOM messages that were sent to commercial PACS. 3) This field is used by the Purge Old HL7 Transaction Global Nodes menu option to determine the number of retention days from the date of creation of the HL7 messages sent from VistA to the DICOM Text Gateway. This value may be overridden by the user when executing any of these menu options. | ||
| 10 | server task | 1;7 | NUMERIC | This field identifies the Kernel scheduled task number for the monthly site report. The Background Processor Monitor utility (menu option [MAGQ BPMONITOR]) reads and updates this field when verifying the monthly site report has been tasked or re-tasked by this utility. This automated process reports version and Imaging system statusback to the development site in order to serve the site better. | ||
| 11 | percent server reserve | 1;8 | NUMERIC | This field allows sites to increase the amount of space that is maintained in reserve for each individual Image server share. The minimum value is 1. The default value is 5. The RPC, MAGQ FS CHNGE, uses this value to determine the RAID Group advance and is part of the automatic Purge algorithm. When this value cannot be maintained, a CRITICAL LOW MESSAGE is triggered. | ||
| 11.5 | tier 2 reserve | 1;9 | NUMERIC | This field allows sites to define a minimum percentage of free space in the tier 2 storage device in order to prevent loss of cache space for temporary storage. The default value is 5. The Background Processor JUKEBOX queue will not write to the currently designated tier 2 storage share if this percent storage capacity is not available or accessible from the Background Processor application. | ||
| 11.9 | date of last critical message | 3;11 | DATE-TIME | It is a parameter used in combination with the CRITICAL LOW MESSAGE INTERVAL to determine if it is appropriate to send a new message when the VistA cache space falls below the PERCENT SERVER RESERVE value. This field should not be edited directly by a user. | ||
| 12 | file types | 2;0 | MULTIPLE | 2006.112 | This field identifies acceptable file types on image captures and is read by the Background Processor to migrate files across the network shares and jukeboxes. | |
| 12.5 | multi namespace | 4;0 | MULTIPLE | 2006.11 | This multiple field is used to store all previously used image prefixes from the CURRENT NAMESPACE field. Any time the CURRENT NAMESPACE field is changed, enter the previous name in this multiple field. | |
| 20 | no autowrite update | 1;10 | SET OF CODES | 0:AUTOWRITE UPDATE OK 1:NO AUTOWRITE UPDATE | This field enables or disables the Background Processor function which evaluates the space availability on each of the online magnetic shares and assigns the current write location to the share with the greatest space available both for PACS and regular image capture. RPC, MAGQ FS CHNGE, utilizes this field when evaluating the current write location. | |
| 22 | purge-retention days big file | 3;2 | NUMERIC | This field is used by the Background Processor purge to determine the number of days to retain BIG files. All BIG images that have not been accessed in this many days will be removed from magnetic storage by the Background Processor purge. | ||
| 23 | purge-retention days abs file | 3;3 | NUMERIC | This field is used by the Background Processor purge to determine the number of days to retain ABS files. All ABS images that have not been accessed in this many days will be removed from magnetic storage by the Background Processor purge. | ||
| 24 | purge-retention days photoid | 3;4 | NUMERIC | This field is used by the Background Processor purge to determine the number of days to retain images designate as PHOTO IDs by the Image file. All PhotoID images that have not been accessed in this many days will be removed from magnetic storage by the Background Processor purge. | ||
| 25 | import queue security | 3;12 | SET OF CODES | 0:OFF 1:ON | This field enables network security for the Import Queue. | |
| 50 | net username | NET;1 | FREE TEXT | This field contains the NT username that the Imaging application uses to access images from the Image shares. | ||
| 51 | net password | NET;2 | FREE TEXT | This field contains the network password for the NET USERNAME entity. The password is encrypted. | ||
| 52 | net update directory | NET;3 | POINTER | 2005.2 | This is the directory where Imaging releases, to be tested, are copied. Workstations with the "WRKS RUNS TEST UPDATES" field set to True will check the directory, defined in this field, for the latest Imaging software to test. A site can limit the number of workstations that will use this procedure to test new versions of the software. When a site is satisfied with the new version, it copies MAGSETUP.EXE to the NETUPDATE DIRECTORY where all workstations will be updated. This field points to the Network Location file (2005.2). | |
| 53 | net update test directory | NET;4 | POINTER | 2005.2 | This is the directory where Imaging releases to be tested are copied. Workstations with NET UPDATE TEST DIRECTORY Field of the IMAGING WORKSTATIONS file = TRUE will check this directory for new versions of Imaging (MAGSETUP.EXE) A site can limit the number of workstations that will test new versions of imaging this way. When a site is satisfied with the new version, they copy MAGSETUP.EXE to the NET UPDATE DIRECTORY where all workstations will update from. | |
| 55 | net site service | NET;5 | POINTER | 2005.2 | The VistA Site Service is used by Remote Image Views to gain access to remote sites. | |
| 60 | autopurge | BPPURGE;1 | SET OF CODES | 0:OFF 1:ON | ||
| 60.1 | purge by | BPPURGE;2 | SET OF CODES | DA:DATE ACCESSED DC:DATE CREATED DM:DATE MODIFIED | This parameter is used by the Purge application. These date criteria apply to the dates within the Master File Table of the network share being purged. | |
| 60.2 | express purge | BPPURGE;3 | SET OF CODES | 0:OFF 1:ON | This enables the Purge application to expedite the purge on a given share if no files are actively being purged. This works with field EXPRESS PURGE RATE (#60.3). | |
| 60.3 | express purge rate | BPPURGE;4 | NUMERIC | This value determines if there is enough idle purge activity on a share to cease processing on the share. | ||
| 60.4 | last purge bpws | BPPURGE;5 | POINTER | 2006.8 | ||
| 60.5 | raid purge factor | BPPURGE;8 | NUMERIC | This factor (a number between 0 and 100), when multiplied by the Percent Server Reserve (#11), determines the automatic purge event triggered by the BP Queue Processor. The RPC, MAGQ FS CHNGE, uses this value and is part of the automatic Purge algorithm. | ||
| 61 | scheduled purge | BPPURGE;6 | SET OF CODES | 0:OFF 1:ON | This field is used to determine whether the BP Queue Processor enables a scheduled purge process. The frequency is determined by the frequency days and the date of the last purge. A default value of 28 days is used if the frequency value is null. A default value of 2400 hours is used if the PURGE TIME is not set. | |
| 61.1 | date of last purge | BPPURGE;7 | DATE-TIME | This is the date of a last scheduled purge process was executed and is automatically set at the beginning of a scheduled purge. | ||
| 61.2 | scheduled purge frequency | BPPURGE;9 | NUMERIC | When the Scheduled Purge process is enabled, this value in days (between 1 and 365) is added to the date of the last purge for the BP Queue Processor to evaluate for launching a purge process. | ||
| 61.3 | date of scheduled purge | BPPURGE;10 | DATE-TIME | This is the scheduled date of the next scheduled purge. It is set at the end of an automated purge by adding the SCHEDULE PURGE FREQUENCY (#61.2) parameter to the date of the last purge. It may be set by the user to establish a new schedule. | ||
| 61.4 | scheduled purge time | BPPURGE;11 | NUMERIC | This number (between 0 and 2359) for military time determines the time of day to trigger the Scheduled Purge. If this number is undefined, the BP Queue Processor uses the default value of 0 if the Scheduled Purge option is enabled and the frequency days plus date of last purge threshold are reached. | ||
| 62 | scheduled verifier | BPVERIFIER;1 | SET OF CODES | 0:OFF 1:ON | This field is used to determine whether the BP Queue Processor enables a scheduled verifier process. | |
| 62.1 | date of last verify | BPVERIFIER;2 | DATE-TIME | This is the date of a last scheduled verifier application and is automatically set at the beginning of a scheduled verifier execution. | ||
| 62.2 | scheduled verifier frequency | BPVERIFIER;3 | NUMERIC | When the Scheduled Verifier process is enabled, this number in days (between 1 and 365) is added to the date of the last verify for the BP Queue Processor to evaluate in launching a verify process. | ||
| 62.3 | date of scheduled verifier | BPVERIFIER;4 | DATE-TIME | This is evaluated by active BP Processors to trigger a BP Verifier process at the date and time designated by the user. In conjunction with the SCHEDULED VERIFER time, this field co-defines the timing of this process. | ||
| 62.4 | scheduled verifier time | BPVERIFIER;5 | NUMERIC | This number (between 0 and 2359) for military time is used to determine the time of the day to trigger the Scheduled Verifier. If this number is undefined, the BP Verifier uses the default value of 0 if the Scheduled Verify option is enabled and the frequency days plus date of last verify threshold are reached. | ||
| 62.5 | last verify bp ws | BPVERIFIER;6 | POINTER | 2006.8 | This field references the BP Server that executed the Verifier process and therefore has the log files that document that activity. The intention of this field is to assist the support staff in locating the BP Verifier activity log files for the last purge. | |
| 62.6 | scheduled verify text check | BPVERIFIER;7 | BOOLEAN | 0:NO 1:YES | This field enables the BP Verifier to validate the RAID text files for patient identification consistencies. | |
| 63 | scheduled rg advance | RGADVANCE;1 | SET OF CODES | 0:OFF 1:ON | This field enables the automatic RAID Group Advance. It is necessary to set the date of the next RG ADVANCE DATE (63.3) and the RG ADVANCE TIME (63.4). If the RG ADVANCE TIME is null, the default is 0. | |
| 63.1 | rg advance frequency | RGADVANCE;2 | NUMERIC | This number in days (between 1 and 365) and the RG ADVANCE TIME determine the date and time of the next scheduled RAID Group Advance. | ||
| 63.2 | date of last rg advance | RGADVANCE;3 | DATE-TIME | This is the date of the last scheduled RAID Group Advance was executed and is automatically set at the beginning of a RAID Group Advance execution. | ||
| 63.3 | rg advance date | RGADVANCE;4 | DATE-TIME | This is the scheduled date (today or later) of the next RAID GROUP advance. | ||
| 63.4 | rg advance time | RGADVANCE;5 | NUMERIC | This number (between 0 and 2359) for military time is the time of day of the RAID Group advance function. If this number is undefined, the BP Queue Processor uses the default value of 0 if the Scheduled RAID Group Advance option is enabled and the frequency days plus date of last RAID Group Advance threshold are reached. | ||
| 66 | bp mail message | 6;0 | MULTIPLE | 2006.166 | This table allows each Imaging site to manage the local distribution of all BP Queue Processor messages as well as the monthly and ad hoc site usage reports. | |
| 70 | ct presets | CT;1 | FREE TEXT | A Series of CT Presets delimited by '~'. Defined at the site. These are used by the Imaging Display Radiology Viewer. They are presented to the user on the CT Presets Menu Option. example of two : Abdomen|350|1041~Bone|500|1274 | ||
| 71 | ct presets 2 | CT2;1 | FREE TEXT | A Series of CT Presets delimited by '~'. Defined at the site. These are used by the Imaging Display Radiology Viewer on Clients running Patch 72 or later. They are presented to the user on the CT Presets Menu Option. example of two : Abdomen|350|1041~Bone|500|1274 | ||
| 100 | default user preference | USERPREF;1 | POINTER | 2006.18 | This field contains the user preference setting for first time users of the Imaging System. This field points to the Imaging User Preference file (2005.18). If this field is empty, the default user preferences are created by the imaging routines. | |
| 101 | default muse site # | USERPREF;2 | NUMERIC | Enter the default MUSE site that the Imaging Display application will connect to. Site numbers are usually 1,2,3... etc. If this field is empty, the application will default to 1. Most sites that have a MUSE server that serves EKG data to a single Medical Center would have the MUSE site number set to 1. If multiple sites are sharing a single MUSE server, each site could be assigned a unique MUSE site number by Marquette. In some cases a single shared MUSE database has been created to serve multiple Medical Centers. In this case all sites would most likely have the MUSE site number set to 1. | ||
| 102 | pct free space dicom msgs | 3;5 | NUMERIC | The value of this field is the minimum percentage of free space for a DICOM server. | ||
| 103 | retention days dicom msgs | 3;6 | NUMERIC | The value of this parameter is the number of days that DICOM messages are to be retained. The subroutine that purges old DICOM messages will only remove messages that are older than this number of days. | ||
| 120 | use capture keys | KEYS;1 | SET OF CODES | 1:TRUE 0:FALSE | This field controls whether the Image capture security keys will be used. If set to true, the appropriate keys must be given for the appropriate Image capture. 'Capture' functionality and Procedure lookup functionality will not be allowed from the capture window if the user does not have the proper security key allocated. The Medicine procedure selection window will only display the types of procedures that the user has keys for. | |
| 121 | timeout windows display | KEYS;2 | NUMERIC | This is the number of Minutes used as the Time Out for the Imaging Display Application. If no activity occurs for this number of minutes, the user will be prompted with a dialog window and given 30 seconds to 'Click' on the 'Stay Connected' button or the application will be closed. | ||
| 122 | timeout windows capture | KEYS;3 | NUMERIC | This is the number of Minutes used as the Time Out for the Imaging Capture Application. If no activity occurs for this number of minutes, the user will be prompted with a dialog window and given 30 seconds to 'Click' on the 'Stay Connected' button or the application will be closed. | ||
| 123 | timeout windows vistarad | KEYS;4 | NUMERIC | This is the number of Minutes used as Time Out for the Imaging VISTARad Application. If no activity occurs for this number of minutes, the user will be prompted with a dialog window and given 30 seconds to 'Click' on the 'Stay Connected' button or the application will be closed. | ||
| 124 | dicom gateway access code | GW;1 | FREE TEXT | The value of this field is a string that may be used by a DICOM Gateway when it needs to provide an ACCESS CODE to the VistA system. This field is also used for auto-login for the BP Queue Processor, Purge and Verifier applications. This value is stored encrypted. | ||
| 125 | dicom gateway verify code | GW;2 | FREE TEXT | The value of this field is a string that may be used by a DICOM Gateway when it needs to provide a VERIFY CODE to a VistA system. This field is also used for auto-login for the BP Queue Processor, Purge and Verifier applications. This value is stored encrypted. | ||
| 126 | last routing activity | LASTROUTE;1 | DATE-TIME | The value of this field is a date (FileMan format, date only, no time). This value indicates the most recent date on which any routing activity took place at the current site. Routing activity can be either Rule Evaluation or Image Transmission. | ||
| 127 | last routing check | LASTROUTE;2 | DATE-TIME | The value of this field is a date (FileMan format, date only, no time part). This value indicates the most recent date on which a check was performed whether or not Routing is still active at the current site. | ||
| 130 | *version checking | KEYS;5 | BOOLEAN | 0:NO 1:YES | This field is obsolete. The value of the field does not control which Imaging Clients are supported. | |
| 131 | telereader timeout (minutes) | KEYS;6 | NUMERIC | The number of minutes that the TeleReader application will remain active before closing due to inactivity. If this field is undefined, the application will not timeout. Max value is 999999, no decimals allowed. | ||
| 132 | version nag message | KEYS;7 | BOOLEAN | 0:NO 1:YES | Enter Yes to display a message to clients that are supported, but are not the released version. This message will inform the user that they should update their version of Imaging Client to the released version. Enter No to suppress the message. No message will display. | |
| 133 | timeout windows importer | KEYS;8 | NUMERIC | This is the number of Minutes used as the timeout for the Imaging Importer Application. If no activity occurs for this number of minutes, the user will be prompted with a dialog window and given 30 seconds to click on the 'Stay Connected' button or the application will be closed. (MAG*3.0*136) | ||
| 134 | telepath unread-retention days | TELEPATH;1 | NUMERIC | This field is used as the default value, in days, by the TELEPATHOLOGY UNREAD WORKLIST for purges. An unread case will be purged after this number of days. | ||
| 135 | timeout windows telepathology | KEYS;9 | NUMERIC | This is the number of Minutes used as Time Out for the Imaging Telepathology Application. If no activity occurs for this number of minutes, the user will be prompted with a dialog window and given 30 seconds to 'Click' on the 'Stay Connected' button or the application will be closed. | ||
| 201 | vistarad grouping | 201;0 | MULTIPLE | 2006.1201 | This field allows multiple Institutions and/or Associated Institutions to be grouped together within VistARad for purposes of Exam Locking and Unread Exams lists display. | |
| 202 | default vistarad userpref rad | 5;7 | POINTER | 2006.68 | Points to a reference MAGJ USER DATA file entry which will serve as the default for initializing new radiologist's profiles. | |
| 203 | default vistarad userpref non | 5;8 | POINTER | 2006.68 | Points to a reference MAGJ USER DATA file entry which will serve as the default for initializing new NON-radiologist's profiles. | |
| 300 | rad technologist | IMPORTER;1 | POINTER | 200 | This is the Radiology Technologist who will be responsible for the importing of the exam. | |
| 301 | rad film size | IMPORTER;2 | POINTER | 78.4 | This is the Film Size to be associated with imported exams. | |
| 302 | rad primary diagnostic code | IMPORTER;3 | POINTER | 78.3 | This is the primary diagnostic code to be associated with imported exams. | |
| 303 | rad primary camera/equip/rm | IMPORTER;4 | POINTER | 78.6 | This is the primary camera/equip/room to be associated with imported exams. | |
| 304 | rad cpt modifiers | IMPORTER;5 | POINTER | 81.3 | This is the CPT modifier to be associated with imported exams. |