1. Device and EMR interoperability (IDCO)

2. Implantable Cardiac Device Information is Collected At Implant … During In Clinic Follow-ups … And in the Home Healthcare Environment.

3. Vendor #2Vendor #1 Moving this Information Collected from Multiple Vendor Products into Clinic Information Systems Vendor #N Supporting Multiple Vendor Integrations is Complicated and Expensive Supporting Multiple Vendor Integrations is Complicated and Expensive Is Required for Workflow Efficiency and Quality Outcomes in the Clinic.

4. Vendor #2Vendor #1 Standardizing the Way Vendor Devices Interoperate with Clinical Information Systems Vendor #N Integration Standards Allows for Reuse of System Interfaces Allows for Reuse of System Interfaces Simplifying Integrations Saving Time, Money and Improving Quality Simplifying Integrations Saving Time, Money and Improving Quality

5. Vendor Participation in the Implantable Cardiac Device Standards Process Good news! Multiple device and EMR vendors have been participating in the standards development process. Implantable Cardiac Device Vendors EMR Vendors

6. Three Type of Standards Being Worked On Semantics –A nomenclature or set of terminology that defines the information being shared Syntax –The structural arrangement of the information Profiles –The specifications for how an integration will be accomplished for a specific use case

7. Standards for Semantics The device vendors and a HRS committee has been working with CEN/ISO/IEEE/11073 to define a nomenclature for implantable cardiac device domain. The standards is a set of normative text identifiers and numeric code identifiers for labeling implantable cardiac device data. It specifies constraints for usage in regards to semantic meaning, data type, unit of measure, and enumerated values. The standard is now in ballot and should be ratified before year end.

8. Standards for Structure Health Level Seven International (HL7) is the global authority on standards for interoperability of health information technology. The device and EMR vendors have adopted a standard HL7 version 2 message structure called an Unsolicited Orders and Observations Message to facilitate data integration. A HL7 version 3 message for the implantable cardiac device domain has also been defined and passed ballot in support of future initiatives. Health Level Seven International

9. Profiling Use of the Standards Integrating the Healthcare Enterprise (IHE) is an initiative by healthcare professionals and industry to improve the way computer systems in healthcare share information. IHE promotes the coordinated use of established standards such as HL7 and DICOM to address specific clinical need in support of optimal patient care. 1.Clinical and technical experts define critical use cases for information sharing. 2.Technical experts create detailed specifications for communication among systems to address these use cases, selecting and optimizing established standards. 3.Industry implements these specifications called IHE Profiles in HIT systems. 4.IHE tests vendors’ systems at carefully planned and supervised events called Connectathons. IHE’s 4 Step Process

10. IHE Domains IHE Planning and Technical committees follow the four step annual process to address interoperability in a variety of clinical domains: –Anatomic Pathology –Cardiology –Eye Care –IT Infrastructure –Laboratory –Patient Care Coordination –Patient Care Devices –Quality, Research and Public Health –Radiation Oncology –Radiology We work within these domains ACC and HRS representatives on Planning Committee define use cases and data requirements Vendors on Technical Committee author the profile Vendors then implement profile specification in their product and participate in the Connectathon

11. IHE Connectathon The Connectathon is a large scale interoperability event held every year where vendors demonstrate connectivity using the IHE profiles.

12. Implantable Cardiac Device Observations Profile (IDCO) IDCO profiles in-clinic and home healthcare device interrogation use cases Based on IEEE 11073 IDC nomenclature and HL7 standards Device and EMR vendors successfully tested the IDCO Profile at the 2010 and 2011 Connectathons

13. Why is IDCO compliance important? Allows device data to be captured in EMR systems automatically which reduces workflow complexity EMR implementation costs are reduced for those systems that comply with IDCO Ensures quality of care by conforming data to standard data format and terminology

14. What’s Planned for this Next Year? Complete the balloting of the IDC Nomenclature Start working on expanding the IEEE IDC Nomenclature with the HRS working group to include detailed data, waveforms and alerts Refine the IDCO Profile to improve usability and ease of implementation Plan support for the evolving HL7 v3 standard

15. How Can You Get Involved? As a physician … Contact info for Planning Committee and HIT Task force As a vendor … Contact info Technical Committee

16. Questions?