Skip to main content

Interoperable Exchange of Patient Health Information Among U.S. Hospitals in 2023

A digital representation of the globe with interconnected data points symbolizing global data exchange.
Greg Wahlstrom, MBA, HCM

2026 executive update · hospital interoperability patient access · Leadership action

Interoperable Exchange of Patient Health Information Among U.S. Hospitals in 2023

ONC’s 2023 hospital interoperability data showed meaningful progress and an equally important use gap. Seventy percent of non federal acute care hospitals reported engaging at least sometimes in all four…

Greg Wahlstrom, MBA, HCMBlog

At a Glance

For executives, the difference between availability and use is the real operating challenge. A network connection, portal, interface, or document feed does not improve care if information arrives too late, remains outside the normal workflow, contains duplicative noise, cannot be trusted, or is inaccessible to the…

Executive perspective

ONC's 2023 hospital interoperability data showed meaningful progress and an equally important use gap. Seventy percent of non-federal acute care hospitals reported engaging at least sometimes in all four domains of interoperable exchange: send, receive, find, and integrate. Yet only 43 percent reported doing so routinely. Seventy-one percent reported routine access to needed outside clinical information at the point of care, while only 42 percent said clinicians routinely used it when treating patients.

For executives, the difference between availability and use is the real operating challenge. A network connection, portal, interface, or document feed does not improve care if information arrives too late, remains outside the normal workflow, contains duplicative noise, cannot be trusted, or is inaccessible to the patient. Interoperability becomes valuable when a clinician can find the right external result during a decision and when a patient can get, understand, correct, and share a usable record.

This playbook focuses on frontline information exchange and patient access. It is intentionally distinct from an enterprise benchmark exercise. The unit of improvement is a real care journey, not a connectivity statistic.

Leadership priorities

Build an integrated leadership response

Select High-Risk Care Journeys

Begin with clinical moments where missing outside information creates clear harm, delay, duplication, or frustration. Examples include emergency evaluation, medication reconciliation, oncology referral, transfer from a skilled nursing facility, behavioral health crisis, high-risk pregnancy, post-discharge follow-up, and care for a patient who receives services across competing systems. Select two or three journeys with measurable baseline defects.

Map the information needed at each decision. An emergency clinician may need allergies, active medications, recent imaging, problem list, and advance directives. A primary care team may need the discharge summary, pending tests, medication changes, and follow-up plan. Ask whether staff can find the information, whether it is integrated without manual re-entry, how they judge recency and source, and what happens when the exchange fails.

Include the patient and caregiver path. Determine what information they can see, download, transmit, and correct before and after the encounter. Test identity verification, proxy access, language, accessibility, mobile usability, and support. A patient who must print a portal screen or repeat a history is exposing an interoperability defect.

Set a bounded aim, such as reducing medication discrepancies after outside discharge or increasing use of external information during emergency care. Connectivity activity can support the aim, but it should not replace the patient and workflow outcome.

Put External Information Inside the Clinical Workflow

Observe clinicians using the current tools. Count logins, clicks, searches, duplicate documents, unmatched records, interrupted sessions, and time spent deciding which source is current. Identify where an external-data alert appears and whether the clinician can act without leaving the workflow. Direct observation often explains why nominal access is not routine use.

Design role-specific summaries. Present provenance, date, author or source organization, and reconciliation status. Prioritize clinically relevant changes rather than inserting every outside record into one undifferentiated list. Preserve the underlying document and allow deeper review. Avoid silently overwriting local data with external information.

Create a reconciliation workflow with clear accountability. Pharmacy, nursing, clinicians, health information management, or another role may validate different data types. Define what can be accepted automatically, what requires review, how conflicts are displayed, and how a corrected value reaches orders, notes, decision support, and the patient-facing record. Measure unresolved items and time to reconciliation.

Build downtime and no-match procedures. Staff should know how to query another route, contact the outside organization, document uncertainty, and escalate urgent gaps. Review failed exchanges and false matches as safety events when appropriate. Reliable use depends on knowing what to do when the preferred connection does not work.

Reduce cognitive burden deliberately. External records can contain repeated notes, copied problem lists, obsolete medications, and multiple versions of the same result. Convene frontline users to define relevance, sorting, suppression, and alert thresholds for each priority journey. Monitor whether summarization or filtering hides important context. The goal is a faster clinical decision with traceable source information, not simply fewer documents on the screen.

Capture use through workflow evidence and structured feedback. A login or opened document does not prove that information changed care. Sample cases to learn whether clinicians avoided duplicate testing, corrected medication, accelerated diagnosis, or confirmed a safe plan. Also record when outside data were misleading, too late, or unnecessary so the design can improve without overstating benefit.

Designate frontline champions on every shift to collect defects, coach peers, and escalate urgent exchange failures during the initial stabilization period.

Close Exchange Gaps Beyond Hospitals and Clinics

ONC found much less broad exchange with long-term and post-acute care and behavioral health providers than with hospitals and ambulatory practices. Those gaps are clinically consequential because transitions often involve medication changes, functional status, behavioral health plans, consent, caregiver information, and time-sensitive follow-up.

Choose partners based on patient flow and risk. Map the organizations that send or receive the most high-risk patients, then assess their technical capability, staffing, record format, network participation, consent workflow, and response time. A smaller partner may need a portal, Direct messaging, structured referral, or shared care-plan workflow before advanced API exchange is realistic.

Agree on a minimum transition dataset and timing. Include diagnoses, medications, allergies, recent results, functional and cognitive status where relevant, treatment plan, pending actions, responsible clinician, and contact route. Behavioral health and substance-use information requires careful application of HIPAA, 42 CFR Part 2, state law, consent, and role-based access. Privacy review should enable lawful care coordination while protecting sensitive information.

