Sharing Laboratory Reports

From IHE Wiki
Jump to navigation Jump to search

Sharing Laboratory Reports (XD-LAB) describes the laboratory report as an electronic content to be shared among a community of healthcare settings and care providers relying on a document sharing infrastructure.



Summary

This Content Integration Profile describes a clinical laboratory report as an electronic document to be published towards a document sharing resource such as an Electronic Health Record (EHR) or in Personal Health Record (PHR) shared by a community of care providers, using one of the document sharing profiles defined in ITI-TF. Such an electronic document contains the set of releasable results produced by a clinical laboratory in fulfillment of one or more test Orders for a patient. The report is shared in a human-readable format. In addition, this electronic laboratory report SHALL contain test results in a machine-readable format, to facilitate the integration of these observations in the database of a consumer system.
The scope of this profile covers all laboratory specialties except anatomic pathology.
This profile leverages IT Infrastructure profiles [ATNA] and [CT] for security, and [XDS], [XDM], [XDR] for document sharing.
This profile leverages the Clinical Document Architecture Release 2 (CDAr2) from [HL7]

Ihe lab xd-lab ip.jpg


Benefits

Reduces Errors and Enhance Patient Care

  • Prevents manual data entry errors by ensuring that each piece of information is entered only once, by the person closest to the source of this information, and from there, made available in due time to any system who needs it.
  • Reduce over-ordering and over blood sampling from the patient by letting the current lab orders and their results follow the movements of the patient from a ward to another.
  • Avoids lost specimens by tracking specimen collection in ward or in sample collection room, and specimen acceptance in laboratory.
  • Accelerate the delivery of laboratory results to the ward staff, especially in emergency situations where a clinical decision is conditioned by some test results.

Improves Throughput in Care Process

  • Suppresses manual order entry time on the laboratory side since the order is placed directly by the clinical system operated in the ward to the laboratory information system.
  • Stremalines sample collection and transportation process, delivering a unique identifier to each specimen collected, tightly coupled with the identifiers of the orders requesting this specimen to be performed.
  • Saves telephone calls between ward and laboratory since urgent results are delivered immediately and all status changes of any current order are reported in real time to the ordering system.
  • Reduces the amount of paper reports since all lab results are consolidated in a global system that shares them with the authorized caregivers in the wards.

Favors independence of healthcare institution from their clinical and ancillary systems

  • By providing clear specifications of interfaces between Clinical Information Systems (CIS), Laboratory Information Systems (LIS) and Laboratory Automation Systems (LAS), enables to replace one of these systems in a department or unit without breaking the existing data workflows involving this department or unit.

Details

The Laboratory Testing Workflow (LTW) Integration Profile establishes the continuity and integrity of diagnostic test orders placed towards clinical laboratories for a patient, and of the results produced for these orders, inside the healthcare institution.
This Integration Profile is bound to in vitro diagnostic testing (tests performed on in vitro specimen). It supports all laboratory specialties but anatomic pathology.
The LTW Integration Profile covers three major use cases:

  • Order placed with specimens collected and identified by the orderer
  • Order placed with specimens collected by a third party, then identified and labeled by the laboratory information system
  • Order generated by the laboratory and notified to the ordering system to obtain an order number.

LTW Integration Profile defines 5 Transactions, all of which based on HL7 release 2.5 or 2.5.1 messaging standard. Each transaction selects a subset of HL7 message structures (based on OML, ORL, ORU 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:

  • One or more Clinical Information Systems (CIS). Each of these systems is operated by a clinical facility and provides a number of features such as order entry, order placing, placer order management and follow-up, order result tracking, management of patient biologic history, specimen calculation, specimen identification... A CIS usually implements the Actors Order Placer and Order Result Tracker.
  • One or more Laboratory Information Systems (LIS). Each of these systems is operated by a number of clinical laboratories inside the institution. The LIS offers features such as order reception, specimen calculation, specimen identification or specimen acceptance, order check, scheduling, filler order management, production of worklists, result manual entry for non connected-tests, clinical validation and interpretation of results, result reporting. Each LIS implements an Order Filler Actor.
  • One or more Laboratory Automation Systems (LAS) operated in each laboratory. A LAS manages a set of automated laboratory devices (pre-analytical devices, analyzers, post-analytical devices). The LAS receives Work Orders related to a specimen and processes the various steps of a WSork Order on its set of devices, to eventually get the test results, perform the technical validation thereof, and upload them back to the LIS.

A laboratory request ordered by a physician for a patient is frequently composed of multiple tests and panels placed to a laboratory. Such a laboratory request containing several orders is called an Order Group in the HL7 standard, and uniquely identified by the ordering CIS with a Placer Group Number. Each of the orders is in turn uniquely identified by the CIS with a Placer Order Number. Each order accepted by the laboratory as well as each reflex order generated by the laboratory is uniquely identified by the LIS with a Filler Order Number.

Actors & Transactions:

Ltw-actor-transaction.JPG
Other requirements for systems implementing LTW (dependencies towards IT Infrastructure Profiles):

  • An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actors Patient Demographics Consumer and Patient Encounter Consumer from either PAM or PDQ Profile or both.
  • An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actor Secure Node from the ATNA Profile, as well as the Actor Time Client from the CT Profile.

Specification

Profile Status: Trial Implementation

Documents:

Underlying Standards:

See Also

Related Profiles

  • Integration Profiles LTW depends on
  • Integration Profiles depending upon LTW
  • Laboratory_Device_Automation (LDA) from the Laboratory Technical Framework: The Actor Automation Manager from the LDA Profile must also be an Automation Manager in the LTW Profile.
  • Laboratory_Point_Of_Care_Testing (LPOCT) from the Laboratory Technical Framework: The Actor Order Filler from the Laboratory LPOCT Profile must also be an Order Filler in the LTW Profile.
  • Laboratory_Specimen_Barcode_Labeling (LBL) from the Laboratory Technical Framework: The Label Information Provider Actor of the LBL profile shall be grouped with either the Order Filler or the Order Placer from the LTW profile..

Consumer Information

This page is based on the Profile Template