Interoperability in healthcare is the ability of different health IT systems, devices, and applications to exchange patient data and use that information meaningfully. When it works, your lab results from one hospital are available to a specialist across town, your medication list follows you to the emergency room, and your primary care doctor can see notes from every provider you’ve visited. When it doesn’t work, you end up repeating the same medical history on a clipboard, getting duplicate tests, or worse, receiving care from a provider who’s missing a critical piece of your record.
The concept sounds simple, but making it happen across thousands of hospitals, clinics, insurance companies, and apps is one of the most complex challenges in modern medicine. It involves technical standards, shared vocabularies, federal regulations, and organizational trust agreements all working in concert.
The Four Levels of Interoperability
Not all data sharing is equal. Healthcare interoperability operates on four distinct levels, each building on the one before it.
Foundational interoperability is the most basic layer. It simply means one system can send data to another. Think of it as opening the pipes so information can flow, without any guarantee that the receiving system knows what to do with it.
Structural interoperability (sometimes called syntactic interoperability) adds formatting rules. The data is organized in a consistent, predictable way so the receiving system can parse it correctly. If foundational interoperability turns on the faucet, structural interoperability makes sure the water goes into a glass instead of spraying everywhere.
Semantic interoperability is where things get genuinely useful. At this level, the receiving system doesn’t just accept and organize the data; it actually understands what the data means. A diagnosis code entered in one hospital carries the same clinical meaning when it arrives at another. This requires standardized medical vocabularies so that “arthritis” in one system isn’t logged as “joint inflammation” in another with no link between the two.
Organizational interoperability sits on top of everything else. It covers the governance, policies, privacy agreements, and trust frameworks that allow different organizations to share data securely and legally. The federal Trusted Exchange Framework and Common Agreement (TEFCA) is a major example: a national infrastructure designed to let health information networks exchange data under a shared set of rules.
How Systems Actually Talk to Each Other
Two technical standards dominate healthcare data exchange. The older one, HL7 version 2, has been around for decades and remains deeply embedded in hospital systems. Every state, local, and territorial public health agency in the U.S. supports it. But it has significant limitations: there’s no underlying information model, the standard allows so much optionality that two “compliant” systems can still struggle to communicate, and it has poor support for standardized medical vocabularies.
The newer standard, FHIR (Fast Healthcare Interoperability Resources), is designed to work like modern web technology. It’s flexible, supports smartphone apps, and can launch directly from electronic health records. When paired with secure app frameworks, developers can build tools that pull patient data in real time. The catch is that public health systems largely can’t accept FHIR messages yet, so the transition from HL7v2 is gradual rather than sudden.
Underneath both standards, two coding systems do much of the heavy lifting for semantic interoperability. One is used to label the question (what type of test was ordered, what observation was made), while the other codes the answer (the specific diagnosis or result). A lab order might use one system to specify “what is the diagnosis?” and the other to specify “arthritis.” The developers of both coding systems have a formal agreement to keep their terminologies aligned, which reduces the kind of translation errors that used to plague cross-system data sharing.
Federal Rules That Require Data Sharing
Interoperability in the U.S. isn’t optional anymore. The 21st Century Cures Act, signed into law in 2016, laid the groundwork, and the ONC’s Cures Act Final Rule put specific teeth behind it. The rule requires the healthcare industry to adopt standardized APIs so patients can securely access their own electronic health information through smartphone apps. Patients have the right to access all of their electronic health data, both structured and unstructured, at no cost.
The rule also targets a practice called “information blocking,” which is anything a health IT developer, health information network, or healthcare provider does that is likely to interfere with the access, exchange, or use of electronic health information. For IT developers and health information networks, penalties can reach up to $1 million per violation. For healthcare providers, the Department of Health and Human Services has established separate disincentives through rulemaking.
On the insurance side, CMS requires that affected payers make claims data, encounter data, and clinical data available through FHIR-based APIs. This means you can, in principle, use a third-party app of your choosing to pull your insurance claims history and clinical records into one place.
Where U.S. Hospitals Stand Today
Adoption has climbed steadily. According to the American Hospital Association’s 2025 health IT survey, 96% of U.S. non-federal acute care hospitals can electronically send summary care records to other organizations. Ninety-three percent can receive them, and 94% can search for and query health information from outside sources. The harder part is integration: only 79% of hospitals can take incoming data and fold it into their own records in a usable way. Overall, 76% of hospitals now engage in all four interoperability domains, up consistently from where things stood a decade ago.
That 76% number matters because sending and receiving data is only half the equation. If a hospital receives your records but a clinician still has to manually re-enter the information, much of the safety and efficiency benefit disappears.
Impact on Patient Safety and Costs
The clinical case for interoperability is strongest around medication errors. In a multi-hospital study published in the Journal of Patient Safety, connecting infusion pumps directly to electronic health records (so prescriptions auto-programmed the pumps instead of requiring manual entry) reduced medication administration errors by 16%. Errors involving high-risk medications dropped from 84% to 16% of observed cases. Expired medication errors fell from 3.1 per 100 infusions to 0.5. The core mechanism is simple: autoprogramming eliminates roughly 86% of the manual keystrokes involved in IV medication administration, and fewer keystrokes means fewer chances to make a mistake.
The financial stakes are enormous. A West Health Institute analysis estimated that widespread medical device interoperability could eliminate at least $36 billion in waste in inpatient settings alone. The savings break down into four main categories: $18 billion from shorter hospital stays (because critical information like lab results reaches clinicians faster), $12 billion from reducing the time clinicians spend manually entering data, $1.9 billion from preventing adverse events through automated safety checks, and $1.5 billion from eliminating redundant testing that happens when providers can’t see what’s already been ordered.
The cost of getting there isn’t trivial. Integrating devices like ventilators and monitors into electronic health records can run $6,500 to $10,000 per hospital bed in upfront costs, plus about 15% annually in maintenance. But set against the scale of the waste it eliminates, the return on investment is hard to argue with.
What This Means for You as a Patient
In practical terms, interoperability determines whether your new doctor already knows your medication list or asks you to recall it from memory. It’s the difference between a specialist seeing your full imaging history and ordering a scan you had two weeks ago. If you’ve ever had to carry a CD of medical images from one facility to another, or fax your own records, you’ve experienced what happens when interoperability breaks down.
You now have a legal right to access all of your electronic health information at no charge. Many hospitals and insurers offer patient portals or support third-party apps that pull your data together using FHIR-based connections. If a provider or health IT company refuses to share your records without a valid reason, that may qualify as information blocking under federal law.
The system isn’t seamless yet. Gaps remain, particularly in how well different organizations integrate incoming data rather than just receiving it, and in how quickly public health infrastructure can adopt newer standards. But the trajectory is clear: health data is becoming more portable, more accessible, and more useful with each year.