September, 2005What IHE Delivers 1 Todd Cooper Jack Harrington Elliot Sloane Raymond Zambuto Business Cases and Warp Speed Ahead to Patient Care Device.

Slides:



Advertisements
Similar presentations
Integrating the Healthcare Enterprise IHE Overview Keith W. Boone Interoperability Architect, GE Healthcare Co-chair, IHE Patient Care Coordination PC.
Advertisements

Polycom Unified Collaboration for IBM Lotus Sametime and IBM Lotus Notes January 2010.
How to Explain Device Reimbursement to your CEO The Medical Device Regulatory and Compliance Congress Barbara J. Calvert March 29, 2006.
Todd Cooper President and Founder, Breakthrough Solutions Inc. Co-Chair of the American College of Clinical Engineering (ACCE) IHE-PCD.
September, 2005What IHE Delivers 1 Key Image Notes Evidence Documents Simple Image & Numeric Report Access to Radiology Information IHE Vendors Workshop.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing for MPI (PIX) Profile Mike Henderson.
September, 2005What IHE Delivers 1 Todd Cooper Co-Chair, ACCE IHE Patient Care Devices Domain Co-Chair, ACCE IHE Patient.
September, 2005What IHE Delivers 1 IHE-Cardiology Technical Committee EP Key Data Elements February 21, 2011 Bryan Jennings - Medical Micrographics Nick.
September, 2005What IHE Delivers 1 Kevin ODonnell, Toshiba Medical Systems Co-chair IHE Radiology Planning Cmte IHE Radiology Update.
IHE Workshop – June 2006What IHE Delivers 1 Cynthia A. Levy Cedara Software IHE Technical Committee Import Reconciliation Workflow Profile.
September, 2005What IHE Delivers VA Success Story – Image Acquisition using IHE Scheduled Workflow June 6~7, 2006 Peter Kuzmak, Andrew Casertano, and.
IHE PCD 2008 Survey PCD Face to Face Meetings October, 2008.
September, 2005What IHE Delivers 1 Purchasing & Integrating Radiology Systems Using IHE: A Tutorial & A Real-world Case Kevin ODonnell, Cor Loef, John.
IHE Patient Care Devices Highlights August 31, 2007.
September, 2005What IHE Delivers 1 Todd Cooper, Co-Chair IHE PCD Andrea Poli, University of Trieste, Italy IHE Patient Care Device Domain IHE Europe 2006.
Integrating the Healthcare Enterprise The Basics of IHE: Concepts and Process Associate Professor of Radiology Chief, Imaging Informatics Northwestern.
Raymond Peter Zambuto, CCE, FASHE, FHIMSS, FACCE President, Technology in Medicine, Inc. Co-Chair IHE Patient Care Devices Domain Emanuel Furst, PhD, CCE.
Patient Care Device Interoperability Standards
Pathfinding Session: Device Integration IHE North America Webinar Series 2008 Todd Cooper Patient Care Device Domain Breakthrough Solutions Foundry, Inc.
September, 2005What IHE Delivers 1 Lloyd Hildebrand, M.D., American Academy of Ophthalmology, Medical Information Technology Committee Chair IHE Eye Care.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise IHE Tools for Users and Integrators: Connectathon, Integration Statements.
September, 2005What IHE Delivers 1 Presenters: Keith W. Boone, John Donnelly, Larry McKnight, Dan Russler IHE Patient Care Coordination.
Interoperability 101 Bridget A. Moorman, CCE Technical Manager Industry Advisory Board Renewing Health The Continua Alliance.
September, 2005What IHE Delivers 1 IHE Quality Domain February 26, 2008.
Connectathon Overview IHE Workshop 2007 Chris Carr RSNA.
Patient Care Device Domain Overview. The Patient Care Device Domain PCD History Established in 2005 when the charter was awarded to the ACCE Jointly sponsored.
September, 2005What IHE Delivers 1 Promoting IHE in the Interoperability Showecase: Demonstration and Education Plans for WHIT 2007 IHE Participant Workshop.
June 28-29, 2005IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Cross-enterprise Document Sharing for Imaging (XDS-I) Rita Noumeir.
September, 2005What IHE Delivers How to purchase eye care systems using IHE IHE Showcase at the AAO Conference November 2006 Andrew Casertano, Peter Kuzmak,
September, 2005What IHE Delivers 1 Joe Auriemma Siemens Medical Solutions, Health Services Senior Director, Integration Engineering Siemens Medical Solutions.
September, 2005What IHE Delivers Andrew M. Keller, MD, FACC, FASE Chief of Cardiology, Danbury Hospital Danbury, CT, USA Integrating the Healthcare Enterprise.
September, 2005What IHE Delivers Andrew M. Keller, MD, FACC, FASE, FACP Chief of Cardiology, Danbury Hospital Danbury, CT, USA Integrating the Healthcare.
September, 2005What IHE Delivers Andrew M. Keller, MD, FACC, FACP, FASE Chief of Cardiology, Danbury Hospital Danbury, CT, USA Integrating the Healthcare.
SOA for EGovernment 1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath COMCARE Michael Daconta Oberon Associates.
CCHSA Accreditation: New Standards for Managing Medications
Patient Care Device Domain Update Todd Cooper President, Breakthrough Solutions Foundry, Inc. Ray Zambuto President, Technology in Medicine, Inc. Jack.
Strategic Meetings Management 101
How to commence the IT Modernization Process?
Supporting National e-Health Roadmaps WHO-ITU-WB joint effort WSIS C7 e-Health Facilitation Meeting 13 th May 2010 Hani Eskandar ICT Applications, ITU.
Interoperability: Progress through Unprecedented Collaboration Charlene Underwood, MBA Director, Government and Industry Affairs, Siemens Chairperson,
HIMAA Symposium 2008, Canberra 1 Integrating the Healthcare Enterprise Klaus Veil Manager - IHE Connectathon and Interoperability Showcase 2008 Chairman.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
DICOM and Integrating the Healthcare Enterprise: Five years of cooperation and mutual influence Charles Parisot Chair, NEMA Committee for advancement of.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Primary Goal: To demonstrate the ability to provide efficient and accurate transitional care, from the hospital OR suite, to the radiology department and.
September, 2005What IHE Delivers Introduction to IHE ACCA IHE Workshop 2007 Jon Elion MD, FACC Associate Professor of Medicine, Brown University Co-Chair,
September, 2005What IHE Delivers IHE Eye Care Integration Profiles Andrew Casertano Department of Veterans Affairs.
Sandy Lum University of Toronto Candidate MHSc in Clinical Engineering The Totally Integrated Electronic Patient Record (EPR)
September, 2005What IHE Delivers 1 IHE Sponsors and Committee Members Welcome to the Interoperability Showcase.
1 Integrating the Healthcare Enterprise Patient Demographics Query IHE IT Technical and Planning Committee June 15 th – July 15 th Public Comment.
ONC FACA HIT Standards Committee Clinical Operations Workgroup Hearing on Barriers & Enablers for Medical Device Interoperability March 28, 2011 ~ Washington,
IHE IT Infrastructure: The Value Proposition HIMSS 2003 Joining the IHE in its New Enterprise Initiatives.
Us Case 5 ICU Event with Pharmacy and Pt Monitoring and Follow-up Care by PCP Care Theme: Transitions of Care, Medical Device Integration Use Case 15 Interoperability.
IHE-Europe – Use Case Based Approach to eHealth Interoperability Peter Künecke, SIEMENS Medical Solutions IHE-Europe „vendor“ co-chair Integrating the.
IHE Marketing and Implementation Resources IHE Marketing and Implementation Resources Chris Carr Director of Informatics, Radiological Society of North.
June 2006What IHE Delivers 1 IHE Workshop Changing the Way Healthcare Connects Flora Lum, M.D. Director, Quality of Care and Knowledge Base Development.
Unit 8.2: Effective Implementation Planning HIT Implementation Planning for Quality and Safety Component 12/Unit 81 Health IT Workforce Curriculum Version.
IHE PCD MEM-DMC CMMS & RTLS User Perspective Monroe Pattillo Practical Health Interoperability, LLC 6/21/2013.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
IHE Update DICOM Committee Taipei, April IHE Global Update IHE Technical Framework for Year 5 V5.5 issued for public comment in February Trial.
PCD User Handbook 2010 Purpose The Handbook is designed to help healthcare professionals implement IHE on a new clinical system purchase or upgrade an.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
September, 2005What IHE Delivers Integrating the Healthcare Enterprise- Patient Care Device Domain (IHE-PCD) Authors : Jack Harrington, Ray Zambuto, Todd.
Author : Elliot B. Sloane, Ph.D. American College of Clinical Engineering, President Villanova University Department of Decision.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise IHE Conformance: Connectathons, Integration Statements & RFPs Kevin.
Jonathan L. Elion MD, FACC Co-Chair, IHE Cardiology Planning Committee The Basics of IHE: Concepts and Process.
Raymond Peter Zambuto ACCE Sept, 2005 IHE Patient Care Devices Domain Kick-off Meeting Stakeholders and Business Value Propositions.
IHE Eye Care Process and Timeline
Unit 5 Systems Integration and Interoperability
Presentation transcript:

