What Is Claim Scrubbing?
Claim scrubbing is the automated pre-submission review of a claim to detect coding errors, missing data, eligibility mismatches, and rule violations before the claim reaches the payer. It is performed by claim scrubbing software — either integrated into the practice management system or operated as a separate clearinghouse function — and is the primary tool for maximizing clean claim rates.
A claim that fails the scrubber is returned to the billing team for correction before submission. A claim that passes is forwarded to the payer (or clearinghouse) as a clean claim, significantly reducing the likelihood of denial or rejection.
What Gets Checked During Scrubbing?
Claim scrubbers apply hundreds of edits simultaneously. The most important categories include:
- Patient and payer data validation: Member ID, date of birth, subscriber name, group number, and NPI all match the payer's records. Mismatches here cause eligibility rejections even when the patient is covered.
- Code validity: CPT, ICD-10, and HCPCS codes are current and valid for the date of service. Deleted codes or invalid code combinations trigger automatic rejections.
- Code pairing and bundling rules: Certain procedure codes cannot be billed together (CCI edits — the CMS National Correct Coding Initiative). Scrubbers catch unbundling errors before payers do.
- Modifier checks: Modifiers must be appropriate for the code and payer. Using a modifier that overrides a bundling rule requires supporting documentation — scrubbers flag these for review.
- Medical necessity edits: Some payers require specific diagnosis codes to support specific procedures. Scrubbers cross-check CPT-ICD10 pairing against payer-specific LCD/NCD rules.
- Authorization flags: If the procedure requires prior authorization and none is on file, the scrubber flags it before the claim goes out.
- Timely filing checks: Claims approaching the payer's filing deadline are flagged for priority submission.
When Is It Used?
Claim scrubbing runs as part of the standard billing workflow — typically as claims are batched for submission, either daily or in real time. In high-volume practices or hospital billing departments, scrubbing is fully automated and runs without manual review unless the scrubber flags an error. In smaller practices, the biller may review scrubber output before releasing the batch.
Some organizations run a secondary scrub at the clearinghouse level in addition to the practice management system's built-in scrubber. This catches payer-specific edits that the PM system may not have loaded for every payer in the mix.
Why It Matters in RCM
The financial case for thorough claim scrubbing is straightforward. According to HFMA MAP Key benchmarks, best-in-class practices achieve a clean claim rate of 98% or higher — meaning fewer than 2 claims in 100 require any rework before payment. The average denied claim costs between $25 and $44 to rework, and claims that are denied once take an average of 16–22 additional days to pay.
More critically, not all denied claims get worked. Industrywide, approximately 65% of denied claims are never resubmitted — meaning every preventable denial that slips past a weak scrubber is a coin-flip between recovered revenue and a write-off. Effective claim scrubbing prevents the denial from ever happening.
Scrubbing also reduces days in AR. Claims that go out clean and pay on first submission contribute directly to a lower DAR figure. A practice running a 95% clean claim rate versus a 98% rate on $10M in annual billings is generating hundreds of additional claims per year that require follow-up — adding AR aging, staff time, and write-off risk.
