Nursing Home Transfer and Discharge Requirements Under 42 CFR § 483.15: A Workflow for 30-Day Notices, Ombudsman Copies, and Hospital Return Rights

In skilled nursing, transfer and discharge problems rarely begin with the notice letter itself. They usually begin earlier, when a hospitalization happens fast, a resident says they want to leave, a return-from-hospital bed question sits unresolved, or the team assumes someone else sent the ombudsman copy. By the time leadership realizes the record is thin, the issue is no longer just operational. It is now survey risk, complaint risk, and resident-rights risk.

That is what makes 42 CFR § 483.15 so operationally important. The rule is not just about whether a facility can transfer or discharge a resident. It is also about timing, documentation, written notice content, bed-hold communication, and whether a resident who went to the hospital is properly permitted to return. In practice, the exposure often comes from fragmented handoffs between nursing, social services, admissions, medical records, and administration.

For operators, the goal is not to memorize every subparagraph. The goal is to build a workflow that answers five questions before a case turns into a fire drill: Is this facility-initiated or resident-initiated? Does one of the permitted bases actually apply? Was the medical record built correctly? Did the required parties get the right notice at the right time? And if the resident went out to the hospital, what is the documented plan for return?

What 42 CFR § 483.15 covers for skilled nursing facilities

42 CFR § 483.15 governs admission, transfer, and discharge rights for residents in Medicare- and Medicaid-participating long-term care facilities. For skilled nursing operators, the most important sections are the limits on when a facility may initiate a transfer or discharge, the medical-record documentation requirements, the notice rules, the bed-hold notice requirements, and the resident’s return rights after hospitalization or therapeutic leave.

CMS survey guidance also makes an important distinction that operators often blur under pressure: the notice requirements at 42 CFR § 483.15(c)(3) through (6) apply to facility-initiated transfers and discharges, not true resident-initiated ones. That distinction matters because many weak files start with a facility calling something resident choice when the record does not actually support that characterization.

The first control point: facility-initiated or resident-initiated?

This is the first branching decision in the workflow, and it drives almost everything that follows. If the facility initiates the move, the notice requirements apply. If the resident or resident representative truly initiates the move, the facility still needs documentation and discharge planning discipline, but the F623 notice path is different.

CMS guidance is especially clear on two high-risk situations. First, a resident’s general statement that they want to go home is not, by itself, a valid notice of intent to leave. Second, an against-medical-advice departure should be investigated carefully. If the evidence shows the resident or representative was forced, pressured, or intimidated into leaving, CMS treats that as facility-initiated, which can trigger the notice requirements and deeper survey scrutiny.

• Do not label a case resident-initiated unless the file contains clear verbal or written notice of intent to leave.
• Do not rely on hallway recollection. Put the resident’s stated intent, date, participants, and discharge-planning discussion into the record.
• Escalate all AMA departures for administrator or designee review before the case is closed as resident-initiated.
• If the facility later decides not to allow return after a hospital transfer, the case can become a facility-initiated discharge even if the original transfer out was emergent.

When a facility may transfer or discharge a resident

A facility cannot discharge for convenience, internal frustration, or because the paperwork is messy. The record has to support one of the permitted bases under the rule. Operationally, this means the file should show both the basis being relied on and the facts supporting it, not just a conclusory sentence.

• The resident’s needs cannot be met in the facility.
• The resident’s health has improved enough that the resident no longer needs the facility’s services.
• The safety of individuals in the facility is endangered due to the resident’s clinical or behavioral status.
• The health of individuals in the facility would otherwise be endangered.
• The resident has failed, after reasonable and appropriate notice, to pay for the stay.
• The facility ceases to operate.

This is where manual workflows often break. Teams document the event, but not the facility’s reasoning, alternatives tried, physician involvement, or why the receiving setting can meet the need. Under the regulation, that missing connective tissue matters.

The 30-day notice rule and the exceptions operators need to control

The default rule is straightforward: for a facility-initiated transfer or discharge, written notice must generally be made at least 30 days before the resident is transferred or discharged. But the exceptions are where the process gets messy, because the rule also allows notice as soon as practicable in specific circumstances.

Those exceptions include situations where the safety of individuals in the facility would be endangered, the health of individuals in the facility would be endangered, the resident’s health improves sufficiently to allow a more immediate move, an immediate transfer or discharge is required by urgent medical needs, or the resident has not resided in the facility for 30 days.

The operator mistake is treating “as soon as practicable” like “whenever we get around to the paperwork.” It is not a cleanup window. It is a narrower timing exception that still requires prompt action, documentation, and a clean handoff to the resident, representative, and, when required, the ombudsman.

What the notice must include

A compliant notice is not just a one-line discharge letter. Under 42 CFR § 483.15(c)(5), the written notice must include the reason for transfer or discharge, the effective date, the location to which the resident will be transferred or discharged, a statement of appeal rights, contact information for the entity that receives appeals, information on how to obtain an appeal form and assistance, and ombudsman contact information. For certain residents with intellectual and developmental disabilities or mental illness, additional protection-and-advocacy contact information is required.

In California, CDPH’s May 28, 2025 AFL-25-17 is especially useful because it restates the required notice content in operator-friendly form and reminds SNFs that notices also apply to discharges that occur while the resident remains in the hospital after an emergency transfer.

• Use a controlled notice template, not free-text letters built from old files.
• Do not send a notice until the destination field is specific enough to be defensible.
• Require a second review for appeal-rights information and contact details before release.
• Store the exact version sent, the date sent, and the method of delivery in the record.