September, 2005What IHE Delivers 1 Todd Cooper Jack Harrington Elliot Sloane Raymond Zambuto Business Cases and Warp Speed Ahead to Patient Care Device Interoperability!

2 IHE Patient Care Devices (PCD) Providers and vendors working together to deliver interoperable health information systems within and between enterprises and settings Helping to fulfill the general IHE Vision:

3 IHE Patient Care Devices (PCD) In June, 2005, The American College of Clinical Engineering (ACCE) was appointed the Domain Sponsor for Patient Care Devices by IHEs principal sponsors, ACC, HIMSS, and RSNA. Clinical Engineer A Clinical Engineer is a professional who supports and advances patient care by applying engineering and managerial skills to healthcare technology. Founded in 1991, ACCE is the professional college of Clinical Engineers throughout the US. (

4 IHE Patient Care Devices (PCD) Why Patient Care Devices? For every connected IT Device in the hospital, there are 4 Patient Care Devices that are not connected For every connected IT Device in the hospital, there are 4 Patient Care Devices that are not connected There are over 1500 Patient Care Device manufacturers and over 3500 Make-Model combinations There are over 1500 Patient Care Device manufacturers and over 3500 Make-Model combinations The typical 200 bed hospital contains 1,000s of Patient Care Devices The typical 200 bed hospital contains 1,000s of Patient Care Devices …that are constantly changing with updated/upgraded technology … and interoperability too?!

5 IHE Patient Care Devices (PCD) One Patient – Many Devices

6 IHE Patient Care Devices (PCD) REALITY CHECK – Patient Care Devices are quite unique … Many devices are used in multiple clinical contexts, with acquired data having different implications depending upon the clinical setting. 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 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 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). Many devices provide data that should be automatically and accurately incorporated directly into the information stream that feeds the emerging Electronic Health Record (EHR).

