August 31, 2004 IHE European Cardiology


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Generalized the systems because there are many ways vendors can bundle products. Some PACS may include a Report Creator, others may not. Some Modalities may include a Print Composer, others may not.
  • Year one (2003) brought the first integration profile « Laboratory Scheduled Workflow ». This profile supports the most common situation: The tests are placed to and performed by a clinical laboratory on specimens collected from a patient correctly identified in the hospital. Year two (2004) is expected to complete the framework with four more profiles: « Laboratory Patient Information Reconciliation » profile provides the messaging to resolve all the exceptional situations: Tests performed on an unidentified patient. Urgent tests performed before the order was generated. Merging of a misidentified patient… « Laboratory Point Of Care Testing » supports specimen testing on the point of care or on the patient’s bedside, by the care unit staff, under the overall supervision of a clinical laboratory. « Laboratory Device Automation » describes the messaging between the laboratory automation manager and all the automated devices (analyzers, robotic decappers, centrifuges, conveyors, aliquoters, …). « Laboratory Code Set Distribution » enables the various actors to rely on a common dictionary of tests and batteries. Some of these new profiles will be achieved in 2004, some others may need one more cycle.
  • August 31, 2004 IHE European Cardiology

    1. 1. Integrating the Healthcare Enterprise IHE, beyond cardiology and radiology An interoperability strategy for the enterprise Charles Parisot, GE Healthcare IHE IT Infrastructure Co-chair
    2. 2. Goals of IHE <ul><li>Speed up the rate and quality of integration in healthcare environments </li></ul><ul><li>Foster communication among vendors </li></ul><ul><li>Prove that integration is attainable based on standards </li></ul><ul><li>Improve the efficiency and effectiveness of clinical practice </li></ul>
    3. 3. IHE drives healthcare standards based-integration
    4. 4. A Proven Standards Adoption Process User Site IHE Technical Framework IHE Connect-a-thon Results <ul><li>IHE Integration Profiles at the heart of IHE : </li></ul><ul><ul><li>Detailed selection of standards and options each solving a specific integration problem </li></ul></ul><ul><ul><li>A growing set of effective provider/vendor agreed solutions </li></ul></ul><ul><ul><li>Vendors can implement with ROI </li></ul></ul><ul><ul><li>Providers can deploy with stability </li></ul></ul>IHE Integration Profiles B IHE Integration Profile A Easy to Integrate Product s IHE Connect-a-thon Product With IHE IHE Demonstration RFP Standards Product IHE Integration Statement
    5. 5. IHE 2004 achievements and expanding scope Over 80 vendors involved world-wide, 4 Technical Frameworks 31 Integration Profiles, Testing at yearly Connectathons, Demonstrations at major exhibitions world-wide Provider-Vendor cooperation to accelerate standards adoption
    6. 6. IHE Deliverables <ul><li>Venues for discussion between users and vendors </li></ul><ul><li>Common vocabulary/ view of the world based on: </li></ul><ul><ul><li>Standard information models (HL7, DICOM, etc.) </li></ul></ul><ul><ul><li>Coded information and their meaning </li></ul></ul><ul><li>Technical Framework = An Implementation Guide </li></ul><ul><ul><li>ACTORS in roles performing TRANSACTIONS to accomplish Specific Processes </li></ul></ul><ul><ul><li>Together they form INTEGRATION PROFILES </li></ul></ul><ul><li>Connectathon: Cross-vendor testing opportunity . </li></ul><ul><li>Public Demonstrations / Education/ Publications </li></ul><ul><li>Marketing Tools for compliant products: </li></ul><ul><ul><li>Connectathon results published </li></ul></ul><ul><ul><li>Products claim conformance with Integration Statement </li></ul></ul>
    7. 7. What IHE is NOT! <ul><li>A standards development organization </li></ul><ul><ul><li>Uses established standards (HL7, DICOM, others) to address specific clinical needs </li></ul></ul><ul><ul><li>Activity complementary to SDOs, formal relationship with HL7 and DICOM </li></ul></ul><ul><li>Simply a demonstration project </li></ul><ul><ul><li>Demos only one means to the end—adoption </li></ul></ul><ul><ul><li>Backed up by documentation, tools, testing, and publication of information </li></ul></ul>
    8. 8. IHE: A stepwise approach Cardiology Labora- t ory Pharmacy,….. Radiolog y Patient Identifier Linkage, Registries, Security Electronic Health Record Enterprise Scheduling Patient Management Order Management
    9. 9. Key IHE Concepts <ul><li>Generalized Systems -> Actors </li></ul><ul><li>Interactions between Actors -> Transactions </li></ul><ul><li>Problem/Solution Scenarios -> Integration Profiles </li></ul><ul><li>For each Integration Profile: </li></ul><ul><ul><li>the context is described (which real-world problem) </li></ul></ul><ul><ul><li>the actors are defined (what systems are involved) </li></ul></ul><ul><ul><li>the transactions are defined (what must they do) </li></ul></ul>
    10. 10. IHE Radiology Integration profiles - Patient Information Reconciliation Access to Radiology Information Consistent Presentation of Images Basic Security Evidence Documents Key Image Notes Simple Image and Numeric Reports Presentation of Grouped Procedures Post-Processing Workflow Reporting Workflow Charge Posting Scheduled Workflow
    11. 11. IHE Penetration in Radiology <ul><li>Now entering Year 6 !! </li></ul><ul><li>50+ vendors worldwide </li></ul><ul><li>100+ systems in annual Connectathons </li></ul><ul><li>Geographic spread </li></ul><ul><ul><li>U.S., France, Germany, Japan, Italy, Korea, Taiwan, U.K, Norway, Netherlands, Spain, etc. </li></ul></ul><ul><li>Well over 100 commercial products available </li></ul>
    12. 12. IHE IT Infrastructure 2004-2005 Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Patient Identifier Cross-referencing for MPI Map patient identifiers across independent identification domains Synchronize multiple applications on a desktop to the same patient Patient Synchronized Applications Enterprise User Authentication Enterprise User Authentication Provide users a single name and centralized authentication process across all systems Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Retrieve Information for Display Access a patient’s clinical information and documents in a format ready to be presented to the requesting user Consistent Time Coordinate time across networked systems Audit Trail & Node Authentication Centralized privacy audit trail and node to node authentication to create a secured domain. New Patient Demographics Query New Personnel White Page Access to workforce contact information New Cross-Enterprise Document Sharing Registration, distribution and access across health enterprises of clinical documents forming a patient electronic health record New
    13. 13. IHE Penetration in IT Infrastructure and Laboratory <ul><li>Has just completed Year 1 !! </li></ul><ul><li>About 20 vendors worldwide </li></ul><ul><li>40+ systems in annual Connectathons </li></ul><ul><li>Geographic spread </li></ul><ul><ul><li>U.S., France, Italy, Japan, Germany, etc. </li></ul></ul><ul><li>Commercial products appearing </li></ul>
    14. 14. IHE Laboratory Integration Profiles Laboratory Scheduled Workflow (LSWF) done in 2003 Tests performed by a laboratory for an identified inpatient or outpatient Laboratory Patient Information Reconciliation (LPIR) year 2004 Tests performed on an unidentified or misidentified patient Laboratory Code Set Distribution (LCSD) year 2004 Sharing the batteries and tests code sets throughout the enterprise Laboratory Device Automation (LDA) year 2004 Pre-analytic process, analysis and post-analytical treatment Laboratory Point Of Care Testing (LPOCT) year 2004 Tests performed on point of care or patient’s bedside
    15. 15. IHE 2004 achievements and expanding scope Over 80 vendors involved world-wide, 4 Technical Frameworks 31 Integration Profiles, Testing at yearly Connectathons, Demonstrations at major exhibitions world-wide Provider-Vendor cooperation to accelerate standards adoption
    16. 16. An Example of IHE IT Infrastructure Integration Profile
    17. 17. Introduction: EHR Cross-Enterprise Document Sharing First step towards the longitudinal dimension of the EHR Focus: Support document sharing between EHRs in different care settings and organizations
    18. 18. Acute Care (Inpatient) GPs and Clinics (Ambulatory) Long Term Care Other Specialized Care (incl. Diagnostics Services) Continuity of Care : Patient Longitudinal Record Typically, a patient goes through a sequence of encounters in different Care Settings
    19. 19. Clinical IT System Finding the records of a patient-Manual & tedious The challenge: Finding and accessing easily documents from other care providers In the community. community Clinical Encounter Records Sent Laboratory Results Specialist Record Hospital Record
    20. 20. Sharing records that have been published community Clinical Encounter Clinical IT System Index of patients records (Document-level) 1-Patient Authorized Inquiry Temporary Aggregate Patient History 4-Patient data presented to Physician Sharing System 3-Records Returned Reference to records Laboratory Results Specialist Record Hospital Record 2-Reference to Records for Inquiry
    21. 21. Acute Care (Inpatient) PCPs and Clinics (Ambulatory) Long Term Care Other Specialized Care or Diagnostics Services Building and accessing Documents EHR-CR: Care Record systems supporting care delivery Documents Registry EHR-LR: Longitudinal Record as used across-encounters Document Repository Submission of Document References Retrieve of selected Documents
    22. 22. XDS – Value Proposition <ul><li>Foundation for Health IT Infrastructures: Shared Electronic Health Record, in a community, region, etc. </li></ul><ul><li>Effective means to contribute and access clinical documents across health enterprises. </li></ul><ul><li>Scalable sharing of documents between private physicians, clinics, long term care, pharmacy, acute care with different clinical IT systems. </li></ul><ul><li>Easy access: Care providers are offered means to query and retrieve clinical documents of interest. </li></ul>
    23. 23. XDS - Value Proposition <ul><li>Distributed: Each Care delivery organization “publishes” clinical information for others. Actual documents may remain in the source EHR-CR. </li></ul><ul><li>Cross-Enterprise: A Registry provides an index for published information to authorized care delivery organizations belonging to the same clinical affinity domain (e.g. an LHII). </li></ul><ul><li>Document Centric: Published clinical data is organized into “clinical documents”. using agreed standard document types (HL7-CDA, ASTM-CCR, PDF, DICOM, etc.). </li></ul><ul><li>Document Content Neutral: Document content is processed only by source and consumer IT systems. </li></ul><ul><li>Standardized Registry Attributes: to ensure deterministic document searches. </li></ul>
    24. 24. XDS – Conclusion <ul><li>Foundation for EHR & Health IT Infrastructures </li></ul><ul><li>Effective contribution and access to shared documents across all types of health enterprises </li></ul><ul><li>Scalable, Flexible and Easy access </li></ul><ul><li>XDS to be one of the major highlights of 2005 Annual HIMSS Conference & Exhibition . Dallas, Tex., Feb. 13-17: </li></ul><ul><ul><li>used as a foundation for an on-site demonstration of interoperability in support of a National Health Information Networks. </li></ul></ul><ul><ul><li>Attendees at the conference will be able to create and share their own health records across vendor booths as well as in the ambulatory and acute care settings on the conference exhibit floor. </li></ul></ul>
    25. 25. How real is XDS ? <ul><li>Specification work since Nov 2003 </li></ul><ul><li>Under Public Comments June-July 2004 </li></ul><ul><ul><li>600 constructive comments received, </li></ul></ul><ul><li>Stable specification IHE TF Aug 15 th , 2004 </li></ul><ul><li>IHE Connectathon January 2005 (USA) </li></ul><ul><li>HIMSS Feb 2005 show-wide demonstration </li></ul><ul><li>IHE Connectathon April 2005 (Europe) </li></ul>
    26. 26. IHE, The practical solutions to the effective use of information exchange standards in healthcare
    27. 27. IHE Thank You !
    28. 28. More information…. <ul><li>IHE Web sites: </li></ul><ul><ul><ul><li> </li></ul></ul></ul><ul><ul><ul><li> </li></ul></ul></ul><ul><ul><ul><li> </li></ul></ul></ul><ul><ul><ul><li> htm . </li></ul></ul></ul><ul><li>Technical Frameworks: </li></ul><ul><ul><ul><li>ITI V1.0, RAD V5.5, LAB V1.0, CARD V1.0 </li></ul></ul></ul><ul><li>Technical Framework Supplements - Trial Implementation </li></ul><ul><ul><ul><li>May 2004: Radiology </li></ul></ul></ul><ul><ul><ul><li>August 2004: Cardiology, IT Infrastructure </li></ul></ul></ul><ul><ul><ul><li>December 2004: Laboratory </li></ul></ul></ul><ul><li>Non-Technical Brochures : </li></ul><ul><ul><ul><li>IHE Fact Sheet and FAQ </li></ul></ul></ul><ul><ul><ul><li>IHE Integration Profiles: Guidelines for Buyers </li></ul></ul></ul><ul><ul><ul><li>IHE Connect-a-thon Results </li></ul></ul></ul><ul><ul><ul><li>Vendor Products Integration Statements </li></ul></ul></ul>