CO-197 Denial Code: Missing Prior Authorization
The Medicare Advantage prior authorisation data contains a number that should alter the way your practice interprets this code. not the rate of denial. rate of overturns. An authorisation denial is often seen as final.
The Medicare Advantage prior authorisation data contains a number that should alter the way your practice interprets this code. not the rate of denial. rate of overturns.
An authorisation denial is often seen as final. According to the data, it's usually not.
What does the CO 197 denial codeΒ mean?
Code 197, which was last updated on May 1, 2018, is defined by X12 as "Precertification/authorization/notification/pre-treatment absent," with effect from October 31, 2006.
There is no mention of "doing the work." The payer does not claim that the service was unneeded or uncovered. It indicates that a necessary permission step was not completed prior to the provision of the service.
What is authorisation in advance? A service must be approved by the payer before it is rendered. Regardless of whether the service was appropriate, the payer refuses payment in the absence of approval.
Pre-certification, authorisation, notification, and pre-treatment are the four different topics covered by the term. A payer who demands notification within 48 hours is enforcing something very different from one who demands clearance before to the first session. These are distinct requirements with separate regulations. Examine your contracts to see if they apply.
Since the group code is CO, the amount is not the patient's responsibility but rather a contractual obligation. Generally speaking, you cannot bill the patient for a service you did not obtain authorisation for, and trying to do so would likely result in a complaint.
How often is this actually denied, and how often is it overturned?
This is the real-world application of the data. Medicare Advantage insurers "fully or partially denied 4.1 million prior authorisation requests, which is a somewhat larger share (7.7%) of all requests" (KFF) of the roughly 53 million prior authorisation requests that were filed to them in 2024.
"Just 11.5% of denied prior authorisation requests were appealed to Medicare Advantage insurers in 2024," and "80.7" of those appeals were partially or totally reversed (KFF). This is the bit that counts for your workflow.
Together, read those two numbers. Approximately one in nine denials are contested, and four out of five challenges are successful. It is evident that a significant number of appealable denials are being accepted without any testing.
Commercial coverage follows the same trend. KFF discovered that "8% due to lack of preauthorization or referral" was one of the stated reasons for denials in HealthCare.gov marketplace plans in 2021, while customers appealed "less than two-tenths of 1." of in-network denials.
Just to be clear, the Medicare Advantage numbers include denials of prior authorisation requests, which are a slightly different demographic than claims that are denied with CO 197 after the fact. It is nevertheless difficult to dispute the findings' direction.
What do you do when a CO 197Β arrives?
Work in this sequence. Neither the appeal nor the write-off should be used first.
Verify the existence of the authorisation. It did, surprisingly frequently, and the number was just not sent on the claim. It settles in a single cycle and is a rectified claim rather than an appeal. This is similar to CO 16, where the stated cause is incomplete information.
Make a request for retroactive approval. In situations where the service was urgent or eligibility was questionable at the time, many payers allow it within a specified window. This is the most frequently omitted phase.
Verify if authorisation was indeed necessary. Requirements are subject to change more frequently than most practices keep track of. It is worthwhile to contest a denial that claims there was no authorisation for a service that no longer needs one.
Make an appeal using clinical records. The appeal focuses on medical necessity and the accompanying documentation if the service was required and provided.
After the foregoing, merely write off. Writing off at step one is leaving money behind due to the overturn rates.
Why is behavioral health hit harder byΒ this?
Because authorisation requirements in the field of behavioural health are more specific, more inconsistent between payers, and more likely to be associated with session counts as opposed to a single authorised episode.
Usually, one authorisation is required for a medical operation. An initial authorisation, a concurrent review at a predetermined number of sessions, and then another may be required for a course of therapy. Each of those represents a distinct chance to miss a deadline, and failing to meet the second one eliminates all subsequent sessions.
This arrangement creates a particular failure mode that is worth keeping an eye out for. Because it belongs to someone, the initial authorisation is sought with caution. The refusal for sessions eleven through eighteen appears all at once, and the concurrent review is overlooked since no one was monitoring session counts against the authorised number.
A tracked session count against each active authorisation, with a trigger prior to the limit instead of after it, is the solution. That is a tracking issue, and tracking issues can be resolved.
Where automation actually helps with COΒ 197
This is the code where automation pays off the most on both sides. Routing recovers a significant portion of the remaining volume after prevention eliminates the majority of it.
At scheduling, requirements are checked. At the time of booking, it is known whether this payer needs authorisation for this service. The intervention that completely stops the denial is checking it at each appointment.
monitoring the session count in relation to authorisation. There is only a counting issue with the concurrent review failure. Instead of raising the flag after the limit, a system that has the authorised number and the sessions provided can do it before.
Sending denials in the proper direction. A rectified claim is a CO 197 where the authorisation was present. An appeal or a retroactive request can be one in which it didn't. Separating those distinct operations prevents everything from defaulting to write-off.
In order to close the gap that the KFF figures highlightβdenials that were appealable but were never appealedβSupabill automates benefits verification across payers and handles denials with routing and appeals.
It's worth specifying the actual limit. Automation cannot create medical necessity or get an authorisation that a payer declines to provide. The write-off is appropriate when a service was actually not authorised and the payer refuses to grant it retroactively. The difference with automation is that you come to that decision after testing it, as opposed to before.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.