Difference between revisions of "Laboratory Point Of Care Testing"

From IHE Wiki
Jump to navigation Jump to search
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''Laboratory Point Of Care Testing LPOCT)''' covers in vitro diagnostic tests performed on the point of care in a healthcare institution.
+
{| 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.'''
 +
|}
 +
'''Laboratory Point Of Care Testing (LPOCT)''' covers diagnostic tests performed at the point of care in a healthcare institution.
  
  
Line 7: Line 10:
 
==Summary==
 
==Summary==
  
The Laboratory Point Of Care Testing Profile covers the workflow related to in vitro diagnostic tests performed on the point of care or on patient bedside by caregivers in the clinical wards of the healthcare institution, this process being supervised by a laboratory of the institution. This supervision includes clinical validation of POC results, Quality Control (QC) surveillance, point of care devices surveillance, reagent delivery, and education on good testing practices delivered to the ward staff. The point of care testing devices operated by physicians and nurses are connected to and controlled by a central Point Of Care Data Manager. This POC Data Manager is connected to the LIS of the laboratory.
+
The Laboratory Point Of Care Testing Profile supports the workflow related to in vitro diagnostic tests performed on the point of care or on patient bedside by caregivers in the clinical wards of the healthcare institution, this process being supervised by a laboratory of the institution. This supervision includes clinical validation of POC results, Quality Control (QC) surveillance, point of care devices surveillance, reagent delivery, and education on good testing practices delivered to the ward staff. <br/>
 +
The point of care testing devices operated by physicians and nurses are connected to and controlled by a central Point Of Care Data Manager. This POC Data Manager is connected to the LIS of the laboratory for consolidation of the point of care testing results, and to the HIS of the institution, which provides up to date patient data.
 
<br/>
 
<br/>
The main value proposition of this profile is the securization of the workflow by a real-time patient identity checking and the consolidation of point of care orders and their observations in the enterprise-wide repository of orders and observations.
+
The main characteristics of point of care testing are:
 +
* Specimen drawn from the patient by the caregiver, tested immediately, and then eliminated. (no pre or post-processing of the specimen).
 +
* The results are produced and displayed at once on the point of care device, and can be used immediately in the caregiver's clinical decisions.
 +
The main value proposition of this profile is the securization of the workflow by a real-time patient identity checking and the consolidation of point of care orders and their observations in the enterprise-wide repository for orders and observations.
  
 
<center>[[Image:Ihe_lab_lpoct_ip.jpg]]</center>
 
<center>[[Image:Ihe_lab_lpoct_ip.jpg]]</center>
Line 17: Line 24:
  
 
'''Reduces Errors and Enhance Patient Care'''
 
'''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.
+
* For POC devices persistently connected, the real time patient identity checking secures the process:
* Reduces 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.
+
:* The caregiver scans or enters manually a patient ID or encounter ID on the device, together with contextual information (device id, staff id, tests to be performed...)
* Avoids lost specimens by tracking specimen collection in ward or in sample collection room, and specimen acceptance in laboratory.
+
:* The device queries the POC data manager and obtains in the response the patient identity as it is registered in the HIS, and displays the patient name.
* Accelerates the delivery of laboratory results to the ward staff, especially in emergency situations where a clinical decision is conditioned by some test results.
+
* POC testing devices usually require a minimal quantity of blood to operate. No transportation, no delay, hence no pre-processing of the specimen. Thus POC testing minimizes blood drawing from the patient, which makes this process particularly accurate in pediatric and neo-natology wards.
'''Improves Throughput in Care Process'''
+
* Accelerates the diagnostic, thus the treatment, in all situations where simple chemistry or hematology tests is critical to set the proper diagnostic or choose the best immediate action. Point of care testing is for this reason useful in emergency departments, intensive care units, and operating theaters.
* 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.
+
* Consolidates point of care testing observation in the common repository of orders and observations, thus keeping available for further historic access by caregivers, point of care observations together with laboratories test results.
* 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.
+
'''Favors independence of healthcare institution from their clinical and ancillary systems and devices'''
* 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.
+
* By providing clear specifications of interfaces between point of care devices, data manager and LIS, this Integration Profile enables the healthcare institution to replace one of these systems without breaking the existing data workflows.
'''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==
 
==Details==
  
The '''''Laboratory Testing Workflow (LTW) Integration Profile''''' establishes the continuity and integrity of in vitro diagnostic test orders placed towards clinical laboratories for a patient, and of the results produced for these orders, inside the healthcare institution.<br/>
+
The '''''Laboratory Point Of Care Testing (LPOCT) Integration Profile''''' is bound to in vitro diagnostic testing (tests performed on in vitro specimen). It supports all laboratory specialties that can be performed by nurses on handy testing devices usable on the point of care. Among other examples are blood gas, electrolyte, hematocrit, glucose level...<br/>
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/>
+
'''The LPOCT Integration Profile covers five major use cases:'''
The LTW Integration Profile covers three major use cases:
+
* Point of care observations to be matched with an existing order previously entered in the enterprise order management system. Process secured by real-time patient identity checking.
* Order placed with specimens collected and identified by the orderer
+
* Unordered observations. The order is to be generated afterwards by the enterprise order management system upon request from the LIS of the supervising laboratory. Process secured by real-time patient identity checking.
* Order placed with specimens collected by a third party, then identified and labeled by the laboratory information system
+
* Unordered observations on a POC device with an intermittent link (no patient identity check)
* Order generated by the laboratory and notified to the ordering system to obtain an order number.
+
* Manual entry of unordered observations. In that use case, the test is manual and the device is a keyboard the observations are keyed in on.
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/>
+
* Centralization of Quality Control (QC) results from the point of care devices to the point of care data manager.
 +
