Health Information Standards and Interoperability
Health information standards and interoperability is the area of health informatics concerned with how clinical and administrative data are structured, encoded, and exchanged so that independently developed systems can share and reuse information with preserved meaning. It spans the messaging and document standards that move data between systems, the controlled vocabularies that give coded data shared meaning, and the organisations and governance processes that develop and maintain those standards.
Definition
Interoperability is the ability of different information systems, devices, and applications to access, exchange, integrate, and cooperatively use data in a coordinated manner, within and across organisational boundaries, with the meaning of the data preserved. Health information standards are the agreed specifications — for syntax, semantics, and transport — that make such exchange possible.
Scope
This area orients the reader to the standards layer of health informatics: how data are formatted for exchange (HL7 v2, HL7 Clinical Document Architecture, and FHIR), how images and their metadata are handled (DICOM), how local data dictionaries and master data are reconciled with national and international terminologies, and how standards development organisations coordinate this work. It frames interoperability as a methodological and organisational topic, not as clinical or procurement advice.
Sub-topics
Core questions
- How can data be moved between systems without losing its clinical meaning?
- What is the difference between technical, syntactic, and semantic interoperability?
- Which standards govern clinical messages, documents, images, and coded terms?
- How are standards developed, balloted, and maintained, and by whom?
Key concepts
- Syntactic versus semantic interoperability
- Messaging standards (HL7 v2, HL7 v3)
- Document standards (Clinical Document Architecture)
- FHIR resources and RESTful exchange
- DICOM for imaging data and metadata
- Controlled terminologies (SNOMED CT, LOINC, ICD)
- Master data management and data dictionaries
- Standards development organisations and balloting
Mechanisms
Interoperability is usually decomposed into layers. Technical and syntactic interoperability concern the transport and the structure of a message or document — for example an HL7 v2 pipe-delimited message, an HL7 Clinical Document Architecture XML document, or a FHIR resource exchanged over a RESTful interface. Semantic interoperability adds shared meaning by binding data elements to controlled terminologies such as SNOMED CT, LOINC, and ICD, so that a coded concept means the same thing to the sending and receiving systems. Standards in each layer are specified, balloted, and maintained by standards development organisations, and adopted within local data dictionaries and master data management practices that reconcile institution-specific codes with the agreed external standards.
Clinical relevance
Standards and interoperability determine whether information generated in one care setting can be safely reused in another — for referrals, imaging review, laboratory result reporting, and population analytics. This entry describes how that exchange is structured and governed; it is reference material for understanding the standards landscape and is not guidance for selecting, configuring, or operating any specific system in patient care.
Evidence & guidelines
The standards in this area are maintained by recognised standards development organisations (HL7 International, DICOM, and terminology bodies such as SNOMED International and the Regenstrief Institute for LOINC) and are referenced in national digital-health policy. Benson and Grieve's textbook provides a consolidated reference to FHIR, HL7, and SNOMED CT, while commentaries such as Mandl and Kohane (2012) frame the policy case for open, substitutable health IT built on shared standards.
History
Health information standards grew out of the need to connect hospital laboratory, pharmacy, and registration systems in the 1980s, giving rise to HL7 version 2 messaging and, in parallel, the ACR-NEMA work that became DICOM for imaging. The 2000s saw richer model-based specifications including the HL7 Clinical Document Architecture, and from the 2010s the FHIR specification reframed exchange around web-style resources and APIs, against a policy backdrop arguing for open, substitutable systems.
Debates
- How much interoperability is realistically achievable across systems?
- Commentators have argued that closed electronic health record architectures impede data liquidity and that progress depends on open standards and substitutable applications; how far standardisation alone can close the gap, versus governance and incentives, remains debated.
Key figures
- Kenneth Mandl
- Isaac Kohane
- Robert Dolin
- Grahame Grieve
- Tim Benson
Related topics
Seminal works
- dolin-2006
- mandl-kohane-2012
- benson-grieve-2021
Frequently asked questions
- What is the difference between syntactic and semantic interoperability?
- Syntactic interoperability means two systems can parse the structure of an exchanged message or document; semantic interoperability means they also share the meaning of the data, typically by using common coded terminologies, so a received concept is interpreted as intended.
- Why are there so many different health data standards?
- Different standards address different problems — messaging between systems, clinical documents, imaging, and coded terminology — and they evolved at different times for different settings, which is why a single deployment often combines several of them.