Laboratory Barcode Labeling

Laboratory Specimen Barcode Labeling(LBL) Integration Profile supports the robotization of specimen container identification and delivery at blood sample collection time, in the context of laboratory test requests.

Summary

The Laboratory Specimen Barcode Labeling(LBL) Integration Profile supports this workflow: A robotic system delivers specimen containers pre-identified with a bar coded label, for the specimen collection related to a laboratory test request. This robotic system receives patient, test order and specimen data from another system (HIS, CIS or LIS depending upon the organization), and issues a label for each specimen container needed, with the specimen identifier bar coded on the label, and possibly other information printed out on this label.
The robotic system is operated in the blood sample collection room. Some healthcare institutions have a central specimen collection room shared by a number of clinical wards. Other institution decentralize the blood sampling process in each clinical ward. This LBL profile supports both kinds of organizations.

Benefits

Improves integrity and efficiency of in vitro diagnostic testing in healthcare institutions

• Identifies the specimen container at blood sample collection time, with an identifier tightly coupled to the laboratory request this specimen is for, and to the patient subject of the request.
• Robotizes and accelerates blood sample collection process.

Details

The Laboratory Device Automation (LDA) Integration Profile covers six major use cases:

• WOS downloaded on the device before specimen arrival
• Query for the WOS at specimen arrival on the device
• Manual entry of the WOS on the LD
• Rerun on the Analyzer, automatically launched by the analyzer or requested by the LAS at technical validation time.
• Quality Control order downloaded by the LAS
• Quality Control order queried by the device
• Unsolicited QC results sent by the device.

The LDA Integration Profile defines 4 Transactions, all of which based on HL7 release 2.5 or 2.5.1 messaging standard:

• LAB-21 WOS download to automated device
• LAB-22 WOS queried by automated device
• LAB-23 Status change of an analytical WOS, and upload of the results produced
• LAB-26: Stautus change of a pre-analytical or post-analytical WOS

Each of these transaction selects a subset of HL7 message structures (based on OML, ORL and OUL) and specifies a set of constraints applying to each message structure, as well as the responsibilities of the sender and receiver.

Systems Affected

Systems involved in this profile are:

• The Actor Automation Manager can be played either by a Laboratory Automation System (LAS), which is a system dedicated to the work area of the laboratory, or by the Laboratory Information System (LIS), which usually supports the capacity to connect some if not all the automated devices of the work area. In frequent organizations a laboratory may combine a LIS and one or more LAS, each system handling a subset of devices.
• This profile distinguishes two categories of automated devices:

• The pre/pos-analytical devices (centrifuge, robotic specimen conveyer, decapper, robotized specimen storage, aliquoter...
• The analyzer, which performs tests and produces observations related to a specimen.

Actors & Transactions:

Other requirements for systems implementing LDA (dependencies towards the LTW profile):

• An application implementing the Actor Automation Manager shall also implement this Actor in the "Laboratory Testing Workflow" (LTW) profile.

Specification

Profile Status: Trial Implementation

Documents:

• IHE Laboratory Technical Framework:

Underlying Standards:

• HL7

See Also

Related Profiles

• Integration Profiles LDA depends on

• Laboratory Testing Workflow (LTW): The Actor Automation Manager shall also be an Automation Manager in the LTW profile.

Consumer Information

This page is based on the Profile Template