7 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! So, in Summer 2005, HIMSS conducted a supplemental Patient Care Devices survey, which allowed us to drill down to the detailed issues and priorities… So, in Summer 2005, HIMSS conducted a supplemental Patient Care Devices survey, which allowed us to drill down to the detailed issues and priorities… * IHE-Europe survey placed Medical Devices behind Pharmacy & Pathology Survey of all IHE UsersSurvey of all IHE Users Over 50% of those surveyed said patient care devices should be the next area developed for IHE *Over 50% of those surveyed said patient care devices should be the next area developed for IHE *

8 IHE Patient Care Devices (PCD) 2005 Summer Survey Results: Highest priority devices for integration are Vital Signs Monitors, Blood Gas Analyzers (POC), and Infusion Pumps Highest priority devices for integration are Vital Signs Monitors, Blood Gas Analyzers (POC), and Infusion Pumps Highest priority departments are ICU, Emergency, OR/Anesthesia, and Lab (POC) Highest priority departments are ICU, Emergency, OR/Anesthesia, and Lab (POC) Highest technology priority is Enterprise Wide Sharing Highest technology priority is Enterprise Wide Sharing Highest priority for clinical application is EHR or CIS integration followed by Improved Management and Decision Support Highest priority for clinical application is EHR or CIS integration followed by Improved Management and Decision Support Highest perceived barrier is Lack of Standards. – Fear of Litigation not a concern Highest perceived barrier is Lack of Standards. – Fear of Litigation not a concern Users are willing, on average, to pay a premium to achieve IHE compliance …but may expect lower cost! Users are willing, on average, to pay a premium to achieve IHE compliance …but may expect lower cost!

