Quick answer
A return to an SNF can start a new PDPM payment stay while continuing the same Medicare benefit period. Review the three-day interruption window, the 30-day qualifying-stay/readmission rule and the 60-day benefit-period break separately. The return date, facility identity, physical departure and skilled-care history determine different parts of that analysis.
One “new stay” switch cannot answer three questions
The three clocks describe different things. A fresh encounter number is a record-management choice; it is not evidence that Medicare benefit days or payment-day counts should restart.
| Clock | Question | Source boundary |
|---|---|---|
| PDPM interruption | Does the payment stay continue at the same SNF? | Three-day interruption window; facility identity matters |
| Qualifying stay/readmission | Can the earlier qualifying hospital stay support the return? | 30-day rule with applicable exceptions and other coverage conditions |
| Benefit period | Has the prior benefit period ended? | 60 consecutive days meeting the break requirements |
The first two rules are addressed separately in CMS Claims Processing Manual, Chapter 6, sections 120.2 and 40.3.2. The benefit-period rule is in CMS General Information Manual, Chapter 3, sections 10.4.2–10.4.4. This is Original Medicare analysis; MA contracted payment must be checked separately.
Establish the interruption window precisely
For a physical departure, the first noncovered day is the departure day. If Part A coverage ends but the person remains in the facility, it is the day after the final covered day. The window ends at 11:59 p.m. on the third consecutive noncovered day. Return to the same SNF within that window continues the payment stay; return outside it or to another SNF creates a new payment stay under the cited rule.
Do not turn that window into an elapsed 72-hour stopwatch. Calendar-day boundaries and the first noncovered day control the exercise. Nor does the payment-window rule independently decide consolidated-billing responsibility during the absence.
Four returns with an answer key
These are original fictional examples. Assume covered Part A care before the interruption, correct event evidence, applicable coverage conditions independently met on return, no relevant waiver, and no other intervening events. “New payment stay” below is a payment-model result, not a coverage approval.
| Case | Events | Payment-stay result | Benefit-period result from these facts |
|---|---|---|---|
| A | Physically leaves SNF-A November 10; returns there November 12 at 6 p.m. | Window is November 10–12; continuation | No 60-day break; existing period continues |
| B | Same departure; returns to SNF-A November 13 at 9 a.m. | Outside window; new payment stay | Still no 60-day break |
| C | Same departure; admitted to SNF-B November 11 | Different facility; new payment stay | Transfer alone does not end existing period |
| D | Final covered day November 10; remains in SNF-A; covered care resumes November 13 | First noncovered day November 11; within November 11–13 window | No 60-day break |
Case A and Case D have different window start dates even though November 10 appears in both records. This is why a screen needs separate fields for actual departure and final covered day.
For Case B, the usual 30-day readmission question and the 3-day payment question reach different conclusions. Being outside the PDPM window does not, by itself, require a new qualifying hospital stay. A return after more than 30 days raises the separate qualifying-stay requirement; it still does not prove that a 60-day benefit-period break occurred.
The counterexample that catches a false benefit reset
Suppose a fictional resident exhausts Part A benefits and continues receiving the relevant skilled level of care in the SNF for 40 days. A system starts a 60-day “new benefits” countdown on the first unpaid day. That is the wrong starting assumption. The benefit manual explains that skilled-level care can prolong the period even when Part A payment has ended.
A change in payer is therefore insufficient evidence for a break. Conversely, remaining physically in a nursing facility does not by itself prove that the relevant skilled-level criteria continued. The level of care and applicable institutional facts need their own review.
Record three conclusions, then connect billing
A compact return record needs the physical departure, last covered day, return timestamp, sending and receiving facility identities, relevant skilled-care history and three separate reviewed conclusions. Keep a reserved-bed flag outside these conclusions; it is not a Medicare utilization determination.
When a return date is corrected, reopen the affected clock reviews without overwriting already submitted claims. The resulting work should name the affected claim periods and calculation versions. If only the payment clock changes, do not manufacture a new benefit period to make the screens agree. A system passes this conceptual test when it can represent the different outcomes in Cases A–D without forcing all counters to reset together.
Questions & answers
Can a new PDPM stay still use the old Medicare benefit period?
Yes. A return outside the PDPM interruption window can create a new payment stay without the 60-day break needed to end the benefit period.
Does benefit exhaustion start the 60-day clock automatically?
No. Continuing skilled-level care can prolong the benefit period even when Part A payment has ended. The actual care and inpatient history need review.
Does a return to another SNF continue the PDPM stay?
The cited interrupted-stay rule treats a return to a different SNF as a new payment stay. That does not automatically create a new benefit period.
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.