IHE Workshop – June 2007What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.

Slides:



Advertisements
Similar presentations
Pathfinding Session: Cardiology IHE North America Webinar Series 2008 Harry Solomon IHE International Board GE Healthcare.
Advertisements

Profile Proposals IHE Cardiology Proposals Image Enabled Office –Grouping of actors in top half of Scheduled Workflow into Practice Management.
IHE Workshop – June 2006What IHE Delivers 1 Cynthia A. Levy Cedara Software IHE Technical Committee Import Reconciliation Workflow Profile.
IHE Cardiology Implantable Cardiac Device Interrogation (ICDI) Profile Nicholas Steblay 2/3/2006.
Buzzword Bingo.
PRESENTATION TITLE Name of Presenter Company Affiliation IHE Affiliation.
IHE Electrophysiology Remote Implantable Rhythm Control Device Interrogation Eliot L. Ostrow November 2005 Rev 0.0.
IHE Workshop – Feb 2007 Tim Becker, PhD Univ- Hospital Schleswig-Holstein, Campus Kiel Implantable Device Cardiac Observations (IDCO) Profile.
IHE Radiology Integration Profiles: ▪ Post-Processing Workflow ▪ Reporting Workflow IHE Educational Workshop – June 11-13, 2007 Nikolaus Wirsz, PhD Manager.
IHE Cardiology Cardiac electrophysiology admission discharge summary for the referring cardiologist Nicholas Steblay 11/7/
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
DICOM and Integrating the Healthcare Enterprise: Five years of cooperation and mutual influence Charles Parisot Chair, NEMA Committee for advancement of.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Device and EMR interoperability (IDCO). Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home.
Rev 2.11 IHE Cardiology 5-year Roadmap Roadmap subcommittee: Bill Weintraub Andrew Kenneth
IHE Cardiology Domain Overview Harry Solomon 27-July-2010.
Joy Hamerman Matsumoto.  St Jude Medical Cardiac Rhythm Management Division manufactures implantable cardiac devices ◦ Pacemakers ◦ Implanted defibrillators.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
September, 2005What IHE Delivers IHE Eye Care Integration Profiles Andrew Casertano Department of Veterans Affairs.
1 HL7 Working Group Session May 3-7, 2004 San Antonio, TX Standards for Implantable Devices - Cardiac.
1 Charles Parisot, GE Healthcare IHE IT Infrastructure Planning Committee Co-chair IHE Update to DICOM.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Audit Trail and Node Authentication Robert Horn Agfa Healthcare.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
IHE Cardiology Office Based Pacemaker and ICD Follow-up Dave Shute November 13,2005 Rev 0.1.
September, 2005What IHE Delivers 1 Presenters: Keith W. Boone, John Donnelly, Larry McKnight, Dan Russler IHE Patient Care Coordination.
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe December 6, 2010.
Integration Profiles - Overview Integrating the Healthcare Enterprise G. Claeys Agfa Healthcare R&D, Technology Manager Vendor co-chair IHE Europe Courtesy.
September, 2005What IHE Delivers 1 An Overview of the IHE IT Infrastructure IHE Vendors Workshop 2006 IHE IT Infrastructure Education Glen F. Marshall.
IHE Radiology –2007What IHE Delivers 1 Ellie Avraham IHE Technical Committee May 23, 2007 Cross Domain Review Laboratory.
1 Integrating the Healthcare Enterprise Audit Trail and Node Authentication Profile IHE IT Technical and Planning Committee June 15 th – July 15 th 2004.
September, 2005What IHE Delivers 1 Cross-Enterprise Document Point-to-point Interchange (XDP) IHE Vendors Workshop 2006 IHE IT Infrastructure Education.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Overview of IHE IT Infrastructure Patient Synchronized Applications.
Sharing Value Sets (SVS Profile) Ana Estelrich GIP-DMP.
Document Digital Signature (DSG) Document Digital Signature (DSG) Gila Pyke / Lori Reed-Fourquet Smart Systems for Health Agency / Identrus IHE ITI Technical.
IHE Workshop – June 2006What IHE Delivers 1 Import Reconciliation Workflow Profile IHE North America Webinar Series 2008 Chris Lindop Radiology GE Healthcare.
February 8, 2005IHE Europe Educational Event 1 Integrating the Healthcare Enterprise Basic Security Robert Horn Agfa Healthcare.
IHE Cardiology Image Enabled Office Harry Solomon Based on IEO draft 19 ftp://ftp.ihe.net/Cardio/Year /Technical_Committee/Supplements/IEO/
IHE Profile – SOA Analysis: In Progress Update Brian McIndoe January 18, 2011.
September, 2005Cardio - June 2007 IHE for Regional Health Information Networks Cardiology Uses.
IHE ITI – Dec 2006What IHE Delivers 1 Nicholas Steblay Implantable Device Cardiac Observations (IDCO) Profile.
September, 2005What IHE Delivers 1 Presenter Maria Rudolph, American College of Cardiology Staff IHE Cardiology.
Cross-Enterprise User Authentication John F. Moehrke GE Healthcare IT Infrastructure Technical Committee.
IHE Cardiology – Technical Committee Telephone Conference Sept. 14, 2009 IHE Cardiology – Technical Committee Telephone Conference Sept. 14, 2009 Antje.
IHE Update IT Infrastructure, Radiology, Laboratory and Cardiology IHE Update to December 2003 DICOM Committee Charles Parisot, GE Medical Systems Information.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Patient Identifier Cross-referencing Charles PARISOT GE Healthcare.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Access to Radiology Information Cor Loef Co-chair IHE Radiology Technical.
IHE Cardiology Image Enabled Office Harry Solomon Based on IEO draft 12.
September, 2005What IHE Delivers 1 Cross-Enterprise Document Point-to-point Interchange (XDM) IHE Vendors Workshop 2006 IHE IT Infrastructure Education.
Jonathan L. Elion MD, FACC Co-Chair, IHE Cardiology Planning Committee Future Integration Profiles (Cardiology)
IHE Workshop – June 2006What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile.
IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Technical Committee co-chair.
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 - towards the electronic patient record The IHE Cardiology Technical Framework Current.
IHE Cardiology Displayable Report (DRPT) Profile Harry Solomon, Tom Dolan February 16, 2005 Rev 0.3.
IHE Workshop – February 2007 What IHE Delivers 1 Credits for many slides to: Cynthia A. Levy, Cedara Software IHE Technical Committee Import Reconciliation.
September, 2005What IHE Delivers 1 Patient Index and Demographic Implementation Strategies IHE Vendors Workshop 2006 IHE IT Infrastructure Education Rick.
September, 2005What IHE Delivers IHE Cardiology Profiles for Electronic Healthcare Record systems ITI Meeting Dec 5 th, 2006.
Integrating the Healthcare Enterprise The IHE Process: Developing Standards-based Solutions Kevin O’Donnell Co-chair, IHE Radiology Planning Committee.
Integrating the Healthcare Enterprise Retrieve Information for Display (RID) Integration Profile Ellie Avraham Kodak Health Imaging IHE IT Infrastructure.
Tung Tran, Ph.D. What is the EMR? Computerized legal medical record created by healthcare organizations Enables storage and retrieval of patient information.
June, 2006What IHE Delivers 1 IHE Workshop Changing the Way Healthcare Connects Donald Van Syckle DVS Consulting, Inc. Jim Riggi, CTO Medflow, Inc.
Patient Demographics Query (PDQ) Didi Davis Director, Eclipsys Corporation Co-Chair, IT Infrastructure Planning Committee.
Cross Enterprise TeleHomeMonitoring Workflow Definition (XTHM-WD)
IT Infrastructure Plans
Patient Identifier Cross-Referencing for MPI (PIX)
IHE Eye Care “Charge Posting”
IHE Workshop: Displayable Reports (DRPT)
Presentation transcript:

