Background

Clinical laboratory automation involves the integration or interfacing of automated or robotic transport systems, analytical instruments, and pre- or post-analytical process equipment such as automated centrifuges and aliquoters, decappers, recappers, sorters, and specimen storage and retrieval systems. In addition to the electrical and mechanical interfaces of these various components, the computers that control these devices or instruments must also be interfaced to each other and/or the Laboratory Information System (LIS).

The types of information communicated between these systems include process control and status information for each device or analyzer, each specimen, specimen container, and container carrier, information and detailed data related to patients, orders, and results, and information related to specimen flow algorithms and automated decision making. This wide array of communicated information is essential for a Laboratory Automation System (LAS) to control the various processes and to ensure that each specimen or aliquot has the correct tests performed in the proper sequence.

As of 1999 there are already more than 200 clinical laboratories in the world with "total laboratory automation" systems and hundreds more with a lesser level of automation – generally workcells or modular automation systems. The development of prospective standards for these aspects of clinical laboratory automation will facilitate the inter-operability of the systems being developed by the various players in lab automation – the vendors of analytical instruments, LIS systems, automation systems and components and their laboratory customers.

In the early 1990's an ad hoc task force, Clinical Testing Automation Standards Steering Committee (CTASSC), began to meet at the annual meetings of the International Conference on Automation and Robotics (ICAR) and the American Association for Clinical Chemistry (AACC). In 1996, CTASSC approached NCCLS,1 a globally-recognized, consensus standards organization that has developed more than 125 clinical laboratory standards and related products since it was founded in 1968, about taking on a project for clinical laboratory automation. NCCLS agreed to sponsor this project which was separately funded via a direct solicitation of the vendors in lab automation, instruments, LIS systems, and automation customers. It was organized as a "fast track" project to develop prospective standards to guide future developments in laboratory automation. With the oversight of an Area Committee on Automation, five separate subcommittees have worked since 1997 to develop a series of prospective standards for:

• Specimen containers and carriers

• Bar codes for specimen container identification

• Communications

• System operational requirements and characteristics

• Electromechanical interfaces

Approved level standards for all five of these areas were published by NCCLS.

[1]     NCCLS, 940 West Valley Road, Suite 1400, Wayne, PA 19087; www.nccls.org

Introduction

This chapter specifies HL7 triggers, messages, and segments required for implementation of clinical laboratory automation communication interfaces. It was developed jointly by the HL7 Laboratory Automation Special Interest Group and the NCCLS Subcommittee on Communications with Automated Systems. This chapter, by agreement between HL7 and NCCLS, is also published in its entirety as part of the NCCLS Approved Level standard:

• AUTO3, "Laboratory Automation: Communications with Automated Clinical Laboratory Systems, Instruments, Devices, and Information Systems, © NCCLS" ²

This document contains other chapters to enable a vendor to successfully implement all of the elements essential to meet the standard.

The other related NCCLS clinical laboratory automation standards are:

• AUTO1: "Laboratory Automation: Specimen Container / Specimen Carrier", © NCCLS.

• AUTO2: "Laboratory Automation: Bar Codes for Specimen Container Identification", © NCCLS.

• AUTO4: "Laboratory Automation: Systems Operational Requirements, Characteristics, and Information Elements", © NCCLS.

• AUTO5: "Laboratory Automation: Electromechanical Interfaces", © NCCLS.

The reader is referred to any or all of these NCCLS standards, particularly AUTO3 and AUTO4, for detailed information on the communications requirements in clinical laboratory automation applications.

The control model proposed in this standard is an extension of the model described in LECIS:

• ASTM E1989-98. Laboratory Equipment Control Interface Specification (LECIS). American Society for Testing and Materials; 1998.

[2]     (NCCLS. Laboratory Automation: Communications With Automated Clinical Laboratory Systems, Instruments, Devices, and Information Systems; Approved Standard - NCCLS Document AUTO3-A [ISBN 1-56238-361-2}. NCCLS, 940 West Valley Road, Suite 1400, Wayne, PA 19087-1898 USA, 2000). www.nccls.org

Glossary

The terminology found in ANSI X3.182-19903 shall be used where applicable. Other computer-related technical terms used in this document can be found in ASTM Terminology E 10134, IEEE 1005, IEEE 6106, and ANSI X3.172.7

[3]     ANSI Standard X3.182-1990. Bar Code Print Quality Guidelines. New York, NY: American National Standards Institute; 1995

[4]     ASTM E1013-93. Standard Terminology Relating to Computerized Systems. West Conshohocken, PA: American Society for Testing and Materials; 1993

[5]     IEEE 100. Dictionary of Electrical and Electronics Terms. Institute of Electrical and Electronics Engineers, Inc.; 1996

[6]     IEEE 610. Glossary of Computer Languages. Institute of Electrical and Electronics Engineers, Inc.; 1993

[7]     ANSI X3.172-1996. Information Technology – American National Standards Dictionary of Information Technology (ANSDIT). New York, NY: American National Standards Institute; 1996

Accession Identifier (also accession number):

A numeric (or alphanumeric) identifier assigned by the LIS for a test order. Depending on the particular LIS a patient's test orders for a single encounter may use one or more accession identifiers and each accession identifier may encompass one or more tests and one or more specimens and/or specimen containers. However, accession identifiers are unique within each patient encounter. The Accession identifier may not be equal to the Placer or Filler Order Numbers, because of uniqueness requirement.

Additive:

As used here, refers to a substance generally a chemical that has been added to a specimen collection tube or container to prevent degradation of one or more constituents of the specimen.

Aliquot:

In Quantitative Analysis, a sample comprising a known fraction or measured portion of the whole; 2) In NCCLS LAB AUTOMATION Standard documents, a portion of a specimen placed in a separate container to facilitate concurrent testing or to hold in reserve for future use.

Notes: a) The portion of the specimen is typically removed from the original specimen after initial processing, such as centrifugation, to obtain serum or plasma samples, and is considered to be chemically identical to all other subdivisions of an original sample of serum, plasma, urine, CSF, etc.;

