CO-167: Service denied because diagnosis not covered

The payer is telling you that the diagnosis attached to the line or claim is not eligible for payment under the plan. It may be excluded entirely, not linked to that service code in their policy, or not covered for the patient's age or benefit type. Mechanically, the claim failed a diagnosis-to-service or diagnosis-to-benefit edit in the payer's system. The payer sets the denied amount as a contractual adjustment, so you cannot bill the patient unless the denial is overturned with a corrected claim or an appeal.

In behavioral health, CO-167 hits a lot when a plan does not cover certain diagnoses for higher levels of care. Example: you bill PHP per diem for F43.23 (adjustment disorder) and the payer only covers PHP for severe mood, psychotic, or eating disorders, so they deny the days as diagnosis not covered. The facility is now looking at several days of nonpayment. You also see this with SUD treatment when a payer ties residential or detox coverage to a substance use diagnosis but the primary code submitted is a mood or trauma diagnosis. The payer's system sees residential SUD revenue codes without a primary F1x.x diagnosis that matches their policy and applies CO-167. For outpatient therapy and IOP, CO-167 can pop when you use "rule out" diagnoses, V/Z-codes tied to psychosocial stressors, or developmental disorders that the plan only covers under a different benefit. Telehealth adds another layer when the payer only covers certain diagnoses for telebehavioral visits and rejects others as noncovered for telehealth.

• Confirm the payer's diagnosis coverage policy for the billed service, level of care, and member's plan type.
• Review the clinical documentation and assessment to confirm the correct primary and secondary diagnoses at the time of service.
• Check whether a more accurate covered diagnosis was documented but not reported, and verify that changing it would still be clinically valid and compliant.
• If diagnosis coding was incomplete or prioritized wrong, correct the diagnosis pointers and codes, then submit a corrected claim using the payer's required frequency code.
• If the diagnosis truly matches the medical record and should be covered per policy, prepare a medical necessity or benefit interpretation appeal with clinical notes and any relevant policy language.
• If the payer clearly excludes the diagnosis for that service and level of care, adjust off the balance as contractual and flag the account for financial counseling and benefit education going forward.

• At intake and prior authorization, verify not just benefits but which behavioral diagnoses are covered for each level of care.
• Build payer specific diagnosis-to-service crosswalks for PHP, IOP, residential, detox, MAT, and telehealth, and use them in your scrubber.
• Train clinicians and coders to avoid unsupported "rule out" or noncovered Z-codes as primaries when a covered behavioral diagnosis is present in the documentation.
• Run periodic denial audits for CO-167 by payer and program and update templates, order sets, and coding guidelines based on patterns.