How to use RARC N517
RARC N517 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
- Read the line-level CARC, group code, and every non-alert RARC attached to the denial line.
- Compare the denied line against the 837 claim image, clearinghouse acceptance, eligibility response, authorization record, and provider enrollment record.
- Fix the specific field that the RARC or EOB identifies. Do not resubmit a clone of the rejected claim.
- Use corrected-claim frequency and original claim number requirements from the applicable local Blue plan.
- Appeal only when the claim already contained the required information and the payer edit appears incorrect.
Evidence checklist
- 837 claim extract or claim image
- ERA/EOB with CARC and RARC
- Eligibility response
- Provider NPI/taxonomy record
- Authorization/referral record if relevant
- Corrected claim note
FAQ
What does RARC N517 mean?
Resubmit a new claim with the requested information.
Is N517 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 N517?
Start with 837 claim extract or claim image, ERA/EOB with CARC and RARC, Eligibility response, Provider NPI/taxonomy record. Add only the records that answer the specific remark code and denial reason.