13
|
Co-Chair: |
Hans BuitendijkCerner Corporation |
|
Co-Chair: |
Lorraine Constable Constable Consulting Inc. |
|
Co-Chair: |
|
|
Co-Chair: |
Patrick LoydICode Solutions |
|
Co-Chair: |
Ken McCaslinAccenture Federal |
|
Co-Chair |
JD NolenMercy Children’s Hospital |
|
Co-Chair: |
Riki MerrickVernetzt. LLC |
|
Co-Chair: |
David BurgessLabCorp |
|
Editor |
Riki MerrickVernetzt. LLC |
|
Sponsoring Work Group: |
Orders & Observations |
|
List Server: |
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, 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:
Approved level standards for all five of these areas were published by NCCLS.
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:
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:
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:
The terminology found in ANSI X3.182-1990 shall be used where applicable. Other computer-related technical terms used in this document can be found in ASTM Terminology E 1013, IEEE 100, IEEE 610, and ANSI X3.172.
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.
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.
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.
An instrument and/or specimen processing and handling device that performs measurements on patient specimens of quantitative, clinically relevant analytes.
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.
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;
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.
An array of parallel rectangular bars and spaces that creates a symbology representing a number or alphanumeric identifier.
The length of the bars in the bar code.
See Separator
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.
The farthest point from the top of the container/test tube that the cap reaches.
The portion of the container/test tube farthest from the cap (see Point of reference).
See Bottom of container.
See Specimen carrier.
1) The smallest abstract element of a writing system or script.
2) A code element.
The integration of laboratory personnel and preanalytical, analytical, and postanalytical processes and information 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.
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.
See Closed-container sampling.
See Specimen container.
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.
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.
The removal of a closure from a specimen container.
A symbol used to separate items in a list.
The orthogonal axes.
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.
Figure 13-2. X Direction
Y-direction, n - The horizontal direction perpendicular to specimen travel along a transportation system;
Figure 13-3. Y Direction
Z-direction, n - The vertical dimension;
Figure 13-4. Z Direction
See Directions of the specimen, etc.
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;
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.
The point at which the vertical (straight) walls of the specimen container bend to form the base.
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.
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.
A system of information and hardware technology that allows the operation of the clinical laboratory process without significant operator intervention;
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).
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.
Acronym for Laboratory Equipment Control Interface Specification, (ASTM E 1989-98).
A physical place within the laboratory, with a unique identifier (e.g., refrigerator shelf number, instrument buffer ID, track identifier).
The action of aspirating a sample from a specimen container from which the closure has previously been removed.
See Open-container sampling.
The center distance between two specimen containers in a carrier or between two sequential specimen container carriers.
The intersection of the xy plane and an infinite line in the 'z' direction.
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.
In NCCLS LAB AUTOMATION documents, the white {blank} space on a bar code immediately preceding the first bar and immediately following the last bar.
To replace the closure on a specimen container; either with the original closure or with a new replacement closure.
A device capable of moving a specimen container, specimen carrier, or another object in the X, Y, and Z directions.
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;
See Specimen carrier.
See Specimen collection container.
See Specimen-positioning system.
See Specimen probe.
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.
See Separator.
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.
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.
A device that holds the specimen container.
The tube that holds a patient specimen.
Figure 13-5: Relationship among Specimen Container, Specimen Carrier, Tray, and Locations.
A device to position a specimen container within acceptable tolerances of a POR.
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.
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.
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.
Short, understandable contractions for test names.
The open end of the container/test tube, closest to the cap.
See Top of container.
A holder for one or more carriers (optional). (See Figure 13-5.)
See Directions.
See Directions.
See Directions.
Each trigger event is listed below, along with the application form of the message exchange. The notation used to describe the sequence, optionality and repetition of segments is described in Chapter 2.
The notation used to describe the sequence, the optionality, and the repetition of segments is described in Chapter 2 under "Format for Defining Abstract Message."
All the ACK messages are varieties of the 'general acknowledgement' message defined in Chapter 2, section 2.13.1. The only difference is the event code.
The "Equipment Notification" message (EAN/ACK event U09) is used to send information about the occurrence of an event. An event does not necessarily cause a state transition. The "Status Update" message (EAU/ACK event U01) is used to transfer information about the current status. This status can be the result of one or more events that led to the state transition. Example: The event of a "warning level of a consumable being reached" (e.g., 10% left) does not cause a state transition, because the system can remain "In operation". This results in an EAN/ACK message. An event "container transport jammed" causes the state transition to "Emergency stop". This results in both EAN/ACK and EAU/ACK messages.
For the transfer of laboratory automation orders and results refer to 4.4.6 OML - laboratory order message (event O21) instead of ORM and 7.3.2 OUL - unsolicited laboratory observation message (event O20) instead of ORU.
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."
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^U01^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U01^ACK | - |
| NE | AL, SU, ER | - | ACK^U01^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U01^ACK | ACK^U01^ACK |
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."
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ESU^U01^ESU_U01 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U02^ACK | - |
| NE | AL, SU, ER | - | ESU^U01^ESU_U01 |
| AL, SU, ER | AL, SU, ER | ACK^U02^ACK | ESU^U01^ESU_U01 |
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).
| Segment | Cardinality | Implement | Status |
|---|---|---|---|
 SSU^U03^SSU_U03 | |||
