How We Cut Repeat CO-167 Denials From 11% to 2.4% for an Infusion Practice

Some practices see a CO-167 denial once and correct it easily. Others see the same CO 167 Denial Code repeat month after month. Repeat denials on the same code rarely happen by accident. They usually point to a systemic diagnosis coding gap somewhere in the process. This case study covers exactly that kind of repeat pattern. At Infusion Billing Services, we recently worked with a client facing this exact problem. Their CO 167 Denial Code kept appearing across different patients and payers, and it was costing them real revenue every month. This case study explains the five diagnosis coverage failures behind that pattern. It also shows how we broke the cycle and achieved full recovery.

What Is the CO 167 Denial Code in Infusion Billing

The CO 167 Denial Code is a Contractual Obligation code from the payer. It states the diagnosis submitted on the claim is not covered under that plan. It signals that the ICD-10 code did not meet the payer’s coverage policy for the billed service. This differs from a Patient Responsibility code in one key way. The patient is never billed under a CO 167 Denial Code. The write off belongs to the practice, not the patient, once the claim lands here. This matters enormously in infusion billing due to recurring visit schedules. One unresolved diagnosis coding error can repeat across many future claims. Left unfixed, a single CO 167 Denial Code becomes a recurring revenue problem.

Client Snapshot

Our client was a mid sized infusion practice with two locations. They submitted roughly 850 claims per month across multiple payers. The payer mix included Medicare, Medicare Advantage, and several commercial plans. Biologic and specialty drug infusions made up a meaningful share of total volume. We reviewed twelve months of denial data before starting this engagement. The CO 167 Denial Code appeared repeatedly across the same patient accounts, and the CO 167 Denial Code pattern had compounded steadily over the full review period. Standard resubmission had not addressed the CO 167 Denial Code coverage gaps involved.

Denial Reason 1: Diagnosis Excluded Under an Updated LCD or NCD Policy

Some patients were being treated under a diagnosis that had previously been covered for a specific infusion drug. The payer’s Local Coverage Determination had since been revised. The internal coding reference list was never updated to reflect the change. This triggered the CO 167 Denial Code on every subsequent visit.

Problem:

• Payer’s LCD or NCD policy had been revised to remove a diagnosis
• Internal coding reference list was not updated after the change
• Claims kept using the outdated diagnosis code repeatedly

Fix:

• Built a policy monitoring process tied to each high volume drug
• Flagged outdated diagnosis codes immediately, not after a denial
• Confirmed current LCD or NCD coverage before further visits

This fix stopped a repeat CO 167 Denial Code pattern tied to a single missed policy update, and it kept the same LCD gap from resurfacing on future visits.

Denial Reason 2: Unspecified Diagnosis Code Used as a Default Template

A coder had set up a recurring visit template using an unspecified ICD-10 code for efficiency. That template was reused for every follow up infusion visit. The payer required a more specific code to establish coverage. Every claim built from this way returned the same CO 167 Denial Code.

Problem:

• Unspecified diagnosis code was saved into a recurring visit template
• Template was reused automatically without a specificity check
• No process existed to catch unspecified codes proactively

Fix:

• Replaced unspecified codes in templates with the most specific option supported
• Reviewed all recurring visit templates for specificity gaps
• Verified diagnosis specificity before resuming claims for that patient

Catching this template error early prevented a lasting CO 167 Denial Code repeat pattern.

Denial Reason 3: Preventive Diagnosis Carried Forward Into Diagnostic Visits

Some claims were billed using a diagnosis originally entered for a screening or preventive encounter. That same diagnosis carried forward into later diagnostic infusion visits. The payer required a diagnostic diagnosis to cover the service. This produced a CO 167 Denial Code despite active coverage under the plan, and it caught the billing team off guard.

Problem:

• Preventive diagnosis was never updated for later diagnostic visits
• Claims were submitted before visit type was reconfirmed
• Coverage appeared excluded despite an active plan

Fix:

• Built a visit type confirmation step before each recurring claim
• Confirmed the diagnosis matched the current visit type first
• Delayed claim submission until diagnosis type was verified

This fix prevented CO 167 Denial Code denials tied to carried forward diagnosis errors.

Denial Reason 4: Correct Drug Identified but Diagnosis-Procedure Pairing Not Verified

Staff correctly identified the right infusion drug on several claims. The wrong diagnosis code was paired with that drug during submission though. This diagnosis did not appear on the payer’s approved list for that drug. The result was a CO 167 Denial Code despite accurate drug identification.

Problem:

• Correct drug was identified, but an unapproved diagnosis was paired with it
• Diagnosis-drug pairing was not checked against the payer’s covered list
• No verification step confirmed the pairing before submission

Fix:

• Standardized diagnosis-drug pairing checks against the payer’s covered list
• Cross checked selected diagnosis against approved codes for that drug
• Reviewed pairing accuracy before every claim submission

This fix closed a small but consistently disruptive coding error.

Denial Reason 5: Coding Error Repeated Across an Entire Recurring Infusion Series

Some patients were on a multi month infusion series billed under the same diagnosis code each visit. An incorrect diagnosis entered at the first visit was never corrected. Every subsequent claim in the series carried the same error forward. This produced a CO 167 Denial Code across the full remainder of the series.

Problem:

• Incorrect diagnosis entered at the first visit of a recurring series
• Error was never flagged or corrected before later visits
• Claims defaulted to the same diagnosis for every visit in the series

Fix:

• Confirmed diagnosis accuracy at the first visit of every recurring series
• Reviewed the diagnosis code before each subsequent claim in the series
• Flagged recurring series patients for a periodic coding accuracy check

This fix resolved a pattern unique to multi visit infusion treatment series.

How Repeat Denials Were Broken and Full Recovery Was Achieved

Each of these five diagnosis coverage failures had been repeated independently. Outdated LCD policy, template errors, carried forward diagnoses, unverified pairings, and series wide errors all compounded together. No single fix would have broken the full repeat pattern alone. Addressing all five simultaneously is what finally stopped the cycle. Once diagnosis coding was corrected at the source, the backlog was fully worked. Aging claims tied to each cause were identified, corrected, and resubmitted. Full recovery followed once the root causes stopped generating new denials.

Financial Recovery Results

The table below shows the shift in performance across the review period. These results reflect what breaking the repeat cycle achieved for this client.

These results confirm that repeat CO 167 Denial Code patterns are fully preventable. Fixing the diagnosis coding source stopped the CO 167 Denial Code from regenerating month after month.

Key Takeaways

These lessons help prevent repeat CO 167 Denial Code patterns going forward.

• Monitor LCD and NCD policy updates for every high volume infusion drug
• Review recurring visit templates for unspecified or outdated diagnosis codes
• Reconfirm diagnosis type before each diagnostic visit, not just at intake
• Cross check diagnosis-drug pairings against the payer’s approved list
• Verify diagnosis accuracy at the start of every recurring infusion series

Conclusion

A repeat CO 167 Denial Code almost always signals a diagnosis coding gap, not chance. Outdated policy, template defaults, carried forward diagnoses, unverified pairings, and series wide errors all matter. As this case shows, fixing each root cause broke the repeat cycle fully. Full recovery followed once these coverage failures stopped repeating month after month.

If your practice faces repeat CO 167 Denial Code patterns, we can help. Infusion Billing Services can identify the exact diagnosis coverage gap behind each denial. We build lasting fixes so revenue reaches your practice reliably.

Contact Infusion Billing Services today for a complete diagnosis coding audit. Start breaking the repeat denial cycle and recovering lost revenue.