US Medical Billing

CO-11The diagnosis does not support the service

The payer's edits say the condition reported and the service performed do not go together. This is not the same as a coverage refusal: CO-167 says the diagnosis is outside what the plan covers for the service, while this one says the pairing itself does not make clinical sense to the edit. Very often the record does support a linkage and the claim simply pointed at the wrong diagnosis line.

Billable to the patient? No — a mismatch between two coded fields on your own claim is a provider-side correction.

Where it strikes

Where this denial is born

  1. Front desk
  2. Coding
  3. Claim build
  4. Submission
  5. Adjudication

This denial is usually created at the highlighted stage — that is where prevention lives.

Work the denial

Answer the questions — follow the path

The same questions an experienced biller asks, in order. Your answers draw the route to the right action.

Does the record document a condition that supports this service?

Read the note rather than the claim — the question is what was documented, not what was coded.

Every path

The full decision tree

Does the record document a condition that supports this service?

Read the note rather than the claim — the question is what was documented, not what was coded.

  • Yes →

    Was that condition on the claim, and did the service line point at it?

    The diagnosis can be present on the claim and still not be the one the line references.

    • Yes →

      Respond with the documentation. If the pairing was reported correctly, answer the payer with the record showing the clinical link, through its reconsideration or appeal route.

    • No →

      Correct the coding or the pointer, and resubmit. Report the documented condition at its most specific code and point the service line at it, then resubmit as a replacement claim. Code what the record supports — never reverse-engineer a diagnosis from what would pay.

  • No →

    Query the provider before touching the code. If the note does not support a linkage, the gap is in the documentation and a coder cannot close it. Query the provider; if nothing supports the service, the denial is correct.

Stop the repeat

Prevention

Check diagnosis pointers at charge entry, not just the diagnosis list. A claim can carry exactly the right condition and still deny because the line pointed somewhere else.

Go deeper

Related reading

Where this rests

The code list, and when it was last checked

X12 maintains the Claim Adjustment Reason Codes list, where this code is listed as 11. The list carries the number alone: the CO in front of it is the adjustment group the payer chose for this line, which decides who owes the balance, and the same code can arrive under a different group from a different payer. It has been on the list since January 1, 1995, and X12 last revised its entry on July 1, 2017.

Checked against the list revision dated November 1, 2025 on August 7, 2026, where it reads as an active code.

X12 — Claim Adjustment Reason Codes (opens in a new tab)

Check the reasoning

Sources

The paragraphs behind the guidance above. A page that tells you what to do about money should show you what the instruction rests on.

Drowning in CO-11 denials?

Our denial team works them for you — root cause to recovery.

Book a consultation

Ready to improve your revenue cycle?

Tell us about your practice and we’ll tell you where we would start.