Integrating the Healthcare Enterprise Patient Care Devices

Transcription

1 Integrating the Healthcare Enterprise Patient Care Devices

2 Anything can be integrated

3 Un-Interoperability: Highest Cause of Health IT project failures Base Standards The Hospital EHRs, CMMS, other ehealth Users IETF??!! IHTSDO

4 Interoperability: From a problem to a solution Base Standards Profile Development EHRs, CMMS, other ehealth Users IETF IHTSDO Specific Extensions

5 What is IHE? Integrating the Healthcare Enterprise (IHE) is an International Standards Profiling Organization Vision: To enable seamless and secure access to information whenever and wherever it is needed Mission: To improve healthcare by providing specifications, tools and services for interoperability

6 IHE Enables Interoperability by: Developing consensus-based, open source Technical Frameworks (specifications) and Integration Profiles, and making them available in the public domain Systems developed in accordance with IHE communicate with one another better, are easier to implement, and enable care providers to use information more effectively

7 Coordinate using established standards, CDA or FHIR (HL7), DICOM (within IHE Radiology and Pathology Profiles), LOINC & CDISC (for Laboratory Orders and Reporting), IEEE x (for mhealth, Medical and Personal Health Devices) to address clinical needs, in support of optimal, organized, and safe patient care Facilitating product conformance testing To obtain feedback and Demonstrate adherence to IHE specifications

8 IHE's Goal and Impact since 1997! Develop, demonstrate, and disseminate trusted, workflow-driven, standards-based interoperability solutions freely available in IHE Technical Frameworks and Integration Profiles IHE uses a globally trusted open ballot process for review

9 IHE's Goal and Impact since 1997! IHE specifications are vetted through the international ISO process Removed barriers to creating seamless and secure access to and exchange of - health data Reduces costs by eliminating or reducing the need for proprietary interfaces between systems

10 IHE Interoperability Domains 18 Years of Steady Evolution Worldwide! Automated, secure data capture and exchange Dentistry since 2010 Endoscopy since 2010 Surgery since 2012 Mobile devices Under way for 2015! Radiology since 1998 User driven & vendor neutral; based on HL7, ICD, and similar global stds. Cardiology since 2004 Pharmacy since 2009 Pathology since 2006 Laboratory since 2004 Eye Care since 2006 Quality Research & Public Health since 2006 (Healthcare) IT Infrastructure since 2003 Patient Care Devices since 2005 Radiation Oncology since 2004 Patient Care Coordination since 2004 Now including home care devices, telehealth, and PHRs Look carefully: MOST Domains capture device AND 10 workflow data; data transfer is accurate and near-

11 Patient Care Devices (PCD) PCD works with vendors, users and others to provide a common framework (Profile) that enables communication between medical devices and other clinical systems ACCE and AAMI are co-sponsors of the IHE Patient Care Device domain

12 Among other benefits, IHE-PCD profiles: Improve patient safety and clinical efficacy, Reduce healthcare delivery cost by improving Efficiency, Reliability, and Operational flexibility for healthcare providers,

13 What's new in PCD New Profiles: MEM-DMC (Device Management Communication) Enables communication between medical devices and a CMMS MEM-LS (Location Services) Enables an RTLS tag to send location to a CMMS 2015 Connectathon: Waveform passed 'live' from equipment to EMR

14 IHE NEEDS user help All Domains benefit from user input They ALL need HTM and clinician participation I Want You to Help

15 IHE PCD on Display HIMSS Interoperability showcase Las Vegas Feb 29-Mar 4 AAMI - PCD Interoperability Demonstration Tampa, FL June 3-6 Includes live RTLS, CMMS and equipment message passing.

16 Finally Contact me at: Thank You! Questions?