b) It may be necessary to identify the aliquot as an individual specimen distinct from the original specimen in a collection container labeled with a unique identifier that may be linked to or associated with the primary collection container.

Analyzer:

An instrument and/or specimen processing and handling device that performs measurements on patient specimens of quantitative, clinically relevant analytes.

Note: A portion of a patient's specimen is consumed in the analytic process.

Automated:

A characterization applied when all analytical processes, including sample and reagent uptake, sample/reagent interaction, chemical/biological analysis, result calculation, and result readout are mechanized.

Automated instrument:

A laboratory instrument that may or may not be connected to a laboratory information system (LIS), hospital information system (HIS), and/or laboratory automation system (LAS), which performs measurements on a patient's sample;

Note: These instruments may have specific hardware and/or software modifications that allow interfacing to a laboratory automation system.

Automation system:

An automation system refers to a variety of possible systems that can include some of the following types: automated instruments, laboratory information systems (LIS), laboratory automation systems (LAS), hospital information systems (HIS), and front-end processing devices.

Bar code:

An array of parallel rectangular bars and spaces that creates a symbology representing a number or alphanumeric identifier.

Bar length:

The length of the bars in the bar code.

Barrier:

See Separator

Barrier Delta:

Identifies the distance from the Point of Reference to the separator material (barrier) within the container. This distance may be provided by the LAS to the instrument and/or specimen processing/handling device to facilitate the insertion of a sampling probe into the specimen without touching the separator. See the Point of reference definition or in NCCLS standard AUTO5 Laboratory Automation: Electromechanical Interfaces.

Bottom of cap:

The farthest point from the top of the container/test tube that the cap reaches.

Note: This point may be inside the tube.

Bottom of container//Bottom of tube:

The portion of the container/test tube farthest from the cap (see Point of reference).

Bottom of tube:

See Bottom of container.

Carrier:

See Specimen carrier.

Character:

1) The smallest abstract element of a writing system or script.

Note: A character refers to an abstract idea rather than to a specific shape.

2) A code element.

Clinical laboratory automation:

The integration of laboratory personnel and preanalytical, analytical, and postanalytical processes and information systems.

Clinical laboratory automation systems:

An assemblage of components that mechanically and electronically transfers, analyzes, and processes information and material related to clinical diagnostic testing of patient specimens, controls, calibrators, standards, and images.

Closed-container sampling//Closed-tube sampling:

The action of aspirating a sample from a container/tube with the closure in place, requiring the sample probe to pierce the closure of the container/sample container.

Closed-tube sampling:

See Closed-container sampling.

Container//Tube//Test Tube:

See Specimen container.

Container Identifier

A numeric (or alphanumeric) identifier provided by the LIS or LAS to uniquely identify each specimen container or aliquot container. The NCCLS LAB AUTOMATION STANDARD requires a unique identifier for each container introduced into the LAS or leaving the LAS.

Cycle time components:

The identified time segments of the process of moving from one sample to the next, including: presentation of specimen along transportation system to docking site at instrument; identification/recognition that the correct specimen is in place; either direct aspiration from specimen container by probe, or transfer of specimen container to instrument, aspiration, and return of specimen container to specimen carrier/transportation system; departure of completed specimen container; movement into position of next specimen container.

Decapping:

The removal of a closure from a specimen container.

Delimiter:

A symbol used to separate items in a list.

Directions of the specimen, Transportation system, Instrument or Specimen processing and handling device interfaces:

The orthogonal axes.

Note: a) These axes are demonstrated in Figure 13-1.

Figure 13-1. Physical Frame of Reference in a Three-Dimensional Space (X-Y-Z)

X–direction, n - The direction that a specimen travels along a transportation system.

Note: b) Specimens would move along the X dimension as, for example, in transportation from station to station in a laboratory (see Figure 13-2.)

Figure 13-2. X Direction

Y–direction, n - The horizontal direction perpendicular to specimen travel along a transportation system;

Note: c) Specimens could move in the Y dimension away from a transport system to be placed onto an instrument for analysis (see Figure 13-3). The sample probe would move in the Y dimension as it moves out from the instrument or specimen processing and handling device to a position directly over the specimen container.

Figure 13-3. Y Direction

Z–direction, n - The vertical dimension;

Notes: d) Specimens could be lifted in the Z dimension off a transport system for transfer between locations;

e) The center line of a container should be controlled, so it is in the Z dimension; a specimen centering device would be referenced to the Z dimension; a sample probe would follow the Z dimension as it moves downward into a specimen container to aspirate serum, blood, etc. for analysis (see Figure 13-4);

    f) Rotation about the Z dimension may be used to locate and read the bar-code label on a specimen container or to assess the quality of a specimen in terms of turbidity, hemolysis, icterus, etc.

Figure 13-4. Z Direction

Directions of the sample, Transportation system, Instrument or Specimen processing handling device and interfaces

See Directions of the specimen, etc.

Direct track sampling:

The process in which aspiration of a sample occurs directly from the specimen container while it is on the transportation system, whereby the instrument probe extends to reach the specimen container on the transportation system;

Note: This process requires agreement between the transportation system and the instrument and specimen processing and handling devices regarding point of reference (POR) to guide movement of the probe to the specimen.

Docking site:

1) The location of the physical interface between two components of a system; 2) In NCCLS LAB AUTOMATION Standard documents, the interface between the transportation system and the instrument and/or the specimen processing and handling devices where the specimen container arrives for sampling to occur.

Flection:

The point at which the vertical (straight) walls of the specimen container bend to form the base.

Interaction:

A standard exchange of messages between two instances of equipment that synchronizes the execution of one or more commands. State models are used describe the standard interactions.

Label:

1) The display of written, printed, or graphic matter upon the immediate container of any article; 2) In NCCLS LAB AUTOMATION Standard documents, the paper and attached adhesive coating on which the bar code and other human readable information is printed.

Laboratory automation system (LAS):

A system of information and hardware technology that allows the operation of the clinical laboratory process without significant operator intervention;

Note: Typical functionality includes information system control of the instruments through direct LAS interfacing, including any technology that manipulates the specimen (i.e., centrifuge); transportation of the specimen; result evaluation, repeat testing, reflex testing; and quality assessment and results reporting.