IHE Workshop – June 2007What IHE Delivers 1 Nicholas Steblay Boston Scientific Implantable Device Cardiac Observations (IDCO) Profile

IHE Workshop – June Implantable Cardiac Devices Pacemakers – therapy for heart rate problems Defibrillators – therapy for life threatening heart rhythms Cardiac Resynchronization – therapy for congestive heart failure

IHE Workshop – June Device Interrogations Implant Clinic Home The act of retrieving data from implanted cardiac devices. Done at implant or during patient follow-ups. Information includes Patient and Device Observations, and Therapy Settings

IHE Workshop – June Clinical Process – Device Follow-up 3.1 Schedule Follow- ups 3.2 Exam Patient & Interrogate Device 3.3 Analyze Information   Schedule In Clinic Follow-ups   Schedule Remote Follow-ups   Exam Patient (Physical & Lab Tests If Needed)   Interrogate Device In Clinic   Interrogate Device Remote   Review Exam and Interrogation Information   Determine New or Adjusted Therapies 3.4 Adjust Therapy and Configure Device   Pharmalogical   Configure and Test Pulse Generator 3.5 Update Medical Record   Record and Follow-up Process and Outcomes   Record Pertinent Data Concerning Device and Pharmalogical   Sign-Off Procedure   Create Follow- up Summary (Referral Letter) for Following Physician 1.0 Diagnosis 2.0 Implant 3.0 Device Follow-up 4.0 Patient Follow-up 5.0 Acute Events Explants Level 0 Level 1 Level 2