Test both directions. Many programs focus on sending a discharge summary without confirming that the receiving team can retrieve, interpret, and incorporate it. Require acknowledgement for priority transitions and track whether the follow-up action occurred. Escalate partners and workflows with repeated nonreceipt or incomplete data.

Make Patient Access a Core Exchange Pathway

Patients have rights to access health information under HIPAA, and federal health IT policy supports secure electronic access and exchange. Treat the patient as an active participant, not a backup courier. Offer straightforward view, download, transmit, and request-correction functions with clear support for people who cannot or do not wish to use a portal.

Reduce identity and proxy friction. Use reasonable verification that protects privacy without creating unnecessary delay. Test caregiver, guardian, adolescent, deceased-patient, and other representative scenarios under applicable law and policy. Make proxy status and expiration understandable. Provide interpreter and accessibility support across enrollment and use.

Explain external information. Label the source, date, and whether the local team has reconciled it. Give patients a simple route to report a duplicate, incorrect medication, wrong demographic link, or missing result. Route corrections to an accountable team, communicate the outcome, and propagate approved changes where required. A downloadable record that no one can correct is incomplete access.

Measure successful use, not portal invitations. Track logins, downloads, transmissions, API connections, proxy use, support calls, abandoned identity verification, correction requests, fulfillment time, and disparities. Pair utilization with patient feedback about whether the information helped them prepare, coordinate, or make a decision.

Operate Exchange as a Reliability Program

Create a cross-functional exchange operations group including clinical informatics, frontline care, health information management, information technology, cybersecurity, privacy, compliance, patient access, quality, and partner relations. Give it authority to resolve workflow and partner barriers. Separate production reliability from longer-term network strategy so urgent defects receive prompt attention.

Monitor end-to-end performance. Include query success, patient-match rate, message and document delivery, integration latency, duplicate volume, reconciliation backlog, external-information use, patient access, and partner acknowledgement. Segment by site, shift, care journey, vendor, and partner type. A high enterprise average can conceal a broken rural, night, behavioral health, or post-acute pathway.

Apply information-blocking review to policies and practices that may interfere with access, exchange, or use of electronic health information. Train teams on approved escalation and applicable exceptions. Legal and compliance analysis should guide decisions, but a generic privacy concern should not automatically stop lawful exchange.

Use TEFCA and other exchange networks as means, not outcomes. Evaluate whether participation closes priority journeys, reduces one-off connections, supports individual access, and improves reliability. Validate cybersecurity, identity, consent, directory, and incident-response requirements. Retire redundant routes only after the replacement performs reliably in representative conditions.

Leadership cadence

Start, strengthen, and measure the system in 90 days.

Start

Phase 1, days 1 to 30

Select two high-risk journeys, observe frontline and patient workflows, establish baseline availability and actual use, map top exchange partners, and identify the highest-impact failure points.

Strengthen

Phase 2, days 31 to 60

Redesign summaries, reconciliation, patient correction, partner handoffs, and downtime escalation. Configure a bounded test, train representative teams, and validate privacy, security, identity, proxy, and information-blocking controls.

Measure

Phase 3, days 61 to 90

Run the test across different shifts and patient scenarios, review reliability weekly, correct defects, and approve a scale plan tied to clinical use, patient access, transition completion, and partner performance.

Decision-grade measurement

Decision-Grade Metrics

  • External-information availability and actual use at priority clinical decisions
  • Query success, patient-match accuracy, integration latency, and duplicate volume
  • Medication, result, and problem-list reconciliation completion and aging
  • Transition records received, acknowledged, and acted on by partner type
  • Patient view, download, transmit, API, proxy, and correction-request performance
  • Access and use by site, shift, language, disability, geography, and digital access
  • Exchange-related safety events, downtime escalations, complaints, and repeat defects

SEO

SEO title: Hospital Interoperability: Frontline and Patient Guide
Meta description: Turn hospital interoperability into frontline clinical use and patient access through better workflows, transitions, reconciliation, and reliability.
Focus keyphrase: hospital interoperability patient access

Conclusion

Turn strategy into an accountable operating system.

The 2023 ONC data showed that hospital interoperability had expanded, but routine clinical use still lagged access. The next leadership frontier is not another connection by itself. It is making outside information visible, trustworthy, actionable, and easy to reconcile during real care.

Patient access belongs in the same operating model. When clinicians and patients can find, understand, correct, and share information across transitions, interoperability becomes a care capability rather than a technical achievement. Executives should measure that lived result.

Executive questions

Frequently Asked Questions

1. What is the difference between information availability and use?

Availability means needed external information can be accessed electronically. Use means clinicians actually retrieve and apply it during care. Workflow fit, relevance, trust, latency, identity matching, and reconciliation determine whether availability becomes use.

2. Which interoperability workflow should a hospital improve first?

Choose a high-risk, high-volume journey with measurable harm or delay from missing information. Emergency care, medication reconciliation, post-acute transfer, behavioral health transition, and outside discharge follow-up are common starting points.

3. Should all external data automatically overwrite the local record?

No. Preserve provenance and apply clinical and data-governance rules. Some information can integrate automatically, while conflicts or high-risk elements need reconciliation. Silent overwrite can introduce error.

4. How does patient access support interoperability?

Patients can review, correct, download, transmit, and share their information across providers and caregivers. A reliable access pathway also reveals identity, proxy, usability, and data-quality defects that organization-to-organization exchange can miss.

5. Is joining an exchange network enough to claim success?

No. Network participation is infrastructure. Success requires reliable queries, accurate matches, useful information in workflow, completed transitions, patient access, lawful exchange, and measurable improvement in care.

Related Blogs