Laboratory equipment control interface specification (LECIS):

A high-level protocol that defines message content for standard behaviors or interactions for remote control of analytical instruments and devices (ASTM E 1989-98).

Laboratory information system (LIS):

The information system that is responsible for management of data regarding patient specimen identification, tests requested, results reported, quality control testing, and other aspects of sample analysis.

Notes: a) The LIS interfaces directly with the LAS to communicate patient, visit, container, test orders, specimen status, and results about specific testing to be done;

b) Instrument or specimen processing and handling devices may be interfaced with the LIS or the LAS to direct specific testing and to retrieve results for reporting;

c) The LIS is frequently also interfaced to a clinical information system for use by physicians and other medical personnel.

LECIS:

Acronym for Laboratory Equipment Control Interface Specification, (ASTM E 1989-98).

Location:

A physical place within the laboratory, with a unique identifier (e.g., refrigerator shelf number, instrument buffer ID, track identifier).

Open-container sampling//Open-tube sampling:

The action of aspirating a sample from a specimen container from which the closure has previously been removed.

Note: The sample probe contacts the surface of the specimen without other physical barriers.

Open-tube sampling:

See Open-container sampling.

Pitch:

The center distance between two specimen containers in a carrier or between two sequential specimen container carriers.

Point of reference//Point in space, (POR):

The intersection of the xy plane and an infinite line in the 'z' direction.

Note: The POR is the reference from which all positioning and alignment of specimen containers are measured.

Process instruments:

In NCCLS LAB AUTOMATION Standard documents, components of an automated laboratory comprising the automated devices that perform a multitude of pre- and postanalytical tasks, and perform nonanalytical tasks on specimens, containers, carriers, and similar processes.

Quiet zone:

In NCCLS LAB AUTOMATION documents, the white {blank} space on a bar code immediately preceding the first bar and immediately following the last bar.

Recap:

To replace the closure on a specimen container; either with the original closure or with a new replacement closure.

Robotic arm:

A device capable of moving a specimen container, specimen carrier, or another object in the X, Y, and Z directions.

Note: Unless this device is an integral part of the LAS system, it is considered an instrument for the purpose of this proposed standard.

Sample//(Specimen):

1) A small part of anything ... intended to show the quality, style, or nature of the whole; 2) In NCCLS LAB AUTOMATION Standard documents, a portion or aliquot withdrawn from a container for the actual test;

Notes:     In NCCLS LAB AUTOMATION Standard documents,

a) samples are typically not placed in containers that will have to be uniquely identified, but may go directly into the instrument or specimen processing and handling device test stream or may be placed in sample cups unique to the instrument or specimen processing and handling device;

b) the ID of the specimen is typically assured by computer linkage of the pipetting or aspiration step to the ID of the container from which it was obtained, or by a separate numbering system for the sample cups that is internal to the analytical instrument or specimen processing and handling device.

Sample carrier:

See Specimen carrier.

Sample container:

See Specimen collection container.

Sample-positioning system:

See Specimen-positioning system.

Sample probe:

See Specimen probe.

Separator:

A material such as a gel which is contained in blood collection tubes to facilitate separation of blood cells from blood serum by creating a physical "barrier" between them.

Serum/Plasma Separator:

See Separator.

Service envelope:

In NCCLS LAB AUTOMATION Standard documents, the space around the transportation system and instruments that may be accessed periodically for maintenance or repair of equipment.

Note: A transportation system and analytic instruments should not have mutually impinging service envelopes.

Specimen:

The discrete portion of a body fluid or tissue taken for examination, study, or analysis of one or more quantities or characteristics, to determine the character of the whole.

Note: The substance may still be referred to as a specimen if it has been processed from the obtained specimen; thus, examples of specimens include whole blood and serum or plasma prepared from whole blood; saliva; cerebrospinal fluid; feces; urine; fingernail clippings; hair clippings; tissue samples, even if embedded in a paraffin block; etc.

Specimen carrier//Sample carrier//Carrier:

A device that holds the specimen container.

Note: The specimen carrier interfaces mechanically with the transportation system to move the specimen from location to location, and may carry one specimen container or many specimen containers. (See Figure 13-5.)

Specimen collection container//Specimen container//Sample container//Container:

The tube that holds a patient specimen.

Note: The container typically consists of a glass or plastic closed-end tube with a removable closure on the opposite end. (See Figure 13-5.)

Figure 13-5: Relationship among Specimen Container, Specimen Carrier, Tray, and Locations.

Specimen-positioning system//Sample-positioning system (SPS):

A device to position a specimen container within acceptable tolerances of a POR.

Specimen probe//Sample probe:

A part of an instrument or specimen processing and handling device that aspirates fluid from a specimen and delivers it to the instrument for analysis.

Note: The sample probe can also be called sample proboscis, nozzle, needle, or sampling mechanism.

Stay clear zone:

In NCCLS LAB AUTOMATION Standard documents, the area between the instrument or specimen processing and handling device and the automation hardware that must remain clear of any physical device, ensuring that there is adequate access by the user or service person to either system.

Symbol:

In NCCLS LAB AUTOMATION Standard documents, a combination of bar-code characters, including start/stop characters, quiet zones, data elements, and check characters which form a complete scanning entity.

Test mnemonics:

Short, understandable contractions for test names.

Top of container//Top of tube:

The open end of the container/test tube, closest to the cap.

Top of tube:

See Top of container.

Tray:

A holder for one or more carriers (optional). (See Figure 13-5.)

X–direction:

See Directions.

Y–direction:

See Directions.

Z–direction:

See Directions.

ESU/ACK - Automated Equipment Status Update (Event U01)

This message is used to send information about the status of a device or equipment from one application to another (e.g., automated device to a Laboratory Automation System). The status update can be sent unsolicited or as a response to the trigger "Automated Equipment Status Request."

ESU^U01^ESU_U01: Equipment Status Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - ESU_U01

Segment	Cardinality	Must Implement	Status
ESU_U01
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
ISD	0..*		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for ESU^U01^ESU_U01

Send Application Ack: ACK^U01^ACK

