If you’ve spent any time in healthcare, you’ve heard the word interoperability. It shows up in strategy decks, vendor pitches, and policy documents — usually without a clear explanation of what it actually means for real people.
Here’s my attempt at a plain-language version.
What It Actually Means
Interoperability in healthcare means that different systems — hospitals, clinics, labs, pharmacies, insurers — can share patient information in a way that is accurate, timely, and useful to whoever needs it.
Not just that the data can move. That it arrives somewhere and actually makes sense.
Think of it this way: a patient shows up to an emergency room they’ve never been to before. The physician needs to know their medications, their allergies, their recent test results. That information exists — it’s just scattered across different systems that weren’t built to talk to each other.
That’s the problem interoperability is trying to solve.
Why It’s So Hard to Fix
The technical piece — getting systems to send data back and forth — is actually the easier part. The harder layers are:
Do systems understand each other? Sending data is one thing. Having the receiving system interpret it correctly is another. Medical terminology needs to mean the same thing regardless of which system it came from.
Do organizations want to share? For a long time, keeping data inside your own walls was a competitive advantage. Changing that culture is slower than changing the technology.
Who’s responsible when something goes wrong? If a patient record gets transmitted incorrectly and a physician makes a decision based on bad data, the governance around that is still being figured out.
Most of the progress we’ve made has been on the technical side. The organizational and cultural layers are where things still get stuck.
The Standards Worth Knowing
You don’t need to be a developer to understand why these exist.
HL7 v2 — The old workhorse. Still used everywhere for lab results, patient admissions, and pharmacy updates. It works, but it’s clunky and was never designed for modern data needs.
HL7 FHIR — The newer standard that regulators are now pushing. It’s more flexible and developer-friendly, and it’s what makes it possible for apps to pull your health data in real time. Think of it as the language that modern health data is starting to speak.
SMART on FHIR — The layer that lets third-party apps securely access your health record. This is what makes patient-facing health apps possible without having to manually enter all your information.
What’s Still in the Way
Even with better standards and regulatory pressure, a few things remain genuinely hard:
Old systems don’t go away easily. A lot of healthcare still runs on technology that predates modern interoperability standards. Connecting them is expensive and messy.
The data itself isn’t always clean. Interoperability assumes the information is worth sharing. Incomplete records, inconsistent coding, and duplicate patient files erode the value of data exchange even when the pipes work.
Matching patients across systems is harder than it sounds. Without a universal patient identifier, linking your records at one hospital to your records at another is error-prone. It’s one of those problems that sounds simple until you try to solve it at scale.
Why This Is a Patient Safety Issue, Not Just an IT Problem
Medication errors happen when a prescribing physician doesn’t know what a patient is already taking. Unnecessary tests get ordered because results from another system aren’t visible. Care teams working in silos make decisions without the full picture.
Interoperability, done well, reduces those gaps. That’s why it matters — not as a technology exercise, but as a direct line to better, safer care.
We’re making real progress. But the pace still lags behind what the problem demands.
What’s your experience with health data exchange? I’d love to compare notes — connect with me on LinkedIn.