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 Simplify Interoperability Integration Standards Simplify Interoperability Simplifying Integration Saves - Time, Money and Improves Quality Simplifying Integration Saves - Time, Money and Improves Quality

5. Vendor #2Vendor #1Vendor #N IDCO IDCO = Implantable Devices Cardiac - Observation IDCO is a Standard Developed Specifically for Device Integration with Clinical Systems

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

7. IDCO consists of three components… 1.A set of terminology called a nomenclature -The nomenclature defines the semantics of the information being shared. 2.The structural arrangement of the information -This defines the syntax of the data being sent. 3.The specification of the integration -This is called a profile and states the rules for how an integration will be accomplished for a specific use case Nomenclature SyntaxProfile = IDCO

8. Standards used 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 specify usage constraints for semantic meaning, data type, unit of measure, and enumerated values using a set of normative text and numeric code identifiers for labeling implantable cardiac device data. The IDCO standard is now in ballot and should be ratified before year end.

9. Standard used 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

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

11. 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 IDCO crosses these two domains ACC and HRS physicians on the 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

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

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 IDCO in 2011? Complete the balloting of the IDC Nomenclature Begin expanding the IEEE IDC Nomenclature with prioritization from 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 or Provide Comments? As a physician … Contact Del Conyers at the HRS –E-mail Del Conyers, MPH, HRS Director of Quality Improvement at dconyers@hrsonline.org As a vendor … Join Google Group: ihe-pcd-idco-wg@googlegroups.com Or Contact: Nick Steblay (Nicholas.Steblay@bsci.com) Tom Schultz (Thomas.W.Schultz@Medtronic.com).

16. Questions?