Enhanced Mode Acknowledgement Choreography for ESU^U01^ESU_U01

When the MSH-15 value of an ESU^U01^ESU_U01 message is AL or ER or SU, an ACK^U01^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an ESU^U01^ESU_U01 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an ESU^U01^ESU_U01 message is AL or ER or SU, an ACK^U01^ACK message SHALL be sent as an application ack.

When the MSH-16 value of an ESU^U01^ESU_U01 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U01^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U01^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: ESU_U01--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE ESU_U01 --> <!-- .. message definition ESU_U01 --> <xsd:complexType name="ESU_U01.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="ISD" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="ESU_U01" type="ESU_U01.CONTENT" /> </xsd:schema>

Download

ESR/ACK - Automated Equipment Status Request (Event U02)

This message is used to request information about a device's or piece of equipment's status from one application to another (e.g., Laboratory Automation System to automated equipment). The equipment identified in the EQU segment should respond with its status using the "Automated Equipment Status Update."

ESR^U02^ESR_U02: Equipment Status Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - ESR_U02

Segment	Cardinality	Must Implement	Status
ESR_U02
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for ESR^U02^ESR_U02

Send Application Ack: ESU^U01^ESU_U01

Enhanced Mode Acknowledgement Choreography for ESR^U02^ESR_U02

When the MSH-15 value of an ESR^U02^ESR_U02 message is AL or ER or SU, an ACK^U02^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an ESR^U02^ESR_U02 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an ESR^U02^ESR_U02 message is AL or ER or SU, an ESU^U01^ESU_U01 message SHALL be sent as an application ack.

When the MSH-16 value of an ESR^U02^ESR_U02 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U02^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ESU^U01^ESU_U01
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: ESR_U02--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE ESR_U02 --> <!-- .. message definition ESR_U02 --> <xsd:complexType name="ESR_U02.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <xsd:element name="ESR_U02" type="ESR_U02.CONTENT" /> </xsd:schema>

Download

SSU/ACK - Specimen Status Update (Event U03)

This message is used to send information concerning the location and status of specimens from one application to another (e.g., automated equipment to a Laboratory Automation System). The OBX segments attached to the SAC should be used for transfer of information not included in the SAC segment, but relevant for automating processing (e.g., additional characteristics of the specimen container). The NTE segments attached to the SAC should be used for transfer of descriptive information not included in the SAC segment, but relevant for the users (e.g., aliquot groups for an aliquot sample container).

SSU^U03^SSU_U03: Specimen Status Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - SSU_U03

Segment	Cardinality	Must Implement	Status
SSU_U03
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
SPECIMEN_CONTAINER	1..*	Yes	additional
SAC	1..1	Yes	additional
OBX	0..*		additional
NTE	0..*		additional
PRT	0..*		additional
SPECIMEN	0..*		additional
SPM	1..1	Yes	additional
OBX	0..*		additional
PRT	0..*		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for SSU^U03^SSU_U03

Send Application Ack: ACK^U03^ACK

Enhanced Mode Acknowledgement Choreography for SSU^U03^SSU_U03

When the MSH-15 value of a SSU^U03^SSU_U03 message is AL or ER or SU, an ACK^U03^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SSU^U03^SSU_U03 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SSU^U03^SSU_U03 message is AL or ER or SU, an ACK^U03^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a SSU^U03^SSU_U03 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U03^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U03^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: SSU_U03--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE SSU_U03 --> <!-- .. message definition SSU_U03 --> <xsd:complexType name="SSU_U03.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SSU_U03.SPECIMEN_CONTAINER" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="SSU_U03" type="SSU_U03.CONTENT" /> <xsd:complexType name="SSU_U03.SPECIMEN_CONTAINER.CONTENT"> <xsd:sequence> <xsd:element ref="SAC" minOccurs="1" maxOccurs="1" /> <xsd:element ref="OBX" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="NTE" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="SSU_U03.SPECIMEN" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="SSU_U03.SPECIMEN_CONTAINER" type="SSU_U03.SPECIMEN_CONTAINER.CONTENT" /> <xsd:complexType name="SSU_U03.SPECIMEN.CONTENT"> <xsd:sequence> <xsd:element ref="SPM" minOccurs="1" maxOccurs="1" /> <xsd:element ref="OBX" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="SSU_U03.SPECIMEN" type="SSU_U03.SPECIMEN.CONTENT" /> </xsd:schema>

Download

SSR/ACK - Specimen Status Request (Event U04)

This message is used to request information concerning the location and status of specimens from one application to another (e.g., Laboratory Automation System to automated equipment). The request can be addressed for a specific container, a specific carrier, a specific tray or a specific location, depending on the arguments set in the SAC segment. The equipment specified in the EQU segment should respond with the "Specimen Status Update."

SSR^U04^SSR_U04: Specimen Status Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - SSR_U04

Segment	Cardinality	Must Implement	Status
SSR_U04
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
SPECIMEN_CONTAINER	1..*	Yes	additional
SAC	1..1	Yes	additional
SPM	0..*		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for SSR^U04^SSR_U04

Send Application Ack: SSU^U03^SSU_U03

Enhanced Mode Acknowledgement Choreography for SSR^U04^SSR_U04

When the MSH-15 value of a SSR^U04^SSR_U04 message is AL or ER or SU, an ACK^U04^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a SSR^U04^SSR_U04 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a SSR^U04^SSR_U04 message is AL or ER or SU, a SSU^U03^SSU_U03 message SHALL be sent as an application ack.

When the MSH-16 value of a SSR^U04^SSR_U04 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U04^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: SSU^U03^SSU_U03
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: SSR_U04--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE SSR_U04 --> <!-- .. message definition SSR_U04 --> <xsd:complexType name="SSR_U04.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SSR_U04.SPECIMEN_CONTAINER" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="SSR_U04" type="SSR_U04.CONTENT" /> <xsd:complexType name="SSR_U04.SPECIMEN_CONTAINER.CONTENT"> <xsd:sequence> <xsd:element ref="SAC" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SPM" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="SSR_U04.SPECIMEN_CONTAINER" type="SSR_U04.SPECIMEN_CONTAINER.CONTENT" /> </xsd:schema>

