Claim Scrubbing

What claim scrubbing is

Claim scrubbing is a pre-submission quality check for claims. The goal is to inspect claim data against coding rules, billing guidelines, and payer policies before anything leaves your system for the clearinghouse or the payer.

Scrubbing runs edits on required fields, demographics, coverage, diagnosis and procedure codes, modifiers, units, revenue codes, NPI and taxonomy, and basic policy rules. Most teams use a mix of system edits built into the EHR or practice management system, edits at the clearinghouse, and sometimes custom payer-specific rules.

In behavioral health, claim scrubbing should also validate authorization numbers, level-of-care coding (for example, ASAM level commonly mapped to rev codes and HCPCS), and episode structure for long stays so the claim lines match how the payer expects to see the treatment.

Why claim scrubbing matters operationally

Every error that escapes claim scrubbing turns into days in A/R and extra staff time. A missed modifier on a telehealth visit can turn into a CO-96 or CO-97 denial and 30 to 60 days of rework. A missing authorization on day 16 of a residential stay can trigger CO-197 for all charges past the auth window.

Good scrubbing reduces claim rejections at the clearinghouse, lowers avoidable denials, and protects timely filing. Operationally, that means fewer touches per claim, faster cash, and cleaner reporting on denial rate and first-pass resolution rate. In small and mid-size behavioral health programs, the difference is often a biller spending most of the week chasing rework versus focusing on high-dollar exceptions and payer relationships.

Scrubbing is also an audit risk control. Catching mismatched diagnosis and procedure codes or billing units beyond policy limits before submission lowers the odds that a payer tags a pattern as abuse or waste.

How claim scrubbing fits into daily workflow

In practice, claim scrubbing runs in layers.

• Front-end edits inside the EHR or billing system: required fields, basic coverage checks, patient demographics, place of service, and simple logic like "diagnosis required for CPT 90791."
• Clearinghouse edits: HIPAA 837 format, payer ID routing, subscriber eligibility format, and general payer rules that apply to all customers.
• Custom payer and program rules: behavioral health specific rules such as "residential per-diem requires revenue code and HCPCS," "telehealth requires modifier 95 for audio-video," or "authorization required after day 14 for Medicaid MCO X."

Operators should review scrubbed claims daily. Common steps are to:

• Work error queues by payer, program, or error type.
• Fix what can be corrected by billers in batch (for example, missing rendering NPI) and route the rest back to clinical or intake.
• Track recurring edit types and upstream them into training, template fixes, or updates to Supanote documentation so the same mistakes stop happening at the charting or scheduling level.

The most effective scrubbing process is tuned over time using denial data. Every new denial pattern that shows up on remittance advice is a candidate for a new edit so future claims fail fast in the scrubber instead of 45 days later on an ERA.

• Relying only on clearinghouse edits and skipping in-system claim scrubbing, so payer-specific behavioral health rules are missed, for example, a Medicaid MCO that requires revenue code 0905 with H2036 for IOP per-diem and denies everything past day 10 with CO-197 when the auth is not checked.
• Not tying scrubbing rules to authorization details for long stays, which leads to PHP or residential claims going out with units beyond the approved dates and triggering partial CO-197 denials for days 15 and beyond.
• Ignoring telehealth-specific edits, such as checking for modifier 95 on audio-video visits or 93 for audio-only, which causes preventable CO-96 or CO-97 denials when payers downcode or deny noncompliant telehealth lines.
• Over-editing claims with vague or conflicting custom rules so claims sit in scrub queues for days waiting on clarification from clinical staff, which quietly extends charge lag and pushes claims up against timely filing limits.
• Failing to update scrubbing logic after payer policy or contract changes, so the system keeps allowing outdated codes or old unit limits until you see a spike in CO-50 and CO-97 denials and have to rework a whole month of claims.

Claim scrubbing in behavioral health has to account for carve-outs where mental health and substance use benefits are administered by a separate vendor. That means checking payer IDs, benefit packages, and policy-specific rules for both the medical plan and the behavioral carve-out entity so claims do not ping-pong between plans or reject at the clearinghouse.

For programs that bill long per-diem episodes like residential, PHP, and IOP, scrubbing must validate revenue codes, HCPCS, and day counts against authorization spans and level of care. A common pattern is that residential is approved in 7 or 14 day chunks. If scrubbing only checks that an auth exists, and not that the dates and units line up, claims will look clean on submission but deny for all units beyond the last concurrent review.

