The SNF ABN is Form CMS-10055, the Skilled Nursing Facility Advance Beneficiary Notice. Facilities issue it before providing items or services Medicare is not expected to cover, so the resident can decide whether to accept financial responsibility. It applies to Part A SNF services and is distinct from the NOMNC, which addresses termination of covered care.
Beneficiary notices are the cleanest revenue a facility can protect and among the most commonly lost. The rules are written down, the forms are provided, the deadlines are fixed — and facilities still issue the wrong notice, deliver it late, or complete it in a way that voids the liability shift entirely.
The consequence of a defective notice is specific and expensive: the facility, not the resident, becomes financially liable for care the resident would otherwise have paid for or declined.
Key takeaways
- The SNF ABN is Form CMS-10055 and covers Part A SNF items and services expected to be non-covered.
- The NOMNC (CMS-10123) is a different notice for termination of all covered services, due at least two calendar days beforehand.
- The notice must be delivered before the non-covered care begins, not after.
- The resident or authorized representative must select an option box and sign; the facility may not select for them.
- Generic or blanket notices issued to every admission are invalid.
- A defective notice shifts liability to the facility.
Which notice, when
| Notice | Form | Use it when | Timing |
|---|---|---|---|
| SNF ABN | CMS-10055 | Specific Part A items or services are expected to be non-covered, or coverage is ending for some services while the stay continues | Before the non-covered care begins |
| NOMNC | CMS-10123 | All Medicare-covered services are ending and the resident is being discharged from covered care | At least 2 calendar days before |
| DENC | CMS-10124 | The beneficiary has appealed a NOMNC to the QIO | Generally by close of business the day the QIO notifies the facility |
| Standard ABN | CMS-R-131 | Part B items and services expected to be non-covered | Before the service |
The single most common structural error is using the SNF ABN when the situation calls for a NOMNC. If all covered care is ending, the resident has appeal rights that only the NOMNC triggers, and issuing the wrong form denies them that pathway.
The five triggering events
CMS identifies five situations in which a SNF ABN is appropriate:
- Initiation. The facility believes Medicare will not cover care from the outset — for example, an admission where the qualifying hospital stay requirement is not met.
- Reduction. A component of care is being reduced, such as a therapy discipline discontinuing while the stay continues.
- Termination. Some but not all covered services are ending.
- Non-covered items or services. Specific items outside the Part A benefit that the resident may want anyway — a private room by preference, a personal comfort item.
- Benefit exhaustion. The resident is approaching or has reached the 100-day limit for the benefit period.
Benefit exhaustion is the one facilities most often handle poorly, because the date is knowable weeks in advance and the notice still tends to be issued in the final days.
Completing the form
The form has numbered blanks and specific completion expectations.
- Resident name and identification number. Must match Medicare records.
- The item or service. Describe it specifically enough that the resident understands what they are deciding about. Skilled nursing care is not specific. Physical therapy five days per week is.
- The reason Medicare may not pay. Plain language, resident-facing. The resident no longer requires daily skilled care communicates; the resident does not meet coverage criteria under the applicable manual provision does not.
- Estimated cost. A good-faith estimate. Omitting it or writing unknown weakens the notice, because a resident cannot make an informed financial decision without a number.
- Option boxes. The resident chooses whether to receive the items and have a claim submitted, receive them without a claim, or decline them. The facility must never pre-select an option. A pre-marked form is a defective notice.
- Signature and date. The resident or an authorized representative signs. Note that the date signed and the date care begins are different dates, and the order matters.
Delivery requirements
Delivery is where otherwise correct notices fail.
- Deliver in person where possible, in advance of the non-covered care.
- Explain it verbally and answer questions. The standard is that the beneficiary comprehends the notice, not that they received a piece of paper.
- Allow time to consider. A notice presented with a pen and an expectation of an immediate signature does not meet the comprehension standard.
- Authorized representatives. Where the resident is not capable of understanding, deliver to the representative and document the basis for that determination.
- Telephone delivery is permitted in defined circumstances when the representative is not available in person, and must be followed by a mailed copy and careful documentation of the conversation.
- Refusal to sign. Annotate the notice with the refusal, have a witness sign, and retain it. Refusal does not void the notice.
- Provide a copy to the resident and retain the original in the record.
What makes a notice defective
- Issued after the care began. Retroactive notice does not shift liability.
- Blanket or routine issuance. Notices given to every admission as a matter of course are invalid, because they do not reflect a specific expectation of non-coverage.
- Vague service description. The resident could not have known what they were declining.
- No cost estimate.
- Pre-selected option box.
- Unsigned and undated, with no documented refusal.
- Illegible or altered.
- Wrong notice entirely — a SNF ABN where a NOMNC was required.
The common thread is that each defect undermines the notice's purpose, which is an informed choice by the beneficiary. Reviewers assess it that way rather than as a checklist.
Building a notice process that holds
- Track benefit day counts on a live report so exhaustion notices are issued a week out, not the night before.
- Assign notice delivery to a named role, trained on the comprehension standard rather than on form completion.
- Build a decision aid that routes staff to the correct notice from the situation — wrong-notice errors are decision errors, not knowledge errors.
- Audit a sample quarterly against the defect list above.
- Retain notices where the business office can find them during an appeal. A valid notice nobody can locate has the same effect as an invalid one.
Where AI helps with beneficiary notices
- Notice selection. Describe the situation and get the correct form identified with the applicable timing rule, before the wrong one is issued.
- Plain-language reason drafting. Convert a clinical rationale into resident-facing language that meets the comprehension standard.
- Retrospective audit. Read a quarter of issued notices and flag those with missing cost estimates, absent signatures, pre-selected options, or dates that fall after the service began.
- Benefit exhaustion forecasting. Read census and benefit day data and identify residents approaching day 100.
- DENC drafting against same-day QIO turnaround, grounded in the clinical record.
Hathr.AI runs Anthropic Claude models inside AWS GovCloud under a FedRAMP High authorization boundary and signs a Business Associate Agreement within 24 hours on every plan. Because issued notices are usually scanned paper with handwritten signatures and annotations, the OCR handling handwriting is what makes a retrospective notice audit practical at all.
Every draft is reviewed and delivered by qualified staff. AI does not determine coverage.
Audit a quarter of notices in one pass
Upload last quarter's issued SNF ABNs and ask Hathr.AI which ones have defects that would fail to shift liability.
Start a free trial — $47 a month, no seat minimum, BAA in 24 hours →
Frequently asked questions
What is the SNF ABN form number?
Form CMS-10055, the Skilled Nursing Facility Advance Beneficiary Notice of Non-coverage.
When must a SNF ABN be issued?
Before the non-covered items or services begin, in one of five triggering situations: initiation, reduction, termination of some services, non-covered items, or benefit exhaustion.
What is the difference between a SNF ABN and a NOMNC?
The SNF ABN addresses specific items or services expected to be non-covered. The NOMNC addresses the end of all Medicare-covered services and must be delivered at least two calendar days beforehand.
Can a facility pre-select an option box?
No. The beneficiary or authorized representative must make the selection. A pre-marked notice is defective.
What happens if the resident refuses to sign?
Annotate the notice with the refusal, have a witness sign, and retain it in the record. Refusal does not invalidate the notice.
Who is liable if the notice is defective?
The facility. A defective notice fails to shift financial responsibility to the beneficiary.
Part of the HIPAA-Compliant AI for Skilled Nursing Facilities hub. Related: SNF Billing Guide · Appealing a Medicare Denial
This article is general regulatory information, not legal or billing advice. Notice forms, instructions, and expiration dates are updated periodically by CMS. Always use the current version of the form from the CMS Beneficiary Notices Initiative page and verify requirements before issuing.
Our Youtube Videos
Hathr.AI is the fastest, safest way to handle sensitive medical records with HIPAA-compliant artificial intelligence. In this demo, watch how you can:✅ Summarize a patient’s medical record ✅ Generate an AI-assisted treatment plan ✅ Write a letter to the patient in plain English ✅ Suggest CPT billing codes ✅ Draft an insurance appeal for a denied claim ✅ Evaluate the case for potential malpractice — all in under 5 minutes.The only AI tool hosted in AWS GovCloud and Powered by Claude 4.0 Sonnet, Hathr.AI is trusted by hundreds of practices that need speed, security, and compliance.Learn more: hathr.ai For healthcare teams: hathr.ai/healthcare Reach out to learn more: contact@hathr.ai
#HIPAACompliantAI#ArtificialIntelligenceInMedicine#HealthcareAI#MedicalBillingAI#AIForDoctors#HIPAAAI#MedicalRecords#AIInHealthcare
Description
As Hathr.AI, we are dedicated to providing a private, secure, and HIPAA-compliant AI solution that prioritizes your data privacy while delivering cutting-edge technology for enterprises and healthcare professionals alike.
In this video, we’ll dive deep into the growing concerns around data privacy with AI tools—especially in light of recent revelations about Microsoft’s Word and Excel AI features. These new features have raised alarm over data scraping practices, where user data could be used without clear consent, leaving individuals and organizations exposed to potential privacy breaches. What makes this especially concerning is the "opt-in by default" design, which could lead to unintended data sharing.
In contrast, Hathr.AI ensures that your data stays yours. With a firm commitment to HIPAA compliance, we take the protection of sensitive healthcare data to the highest level. Our platform is built with the understanding that privacy is not an afterthought but a fundamental pillar of our design. We don’t collect, store, or sell user data, and we employ state-of-the-art encryption, secure access protocols, and clear user consent processes to keep you in full control.
We’ll also touch on why Hathr.AI, powered by advanced LLM (Large Language Models) like Claude AI, offers a secure and private alternative for businesses looking to leverage AI technology without compromising sensitive information. While some AI tools may collect or expose data through ambiguous or hard-to-find opt-out settings, Hathr.AI puts transparency and security at the forefront, offering peace of mind in an era of increasing digital vulnerability.
If you’re concerned about your privacy or looking for a HIPAA-compliant AI solution that respects your data, Hathr.AI provides the robust security, transparency, and ethical design that you need.
Key Points:
- HIPAA Compliant AI: Built for healthcare professionals, ensuring compliance with privacy regulations.
- Privacy-first: No data scraping, no data selling, full user control over information.
- Claude AI: Secure, powerful LLM tools for advanced capabilities without compromising security.
- Data Transparency: Say goodbye to hidden opt-in/opt-out toggles—Hathr.AI gives you clear, easy-to-understand privacy settings.
Tune in to learn how Hathr.AI ensures your AI tools remain private, secure, and trustworthy, while still delivering the performance and accuracy you need to thrive in a fast-evolving digital landscape.
Don't forget to like, comment, and subscribe for more insights on secure AI solutions and how to protect your organization from emerging privacy risks!
Description
Discover how Hathr AI's advanced AI tools transform federal acquisition processes with unparalleled security and efficiency. Designed for government professionals, this video showcases Hathr AI’s capabilities, including secure AI data analysis, HIPAA-compliant tools, and AWS GovCloud integration, to help streamline decision-making and document management. Perfect for agencies seeking private, compliant, and powerful AI solutions, Hathr.AI delivers tools tailored for healthcare and government needs.
Key Topics Covered:
AI-driven data analysis for governmentHIPAA-compliant, secure AI tools for federal agencies
Private deployment options with AWS GovCloud
Learn more about Hathr AI’s secure, high-performance solutions at hathr.ai and transform your agency’s acquisition process with cutting-edge AI.
Description
Discover how Hathr.AI simplifies NSF grant evaluations with advanced AI-driven compliance and proposal review tools. This video showcases Hathr.AI’s capability to streamline grant compliance checks, enhance accuracy, and save time for evaluators and applicants alike. Ideal for research institutions, government agencies, and proposal writers, Hathr.AI offers secure, HIPAA-compliant AI solutions tailored to meet the complex requirements of NSF and other grant processes.Highlights:AI-powered compliance checks for NSF grant proposalsFast, accurate, and secure evaluations with Hathr.AITailored solutions for research, government, and healthcareOptimize your grant proposal process with Hathr.AI's private, secure AI tools. Learn more at hathr.ai and transform how you handle grant evaluations and compliance.
Description
Join Hathr.AI at the Defense Information Systems Agency (DISA) Technical Exchange Meeting to explore innovative AI solutions tailored for federal and defense applications. In this session, we highlight Hathr.AI's secure, private AI tools designed for efficient data handling, HIPAA compliance, and seamless integration within government systems, including AWS GovCloud. Perfect for agencies seeking reliable AI for data analysis, document summarization, and secure decision-making, Hathr.AI provides cutting-edge technology for defense and healthcare needs.Highlights:AI tools for federal and defense data managementSecure, HIPAA-compliant AI solutions with AWS GovCloudEnhancing operational efficiency with private AI deploymentsDiscover how Hathr.AI's solutions empower government and defense agencies to stay at the forefront of innovation. Visit https://hathr.ai to learn more about our services.


.png)