Download

INU/ACK – Automated Equipment Inventory Update (Event U05)

This message is used to send information about inventory items from one application to another (e.g., automated Equipment to a Laboratory Automation System).

INU^U05^INU_U05: Inventory Update Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - INU_U05

Segment	Cardinality	Must Implement	Status
INU_U05
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
INV	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for INU^U05^INU_U05

Send Application Ack: ACK^U05^ACK

Enhanced Mode Acknowledgement Choreography for INU^U05^INU_U05

When the MSH-15 value of an INU^U05^INU_U05 message is AL or ER or SU, an ACK^U05^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an INU^U05^INU_U05 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an INU^U05^INU_U05 message is AL or ER or SU, an ACK^U05^ACK message SHALL be sent as an application ack.

When the MSH-16 value of an INU^U05^INU_U05 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U05^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U05^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: INU_U05--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE INU_U05 --> <!-- .. message definition INU_U05 --> <xsd:complexType name="INU_U05.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="INV" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="INU_U05" type="INU_U05.CONTENT" /> </xsd:schema>

Download

INR/ACK – Automated Equipment Inventory Request (Event U06)

This message is used to request information about inventory items from one application to another (e.g., Laboratory Automation System to automated equipment). The equipment specified in the EQU segment should respond with the information about inventory item requested in the INV segment (or all items).

INR^U06^INR_U06: Inventory Request Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - INU_U05

Segment	Cardinality	Must Implement	Status
INU_U05
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
INV	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for INR^U06^INR_U06

Send Application Ack: INU^U05^INU_U05

Enhanced Mode Acknowledgement Choreography for INR^U06^INR_U06

When the MSH-15 value of an INR^U06^INR_U06 message is AL or ER or SU, an ACK^U06^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an INR^U06^INR_U06 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an INR^U06^INR_U06 message is AL or ER or SU, an INU^U05^INU_U05 message SHALL be sent as an application ack.

When the MSH-16 value of an INR^U06^INR_U06 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U06^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: INU^U05^INU_U05
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: INR_U06--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE INR_U06 --> <!-- .. message definition INR_U06 --> <xsd:complexType name="INR_U06.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="INV" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="INR_U06" type="INR_U06.CONTENT" /> </xsd:schema>

Download

EAC/ACK – Automated Equipment Command (Event U07)

This message is used to send equipment commands from one application to another (e.g., a Laboratory Automation System to automated Equipment). The OBR segments attached to the SAC should be used for transfer of information about tests assigned to a specific aliquot in the aliquoting command (not included in the SAC segment, but relevant for automating processing).

The repeatability of the DST segment should be used for multiple destinations in sequence and the remark may be used as additional information, e.g. for destination dependent bar code labels for the secondary (aliquot) containers.

The repeatability of the Specimen Container block enables sending commands for Pooling specimen (multiple sources) from a Primary Specimen. Command for multiple aliquots requires specific Command group for each aliquot.

EAC^U07^EAC_U07: Equipment Command Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - EAC_U07

Segment	Cardinality	Must Implement	Status
EAC_U07
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
COMMAND	1..*	Yes	additional
ECD	1..1	Yes	additional
TQ1	0..1		additional
CNS	0..1		additional
SPECIMEN_CONTAINER	0..*		additional
SAC	1..1	Yes	additional
SPM	0..*		additional
DST	0..*		additional
ORDER_FOR_SPECIMEN_CONTAINER	0..*		additional
OBR	0..*		additional
PRT	0..*		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for EAC^U07^EAC_U07

Send Application Ack: EAR^U08^EAR_U08

Enhanced Mode Acknowledgement Choreography for EAC^U07^EAC_U07

When the MSH-15 value of an EAC^U07^EAC_U07 message is AL or ER or SU, an ACK^U07^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an EAC^U07^EAC_U07 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an EAC^U07^EAC_U07 message is AL or ER or SU, an EAR^U08^EAR_U08 message SHALL be sent as an application ack.

When the MSH-16 value of an EAC^U07^EAC_U07 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U07^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: EAR^U08^EAR_U08
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: EAC_U07--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE EAC_U07 --> <!-- .. message definition EAC_U07 --> <xsd:complexType name="EAC_U07.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EAC_U07.COMMAND" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAC_U07" type="EAC_U07.CONTENT" /> <xsd:complexType name="EAC_U07.COMMAND.CONTENT"> <xsd:sequence> <xsd:element ref="ECD" minOccurs="1" maxOccurs="1" /> <xsd:element ref="TQ1" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EAC_U07.SPECIMEN_CONTAINER" minOccurs="0" maxOccurs="1" /> <xsd:element ref="CNS" minOccurs="0" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAC_U07.COMMAND" type="EAC_U07.COMMAND.CONTENT" /> <xsd:complexType name="EAC_U07.SPECIMEN_CONTAINER.CONTENT"> <xsd:sequence> <xsd:element ref="SAC" minOccurs="1" maxOccurs="1" /> <xsd:element ref="OBR" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="SPM" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAC_U07.SPECIMEN_CONTAINER" type="EAC_U07.SPECIMEN_CONTAINER.CONTENT" /> </xsd:schema>

Download

EAR/ACK – Automated Equipment Response (Event U08)

This message is used to send equipment responses to previously issued commands from one application to another (e.g., automated Equipment to a Laboratory Automation System).

EAR^U08^EAR_U08: Equipment Command Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - EAR_U08

Segment	Cardinality	Must Implement	Status
EAR_U08
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
COMMAND_RESPONSE	1..*	Yes	additional
ECD	1..1	Yes	additional
ECR	1..1	Yes	additional
SPECIMEN_CONTAINER	0..1		additional
SAC	1..1	Yes	additional
SPM	0..*		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for EAR^U08^EAR_U08

Send Application Ack: ACK^U08^ACK

Enhanced Mode Acknowledgement Choreography for EAR^U08^EAR_U08

When the MSH-15 value of an EAR^U08^EAR_U08 message is AL or ER or SU, an ACK^U08^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an EAR^U08^EAR_U08 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an EAR^U08^EAR_U08 message is AL or ER or SU, an ACK^U08^ACK message SHALL be sent as an application ack.

