Difference between revisions of "Sharing Laboratory Reports"

Latest revision as of 09:45, 14 April 2020

This profile is part of the Pathology and Laboratory Medicine (PaLM) domain, which merged the former AP and LAB domains since 2016, January 4th.

Sharing Laboratory Reports (XD-LAB) addresses the sharing of laboratory reports among a community of healthcare settings and care providers.

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 a 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 both human-readable and importable in the consumer systems so as to consolidate their patient medical records.
The scope of this profile covers all laboratory specialties except anatomic pathology.

Benefits

Facilitates Patient Care Coordination

Enables the caregiver to obtain at once the laboratory reports produced during previous episodes of care, which enhances continuity of care.
Reduces over-ordering and over blood sampling from the patient by sharing the last laboratory reports among the various physicians attending the patient.
Enables the physician to consolidate their patient biological history by importing into their EHR the structured and coded data embedded in the electronic laboratory report.
Allows a public health laboratory to share broadly its reports related to a suspected outbreak

Details

The Sharing Laboratory Reports (XD-LAB) Integration Profile provides an electronic format for the laboratory report, to make this report:

human-readable: displayed on screen or printed out, with a proper and clear layout and presentation.
machine-readable: Each observation displayed in the report is also represented in the document as a set of structured and coded data that can be imported in the database of any consumer of the document.

This double capacity is achieved by leverageing the [Clinical Document Architecture Release 2] (CDAr2) standard from [HL7]
The XD-LAB Integration Profile covers six major use cases:

At discharge time, a hospital physician publishing a summary laboratory report with the most significant results obtained during the patient stay.
The bio-medical scientist of a private laboratory publishes a report for a patient into the regional Patient Health Record.
An ambulatory physician shares a laboratory report obtained from a laboratory.
A private or public laboratory publishes automatically all its reports in a shared document repository.
A healthcare institution produces a cumulative report of all laboratory tests performed for the patient during the encounter.
A public health laboratory shares its reports into a regional repository.

The standard CDAr2 leveraged by XD-LAB enables to share reports embedding images and charts, which are faithfully rendered by a web browser supporting RFC 2397:

Systems Affected

Systems involved in this profile are:

A system owning a laboratory report and willing to publish it into a document sharing infrastructure. Depending upon the use cases, this can be the system of a clinical laboratory (LIS), the EHR of an ambulatory physician, the EMR of a care setting, the system of a public health laboratory. Each of these systems can play the role of Content Creator.
The system operated by a professional caregiver who wants to view a laboratory report, and may want to import its structured and coded results into its own database. This system plays the role of Content Consumer.

Actors & Transactions:

Specification

Profile Status: Final Text

Documents: IHE Laboratory Technical Framework:

Vol. 1 - XD-LAB profile overview
Vol. 3 - Content

Computable specification:

XD-LAB specified in Art-Decor on ihe-europe.net - templates and value sets

Underlying Standards:

@@ Line 1: / Line 1: @@
-''' 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.
+{| style="color: blue;"
+| '''This profile is part of the Pathology and Laboratory Medicine (PaLM) domain, which merged the former AP and LAB domains since 2016, January 4th.'''
+|}
+''' Sharing Laboratory Reports (XD-LAB)''' addresses the sharing of laboratory reports  among a community of healthcare settings and care providers.
@@ Line 7: / Line 10: @@
 ==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. <br/>
+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 a 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. <br/>
+The report is both human-readable and importable in the consumer systems so as to consolidate their patient medical records. <br/>
 The scope of this profile covers all laboratory specialties except anatomic pathology. <br/>
-This profile leverages IT Infrastructure profiles [ATNA] and [CT] for security, and [XDS], [XDM], [XDR] for document sharing.<br/>
-This profile leverages the [Clinical Document Architecture Release 2] (CDAr2) standard from [[http://www.hl7.org HL7]]
 <center>[[Image:ihe_lab_xd-lab_ip.jpg]]</center>
@@ Line 18: / Line 22: @@
 '''Facilitates Patient Care Coordination'''
-* Enables the caregiver to obtain at once the laboratory reports produced during previous episodes of care.
+* Enables the caregiver to obtain at once the laboratory reports produced during previous episodes of care, which enhances continuity of care.
-* Reduce over-ordering and over blood sampling from the patient by sharing the last laboratory reports among the various physicians attending the patient.
+* Reduces over-ordering and over blood sampling from the patient by sharing the last laboratory reports among the various physicians attending the patient.
 * Enables the physician to consolidate their patient biological history by importing into their EHR the structured and coded data embedded in the electronic laboratory report.
+* Allows a public health laboratory to share broadly its reports related to a suspected outbreak
 ==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.<br/>
+The '''''Sharing Laboratory Reports (XD-LAB) Integration Profile''''' provides an electronic format for the laboratory report, to make this report:
-This Integration Profile is bound to in vitro diagnostic testing (tests performed on in vitro specimen). It supports all laboratory specialties but anatomic pathology.<br/>
+* human-readable: displayed on screen or printed out, with a proper and clear layout and presentation.
-The LTW Integration Profile covers three major use cases:
+* machine-readable: Each observation displayed in the report is also represented in the document as a set of structured and coded data that can be imported in the database of any consumer of the document.<br/>
-* Order placed with specimens collected and identified by the orderer
+This double capacity is achieved by leverageing the [Clinical Document Architecture Release 2] (CDAr2) standard from [[http://www.hl7.org HL7]]<br/>
-* Order placed with specimens collected by a third party, then identified and labeled by the laboratory information system
+The XD-LAB Integration Profile covers six major use cases:
-* Order generated by the laboratory and notified to the ordering system to obtain an order number.
+* At discharge time, a hospital physician publishing a summary laboratory report with the most significant results obtained during the patient stay.
-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.<br/>
+* The bio-medical scientist of a private laboratory publishes a report for a patient into the regional Patient Health Record.
+* An ambulatory physician shares a laboratory report obtained from a laboratory.
+* A private or public laboratory publishes automatically all its reports in a shared document repository.
+* A healthcare institution produces a cumulative report of all laboratory tests performed for the patient during the encounter.
+* A public health laboratory shares its reports into a regional repository.
+<br/>
+The standard CDAr2 leveraged by XD-LAB enables to share reports embedding images and charts, which are faithfully rendered by a web browser supporting RFC 2397:<br/>
+<center>[[Image:ihe_lab_xd-lab_example.jpg]]</center>
+<br/>
 ==Systems Affected==
@@ Line 36: / Line 50: @@
 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.
+* A system owning a laboratory report and willing to publish it into a document sharing infrastructure. Depending upon the use cases, this can be the system of a clinical laboratory (LIS), the EHR of an ambulatory physician, the EMR of a care setting, the system of a public health laboratory. Each of these systems can play the role of Content Creator.
-* 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.
+* The system operated by a professional caregiver who wants to view a laboratory report, and may want to import its structured and coded results into its own database. This system plays the role of Content Consumer.
-* 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.<br/>
-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'''.<br/>
 '''Actors & Transactions:'''
