RARC N800 Remark Code: Meaning & Resolution

Official X12 description

“Only one evaluation and management code at this service level is covered during the course of care.”

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 N800 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 CARC	What the CARC means
CARC 18	Exact duplicate claim/service
CARC B14	Only one visit or consultation per physician per day is covered.
CARC 97	The benefit for this service is included in the payment/allowance for another service/procedure that has already been adjudicated.

CARCs CAQH CORE pairs with RARC N800

Under the CAQH CORE Payment and Remittance Uniform Use rule, a health plan that reports remark code N800 on an 835 should pair it with one of the 1 claim adjustment reason code below, with the listed group code, for the business scenario 2 (Missing, invalid or incomplete data from the submitted claim). A remark paired outside this list is itself a compliance question to raise with the payer.

CORE-required CARC and group code combinations that include RARC N800
CARC	Group code	Scenario
16	CO or PI	2: Missing, invalid or incomplete data from the submitted claim

Source: CAQH CORE-required Code Combinations v3.10.0 (2026-02), published by CAQH CORE (operating rules).

What RARC N800 actually means

RARC N800 caps covered E/M levels during a course of care. Reconcile charges; appeal with clinical distinctness if applicable.

Common root causes

Multiple E/M visits at same level during care episode.

Prevention checklist

E/M-frequency-aware scheduling.

Resolution & appeal strategy — step by step

Because RARC N800 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.

1Appeal with documentation of distinct encounters.

Sample reconsideration language referencing RARC N800

[Provider letterhead] Re: Reconsideration — Claim #{claim_number}, CARC 18 / RARC N800 Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} The 835 remittance on {remittance_date} carried RARC N800: "Only one evaluation and management code at this service level is covered during the course of care." 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 N800?

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 N800

QuickRCM reads RARC N800 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.

Prevent denials before submission →Manage RARC-driven denials Book a demo

Frequently asked questions — RARC N800

What does RARC N800 mean?

RARC N800 is an X12 Remittance Advice Remark Code. The official X12 definition is: "Only one evaluation and management code at this service level is covered during the course of care." It is supplemental to a Claim Adjustment Reason Code (CARC) on the same 835 line.

Which CARC is paired with RARC N800?

RARC N800 is most commonly paired with CARC 18, CARC B14, CARC 97. 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 N800 remark on a remit?

Start from the root cause: Multiple E/M visits at same level during care episode. First step: Appeal with documentation of distinct encounters. Because RARCs are supplemental, the resolution is almost always to address the paired CARC rather than appeal the RARC alone.

Where does RARC N800 appear on the 835 ERA?

RARC N800 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 N800 the same as ICD-10 code N800?

No. RARC N800 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.

RARC N800 Remark Code: Only one evaluation and management code at this service level is covered during…

TL;DR