When the MSH-16 value of an EAR^U08^EAR_U08 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U08^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U08^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: EAR_U08--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE EAR_U08 --> <!-- .. message definition EAR_U08 --> <xsd:complexType name="EAR_U08.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EAR_U08.COMMAND_RESPONSE" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAR_U08" type="EAR_U08.CONTENT" /> <xsd:complexType name="EAR_U08.COMMAND_RESPONSE.CONTENT"> <xsd:sequence> <xsd:element ref="ECD" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EAR_U08.SPECIMEN_CONTAINER" minOccurs="0" maxOccurs="1" /> <xsd:element ref="ECR" minOccurs="1" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAR_U08.COMMAND_RESPONSE" type="EAR_U08.COMMAND_RESPONSE.CONTENT" /> <xsd:complexType name="EAR_U08.SPECIMEN_CONTAINER.CONTENT"> <xsd:sequence> <xsd:element ref="SAC" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SPM" minOccurs="0" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAR_U08.SPECIMEN_CONTAINER" type="EAR_U08.SPECIMEN_CONTAINER.CONTENT" /> </xsd:schema>

Download

EAN/ACK - Automated Equipment Notification (Event U09)

This message is used to send equipment notifications from one application to another (e.g., alerts sent by automated equipment to a Laboratory Automation System).

EAN^U09^EAN_U09: Equipment Status Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - EAN_U09

Segment	Cardinality	Must Implement	Status
EAN_U09
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
NOTIFICATION	1..*	Yes	additional
NDS	1..1	Yes	additional
NTE	0..1		additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for EAN^U09^EAN_U09

Send Application Ack: ACK^U09^ACK

Enhanced Mode Acknowledgement Choreography for EAN^U09^EAN_U09

When the MSH-15 value of an EAN^U09^EAN_U09 message is AL or ER or SU, an ACK^U09^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an EAN^U09^EAN_U09 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an EAN^U09^EAN_U09 message is AL or ER or SU, an ACK^U09^ACK message SHALL be sent as an application ack.

When the MSH-16 value of an EAN^U09^EAN_U09 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U09^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U09^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: EAN_U09--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE EAN_U09 --> <!-- .. message definition EAN_U09 --> <xsd:complexType name="EAN_U09.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EAN_U09.NOTIFICATION" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAN_U09" type="EAN_U09.CONTENT" /> <xsd:complexType name="EAN_U09.NOTIFICATION.CONTENT"> <xsd:sequence> <xsd:element ref="NDS" minOccurs="1" maxOccurs="1" /> <xsd:element ref="NTE" minOccurs="0" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <xsd:element name="EAN_U09.NOTIFICATION" type="EAN_U09.NOTIFICATION.CONTENT" /> </xsd:schema>

Download

TCU/ACK - Automated Equipment Test Code Settings Update (Event U10)

This message is used to send information concerning test codes and parameters from one application to another (e.g., automated equipment to a Laboratory Automation System). This message transfers the current snapshot of the test parameters of the sending system. The sent parameter sets are supposed to replace the parameter sets existing at the receiver of this message before the trigger (there is no selective "Add" or "Delete").

TCU^U10^TCU_U10: Test Code Settings Update

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - TCU_U10

Segment	Cardinality	Must Implement	Status
TCU_U10
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
TEST_CONFIGURATION	1..*	Yes	additional
SPM	0..1		additional
TCC	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for TCU^U10^TCU_U10

Send Application Ack: ACK^U10^ACK

Enhanced Mode Acknowledgement Choreography for TCU^U10^TCU_U10

When the MSH-15 value of a TCU^U10^TCU_U10 message is AL or ER or SU, an ACK^U10^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a TCU^U10^TCU_U10 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a TCU^U10^TCU_U10 message is AL or ER or SU, an ACK^U10^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a TCU^U10^TCU_U10 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U10^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U10^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: TCU_U10--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE TCU_U10 --> <!-- .. message definition TCU_U10 --> <xsd:complexType name="TCU_U10.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="TCU_U10.TEST_CONFIGURATION" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="TCU_U10" type="TCU_U10.CONTENT" /> <xsd:complexType name="TCU_U10.TEST_CONFIGURATION.CONTENT"> <xsd:sequence> <xsd:element ref="SPM" minOccurs="0" maxOccurs="1" /> <xsd:element ref="TCC" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="TCU_U10.TEST_CONFIGURATION" type="TCU_U10.TEST_CONFIGURATION.CONTENT" /> </xsd:schema>

Download

TCR/ACK - Automated Equipment Test Code Settings Request (Event U11)

This message is used to request information concerning test codes from one application to another (e.g., Laboratory Automation System to automated equipment).

TCR^U11^TCU_U10: Test Code Settings Request

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - TCU_U10

Segment	Cardinality	Must Implement	Status
TCU_U10
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
TEST_CONFIGURATION	1..*	Yes	additional
SPM	0..1		additional
TCC	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for TCR^U11^TCU_U10

Send Application Ack: TCU^U10^TCU_U10

Enhanced Mode Acknowledgement Choreography for TCR^U11^TCU_U10

When the MSH-15 value of a TCR^U11^TCU_U10 message is AL or ER or SU, an ACK^U11^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a TCR^U11^TCU_U10 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a TCR^U11^TCU_U10 message is AL or ER or SU, a TCU^U10^TCU_U10 message SHALL be sent as an application ack.

When the MSH-16 value of a TCR^U11^TCU_U10 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U11^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: TCU^U10^TCU_U10
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: TCU_U10--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE TCU_U10 --> <!-- .. message definition TCU_U10 --> <xsd:complexType name="TCU_U10.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="TCU_U10.TEST_CONFIGURATION" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="TCU_U10" type="TCU_U10.CONTENT" /> <xsd:complexType name="TCU_U10.TEST_CONFIGURATION.CONTENT"> <xsd:sequence> <xsd:element ref="SPM" minOccurs="0" maxOccurs="1" /> <xsd:element ref="TCC" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="TCU_U10.TEST_CONFIGURATION" type="TCU_U10.TEST_CONFIGURATION.CONTENT" /> </xsd:schema>

