Detailed Notice of Discharge: what it means and what to do

The hospital's stated reasons for a discharge decision, sent after a beneficiary requests QIO review. Same posture as the DENC — not itself separately appealable.

A Detailed Notice of Discharge is the hospital's own written case for why your parent is medically ready to leave, sent to the QIO once you've requested a fast appeal of the discharge decision.

It arrives quickly — the QIO's own 1-day clock depends on having it.

As with the DENC, this is the hospital's own reasoning, not an independent judgment — the whole reason an independent QIO review exists.

Reading it closely usually tells you exactly what the QIO's 1-day decision will turn on — whether the hospital is pointing to a specific change in your parent's condition, a completed course of treatment, or a discharge plan it considers ready. Comparing that stated basis against what's actually happening day to day is often the single most useful thing you can do while waiting for the decision.

Because this notice arrives fast — the QIO's own 1-day clock depends on having it — it's worth asking a nurse or case manager directly whether it's already been sent if you haven't seen it yet, rather than assuming the review is delayed.

Read it for the hospital's own reasoning. The Detailed Notice of Discharge is the hospital's stated reasons for the discharge decision, sent after you've requested QIO review — same posture as the DENC for a termination.

Compare it against your parent's condition today. Check whether the stated reasoning still holds given how your parent is doing right now, not how they were doing when the discharge plan was first made.

Let the QIO do its review. The hospital sends this directly to the QIO; reading your own copy tells you what the 1-day decision will actually turn on.

It isn't a second deadline and doesn't require any response from the family — no acknowledgment or reply is needed. It exists solely to give the QIO, and you, the hospital's own written case on the same clock the fast-appeal request already started.