The CO-167 denial code tells a billing team that the payer considers one or more reported diagnoses noncovered. It does not automatically mean the ICD-10-CM code is invalid, the service lacked medical necessity, or the patient owes the balance. The denial may reflect a benefit exclusion, policy restriction, claim-data problem, or payer processing issue.
Resolution starts with the full remittance advice and the policy effective on the date of service. Teams should compare the claim with the contemporaneous record, confirm how each diagnosis was reported and linked, and then choose a correction, reprocessing request, or supported appeal.
What does the CO-167 denial code mean?
Claim Adjustment Reason Code 167 means, “This (these) diagnosis(es) is (are) not covered.” The “CO” group code generally identifies a contractual obligation adjustment. CARC 167 may appear at the claim or service-line level, and a remark code may add instructions or identify the policy.
The wording is broader than “invalid diagnosis.” A valid ICD-10-CM code can still be outside a plan benefit, excluded for the billed service, absent from a payer’s covered-diagnosis list, or inconsistent with the policy effective for that date. Conversely, the denial may result from a data problem even when the documented diagnosis would support coverage.
Read the CARC with the group code, any Remittance Advice Remark Code, the 835 policy-identification segment when present, and the payer’s denial message. These details help distinguish a coverage decision from a correctable claim or processing error.
Why CO-167 denials occur
Common operational causes include:
- The diagnosis linked to the denied service is not listed as covered under the applicable payer policy.
- The claim carries an incorrect, incomplete, nonspecific, or outdated ICD-10-CM code, or the correct diagnosis was omitted or linked to the wrong line.
- The payer applied a national or local coverage rule, benefit exclusion, frequency rule, or diagnosis restriction.
- The claim used a code set or coverage policy that was not effective on the date of service.
- The record does not establish the condition represented by the submitted diagnosis.
- The payer processed the wrong policy version or overlooked submitted information.
For Medicare claims, the CMS Medicare Coverage Database helps locate national and local coverage determinations and related articles. Use the version effective for the service date.
A practical CO-167 denial resolution workflow
1. Read the complete denial message
Capture the denied line, group, CARC, RARC, amount, policy reference, and instructions. Confirm whether the diagnosis itself was rejected or failed a coverage relationship for a specific service.
2. Compare the remittance with the original claim
Review every diagnosis, its sequence, and its connection to the denied line. Verify the procedure, modifier, units, place of service, provider, and date because another claim element may determine which diagnosis rules apply. Check the claim accepted by the payer, not only the practice-management view.
3. Validate the diagnosis against the record
Confirm that the provider’s assessment supports the diagnosis. Check specificity, laterality, encounter character, combination-code requirements, exclusions, and sequencing. Never change a diagnosis merely to obtain payment.
4. Confirm the correct code set and effective date
ICD-10-CM files and guidelines change over time. Use the code set applicable to the service date and check whether a code became active, changed, or was deleted. The CMS ICD-10 resources provide current and historical files and official guidance.
5. Review the applicable coverage rule
Identify the policy, plan benefit, NCD, LCD, or article cited. Compare its indications, diagnosis list, documentation requirements, setting limits, and effective dates with the claim and record. If none was cited, request the exact rule used.
6. Select the right response and track it
Correct only when claim data was wrong and the record supports the change. Request reprocessing when correct information was overlooked or a rule misapplied. Appeal when the diagnosis and service were accurate and supported. Track the action, deadline, proof, outcome, and root cause.
Corrected claim, reprocessing request or appeal?
A corrected claim fits a genuine coding or entry error—for example, a supported diagnosis was omitted, the wrong code was selected, or the diagnosis pointer linked the wrong condition. The correction must be traceable to the existing record.
A reprocessing request may fit when the payer applied the wrong policy version, overlooked a diagnosis on the claim, or failed to use information on file. Confirm the payer’s routing because some plans handle this outside appeals.
Appeal when the original claim reflects the documentation and the diagnosis meets coverage requirements. For Original Medicare, the CMS first-level appeal guidance explains redetermination and filing expectations. Other plans set their own deadlines and methods.
How to build a stronger CO-167 appeal
Begin with the exact denial reason and policy at issue. Include the claim and remittance, identify the denied line, and state the action requested. Explain where the diagnosis appears in the signed record, how it relates to the service, and which policy requirement it satisfies.
Attach only evidence that answers the denial, such as the assessment and plan, test results, procedure note, authorization, and date-specific policy. A focused packet with page references is easier to evaluate than an unindexed chart.
Use a consistent claim-denial appeal framework to verify the payer, appeal level, deadline, supporting records, requested outcome, and proof of submission. Do not use an appeal to defend a diagnosis that the record does not support.
Preventing diagnosis coverage denials
Maintain current payer-policy references for high-risk services, confirm benefit and authorization requirements, and build edits around known diagnosis restrictions. Assign ownership for policy updates and effective-date changes on a consistent review schedule. Edits should prompt qualified review, not automatic code changes.
Coding quality checks should compare the provider’s documentation with code specificity, sequencing, and service-line linkage. A structured medical coding quality process can connect recurring denial findings with focused coder and provider education.
Track CO-167 by payer, plan, service, diagnosis, provider, value, cause, and disposition. Separating coding errors from exclusions and payer errors directs prevention to the correct team.
How RCMGen approaches CO-167 denial resolution
RCMGen treats CO-167 as a coverage-and-evidence question rather than an instruction to replace the diagnosis. The review connects the complete remittance, original claim, contemporaneous record, date-specific code set, and applicable payer policy before an action is selected.
RCMGen’s denial management approach also uses root-cause trends to support work queues, appeal decisions, coding feedback, payer escalation, and management reporting. The goal is accurate resolution without compromising coding integrity.
Frequently asked questions about the CO-167 denial code
Is CO-167 the same as a medical-necessity denial?
Not necessarily. CARC 167 says the diagnosis is not covered. Medical necessity may be part of the payer’s policy, but the denial can also reflect a benefit exclusion, diagnosis restriction, claim error, or processing problem.
Does CO-167 mean the ICD-10-CM code is invalid?
No. The code may be valid but not covered for the service, plan, setting, or date involved. Validate both the code and the coverage relationship.
Can the billing team change the diagnosis and resubmit?
Only when the original claim was incorrect and the medical record supports the corrected diagnosis. A diagnosis must never be changed solely to obtain payment.
Should a CO-167 claim be corrected or appealed?
Correct a real claim error, request reprocessing when the payer mishandled correct information, and appeal when the original diagnosis and service meet the applicable coverage requirements.
Can the remaining balance be billed to the patient?
Not automatically. Patient responsibility depends on the payer decision, provider contract, plan benefits, required notices, and applicable federal or state rules. Review those requirements before transferring any balance.
What documentation should support a CO-167 appeal?
Include the denial notice, original claim, signed clinical record, relevant test or procedure documentation, and the coverage policy effective on the date of service. Point reviewers to the specific evidence that supports the reported diagnosis and requested payment.
Resolve the coverage question before resubmitting
CO-167 resolution depends on identifying why the payer treated the diagnosis as noncovered. Review the remittance, validate the claim against the record and date-specific code set, confirm the coverage rule, and choose the response supported by the facts. This protects coding accuracy, improves appeals, and helps prevent repeat denials.