Skip to main content
Call
RARC N179 · Remittance Advice Remark Code

RARC N179 Remark Code: Additional information has been requested from the member. The charges will be…

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

Not an ICD-10 code. RARC N179 is a remittance-advice remark code published by X12 and carried on the 835 LQ segment. Any ICD-10 code with the same letters and digits (e.g., ICD-10 M15 osteoarthritis, N130 other urinary tract disorders) is a separate, unrelated code set used in diagnoses on the 837. Confirm the context before acting on this page.

TL;DR

RARC N179 (X12 Additional information has been requested from the member. The charges will be reconsidered upon re…). Commonly paired with CARC 133, CARC 226. RARC N179 indicates the payer has requested information from the member (COB questionnaire, accident questionnaire).

Official X12 description

“Additional information has been requested from the member. The charges will be reconsidered upon receipt of that information.”

Source: X12 Remittance Advice Remark Codes. X12 publishes and maintains the RARC set; always verify against the current release before building a claim workflow.

Paired CARC codes

RARC N179 almost never appears alone — it accompanies one of the CARCs below on the same 835 remittance line. Fix the CARC and the RARC typically clears; the RARC alone is informational.

Paired CARCWhat the CARC means
CARC 133The disposition of this service line is pending further review.
CARC 226Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete.
CARC 227Information requested from the Billing/Rendering Provider was not provided or was insufficient/incomplete.

What RARC N179 actually means

RARC N179 indicates the payer has requested information from the member (COB questionnaire, accident questionnaire). No provider-side action; follow up with the patient to complete the payer's request, then expect reprocessing.

Common root causes

  • COB or accident questionnaire not yet returned by member.

Prevention checklist

  • Patient-outreach workflow when the payer signals missing member information.

Resolution & appeal strategy — step by step

Because RARC N179 is supplemental to a CARC, the resolution path usually starts by fixing the underlying adjustment reason. A formal appeal of the RARC alone is rarely necessary.

  1. 1Coach the patient to complete the payer's questionnaire; reprocessing follows.
Sample reconsideration language referencing RARC N179
[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 133 / RARC N179 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N179: "Additional information has been requested from the member. The charges will be reconsidered upon receipt of that information." We request reconsideration. The attached documentation rebuts the remark code: 1. [State the fact that rebuts the remark — authorization number, primary 835, modifier rationale, LCD citation, etc.] 2. [Reference the paired CARC and the corresponding fix] 3. [Attach the supporting document listed in step 1] Attached: {list supporting documents} Please process this line under the member's benefits. Contact the billing office at {provider_phone} for questions. Sincerely, {billing_manager_name}, {credentials}

Edit the bracketed fields before sending. Payer-specific reconsideration forms are often required — check the provider portal first.

How common is RARC N179?

Platform frequency
Pending ETL

Platform frequency ranks publish once the anonymized denial-rate pipeline reaches the publication threshold (strategy §12 Phase 2).

How QuickRCM handles RARC N179

QuickRCM reads RARC N179 alongside its paired CARC in the 835 LQ segment and routes the line to the correct worker queue with the right documentation already attached:

  • Denial routing rules tuned to the CARC+RARC pair — the paired combination tells QuickRCM which documentation the payer will accept.
  • Reconsideration template for this exact remark code pulls the supporting facts from the claim automatically.
  • Pre-submission scrubs that catch the preventable drivers surfaced on this page before the 837 leaves the clearinghouse.
See QuickRCM →Book a demo

Frequently asked questions — RARC N179

What does RARC N179 mean?

RARC N179 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Additional information has been requested from the member. The charges will be reconsidered upon receipt of that information." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N179?

RARC N179 is most commonly paired with CARC 133, CARC 226, CARC 227. The CARC is the financial adjustment reason; the RARC is the informational remark. Fix the paired CARC first — the RARC usually clears with the corrected claim.

How do I resolve a RARC N179 remark on a remit?

Start from the root cause: COB or accident questionnaire not yet returned by member. First step: Coach the patient to complete the payer's questionnaire; reprocessing follows. Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC N179 appear on the 835 ERA?

RARC N179 is carried on the 835 Loop 2110 LQ segment alongside the CARC in the CAS segment of the same service line. The code and its X12 description also print on the paper EOB in the "Remark Code" or "Remark" column next to the corresponding denial or adjustment reason.

Is RARC N179 the same as ICD-10 code N179?

No. RARC N179 is a remittance-advice remark code published by X12 and carried on the 835. Any ICD-10 code with the same letters and digits is a diagnosis code on the 837 HI segment — a completely different code set maintained by the WHO/CMS. Use the transaction context (835 = RARC; 837 = ICD-10) to disambiguate.

Disclaimer

This page is operational reference for medical-billing professionals. It is not legal, clinical, or contractual advice. X12 code descriptors are maintained by the X12 External Code Lists; always verify against the current X12 release and the payer's own published policy before submitting or appealing a claim.