RARC remark code guide

BCBS RARC N661 — Documentation does not support medical necessity

What RARC N661 means with BCBS denials, common paired CARCs, evidence checklist, and provider next steps.

Fast answer: Documentation does not support that the services rendered were medically necessary.

How to use RARC N661

RARC N661 should be read with the CARC and group code on the same claim or service line. For BCBS denials, the remark often tells you whether the next move is a corrected claim, attachment response, COB update, authorization proof, or appeal packet.

Common paired CARCs

Recommended workflow

  1. Obtain the denial letter and identify the policy, guideline, or missing criterion.
  2. Map each criterion to a specific page or record date: symptoms, exam, imaging, labs, prior treatment, and plan of care.
  3. Ask the treating provider for a short medical-necessity statement that addresses the denial rationale directly.
  4. Index the appeal packet so a reviewer can find the support without searching the entire chart.
  5. Escalate to peer-to-peer or external review only when the plan’s process allows it and the evidence is complete.

Evidence checklist

  • Denial letter
  • Applicable medical policy
  • Progress notes
  • Labs/imaging/results
  • Treatment history
  • Provider letter of medical necessity
  • Plan of care

FAQ

What does RARC N661 mean?

Documentation does not support that the services rendered were medically necessary.

Is N661 enough to appeal a BCBS denial?

No. Pair the RARC with the CARC, group code, EOB text, claim line, and plan rule. The RARC explains the missing detail or context; the CARC explains the adjustment reason.

What should I attach for N661?

Start with Denial letter, Applicable medical policy, Progress notes, Labs/imaging/results. Add only the records that answer the specific remark code and denial reason.