The ombudsman copy is not optional admin cleanup

CMS clarified in Survey and Certification Letter 17-27-NH that facilities must send a copy of the notice of transfer or discharge to the Office of the State Long-Term Care Ombudsman for facility-initiated cases. CMS later incorporated related guidance into Appendix PP, where surveyors are instructed to look for evidence that the ombudsman copy was sent.

That makes ombudsman notice a workflow control, not an afterthought. If your team cannot easily prove when the copy was sent, by whom, and for which notice version, you do not really have a closed-loop process.

The fastest way to create discharge risk is to treat resident notice, representative notice, and ombudsman notice as three separate tasks with no single owner.

Hospital transfers, bed-hold notice, and the right to return

One of the most misunderstood parts of the rule is what happens after a resident leaves for the hospital. A temporary emergency transfer out is still a facility-initiated transfer, and the bed-hold and return-rights workflow starts immediately. Under 42 CFR § 483.15(d), the facility must provide written bed-hold information before transfer policies and again at the time of transfer for hospitalization or therapeutic leave.

Under 42 CFR § 483.15(e), the facility must establish and follow a written policy on permitting residents to return after hospitalization or therapeutic leave. If the hospitalization exceeds the bed-hold period, the resident must be allowed back to the previous room if available or the first available bed in a semi-private room, so long as the resident requires the facility’s services and is eligible for Medicare skilled nursing facility services or Medicaid nursing facility services.

CMS guidance goes a step further: if the facility decides the resident who was transferred out cannot return, that decision functions like a facility-initiated discharge and the facility must comply with the discharge requirements. In other words, a hospital transfer does not give the building a free reset on resident rights.

For California operators, this gets even more practical. CDPH’s August 5, 2025 AFL-25-24 reminds SNFs of federal and state bed-hold rules and specifically notes California’s seven-day bed-hold option when a resident is transferred from the SNF to a hospital. That means your federal workflow and your state-specific packet process need to match.

The hospital-return trap that creates late exposure

A common late-stage failure looks like this: the resident goes out emergently, the bed status is not tracked clearly, the hospital says the resident is ready to return, the building is unsure whether the prior bed is available, someone informally says the resident is now 'more appropriate elsewhere,' and only then does leadership realize there is no clean return-rights decision trail.

That is exactly where manual coordination becomes expensive. The risk is not just a citation. It is delay, family conflict, ombudsman involvement, hospital friction, social-services rework, and a file that now has to be reconstructed under scrutiny.

A practical transfer and discharge workflow for SNF operators

High-functioning facilities treat transfer and discharge as a cross-functional control path, not a social-services-only task. The workflow should start the moment a case becomes even potentially facility-initiated, or when a hospitalization creates a future return-rights decision point.

• Step 1: Triage the event. Identify whether this is resident-initiated, potentially facility-initiated, or a temporary hospital transfer with expected return.
• Step 2: Lock the basis. If facility-initiated, document which permitted basis under 42 CFR § 483.15(c)(1) is being used and what facts support it.
• Step 3: Build the clinical record. Capture physician documentation where required, facility attempts to meet needs, safety or health concerns, and receiving-provider rationale.
• Step 4: Trigger notice workflow. Determine whether the case is on the 30-day path or the as-soon-as-practicable exception path.
• Step 5: Generate the notice from a controlled template. Include all required content, appeal information, destination details, ombudsman information, and any additional advocacy contacts required.
• Step 6: Send all required notices. Resident, representative, and ombudsman distribution should be logged in one place with date, method, and owner.
• Step 7: Manage bed-hold and return rights. For hospital or therapeutic-leave cases, issue the bed-hold notice, track return expectations, and document room or first-available-bed decisions.
• Step 8: Escalate no-return decisions. If the facility believes the resident cannot return, move the case into a formal discharge workflow rather than handling it informally by phone.
• Step 9: Audit weekly. Review open hospital transfers, pending return requests, and discharge files for missing notice elements or weak documentation before surveyors or families find the gap.

Where workflow automation helps without turning ePeople AI into legal counsel

Facilities do not need another static checklist that lives in a binder. They need earlier visibility into which cases are drifting into facility-initiated territory, which hospital transfers are aging without a documented return path, which notices are incomplete, and which required parties have not yet been notified.

This is where an AI operating layer helps. ePeople AI can sit across the workflow, surface exceptions early, chase missing documentation, keep bed-hold and return tasks from stalling between departments, and turn scattered transfer or discharge steps into one visible action queue. The point is not to replace clinical or legal judgment. The point is to make sure operators do not discover a broken file after the risk has already matured.

What smart operators tighten this month

• Review your discharge notice template against the required 42 CFR § 483.15(c)(5) elements.
• Confirm who owns ombudsman notification and what evidence is retained.
• Pull every open hospital transfer and verify bed-hold and return-rights documentation is current.
• Audit any recent AMA or 'resident wanted to leave' files for proof that the case was truly resident-initiated.
• Make sure California-specific bed-hold and discharge packet requirements are not being handled outside the core workflow.

If your team would struggle to answer those questions quickly, the problem is probably not knowledge alone. It is workflow design.

If you want to see how ePeople AI helps skilled nursing operators stay ahead of discharge risk, hospital-return confusion, and missing documentation before the file breaks, book a demo and we will walk through the workflow with your real process in mind.