State Medicaid and Medicaid MCOs often stack additional behavioral health rules on top of national coding standards. Examples include daily limits on therapy units, distinct modifiers for SUD services, specific rev code to HCPCS pairings, and strict medical necessity rules for each ASAM level commonly mapped to billing codes. Your scrubber should enforce these prior to submission to avoid CO-50 and N130 denials that can leave significant revenue uncollected.

Carve-outs and long episodes also distort standard metrics. A strong scrubbing process will keep behavioral health claims from sitting in "pending info" status for days while staff chase missing ASAM documentation, clinical notes, or updated auths, which helps your team protect both cash and compliance in a benefit space that is more fragmented than standard medical billing.

AI agents can take on the repetitive pattern-recognition work inside claim scrubbing. An AI-driven scrubber can hold payer- and program-specific rules in memory, read every 837 before submission, and flag missing data, mismatched codes, and likely denials based on historical CARC and RARC patterns. It can also watch denial feeds and suggest new edit rules when it sees the same denial reason codes popping up repeatedly for the same payer, program, or code pair.

Supabill's claims-scrubbing agent can maintain payer rules for your behavioral health lines of business, tie those rules to benefit and authorization data collected by a benefits-verification agent, and then adjust scrubbing when the denials agent sees new CO-16, CO-50, or CO-197 patterns in your 835 files. The limit is that AI still should not make judgment calls on gray-area medical necessity or how to negotiate exceptions with payers. Humans need to decide when to override an edit, how to argue clinical appropriateness, and how to work with payers on policy clarifications and appeals.

Is claim scrubbing the same as checking for HIPAA 837 format compliance?

No. HIPAA 837 format compliance is about whether the claim file meets the technical EDI standard required to be transmitted, which is defined by X12 and enforced by CMS and clearinghouses. Claim scrubbing is about the business logic on top of that standard, such as whether a residential stay has the right revenue code and HCPCS pair or whether an auth covers the billed dates. A claim can be perfectly valid as an 837 file and still deny for CO-50 or CO-197 if scrubbing does not catch policy issues. X12 maintains the HIPAA transaction standards, including 837 claim requirements. Source

Should claim scrubbing happen in the EHR, the clearinghouse, or both?

Ideally both. The EHR or billing system should handle core data-quality and behavioral health specific rules that rely on clinical or scheduling data, such as level of care, clinician credentials, and visit type. The clearinghouse is better for HIPAA format edits and common payer rules that apply across many providers. For high-volume behavioral health programs, the best setup is to put program- and payer-specific edits as close to the source as possible so issues are caught before claims ever leave your system. CMS explains that covered entities must use HIPAA transaction standards, which clearinghouses help enforce. Source

Can claim scrubbing prevent all behavioral health denials?

No. Scrubbing can prevent most technical and many avoidable clinical denials, such as missing auth numbers or incorrect rev-code-to-HCPCS pairing for IOP, PHP, or residential. It cannot prevent denials tied to payer discretion or shifting medical necessity interpretations, for example, when a Medicaid MCO decides that a certain ASAM level of care is no longer appropriate based on internal criteria. Scrubbing reduces noise and frees staff to focus on those judgment-based denials rather than chasing basic errors. Source

How often should claim-scrubbing rules be reviewed or updated for Medicaid and MCO behavioral health plans?

Scrubbing rules for Medicaid and Medicaid MCOs should be reviewed whenever you see a new denial pattern or when you receive contract or policy changes from the plan. In practice, that often means a standing quarterly review plus ad hoc changes when your team notices the same CARC appearing repeatedly for a specific code or program. Many state Medicaid and behavioral health carve-outs publish periodic provider bulletins that include coding and authorization changes, and those should trigger rule updates. General Medicaid coverage and policy information is available through Medicaid.gov. Source

Can claim scrubbing check medical necessity for behavioral health services?

Scrubbing can check that documentation and codes line up with basic medical-necessity rules, such as requiring a covered diagnosis for a psychotherapy code or linking ASAM level documentation to the billed level of care. It cannot fully evaluate clinical nuance, such as whether a step-down from residential to PHP is appropriate at a certain day in the stay. Those decisions rely on clinical judgment and payer criteria. Scrubbing should enforce the mechanical side of medical necessity and then route edge cases to utilization review or medical directors for review. ASAM publishes criteria that many payers commonly map to level-of-care decisions. Source

• CMS
• X12
• HFMA
• Medicaid.gov
• SAMHSA