The hospital-to-SNF transition is one of the most data-intensive moments in a patient's care continuum — and one of the most reliably broken from a health information exchange standpoint. A patient leaves an acute hospital with a discharge summary, a medication reconciliation, imaging orders, and a care plan that a skilled nursing team needs to act on within 24 to 48 hours of admission. What often arrives at the SNF is a faxed PDF, a CD of imaging, and a phone call from a discharge planner.
This isn't a technology problem in isolation. The HL7 FHIR (Fast Healthcare Interoperability Resources) standard, mandated through the ONC's 21st Century Cures Act Final Rule and the CMS Interoperability and Patient Access Final Rule published in 2020, provides a well-defined technical framework for structured clinical data exchange. The gap between what the standard makes possible and what SNFs and post-acute providers actually receive from hospital systems is a function of adoption timelines, implementation incentive misalignment, and some specific characteristics of the post-acute market that make interoperability harder to achieve than in acute settings.
Why FHIR Mandates Haven't Fully Solved the Problem
The 2020 CMS interoperability rules required that hospitals, health plans, and Medicaid programs implement FHIR R4 APIs for patient access and payer-to-payer data exchange. The ONC's rules required that EHR vendors support FHIR-based data export and implement standardized USCDI (United States Core Data for Interoperability) data elements. These are real requirements with compliance timelines that have largely been met by major acute-care EHR vendors.
But here's where the SNF context diverges: the mandates primarily obligated hospitals and health plans. Post-acute facilities — SNFs, home health agencies, LTACH facilities — are on the receiving end of those data flows, but they are not symmetrically obligated senders under the same rules. A hospital is required to make a patient's data accessible via FHIR API; the SNF admitting that patient is required to have a certified EHR (as of the IMPACT Act's requirements for standardized assessment data), but the interoperability obligations placed on SNFs are less extensive than those on acute hospital systems.
The result is an asymmetric landscape: acute systems have built FHIR infrastructure because they were required to, post-acute systems have adopted it more slowly because the direct regulatory pressure was lighter and the vendor market serving SNFs has historically been smaller and more fragmented than the acute EHR market.
The Admission Data Gap: What SNFs Actually Need
The data that a skilled nursing team needs to safely admit and begin caring for a patient covers several domains that don't always flow cleanly through existing ADT (admission/discharge/transfer) notifications and C-CDA (Consolidated Clinical Document Architecture) discharge documents.
Medication reconciliation is the most immediately critical. A patient's home medication list, inpatient medication changes, and any new prescriptions ordered at discharge need to arrive in a form that the SNF pharmacist and admitting clinician can review, reconcile, and load into the SNF's medication administration system without manual re-transcription. When that data arrives as a scanned PDF, the re-transcription step introduces error risk at a moment when the patient is clinically transitioning and potentially unstable.
Functional status data — particularly the CARE tool (Continuity Assessment Record and Evaluation) sections used for post-acute care planning — is a data element that the IMPACT Act specifically requires to be standardized across care settings. In theory, this means that a hospital's assessment of a patient's mobility, self-care capacity, and cognitive function should be expressible in a form that a SNF can import directly into its own assessment workflow. In practice, the implementation of standardized functional data elements across EHR systems is inconsistent, and SNFs frequently rebuild this assessment from scratch on admission rather than importing it from the hospital record.
The third critical data category is pending diagnostic results and follow-up orders. A patient discharged with a pending culture result, an unreviewed imaging study, or a specialist referral in progress may arrive at the SNF without those items being explicitly communicated. When those items arrive weeks later — a lab result that goes to the hospital system rather than the SNF — there's no structured mechanism in most current implementations for routing that information to the current treating team.
The Realistic Current State: What SNFs Can Actually Accomplish
We're not saying that HL7 FHIR is failing — the standards are sound and adoption is genuinely progressing. What we're saying is that SNFs waiting for perfect interoperability to arrive from the acute sector before building their own data reception capabilities are in a passive position that creates ongoing admission quality problems.
Take a mid-size SNF in the Southeast operating with a mix of referral partners. For the subset of referring hospitals that have implemented FHIR Patient Access APIs, the SNF can query for discharge summaries and medication lists using SMART on FHIR applications linked to the patient's consent — if the SNF has built or procured that query capability. For the remaining referring hospitals still sending discharge documentation by fax or via Health Information Exchange (HIE) portals that require manual retrieval, the SNF can implement a structured intake workflow: a dedicated admission coordinator role that retrieves, reviews, and digitizes incoming transition documents within a defined window from admission notification.
Neither of those approaches requires waiting for the acute sector to fully adopt FHIR. Both require the SNF to have an EHR that can receive and structure incoming data from multiple channels and a workflow that assigns explicit responsibility for admission data completeness before the first clinical assessment occurs.
What to Demand from Your EHR Vendor
SNF operators and post-acute practice administrators evaluating EHR platforms for interoperability capability should ask for specifics that go beyond claims about FHIR support.
The FHIR questions that matter: Does the platform support SMART on FHIR app integration, enabling query of external patient data from within the EHR workflow? Does it support incoming FHIR R4 data imports from hospital discharge systems? What USCDI v1 (and v2, now required by ONC) data elements does the platform send and receive in structured form?
Beyond FHIR: Does the platform have Direct Secure Messaging capability for HIE connectivity? Can it parse and import structured C-CDA documents from referral sources, or does it treat all incoming documents as unstructured attachments? Does the care coordination module include transition of care documentation that generates compliant TOC summary documents for MIPS Promoting Interoperability objectives?
For SNFs specifically, ask about MDS data integration: can the platform import functional status data from external assessments in CARE tool format, and does its MDS workflow support the standardized data elements required under the IMPACT Act? These questions surface whether the platform has been built with post-acute data flows in mind or is adapting acute-care infrastructure for a use case it wasn't designed for.
The HIE Layer: An Underutilized Resource
Most states have operational Health Information Exchange networks that aggregate clinical data from participating providers and make it queryable through provider-facing portals and EHR integrations. For SNFs that lack direct FHIR connectivity to major referral hospitals, HIE participation is often the most practical near-term path to receiving structured clinical data at admission.
HIE connectivity varies considerably by state. Some state HIEs have achieved broad hospital participation and offer real-time event notification (ADT feeds) that can alert a SNF when a patient they are expecting has been formally discharged from a hospital. That notification — even if the clinical data it carries is limited — enables the SNF's intake coordinator to query the HIE for available records before the patient physically arrives, rather than beginning data collection from scratch at bedside admission.
The interoperability picture for post-acute care is improving, driven by regulatory pressure, value-based care contracting that creates financial incentive for care transition quality, and an EHR vendor market that is gradually consolidating around platforms with genuine post-acute data exchange capabilities. But the improvement trajectory is measured in years, not quarters. SNFs that build structured data reception workflows now — regardless of what data their referral partners are sending — are better positioned to absorb improved data flows as they materialize than those waiting for the infrastructure to solve the problem on their behalf.
