Health interoperability
In short
Health interoperability is the ability of systems and organizations to exchange clinical information and use it without special effort, with both ends understanding the same thing. It does not depend on technology alone: it also requires compatible laws, agreed processes and a common vocabulary. It is what lets patient data follow the patient across facilities, regions and countries.
- Type
- Concept
- Steward
- No single steward: general concept or generic technology
- Reviewed
- October 25, 2026
Explanation
What it is
There is no single definition. Three official references show its different sides:
- European Interoperability Framework (EIF, European Commission, 2017): the ability of organisations to interact towards mutually beneficial goals, sharing information and knowledge through the business processes they support, by means of the exchange of data between their ICT systems.
- Pan American Health Organization (PAHO): the ability of different information technology systems, software applications and networks to communicate, to exchange data accurately, effectively and consistently, and to use the information that has been exchanged.
- United States federal law (42 U.S.C. 300jj): technology that enables the secure exchange and use of electronic health information without special effort on the part of the user, allows complete access to all authorized information, and does not constitute information blocking.
The first focuses on organizations, the second on systems, and the third adds a legal consequence.
The layers
This glossary classifies terms with the EIF layers, but treats syntax, which the EIF includes in the semantic layer, as a layer of its own:
| Layer | Question it answers | Health examples |
|---|---|---|
| Legal | Do the rules allow sharing, and on what terms? | data protection, consent |
| Organizational | Are processes, responsibilities and expectations aligned? | agreements between institutions, referral workflows |
| Semantic | Is what is sent understood the same way? | SNOMED CT, LOINC, value sets |
| Syntactic | Does what is sent have the agreed format and structure? | HL7 v2 messages, CDA documents, FHIR resources |
| Technical | Can the systems connect? | interfaces, protocols, FHIR APIs |
The EIF adds two governance pieces: integrated public service governance, which cuts across its four layers, and interoperability governance, which is the background layer.
Technical and semantic
PAHO describes two problems to solve: technical interoperability, which ensures that data can move reliably between systems, and semantic interoperability, which ensures that each system understands what it receives. To get the full benefit, PAHO adds, systems must interpret the data and act on it, for example by automatically integrating lab results from another facility into the health record.
Common misconceptions
- Reducing it to a technical standard. Adopting FHIR or HL7 v2 solves the connection, not the meaning or the agreements between institutions.
- Treating it as an IT project. The EIF defines it as an ability of organizations.
- Believing it is achieved once. The EIF warns that it is disrupted by changes in legislation, in people's needs, in the structure of administrations, in business processes and by new technologies, so its governance is continuous.
- Ignoring its legal dimension. In the United States, the legal definition excludes information blocking practices.
Usage examples
In the European Union, MyHealth@EU lets countries exchange patient summaries and ePrescriptions through national contact points for eHealth, to treat people travelling within the EU.
The European Health Data Space Regulation (Regulation (EU) 2025/327) provides that from March 2029 all Member States exchange patient summaries and ePrescriptions, and from March 2031 medical images, lab results and discharge reports.
In Brazil, the National Health Data Network (RNDS) is the Ministry of Health's official interoperability platform. According to the Ministry, one example of the data journey is a vaccine recorded in a primary care system, which becomes available to professionals and to the citizen in the Meu SUS Digital app.
In the United States, 42 U.S.C. 300jj defines interoperability of health IT and includes as a condition that it does not constitute information blocking.
PAHO recommends that national policy frameworks include security and privacy principles, exchange requirements, the formal adoption of messaging and content standards, and policies on national patient identifiers.
A hospital receives another institution's lab result electronically and adds it to the health record without retyping it, because both use the same codes and units.
Relation to other terms
Relies on1
- Health data governanceMedium
PAHO recommends a national policy and governance framework to adopt standards and share data while protecting privacy.
Depend on this one1
- EIFRequired
The EIF defines interoperability and organizes it in layers; without that concept it has no subject.
Sources
- European Commission — New European Interoperability Framework (2017)interoperable-europe.ec.europa.eu
- PAHO — Interoperability in Public Health (Digital Transformation Toolkit, Knowledge Tools 24)iris.paho.org
- 42 U.S.C. 300jj — Definitions (U.S. Code, govinfo)govinfo.gov
- European Commission — Electronic cross-border health services (MyHealth@EU)health.ec.europa.eu
- European Commission — European Health Data Space Regulation (EHDS)health.ec.europa.eu
- Ministério da Saúde — Rede Nacional de Dados em Saúde (RNDS)gov.br

