58% of US hospitals still can't fully use outside patient data in real time, ONC figures show
Nearly every hospital now exchanges some health data electronically, but federal interoperability data shows most still can't pull outside records into clinical workflows in real time — a gap with direct patient-safety and cost consequences.
Direct answer: According to federal interoperability data from the Office of the National Coordinator for Health IT (ONC), roughly 70% of U.S. hospitals exchange health information electronically with outside providers at least sometimes, but only about 42% actually integrate that outside data into clinical care processes — meaning close to 58% of hospitals still can't reliably use real-time outside patient data at the point of care.
What happened
Hospital EHR adoption is effectively universal at this point, and electronic exchange of health data with outside providers has climbed steadily for years. But ONC's own quickstats data on hospital electronic health information exchange shows a persistent, well-documented gap between hospitals that can send and receive data and hospitals that can actually use that data inside a real-time clinical workflow.
Key facts and numbers
- Around 70% of non-federal acute care hospitals report exchanging health information electronically with outside providers at least sometimes.
- Only about 42% report integrating that externally received data into their clinical care processes — the step that actually makes it useful to a clinician mid-visit.
- The U.S. national interoperability rate lags well behind international peers with more unified health data systems, such as Estonia and Denmark, both of which report interoperability rates above 98%.
- Nine in ten hospitals now enable patient access to a third-party app via API, and seven in ten do so through a standards-based API — connectivity has genuinely improved even where integration hasn't kept pace.
Why it matters
A hospital that can technically "receive" a referral record but can't surface it inside a clinician's workflow in real time hasn't actually solved the interoperability problem — it's just moved the bottleneck from data transmission to data usability. That gap shows up as duplicate tests, delayed diagnoses when outside records aren't checked in time, and clinicians making decisions without the full picture, even when the missing information technically exists somewhere in the system.
The technology behind the gap
The shift closing this gap is the same one reshaping enterprise data more broadly: moving from batch, document-based exchange (a PDF summary sent after the fact) toward standards-based, real-time API access (FHIR-based data pulled live during a visit). Hospitals with modern, API-first data architecture are the ones actually closing the integration gap — legacy, batch-oriented systems are where the 58% figure concentrates.
What businesses should do next
Healthcare organizations sitting on the wrong side of this gap don't need a new interoperability mandate to act — the standards (FHIR-based APIs) already exist and are already required for certified EHR technology. The real blocker is usually internal: legacy data architecture that can receive a file but can't surface it live inside a clinical workflow. That's an integration and data-architecture problem, not a policy problem.
What happens next
Expect continued regulatory pressure (through ONC's certification and information-blocking rules) to push the remaining gap closed, alongside growing use of AI-based clinical summarization tools that make outside records genuinely usable inside a visit, not just technically available somewhere in the chart.
Frequently asked questions
What percentage of hospitals can't share patient data in real time? About 58% of U.S. hospitals don't fully integrate outside patient data into clinical care processes, even though roughly 70% technically exchange data electronically at least sometimes, according to ONC data.
Why is there a gap between hospitals exchanging data and hospitals using it? Exchanging data (sending or receiving a file) and integrating it into a live clinical workflow are different technical problems — many hospitals have solved the first without solving the second, often due to legacy, batch-oriented data systems.
How does the US compare to other countries on healthcare interoperability? The US lags well behind countries like Estonia and Denmark, which report interoperability rates above 98%, reflecting those countries' more unified national health data infrastructure.
What technology closes this gap? Standards-based, real-time APIs (commonly FHIR-based) that pull outside records directly into a clinician's workflow during a visit, replacing older batch or document-based exchange methods.
Does this affect patient safety? Yes — when outside records aren't available in real time, clinicians can order duplicate tests, miss relevant history, or make decisions without a complete picture, even when the needed information technically exists elsewhere in the healthcare system.
Cor Advance Solutions builds modern, connected data platforms for healthcare organizations moving off legacy, batch-based systems. See our healthcare unified data platform case study or explore our Data Warehousing & Analytics services.
Source: ONC — Electronic Health Information Exchange by Hospitals
More Industry Updates
See How This Applies to Your Business
Talk to our team about what this shift means for your roadmap.
Schedule Free Consultation