Medicare Part B Compliance for SNFs: What to Watch
Aviation got safe by studying the events where nothing went wrong. Your billing has those too.
Flying is the safest way to travel. The way it got there is the surprising part. In 1976, aviation built something that sounds backwards: a system that asks people to report their own mistakes, voluntarily, confidentially, with no punishment for owning up.
It's the Aviation Safety Reporting System, run by NASA, and it has collected more than 2 million reports. Around 100,000 arrive every year. Most of them describe a near-miss: the altitude someone almost busted, the runway someone almost crossed, the checklist someone almost skipped. Events where nothing bad actually happened.
That's the counterintuitive part. The industry most obsessed with safety spends its energy on the incidents that never became incidents. A near-miss is a free lesson. It's the accident that warned you instead of costing you.
Your Part B billing has near-misses every day. The claim someone almost sent without an order. The status someone almost assumed. The supply a vendor almost billed under your name. Each one is a free lesson, if you catch it and write it down.
Here's the uncomfortable part. A facility that never records a near-miss isn't running clean. It isn't looking. In billing, the exclusion you logged and the mismatch you caught are your near-misses, and they're the best proof you have that the process is actually watching.
1. Watch resident status and consolidated billing
The first near-miss usually hides here.
Document the resident's status for the dates under review. In a covered Part A stay, consolidated billing generally requires the SNF to submit the claims for the services a resident receives, with specific exclusions. Bill a bundled item separately and you've created an overpayment to give back later.
The risk is quiet: assuming status instead of verifying it. A clear status check on every review file is the catch that prevents it.
2. Watch documentation completeness
A claim is only as strong as the record behind it.
The facility should be able to connect the item, the resident, the medical need, the order, the date, the quantity, the proof of delivery or use, and the coverage rationale. If the record only shows that a supply was ordered, that's a near-miss waiting to happen. See the full documentation requirements for Part B supplies.
Label each record: complete, incomplete, unclear, or excluded. That single habit gives the team a consistent way to pause a weak file before it flies.
3. Watch coverage and code alignment
Medicare claims live or die on coverage and coding.
HCPCS Level II codes identify many supplies and products that CPT doesn't, including DMEPOS items. A code that exists is not a code that's covered. The Medicare Coverage Database, through its LCDs and articles, is where the coverage conditions, modifiers, quantity rules, and documentation requirements are spelled out. See how LCDs govern Part B coverage.
The near-miss to catch: using a code because it "looks close" before confirming the coverage conditions actually line up.
4. Watch supplier and vendor visibility
Vendors can hand you useful invoice and delivery detail. What they can't hand you is a clear view of how the billing decisions get made.
Ask for records showing what was reviewed, what was billed, and what was excluded. If the vendor reporting is too general to connect a supply back to the chart and the claim decision, that gap is the near-miss, and it's one that ends with your facility answering for a claim you never reviewed.
5. Watch denial and appeal patterns
A denial is a near-miss that already left a mark. The question is whether you read it.
Treat every denial as process feedback. A repeated denial reason points at something upstream: a documentation habit, a coding issue, a status problem, a weak intake. Review denial trends monthly and ask what changed because of them. Aviation acts on the first report. If your denials repeat and the workflow never changes, the process isn't learning.
6. Keep audit-ready files
Every aircraft carries a recorder so the story survives the flight. Your claims need the same.
Audit readiness means the file is built before anyone asks, not assembled in a scramble across email, EHR notes, vendor files, and billing exports. For each submitted claim, you should be able to show why it was reviewed, what documentation supported it, who approved it, and where the records live.
Build the record as the decision happens, and the audit is already answered.
The standard, in one breath
Here's the whole watchlist, on one page.
| Watchpoint | The near-miss it catches | The incident it prevents |
|---|---|---|
| Resident status and consolidated billing | Assuming status instead of verifying it | A Part A item billed to Part B, an overpayment to repay |
| Documentation completeness | An item with an order but no proof of use | An unsupported claim that fails on audit |
| Coverage and code alignment | A code that "looks close" without confirmed coverage | A denial, or a claim you can't defend |
| Supplier and vendor visibility | A supplier billing under your name you can't see | Answering for a claim you never reviewed |
| Denial and appeal patterns | The same denial reason repeating | A fixable process gap that quietly compounds |
| Audit-ready files | A record scattered across email, EHR, and vendor files | A scramble, or a failure, when an auditor asks |
The rule underneath all six is simple. Don't submit what you can't support. Don't guess when status or coverage is unclear. Don't let the dollar outrank the documentation. That will exclude some items. It also makes every claim that moves forward one you can defend.
"In billing, your near-misses are the claims you held back and the reasons you wrote down. Show me a facility that never excludes a thing, and I'll show you one that isn't looking."
Aviation got safe by refusing to waste a near-miss. Do the same with your billing. Treat every exclusion, every caught status change, every held claim as a report worth keeping. Review the patterns monthly, and change the workflow when they repeat.
The goal is a process that catches its own near-misses. A clean audit is just what that process leaves behind. Write down the catch.
Schedule a free 30-minute assessment with Burst to see where your current workflow stands on each watchpoint. You'll get the findings in writing.
Compliance note
This article is for general educational purposes only and does not replace facility-specific compliance, billing, legal, or payer guidance. SNFs should verify coverage, coding, documentation, and submission decisions against applicable CMS guidance, payer rules, and their own compliance policies.
References
- NASA, Aviation Safety Reporting System (ASRS)
- CMS, Skilled Nursing Facility (SNF) Consolidated Billing
- CMS, Healthcare Common Procedure Coding System (HCPCS)
- CMS, Medicare Coverage Database
Watchpoints are easier to hold when someone owns them daily. Medicare audit defense for SNF claims covers the response side, and a 12-month SNF revenue recovery review shows which past encounters were documented well enough to still bill.
Related

