Revenue Cycle Management
Prior Authorization: Where the Workflow Breaks Down and What Practices Can Track
Where prior authorization fails operationally — identification, ownership, documentation, tracking, matching — what CMS-0057-F changes, and the metrics worth monitoring.

Prior authorization (PA) is a payer's requirement that certain services, procedures, or medications be approved before they are provided in order to be covered. Physicians and payers disagree about how much of it is necessary — the AMA tracks physician experience through an annual survey, and payers point to utilization and cost management (AMA: prior authorization research & reports). This article sets that debate aside. Whatever one's view of PA, it is part of the workflow today, and where it breaks down is largely an operational question.
Where the rules come from
PA requirements are set by each payer and plan, and they change. Reference points worth knowing:
- Medicare Advantage, Medicaid, CHIP, and certain Exchange plans. The CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) requires impacted payers — Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the Federally-facilitated Exchanges — to meet new requirements. Beginning in 2026, impacted payers (other than those QHP issuers) must send PA decisions within 72 hours for expedited requests and seven calendar days for standard requests; payers must give a specific reason for denials; and payers must publicly report PA metrics annually, with the first reports due March 31, 2026. A Prior Authorization API is required generally beginning January 1, 2027, with exact dates varying by payer type. The rule applies to medical items and services, not drugs (CMS: CMS-0057-F fact sheet).
- Original Medicare historically has used PA sparingly. The CMS WISeR Model, running from 2026 through 2031 in six states (New Jersey, Ohio, Oklahoma, Texas, Arizona, and Washington), adds a prior authorization option for selected services; providers who don't request PA face pre-payment review instead (CMS: WISeR Model).
- Commercial plans set requirements through their own policies and contracts, and publish authorization lists that are updated periodically.
The practical upshot: which services need PA, and how fast you'll get an answer, depends on the payer, the plan, and sometimes the site of care.
Where the workflow breaks down
1. The requirement isn't identified
The most expensive failure is not knowing PA was required until the claim denies. It usually happens because the requirement is checked from memory, the payer's list changed, or the patient's plan (for example, a Medicare Advantage plan rather than Original Medicare) wasn't recognized at scheduling.
2. No clear owner
PA sits between clinical and administrative work. When no single role owns it, requests start late and follow-up depends on whoever remembers.
3. Documentation isn't ready
Payers approve based on clinical information — history, prior treatment, test results, and rationale. Requests that go out incomplete come back pended or denied, and the clock restarts.
4. Status isn't tracked
Requests submitted through portals, fax, and phone scatter across systems. Without a single tracker, pending requests stall unnoticed and approvals aren't recorded where schedulers can see them.
5. The approval doesn't match the service
An authorization covers specific codes, units or visits, dates, and sometimes a specific provider or location. If the procedure changes, the date moves, or a different clinician performs it, the approval may no longer apply.
6. Clinical and administrative teams aren't connected
Front-office staff can't answer clinical questions from the payer; clinicians don't see the status of requests. Peer-to-peer reviews get scheduled without the treating physician knowing.
Impact on scheduling and the revenue cycle
- Scheduling: visits delayed or rescheduled while PA is pending; slots left open
- Patient experience: uncertainty about whether care will proceed or be covered
- Denials: authorization denials are often hard to overturn after the fact
- Rework: retro-authorization requests and appeals consume staff time
A workflow that holds up
- At scheduling: identify the payer and plan precisely, and check the service against that payer's current PA list.
- Route the request to a named owner with a target start time.
- Assemble documentation using payer-specific checklists for high-volume services.
- Submit and log in a single tracker: patient, payer, service codes, units/visits, date range, provider, location, submission date, reference number, and status.
- Follow up on a fixed cadence; escalate pending requests approaching the service date.
- Record the outcome where scheduling and billing can see it, including the approval number.
- Verify the match before the visit — codes, dates, provider, site.
- Put the authorization number on the claim.
- Handle denials promptly — peer-to-peer, reconsideration, or appeal, per the payer's process.
Metrics a practice can monitor
- PA requests by payer and service, per month
- Turnaround time from submission to decision, by payer
- Approval, pend, and denial rates, by payer and service
- Visits rescheduled due to pending PA
- Claims denied for missing or mismatched authorization
- Authorizations expiring before use
Tracking turnaround by payer is especially useful now that impacted payers are publishing their own metrics under CMS-0057-F; your data shows how those payers perform for your patients.
How this scales to larger organizations
Hospitals and health systems typically centralize PA in patient access or a financial clearance team, working from orders placed across many departments. The breakdown points are the same — identification, documentation, tracking, and matching — but volume makes integration between the ordering system, the PA work queue, and scheduling essential. Many organizations also track PA as a condition of scheduling high-cost services, so procedures aren't booked until financial clearance is complete.
Related: What Practice Owners Should Know About Eligibility Verification · Why Claims Deny After a Clean Submission
Key Takeaways
- Most PA failures are operational: the requirement isn't identified, no one owns it, or the approval doesn't match the service.
- Under CMS-0057-F, impacted payers other than Exchange QHP issuers must decide within 72 hours (expedited) or 7 calendar days (standard) from 2026.
- Track PA volume, turnaround, and outcomes by payer — your own data shows how payers perform for your patients.
Sources & References
Regulations, program rules, and payer policies change. Educational content only — confirm current requirements with the payer, program, or your advisors before acting.
Related Renvara Solution
Practice SupportWant to discuss how this applies to your practice?
Book a Practice Assessment to talk through this operational area with Renvara.
