Quick answer
For SNF notice routing, identify the Medicare program and purpose before selecting a form. In Original Medicare, the SNF ABN addresses specified expected Part A noncoverage; applicable Part B notices use the separate ABN. NOMNC addresses ending covered services, and DENC explains that ending when an expedited determination is requested. Follow the applicable instructions for each communication.
Choose the purpose before the template
A folder named “Medicare notices” is not a routing system. Start with the program, the service and the event. The following table is an orientation to the official sources, not a resident-specific determination of required notice or timing.
| Question being addressed | Starting form/process | Important boundary |
|---|---|---|
| Original Medicare Part A item or service usually covered, but expected not to be paid because it is not medically reasonable and necessary, or is custodial care | SNF ABN, CMS-10055 | Potential financial liability; check the specific instructions |
| Original Medicare Part B item or service with an applicable noncoverage concern | ABN, CMS-R-131 | A different form from the SNF ABN |
| Medicare-covered SNF services are ending | NOMNC process | Expedited-determination information; FFS and MA instructions differ |
| Beneficiary requests expedited determination of that ending | DENC process | Specific explanation of the coverage ending |
| Program, reason or service scope is unclear | Unresolved notice review | Do not choose whichever template was used last time |
The first two rows come from CMS FFS SNF ABN; the next two come from CMS FFS and MA NOMNC/DENC. The latter page links the FFS process in Claims Processing Manual Chapter 30, section 260, and the MA process in the applicable appeals guidance. Open those instructions when deciding timing, delivery, exceptions and responsible parties. A broad “coverage ended” event is not enough to populate them correctly.
A completed routing exercise
This original fictional case assumes that the appropriate team has established that the NOMNC process applies. A separate potential-liability question remains unresolved. It does not instruct staff to select a notice for a real person.
| Event | Correct operational output | Incorrect shortcut |
|---|---|---|
| Team documents the applicable service-ending process | NOMNC task linked to program, ending date and current instructions | One task labeled “all notices” |
| Notice is delivered through the reviewed process | Actual form version and delivery evidence retained | Saving only a blank template |
| Expedited-determination request arrives later | Linked DENC workflow and responsible team | Reusing the earlier notice-complete flag |
| Liability question remains open | Separate unresolved financial review | Treating the NOMNC signature as a billing authorization |
The result is two different communication events plus an open financial question. It is not one green account status. If the expedited request never arrives, the exercise does not manufacture a DENC merely to complete a checklist.
Keep the form that was actually delivered
On the review date, the CMS NOMNC/DENC page lists downloads effective January 2025. Record the exact downloaded version, source and instructions used in the local approved library. Recheck the source before release; a date in this article is not a perpetual version approval.
A minimal release record has four fields: official source, approved local copy, places distributed and replacement confirmation. Include printed packets and facility overrides. Historical records should display the delivered form, not rebuild an old communication from today's template.
If an old packet is discovered, preserve it and identify affected cases for appropriate review. Replacing the file fixes future distribution; it does not establish that an earlier communication was sufficient or repair it automatically.
Place a separate gate before resident statements
CMS payment and remittance guidance identifies Medicare patient-responsibility group-code context. It does not resolve every other beneficiary protection or notice condition. The statement reviewer needs the balance's origin, remittance detail, relevant notice conclusion and any unresolved program restriction.
For a fictional $240 balance, “payer did not pay” is insufficient support for transferring $240 to the resident. If responsibility remains unconfirmed, leave a specific review item and prevent that unreviewed amount from becoming a definitive statement. If a statement was already sent, retain the communication and route its correction along with the account correction.
This separation gives the platform buyer a concrete requirement: a notice event, an appeal-related event and a resident-balance decision must remain independently inspectable. A signature may document a communication; it is not a universal substitute for the other two decisions.
Questions & answers
Does a signed SNF ABN replace a NOMNC?
No. Potential financial liability and the right to request expedited review of ending services are different purposes. Review each applicable notice requirement separately.
Is a DENC automatically required with every NOMNC?
CMS describes the DENC as provided when the beneficiary requests an expedited determination. Follow the applicable FFS or MA instructions for the actual situation.
Does a patient-responsibility code alone authorize a resident statement?
No. Preserve the adjustment evidence and review applicable notices, program protections and case facts before releasing the statement.
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.