How to Check Prior Authorization Status Across Payers

TL;DR

  • Check prior authorization status in the payer's provider portal first, or in a multi-payer portal such as Availity when the payer uses it. Use the phone line when the portal shows nothing or the status is unclear.
  • Have the member ID, the auth or reference number, the rendering and requesting provider NPIs and tax ID, the CPT/HCPCS codes and the dates of service ready before you look.
  • For Medicare Advantage and Medicaid managed care, standard prior authorization decisions now have a 7-calendar-day ceiling (phased in from January 1, 2026) and expedited decisions a 72-hour ceiling, with possible extensions. Time your follow-ups to those clocks.
  • Generally beginning January 1, 2027, payers covered by CMS-0057-F must offer a Prior Authorization API that communicates whether a request is approved, denied or needs more information. Exact compliance dates vary by payer type.
  • Log every check: channel, date, status, reference number and, for calls, the representative's name.

Seven calendar days. That is the longest a Medicare Advantage plan can now take, absent an extension, to decide a standard request for an item or service subject to its prior authorization rules. If no decision or extension notice has arrived by then, it is time to check prior authorization status and escalate. The harder part is that every payer puts the answer in a different place, labels it differently, and sometimes hands the review to a vendor with its own portal.

Below is a practical guide for patient access and prior authorization coordinators: where status lives, what to have ready, how to read the result, and how to run follow-up across many payers without losing track.

Where prior authorization status lives

Many payers offer several channels. They rarely show identical detail, so it helps to know what each one is good for.

ChannelBest forWatch out for
Payer provider portalStatus, reference number, decision details, uploading recordsSeparate login per payer; search windows and access rules vary
Multi-payer portal (e.g., Availity)Checking several plans from one loginOnly covers payers that use it for authorizations
X12 278 transaction via EDIHigh-volume, system-to-system exchangeDepends on your clearinghouse, practice management system and payer support
Payer phone line or IVRUnclear statuses, missing requests, what's still neededHold times; answers must be documented by hand
CMS Prior Authorization API (from 2027)Standardized electronic status for impacted payersNot required until 2027; payer readiness will vary

Payer provider portals

Many payers expose status in their own portal, and the details can be more specific than the summary suggests. UnitedHealthcare lists its Provider Portal "for online submission and status tracking," alongside an API and EDI. For its Community Plan of Texas, UnitedHealthcare says providers can check the status of an existing prior authorization 24/7 through the Prior Authorization and Notification tool in the portal or by calling Clinical Authorization Services.

Blue Shield of California's step-by-step guide to its AuthAccel tool shows how much the rules of a single portal matter, though it dates from July 2023, so confirm the details in the current portal. The guide says the status table displays all open authorizations and those closed within the last 30 days. Older closed requests require a separate search, and when searching those by date, the guide says to use the decision date rather than the submission date. A servicing provider added through the "Add Unknown Provider" window cannot view the status online; the guide says it must be "known" or in the health plan's database.

Multi-payer portals

Availity describes its Essentials authorization tools as letting providers "Review pending authorizations for all health plans through a dashboard," among other functions. Some plans point providers to it for authorizations. Blue Cross and Blue Shield of Texas, for example, says Availity's Authorizations & Referrals tool lets providers submit requests and "check status on previously submitted requests."

Check whether a specific service is reviewed by a vendor rather than the plan. BCBSTX notes that eviCore "provides utilization management services for BCBSTX," and specialty programs like this can have their own submission and status channels. If a request doesn't appear where you expect, ask whether a delegated vendor handled the review. Our guide to delegated utilization management covers how those arrangements work.

The X12 278 transaction

HIPAA defines a "referral certification and authorization transaction" that covers a provider's request to a health plan for authorization and the plan's response. The currently adopted standard for professional, institutional and dental requests is the X12 278 Health Care Services Review, Request for Review and Response (version 005010X217). BCBSTX describes Availity's Authorizations & Referrals tool as a HIPAA-standard 278 transaction.

Whether you can use 278 traffic for status checks in practice depends on your practice management or EHR system, your clearinghouse and each payer's implementation. Ask your vendor what 278 responses you receive back and how they post to your work queues.

Payer phone lines and IVRs

Phone is still the fallback when a portal shows nothing, the status is ambiguous, or you need to know exactly what document a reviewer is waiting for. Expect to authenticate with the same identifiers you would enter online, and get a reference number for the call itself. Calls are also where most of the manual labor in prior authorization follow-up hides, which our piece on the hidden labor behind prior authorization follow-up breaks down.

The CMS Prior Authorization API (coming in 2027)

The CMS Interoperability and Prior Authorization final rule (CMS-0057-F) applies to 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. CMS calls these "impacted payers." They must implement a Prior Authorization API that, among other things, communicates whether the payer approves a request (and when the authorization ends), denies it (with a specific reason), or requests more information. CMS says this must be implemented beginning January 1, 2027, and that exact compliance dates vary by payer type. The rule excludes prior authorizations for drugs.

For Medicare Advantage, the requirement is codified at 42 CFR 422.122(b), which starts January 1, 2027. Until payers implement it, and until your systems connect to it, portals and phone lines remain the everyday tools. Employer plans and other commercial coverage fall outside CMS's list of impacted payers.

What to have ready before you check

