1. September, 2005What IHE Delivers IHE Cardiology Profiles for Electronic Healthcare Record systems ITI Meeting Dec 5 th, 2006

2. 2 Some facts Cardiac related events comprise more than 25% of all hospital admissions in the U.S.!! Cardiology is typically (still) a profit center and not a cost center in a hospital Almost all cardiologists maintain both a private office practice and hospital affiliations As the population ages and with increased obesity issues, cardiovascular issues are rising dramatically

3. 3 IHE Cardiology Profiles Y1-Y4 Cath Lab Workflow and Measurements Intra-departmental Workflow Profiles Inter-departmentalProfilesAggressivelyadopted/ Promoted ITI And PCC Profiles Echo Lab Workflow and Measurements Stress Lab Workflow and Measurements Nuclear Medicine Imaging Retrieve ECG for Display (based on RID) Electrophysiology Lab Workflow and Measurements Implantable Device Cardiac Observations (IDCO) Displayable Reports Urgent Implantable Device Query (based on PDQ) Data Harvesting (Year 5) Retrieve Information for Display (RID) PIX/PDQ Many variants of XDS and PCC content profiles Consistent Time

4. 4 Example - Displayable Reports Cardiology reports typically PDF with lots of graphics – how to get them into an EMR? Solved with IHE Displayable Reports Profile Submitting reports encapsulated in HL7 v2 MDM message

5. 5 DRPT to XDS

6. 6 ITI creates an “Appendix H”? In the IHE Cardiology Technical Framework, we have an Appendix which explicitly calls out Profiles from other Domains which we want the Cardiology vendors to implement (perhaps ITI could do the same for PCD and Cardiology!?!)

7. 7 Appendix H Example Appendix H:Cardiology Summary of Relevant Profiles from Other Domains  H.1Consistent Time (CT) H.1Consistent Time (CT) H.1.1CT ActorsH.1.1CT Actors H.1.2CT TransactionsH.1.2CT Transactions H.1.3Cardiology Use CasesH.1.3Cardiology Use Cases  H.2Scheduled Workflow (SWF) and Patient Information Reconciliation (PIR) H.2Scheduled Workflow (SWF) and Patient Information Reconciliation (PIR) H.2.1Cardiology Use Case for SWF and PIRH.2.1Cardiology Use Case for SWF and PIR  H.3Retrieve Information for Display (RID) H.3Retrieve Information for Display (RID) H.3.1RID Process FlowH.3.1RID Process Flow H.3.2Cardiology Use CasesH.3.2Cardiology Use Cases  H.4Cross-Enterprise Document Sharing (XDS) H.4Cross-Enterprise Document Sharing (XDS) H.4.1XDS Process FlowH.4.1XDS Process Flow H.4.2Cardiology Use CasesH.4.2Cardiology Use Cases H.4.3XDS Content ProfilesH.4.3XDS Content Profiles H.4.3.1XDS-MS Medical SummaryH.4.3.1XDS-MS Medical Summary H.4.3.2XDS-I ImagingH.4.3.2XDS-I Imaging

8. 8 Appendix H Introduction Appendix H: Cardiology Summary of Relevant Profiles from Other Domains This appendix calls out specific Integration Profiles defined in the IHE Radiology and IT Infrastructure Technical Frameworks. These Integration Profiles are sufficiently important to the cardiology domain that they have been explicitly included in the IHE Cardiology Technical Framework. However, they are specified only by reference to their original definition in the other Technical Frameworks, with notes and use cases on their applicability to cardiology. There are no additional technical requirements defined in this Appendix. The full specification of the Profiles identified in this Appendix can be found in the IHE Technical Framework documents of other domains. These descriptions are provided for reference related to their use in the Cardiology domain.

9. 9 In Summary We need a more bi-directional, active dialogue with the ITI and PCC domains to:  get feedback on IHE Cardiology Technical Framework implementation plans (e.g., IDCO)  A way to promote Cardiology and PCD (and other?) Profiles to the EHR vendors because you are missing the Departmental content