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,

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise
Advertisements

Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing for MPI (PIX) Profile Mike Henderson.
March 17, 2005IHE and medical Standards in Denmark 1 Integrating the Healthcare Enterprise IHE for interoperability within the enterprise - Overview Charles.
September, 2005What IHE Delivers 1 HIMSS 2006 – Interoperability Showcase François Macary, AGFA HCES IHE Lab Committee co-chair IHE Clinical Laboratory.
IHE Cardiology Implantable Cardiac Device Interrogation (ICDI) Profile Nicholas Steblay 2/3/2006.
Clinical Laboratory Domain New Integration Profiles Clinical Laboratory Domain New Integration Profiles Charles Parisot GE Healthcare IHE IT Technical.
Clinical Laboratory Domain François Macary AGFA Healthcare IT IHE Laboratory Committee Co-chair.
and Patient Information Reconciliation
An Introduction to HL7 Version 2 Charlie Bishop 9 February 2005 HL7 and its key role in NPfIT and Existing Systems Integration.
1 IHE Cardiology Profiles Harry Solomon Co-chair, IHE Cardiology Technical Committee.
European Society of Cardiology IHE Cardiology Profiles Harry Solomon Co-chair, IHE Cardiology Technical Committee.
IHE PCD Interoperability Mini-Showcase at AAMI 2013 Long Beach, CA CMMS New Directions Demonstrations Monroe Pattillo Practical Health Interoperability,
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)
Systems interoperability for a better treatment and surveillance of infections ECCMID Symposium Interest of IT solutions to improve patient management.
March 30, 2005IHE Update 1 Integrating the Healthcare Enterprise IHE Update Charles Parisot, GE Healthcare IHE IT Infrastructure Technical Committee Co-chair.
Organizing IHE Integration Profiles related to the Electronic Health Record Input to the IHE ITI Tech Committee November 2002 Charles Parisot, GE Medical.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Session 5: Laboratory IHE North America Webinar Series 2008 François Macary - GMSIH (
Sept 13-15, 2004IHE Interoperability Workshop 1 Laboratory Technical Framework New Integration Profiles Francois Macary GWI Medica France - Agfa Healthcare.
Chris Lindop GE 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.
Initial slides for Layered Service Architecture
S New Security Developments in DICOM Lawrence Tarbox, Ph.D Chair, DICOM WG 14 (Security) Siemens Corporate Research.
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.
HL7 HL7  Health Level Seven (HL7) is a non-profit organization involved in the development of international healthcare.
Patient Encounter Tracking Query (PEQ) Profile Proposal for IHE International IT Infrastructure Technical Committee Last update: 23/Apr/2012.
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.
SWF Options/Charge Posting Andrei Leontiev Dynamic Imaging IHE Radiology Planning Committee.
Charles Parisot IHE Radioology Planning & Technical Committee GE Medical Systems Information Technologies IHE - A Novel Approach IHE Methodology.
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.
February 8, 2005IHE Europe Educational Event 1 Integrating the Healthcare Enterprise Basic Security Robert Horn Agfa Healthcare.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
Integrating the Healthcare Enterprise
Integrating the Healthcare Enterprise Stephen G Davies Royal Glamorgan Hospital.
1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.
Nov 30, 2004IT International Update 1 Integrating the Healthcare Enterprise IHE Update Charles Parisot, GE Healthcare IHE IT Infrastructure Technical Committee.
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.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Access to Radiology Information Cor Loef Co-chair IHE Radiology Technical.
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.
Cath Workflow Manage multimodality synchronized procedure from admission to lab discharge including unidentified patients Echo Workflow Manage echocardiography.
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.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
IHE Cardiology Displayable Report (DRPT) Profile Harry Solomon, Tom Dolan February 16, 2005 Rev 0.3.
September, 2005What IHE Delivers 1 Jim Riggi – Medflow, Inc. Co-Chair Technical Committee IHE Eye Care Webinar Requirements for HIS/PMS/HER vendors for.
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.
Case Study: HL7 Conformance in VA Imaging Mike Henderson Principal Consultant Eastern Informatics, Inc.
June, 2006What IHE Delivers 1 IHE Workshop Changing the Way Healthcare Connects Donald Van Syckle DVS Consulting, Inc. Jim Riggi, CTO Medflow, Inc.
Patient Demographics Query (PDQ) Didi Davis Director, Eclipsys Corporation Co-Chair, IT Infrastructure Planning Committee.
Patient Identifier Cross-Referencing for MPI (PIX)
IHE Eye Care “Charge Posting”
IHE Clinical Laboratory Update
Retrieve Protocol for Execution (RPE)
Presentation transcript:

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, France René Spronk, Ringholm GmbH IHE Laboratory Planning and Technical Committee

Feb. 9, 2005IHE Educational Meeting 2 Laboratory IHE Integration Profiles In Process –TI Nov 2004 Laboratory Device Automation (LDA) In Process –TI Nov 2004 Pre-analytic process, analysis and post-analytical treatment Laboratory Scheduled Workflow (LSWF) Completed in 2003 Tests performed by a laboratory for an identified inpatient or outpatient In Process Laboratory Information Reconciliation (LIR) In Process Tests performed on an unidentified or misidentified patient Laboratory Code Set Distribution (LCSD) Sharing the batteries and tests code sets throughout the enterprise In Process –TI Nov 2004 Laboratory Point Of Care Testing (LPOCT) In Process –TI Nov 2004 Tests performed on point of care or patient’s bedside

Feb. 9, 2005IHE Educational Meeting 3 LSWF: Workflow Technical validation Clinical validation Selected standard: HL7 version 2.5

Feb. 9, 2005IHE Educational Meeting 4 The Laboratory Technical Framework Laboratory Code Set Distribution

Feb. 9, 2005IHE Educational Meeting 5 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 …

Feb. 9, 2005IHE Educational Meeting 6 Laboratory Code Set Distribution Actors/Transaction Laboratory Code Set Master LAB-xx: Laboratory Code Set Management Laboratory Code Set Consumer Order Filler Enterprise Common Repository … Order Placer Order Result Tracker Automation Manager Order Filler …

Feb. 9, 2005IHE Educational Meeting 7 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)