Every channel asks for roughly the same identifiers. Pull them into one place before you start:

  • Member ID and date of birth, exactly as on the card
  • Auth or reference number from the submission, if you have one
  • Requesting and servicing provider NPIs and tax ID. Portals often restrict visibility by tax ID; Blue Shield of California's AuthAccel FAQ (updated January 2026), for example, says you can see requests submitted by providers who share your tax identification number.
  • CPT/HCPCS codes and diagnosis codes as submitted
  • Dates of service and setting (inpatient, outpatient, office)
  • Submission date and channel, which you need when a payer says it has no record

What each status usually means

Payers use their own labels, so read the payer's definitions where they publish them. The categories below are generic.

Status (generic)What it usually meansYour next step
Received / pending / in reviewThe payer has the request and hasn't decidedNote the decision deadline; check again before it passes
Pended for informationThe reviewer needs more documentationFind out exactly what is missing and send it through the channel the payer specifies
ApprovedAuthorized for the codes, units and dates listedRecord the auth number, approved units and validity dates; confirm they match the order
Partially approvedSome codes, units or dates approved, others notTreat the unapproved part as a denial and decide whether to appeal or adjust
DeniedThe request was not approvedGet the specific denial reason; consider peer-to-peer or appeal
Withdrawn / cancelled / dismissedThe request was closed without a decision on the meritsConfirm why, and resubmit if the service is still planned

Some of this is anchored in regulation. CMS-0057-F's API must distinguish approved, denied and more-information-requested. In Medicare Advantage, a plan must give written notice when it denies a service "in whole or in part," so a partial approval is, in regulatory terms, a partial denial that comes with notice rights. MA rules also allow a requester to withdraw a request before a decision and describe when a plan dismisses one. Blue Shield of California shows how payer labels differ: its AuthAccel FAQ uses "In Progress" for open requests that have not been decided and can still accept documentation.

Beginning in 2026, CMS requires impacted payers to give a specific reason for a denied prior authorization regardless of how the request was sent. CMS says the decision may be communicated by portal, fax, email, mail or phone. If you see a bare "denied," ask for the reason.

Building a status-tracking workflow across payers

Tie follow-up to decision clocks

Follow-up works best when it is scheduled against the deadline the payer actually faces. In Medicare Advantage, the standard decision deadline for items subject to prior authorization is 7 calendar days beginning January 1, 2026 (14 days for other standard requests), and the expedited deadline is 72 hours. The plan may extend either by up to 14 calendar days in defined circumstances. In Medicaid managed care, rating periods starting on or after January 1, 2026 use state-set standard timeframes that may not exceed 7 calendar days, with a 72-hour expedited limit and possible extensions. CMS says the new timeframes do not apply to QHP issuers on the Federally Facilitated Exchanges, and other commercial plans are outside the rule's scope, so check state requirements and your contracts.

A workable cadence for most teams:

  1. At submission: record the channel, time stamp and any confirmation or reference number.
  2. Within one business day: confirm the request shows as received. A request that never registered is the most expensive status to discover late.
  3. Before the deadline: check once more ahead of the applicable deadline, earlier for urgent cases.
  4. On a pend: act the same day; the clock you care about is the date of service.
  5. After the deadline: if there's no decision and no extension notice, call and escalate.

Document like someone else will pick it up

Every check should leave a record another coordinator could act on: date, channel, status, auth or reference number, approved units and dates, the representative's name and call reference for phone checks, and the next action with a due date. This matters most when a claim later denies for "no authorization" and you need to show what the payer told you and when. Tracking turnaround by payer also feeds the kind of prior authorization metrics that show where delays concentrate.

Escalate denials quickly

When a denial comes back, the specific reason decides the next move. A missing document may justify a corrected resubmission. A medical necessity denial may warrant a peer-to-peer conversation where the payer offers one; our guide to peer-to-peer review for prior authorization covers how to prepare. Medicare Advantage denial notices must also inform the enrollee of the right to a reconsideration, which is the first step in the MA appeal process.

Where automation fits

Some teams that check dozens of payers a day automate the repetitive checks and keep people on the exceptions. SuperDial's prior authorization workflow uses voice agents that navigate payer IVRs, wait on hold and speak with representatives to retrieve approval, pending, denied, withdrawn or missing-information status, returned as structured data. Whatever tools you use, the tracking discipline above stays the same.

FAQ

Can I check prior authorization status without calling the payer?

Usually. Many payers show status in their provider portal, and some support multi-payer portals or 278 transactions. Calling is still useful when a request is missing, the status is unclear, or you need the exact missing item.

How long should I wait before following up on a prior authorization?

For Medicare Advantage and Medicaid managed care, standard decisions on items subject to prior authorization must come within at most 7 calendar days (from 2026) and expedited ones within 72 hours, unless extended. Confirm receipt within a day, then check again before the deadline. For other plans, use the timeframe in state law or your contract.

Why can't I see an authorization in the payer portal?

Common reasons include searching under a different tax ID or provider than the one on the request, looking outside the portal's default date window, or a review handled by a separate vendor. Blue Shield of California's 2023 AuthAccel guide, for example, describes showing closed requests older than 30 days only through an extra search.

Does the CMS rule apply to my commercial patients?

CMS-0057-F covers Medicare Advantage, Medicaid and CHIP fee-for-service and managed care, and QHP issuers on the Federally Facilitated Exchanges. Employer-sponsored and other commercial plans outside those categories are not on CMS's list of impacted payers, though state laws may set their own rules.

Sources

Run a pilot on a real workflow.

Bring a representative batch, define the output schema, and validate ROI with your payer mix in 30 to 90 days.