Laboratory Barcode Labeling: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Fmacary (talk | contribs)
Fmacary (talk | contribs)
Line 28: Line 28:
* LAB-61 Label Delivery Request (push mode)
* LAB-61 Label Delivery Request (push mode)
* LAB-62 Query for Label Delivery Instructions (pull mode)
* LAB-62 Query for Label Delivery Instructions (pull mode)
* <br/>
<br/>


==Systems Affected==
==Systems Affected==

Revision as of 08:37, 28 March 2008

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 Specimen Barcode Labeling (LBL) Integration Profile covers 5 use cases:

  • Specimen container identification and delivery process driven by the clinical ordering system (HIS/CIS/EMR), in push mode.
  • Specimen container identification and delivery process driven by the laboratory information system (LIS), in push mode.
  • Specimen container identification and delivery process driven by HIS/CIS/EMR, from specimen data provided by LIS, in push mode.
  • Specimen container identification and delivery process driven by HIS/CIS/EMR, in pull mode.
  • Specimen container identification and delivery process driven by LIS, in pull mode.

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

  • LAB-61 Label Delivery Request (push mode)
  • LAB-62 Query for Label Delivery Instructions (pull mode)


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:

Underlying Standards:

See Also

Related Profiles

  • Integration Profiles LDA depends on


Consumer Information

This page is based on the Profile Template