The Clearinghouse: Claim Scrubbing and EDI Routing

The Role of the Clearinghouse#

A clearinghouse is an intermediary that sits between providers and payers in the electronic claim lifecycle. It receives claims from providers, validates and reformats them, and routes them to the correct payers — then routes acknowledgments and remittances back.

What a clearinghouse does:

• Claim scrubbing / edits. Checks claims against payer-specific and standard edits (valid NPIs, required fields, NCCI bundling, format compliance) and flags or rejects problem claims *before* they reach the payer. This is a front-line defense against denials like CARC 16 (missing info).
• Format translation. Converts the provider's claim into the standardized 837 EDI format each payer expects and manages payer-specific quirks.
• Routing. Sends each claim to the right payer and returns acknowledgments (277CA, 999) and remittances (835).
• Status and eligibility. Often brokers eligibility (270/271) and claim-status (276/277) transactions as well.

Front-end rejection vs. denial. A claim *rejected* by the clearinghouse or in the payer's front-end (e.g., a 277CA reject) never entered adjudication — it can be fixed and resubmitted without a formal appeal, and it does *not* count as a denial. A *denial* happens after adjudication and is reported via CARC/RARC on the 835. Distinguishing rejections from denials is a common point of confusion that affects denial-rate metrics.

Why it matters in RCM. The clearinghouse is the first automated checkpoint. The more edits applied here (and upstream in the provider's own scrubbing), the higher the clean-claim rate and the fewer denials downstream. A strong scrubbing layer is one of the highest-ROI investments in a revenue cycle.