Written by
Eric Hansen
Founder, Burst Billing
Eric Hansen is the founder of Burst Billing. He has spent over a decade helping skilled nursing facilities recover missed Medicare Part B supply reimbursement through cleaner documentation, tighter vendor workflows, and risk-free billing reviews.
More from Eric →Frequently asked questions
- Six: resident status and consolidated billing, documentation completeness, coverage and code alignment, supplier and vendor visibility, denial and appeal patterns, and audit-ready file discipline. Each is a place where a small error can be caught before it becomes an overpayment, a denial, or an audit finding.
- Before, and throughout. Compliance should shape the first status screen, the documentation review, the coverage check, the exclusion decision, and the audit file, rather than waiting until a claim is ready. Building it into the workflow is what keeps reimbursement work from becoming an avoidable risk.
- Because they're free data. Aviation improved safety by capturing near-misses, the events where nothing bad happened, and learning from them. In billing, an exclusion log and a record of caught mismatches show the process applies judgment, and they reveal the patterns worth fixing. A process that never flags anything isn't clean; it's not watching.
- Treat every denial as process feedback. A repeated denial reason usually points upstream to a documentation habit, a coding issue, a status problem, or a weak intake. Review denial trends monthly and change the workflow when a reason repeats. If denials repeat and nothing changes, the process isn't learning.
- The file is organized before anyone asks. For each submitted claim, the facility can show why it was reviewed, what documentation supported it, who approved it, and where the records are stored, without a scramble across email, EHR notes, vendor files, and billing exports. Building the record as the decision happens is what makes it audit-ready.
- During a covered Part A stay, consolidated billing generally requires the SNF to submit the claims for most services a resident receives, with specific exclusions. The risk is assuming a resident's status instead of verifying it, which can lead to billing a bundled item separately and creating an overpayment. Confirm status for the dates under review.
- A simple one: don't submit what you can't support, don't guess when status or coverage is unclear, and don't let reimbursement outrank documentation. It will exclude some items, and it strengthens every claim that does move forward. Verify decisions against current CMS guidance, payer rules, and your own compliance policies.
See what your facility may be missing
No upfront cost · No recovery, no fee
