A practical decision model
Stop
Do not submit or change a claim when you know the information is unsupported or materially uncertain.
Check
Review the documentation, payer rule, coding guidance and internal policy that actually apply.
Escalate
Use the compliance, coding, privacy, legal or supervisory channel appropriate to the issue.
When an error is discovered
- Preserve the original record and relevant evidence.
- Notify the appropriate internal owner.
- Determine the scope and affected claims.
- Correct or refund as required by the applicable payer/program process.
- Address the root cause through training, configuration or workflow changes.
Red flags
- “Everyone does it” used as justification for unsupported billing.
- Instructions to delete or alter records after a concern is raised.
- Pressure to bill a higher code without supporting documentation.
- Repeated resubmission without resolving the underlying issue.
- Discouraging staff from using compliance reporting channels.
Quick knowledge check
What should come first when a claim instruction appears unsupported?
Stop the questionable action, verify the facts/rules and escalate through the proper channel.
Should the original record be preserved when correcting an error?
Yes. Corrections should follow approved workflows rather than concealing the original information.
What should happen after a recurring compliance issue is fixed?
Address the root cause so the issue is less likely to recur.
Module 9 Compliance & HIPAA Pack
Open your learner dashboard for the HIPAA billing checklist, compliance red-flags reference, incident/escalation worksheet and Module 9 assessment.
Open Learner DashboardRelated services, tools & guides
Use these next-step resources to connect the lesson with real revenue-cycle workflows.
Create a free learner account to mark lessons complete and track Module 9 on your dashboard.
Create Free Account