IHE Workshop – June Implantable Cardiac Device Follow-up Problems and Opportunities Electrophysiologists follow patients with implantable cardiac devices from multiple vendors For each patient follow-up information that is stored in the implantable device is electronically collected by an “interrogating” device  In-Clinic – Programmer  Remote – Communicator / Data Collector Each “interrogating” device is vendor proprietary The follow-ups can occur in-clinic or remotely in the home healthcare environment Access to follow-up information often requires clinicians to use multiple vendor specific systems and interfaces, complicating efficiency and quality of workflows Aggregation of data into a central EMR or device clinic management systems requires manual and paper processes

IHE Workshop – June IDCO Value Proposition Enable management of follow-up information in a central system such as an Device Clinic Management System or EMR Improve efficiency and quality of related clinical processes  Single point of access for information  Automation of current manual processes for data collection, aggregation and analysis  Standardization of workflow processes  Enabling of analytics

IHE Workshop – June IDCO Profile Approach Rally domain vendors around a profile that defines a standard approach to integrating implantable cardiac device follow-up information into a receiving clinic system Enable the needed systems integration by profiling the use of standard, domain applicable messaging protocols, structures and data semantics  HL7 v2.5 ORU message  ISO/IEEE Point of Care Medical Device Communication Standards nomenclature Define actors, transactions and constraints consistent with existing and evolving IHE profiles and contexts  Align with EP Workflow and other related profiles

IHE Workshop – June IDCO Profile Use Cases In-Clinic Implants or Follow-ups  Patients present themselves in-clinic for implantation or follow-ups  Information is collected using vendor specific “programmers”  Information is sent from interrogation system to a central Device Clinic Management System or EMR Remote Follow-ups  Patients devices are interrogated in the home health care environment  Information is collected using vendor specific communication devices and systems  Information is sent from interrogation system to a central Device Clinic Management System or EMR

IDCO Profile Systems Model

IHE Workshop – June IDCO Actors and Transaction

IHE Workshop – June IDCO Actors Observation Creator - A system that creates and transmits diagnostic or therapeutic observational data. Observation Processor and Repository – Systems that receive clinical observations and further process them or store them for retrieval and display. Grouped with PIX and PAM actors for patient identification and demographics management.

IHE Workshop – June IDCO Actors Alternative Actor configuration HL7 Router - A system that receives HL7 messages, routes them to one or more configured actors, and handles transport level acknowledgements. Router will manage patient identification cross-referencing

IHE Workshop – June Potential Participants Observation Creator  Implantable Cardiac Device Vendors Observation Processor and Repository  EMR, CIS or Device Clinic Management System Vendors HL7 Router  Integration Engine Vendors Others (?)

IHE Workshop – June IDCO Transaction CARD-12  Unsolicited HL7 v2.5 ORU message  Observation values coded using ISO/IEEE IDC nomenclature  Option for embedded PDF report  Audit Trail and Node Authentication (ATNA) profile recommended for remote follow-ups across non-trusted networks

IHE Workshop – June IDC Nomenclature Containment Tree

IHE Workshop – June HL7 2.5 ORU OBX-4 Used for Containment

IHE Workshop – June Example Transaction Flow

IHE Workshop – June Potential Extended Actor Groupings Basic IDCO Report Display using Retrieve Information for Display Profile (RID) IDCO Data Incorporation into a Report using Displayable Reports Profile (DRPT) IDCO Discrete Data Storage using Evidence Documents Profile (ED) IDCO Submission to an EHR using Cross Domain Document Sharing Profile (XDS)

IHE Workshop – June What’s Next? Scheduling / Orders Waveforms HL7v3 CDA

IHE Workshop – June More info on IDCO Profile in public comment June 18 – July 16 Final version for trial implementation available Aug 1 st

IHE Workshop – June Conclusion With the increased use of EMR systems, the networking of in-clinic and remote follow-up systems for implanted cardiac devices, and the continued growth of the implantable cardiac device market, the importance of this profile to clinicians has become more acute. Strong device vendor participation in the IDCO profile development this year is an acknowledgement of this importance. As the IDCO Profile and associated standards continue to evolve there is little doubt that the use of this profile will be a critical component of comprehensive cardiac care.

IHE Workshop – June Questions Questions? Nicholas Steblay Boston Scientific (651)

IHE Workshop – June