Feb. 9, 2005IHE Educational Meeting 8 Laboratory Code Set Distribution Use Case 2 (out of scope for this year) Laboratory Code Set Master Laboratory Code Set Consumer Updates observation/test/battery codes Laboratory Code Set Management (UPD) Updates Observation/Test/Battery Code Sets Observation, Test and Battery codes of the Consumer are updated by codes sent by the Master. Updates are at the record level : add record(s), delete record(s), update record(s).

Feb. 9, 2005IHE Educational Meeting 9 Laboratory Code Set Distribution Use Case 3 (out of scope for this year) Laboratory Code Set Master Laboratory Code Set Consumer Unknown / Expired observation/test/battery codes Laboratory Code Set Management Query for Observation/Test/Battery Code Sets The Laboratory Code Set consumer either periodically queries for the entire codeset, or it queries for the details of specific Observation, Test and Battery codes. The query responses are used to update the code set are at the record level : add record(s), delete record(s), update record(s). Query for Laboratory Code Set

Feb. 9, 2005IHE Educational Meeting 10 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

Feb. 9, 2005IHE Educational Meeting 11 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

Feb. 9, 2005IHE Educational Meeting 12 Generic MFN – Abstract Message MSH MFI Master File Identification { MFE Master File Entry [ <other resource related segments, e.g. LOC > ] } MFIMFELOC 1..n 0..n

Feb. 9, 2005IHE Educational Meeting 13 Generic MFN – Location Example MSH|^~\&|MyHIS||PhysioApp|| ||MFN^M05|31|P|2.4||AL|NE MFI|LOC|EH_Locations|UPD|||ER MFE|MDL|M226||Aqua1^^^Eastern Hospital^^^Physio^B^ Aqua therapy room 1|PL LOC|Aqua1^^^Eastern Hospital^^^Physio^B^Aqua therapy room 1||L MFE|MUP|M227||Aqua2^^^Eastern Hospital^^^Physio^B^ Aqua therapy room 2|PL LOC|Aqua2^^^Eastern Hospital^^^Physio^B^Aqua therapy room 2| Aqua therapy room 2|L|Eastern Hospital| LDP| Aqua2^^^Eastern Hospital^^^Physio^B^Aqua therapy room 2|PHY^ Physiotherapy||REH~PRE|D~O|

Feb. 9, 2005IHE Educational Meeting 14 Generic MFN Event Codes MFI – File Level Event Codes REP:Replace current version of this master file with the version contained in this message. UPD:Change file records as defined in the record-level event codes for each record that follows. (out of scope for this year) MFE – Record Level Event Codes MAD:Add record to master file. MDL:Delete record from master file. MUP:Update record for master file. MDC:Deactivate: discontinue using record in master file, but do not delete from database. MAC:Reactivate deactivated record.

