This is the interoperability problem, and it's not just a hospital issue. Certified EHR adoption sits at 99.4% among U.S. acute care hospitals, according to ONC's 2024 data brief—yet having a system isn't the same as having a connected one. Interoperability is what lets health data move securely between platforms and actually mean the same thing wherever it lands, whether that's a hospital, a pediatric office, or a school health office.
This guide covers what interoperability really means, the four recognized levels, the HL7/FHIR standards behind it, and where the biggest gaps—and fixes—still exist.
Key Takeaways
- Interoperability means systems exchange and correctly interpret health data, not just transfer files
- Four levels—foundational, structural, semantic, and organizational—set how deeply systems can share usable care data
- HL7 and FHIR standards enable CMS-mandated data-sharing rules across U.S. healthcare
- School health platforms use the same principles so nurses, parents, and students share one usable student health record
What Does It Mean for Electronic Health Records to Be Interoperable?
HIMSS defines interoperability as the ability of different systems to "access, exchange, integrate and cooperatively use data in a coordinated manner...to provide timely and seamless portability of information."
That's a mouthful, so here's the simpler version: an EMR is one provider's internal record. An EHR is meant to follow the person across providers. An interoperable EHR is what actually makes that following-the-person part real, instead of theoretical.
Three things have to be true for interoperability to count as real:
- Security: data only reaches authorized recipients
- Functionality: the transfer arrives accurate and complete
- Usefulness: the receiving system can act on the data, not just store it
In school health, this looks like a nurse's visit note or medication log showing up correctly for a parent, and—when needed—getting shared with the student's primary care provider without a fax machine involved.
The gap between having an EHR and having interoperability is wider than most people assume. A 2025 JAMA Network Open study of 8,122 family physicians found:
- Only 19% reported ideal interoperability for outside encounter documents
- Just 8% reported it for test results
- Fewer than 15% reported ideal interoperability overall
Adoption is nearly universal. Real interoperability isn't.
What Are the Four Types of Interoperability in Healthcare?
HIMSS breaks interoperability into four progressive levels. Each builds on the one before it, and each shows up differently in a district.
Foundational Interoperability
This is the baseline: one system can send data to another and the data arrives intact. The receiving system doesn't need to interpret anything yet. A roster file landing in a school health platform from the student information system is this level.
Structural Interoperability
Here, data format and organization get standardized. Fields, syntax, and structure are consistent enough that information doesn't get scrambled or lost between systems. Think of it as agreeing on where the "allergy" field goes and what it should contain, so a transferring student's allergy doesn't arrive buried in a free-text note.
Semantic Interoperability
At this level, systems don't just transfer data. They share the same meaning. A "penicillin allergy" coded in one system is understood identically in another, thanks to standardized vocabularies and coding systems. Without semantic interoperability, structured data can still get misread — which is how a documented allergy becomes a blank field at a new school.
Organizational Interoperability
The fourth type covers governance, policy, and workflow alignment between organizations: the human and legal side of data sharing, and the level where a district and a clinic have to agree who may share what about a student.
This is where schools and healthcare providers have to align under FERPA and HIPAA at the same time. School nurses generally fall under FERPA, while clinical providers fall under HIPAA. Getting this wrong doesn't corrupt data; it creates compliance risk.
HL7 and FHIR Standards Explained
Two acronyms dominate conversations about healthcare data exchange: HL7 and FHIR.
HL7 (Health Level Seven) is the standards organization behind healthcare messaging protocols. Its HL7 v2 messaging standard, last significantly updated in 2011, has handled clinical data exchange between systems for decades. It works, but it's rigid and often requires custom interfaces between vendors.
FHIR (Fast Healthcare Interoperability Resources) is HL7's modern standard for the same problem. Built on web standards like JSON and REST APIs, FHIR represents health information as reusable "resources" that fit modern software architecture the way most other APIs do. The Office of the National Coordinator (ONC) has positioned FHIR as the path to align healthcare data exchange with broader internet practices.
That shift is now written into regulation. The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), finalized in January 2024, mandates FHIR-based APIs for payers. Covered organizations include Medicare Advantage plans, state Medicaid/CHIP programs, and Qualified Health Plan issuers.
| Requirement | Compliance Date |
|---|---|
| Operational prior-auth timelines (72 hrs expedited, 7 days standard) | January 1, 2026 |
| Public reporting of prior-auth metrics | Begins 2026, first report March 31, 2026 |
| Patient Access, Provider Access, Payer-to-Payer, Prior Auth APIs | January 1, 2027 |
| MIPS electronic prior-auth measure for clinicians | CY 2027 |
The rule targets payers directly. It does not set a separate FHIR deadline for individual providers, though clinicians will need certified EHR technology to meet the new reporting measure. Schools are not covered by CMS-0057-F, so no district has a deadline here. It still matters indirectly: as the clinics and plans around a district standardize on FHIR, the pipes that could one day carry an immunization record or a provider order into a student health record get more consistent.
Why Interoperable EHRs Matter for Schools: Core Benefits
The case for interoperability isn't abstract. It shows up in safety, cost, and daily administrative work.
Core benefits include:
- Safer care — Missing allergy, medication, or diagnosis data drives preventable errors. A Boston hospital pilot found duplicate testing in 32% of transferred patients, with clinically unnecessary duplication in 20%—about $14.77 per admitted patient in that sample.
- Less admin drag — Faxing, re-keying, and manual follow-up pull staff off care. 43% of hospitals report extra costs just to exchange data outside their system, per ONC's 2021 hospital data.
- Tighter coordination — Providers, nurses, and parents work from the same live record instead of chasing updates after the fact.
- Lower waste — With more than 14 billion lab tests ordered yearly in the U.S., cutting redundant orders through shared data reduces avoidable spend at scale.
How This Plays Out in School Health
Those same pressures show up in school health offices: fragmented forms, delayed parent updates, and records trapped in one building. MyCabinet School Health applies interoperability at that level through its connected Nurse Portal, Parent App, and Parent Web Portal:
- Medication logs, visit notes, and health forms stay visible to authorized parents and nurses—no paper or fax
- Automated emails prompt parents to submit forms digitally, ending scattered "inbox scavenger hunts"
- Nurses review and approve submissions in the Nurse Portal; approved files attach straight to the student record
- Parents get real-time push or email alerts when a clinic visit or medication dose is recorded
Cobb County School District's superintendent said digitized documentation eases nurse workload and called parent visibility into clinic visits a clear win for families and the district. The throughline is simple: health data follows the student instead of sitting in a single filing cabinet.
Solutions and Challenges to Achieving EHR Interoperability
Interoperability sounds simple in theory. In practice, three problems keep showing up.
The challenges:
- Inconsistent data structures: 72% of hospitals struggle more when exchanging across vendor platforms; 64% say partner systems can't receive the data sent (ONC, 2021)
- Vendor lock-in and proprietary formats: 54% of hospitals needed customized interfaces to exchange data with outside organizations (ONC, 2021)
- Privacy and compliance complexity: HIPAA and FERPA don't automatically align, especially in schools, where both frameworks apply to different people handling the same child's data
The solutions:
- Adopt FHIR-based APIs to standardize the format and reduce custom-interface dependency
- Move to cloud-based platforms built for exchange rather than retrofitted legacy systems
- Implement role-based access controls so data sharing stays limited to what's necessary and consented
Purpose-built platforms can sidestep some of this friction by designing workflows around one setting's compliance needs from day one.
MyCabinet, for instance, restricts parent access to their own child's information only and limits nurse access to what's needed for care. Broader sharing happens only when legally required or during a safety emergency. That's organizational interoperability built into the architecture rather than bolted on afterward.
Frequently Asked Questions
What is the CMS interoperability rule 2026?
CMS-0057-F requires payers like Medicare Advantage and Medicaid managed care plans to meet operational prior-authorization timelines (72 hours expedited, 7 days standard) and begin public reporting by 2026. Full FHIR-based API requirements for payers follow in 2027.
What are some solutions for EHR interoperability?
Adopting FHIR-based APIs, moving to cloud-based platforms, and standardizing data structures are the leading fixes. Role-based access controls also help keep data sharing secure and compliant.
What are HL7 and FHIR standards?
HL7 is the standards organization behind healthcare data exchange, with HL7 v2 as its legacy messaging protocol. FHIR is HL7's modern, API-based standard built on web technologies like JSON and REST.
What are the four types of interoperability in healthcare?
The four types are:
- Foundational: basic data transfer between systems
- Structural: data in a standardized format
- Semantic: shared meaning of clinical terms
- Organizational: governance and policy alignment across organizations
What does it mean for electronic health records to be interoperable?
It means systems can securely exchange health data and correctly interpret it so the information is usable wherever it lands, from a hospital to a school nurse's office.