9 IHE Patient Care Devices (PCD) Key Benefits of PCD Interoperability: Heterogeneity – Multiple manufacturers + multiple device modalities coexisting over a shared infrastructure Heterogeneity – Multiple manufacturers + multiple device modalities coexisting over a shared infrastructure Semantic Interoperability ( comparability) – shared terminology and data models, interpret data based on the clinical context, compare information from different healthcare facilities, and interrogate systems across enterprises and regions. Semantic Interoperability ( comparability) – shared terminology and data models, 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). Real-Time Availability – ability to provide data in a time frame appropriate to the physiologic function being measured, displayed or affected (controlled).

10 IHE Patient Care Devices (PCD) SO, WHAT IS HAPPENING IN THIS DOMAIN? 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.

11 IHE Patient Care Devices (PCD) The PCD Business Case What outcomes of IHE-PCD Domain will create real, tangible value for the participants (i.e., What is the Value Proposition or, Why should we do this, and why now?) Nothing durable can be accomplished with a project like this UNLESS there are clear rewards for all stakeholders (economic, safety, quality, etc.). Nothing durable can be accomplished with a project like this UNLESS there are clear rewards for all stakeholders (economic, safety, quality, etc.).

12 IHE Patient Care Devices (PCD) Key Stakeholders with Business Cases that are driving the PCD Stakeholders presently fall into four general categories Stakeholders presently fall into four general categories Vendors who sell devices or services Vendors who sell devices or services Purchasers who buy devices - Providers (Clinicians) who use devices Purchasers who buy devices - Providers (Clinicians) who use devices Regulators and Government who represent the public good Regulators and Government who represent the public good

13 IHE Patient Care Devices (PCD) Business Case for the Vendor as a stakeholder Value lies in the ability to attract, retain, or deepen a customer relationship For example IHE PCD will enable new market development would be a value proposition

14 IHE Patient Care Devices (PCD) Vendor Value Propositions (e.g., ROI and other motivations): Simplify product development process Simplify product development process Spend time innovating rather than doing infrastucture work Spend time innovating rather than doing infrastucture work Facilitate clinical decision support - innovation - added functionaliity Facilitate clinical decision support - innovation - added functionaliity Reduce regulatory impact/work Reduce regulatory impact/work Improve patient safety - reduce liability - make operations easier - device aware Improve patient safety - reduce liability - make operations easier - device aware

15 IHE Patient Care Devices (PCD) Business Case for the Purchaser/Provider Stakeholders Value lies in simplifying quality buying decision criteria For example IHE PCDD will reduce the complexity of the purchase would be a value proposition Provider Stakeholders Purchaser Stakeholders Value lies in the benefit you derive For example IHE PCDD will simplify workflow would be a value proposition

16 IHE Patient Care Devices (PCD) Value Propositions for Purchaser and Provider: Integrity of data – automatic population of all information systems – reducing medical errors Integrity of data – automatic population of all information systems – reducing medical errors Automated systems saves time for clinicians Automated systems saves time for clinicians Improves agility of enterprises to meet varied patient loads Improves agility of enterprises to meet varied patient loads Improved life-cycle cost of ownership Improved life-cycle cost of ownership Automates clinical data capture for EHR Automates clinical data capture for EHR Access to patient data across devices and systems so custom communication interfaces can be eliminated. Allows for best of breed Access to patient data across devices and systems so custom communication interfaces can be eliminated. Allows for best of breed

