SNF Admissions Workflow: Connect Referrals, Bed Readiness and Actual Arrival

Follow one referral through the actual handoffs

Clinical suitability, resident rights and financial eligibility require qualified review under applicable procedures. This guide organizes the administrative record supporting those decisions. It is not a list of admission criteria.

Create a stable referral ID independent of submission count. If the hospital sends a revised packet, attach it to the same opportunity when appropriate under the facility's matching process. A return episode for an existing resident can still be a new referral opportunity; person, referral and stay are different units.

The AHRQ On-Time transfer and intake report handouts identify structured transfer and intake information used in nursing-home reporting. The original ledger below extends that idea to administrative continuity; it does not replace clinical transfer information or local intake procedures.

Use an event ledger with distinct open work

Here is a fully synthetic Friday-to-Saturday case:

This sequence prevents three common false conclusions: a new upload is not automatically a new referral, a file receipt is not verification, and arrival does not erase unfinished work.

Each event needs source, observed or received time, and reference to the previous state. Corrections should be distinguishable from genuine changes. An incorrectly typed 10:00 estimate and a source-reported transport delay are different explanations for the same changed field.

Make missing information recoverable

Record the specific requested item, source contact route, prior attempts, expected receipt location and person qualified to verify the response. “Needs records” does not explain what the next coordinator should do. Keep clinical content and sensitive details in approved systems; use references in general coordination views.

Distinguish four queues: not yet requested, awaiting source response, awaiting internal verification and awaiting correction. Their ages answer different questions. A referral received five days ago with a request sent yesterday has both a five-day referral age and a one-day response wait. Do not select whichever clock makes the backlog appear newer.

If the document already exists in a shared system but the current owner cannot find it, investigate retrieval and access before repeatedly asking the source to resend it. The useful question is where the handoff failed.

Make the bed board agree with the event ledger

Suppose a fictional facility has 100 beds: 90 occupied, six empty and confirmed ready, four empty with unresolved blocks. The confirmed-ready count is six, not ten. Two of the six are assigned to expected arrivals; show that future commitment separately. It should not turn the current occupied count into 92.

Have the responsible teams define whether and how pending assignments affect what can be offered. Preserve approved blocks during routine data refresh. A vacancy feed should not clear a deliberate readiness constraint simply because no resident is assigned.

Store both operational confirmation time and source refresh time. If a dashboard refreshes at noon using a 09:00 readiness decision, users need that distinction. When the transport plan becomes uncertain, update the expectation and its recheck action without inventing an actual arrival.

Transfer responsibility across the weekend

The incoming coordinator should be able to answer: what is unresolved, what was last attempted, where a response will appear, what action is authorized and who handles a question beyond that authority. A generic “received” message does not establish that access and context are sufficient.

The workflow-planning sections of ONC Health IT Playbook provide general implementation context. In this case, the practical test is a different user continuing F21 without a private explanation from its creator.

An independent facility may have one covering coordinator; test that person's access and backup contact. A group must establish whether central admissions or the receiving site owns each item after transfer. Visibility in two queues can create an ownership gap if each team assumes the other acts.

Keep the arrival transition from closing the wrong work

After actual arrival, preserve the source referral and attach outstanding administrative tasks to the appropriate episode workflow. A closed referral stage should not hide a missing-document request. Likewise, copying every old task into a new stay can import obsolete work; give each item an explicit disposition.

Contact routing also needs an approved purpose and verified role. A person's position as primary contact should not automatically determine every communication. Apply the facility's privacy and authority processes to the actual situation; the software should implement those decisions faithfully.

During procurement, ask the supplier to replay the entire ledger, including the unreadable document and shift change, using ordinary roles. Inspect the final referral count, arrival count, bed state and open task. Passing only the fully prepared arrival case does not answer whether the workflow survives ordinary uncertainty.