The four levels of interoperability: foundational, structural, semantic and organizational
What it takes for two health systems not only to send each other data, but to understand it and use it safely.
What is interoperability in healthcare?
Interoperability is the ability of different information systems, devices and applications to access, exchange, integrate and use data together, within and across organizational boundaries, so that care is better for individuals and populations. The last verb, use, matters most: data that arrives but cannot be understood, trusted or acted on is exchange, not interoperability.
The levels below follow the HIMSS definition of 2019. Other models use different names (some call the structural level "syntactic", some add a "process" level), but the idea is the same: from connection, to format, to meaning, to use.
What are the four levels of interoperability?
| Level | What it establishes | The question it answers | Typical examples |
|---|---|---|---|
| 1. Foundational | The connection: one system can securely send data to another and receive data from it. | Can the data get there? | Network connection, secure transport (TLS, VPN), an interface engine passing a file or message. |
| 2. Structural | The format, syntax and organization of the data, down to the field, so it can be parsed. | Can the receiver find each piece of data? | HL7 v2 segments and fields, C-CDA document sections, FHIR resources and their elements. |
| 3. Semantic | Shared models and coded data with standard definitions, so the meaning is the same at both ends. | Does the receiver understand it the same way? | SNOMED CT for problems, LOINC for tests, RxNorm for medicines, ICD-10 for diagnoses, UCUM for units. |
| 4. Organizational | Governance, policy, legal agreements, consent, trust and workflow, so the data is used safely and in time. | Is the data allowed, trusted and built into care? | Data sharing agreements, consent policies, trust frameworks such as TEFCA, agreed workflows for acting on received data. |
The levels build on each other: a perfectly coded result (semantic) is of no use if it never arrives (foundational), and a connection that carries well-formed but uncoded free text stops at the structural level.
How do the levels look on one example?
A laboratory sends a potassium result to a clinic's EHR:
- Foundational: the lab system and the EHR have a secure connection, and the message reaches the interface engine.
- Structural: the message is an HL7 v2 ORU result, so the EHR finds the patient in the PID segment and the result in an OBX segment.
- Semantic: the test is coded with LOINC and the unit with UCUM, so the EHR files it as serum potassium in mmol/L, trends it with earlier results and can fire a decision support rule on a high value.
- Organizational: an agreement says who may receive the result, the patient's identity is matched by an agreed process, and the clinic has a workflow in which someone sees and acts on a critical value in time.
Take away the LOINC code and the result still arrives and still displays, but it may be filed under a local name, missed by the trend graph and ignored by the alert: the exchange worked, the interoperability did not.
What is the difference between compatibility and interoperability?
Compatibility is the ability of systems or components to work in the same environment without conflict: the application runs on the operating system, the device fits the network, two programs do not break each other. Interoperability goes further: the systems exchange information and use what they receive. Two systems can be fully compatible (they run side by side on the same servers) and still share no data at all. When a new system is designed or selected, both are asked of it: that it fits the existing environment, and that it exchanges data with the systems around it.
Which standards belong to which level?
- Transport and security (foundational): network protocols, TLS, VPN, Direct secure messaging, web services and APIs as a channel.
- Message and document formats (structural): HL7 v2 messages, HL7 CDA and C-CDA documents, FHIR resources, DICOM for images.
- Terminologies and code sets (semantic): SNOMED CT, LOINC, RxNorm, ICD-10, CPT, UCUM. In the United States, USCDI (ONC) names a common set of data classes and elements, with the vocabulary each should use.
- Implementation profiles: IHE profiles (such as XDS for sharing documents and PIX/PDQ for patient identifiers) combine existing standards for one use case, so vendors implement them the same way. They cut across the levels.
- Policy and trust (organizational): data use agreements, consent rules, national or regional trust frameworks, and rules against information blocking.
One standard can touch more than one level: FHIR gives the structure of a resource, and its elements are bound to code systems for the meaning. Standards make interoperability possible; they do not achieve it alone, because two systems can implement the same standard with different local choices.
What do candidates get wrong?
- Treating a working interface as interoperability. Data arriving is the foundational level; meaning and use come later.
- Mixing up structural and semantic. Structure is where the data sits (the field); semantics is what it means (the code and its definition).
- Forgetting the organizational level. Many exchange projects fail on agreements, consent, patient matching or workflow, not on technology.
- Equating compatibility with interoperability. Running side by side is not exchanging and using data.
- Assuming one standard solves everything. A format without shared code sets, or a code set without agreed policy, stops short.
Summary for revision
- Foundational: the data gets there securely.
- Structural: the format and fields are agreed (HL7 v2, CDA, FHIR).
- Semantic: the meaning is shared through codes (SNOMED CT, LOINC, RxNorm).
- Organizational: governance, policy, consent and workflow let the data be used.
- Compatibility is working side by side; interoperability is exchanging and using data.
Sources
- HIMSS, definition of interoperability and its four levels (2019).
- Office of the National Coordinator for Health IT (ONC), United States Core Data for Interoperability (USCDI).
- HL7 International, descriptions of HL7 v2, CDA and FHIR; IHE International, IHE technical frameworks and profiles.
Related free practice questions
- Which code set for which type of data?
- Compatibility and interoperability: the two design aspects
- Health information exchange architectures
The site files this concept under the domain Healthcare and Technology Environments.
Try exam-style questions
A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.
Start the trial examQuestions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?
Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Testing types · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance
The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership
Written by Adel Moustafa, About us
Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.