17 IHE Patient Care Devices (PCD) Value Proposition for Government and Regulatory Stakeholders Value lies in easing regulators tasks by industry adoption and implementation of uniform specifications. Value lies in easing regulators tasks by industry adoption and implementation of uniform specifications. For example one Business Case statement for government and regulatory stakeholders is: IHE PCDD can simplify the approval process for medical devices and related clinical information systems. For example one Business Case statement for government and regulatory stakeholders is: IHE PCDD can simplify the approval process for medical devices and related clinical information systems. IHE-PCD accelerates the fulfillment of key clinical requirements for Efficacy, Efficiency, and Safety in the emerging Electronic Health Record programs that have been mandated by President Bush and Health and Human Services leadership. IHE-PCD accelerates the fulfillment of key clinical requirements for Efficacy, Efficiency, and Safety in the emerging Electronic Health Record programs that have been mandated by President Bush and Health and Human Services leadership.

18 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. 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.

19 IHE Patient Care Devices (PCD) IHE-PCD Domain Vision Statement The IHE Patient Care Devices 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. IHE-PCD profiles: 1. improve patient safety and clinical efficacy, 1. improve patient safety and clinical efficacy, 2. optimize healthcare delivery cost by improving 2. optimize healthcare delivery cost by improving efficiency, reliability, and operational flexibility for efficiency, reliability, and operational flexibility for healthcare providers, healthcare providers, 3. enable innovative patient care capabilities, and 3. enable innovative patient care capabilities, and 4. expand the international marketplace for patient care 4. expand the international marketplace for patient care device vendors. device vendors.

20 IHE Patient Care Devices (PCD) IHE-PCD Mission The IHE Patient Care Devices Domain will apply the proven, Use Case driven IHE processes to: 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; Deliver the technical framework for the IHE-PCD domain profiles; Validate IHE-PCD profile implementations via Connectathons; and Validate IHE-PCD profile implementations via Connectathons; and Demonstrate marketable solutions at public trade shows. Demonstrate marketable solutions at public trade shows.

21 IHE Patient Care Devices (PCD) Examples of emerging IHE-PCD Work flows: Enterprise sharing of Patient Care Data Enterprise sharing of Patient Care Data * Patient & Device ID Binding to Device Patient & Device ID Binding to Device * Real-time data archiving and communication Real-time data archiving and communication PCD Alarm Management PCD Alarm Management Drug Administration Drug Administration Hospital Bed–Blood Pressure Coordination Hospital Bed–Blood Pressure Coordination Mobile, enterprise-wide, reliable vital signs monitoring Mobile, enterprise-wide, reliable vital signs monitoring … many more! … many more! Initial device classes – vital sign monitors, infusion pumps and ventilators * Key Objectives for 2006/2007

Development Schedule: 2006 Development Schedule: Planning Committee decision:mid-January Planning Committee decision:mid-January Issue Public Comment version: June 2006 Issue Public Comment version: June 2006 Public Comment Due:July 2006 Public Comment Due:July 2006 Issue Trial Implementation version: August 2006 Issue Trial Implementation version: August 2006 IHE Connectathon: January 2007 IHE Connectathon: January 2007 HIMSS Demo: February 2007 HIMSS Demo: February 2007 IHE Patient Care Devices (PCD)

23 IHE Patient Care Devices (PCD) Come and join the IHE-PCD Domain Team - see or any of the following PCD leaders: Todd Cooper Todd Cooper Emanuel (Manny) Furst Emanuel (Manny) Furst Jack Harrington Jack Harrington Elliot Sloane Elliot Sloane Ray Zambuto Ray Zambuto … or visit us at … or visit us at

24 … Patient Care Devices!