Integrating the Healthcare Enterprise

Integrating the Healthcare Enterprise
Integrating the Healthcare Enterprise · Public domain · source
Name	Integrating the Healthcare Enterprise
Abbreviation	IHE
Formation	1998
Type	Nonprofit initiative
Headquarters	Chicago
Region served	International

Integrating the Healthcare Enterprise is a standards-based initiative that promotes coordinated use of established Health Level Seven International specifications, DICOM profiles, and other interoperability frameworks to improve information exchange among hospitals, clinics, and healthcare enterprises. It convenes vendors, providers, and regulators to define integration profiles that map workflows across systems such as electronic health records, picture archiving and communication systems, and health information exchanges like eHealth Exchange and regional networks. The initiative influences procurement, certification, and deployment practices used by organizations including the World Health Organization, Centers for Medicare & Medicaid Services, and national health systems such as the National Health Service (England).

Overview

IHE develops integration profiles that specify how to implement existing standards from organizations such as Health Level Seven International, DICOM, ISO, CEN (European Committee for Standardization), and IHE International. Vendors including Epic Systems, Cerner Corporation, GE Healthcare, Philips Healthcare, and Siemens Healthineers use IHE profiles to ensure interoperability among systems deployed in institutions like Mayo Clinic, Cleveland Clinic, Johns Hopkins Hospital, and university hospitals in networks such as HSRnet. IHE organizes domain committees—Radiology, Cardiology, IT Infrastructure, Patient Care Coordination—that map clinical workflows to technical transactions adopted by agencies such as the Office of the National Coordinator for Health Information Technology and regulators including the European Commission.

History and Development

IHE was initiated in 1998 by clinicians and vendors in radiology and expanded to domains influenced by milestones such as the adoption of DICOM in imaging and the promulgation of HL7 v2 and v3 messaging. Stakeholders from institutions such as Massachusetts General Hospital, Brigham and Women's Hospital, and vendors like Agfa-Gevaert participated in early interoperability demonstrations analogous to events organized by IETF and IEEE. Over time IHE added technical frameworks, connectathons, and publishing cycles that paralleled work by ISO/TC 215, the Clinical Data Interchange Standards Consortium, and national bodies like Standards Australia.

Standards and Technical Framework

IHE defines profiles that constrain and combine standards including HL7 FHIR, CDA (Clinical Document Architecture), DICOM, IHE XDS, and transport specifications like TLS for secure exchange. Profiles such as XDS.b, XCA, XDS-I, and ATNA interoperate with identifiers and vocabularies from LOINC, SNOMED CT, and ICD-10 used in clinical documentation across systems from vendors such as Allscripts and McKesson Corporation. Testing events called Connectathons mirror conformance activities seen in W3C and OASIS communities, and certification programs align with initiatives by the National Institute of Standards and Technology and regional certification authorities like NHS Digital.

Implementation and Use Cases

IHE profiles support use cases including image sharing among institutions like Memorial Sloan Kettering Cancer Center and regional networks such as Erasmus MC and telemedicine programs in collaboration with organizations like Doctors Without Borders. Clinical portals aggregate records for emergency care at centers such as Karolinska University Hospital using XDS and FHIR interfaces, while cardiology workflows integrate devices from Medtronic and Abbott Laboratories using IHE Cardio profiles. Public health reporting to agencies such as the Centers for Disease Control and Prevention relies on structured messaging consistent with IHE profiles for syndromic surveillance and immunization registries administered by ministries of health like Ministry of Health (New Zealand).

Governance, Privacy, and Security

IHE governance involves national and regional committees analogous to governance models at World Health Organization assemblies and standards bodies such as IEC. Security profiles like ATNA reference cryptographic practices promoted by NIST and privacy controls that reflect legislation including Health Insurance Portability and Accountability Act and directives from the European Commission on data protection. Implementers coordinate with certification programs run by bodies such as HIMSS and national health agencies to ensure adherence to access control, audit logging, and consent management used by institutions like Kaiser Permanente.

Impact and Evaluation

Empirical assessments by health systems including Partners HealthCare and studies published in journals associated with BMJ and The Lancet report improvements in workflow efficiency, reduced duplicate testing, and faster access to imaging and lab results when IHE profiles are adopted. Governments and purchasers such as U.S. Department of Veterans Affairs and regional health authorities in Ontario incorporate IHE conformance into procurement, citing experience from large-scale programs like Netherlands' National Switch Point and multi-institution initiatives comparable to epSOS. Connectathon participation and vendor certification metrics provide quantitative indicators of interoperability maturity used by evaluators at RAND Corporation and academic centers.

Criticisms and Challenges

Critics cite challenges including complexity of profile sets, resource demands for integration in smaller providers like community hospitals, and fragmentation due to competing approaches exemplified by debates between proponents of FHIR-centric implementations and legacy HL7 v2 deployments. Interoperability gaps persist across borders because of divergent national regulations such as the General Data Protection Regulation and differing vendor roadmaps from companies like Oracle Corporation and IBM. Scalability, semantic harmonization across terminologies like SNOMED CT and ICD-11, and sustaining voluntary governance models remain ongoing obstacles noted by analysts at OECD and standards observers.

Category:Health information technology