What CO-197 denial code means (authorization absent)

CO-197 means precertification, prior authorization, or notification was absent, expired, or wasn't linked to the claim before the service was performed. It's a pre-service administrative failure, unrelated to medical necessity or coding accuracy, and the practice absorbs the write-off since the patient cannot be billed.

Key Takeaways

• CO-197 means the precertification, prior authorization, notification, or pre-treatment requirement was absent, missing, expired, or not properly linked to the claim before the service was performed.

• This is a pre-service administrative failure, not a clinical judgment about medical necessity, not a coding error, and not a pricing adjustment; the payer's authorization rules simply weren't satisfied before the visit.

• Because CO-197 falls under the Contractual Obligation group code, the practice absorbs the write-off and cannot bill the patient for the denied amount.

• A retroactive authorization request is sometimes possible depending on the specific payer's policy, but it's inconsistent and shouldn't be relied on as a routine recovery path.

• Given the current expansion of prior authorization requirements under models like CMS's WISeR, practices in newly affected service categories or states are especially exposed to this exact denial if intake workflows haven't been updated.

A service is performed, documented thoroughly, and coded correctly, and the claim still comes back denied. CO-197 means none of that mattered because a required step happened before any of it: the payer needed prior authorization, and it was never obtained, or was obtained but never made it onto the claim.

Numetix takes an expert-led, AI-powered, and human-in-the-loop approach to authorization tracking, catching a missing or unlinked prior authorization before the claim is submitted, not after it's denied. This guide covers what CO-197 means and the narrow path to recovering it.

Quick Answer: What does CO-197 denial code mean?

• CO-197 means precertification, prior authorization, or notification was absent, expired, or wasn't linked to the claim before the service was performed, a pre-service administrative gap.

• It's unrelated to medical necessity or coding accuracy; the service could be perfectly appropriate and correctly billed and still be denied for this specific missing step.

• As a Contractual Obligation code, the practice absorbs the amount and cannot bill the patient; recovery generally requires a retroactive authorization request, which succeeds inconsistently.

How CO-197 differs from the rest of the denial code family

CO-197 is specifically a utilization management denial: the payer's authorization rules weren't satisfied, independent of whether the service was clinically appropriate or correctly coded, per the official X12 Claim Adjustment Reason Code registry. This distinguishes it clearly from CO-16, a claim-level data completeness issue; from CO-45, a pricing mechanism tied to the fee schedule; and from CO-50, a clinical medical-necessity judgment. CO-197 sits in its own category: a process gap in the authorization workflow that should have been closed before the patient was ever seen.

Why this is becoming more common, not less

Prior authorization requirements are actively expanding, not staying static. CMS's WISeR model, for instance, adds new prior authorization requirements to a defined list of services in six specific states starting in 2026, for procedures that historically didn't require authorization under traditional Medicare. A practice that hasn't rebuilt its intake workflow to flag newly authorization-required services is the practice most exposed to a wave of CO-197 denials it didn't previously need to plan for.

The narrow recovery path

Some payers allow a retroactive or expedited authorization request in specific, limited circumstances, but this succeeds inconsistently and shouldn't be treated as a standard recovery strategy, a pattern documented by CMS's own WISeR model guidance. The far more reliable fix is preventing the gap before the service date: verifying authorization status, confirming it's linked correctly to the claim, and confirming it hasn't expired, immediately before the appointment rather than only at the time it was originally requested weeks earlier.

Frequently asked questions

Can a patient be billed for a CO-197 denial?

No. As a Contractual Obligation code, the financial responsibility sits with the practice, not the patient, since the missing authorization was an administrative failure on the provider side, not a coverage exclusion the patient owes for.

Does CO-197 always mean no authorization exists at all?

Not necessarily. The code's broad description covers several distinct scenarios: no authorization was ever obtained, an authorization exists but wasn't included on the claim, or a required notification step was skipped even though the underlying authorization itself was in place. Confirming which specific scenario applies determines whether a simple corrected resubmission or a full retroactive authorization request is the right next step.

How is CO-197 different from CO-198?

CO-197 means no valid authorization exists for the service at all. CO-198 means an authorization does exist but its limits, visits, units, or dates, were exceeded. Both are authorization-related, but the fix differs: CO-197 requires establishing authorization from scratch, while CO-198 requires requesting an expanded scope under an authorization that's already partially in place.

Can a CO-197 denial be prevented if the referring provider, not the treating practice, was responsible for obtaining authorization?

This is a common source of CO-197 denials in referral-based care, and the fix is procedural rather than clinical: confirming authorization status directly with the payer or through the practice's own eligibility system before the appointment, rather than assuming a referring provider's office secured it, closes this specific gap regardless of whose administrative responsibility it was supposed to be.

Does CO-197 apply to emergency services?

Generally no, or with significant exceptions; most payer policies and applicable law recognize that genuine emergency care cannot reasonably wait for prior authorization, and many plans require only notification within a defined window after the emergency service rather than pre-service authorization. Confirming the specific payer's emergency care authorization policy, rather than assuming standard elective-service rules apply, matters directly for correctly billing emergency encounters.

How quickly should a practice verify authorization status before a scheduled appointment?

As close to the actual appointment date as the payer's system allows, rather than only at the time the appointment was originally scheduled weeks or months earlier, since authorizations can expire, be revoked, or fail to transfer correctly between systems in the interim. A verification check within 24 to 48 hours of the appointment catches most of the gaps a much earlier one-time check would miss.

Does a CO-197 denial ever indicate a payer system error rather than a genuine missing authorization?

Occasionally, yes. An authorization that was genuinely obtained and confirmed can still trigger CO-197 if it wasn't correctly linked to the claim in the payer's own system, a data-matching issue rather than a true absence of authorization. Retaining the original authorization confirmation number and date is what allows a practice to demonstrate this distinction when disputing what initially looks like a straightforward missing-authorization denial.

For medical practices that need authorization status verified before the date of service, not after a denial, our bookkeeping services connect revenue cycle tracking to current authorization requirements, expert-led, AI-powered, and human-in-the-loop.

See the healthcare revenue cycle guide for the full authorization and billing framework.