Lesson 0010

Rejection Is Not Denial

The practical product skill: classify claim outcome evidence before deciding whether to correct, resubmit, work a denial, check status, or post money.

Your Tangible Win

After this lesson, you should be able to sort a claim signal into one of five lanes: BCH, RJT, DNY, ADJ, or STS.

Primary source to read after the lesson: CMS Electronic Health Care Claims.

The Core Idea

A claim can fail at different points, and each point needs a different product action. CMS describes basic HIPAA front-end edits that can reject an entire batch, implementation-guide edits that can reject individual claims for correction and resubmission, and later coverage/payment policy edits that can reject or deny individual claims (CMS Electronic Health Care Claims).

After Medicare processes a claim, CMS says an ERA or SPR contains final claim adjudication and payment information, including adjustment reasons and values at line, claim, or provider level (CMS Health Care Payment and Remittance Advice).

Five Lanes

Code Meaning Product Action Do Not Treat As
BCH Batch rejection before individual claim processing. Fix transmission, envelope, or batch-level format, then resend. Individual claim denial.
RJT Individual claim rejected for correction and resubmission. Route to claim correction with the rejected field or rule visible. Final adjudication.
DNY Claim denied after payer coverage or payment decisioning. Route to denial workqueue, appeal, corrected claim, or write-off review. Formatting error.
ADJ Remittance adjustment with payment, responsibility, or reason codes. Post payment, contractual adjustment, patient responsibility, or provider-level adjustment. Claim status ping.
STS Claim status response about where the claim is in process. Update tracking and follow-up timing without posting payment. Final remittance.

The Product Test

Ask: what should the user do next? If the answer is "fix and resend," you are probably looking at a rejection. If the answer is "work the payer decision," you are probably looking at a denial. If the answer is "post money or responsibility," you are looking at remittance.

Question Lane
Did the whole batch fail before claim-level processing? BCH
Was one claim returned for correction and resubmission? RJT
Did the payer make a coverage or payment decision against the claim? DNY
Does the evidence include payment, responsibility, CARC, RARC, or group code data? ADJ
Is the evidence just telling you current claim location or processing state? STS

Mini Case

A clearinghouse response says one claim was rejected because the rendering provider taxonomy was missing. The product stores claim_failed = true and sends the account to denial follow-up.

Product diagnosis: the product collapsed rejection into denial. The safer state is claim_status = rejected with a correction task for the missing taxonomy, then resubmission after the claim is fixed.

Scenario Practice

Choose the lane that owns the signal. Use only the code: BCH, RJT, DNY, ADJ, or STS.

1. A response says the entire file failed basic HIPAA standard checks. Which lane owns this?
2. One claim is returned because a required provider field is missing. Which lane owns this?
3. The payer processed the claim and denied the service for lack of medical necessity. Which lane owns this?
4. An ERA reports a contractual adjustment amount with CARC and group code values. Which lane owns this?
5. A 277 response says the claim is accepted and still in process. Which lane owns this?

What to Ask Me Next

Ask follow-up questions when you want to turn this into workflow design. Good next questions: "What statuses should a claim table have?", "How should I model corrected claims?", or "Where does the clearinghouse response fit?"

For review, keep the claim outcome triage card nearby.