What CO-197 Means
CO-197 indicates that precertification, authorization, or notification was absent — the payer required prior approval for the service and either didn't receive a request, didn't approve one before the service was rendered, or has no record of the authorization the practice believes it obtained.
The Three Common Root Causes
First, and most common: the authorization was genuinely never requested, often because staff didn't realize the specific service or specific payer required it, or because a service that didn't previously require authorization began requiring it after a policy update the practice hadn't caught. Second: the authorization was requested and approved, but for a slightly different code, date, or provider than what was ultimately billed, causing a technical mismatch. Third, less common but real: the authorization exists on the payer's side but wasn't properly logged or linked to the claim during adjudication.
Is CO-197 Appealable?
It depends heavily on which root cause applies. If the authorization genuinely exists and can be documented — an approval number, a confirmation from the payer's portal, a fax confirmation — this is often a strong, fast-resolving appeal, since it's essentially a documentation gap rather than a clinical dispute. If no authorization was ever obtained, appeal options are much narrower and payer-specific; some payers allow a retrospective authorization request under limited circumstances (urgent/emergent care, for instance), but this shouldn't be assumed to apply broadly.
Prevention Is Higher-Leverage Than Appeal Here
Because a true no-authorization CO-197 denial is difficult to reverse, the highest-value fix is a reliable pre-service authorization check — verifying requirement status against the specific payer and specific service before the service is rendered, and confirming the authorization on file matches the code, date, and provider that will ultimately be billed.
ResolveRCM helps billing teams quickly distinguish a documentation-gap CO-197 (fast to fix) from a true no-authorization denial (harder to reverse) — and builds the right response for each. Learn more. |