Clinical Laboratory Domain New Integration Profiles Clinical Laboratory Domain New Integration Profiles Charles Parisot GE Healthcare IHE IT Technical.

Slides:



Advertisements
Similar presentations
Pathfinding Session: Cardiology IHE North America Webinar Series 2008 Harry Solomon IHE International Board GE Healthcare.
Advertisements

Integrating the Healthcare Enterprise
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing for MPI (PIX) Profile Mike Henderson.
April 4, 2005François Macary - AGFA Healthcare IT 1 Identifiers for work items in Laboratory Scheduled Work Flow (LSWF) and Laboratory Device Automation.
March 17, 2005IHE and medical Standards in Denmark 1 Integrating the Healthcare Enterprise IHE for interoperability within the enterprise - Overview Charles.
Charge Posting Integration Profile Rita Noumeir Ph.D. IHE Planning Committee IHE Technical Committee.
September, 2005What IHE Delivers 1 HIMSS 2006 – Interoperability Showcase François Macary, AGFA HCES IHE Lab Committee co-chair IHE Clinical Laboratory.
IHE Workshop – June 2006What IHE Delivers 1 Cynthia A. Levy Cedara Software IHE Technical Committee Import Reconciliation Workflow Profile.
September, 2005What IHE Delivers 1 IHE Laboratory François Macary, AGFA Healthcare IHE Laboratory cochair IHE Laboratory cochair.
IHE Cardiology Implantable Cardiac Device Interrogation (ICDI) Profile Nicholas Steblay 2/3/2006.
IHE Eye Care Appointment Scheduler Linda Wedemeyer, MD Co-Chair, IHE Eye Care Planning Committee Ophthalmologist, Veterans Health Administration
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Post-Processing Workflow Sanjay Jain Co-Chair, Radiology Planning.
September, 2005What IHE Delivers 1 Francois Macary, Agfa HealthCare co-chair Lab Technical Committee co-chair Lab Technical Committee Sharing Laboratory.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise IHE Tools for Users and Integrators: Connectathon, Integration Statements.
September, 2005What IHE Delivers 1 IHE Laboratory Sending out the ADT actor, back to the infrastructure.
Clinical Laboratory Domain François Macary AGFA Healthcare IT IHE Laboratory Committee Co-chair.
Integrating the Healthcare Enterprise
DICOM Structured Reporting Workshop - March 2000 Structured Reporting and the IHE Year 2 Technical Framework Simon Wail, PhD Marconi Medical Systems.
and Patient Information Reconciliation
February 7-10, 2005Noordwijkerhout, IHE Workshop 1 A new Profile for the Laboratory Domain: Laboratory Device Automation Francois Macary GWI Medica France.
Feb 07-10, 2005IHE Educational Workshop 1 The Laboratory Technical Framework Laboratory Information Reconciliation Michael Müller (iSOFT Deutschland, Germany)
Cross-Jurisdictional Immunization Data Exchange Project Updated 4/29/14.
Systems interoperability for a better treatment and surveillance of infections ECCMID Symposium Interest of IT solutions to improve patient management.
This presentation prepared for Now is the time to initiate the one change that will have the most leverage across your business systems Patient Identity.
Integrated Hospital Management System. Integrated Hospital Management System software is user-friendly software. The main objectives of the system is.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Organizing IHE Integration Profiles related to the Electronic Health Record Input to the IHE ITI Tech Committee November 2002 Charles Parisot, GE Medical.
Feb. 9, 2005 IHE Educational Meeting 1 IHE LCSD Profile – Laboratory Code Set Distribution Based on HL7 version 2.x, Chapter 8 Jean-Christophe Cauvin,
Session 5: Laboratory IHE North America Webinar Series 2008 François Macary - GMSIH (
September, 2005What IHE Delivers 1 Cochairs:Francois Macary - Agfa HealthCare Nobuyuki Chiba - A&T Corporation IHE Laboratory.
Sept 13-15, 2004IHE Interoperability Workshop 1 Laboratory Technical Framework New Integration Profiles Francois Macary GWI Medica France - Agfa Healthcare.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
February 7-10, 2005IHE Interoperability Workshop 1 Established Profile for connectathon 2005: Laboratory Scheduled WorkFlow Francois Macary GWI Medica.
1 Charles Parisot, GE Healthcare IHE IT Infrastructure Planning Committee Co-chair IHE Update to DICOM.
February 7-10, 2005Noordwijkerhout IHE Workshop 1 Integrating the Healthcare Enterprise A new Profile for the Laboratory Domain: Laboratory Point Of Care.
Patient Encounter Tracking Query (PEQ) Yutaka Ando MD Yutaka Ando MD
Pathfinding Session: Lab Information Systems Lab Automation Managers Lab IVD devices POCT IVD devices POC Data Managers Robotized container dispensers.
Improving Efficiency in Clinical Laboratory
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
Integration Profiles - Overview Integrating the Healthcare Enterprise G. Claeys Agfa Healthcare R&D, Technology Manager Vendor co-chair IHE Europe Courtesy.
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
SWF Options/Charge Posting Andrei Leontiev Dynamic Imaging IHE Radiology Planning Committee.
CS 493 Project Definition The project assignment is a simplified version of the Integrating Healthcare Enterprise (IHE) Cross-Enterprise Document Sharing.
IHE Radiology –2007What IHE Delivers 1 Ellie Avraham IHE Technical Committee May 23, 2007 Cross Domain Review Laboratory.
Feb , 2005IHE Europe Workshop 1 Integrating the Healthcare Enterprise – Radiology – Established IHE Integration Profiles: Dr. Nikolaus Wirsz –Siemens.
Established Profile Laboratory Scheduled WorkFlow Established Profile Laboratory Scheduled WorkFlow Charles Parisot GE Healthcare IHE IT Technical Committee.
Sharing Value Sets (SVS Profile) Ana Estelrich GIP-DMP.
August 31, 2004IHE European Cardiology 1 Integrating the Healthcare Enterprise IHE, beyond cardiology and radiology An interoperability strategy for the.
IHE Workshop – June 2006What IHE Delivers 1 Import Reconciliation Workflow Profile IHE North America Webinar Series 2008 Chris Lindop Radiology GE Healthcare.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Integrating the Healthcare Enterprise
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Status of IHE Laboratory Francois Macary, GWI Medica France Charles.
IHE Workshop – June 2007What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.
PCD User Handbook 2010 Purpose The Handbook is designed to help healthcare professionals implement IHE on a new clinical system purchase or upgrade an.
IHE Workshop – June 2006What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.
20/11/2009 DICOM WG13 Atsushi Amano Medical Imaging Systems Committee Japanese Association of Healthcare Information Systems Industry (JAHIS) 1 JAHIS /
IHE –Radiology Workflow – Present & Future Extensions EuroPACS 2002 Conference – Oulu / Finland Integrating the Healthcare Enterprise – –The Radiology.
September, 2005What IHE Delivers 1 Jim Riggi – Medflow, Inc. Co-Chair Technical Committee IHE Eye Care Webinar Requirements for HIS/PMS/HER vendors for.
IHE Workshop – February 2007 What IHE Delivers 1 Credits for many slides to: Cynthia A. Levy, Cedara Software IHE Technical Committee Import Reconciliation.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
Integrating the Healthcare Enterprise Update on IHE-Laboratory Charles Parisot General Electric Medical Systems IT.
June, 2006What IHE Delivers 1 IHE Workshop Changing the Way Healthcare Connects Donald Van Syckle DVS Consulting, Inc. Jim Riggi, CTO Medflow, Inc.
Integration Profiles Scheduled Workflow Admit, order, schedule,
Patient Identifier Cross-Referencing for MPI (PIX)
IHE Clinical Laboratory Update
Health Care Information Systems
Presentation transcript:

Clinical Laboratory Domain New Integration Profiles Clinical Laboratory Domain New Integration Profiles Charles Parisot GE Healthcare IHE IT Technical Committee Co-chair François Macary AGFA Healthcare IT IHE Laboratory Committee Co-chair

IHE Lab today and to-morrow Five profiles: –Laboratory Scheduled Workflow (LSWF) –Laboratory Information Reconciliation (LIR) –Laboratory Point Of Care Testing (LPOCT) –Laboratory Device Automation (LDA) –Laboratory Code Set Distribution (LCSD) Future plans –Incorporate analyzer images in the result workflow –Cross-enterprise sharing of lab reports, using CDA-R2 –Specimen labels workflow Ordering, placing, scheduling and performing clinical laboratory tests both for Hospital and Ambulatory. Microbiology included. Anatomic pathology and blood bank excluded

Laboratory Information Reconciliation Match clinical lab observations produced on specimens collected from misidentified or unidentified patient with the patients record. Match clinical lab observations produced on specimens with orders created afterwards, either in the Order Placer or in the Order Filler application. LIR profile depends upon LSWF and LDA profiles

1.Unidentified Patient registered at ADT. Clinical lab tests ordered at Order Placer level. 2.Unidentified Patient registered at ADT. Clinical lab tests ordered at Order Filler level. 3.Unidentified Patient registered at Order Placer. Clinical lab tests ordered at Order Placer level. 4.Unidentified Patient registered at Order Filler. Clinical lab tests ordered at Order Filler level. Laboratory Information Reconciliation Use Cases 1, 2, 3, 4 The Unidentified Patient cases cover scenarios in which the care situation requires that tests be ordered immediately, even before proper Patient registration. It also covers the scenario of tests performed before the order is entered, whether the patient is identified or not.

5.Clinical lab tests performed on laboratory automation before creation of the order. The order is created automatically from the results. The order is created afterwards at Order Filler and matched to the results. Laboratory Information Reconciliation Use Case 5 LIR also covers the scenario of tests performed before the order is entered, no matter the patient is identified or not.

IHE Lab today and to-morrow Five profiles: –Laboratory Scheduled Workflow (LSWF) –Laboratory Information Reconciliation (LIR) –Laboratory Device Automation (LDA) –Laboratory Point Of Care Testing (LPOCT) –Laboratory Code Set Distribution (LCSD) Future plans –Incorporate analyzer images in the result workflow –Cross-enterprise sharing of lab reports, using CDA-R2 –Specimen labels workflow Ordering, placing, scheduling and performing clinical laboratory tests both for Hospital and Ambulatory. Microbiology included. Anatomic pathology and blood bank excluded

Laboratory Device Automation (LDA) Order FillerOrder Placer Order Result Tracker ADT Placer order Filler order Demographics Results Demographics Results Work order LSWF LDA Work Order Steps Automation Manager Clinical Laboratory

Scope of LDA Integration Profile Workflow between an Automation Manager and the automated devices that it handles. Workflow specimen based: A sequence of steps, each of which uses a specimen on a device. Scope limited to devices operated by the lab staff. Goal: To fulfill a Work Order and its clinical tests on the related specimens, using the various devices connected to the Automation Manager. Except for the robotic transportation of the specimen, this profile does not address electromechanical command interface. Its transactions carry the needed or produced specimen related data back and forth between Automation Manager and Devices

Fulfillment of a Work Order A Work Order is split into a sequence of steps according to the devices involved in its process. This sequence of steps includes three main phases: –the pre-analytical process of the specimens (sorting, centrifugation, aliquoting, transportation, decapping) –the analytical process (run of the clinical tests on the specimen) –the post-analytical process (recapping, transportation, rerun, dilution, storage and retrieval).

Example of workflow Automation Manager Robotic Specimen Transportation System decapper Step 2: decap Chemistry Analyzer Step 3: Convey to chemistry analyzer centrifuging Test Na, K, Cl Perform electrolye Work Order for serum n° 123 Step 4: Query for test? Schedules steps 1 to 6 Downloads steps 1, 2, 3, 5, 6 Schedules steps 1 to 6 Downloads steps 1, 2, 3, 5, 6 Send the results Step 1: Convey to decapper recapper Step 6: recap Step 5: Convey to recapper Blood specimen Serum

LAB-22 Query for WOS LAB-26 SWOS status change LAB-21 WOS download LAB-22 Query for WOS LAB-23 AWOS status change LAB-21 WOS download Pre/Post-processorAnalyzer Automation Manager LDA: Actors & Transactions WOS = Work Order Step –AWOS = Analytical Work Order Step: Produces observations –SWOS = Specimen processing Work Order Step. Does not produce any observation

LDA: Actors and transactions ActorsTransactionsOptHL7 2.5 messages Automation Manager LAB-21 : WOS DownloadR OML^O33 / ORL^O34 LAB-22 : WOS QueryR QBP^Q11 / RSP^K11 LAB-23 : AWOS Status Change R OUL^R22 / ACK^R22 LAB-26 : SWOS Status Change O SSU^U03 / ACK^U03 AnalyzerLAB-21 : WOS DownloadO OML^O33 / ORL^O34 LAB-22 : WOS QueryO QBP^Q11 / RSP^K11 LAB-23 : AWOS Status Change R OUL^R22 / ACK^R22 Pre/Post Processor LAB-21 : WOS DownloadO OML^O33 / ORL^O34 LAB-22 : WOS QueryO QBP^Q11 / RSP^K11 LAB-26 : SWOS Status Change R SSU^U03 / ACK^U03

LDA: Options ActorOptions Automation ManagerManagement of Pre/Post-processor AnalyzerQuery mode WOS Download mode WOS Pre/Post-processorQuery mode WOS Download mode WOS

IHE Lab today and to-morrow Five profiles: –Laboratory Scheduled Workflow (LSWF) –Laboratory Information Reconciliation (LIR) –Laboratory Device Automation (LDA) –Laboratory Point Of Care Testing (LPOCT) –Laboratory Code Set Distribution (LCSD) Future plans –Incorporate analyzer images in the result workflow –Cross-enterprise sharing of lab reports, using CDA-R2 –Specimen labels workflow Ordering, placing, scheduling and performing clinical laboratory tests both for Hospital and Ambulatory. Microbiology included. Anatomic pathology and blood bank excluded

Scope of LPOCT Tests of clinical biology, performed on point of care or patient bedside –In vitro tests: performed on a specimen, not on the patient itself –Usually quick tests, specimen collected, tested at once and eliminated –No pre or post-processing (like in LDA) –Results used immediately by the care provider in its clinical decisions Supervision by a clinical laboratory of the healthcare enterprise –Training provided to the ward staff good practices on specimen and analyzer –Provision of reagent –Supervision of quality control –Clinical validation a posteriori

Contraints and benefits of point of care testing Results obtained at once increases the efficiency of clinical decisions Minimizes the blood quantity drawn from the patient, because of the immediate use of the specimen. E.g. Two drops are enough to test blood gas, electrolyte and hematocrit of a new-born baby. Preserving a high level of quality of the POCT process requires its supervision by a clinical laboratory.

Examples of LPOCT Portable blood gaz and chemistry analyzer used by the nurse on patient bedside Blood gas analyzer permanently installed in a surgery theater Coagulation analyzer in acute care ward Glucometer used by the patient in home care Work station on which the nurse manually enters the results of pregnancy stick tests.

The IHE actors of LPOCT Point Of Care Result Generator (POCRG) Produces the results from a specimen By measurement of an analyte on a specimen By calculation By manual entry Point Of Care Data Manager (POCDM) Handles and administers a set of POCRG Controls the process, checks the patient identity and location Collects the patient results Collects and manages the QC results Forwards the patient results to the Order Filler

The IHE actors of LPOCT Order Filler Recipient of POCT results Stores the results within matched or generated orders Performs the clinical validation

Ward Clinical laboratory LPOCT: Actors and Transactions Point Of Care Result Generator Point Of Care Data Manager Order Filler Lab-32: Accepted observation set Lab-31: Performed observation set Lab-30: (option persistent cnx) Initiate testing on a specimen POCDM is assumed to be provided with up-to-date patient demographics and visit data, using an appropriate profile (PAM or PDQ) LPOCT depends upon LSWF: The Order Filler is also involved in LSWF profile.

Transactions and options ActorsTransactionsOptionality Order FillerTransaction LAB-32R Point Of Care Data Manager Transaction LAB-30O Transaction LAB-31R Transaction LAB-32R Point Of Care Result Generator Transaction LAB-30O Transaction LAB-31R Transaction LAB-30 is required with option Patient Identity Checking

Selected standards POCRGPOCDMOrder Filler Based on HL7 v2.5 Based on HL7 early v3 POCT 1-A, published by CLSI (ex NCCLS)

IHE Lab today and to-morrow Five profiles: –Laboratory Scheduled Workflow (LSWF) –Laboratory Information Reconciliation (LIR) –Laboratory Device Automation (LDA) –Laboratory Point Of Care Testing (LPOCT) –Laboratory Code Set Distribution (LCSD) Future plans –Incorporate analyzer images in the result workflow –Cross-enterprise sharing of lab reports, using CDA-R2 –Specimen labels workflow Ordering, placing, scheduling and performing clinical laboratory tests both for Hospital and Ambulatory. Microbiology included. Anatomic pathology and blood bank excluded

Laboratory Code Set Distribution The goal of this profile is to simplify the configuration of the systems involved in the Laboratory Scheduled Workflow. The Laboratory Code Set Distribution Profile offers the means to share the same set of test/observation codes between different actors. Other information can be also exchanged like presentation of results, laboratory codes (in which lab a test is performed), units …

Laboratory Code Set Distribution Actors/Transaction Laboratory Code Set Master LAB-51: Laboratory Code Set Management Laboratory Code Set Consumer Grouped with: Order Filler Enterprise Common Repository … Grouped with: Order Placer Order Result Tracker Automation Manager Order Filler …

Replaces Observation/Test/Battery Code Sets All Observation, Test and Battery code sets of the Consumer are replaced by the code sets sent by the Master. This Use Case is used both for initialization as well as periodic (weekly, monthly) update. Laboratory Code Set Distribution Use Case 1 Laboratory Code Set Master Laboratory Code Set Consumer Creates observation-test - battery codes Laboratory Code Set Management (REP)

Laboratory Code Set Distribution Standard Interactions based on HL7 V2.5, Master Files (chapter 8). Advantages of using HL7 V2.5: HL7 is already implemented on laboratory systems; no need to implement a new protocol Master Files are already adopted by some vendors. Messages are rich enough to transport other information than just observation/test/battery codes : presentation of the results laboratory codes units of measure

HL7 Master Files Master files are a set of common reference files used by one or more application systems. Some common examples of master files in the healthcare environment include: staff and health practitioner master file location (census and clinic) master file lab test definition file exam code (lab, radiology) definition file