8ProcessProblem Identification: Clinicians and IT experts identify common integration problems in access to information, clinical workflow, administration and underlying infrastructure.Integration Profile Specification: Stakeholders select standards that address each identified integration need. The technical specifications for implementing these standards are documented in the IHE Technical Framework.Implementation and Testing: Vendors implement these profiles and test their systems with software tools and at a face-to-face Connectathon, where they test interoperability with other vendors’ systems.Integration Statements and RFPs: Vendors publish IHE Integration Statements to document the integration profiles supported by their products. Users can reference integration profiles in requests for proposals, simplifying the systems acquisition process.
14Over 100 vendors involved world-wide, 5 Technical Frameworks 39 Integration Profiles, Testing at ConnectathonsDemonstrations at major conferences world-wide16 Active national chapters on 4 continents
15IHE Patient Care Devices (PCD) HIMSS Survey IHE pre-2005 Annual Conference results:Survey of all IHE UsersOver 50% of those surveyed said patient care devices should be the next area developed for IHE *
16IHE 2005 Summer Survey Results Highest priority devices for integration are Vital Signs Monitors, Blood Gas Analyzers (POC), and Infusion PumpsHighest priority departments are ICU, Emergency, OR/Anesthesia, and Lab (POC)Highest technology priority is Enterprise Wide SharingHighest priority for clinical application is EHR or CIS integration followed by Improved Management and Decision Support
17IHE PCD Formed in September 2005 In September, 2005, the PCD gathered 60 vendors, purchasers, providers, and regulators in Washington D.C. for 2 days to explore the value propositions, explore the scope and mission of the domain, and begin the process of use case development.IHE 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.Current membership is 100+ and growing.
18IHE-PCD Domain Vision Statement The IHE Patient Care Device Domain (IHE PCD) is the nexus for vendors and providers to jointly define and demonstrate unambiguous interoperability specifications, called profiles, which are based on industry standards, and which can be brought to market.
19IHE-PCD MissionThe 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; andDemonstrate marketable solutions at public trade shows.
20Agenda Evolution of the IHE PCD Year 1 - Device Enterprise Communication ProfileYear 2 – Survey and Proposed Profile Development
21IHE Patient Care Devices (PCD) One Patient – Many Devices
22Product IHE Integration Statement IHE ProcessProduct IHE Integration StatementIHE Connect-a-thon ResultsIHE Connect-a-thonProductWith IHEIHE DemonstrationEasy toIntegrateProductsIHE Technical FrameworkStandardsIHE IntegrationProfiles BProfile AUser SiteRFP
25Device Enterprise Communication (DEC) Profile - Year 1
26DEC Profile Mapping Model ISO/IEEE Domain Information Model and Nomenclature mapped to HL7 Observation ReportISO/IEEE Data Types mapped to HL7 Data TypesMapping preserves measurement context for complex devices.
42Demographics: User Organization Types 77 Hospital Based Respondents* *26 of the 103 Non-Vendor Respondents do not work in hospitals
43Relationship of Clinical Engineering and IT at Respondents’ Hospitals 77 Hospital Based Respondents* *26 of the 103 Non-Vendor Respondents do not work in hospitals
44Importance of Interoperability to Hospital Based Respondents
45Survey Question: With respect to Medical Devices, how important is it for the following devices to become integrated under the IHE?Percent of respondents that consider it important= Vendors= Users
46Survey Question: Rate the importance to each department below in terms of the benefit from implementing IHEPercent of respondents that consider it important= Vendors= Users
47Survey Question: Which clinical applications should IHE target? Percent of respondents that consider it important= Vendors= Users
48Survey Question: Which technological areas are the most important for Patient Care Device integration?= Vendors= Users
49IHE Profile Proposal (Short) Proposed Profile: Patient Identification Proposal Editor: Ray ZambutoDate: February 16, 2006Version: 3Domain: Patient Care DevicesThe ProblemManual entry of patient identification to Patient Care Devices is inefficient and subject to error. Patient Identification is perhaps the most essential component of any interoperability and communication process, particularly when PCD data is exported to the enterprise. It is the basis for communication and control of any medical device, data analysis, reporting and record keeping. Automation of the entry of patient identification to Patient Care Devices has the potential for reducing errors, and is an essential component of any effort to increase safety, device and drug effectiveness, and efficiency.Key Use Case1) Setup of PCD. The caregiver connects the patient to a Patient Care Device. The patient is physically identified by some institutionally unique means of identification such as a wrist band barcode, RFID or other means which may or may not be solely considered as authoritative. The caregiver uses the information from the physical patient identification to obtain an authoritative electronic identifier which is associated with all data communicated from the PCD. The interaction may involve direct entry of the data to the device based on the physical identifier, a dialog between a PCD Manager and an authoritative source, and the use of more than one identifier. The end result is that data communicated from the PCD or PCD Manager contains an authoritative institutionally unique identifier.2) Disconnect PCD. The caregiver removes the PCD causing the data from that device to no longer be communicated to the enterprise.Standards & SystemsThis profile is intended for identification of patients by patient monitors, infusion pumps, ventilators, point of care glucometers etc..>ISO/IEEE 11073, HL7, IHE-ITI Patient Administration, IHE-ITI PDQDiscussionPatient identification is a fundamental requirement for any electronic communication from or to a medical device. As such, the IHE with its broad scope, full range of stakeholders, and present or future involvement in the development of interoperability specifications for the vast number of types of medical devices and information technology is the ideal (and only) logical place for this universally needed specification.
50Short Proposals Submitted for 2007 Profile NamePatient IDCross-Enterprise Sharing of Patient Care Device Data SynchronousReal-Time Clinical Data Management Storage and RetrievalIHE-ECG-WorkflowInfusion Pump Integration to Medication Administration ProcessPoC Real-Time PnP Device IntegrationSmall Data Element ExchangeHomeTelehealthAlarm InteroperabilityPCA Infusion SafetyPCD-02 Query
51Short Proposals Vetting 2007 vs reconsideration in 2008 Profile NamePatient IDCross-Enterprise Sharing of Patient Care Device Data-SynchronousReal-Time Clinical Data Management Storage and RetrievalIHE-ECG-WorkflowInfusion Pump Integration to Medication Administration ProcessPoC Real-Time PnP Device IntegrationSmall Data Element ExchangeHome TelehealthAlarm InteroperabilityPCA Infusion SafetyPCD-02 Query
52Short Proposals Setting Priorities Polling Results of Planning Committee Three Proposals for 2007* Profile NamePatient IDPCD-02 QueryPoCRealTimePnPDeviceIntegrationHomeTelehealthSmall Data Element ExchangePCA Infusion Safety123* Based on resource limitations. Additional work can be added if author/champion demonstrates sufficient additional resources
53SummaryFrom its inception in September 2005 the IHE PCD has grown to 100+ members representing vendors, purchasers, providers, and regulatory agencies.The Device Enterprise Communication (DEC) Framework for Trial Implementation published in August 2006.6 Vendors and 8 systems/applications tested at Connectathon 2007Process for developing Year 2 profiles is in progress.
54To Learn More This Week – Visit the IHE PCD in the HIMSS Interoperability Showcase
55Your Participation in IHE PCD is Encouraged PCD CoChairs:Todd CooperJack Harrington -Ray ZambutoOther Contacts:Manny FurstElliot Sloane