Prior Authorization: The Workflow That Prevents Denials

Prior authorization is a pre-service administrative decision process used by many health plans for selected items and services. It is not the same as eligibility and it is not a guarantee that every later claim will be paid. The operational goal is to identify the requirement early, submit the correct clinical and administrative information, track the decision and validity period, communicate it to scheduling/clinical staff, and carry the authorization data into billing. A missing handoff can turn an approved service into a denial months later.

The first question is not ‘how do I request it?’

First confirm whether the member’s exact plan requires authorization for the proposed service, provider, setting, and date. Requirements can differ across products under the same payer. Use the payer portal, current policy, eligibility response, or payer contact channel specified by the organization. Record the source and reference number. If the service changes—different code, later date, more units, another facility—ask whether the existing approval still covers the new plan of care rather than assuming the authorization follows automatically.

Clinical documentation should answer the payer’s criterion

Authorization teams should not invent medical necessity; they assemble the record that supports the clinician’s request. Read the payer’s documentation requirements before faxing a stack of notes. If the policy requires a failed course of conservative treatment, identify where that is documented. If imaging or a specialist note is required, confirm it is present. Missing evidence creates avoidable pend/denial cycles and delays care. When the record does not support the criterion, escalate to the ordering clinician rather than editing clinical language from the administrative desk.

2026 rules make turnaround worth understanding

CMS’s current interoperability/prior-authorization policy requires certain impacted payers to meet operational decision timeframes beginning in 2026: no later than 72 hours for expedited requests and seven calendar days for standard requests for covered medical items and services, subject to program-specific rules and permitted extensions. The CMS-0057-F FAQ explicitly excludes drugs from these timeframes and notes that QHP issuers on the Federally-facilitated Exchanges are not governed by this particular timeframe rule. The major API implementation requirements are generally tied to January 1, 2027. Those federal requirements still do not make every payer, product, or service identical; staff must identify which rule actually governs the request in front of them.

Peer-to-peer is a clinical escalation, not a billing script

Some payer denials allow a clinician-to-clinician review. Administrative staff can identify the option, deadline, phone number, required availability, and documents, but the clinical discussion belongs to the appropriate clinician. Track whether the peer-to-peer occurs and the resulting decision. If the payer instead requires a formal appeal, move the case into that process with the correct deadline. Do not leave a denied authorization in a generic “follow up” queue with no next event.

The final handoff is to the claim

An approval that lives only in a portal screenshot is fragile. Store the authorization number, approved service details, units/visits, dates, and payer reference in the field or workflow that billing can retrieve. At charge review, compare the actual service with the approval. If they do not match, stop and investigate before submitting a claim that is likely to deny. Authorization work succeeds when the approval can be reconstructed months later by someone who did not submit the request.

The approval number is only one field in the authorization record

A usable authorization record should connect the member, payer and product, ordering/referring provider where relevant, servicing provider or facility, requested service, code or service description, approved quantity or visits, date span, authorization number, decision status, submission channel, clinical documents sent, and the person or team responsible for the next action. If any of those elements change between scheduling and service, the team needs to know whether the approval still applies. “Auth obtained” is too vague to protect a claim.

CMS’s interoperability and prior-authorization rule makes the process more transparent for impacted payers, with operational requirements beginning in 2026 and major API requirements primarily in 2027. That policy direction does not erase payer-specific criteria today. Staff still need to verify whether authorization is required for the exact plan and service, submit the requested clinical material, monitor pending decisions, route medical-necessity disputes to the appropriate clinical escalation such as peer-to-peer review, and carry the final authorization data into the claim workflow. An approved request that is never linked to the scheduled service can still become a denial.

Do a final authorization-to-schedule reconciliation the day before service

For higher-risk services, compare the authorization record with the actual appointment before the patient arrives: date, location, rendering provider, service or code family, units or visits, and remaining validity. Reschedules, provider substitutions, or a changed procedure can make an earlier approval unusable. The staff member who spots the mismatch should create a visible hold or escalation rather than assuming billing will fix it after the claim denies. That one pre-service check is often cheaper than an appeal built weeks later.