Files > CP INSTRUMENT

name
CP INSTRUMENT
number
702.09
location
^MDS(702.09,
description
This file contains the list of instruments used by the Clinical Procedures package. This file is exported with data.
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1FREE TEXTBName or mnemonic of instrument - used by vendor in HL7 message header.
.02notification mailgroup0;2POINTER3.8This field contains a pointer to a VA Mailman Mail Group that will receive error messages and other notifications dealing with this device from the interface routines.
.03description0;3FREE TEXTThis field contains a short informational description text for the instrument.
.05delete when submitted0;5BOOLEAN0:No
1:Yes
Select 'Yes' if you want files created by this instrument deleted once they are successfully copied to the VistA Imaging Server. Deletion will be performed by the VistA Imaging application.
.06printable name0;6FREE TEXTName of instrument that is printed on reports/etc.
.07default file ext0;7FREE TEXTDefault file extension for vendor instrument reports (e.g. .doc .pdf).
.08serial number0;8FREE TEXTVendor serial number of the instrument (for reference only).
.09active(+)0;9BOOLEAN0:No
1:Yes
Whether or not the instrument is active on the network.
.1id(+)ID;1FREE TEXTThis is a Globally Unique IDentifier (GUID) for this instrument. This is maintained nationally so it is the same throughout the enterprise. A sample ID could be "{69DBD11E-9A8C-4ECE-AFA4-73947218807D}".
.11processing routine.1;1FREE TEXTName of the MUMPS routine used to process interface information.
.12processing code.1;2SET OF CODESM:Medicine
C:CP V1.0
O:CliO
This field indicates whether data from this instrument will upload to the "M"edicine, "C"linical Procedures, or Clinical "O"bservations package for processing.
.13bi-directional.1;3BOOLEAN0:No
1:Yes
'Yes' or 'No" to indicate if this device can accept HL7 messages from VistA.
.14ip address.1;4FREE TEXTThis field contains the IP address of this instrument.
.15port.1;5NUMERICThis field contains the port number for this instrument.
.16hl7 instrument id.1;6FREE TEXTThis is the name of the actual device where the device name can be 'SMC St. Louis'. This field is used to ID the device.
.17hl7 universal service id.1;7FREE TEXTThis field defines what type of procedure the device can perform if the device can perform more than one procedure.
.18hl7 logical link.1;8POINTER870This field contains the HL7 Logical Link. There is one unique link for each instrument. Used to determine where the bi-directional messages are sent. (Reference IA #1496)
.21server name.2;1FREE TEXTNetwork name of instrument server application that generates the attachments.
.22server share.2;2FREE TEXTShare folder/drive on the instrument server where the report is stored.
.23server path.2;3FREE TEXTPath on the network where the report is stored.
.24server executable.2;4FREE TEXTName of server program that is ran to create the report for the interface.
.301process unc.3;1BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces UNC type data.
.302process text.3;2BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces text type data.
.303process url.3;3BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces URL type data.
.304process dll.3;4BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces DLL type data.
.305process uuencode.3;5BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No" to indicate if this instrument produces UUENCODE type data.
.306process xml.3;6BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces XML type data.
.307process xms.3;7BOOLEAN0:No
1:Yes
Enter 'Yes' or 'No' to indicate if this instrument produces XMS type data.

Referenced by 2 types

  1. CP TRANSACTION (702) -- submitted to instrument
  2. CP RESULT REPORT (703.1) -- instrument