Download

LSU/ACK - Automated Equipment Log/Service Update (Event U12)

This message is used to send log and/or service events from one application to another (e.g., automated equipment to Laboratory Automation System).

LSU^U12^LSU_U12: Equipment Log/Service Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - LSU_U12

Segment	Cardinality	Must Implement	Status
LSU_U12
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
EQP	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for LSU^U12^LSU_U12

Send Application Ack: ACK^U12^ACK

Enhanced Mode Acknowledgement Choreography for LSU^U12^LSU_U12

When the MSH-15 value of a LSU^U12^LSU_U12 message is AL or ER or SU, an ACK^U12^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a LSU^U12^LSU_U12 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a LSU^U12^LSU_U12 message is AL or ER or SU, an ACK^U12^ACK message SHALL be sent as an application ack.

When the MSH-16 value of a LSU^U12^LSU_U12 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U12^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: ACK^U12^ACK
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: LSU_U12--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE LSU_U12 --> <!-- .. message definition LSU_U12 --> <xsd:complexType name="LSU_U12.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EQP" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="LSU_U12" type="LSU_U12.CONTENT" /> </xsd:schema>

Download

LSR/ACK - Automated Equipment Log/Service Request (Event U13)

This message is used to request log and/or service events from one application to another (e.g., Laboratory Automation System to automated equipment).

LSR^U13^LSU_U12: Equipment Log/Service Message

• Message Structure
• Acknowlegment Choreography
• v2.xml XSD

HL7 MessageStructure Table - LSU_U12

Segment	Cardinality	Must Implement	Status
LSU_U12
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
EQP	1..*	Yes	additional
ROL	0..1		B

Original Mode Acknowledgement Choreography for LSR^U13^LSU_U12

Send Application Ack: LSU^U12^LSU_U12

Enhanced Mode Acknowledgement Choreography for LSR^U13^LSU_U12

When the MSH-15 value of a LSR^U13^LSU_U12 message is AL or ER or SU, an ACK^U13^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of a LSR^U13^LSU_U12 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of a LSR^U13^LSU_U12 message is AL or ER or SU, a LSU^U12^LSU_U12 message SHALL be sent as an application ack.

When the MSH-16 value of a LSR^U13^LSU_U12 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U13^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: LSU^U12^LSU_U12
	NE, AL, ER, SU	(none)

<?xml version="1.0"?> <!-- v2.xml Message Definitions for Version 2.8.2 - here: LSU_U12--> <!-- Copyright (c) 1999-2019, Health Level Seven. All rights reserved. --> <!-- (generated on 09.01.2019 by HL7-Database) D:\Eigene Dateien\HL7\Datenbank\hl7_94.mdb--> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:hl7-org:v2xml" xmlns:hl7="urn:hl7-org:v2xml" targetNamespace="urn:hl7-org:v2xml" version="1.1"> <!-- import segment definition for version --> <xsd:include schemaLocation="segments.xsd" /> <!-- MESSAGE LSU_U12 --> <!-- .. message definition LSU_U12 --> <xsd:complexType name="LSU_U12.CONTENT"> <xsd:sequence> <xsd:element ref="MSH" minOccurs="1" maxOccurs="1" /> <xsd:element ref="SFT" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UAC" minOccurs="0" maxOccurs="1" /> <xsd:element ref="EQU" minOccurs="1" maxOccurs="1" /> <xsd:element ref="EQP" minOccurs="1" maxOccurs="unbounded" /> </xsd:sequence> </xsd:complexType> <xsd:element name="LSU_U12" type="LSU_U12.CONTENT" /> </xsd:schema>

Download

INR/ACK – Automated Equipment Inventory Request (Event U14)

This message is used to request information about inventory items from one application to another (e.g., Laboratory Automation System to automated equipment). The equipment specified in the EQU segment should respond with the information about inventory item requested in the INV segment (or all items).

Compared to INR^U06, it declares INV as optional and does not require fields INV-1 and INV-2 there. In that way, it supports queries for all inventory items without filtering on any attributes.

INR^U14^INR_U14: Inventory Request Message

• Message Structure
• Acknowlegment Choreography

HL7 MessageStructure Table - INR_U14

Segment	Cardinality	Must Implement	Status
INR_U14
MSH	1..1	Yes	additional
SFT	0..*		additional
UAC	0..1		additional
EQU	1..1	Yes	additional
INV	0..*		additional

Original Mode Acknowledgement Choreography for INR^U14^INR_U14

Send Application Ack: INU^U05^INU_U05

Enhanced Mode Acknowledgement Choreography for INR^U14^INR_U14

When the MSH-15 value of an INR^U14^INR_U14 message is AL or ER or SU, an ACK^U14^ACK message SHALL be sent as an immediate ack.

When the MSH-15 value of an INR^U14^INR_U14 message is NE or AL or ER or SU, an immediate ack SHALL NOT be sent.

When the MSH-16 value of an INR^U14^INR_U14 message is AL or ER or SU, an INU^U05^INU_U05 message SHALL be sent as an application ack.

When the MSH-16 value of an INR^U14^INR_U14 message is NE or AL or ER or SU, an application ack SHALL NOT be sent.

Field	Value	Send Response
MSH-15	AL, ER, SU	immediate ack: ACK^U14^ACK
	NE, AL, ER, SU	(none)
MSH-16	AL, ER, SU	application ack: INU^U05^INU_U05
	NE, AL, ER, SU	(none)

Other Required Original HL7 Messages

The transaction for synchronization of system clocks must be supported by all equipment as receiver. The master (sender) of the time is either the LAS computer or the LIS.

Transfer of Laboratory Test Orders and Results

For the transfer of laboratory automation orders and results refer to 4.2.6 OML - laboratory order message (event O21) instead of ORM and 7.2.2 ORL – unsolicited laboratory observation message (event O20) instead of ORU.

Transfer of QC Results

Use SPM-11 Specimen Role, or SAC-6 Specimen Source, or the 7th component of OBR-15 Specimen Source or SAC-6 Specimen Source to indicate that this is a control specimen. Use SAC-3 Container Identifier for the identification of a control specimen container. The SID segment appended to this SAC segment specifies the manufacturer, lot identifiers, etc. for the control specimen.

