Quick answer
A useful hospital partnership packet proves what a particular SNF can provide, when it can provide it and how information will move. Date every capability and measure, identify limits and test the transfer workflow. Preserve patient choice and disclose relevant relationships. A preferred-network label is not a guaranteed referral stream or evidence that every resident is appropriate.
A hospital evaluating a post-acute partner needs evidence that survives a real transfer. A brochure may describe a service that is unavailable on weekends, a public measure may cover a different period from a local dashboard, and a portal connection may not deliver the documents staff need. A useful packet makes those differences visible before commitments are signed.
The hospital discharge-planning rule calls for relevant quality and resource-use information, necessary medical information at transfer, available post-acute options and patient choice. Those are hospital obligations that help explain the evidence a SNF partner should prepare. Current section 482.43 places the post-acute choice requirements in paragraph (d); paragraph (c) now addresses transfer protocols. 42 CFR 482.43.
Build a facility-specific evidence matrix
Use one row per claim, with the site, supporting record, responsible verifier, effective date, review date and limitation. An enterprise-level claim must not silently apply to facilities that lack the same capability.
| Claim under review | Evidence to obtain | Limitation to show |
|---|---|---|
| A service can be provided | Current approved capability and qualified coverage | Hours, equipment, supply or clinical exclusions |
| A bed may be available | Named source and timestamp for current status | Subject to resident assessment and readiness confirmation |
| A quality result is favorable | Measure definition, period, denominator and provenance | Small samples, exclusions and comparability limits |
| Records can be exchanged | Completed sender-to-recipient test | Required documents, access hours and failure route |
| A concern receives follow-up | Defined escalation route and tested contacts | Coverage gaps and expected acknowledgment process |
This is an original packet structure, not a CMS network-approval form. Keep the underlying evidence accessible to authorized reviewers rather than filling the packet with unsupported labels such as “comprehensive” or “seamless.”
Test a claim that changes with time
Suppose a fictional facility can support a service on weekdays but is awaiting weekend coverage. The packet should state the current window and the decision point for exceptions. A planned staffing arrangement belongs in a separately identified future capability, with no implication that it is available today.
Have the hospital reviewer select a Friday-evening case. The SNF team should identify who can assess suitability, confirm the actual service window and communicate a decision. If the test succeeds only because an executive happens to answer a personal phone, revise the operating commitment before using it in the agreement.
Make data claims reproducible
For an internal readmission result, identify the starting cohort, observation window, numerator, denominator, exclusions and data source. Do not place a locally defined rate beside a public measure as if the methods were identical. Show the dates and explain any missing follow-up. Rating methodology belongs in the relevant quality guidance; the partnership packet's job is to preserve provenance and comparability.
For exchange, use synthetic residents to test transfer documents, corrected records and after-hours retrieval. A successful login proves less than receipt of the right resident's complete, current information. Record what happens when the sending hospital cannot deliver an attachment and who closes the loop.
Preserve choice in the commercial agreement
Separate a commitment to communicate and maintain accurate capability information from a volume promise. Review financial relationships, any service or technology transfers, and the language used when presenting options. The hospital rule addresses disclosure of specified financial interests and prohibits limiting the qualified providers available to the patient.
The purchasing consequence is concrete: require facility-level capability records, dated measure exports and evidence of exchange tests. A dashboard that aggregates everything to the enterprise level may obscure the very limits a partner needs to know.
Ease's skilled nursing offering is planned. Any partnership-management or information-sharing functionality would need to be established and demonstrated before it could support these commitments.
Questions & answers
What belongs in a SNF preferred-network packet besides quality ratings?
Include verified service capability, operating windows, admission limitations, current availability contacts, data definitions and tested information-transfer responsibilities. Keep public measures distinct from internally calculated results.
Can a preferred hospital network promise the SNF all suitable discharges?
A partnership must be structured consistently with patient choice and other applicable rules. Hospital discharge-planning requirements do not permit a preferred label to eliminate other qualified options available to the patient.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.