| [1..1] | SHALL | ||
| [0..1] | |||
| [1..1] | SHALL | ||
 SPECIMEN_CONTAINER |
[1..*] | SHALL | |
| [1..1] | SHALL | ||
  SPECIMEN |
|||
| [1..1] | SHALL | ||
| [0..1] | B |
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^U03^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U03^ACK | - |
| NE | AL, SU, ER | - | ACK^U03^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U03^ACK | ACK^U03^ACK |
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."
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | SSU^U03^SSU_U03 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U04^ACK | - |
| NE | AL, SU, ER | - | SSU^U03^SSU_U03 |
| AL, SU, ER | AL, SU, ER | ACK^U04^ACK | SSU^U03^SSU_U03 |
This message is used to send information about inventory items from one application to another (e.g., automated Equipment to a Laboratory Automation System).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^U05^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U05^ACK | - |
| NE | AL, SU, ER | - | ACK^U05^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U05^ACK | ACK^U05^ACK |
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).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | INU^U05^INU_U05 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U06^ACK | - |
| NE | AL, SU, ER | - | INU^U05^INU_U05 |
| AL, SU, ER | AL, SU, ER | ACK^U06^ACK | INU^U05^INU_U05 |
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.
| Segment | Cardinality | Implement | Status |
|---|---|---|---|
| EAC^U07^EAC_U07 | |||
| [1..1] | SHALL | ||
| [0..1] | |||
| [1..1] | SHALL | ||
| COMMAND |
[1..*] | SHALL | |
| [1..1] | SHALL | ||
| [0..1] | |||
| SPECIMEN_CONTAINER |
|||
| [1..1] | SHALL | ||
| ORDER_FOR_SPECIMEN_CONTAINER |
|||
| [0..1] | |||
| [0..1] | B |
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | EAR^U08^EAR_U08 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U07^ACK | - |
| NE | AL, SU, ER | - | EAR^U08^EAR_U08 |
| AL, SU, ER | AL, SU, ER | ACK^U07^ACK | EAR^U08^EAR_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).
| Segment | Cardinality | Implement | Status |
|---|---|---|---|
| EAR^U08^EAR_U08 | |||
| [1..1] | SHALL | ||
| [0..1] | |||
| [1..1] | SHALL | ||
| COMMAND_RESPONSE |
[1..*] | SHALL | |
| [1..1] | SHALL | ||
| SPECIMEN_CONTAINER |
[0..1] | ||
| [1..1] | SHALL | ||
| [1..1] | SHALL | ||
| [0..1] | B |
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^U08^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U08^ACK | - |
| NE | AL, SU, ER | - | ACK^U08^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U08^ACK | ACK^U08^ACK |
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).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | ACK^U09^ACK |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U09^ACK | - |
| NE | AL, SU, ER | - | ACK^U09^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U09^ACK | ACK^U09^ACK |
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").
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | TCU^U10^TCU_U10 |
| Blank | Blank | - | ACK^U10^ACK |
| NE | NE | - | - |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U11^ACK | - |
| AL, SU, ER | NE | ACK^U10^ACK | - |
| NE | AL, SU, ER | - | TCU^U10^TCU_U10 |
| NE | AL, SU, ER | - | ACK^U10^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U11^ACK | TCU^U10^TCU_U10 |
| AL, SU, ER | AL, SU, ER | ACK^U10^ACK | ACK^U10^ACK |
This message is used to request information concerning test codes from one application to another (e.g., Laboratory Automation System to automated equipment).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | TCU^U10^TCU_U10 |
| Blank | Blank | - | ACK^U10^ACK |
| NE | NE | - | - |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U11^ACK | - |
| AL, SU, ER | NE | ACK^U10^ACK | - |
| NE | AL, SU, ER | - | TCU^U10^TCU_U10 |
| NE | AL, SU, ER | - | ACK^U10^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U11^ACK | TCU^U10^TCU_U10 |
| AL, SU, ER | AL, SU, ER | ACK^U10^ACK | ACK^U10^ACK |
This message is used to send log and/or service events from one application to another (e.g., automated equipment to Laboratory Automation System).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | LSU^U12^LSU_U12 |
| Blank | Blank | - | ACK^U12^ACK |
| NE | NE | - | - |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U13^ACK | - |
| AL, SU, ER | NE | ACK^U12^ACK | - |
| NE | AL, SU, ER | - | LSU^U12^LSU_U12 |
| NE | AL, SU, ER | - | ACK^U12^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U13^ACK | LSU^U12^LSU_U12 |
| AL, SU, ER | AL, SU, ER | ACK^U12^ACK | ACK^U12^ACK |
This message is used to request log and/or service events from one application to another (e.g., Laboratory Automation System to automated equipment).
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | LSU^U12^LSU_U12 |
| Blank | Blank | - | ACK^U12^ACK |
| NE | NE | - | - |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U13^ACK | - |
| AL, SU, ER | NE | ACK^U12^ACK | - |
| NE | AL, SU, ER | - | LSU^U12^LSU_U12 |
| NE | AL, SU, ER | - | ACK^U12^ACK |
| AL, SU, ER | AL, SU, ER | ACK^U13^ACK | LSU^U12^LSU_U12 |
| AL, SU, ER | AL, SU, ER | ACK^U12^ACK | ACK^U12^ACK |
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.
| MSH-15 | MSH-16 | Immediate ACK | Application Ack |
|---|---|---|---|
| Blank | Blank | - | INU^U05^INU_U05 |
| NE | NE | - | - |
| AL, SU, ER | NE | ACK^U14^ACK | - |
| NE | AL, SU, ER | - | INU^U05^INU_U05 |
| AL, SU, ER | AL, SU, ER | ACK^U14^ACK | INU^U05^INU_U05 |
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.
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.
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.
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.
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.
This section provides examples of INV segments related to reporting and querying values of equipment state indicators (special non-material inventory items).
Example 1: Reporting that all tests are available (in INU^U05):
INV|NONE^^HL70451|OK^^HL70383|||||||||||||||||||TA^^HL70942
Example 2: Reporting that tests with LOINC codes 1492-8 and 1496-8 are available (in INU^U05):
INV|NONE^^HL70451|OK^^HL70383|||||||||||||1492-8^^LN~1496-8^^LN||||||TA^^HL70942
Example 3: Reporting that the current instrument processing capacity is 42 % (in INU^U05):
INV|NONE^^HL70451|OK^^HL70383|||||||||||||||||||IC^^HL70942|42^%&&UCUM
Example 4: Reporting that an output specimen buffer “Buffer1” is full (in INU^U05):
INV|BufferId1^^HL70451|OK^^HL70383|||||||||||||||||||OB^^HL70942|100^%&&UCUM
Example 5: Reporting that an emergency input specimen buffer “Buffer2” is empty (in INU^U05):
INV|BufferId2^^HL70451|OK^^HL70383|||||||||||||||||||EB^^HL70942|0^%&&UCUM
Example 6: Querying the current instrument processing capacity (in INR^U14):
INV|||||||||||||||||||||IC^^HL70942
Example 7: Querying the current capacity of all regular specimen input buffers (in INR^U14):
INV|||||||||||||||||||||IB^^HL70942
Example 8: Querying the current capacity of the regular specimen input buffer “Buffer3” (in INR^U14):
INV|Buffer3^^HL70451||||||||||||||||||||IB^^HL70942
This sub-chapter contains examples to messages defined in the chapter 13. Examples for other messages using segments defined in the chapter 13 are published in corresponding chapters, e.g., for laboratory orders in chapter 4 and for laboratory observations in chapter 7.
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|^~\&|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
The LAS queries the chemistry analyzer 0001 for status information.
MSH|^~\&|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |ESR^U02^ESR|MSG00001|P|2.9|
EQU|0001^CHEMISTRYANALYZER|19980630080038
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|^~\&|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|^~\&|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
The chemistry analyzer 0001 queries the LAS for status of specimen/container (id=092321A).
MSH|^~\&|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
The chemistry analyzer 0001 sends to the LAS the status of a TSH reagent (id=MF01239) in bottle (id=12345).
MSH|^~\&|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
The LAS queries the chemistry analyzer 0001 for status of all packages of the substance (id=MF01239).
MSH|^~\&|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |INR^U06^INR|MSG00001|P|2.9|
EQU|0001^CHEMISTRYANALYZER|19980630080038
INV|MF01239^REAGENT1|OK^OK_STATUS
The LAS sends command of "Clearing Notification" to the chemistry analyzer 0001.
MSH|^~\&|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
The chemistry analyzer confirms completion of the execution of the initialization command.
MSH|^~\&|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
The chemistry analyzer sends a notification (warning) about drift in the detection unit.
MSH|^~\&|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
The LAS send update of configuration parameters for Glucose test.
MSH|^~\&|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
The chemistry analyzer 0001 queries the LAS for configuration parameters of the Glucose test.
MSH|^~\&|INSTPROG|AUTINST|LASPROG|LASSYS|19980630080040|SECURITY |TCR^U11^TCU|MSG00001|P|2.9|
EQU|0001^CHEMISTRYANALYZER|19980630080038
TCC|15074-8^GLUCOSE|GLU-HK^CHEMISTRYANALYZER
The chemistry analyzer 0001 sends 1 record from the event log to the LAS.
MSH|^~\&|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
The LAS queries chemistry analyzer for log file of events occurring between 7am and 8am on 30th June 1998.
MSH|^~\&|LASPROG|LASSYS|INSTPROG|AUTINST|19980630080040|SECURITY |LSR^U13^LSU|MSG00001|P|2.9|
EQU|0001^CHEMISTRYANALYZER|19980630080038
EQP|LOG^LOG_EVENT||199806300700|199806300800
The element definition for TCC-15 Test Criticality in section 13.4.9.15 proposes an ambigous use of the CWE data type in. Currently the element definition indicates that a CWE data type is used; however, the definition also advises that the element can be populated with "a sequential number of the test sorted according to the criticality assigned by the lab". In general practice, the CWE data type references a table of assigned values, recognizing that those values are often assigned by the user. It is expected that the definition for this element will be reviewed and revised with the next release.
The Demo site for our new HL7 Version 2+ (plus) Standard
