Home Package List Routine Alphabetical List Global Alphabetical List FileMan Files List FileMan Sub-Files List Package Component Lists Package-Namespace Mapping

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | Found Entries | External References | Global Variables Directly Accessed | Local Variables | All

Print Page as PDF

Global: ^LAHM(62.48

Package: Automated Lab Instruments

Global: ^LAHM(62.48

Information

FileMan FileNo	FileMan Filename	Package
62.48	LA7 MESSAGE PARAMETER	Automated Lab Instruments

Description

This file is used to store parameters associated with a Lab Messaging system configuration.

Directly Accessed By Routines, Total: 50

Package	Total	Routines
Automated Lab Instruments	46	ALERT CONDITION LA66 LA68 LA7CHKF LA7HDR LA7HDR1 LA7HL7 LA7LOG LA7PCFG LA7POC LA7PURG LA7SMB1 LA7SMU2 LA7SRPT1 LA7SRPT2 LA7SRPT3 LA7SRPT4 LA7UCFG LA7UID LA7UID1 LA7UIIN LA7UIO1 LA7UTILA LA7UTILB LA7UXQA LA7VHL LA7VHLU1 LA7VHLU8 LA7VIN LA7VIN1 LA7VIN4 LA7VLCM2 LA7VLCM7 LA7VMSG LA7VMSG1 LA7VOBRB LA7VOBX2 LA7VORM1 ^LAHM(62.93 LA7VSET LA7VSET1 LA7VSTP1 ^LAHM(62.48 NON-VA ORDER SNOMED CODES REMOTE SYSTEM ID ^LAHM(62.485
Lab Service	3	LRVRARU LRVRPOCU LRWRKINC
Kernel	1	FILE

Accessed By FileMan Db Calls, Total: 11

Package	Total	Routines
Automated Lab Instruments	9	LA7LOG LA7PCFG LA7UCFG LA7VHLUA LA7VIN1A LA7VIN1B LA7VSET LA7VSET1 LA7VSTP1
Lab Service	2	LRVRPOC LRVRPOCU

Pointed To By FileMan Files, Total: 4

Package	Total	FileMan Files
Automated Lab Instruments	2	LA7 MESSAGE QUEUE(#62.49)[.5] LAB SHIPPING CONFIGURATION(#62.9)[.07]
Lab Service	2	AUTO INSTRUMENT(#62.4)[8] LAB CODE MAPPING(#62.47)[#62.4701(2.2)]

Pointer To FileMan Files, Total: 4

Package	Total	FileMan Files
Lab Service	2	TOPOGRAPHY FIELD(#61)[#62.482(.01)] COLLECTION SAMPLE(#62)[#62.482(.01)]
Health Level Seven	1	HL7 NON-DHCP APPLICATION PARAMETER(#770)[7]
MailMan	1	MAIL GROUP(#3.8)[#62.481(.02)]

Fields, Total: 13

Field #	Name	Loc	Type	Details
.01	CONFIGURATION	0;1	FREE TEXT	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X` LAST EDITED: `APR 25, 1994` HELP-PROMPT: `Answer must be 3-30 characters in length.` DESCRIPTION: `This field contains the descriptive name for all Lab Messaging configurations. Each external partner that the Lab system exchanges messages with should have an entry in the file, e.g. OERR, Universal Interface.` CROSS-REFERENCE: `62.48^B` `1)= S ^LAHM(62.48,"B",$E(X,1,30),DA)=""` `2)= K ^LAHM(62.48,"B",$E(X,1,30),DA)`
1	PROTOCOL	0;2	SET	'HL7' FOR HEALTH LEVEL SEVEN; 'X12' FOR ANSI X.12; '1238' FOR ASTM 1238; '1381' FOR ASTM 1381; '1394' FOR ASTM 1394; 'LOCAL' FOR LOCAL; LAST EDITED: `JAN 22, 1995` HELP-PROMPT: `Enter the protocol name that best fits this configuration.` DESCRIPTION: `This field should contain the type of messages that are used by this configuration. This field is primarily for documentation.`
2	STATUS	0;3	SET	'1' FOR ACTIVE; '0' FOR INACTIVE; LAST EDITED: `APR 25, 1994` HELP-PROMPT: `Enter "Active" to allow this configuration to send and receive messages.` DESCRIPTION: `This field is used to turn this configuration on or off.`
3	GRACE PERIOD FOR MESSAGES	0;6	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>31)!(X<1)!(X?.E1"."1N.N) X` LAST EDITED: `MAR 05, 1997` HELP-PROMPT: `Type a Number between 1 and 31, 0 Decimal Digits.` DESCRIPTION: `Grace period determines the number of days that messages for this configuration are kept on the system before purging when the message status is "purgable". If this field is left blank, the system assumes 3 days. These` `messages are found in the LA7 MESSAGE QUEUE file (#62.49). When messages have status of "error" they remain on the system until their corresponding error message is removed from the XTMP global by a KERNEL cleanup task.` `The messages then become "purgable".`
4	LOG ERRORS	0;4	SET	'0' FOR OFF; '1' FOR ON; LAST EDITED: `FEB 04, 1997` HELP-PROMPT: `Answer "Yes" to log errors in ^XTMP.` DESCRIPTION: `If turned on, errors or exceptional conditions that occur during message processing are stored in the ^XTMP global for review. To review the log, in programmer mode, type D PRINT^LA7LOG.`
5	PROCESS IN	1;E1,245	MUMPS	INPUT TRANSFORM: `K:$L(X)>245 X D:$D(X) ^DIM` LAST EDITED: `MAY 07, 1994` HELP-PROMPT: `This is Standard MUMPS code.` DESCRIPTION: `This field is executable MUMPS code. It should contain a call to an application routine that will process the incoming message. For a Universal Interface setup, it should contain the call D QUE^LA7UIIN.` `WRITE AUTHORITY: @`
6	PROCESS DOWNLOAD	2;E1,245	MUMPS	INPUT TRANSFORM: `K:$L(X)>245 X D:$D(X) ^DIM` LAST EDITED: `MAY 16, 1994` HELP-PROMPT: `This is Standard MUMPS code.` DESCRIPTION: `This field contains executable MUMPS code. It should contain the call point in a routine that will process building a message to be sent to the receiving system. For a Universal Interface configuration it should contain` `the call D EN^LA7UID1.` `WRITE AUTHORITY: @`
7	HL7 NON-DHCP APPLICATION	0;5	POINTER TO HL7 NON-DHCP APPLICATION PARAMETER FILE (#770)	HL7 NON-DHCP APPLICATION PARAMETER(#770) LAST EDITED: `MAY 16, 1994` HELP-PROMPT: `Used to call the HL7 package with the appropriate remote system identifier.` DESCRIPTION: `This field is a pointer to the HL7 NON-DHCP APPLICATION PARAMETER file (#770). The field is used by the Universal Interface to create an Health Level Seven message using the Vista HL7 v1.5 package.` TECHNICAL DESCR: `The variable HLNDAP is often required by the HL7 package. This is a pointer to the HL7 NON-DHCP APPLICATION PARAMETER file (#770). This field is a pointer to that file and can be used in messaging building routines to` `set the HLNDAP variable.`
10	MULTIPLE ORDERS	0;8	SET	'0' FOR MULTIPLE PATIENTS; '1' FOR SINGLE PATIENT; '2' FOR SINGLE ORDER; LAST EDITED: `AUG 31, 2001` HELP-PROMPT: `Select if multiple/single patients/orders should be sent in a single message. See description (??) for additional help.` DESCRIPTION: `Determines when building a HL7 message if message should contain only one patient/order or multiple patients/orders.` `Default is multiple patients per message if possible.` `This allows site to configure message building when communicating with a non-VA system that can not handle a message that has more than one patient in the message. It applies to both order (ORM) and result (ORU) messages.` `When communicating with a VA facility this field can be left blank (default) or set to 0 - MULTIPLE PATIENTS` `If the receiving system can only accept one patient per HL7 message then select 1 - SINGLE PATIENT. This will place multiple orders or results for multiple orders in one message but only one patient will be contained in` `the message.` `If the receiving system can only accept one order per HL7 message then select 2 - SINGLE ORDER. This will place in the message one order or the results associated with one order for a single patient` `Note: An order in the VA is considered those tests found on one accession. What the VA considers as an accession other non-VA systems may refer to as an order.`
11	INTERFACE TYPE	0;9	SET	'1' FOR LAB UI; '10' FOR LEDI; '20' FOR POC; '21' FOR POCA; '30' FOR HDR; '40' FOR OCS; '99' FOR OTHER; LAST EDITED: `OCT 19, 2007` HELP-PROMPT: `Enter the purpose for this messaging interface.` DESCRIPTION: `This field determines how and for what purpose this configuration is used. It allows the laboratory software to generate, handle and process messages.` `LAB UI - Used to identify configurations that are for processing` `laboratory automated instrument data via a generic interface` `manager.` `LEDI - Designate entries involved with Laboratory Electronic Data` `Interchange (LEDI). Used to identify interfaces involved in` `the generation, transmission and processing of HL7 order (ORM)` `and result (ORU) messages involving reference laboratory` `testing between VistA and other VistA systems, commercial` `reference laboratories, DoD laboratories and civilian` `institutions.` `POC - Point of Care (POC) interface. These interfaces transmit` `laboratory test results for which there is no pre-existing` `VistA laboratory order. VistA creates an order as part of` `result processing and storage.` `POCA - Point of Care interface that subscribes to HL7 patient` `demographic (ADT) messages from VistA. Used by POC interfaces` `that subscribe to patient information from VistA to maintain` `the POC's patient database.` `HDR - Designates interface to the VA Health Data Repository (HDR).` `And those systems which subscribe to VistA Lab HL7 Result (ORU)` `messages broadcast by VistA when lab results are made available` `within VistA. Examples are COTS clinical decision support` `systems.` `OCS - Order Collection System. Interfaces involved in phlebotomy` `and other specimen collection systems. Information regarding` `lab orders and specimen requirement are transmitted to an` `external system which assists in the specimen collection` `and updates VistA Lab with information related to the specimen` `and the related order/accession.` `OTHER - Designate other non-laboratory interfaces that utilize the` `Laboratory package.`
20	ALERT CONDITION	20;0	SET Multiple #62.481	62.481 DESCRIPTION: `This field allows the user to identify whether to receive alerts when there are new results, new orders or when an error is logged to the ^XTMP global.`
30	NON-VA ORDER SNOMED CODES	SCT;0	VARIABLE POINTER Multiple #62.482	62.482 DESCRIPTION: `Allows mapping a SNOMED CT code to specimen (topography) and/or collection sample which an external system requires and which is different from the SNOMED CT code assigned to the concept by the Dept of Veterans Affairs.` TECHNICAL DESCR: `This field uses a combination of an Output Transform and a "WRITE ID" node in the DD to display the file that the particular entry is from.` IDENTIFIED BY: `"LA": D EN^DDIOL(" "_$$ID62482^LA7XREF(),"","$C(32)")` INDEXED BY: `VA FILE ENTRY & SNOMED CT ID (AC), SNOMED CT ID & VA FILE ENTRY (AD), SNOMED CT ID & VA FILE ENTRY (AD1), SNOMED CT ID & VA FILE ENTRY (AD2)`
90	REMOTE SYSTEM ID	90;0	Multiple #62.483	62.483 DESCRIPTION: `This field is used to locate the correct configuration in this file when a message is received from a remote system. Most messaging protocols contain information about the system that originated the message and the system` `that is the destination. Since there can be several senders and receivers, this field can be used to determine the correct receiver by using a special lookup on this field. The Universal Interface utilizes this field in` `the following manner.` `The VISTA Health Level Seven (HL7) package requires that every message must have four fields in the message header so that it can determine the application route for the message. Those four fields are called Sending` `Application, Sending Facility, Receiving Application, and Receiving Facility. The HL7 software must find values for each of these fields in the message within the HL7 package files. The fields must match in the following` `way.` `For HL7 v1.5 interfaces` `Sending Application = the NAME field (#.01) in the HL7 NON-DHCP` `APPLICATION PARAMETER file (#770)` `Sending Facility = the NON-DHCP FACILITY NAME field (#3) in File 770` `Receiving Application = the NAME field (#.01) in the HL7 APPLICATION` `PARAMETER file (#771)` `Receiving Facility = the DHCP STATION NUMBER field (#2) in File 770` `For HL7 v1.6 interfaces` `Sending Application = the NAME field (#.01) in the HL7 APPLICATION` `PARAMETER file (#771)` `Sending Facility = the FACILITY NAME field (#3) in File 771` `Receiving Application = the NAME field (#.01) in the HL7 APPLICATION` `PARAMETER file (#771)` `Receiving Facility = the FACILITY NAME field (#3) in File 771` `For the Universal Interface, all four of those fields should be entered into this multiple field, exactly as they are entered in the HL7 fields listed above, including upper and lower case characters. No spaces should be` `entered between the field values. An example of a Universal Interface value for this field is listed below. LAB INTERFACEInstrument ManagerLA AUTO INST695 Where LAB INTERFACE is the NAME in File 770, Instrument Manager is` `the NON-DHCP FACILITY NAME in File 770, LA AUTO INST is the NAME in File 771, and 695 is the DHCP STATION NUMBER in File 770.` `When an HL7 message comes in, these four fields are taken out of the message, concatenated together, and a lookup is done on the "C" cross reference to find this configuration and its associated parameters. The processing` `routine can then continue to process the data.`

Found Entries, Total: 16

CONFIGURATION: LA7POC1	CONFIGURATION: LA7POC2	CONFIGURATION: LA7POC3	CONFIGURATION: LA7POC4	CONFIGURATION: LA7POC5	CONFIGURATION: LA7UI1	CONFIGURATION: LA7UI2	CONFIGURATION: LA7UI3
CONFIGURATION: LA7UI4	CONFIGURATION: LA7UI5	CONFIGURATION: LA7HDR	CONFIGURATION: LA7UI6	CONFIGURATION: LA7UI7	CONFIGURATION: LA7UI8	CONFIGURATION: LA7UI9	CONFIGURATION: LA7UI10

External References

Name	Field # of Occurrence
^DIM	5+1, 6+1
EN^LA7UIO	6(IEN:6), 6(IEN:23), 6(IEN:24), 6(IEN:25), 6(IEN:26), 6(IEN:52), 6(IEN:53), 6(IEN:54), 6(IEN:55), 6(IEN:56)
QUE^LA7VIN	5(IEN:1), 5(IEN:2), 5(IEN:3), 5(IEN:4), 5(IEN:5), 5(IEN:6), 5(IEN:23), 5(IEN:24), 5(IEN:25), 5(IEN:26) , 5(IEN:52), 5(IEN:53), 5(IEN:54), 5(IEN:55), 5(IEN:56)

Global Variables Directly Accessed

Name	Line Occurrences (* Changed, ! Killed)
^LAHM(62.48 - [#62.48]	.01(XREF 1S), .01(XREF 1K)

Local Variables

Legend:

>>	Not killed explicitly
*	Changed
!	Killed
~	Newed

Name	Field # of Occurrence
>> DA	.01(XREF 1S), .01(XREF 1K)
X	.01+1!, .01(XREF 1S), .01(XREF 1K), 3+1!, 5+1!, 6+1!

Info | Desc | Directly Accessed By Routines | Accessed By FileMan Db Calls | Pointed To By FileMan Files | Pointer To FileMan Files | Fields | Found Entries | External References | Global Variables Directly Accessed | Local Variables | All