The median prior authorization turnaround time across U.S. specialty practices sits somewhere between 3 and 5 business days. That number has been stubbornly consistent for years, even as payers have built out electronic submission portals and CMS has pushed for electronic PA mandates. The bottleneck was never really on the payer side. It was always on the clinical side: assembling the right documentation package before any submission happens.
We've been tracking this closely as we build Prioriq's PA automation layer. The practices we've spoken with — rheumatology groups, orthopedic surgeons, multi-specialty outpatient clinics — share a consistent pattern. The actual payer review time, once a complete and well-documented submission lands, is often 24 to 48 hours for non-urgent cases. The 4-day average is almost entirely pre-submission lag.
Where the Time Actually Goes
A typical prior auth request for a specialty medication or procedure involves several distinct steps before anything touches a payer portal. The treating physician completes the clinical encounter. Someone on the care team — often a medical assistant, PA, or dedicated auth coordinator — identifies that the requested service requires prior authorization. They pull the patient's insurance information, check the payer's specific PA requirements for that CPT code, and begin assembling documentation: clinical notes, relevant lab values, previous treatment history, ICD-10 codes mapped to the payer's medical necessity criteria.
This assembly step is where most of the time disappears. For a drug requiring step therapy documentation (meaning the patient must have tried and failed at least two prior therapies before the payer will approve the target medication), the coordinator needs to extract that history from the patient's chart, format it in a way that maps to the payer's language, and attach supporting clinical notes. Manually, for a patient with a complex history across multiple providers, this can take 45 to 90 minutes per request.
For a practice processing 30 PA requests per week — which is modest for a busy rheumatology group — that's 22 to 45 hours of staff time just in documentation assembly before submission. Then add follow-up: checking payer portals, calling the prior auth line when a portal submission disappears into a queue, calling back when the authorization is denied and needs to go to peer-to-peer review.
What Automation Actually Changes
When we talk about automating PA turnaround, the biggest upstream lever is documentation quality at the time of the clinical encounter. Ambient clinical documentation — capturing the encounter in real time, generating a structured SOAP note automatically — means the physician is already producing a chart note that contains the relevant clinical narrative, the assessment, and the plan in a format that maps cleanly to PA criteria.
That sounds like a modest improvement. In practice, it's the difference between a coordinator who spends an hour hunting through a chart for step therapy history and one who has a structured note where that history is already surfaced and formatted. The note doesn't just record the encounter — it records the encounter in a way that anticipates the medical necessity questions a payer is likely to ask.
The second automation layer is PA criteria pre-checking. Before a request is submitted to a payer portal, the system checks whether the documentation package satisfies the payer's own criteria for that CPT/ICD-10 combination. This is not trivial. Payer medical necessity criteria vary — United, Aetna, Cigna, and regional Blues all maintain different clinical criteria documents, and those documents are updated regularly. A request for adalimumab for a new rheumatoid arthritis patient requires different supporting documentation than the same drug for a patient with established disease. A system that has ingested and normalized those criteria can flag gaps before submission.
We are not saying automated pre-checking eliminates all denials — payer criteria language is often ambiguous, and reviewers interpret the same criteria differently. But catching an obvious gap — missing a baseline HAQ-DI score, omitting prior DMARD failure documentation — before submission is genuinely different from getting a denial 3 days later and restarting the process.
A Real Scenario: A Rheumatology Practice in the Mid-Atlantic Region
Consider a 10-provider rheumatology group running roughly 45 PA requests per week, primarily for biologic therapies. Before any workflow changes, their internal benchmark was 4.2 days average from encounter to authorization decision. The breakdown: 1.8 days to assemble and submit documentation, and 2.4 days average payer review time once submitted.
When ambient scribing feeds directly into structured PA documentation — with the SOAP note's clinical reasoning section already formatted around the payer's medical necessity language — the assembly-to-submission window shrinks substantially. The coordinator still reviews everything before submission. The physician still signs off on the note. But the mechanical extraction work is gone. In a scenario like this, the pre-submission time drops to under half a day in a well-optimized workflow, moving the overall average from 4+ days to under 2.
The second lever that appears in these scenarios: first-pass approval rate improvement. When documentation packages arrive complete and structured, payer automated review systems (which handle an increasing share of routine PAs) route them to approval without human reviewer involvement. Human review adds a day. Removing it from requests that don't need it is where the hours-not-days outcome becomes achievable for routine cases.
What "Hours" Actually Requires
It's worth being clear about what achieving same-day turnaround actually demands. It requires several things coming together: the encounter note is generated and reviewed before the encounter slot closes or shortly after; the PA submission is built automatically from that note; and the payer's portal supports electronic submission with a fast automated review pathway for the CPT/ICD-10 combination in question.
Not all payers have fast automated review pipelines. Not all CPT codes are eligible for electronic submission. Some payers for some services still require fax submission or phone-based peer-to-peer review for any prior auth, regardless of documentation quality. For those, the floor isn't hours — it's next business day at the fastest. Automation helps you get to the floor faster, but the floor itself is set by payer infrastructure and process, not by what the practice does.
There's also a meaningful difference between urgent PAs — which have different regulatory timelines — and routine PAs. CMS requires payers to respond to urgent prior auth requests within 72 hours, and to routine requests within 7 days for Medicare Advantage (with the 2024 CMS interoperability rule further tightening timelines). Getting documentation right and submitted quickly matters more for urgent requests where payer turnaround is already compressed.
The Integration Layer That Makes It Work
None of this automation produces results without integration into the practice's EHR and into payer submission channels. The ambient documentation captures the encounter, but it has to write back into the EHR record cleanly — whether that's via a FHIR R4 write-back, an HL7 v2 message to the clinical system, or direct API integration with an EHR vendor. The PA submission has to go somewhere useful: a payer portal API, a clearinghouse integration, or at minimum a structured attachment pre-built for portal submission.
We've built Prioriq to support multiple integration paths because practices don't all run the same stack. Some run Epic with solid FHIR support. Others run eClinicalWorks or Athenahealth with different integration patterns. The PA submission layer connects to payer portals through Availity, Emdeon, and direct APIs where payers have opened them. The integration complexity is real, but it's the work that makes the turnaround improvement a practice-level outcome rather than a feature demo.
What to Measure When You Pilot
If you're evaluating PA automation tooling, the metric that matters most is not approval rate in isolation. It's time-to-approval for cases where the first submission was ultimately approved — that's the cleanest signal for whether documentation assembly and submission quality improved. Denied cases that eventually get approved after peer-to-peer review should be tracked separately; they tell you about documentation completeness gaps, not payer behavior.
Secondary metrics worth tracking: staff time per PA request (in minutes, measured before and after), portal vs. fax submission rate (portal submissions process faster in almost all cases), and first-pass approval rate segmented by payer and CPT code. Those three metrics together tell you where the time went and where it went when it disappeared.
Prior auth turnaround isn't going to drop to hours for every request at every practice. But for the category of routine, elective procedures and specialty medication authorizations where payer automated review applies — which is growing as CMS and state mandates push payers toward electronic PA — same-day submission with next-business-day decision is already achievable for practices that have the documentation workflow right.