Feb. 9, 2005IHE Educational Meeting 15 Generic MFK – Acknowledgment MSH MSA Message Acknowledgement [ERR] MFI Master File Identification { [MFA] Master File Acknowledgement } MFIMFA 0..n MFIMFELOC 1..n 0..n Only in case of errors in related MFE/LOC

Feb. 9, 2005IHE Educational Meeting 16 Generic MFK Ack, Location Example MSH|^~\&|FysioApp||MyZIS|| ||MFK^M05|31|P|2.4| |AL|NE MFI|LOC|EH_Locations|UPD|||NE MFA|MDL|M226||U^Location not present| Aqua1^^^Eastern Hospital^^^Physio^B^Aqua therapy room 1|PL (NOTE: successful changes are NOT acknowledged) MFA|MUP|M227||S|Aqua2^^^Eastern Hospital^^^Physio^B^Aqua therapy room 2|PL

Feb. 9, 2005IHE Educational Meeting 17 Laboratory Code Set Distribution LAB-XXX Message Structures MFN^M08 – Master File Notification – Test/Observation (Numeric) MSHMessage Header[1..1]chap. 2 MFIMaster File Identification[1..1]chap. 8 {[1..*] MFEMaster File Entry[1..1]chap. 8 OM1General Segment[1..1]chap. 8 [OM2] Numeric Observation Segment[0..1]chap. 8 } MFN^M09 – Master File Notification – Test/Observation (Categorical) MFN^M10 – Master File Notification – Batteries MFN^M11 – Master File Notification – Test/Calculated Observation [OM3] Categorical Test/Obs. Segment[0..1]chap. 8 [OM5] Observation Batteries[0..1]chap. 8 [OM6 Obs. calculated from other Obs.[0..1]chap. 8 OM2] Numeric Observation Segment[0..1]chap. 8

Feb. 9, 2005IHE Educational Meeting 18 OM1-2Producer’s Service/Test/Observation ID OM1-4Specimen required OM1-5Producer ID OM1-18Nature of Service/Test/Observation: P battery, A atomic, S super-set of batteries, C single observation calculated OM1-19Report sub-header OM1-20Report display order OM2-2Units of Measure OM2-3Range of Decimal Precision Laboratory Code Set Distribution OM1 – General Segment OM2 – Numeric Observation Segment

Feb. 9, 2005IHE Educational Meeting 19 OM3-2Preferred Coding System OM3-3Valid Coded answers OM3 – Categorical Service/Test/Observation Segment Laboratory Code Set Distribution OM5 –Observation Batteries Segment OM5-2Tests/observations included within Battery OM6 –Observation that are Calculated OM6-2Derivation Rule

Feb. 9, 2005IHE Educational Meeting 20 Atomic Tests, Numeric Results MSH|^~\&|OF|LabSystem|OP|| ||MFN^M08|2106|2.5|||NLD|8859/1|NL| MFI|OMA|OF_OMA_NL_ |REP|||ER| MFE|MAD|1846||1846^CREABL/Creatinine^L|CE| OM1|1|1846^CREABL/Creatinine^L|NM|Y|K231^Klinisch Chemisch Laboratorium^?|||Creatinine||||||||||A| OM2|1|umol/l|6.0|| OM4|1||stolbuis rode dop4||ml|^volbloed| MFE|MAD|1848||1848^CREAUV/Creatinine^L|CE| OM1|2|1848^CREAUV/Creatinine^L|NM|Y|K231^Klinisch Chemisch Laboratorium^?|||Creatinine||||||||||A| OM2|2|mmol/l|6.0|| OM4|2||24-uurs bokaal|||^urine verzamel|

Feb. 9, 2005IHE Educational Meeting 21 Test with derived result MSH|^~\&|OF|LabSystem|OP|| ||MFN^M11|2107|2.5||| NLD|8859/1|NL| MFI|OMD|OF_OMD_NL_ |REP|||ER| MFE|MAD|1849||1849^CLEA/Creatinine clearance^L|CE OM1|1|1849^CLEA/Creatinine clearance^L|NM|Y|K231^Klinisch Chemisch Laboratorium^?|||Creatinine clearance||||||||||C| OM6|1|(CREAUV * HOEV) / (CREASE * 1440) OM2|1|ml/min|4.0||

Feb. 9, 2005IHE Educational Meeting 22 Thank you for your attention…