Difference between revisions of "Inter Laboratory Workflow"
| Line 44: | Line 44: | ||
'''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:] | '''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:] | ||
| − | :* [http://www.ihe.net/Technical_Framework/upload/IHE_LAB_TF_Supplement_Inter-Laboratory-Workflow_ILW_TI_2009-07-16.pdf ILW supplement] | + | :* [http://www.ihe.net/Technical_Framework/upload/IHE_LAB_TF_Supplement_Inter-Laboratory-Workflow_ILW_TI_2009-07-16.pdf ILW supplement] |
| − | |||
==See Also== | ==See Also== | ||
Revision as of 05:50, 17 December 2009
Inter Laboratory Workflow (ILW) supports the workflow of orders and results of in vitro diagnostic tests between a requesting laboratory and a subcontracting laboratory.
Summary
The Inter-Laboratory Workflow Profile covers the workflow of orders and results beween a requesting lab providing the specimens and the orders and a subcontracting lab performing the tests and reporting the results to the former one. This workflow is able to carry the payors information along with the order (patient insurances, guarantor, ...). The structured results may be accompanied by a pdf copy of the performing lab report.
Benefits
Improves Throughput in Care Process
Details
The Inter-Laboratory Workflow (ITW) Integration Profile is bound to in vitro diagnostic testing. The specimen is always provided by the requesting lab. The subcontracting lab does not see the patient. This profile supports all laboratory specialties but anatomic pathology.
Use cases:
The ILW Integration Profile covers three major use cases:
- Cooperation between a hospital and a specialized private laboratory
- Specific tests subcontracted to a national reference laboratory
- Distributed process in a cooperative group of laboratories
Transactions:
ILW Integration Profile defines 2 Transactions: LAB-35 "Sub-order management" and LAB-36 "Sub-order results delivery". Both transactions are based on HL7 release 2.5.1 messaging standard. LAB-35 is implementing an OML/ORL message pair. LAB-36 is implementing an ORU/ACK message pair.
Systems Affected
Systems involved in this profile are the laboratory informations systems (LIS) of the requesting lab and the subcontracting lab, messaging with one another.
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents: IHE Laboratory Technical Framework:
See Also
Related Profiles
- Integration Profiles LTW depends on
- Patient Administration Management (PAM) and/or Patient Demographics Query (PDQ) provide accurate patient demographics used by LTW: 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.
- Audit_Trail_and_Node_Authentication (ATNA) to audit creation and access to patient data during LTW. An application implementing one of the Actors Order Placer, Order Result Tracker, Order Filler shall also implement the Actor Secure Node from ATNA.
- Consistent_Time (CT) to ensure timestamps in LTW data and audit messages are accurate.
- 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_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