'''LPOCT Integration Profile defines 3 Transactions:'''
 +
* LAB-30 "Initiate point of care testing" accomplishes the real-time patient identity check before the test starts. This transaction is mandated by the "Patient identity checking" option.
 +
* LAB-31 "Produced observation set" uploads to the POC data manager a set of results measured on a patient specimen or on a QC specimen by a POC device. The POC data manager controls the coherence of this set of observations against its own business rules, and accepts it or rejects it.  
 +
* LAB-32 "Accepted observation set" uploads the accepted patient results from the POC data manager to the LIS of the supervising laboratory.
 +
These three transactions are leveraging the standard [http://www.clsi.org POCT1A published by CLSI]. <br/><br/>
 +
'''Other requirements for systems implementing LPOCT (mandated combinations with Actors from other Profiles):'''
 +
* The Point Of Care Data Manager system (POCDM Actor) shall also implement the Actors Patient Demographics Consumer and Patient Encounter Consumer from either '''PAM''' or '''PDQ''' Profile or both, in the ITI Technical Framework.
 +
* The LIS implementing the Order Filler Actor in the LPOCT profile shall also implement the Order Filler Actor from the '''LTW''' Profile in the Laboratory Technical Framework. This enables point of care results and orders to be consolidated together with laboratory orders and results, in the common orders and observations management system of the institution.
 +
<br/>
 +
<center>[[Image:LPOCT_dependencies_final.JPG]]</center>
 +
<br/><br/>
 +
The LPOCT profile leverages the standard [http://www.clsi.org POCT1A published by CLSI]. The table below maps the IHE Actors of LPOCT to the roles defined in the POCT1A standard:<br/>
 +
<center>[[Image:IHE_Correspondance_poct1A.JPG]]</center>
 +
<br/>
  
 
==Systems Affected==
 
==Systems Affected==
Line 43: Line 62:
 
Systems involved in this profile are:
 
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 set of point of care testing devices, performing the tests and producing the observations. Each one implements the Actor "Point Of Care Result Generator" ('''POCRG''').
* 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 Point Of Care Data Managers (Actor '''POCDM'''). Each one consolidates the observations produced by a set of POCRGs.
* 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 Information System ('''LIS''') operated in the laboratory in charge with the overall supervision of the point of care testing process. This LIS implements the Actor Order Filler.
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:'''
 
'''Actors & Transactions:'''
  
<center>[[Image:ltw-actor-transaction.JPG]]</center>
+
<center>[[Image:LPOCT_actors_transactions.JPG]]</center>
 
<br/>
 
<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==
 
==Specification==
  
'''Profile Status:''' [[Comments| Trial Implementation]]   
+
'''Profile Status:''' [[Comments| Final Text]]   
  
'''Documents:'''  
+
'''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/index.cfm#laboratory IHE Laboratory Technical Framework:]
+
:* Vol. 1 - Section 6 (LPOCT profile overview)
 +
:* Vol. 2b - Sections 3.30 - 3.32 (LPOCT transactions descriptions)
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
 +
:* [http://www.clsi.org POCT1A published by CLSI]
  
 
==See Also==
 
==See Also==
Line 69: Line 86:
 
'''Related Profiles'''
 
'''Related Profiles'''
  
* '''Integration Profiles LTW depends on'''
+
* '''Integration Profiles LPOCT 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.
+
:* [[Patient_Administration_Management]] (PAM) or [[Patient_Demographics_Query]] (PDQ) from ITI Technical Framework: The Actor Point Of Care Data Manager shall be grouped with demographics consumer Actors from PAM or PDQ or both.
:* [[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.
+
:* [[Laboratory Testing Workflow]] (LTW) from LAB Technical Framework: The Actor Order Filler in LPOCT profile shall also be an Actor Order Filler in LTW profile.
* '''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'''
 
'''Consumer Information'''
Line 82: Line 95:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:PaLM Profile]]
 +
[[Category:HL7v2]]

Latest revision as of 05:29, 1 August 2017

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

Laboratory Point Of Care Testing (LPOCT) covers diagnostic tests performed at the point of care in a healthcare institution.



Summary

The Laboratory Point Of Care Testing Profile supports the workflow related to in vitro diagnostic tests performed on the point of care or on patient bedside by caregivers in the clinical wards of the healthcare institution, this process being supervised by a laboratory of the institution. This supervision includes clinical validation of POC results, Quality Control (QC) surveillance, point of care devices surveillance, reagent delivery, and education on good testing practices delivered to the ward staff.
The point of care testing devices operated by physicians and nurses are connected to and controlled by a central Point Of Care Data Manager. This POC Data Manager is connected to the LIS of the laboratory for consolidation of the point of care testing results, and to the HIS of the institution, which provides up to date patient data.
The main characteristics of point of care testing are:

  • Specimen drawn from the patient by the caregiver, tested immediately, and then eliminated. (no pre or post-processing of the specimen).
  • The results are produced and displayed at once on the point of care device, and can be used immediately in the caregiver's clinical decisions.

The main value proposition of this profile is the securization of the workflow by a real-time patient identity checking and the consolidation of point of care orders and their observations in the enterprise-wide repository for orders and observations.

Ihe lab lpoct ip.jpg


Benefits

Reduces Errors and Enhance Patient Care

  • For POC devices persistently connected, the real time patient identity checking secures the process:
  • The caregiver scans or enters manually a patient ID or encounter ID on the device, together with contextual information (device id, staff id, tests to be performed...)
  • The device queries the POC data manager and obtains in the response the patient identity as it is registered in the HIS, and displays the patient name.
  • POC testing devices usually require a minimal quantity of blood to operate. No transportation, no delay, hence no pre-processing of the specimen. Thus POC testing minimizes blood drawing from the patient, which makes this process particularly accurate in pediatric and neo-natology wards.
  • Accelerates the diagnostic, thus the treatment, in all situations where simple chemistry or hematology tests is critical to set the proper diagnostic or choose the best immediate action. Point of care testing is for this reason useful in emergency departments, intensive care units, and operating theaters.
  • Consolidates point of care testing observation in the common repository of orders and observations, thus keeping available for further historic access by caregivers, point of care observations together with laboratories test results.

Favors independence of healthcare institution from their clinical and ancillary systems and devices

  • By providing clear specifications of interfaces between point of care devices, data manager and LIS, this Integration Profile enables the healthcare institution to replace one of these systems without breaking the existing data workflows.

Details

The Laboratory Point Of Care Testing (LPOCT) Integration Profile is bound to in vitro diagnostic testing (tests performed on in vitro specimen). It supports all laboratory specialties that can be performed by nurses on handy testing devices usable on the point of care. Among other examples are blood gas, electrolyte, hematocrit, glucose level...
The LPOCT Integration Profile covers five major use cases:

  • Point of care observations to be matched with an existing order previously entered in the enterprise order management system. Process secured by real-time patient identity checking.
  • Unordered observations. The order is to be generated afterwards by the enterprise order management system upon request from the LIS of the supervising laboratory. Process secured by real-time patient identity checking.
  • Unordered observations on a POC device with an intermittent link (no patient identity check)
  • Manual entry of unordered observations. In that use case, the test is manual and the device is a keyboard the observations are keyed in on.
  • Centralization of Quality Control (QC) results from the point of care devices to the point of care data manager.

LPOCT Integration Profile defines 3 Transactions:

  • LAB-30 "Initiate point of care testing" accomplishes the real-time patient identity check before the test starts. This transaction is mandated by the "Patient identity checking" option.
  • LAB-31 "Produced observation set" uploads to the POC data manager a set of results measured on a patient specimen or on a QC specimen by a POC device. The POC data manager controls the coherence of this set of observations against its own business rules, and accepts it or rejects it.
  • LAB-32 "Accepted observation set" uploads the accepted patient results from the POC data manager to the LIS of the supervising laboratory.

These three transactions are leveraging the standard POCT1A published by CLSI.

Other requirements for systems implementing LPOCT (mandated combinations with Actors from other Profiles):

  • The Point Of Care Data Manager system (POCDM Actor) shall also implement the Actors Patient Demographics Consumer and Patient Encounter Consumer from either PAM or PDQ Profile or both, in the ITI Technical Framework.
  • The LIS implementing the Order Filler Actor in the LPOCT profile shall also implement the Order Filler Actor from the LTW Profile in the Laboratory Technical Framework. This enables point of care results and orders to be consolidated together with laboratory orders and results, in the common orders and observations management system of the institution.


LPOCT dependencies final.JPG



The LPOCT profile leverages the standard POCT1A published by CLSI. The table below maps the IHE Actors of LPOCT to the roles defined in the POCT1A standard:

IHE Correspondance poct1A.JPG


Systems Affected

Systems involved in this profile are:

  • A set of point of care testing devices, performing the tests and producing the observations. Each one implements the Actor "Point Of Care Result Generator" (POCRG).
  • One or more Point Of Care Data Managers (Actor POCDM). Each one consolidates the observations produced by a set of POCRGs.
  • A Laboratory Information System (LIS) operated in the laboratory in charge with the overall supervision of the point of care testing process. This LIS implements the Actor Order Filler.

Actors & Transactions:

LPOCT actors transactions.JPG


Specification

Profile Status: Final Text

Documents: IHE Laboratory Technical Framework:

  • Vol. 1 - Section 6 (LPOCT profile overview)
  • Vol. 2b - Sections 3.30 - 3.32 (LPOCT transactions descriptions)

Underlying Standards:

See Also

Related Profiles

  • Integration Profiles LPOCT depends on

Consumer Information

This page is based on the Profile Template