Dermatology Denial Code Index

How to read a CARC and RARC pairing

Every line on a remittance that pays less than billed carries a claim adjustment reason code (CARC) and, usually, one or more remark codes (RARC). They are not alternatives. The CARC is the category of decision — this was bundled, this was not medically necessary, this duplicated another line — and it is what determines whether the balance is provider liability, patient liability or a contractual adjustment. The RARC is the explanation underneath it: which field was missing, which policy was applied, which other claim it collided with.

Read them together and in that order. CO-16 alone says only that information was missing; the RARC beside it says whether the missing item was a referring provider identifier, a diagnosis pointer or an attachment, and those are three different fixes in three different departments. A denial worked from the CARC alone is worked blind, which is why the same rejection reappears the following month.

What the group code tells you before anything else

• CO — contractual obligation. The balance cannot be billed to the patient. Either correct and resubmit, or appeal.
• PR — patient responsibility. The balance moves to the patient statement; the work is collection, not appeal.
• OA — other adjustment, usually a routing or coordination-of-benefits event rather than a clinical decision.
• PI — payer initiated reduction, which is the payer asserting its own policy and is the group most worth challenging in aggregate rather than per claim.
• The group code, not the reason code, decides who owes the money — and misreading it is how practices write off balances they were entitled to bill.

Correct, appeal or prevent

Once the pairing is read, every denial resolves into one of three actions. Correct and resubmit applies where the claim was wrong and the payer was right — a missing identifier, a wrong pointer, a unit count that does not match the record. Appeal applies where the claim was right and the payer's determination was not, and it needs the clinical record attached rather than a restatement of the code. Prevent applies where the same pairing keeps returning, which means the cause sits upstream in registration, scheduling, the note template or a scrubber rule.

Sorting denials this way rather than by dollar value is what changes the trend line. A queue worked purely by value recovers the largest claims and leaves the recurring pairing generating the same volume next month, at the same cost to work.

Read the denial before you rework it

Every denial on a remittance carries a claim adjustment reason code and often one or more remark codes. The reason code says what category of decision was made; the remark codes usually say what specifically went wrong. Practices that work denials as one undifferentiated queue rework them all the same way, which is why the same denial reappears next month at the same rate.

Three of the codes below should almost never be appealed — they should be corrected and resubmitted, or prevented at registration and scheduling. Two of them should be appealed only after reconciling the claim against the record, because a meaningful share of them are correct. Knowing which is which is most of the work.

Track denials by cause, not by rate

• A single denial rate hides everything. A 9% rate that is mostly missing-information rejections is a registration problem; the same rate driven by bundling is a documentation problem.
• Segment by reason code, by payer and by rendering provider. Denials cluster on all three, and the cluster is the fix.
• Separate administrative rejections from clinical denials so neither hides inside the other.
• Measure the recovery rate per reason code, not just the appeal count. Appealing a code you rarely win is a cost center.
• Watch for step changes on a single date. A cliff usually means a payer edit changed, not that your practice suddenly got worse.