Presentation on theme: "Patient Care Device Domain Update Todd Cooper President, Breakthrough Solutions Foundry, Inc. Ray Zambuto President, Technology in Medicine, Inc. Jack."— Presentation transcript:
Patient Care Device Domain Update Todd Cooper President, Breakthrough Solutions Foundry, Inc. Ray Zambuto President, Technology in Medicine, Inc. Jack Harrington Co-Chair, IHE Patient Care Device Domain Ken Fuchs Director of Systems and Connectivity Engineering, Draeger Medical Systems, Inc.
IHE Patient Care Devices (PCD) Providers and vendors working together to deliver interoperable health information systems within and between enterprises and settings The PCD, helping to fulfill the general IHE Vision:
IHE Patient Care Devices (PCD) Why Patient Care Devices? There are over 1500 Patient Care Device manufacturers and over 3500 Make-Model combinationsThere are over 1500 Patient Care Device manufacturers and over 3500 Make-Model combinations The typical 200 bed hospital contains 1,000s of Patient Care DevicesThe typical 200 bed hospital contains 1,000s of Patient Care Devices …that are constantly changing with updated/upgraded technology … and interoperability too?!…that are constantly changing with updated/upgraded technology … and interoperability too?! For every connected IT Device in the hospital, there are 4 Patient Care Devices that are not connectedFor every connected IT Device in the hospital, there are 4 Patient Care Devices that are not connected
IHE Patient Care Devices (PCD) Patient Care Devices are unique … Many devices are used in multiple clinical contexts, with acquired data having different implications depending upon the clinical setting. Many devices provide signals or critical alarms that have direct significance to patient safety and well being in real- time, and should be accorded appropriate priority in the system. Many devices are portable, meaning that connectivity must include wireless portions, direct network connections, and Internet links, all with hacker and virus risks, too. Many devices provide data that should be automatically and accurately incorporated directly into the information stream that feeds the emerging Electronic Health Record (EHR).
The Patient Care Device Domain The PCD Established in 2005 when the charter was awarded to the ACCE Jointly sponsored by ACCE and HIMSS as of July 1, 2006 Technical Framework 2006-7 developed to communicate patient data (asynchronous) Successful demonstration at the 2007 & 2008 Connectathons and HIMSS Interoperability Showcases
IHE Patient Care Devices (PCD) HIMSS Survey IHE pre-2005 Annual Conference results: Further, 56% said theyd pay more for IHE-compliant products!Further, 56% said theyd pay more for IHE-compliant products! Survey of all IHE Users Over 50% of those surveyed said patient care devices should be the next area developed for IHE *
IHE Patient Care Devices (PCD) Key Benefits of PCD Interoperability Heterogeneity – Multiple manufacturers + multiple device modalities coexisting over a shared infrastructure Semantic Interoperability ( comparability) – shared terminology and data models permit users to interpret data based on the clinical context, compare information from different healthcare facilities, and interrogate systems across enterprises and regions. Real-Time Availability – ability to provide data in a time frame appropriate to the physiologic function being measured, displayed or affected (controlled).
Why Do I Care About the IHE PCD? Significance Clinical implications –Patient safety –Enterprise wide access to the patients data –Quality of care –Ability to implement best of breed for your applications –Workflow improvements
Why Do I Care About the IHE PCD? Significance Technical implications –CE and IT must collaborate on selection, specification, support of these systems –New knowledge and skills are required Financial implications –Rapid changes in technology increase risk –Interoperability reduces risk –Interoperability improves efficiency
Examples of Purchaser and User Value Propositions (i.e, ROI and other motivations) Automatic population of all information systems – reducing medical errors - integrity of data Automated systems - saves time for clinicians Defined and easily accessible - audit trails Eases integration of multiple modalities into a single system; provides one consistent view of patient data Facilitates intelligent systems to support clinical reasoning International standardization of systems so that international outcomes research can be accomplished Common and safe user authentication Access to patient data across devices and systems so custom communication interfaces can be eliminated. Allows best of breed selection for your application Efficiency of care, testing and training - Reduces redundancy
User/Provider/Purchaser Benefit ExamplesSignificance Improves agility of enterprises to meet varied patient loads Improved life-cycle cost of ownership –Facilitates heterogeneous brand and model deployment –May allow use of technologies over longer periods of time, reducing the obsolescence effect Vendor-provided IHE-PCD conformance statements will ease selection decisions and reduce business risk Automates clinical data capture for EHR
IHE Patient Care Devices (PCD) IHE-PCD Charter The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated patient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging and laboratory. The Patient Care Devices Domain is concerned with Use Cases in which at least one actor is a regulated patient care device. The PCD coordinates with other IHE clinical specialty based domains such as medical imaging and laboratory.
IHE Patient Care Devices (PCD) IHE-PCD Mission The IHE Patient Care Devices Domain will apply the proven, Use Case driven IHE processes to: Deliver the technical framework for the IHE-PCD domain profiles; Validate IHE-PCD profile implementations via Connectathons; and Demonstrate marketable solutions at public trade shows.
IHE PCD in the HIMSS 2007 Interoperability Showcase
IHE Patient Care Devices (PCD) Examples of emerging IHE-PCD Work flows Enterprise sharing of Patient Care Data* Patient & Device ID Binding* Point of Care Plug and Play* (multiyear effort) Subscribe to Patient Data Rosetta Stone Terminology Project PCD Alarm Communication Management Real-time data archiving and communication Infusion Pump Integration - Drug Administration Hospital Bed–Blood Pressure Coordination Mobile, enterprise-wide, reliable vital signs monitoring … many more! Initial device classes… vital sign monitors, bedside monitors, infusion pumps and ventilators * Key Objectives for 2007/2008
Device Enterprise Communication (DEC) Profile - Year 1
DEC Profile Mapping Model ISO/IEEE 11073 Domain Information Model and Nomenclature mapped to HL7 (v2.5) Observation Report ISO/IEEE 11073 Data Types mapped to HL7 Data Types Mapping preserves measurement context for complex devices.
Process for Year 2 Year 2 2006 Survey Call for Short Proposals Vetting by Planning and Technical Committees Setting of Priorities Development of the T/F Supplements Testing of new profiles @ Connectathon TODAY!!!Demonstration at HIMSS 2008 – TODAY!!!
IHE-PCD Survey Summer- Winter 2008 2008 Survey – We want your input! Survey Managed by HIMSS Analytics Open Solicitation to HIMSS, ACCE, AdvaMed, Anesthesia Patient Safety Foundation, ECRI, … Survey URL: http://surveys.himss.org/himss/Surveys/ TakeSurvey.aspx?surveyid=1456
What Can You Do? To Define the Future Become a member of a Domains Planning or Technical Committees –Help establish priorities – what the domain will work on –Help define profiles – clinical, IT requirements –Provide the business case to encourage developments Whats required of you? Poll the room--- Questions, etc.
PCD Contacts PCD CoChairs: – Todd Cooper email@example.com@ieee.org – Ken Fuchsken.firstname.lastname@example.org@draeger.com – Jack Harrington email@example.com@philips.com – Ray Zambuto firstname.lastname@example.org@techmed.lincfs.com PCD Technical Project Manager: – Manny Furstefurst@email@example.com IHE (International) Strategic Development Committee Co- Chair: – Elliot Sloaneebsloane@firstname.lastname@example.org