Prior authorization: the denial you can only prevent before the visit

Most denials are arguments about whether a claim was coded, documented, or billed correctly. An authorization denial is different: it is an argument about something that was supposed to happen before the patient arrived. By the time it shows up on a remittance, the service has been rendered, the cost has been incurred, and the one action that would have prevented the denial is weeks in the past.

That is what makes prior authorization the most expensive administrative failure in the revenue cycle. The money is usually not recoverable by working harder on the back end. It is recoverable only by changing what happens at scheduling.

The denial that says the authorization is missing

The remittance code you will see most often is CO-197 — precertification, authorization, or notification absent. Read literally, it means the payer has no record of approving the service. Read practically, it means one of five quite different things, and the fix is different for each:

• No authorization was requested. The service was not flagged as requiring one, usually because the payer's requirement list changed or the plan was misidentified at registration.
• An authorization exists but does not match the claim. The approved CPT code, units, or place of service differ from what was ultimately billed — common when the plan of care changes between scheduling and the visit.
• The authorization expired. Approvals carry date ranges. A rescheduled procedure can fall outside a window that was valid when it was issued.
• The authorization belongs to the wrong provider. Approval was tied to a rendering provider or facility NPI that did not perform the service.
• The payer was not the one who required it. The patient's coverage changed, or the claim went to a secondary plan with its own rules.

Only the first is a missed step. The other four are cases where someone did the work and the claim still failed, which is why "we always get auths" is not a sufficient answer when the denial rate says otherwise.

Why appealing is the wrong first instinct

Some authorization denials are winnable. If the service was urgent, if the payer's own portal was unavailable, or if medical necessity is thoroughly documented, an appeal with the clinical record attached is worth filing — and some payers permit retroactive authorization within a stated window, which is faster than an appeal when it applies.

But the base rate is poor compared with other denial categories, and the reason is structural: you are asking a payer to approve, after the fact, a decision it reserved the right to make in advance. Plan the workflow around prevention and treat appeals as recovery of the exceptions, not as the strategy. Denial management works best when it is cleaning up a small residue rather than absorbing a systemic leak.

What prevention actually looks like

• Maintain a payer-by-payer, service-by-service requirement list, and give it an owner who updates it when policies change. This list going stale is the single most common root cause.
• Check requirements at scheduling, not at check-in. An authorization that takes a week to obtain is useless if you discover the need the morning of the procedure.
• Verify coverage first. Authorization sits on top of eligibility — an auth against the wrong plan is not an auth at all.
• Re-verify when anything changes. A rescheduled date, an added procedure, a different surgeon, or a site-of-service change can all invalidate an approval that was correct when issued.
• Record the authorization number, approved codes, unit count, and date range where billing can see them, and reconcile against the claim before it goes out.
• Track which payers permit retroactive requests and how long the window is, so the exceptions get worked inside their deadline.

An authorization denial is not a billing error. It is a scheduling decision that nobody costed.

How to know it is working

Track authorization denials as their own category, by count and by dollars, and separate the five causes above rather than lumping them together — the mix tells you whether your problem is the requirement list, the front desk, or the gap between scheduling and coding. Then watch the share of auth-requiring services verified before the date of service. When that number rises and the denial dollars fall, the front end is doing work the back end used to pay for.

Specialties with high procedural volume feel this first. If you run an orthopedic practice or any service line where imaging, injections, and surgical procedures dominate, authorization discipline is not an administrative nicety — it is most of the difference between a clean month and a bad one. Our prior authorization service exists because this is the one denial category where working the back end harder cannot help.