Skip to main content
Call
CARC 160 · CO-160

CARC 160 Denial: Injury/illness was the result of an activity that is a benefit exclusion — How to Fix and Appeal

Reviewed by QuickIntell RCM Editorial Team · Last reviewed

Updated

TL;DR

CARC 160 (X12 Injury/illness was the result of an activity that is a benefit exclusion). CARC 160 denies services as benefit-excluded because the injury or illness resulted from an activity the plan excludes (e.g., certain high-risk sports, criminal activity, self-inflicted harm — depending on plan).

Official X12 description

“Injury/illness was the result of an activity that is a benefit exclusion.”

Source: X12 Claim Adjustment Reason Codes. The X12 External Code Lists are the single authoritative source for every CARC descriptor — always verify against the current release before building a claim-scrub rule.

What CARC 160 actually means

CARC 160 denies services as benefit-excluded because the injury or illness resulted from an activity the plan excludes (e.g., certain high-risk sports, criminal activity, self-inflicted harm — depending on plan). Verify the exclusion applicability.

Common root causes

  • Injury/illness mechanism matches plan exclusion (hazardous activity, self-inflicted).

Prevention checklist

  • Activity/mechanism capture at registration and coding to match payer policy language.

Appeal strategy — step by step

Most CARC 160 denials clear faster with the right remediation than with a formal appeal. Work the steps in order and escalate only when a lower-effort path has been ruled out.

  1. 1Appeal if the mechanism does not match the exclusion or if state law (e.g., MHPA) preempts the exclusion.
Sample appeal-letter language for CARC 160
[Provider letterhead] Re: Appeal of CARC 160 — Claim #{claim_number} Member: {member_name} · Member ID: {member_id} Date(s) of Service: {dos} On {remittance_date} this claim was adjusted with CARC 160: "Injury/illness was the result of an activity that is a benefit exclusion." We respectfully request reconsideration. The X12 External Code List definition of CARC 160 does not apply to this claim for the following reasons: 1. [Cite the clinical / coding / policy fact that rebuts the adjustment] 2. [Cite the supporting documentation attached — op note, EOB, LCD/NCD citation, NCCI edit indicator, modifier rationale] 3. [Cite the payer's own policy where applicable] Attached: {list supporting documents} Please process payment under the member's benefits. If additional information is required, contact the billing office at {provider_phone} or {provider_email}. Sincerely, {billing_manager_name}, {credentials}

Edit the bracketed fields before sending. This template is a starting point; a payer-specific appeal form may still be required — check the provider portal first.

Payer-specific notes

Payer-specific behavior for CARC 160 publishes here as the QuickIntell anonymized denial ETL ingests sufficient volume. In the meantime, consult the payer directory for the relevant provider manual and appeal form.

How common is CARC 160?

Search demand rank
#191

Out of 306 seeded CARCs, ranked by combined US monthly search volume for "CARC 160", "CO-160 denial", and "denial code 160".

Platform frequency
Pending ETL

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

How QuickRCM prevents CARC 160

QuickRCM catches the root causes above before the 837 leaves the clearinghouse:

  • Claim-scrub rules fire on every root cause listed above — the scrub references the same X12 CAS segment logic that drives the denial, so what the payer checks, QuickRCM checks first.
  • When a denial lands, QuickRCM routes it to the correct worker with the documentation bundle already attached (op note, LCD citation, modifier rationale, EOB, primary 835).
  • Appeal templates tuned to each CARC (including this one) pull the supporting facts from the claim and fill the bracketed fields automatically.
See QuickRCM →Book a demo

Frequently asked questions — CARC 160

What does CARC 160 mean?

CARC 160 is an X12 Claim Adjustment Reason Code. The official definition is: "Injury/illness was the result of an activity that is a benefit exclusion." In plain English, the payer is telling you cARC 160 denies services as benefit-excluded because the injury or illness resulted from an activity the plan excludes (e.g., certain high-risk sports, criminal activity, self-inflicted harm — depending on plan). Verify the exclusion applicability.

How do I resolve a CARC 160 (CO-160) denial?

Start with the most common root cause: Injury/illness mechanism matches plan exclusion (hazardous activity, self-inflicted). First step: Appeal if the mechanism does not match the exclusion or if state law (e.g., MHPA) preempts the exclusion. See the full remediation and appeal checklist on this page before filing a formal appeal.

Is CARC 160 patient responsibility?

No — CARC 160 is typically carried under CO (Contractual Obligation) or OA (Other Adjustment), which means it is the provider's responsibility, not the patient's. Do not bill the patient unless the 835 CAS group code is PR.

What does CARC 160 look like on an EOB or 835 remittance?

On the 835 ERA, CARC 160 appears in Loop 2110 CAS segment as "CAS*CO*160*{amount}". On a paper EOB the same code prints in the Adjustment/Denial Reason column with the X12 description: "Injury/illness was the result of an activity that is a benefit exclusion." — usually paired with one or more RARC remark codes in the same remittance line for additional context.

Can CARC 160 be appealed successfully?

Yes — when the root cause does not apply to the specific claim. Overturn rates are strongest when the appeal cites the X12 definition, the payer's own published policy, and documentation that rebuts the payer's rationale. The sample appeal language block above is a starting point; always adapt it to the payer's reconsideration form.

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.