Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TR 28380-1 — Health Informatics: IHE — Part 1: Integration Profiles
Technical Guide to Integrating the Healthcare Enterprise Profile Framework and Integration Patterns
Introduction to IHE and ISO/TR 28380-1
ISO/TR 28380-1 introduces the Integrating the Healthcare Enterprise (IHE) initiative and provides a comprehensive overview of the IHE integration profile framework. IHE is not a standards development organization but rather an initiative that promotes the coordinated use of established standards such as HL7, DICOM, and ISO to address specific clinical interoperability needs. The technical report describes how IHE defines integration profiles that specify how existing standards should be implemented together to solve particular healthcare information exchange problems.
The IHE technical framework is organized by clinical domains, each addressing a specific area of healthcare. These domains include Radiology, Cardiology, Laboratory, Patient Care Coordination, IT Infrastructure, Pharmacy, Patient Care Devices, and many others. Each domain develops integration profiles relevant to its clinical focus, following a well-defined development process that includes clinical requirements gathering, standards selection, technical specification development, and connectathon testing for validation.
IHE profiles are not new standards but rather implementation guides that specify how existing standards should be used together. This pragmatic approach accelerates interoperability by reducing the implementation choices that would otherwise lead to incompatible systems.
Core Integration Profiles
ISO/TR 28380-1 describes several foundational integration profiles that form the backbone of healthcare interoperability. The Cross-Enterprise Document Sharing (XDS) profile enables healthcare organizations to share clinical documents across enterprise boundaries through a federated registry-repository architecture. XDS defines how document sources, document consumers, and document registries interact to publish, discover, and retrieve clinical documents. The profile supports both indexed metadata search and content-based retrieval, enabling clinicians to find relevant patient information regardless of where it was originally created.
| Integration Profile | Abbreviation | Primary Function |
|---|---|---|
| Cross-Enterprise Document Sharing | XDS | Federated clinical document sharing across healthcare enterprises |
| Patient Identifier Cross-Referencing | PIX | Cross-referencing patient identifiers across multiple domains |
| Patient Demographics Query | PDQ | Query for patient demographics across healthcare enterprises |
| Audit Trail and Node Authentication | ATNA | Security audit logging and secure node communication |
| Consistent Time | CT | Time synchronization across networked healthcare systems |
| Cross-Enterprise User Assertion | XUA | Cross-enterprise user authentication and identity propagation |
| Document Digital Signature | DSG | Digital signing of clinical documents for integrity and non-repudiation |
| Basic Patient Privacy Consents | BPPC | Management of patient privacy consent directives |
The Patient Identifier Cross-Referencing (PIX) profile addresses the fundamental challenge of patient identity management across organizational boundaries. It defines transactions for linking patient identifiers from different domains to a common patient identity, enabling clinicians to access a comprehensive longitudinal patient record. The Patient Demographics Query (PDQ) profile complements PIX by enabling systems to query patient demographic information across domains, supporting patient look-up and identity resolution workflows.
Patient identity management remains one of the most challenging aspects of healthcare interoperability. Even small error rates in patient matching can lead to serious patient safety incidents. Implementers should consider probabilistic matching algorithms and manual review processes as complements to deterministic patient identity cross-referencing.
IHE Technical Framework and Domain Organization
The IHE Technical Framework is organized into domain-specific volumes, each containing detailed technical specifications for the integration profiles within that domain. Each profile specification includes the actors involved, the transactions exchanged between actors, the required standards and their specific options, and the expected behavior under normal and error conditions. Actors are functional units that exchange information through standards-based transactions, and a single system may implement multiple actors across different profiles.
ISO/TR 28380-1 describes the process by which IHE profiles are developed, tested, and maintained. New profiles are proposed in response to identified clinical interoperability needs, developed through a consensus process involving vendors, healthcare providers, and standards organizations, and validated through annual connectathon events where vendors test their implementations against each other. Successful profiles are published as final text specifications and may be referenced in procurement requirements by healthcare organizations seeking interoperable systems.
| IHE Domain | Focus Area | Key Profiles |
|---|---|---|
| Radiology | Medical imaging workflow and image sharing | SWF, PDI, CPI, IMPAX |
| IT Infrastructure | Cross-enterprise communication and security | XDS, PIX, PDQ, ATNA, CT |
| Patient Care Coordination | Care documentation and clinical pathways | XPHR, XDM, XPS |
| Laboratory | Laboratory testing workflow and results sharing | LPOCT, LAW, XD-LAB |
| Cardiology | Cardiac imaging and measurement | ECG, EB,CATH, CARD |
| Pharmacy | Medication management and dispensing | CM, DIS, PRE, PML |
The technical report also addresses the relationship between IHE profiles and national/regional health information exchange initiatives. Many countries have adopted IHE profiles as the basis for their national eHealth strategies, leveraging the standardized interoperability patterns to enable cross-organizational health information exchange while allowing for jurisdictional variations in policy and practice.
IHE connectathons have proven remarkably effective at identifying interoperability issues before systems reach production deployment. Organizations implementing IHE profiles should prioritize participation in connectathon events to validate their implementations against real-world peer systems.
Implementing IHE Profiles in Practice
Implementing IHE profiles requires a systematic approach to standards adoption that goes beyond simply supporting the required transactions. ISO/TR 28380-1 emphasizes the importance of understanding the clinical workflow context that the profile is designed to support, as successful interoperability depends not only on technical compliance but also on alignment with organizational processes and policies. The report recommends a phased implementation approach, beginning with a limited set of high-value profiles and expanding incrementally.
Testing and validation are critical success factors for IHE implementations. The standard describes the integration testing process used at IHE connectathons, where vendors test their systems against other vendors’ implementations in a structured environment. This peer-to-peer testing identifies interoperability issues that would not be discovered through standalone conformance testing alone. Organizations should incorporate similar cross-vendor testing into their own implementation projects.
Implementing IHE profiles without adequate testing against other vendors’ systems is a high-risk strategy. The complexity of healthcare interoperability means that even standards-compliant implementations may fail to interoperate correctly due to ambiguous specifications or differing interpretations. Invest in cross-vendor testing early in your implementation cycle.
Frequently Asked Questions
Q1: Is IHE a standards development organization?
No, IHE is not a standards development organization. It is an initiative that promotes the coordinated use of established standards (HL7, DICOM, ISO, etc.) to address specific clinical interoperability needs. IHE defines integration profiles that specify how existing standards should be used together.
No, IHE is not a standards development organization. It is an initiative that promotes the coordinated use of established standards (HL7, DICOM, ISO, etc.) to address specific clinical interoperability needs. IHE defines integration profiles that specify how existing standards should be used together.
Q2: What is an IHE actor?
An IHE actor is a functional unit defined by an IHE profile that communicates with other actors through standards-based transactions. A single software system may implement multiple actors across different profiles. For example, an electronic health record might implement both the document consumer actor (from XDS) and the patient demographics consumer actor (from PDQ).
An IHE actor is a functional unit defined by an IHE profile that communicates with other actors through standards-based transactions. A single software system may implement multiple actors across different profiles. For example, an electronic health record might implement both the document consumer actor (from XDS) and the patient demographics consumer actor (from PDQ).
Q3: How are IHE profiles validated?
IHE profiles are validated through annual connectathon events where vendors test their implementations against each other in a structured environment. These events identify interoperability issues and provide feedback for profile refinement. Successful profiles are published as final text specifications.
IHE profiles are validated through annual connectathon events where vendors test their implementations against each other in a structured environment. These events identify interoperability issues and provide feedback for profile refinement. Successful profiles are published as final text specifications.
Q4: What is the relationship between IHE and national eHealth strategies?
Many countries have adopted IHE profiles as the technical foundation for their national health information exchange strategies. IHE provides standardized interoperability patterns that can be adapted to national policy contexts while maintaining cross-border interoperability potential.
Many countries have adopted IHE profiles as the technical foundation for their national health information exchange strategies. IHE provides standardized interoperability patterns that can be adapted to national policy contexts while maintaining cross-border interoperability potential.
📥 Standard Documents Download
No download files available yet