Standards & Interoperability
Healthcare Interoperability
Healthcare interoperability is the ability of different information systems, devices, and applications to access, exchange, integrate, and use health data in a coordinated way — within and across organisational boundaries. It is the difference between a patient's records following them seamlessly from GP to hospital to specialist, and a fax machine re-keying the same allergy list three times. For any AI product engineering team, interoperability is the substrate everything else depends on: an agent can only assist with care it can actually see, and it can only act through systems that will accept its writes.
The four levels of interoperability
HIMSS defines interoperability across four ascending levels. Foundational interoperability means one system can send data to another and the receiver can accept it — the wire works. Structural interoperability means the format and syntax are preserved, so a field arrives as a field. Semantic interoperability is the hard one: both systems share the same meaning, so a 'diagnosis of type 2 diabetes' coded as SNOMED CT 44054006 is understood identically on both ends. Organisational interoperability adds the governance, policy, consent, and trust frameworks that let humans and institutions actually exchange data lawfully. Most real-world pain lives at the semantic and organisational levels, not the technical wire.
The standards that make it possible
Interoperability is achieved through layered standards. HL7 v2 still carries the bulk of intra-hospital messaging. HL7 FHIR is the modern API standard for external and app integrations. Terminologies — SNOMED CT for clinical concepts, LOINC for lab observations, ICD-10 for diagnoses, dm+d for UK medicines — provide the shared vocabulary that enables semantic understanding. Document standards like CDA and frameworks like IHE profiles fill specific exchange use cases. A competent integration strategy picks the right combination per customer rather than assuming a single standard solves everything.
Why interoperability is so difficult
Even with standards, true interoperability is rare. Vendors implement specifications inconsistently, populate optional fields differently, and use local codes that never get mapped to national terminologies. Data quality varies wildly, and governance — who is allowed to see what, under which lawful basis — adds a non-technical barrier that engineering alone cannot solve. The result is that 'we support FHIR' is a starting point, not a guarantee. Real interoperability work is equal parts data engineering, terminology mapping, and patient navigating the trust and consent landscape.
Interoperability as a product advantage
For a healthcare AI company, mastering interoperability turns a recurring cost into a competitive moat. The team that can reliably normalise messy data from many sources, map local codes to standard terminologies, and exchange data lawfully can deploy the same product across many customers with predictable effort. That repeatability is what makes AI copilots, RCM automation, and population health analytics economically viable at scale — and it is exactly the capability buyers struggle to build in-house.
Frequently asked questions
What is the hardest level of interoperability to achieve?
Semantic interoperability — ensuring both systems interpret the data identically. Two systems can exchange a diagnosis perfectly at the technical level yet disagree on what it means if they use different code systems or local codes that were never mapped to a shared terminology like SNOMED CT.
Does FHIR solve interoperability on its own?
No. FHIR provides a strong, modern transport and data model, but semantic agreement (shared terminologies) and organisational governance (consent, lawful basis, trust frameworks) still have to be solved alongside it. FHIR makes the plumbing easier, not the meaning or the politics.
What is an HIE?
A Health Information Exchange (HIE) is an organisation or network that enables the sharing of clinical data across providers in a region or country. HIEs and national programmes (like the NHS's shared care records) are part of the organisational layer of interoperability.
Struggling to make your systems talk to each other? We turn messy, multi-source health data into clean, interoperable pipelines. Book a discovery call.