The identification of the instrument performing the QC measurement, should be transferred with the OBX-18 Equipment Instance Identifier), the measurement data/time with the OBX-19 Date/Time of the Analysis.

Query for Order Information – Triggers for Download of Test Orders

There is no specific query for laboratory order information. Instead, the order information should be downloaded to the LAS either unsolicited (based on LIS internal triggers such as Sample Collected or Order Entered) or after an implicit trigger such as Sample Status Update – sample identified by the LAS.

Transfer of Additional Information for Automated Processing

Instruments requiring additional information for performing of automated processing based on automatic validation, such as Expected Date of Birth (Delivery Date), Menstrual Status, History of Medication Use, should consider using OBX segments and LOINC codes. For example, the LOINC code for Delivery Date is 11778-8, Menstrual status is 8678-5, History of Medication Use is 10160-0.

Working With Non-Substance Inventory Items

Automated Equipment Status Update

The chemistry analyzer 0001 was powered up directly by the operator (local control) and correctly performed the initialization process. This information is sent by the analyzer to the LAS.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |ESU^U01^ESU|MSG00001|P|2.8|

EQU|0001^CHEMISTRYANALYZER|19980630080038|PU^POWERED_UP|L^LOCAL|N^NORMAL

ISD|123456789|IN^INIT|OK

Automated Equipment Status Request

The LAS queries the chemistry analyzer 0001 for status information.

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |ESR^U02^ESR|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

Specimen Status Update

The chemistry analyzer 0001 recognized an aliquot container (id=092321A) with blood. This container is in a position 1 of carrier type R5 (id=120) and is located in the input buffer 1.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |SSU^U03^SSU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

SAC|991912376^EXTLAB|01039421^THISLAB|092321A^LAS|092321^LAS||BLD^BLOOD |19980620080037|I^IDENTIFIED|R5^5_HOLE_RACK|120|1||||BUF1^INPUT BUFFER 1

A pre-analytical instrument 0001 performed aliquoting and sorting operation. (See Fig. 13-5 for visualization of positions and locations)The carrier (id=2002) with primary/parent container (id=12345) at position 2 was transported in the location: output buffer 1, into position 4 of the output tray (id=A1203). The aliquot container (id=12345A) was sorted into the manual transportable carrier (id=045), in row 3, column 2. This carrier is located in the sorter bed at location 4.

MSH|^~VALUEamp;|PREANPROG|AUTPREAN|LASPROG|LASSYS|19980630080040|SECURITY |SSU^U03^SSU|MSG00002|P|2.9|

EQU|0001^AQS|19980630080043

SAC|991912376^EXTLAB|01039421^THISLAB|12345^LAS||||19980620080039|R^COMPLETED |R3^3_HOLE_RACK|2002|1|OT^OUTPUTTRAY|A1203^AQSTRAY|4|OB1^OUTPUTBUFFER

SAC|991912376^EXTLAB|01039421^THISLAB|12345A^LAS|12345^LAS|||19980620080039 |R^COMPLETED|R14^14_HOLE_RACK|045|3^2||||AQSBED||||||2|0.5||ml

Specimen Status Request

The chemistry analyzer 0001 queries the LAS for status of specimen/container (id=092321A).

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |SSR^U04^SSR|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

SAC|991912376^EXTLAB|01039421^THISLAB|092321A^LAS||||199806200823

Automated Equipment Inventory Update

The chemistry analyzer 0001 sends to the LAS the status of a TSH reagent (id=MF01239) in bottle (id=12345).

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |INU^U05^INU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

INV|MF01239^REAGENT1|OK^OK_STATUS|SR^SINGLE_TEST_REAGENT |12345^BOTTLE_NUM|||||190||ML|20000101||^^D60|TSH|A12345678|PROD1

Automated Equipment Inventory Request

The LAS queries the chemistry analyzer 0001 for status of all packages of the substance (id=MF01239).

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |INR^U06^INR|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

INV|MF01239^REAGENT1|OK^OK_STATUS

Automated Equipment Command

The LAS sends command of "Clearing Notification" to the chemistry analyzer 0001.

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |EAC^U07^EAC|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

ECD|89421|CN^CLEAR NOTIFICATION|Y^YES

CNS|1209|1500|199806010800|199806300800

Automated Equipment Response

The chemistry analyzer confirms completion of the execution of the initialization command.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |EAR^U08^EAR|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

ECD|89421|IN^INIT|Y^YES

ECR|OK^COMMAND_COMPLETE|19980630080035

Automated Equipment Notification

The chemistry analyzer sends a notification (warning) about drift in the detection unit.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |EAN^U09^EAN|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

NDS|8923|199806300800|W^WARNING^|DU001^DETECTIO UNIT DRIFT

Automated Equipment Test Code Settings Update

The LAS send update of configuration parameters for Glucose test.

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |TCU^U10^TCU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

TCC|15074-8^GLUCOSE|GLU-HK^CHEMISTRYANALYZER|SER^SERUM|10|10|0|0|500| Y^YES|Y^YES|N^NO |^2^-^400|mg/dL|P

Automated Equipment Test Code Settings Request

The chemistry analyzer 0001 queries the LAS for configuration parameters of the Glucose test.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |TCR^U11^TCU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

TCC|15074-8^GLUCOSE|GLU-HK^CHEMISTRYANALYZER

Automated Equipment Log/Service Update

The chemistry analyzer 0001 sends 1 record from the event log to the LAS.

MSH|^~VALUEamp;|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |LSU^U12^LSU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

EQP|LOG^LOG_EVENT||199806300755|199806300800|I976 Instrument Initialization

Automated Equipment Log/Service Request

The LAS queries chemistry analyzer for log file of events occurring between 7am and 8am on 30th June 1998.

MSH|^~VALUEamp;|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |LSR^U13^LSU|MSG00001|P|2.9|

EQU|0001^CHEMISTRYANALYZER|19980630080038

EQP|LOG^LOG_EVENT||199806300700|199806300800