-[[Image:ltw-actor-transaction.JPG]]
+<center>[[Image:xd-lab_actor_transaction.JPG]]</center>
 <br/>
-'''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:''' [[Comments| Trial Implementation]]
+'''Profile Status:''' [[Comments| Final Text]]
+'''Documents:''' [https://www.ihe.net/resources/technical_frameworks/#PaLM IHE Laboratory Technical Framework:]
+:* [https://www.ihe.net/uploadedFiles/Documents/PaLM/IHE_PaLM_TF_Vol1.pdf Vol. 1] - XD-LAB profile overview
+:* [https://www.ihe.net/uploadedFiles/Documents/PaLM/IHE_PaLM_TF_Vol3.pdf Vol. 3] - Content
+'''Computable specification:'''
+:* [https://art-decor.ihe-europe.net/art-decor/decor-project--XDLAB- XD-LAB specified in Art-Decor on ihe-europe.net] - templates and value sets
-'''Documents:'''
-:* [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:]
 '''Underlying Standards:'''
-:* [http://www.hl7.org HL7]
+:* [http://www.hl7.org HL7 CDA Release 2]
+:* [http://www.regenstrief.org/medinformatics/loinc LOINC (Logical Observation Identifiers Names and Codes)]
+:* [http://unitsofmeasure.org/trac The Unified Code for Units of Measure (UCUM)]
+:* RFC 2397
 ==See Also==
@@ Line 62: / Line 79: @@
 '''Related Profiles'''
-* '''Integration Profiles LTW depends on'''
+* '''Integration Profiles XD-LAB depends on'''
-:* [[Patient_Administration_Management]] (PAM) or [[Patient_Demographics_Query]] (PDQ) from ITI Technical Framework: The Actors Order Placer, Order Filler, Order Result Tracker shall be grouped with Actors from PAM or PDQ or both.
+:* [[Cross Enterprise Document Sharing]] (XDS) or [[Cross_Enterprise_Document_Media_Interchange]] (XDM) or [[Cross_Enterprise_Document_Reliable_Interchange]] (XDR) from the ITI Technical Framework. Each of these three profiles provides an infrastructure for the sharing of medical documents between the creators and the consumers.
-:* [[Audit_Trail_and_Node_Authentication]] (ATNA) and [[Consistent_Time]] (CT) from ITI Technical Framework: The Actors Order Placer, Order Filler, Order Result Tracker shall be grouped with the Actors "Secure Node" from ATNA and "Time Client" from ATNA.
+:* [[Audit Trail and Node Authentication]] (ATNA) from the ITI Technical Framework, to authenticate and audit the document-sharing transactions: Document storage and registration, document query and retrieval.
-* '''Integration Profiles depending upon LTW'''
+:* [[Consistent Time]] (CT) from the ITI Technical Framework, to ensure accuracy of the time stamps in the shared documents and in the associated metadata.
-:* [[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'''
@@ Line 75: / Line 90: @@
 [[Category:Profiles]]
+[[Category:PaLM Profile]]
+[[Category:DocShare]]
+[[Category:CDA]]

Difference between revisions of "Sharing Laboratory Reports"

Latest revision as of 09:45, 14 April 2020

Contents

Summary

Benefits

Details

Systems Affected

Specification

See Also

Navigation menu

Search