Anthem Prior Authorization Guide 2026: Operational Workflow, Documents, and Appeals

Quick answer

Anthem prior authorization is a plan- and state-specific workflow for Anthem and Elevance Health Blue Cross Blue Shield products. Before service, verify the member's Anthem state plan, check the current prior authorization source or Availity, identify whether the request routes to Anthem, Carelon Medical Benefits Management, pharmacy, phone, or fax, assemble the required documentation, and track the decision through claim release. Confirm against the current provider manual when requirements are unclear, and route clinical, coding, appeal, or compliance decisions to qualified staff for final review.

Reviewed by: QuickIntell RCM Editorial Team Last reviewed: June 28, 2026

Who this guide applies to

This guide is for provider-side scheduling, referral, authorization, revenue integrity, coding, denial, and AR teams working with Anthem Blue Cross, Anthem Blue Cross and Blue Shield, Empire/Anthem state plans, and related Elevance Health products. It is most useful for teams that support multiple Anthem states or that see a mix of commercial, Medicare Advantage, Medicaid managed care, imaging, surgical, behavioral health, and specialty-drug workflows.

Use this as an operational checklist. Anthem requirements vary by state, plan, product, delegated reviewer, and service. Final clinical judgment, appeal strategy, and compliance interpretation should be handled by qualified staff using the current payer documents.

Anthem portal and source links

Anthem portal routing is fragmented by state and product. Start with current payer sources for the specific member.

Use case	Source
Anthem provider resources	Anthem provider portal
Prior authorization entry point	Anthem prior authorization
Claims and administrative resources	Anthem claims resources
California state-provider example	Anthem Blue Cross California providers
Delegated specialty review	Carelon provider portal
Multi-payer authorization workflow	Availity

Operational rule: verify in the payer portal for the member's state plan and product, then confirm against the current provider manual or prior authorization source before acting on ambiguous results.

2026 Anthem prior authorization routing checkpoints

Anthem prior authorization recovery depends on state-level routing. Before submission, record the Anthem state plan, product type, alpha prefix, service category, delegated reviewer, and portal used. A request may belong in Availity, an Anthem state workflow, Carelon, a pharmacy workflow, phone, fax, or another payer-directed path. The same service category can route differently by state and line of business.

The claim team should not treat an approval as reusable unless the billed claim still matches the approved code, units, dates, place of service, rendering provider, facility, and diagnosis context. If any of those facts changed between scheduling and billing, verify whether Anthem requires a modification, renewal, new request, or appeal/reconsideration path.

How Anthem prior authorization work should be structured

Anthem's main operational challenge is variation: state plans, BlueCard routing, Medicaid products, Medicare Advantage products, delegated specialty review, and state-specific phone or fax rules can all change the correct path.

1. Identify the member's Anthem state plan, product type, alpha prefix when applicable, and date of service.
2. Verify eligibility, network status, referral requirements, and benefits.
3. Check whether the planned service requires prior authorization for the exact plan and service date.
4. Determine the correct submission channel: Availity, Anthem state portal, Carelon, pharmacy, phone, fax, or another payer-directed route.
5. Assemble clinical and administrative documentation according to the portal prompts or current provider source.
6. Route missing or ambiguous documentation back to the appropriate owner before submission.
7. Submit the request and store the confirmation number, channel, attachments, timestamp, user, and expected decision path.
8. Monitor status and reconcile approved details to the scheduled service and eventual claim.

Do not assume one Anthem state workflow applies to another. Confirm every request against the current member-specific source.

Common documents required

The exact requirements vary by state, product, service, and delegated reviewer. Most Anthem requests need these packet components.

Document or data element	Operational purpose
Member name, Anthem ID, group number, date of birth, and alpha prefix if present	Identifies the correct state plan and routing
Ordering provider, rendering provider, facility, NPI, tax ID, and network status	Supports provider/facility alignment
Requested CPT/HCPCS, ICD-10, units, service date, and place of service	Aligns the request with scheduling and claims
Recent clinical notes, exam findings, and physician order	Supports review of the requested service
Imaging, lab, therapy, medication, or conservative-treatment history when relevant	Addresses service-specific criteria and pathway questions
Carelon or specialty-review questionnaire answers when delegated	Prevents wrong-channel and incomplete-submission delays
Referral or PCP documentation when required by plan type	Avoids referral/auth mismatch
Existing authorization, denial, or case number for renewal or appeal	Preserves continuity

If staff cannot connect a document to a portal prompt, payer instruction, or denial reason, it should be reviewed before upload. More pages are not always better; relevant documentation is better.

Denial prevention checklist

• Confirm the exact Anthem state plan and product before checking requirements.
• Verify authorization requirements in Availity, the Anthem state portal, Carelon, or the current payer-directed source.
• Confirm against the current provider manual when the portal result conflicts with historical workflow.
• Route imaging, cardiology, musculoskeletal, radiation, sleep, pharmacy, or other delegated categories to the correct reviewer when required.
• Match CPT/HCPCS, ICD-10, units, site of service, provider, facility, and service date to the scheduled encounter.
• Confirm network and referral requirements before submission.
• Attach records that directly answer portal or delegated-review prompts.
• Store confirmation numbers, attachments, timestamps, expected response windows, and status history.
• Monitor pended requests and respond to information requests through the same channel.
• Before billing, reconcile the approved authorization against the service actually performed and route mismatches to qualified staff.

Renewal and resubmission workflow

Anthem renewals and resubmissions should start from the existing case and current state-plan source.

1. Find the existing Anthem, Availity, Carelon, pharmacy, or state-plan case number.
2. Confirm the approved date range, units, provider, facility, place of service, and service codes.
3. If the authorization is expiring before the next visit or procedure, start renewal early and include the existing case number.
4. If Anthem requested additional information, respond through the channel specified in the portal or notice and log the response.
5. If the case was denied or closed, read the notice to determine whether the next step is a corrected request, peer-to-peer, reconsideration, formal appeal, or new request.
6. Re-check eligibility and plan requirements because state products and employer plans can change.
7. Route clinical rationale, coding questions, or appeal strategy to qualified staff for final review.

Do not treat resubmission as a shortcut around an appeal deadline. Use the denial notice and current payer source to confirm the available route.

Appeal workflow

When an Anthem authorization is denied, preserve the procedural record before drafting the response.

1. Save the denial notice, denial date, member plan, case number, service codes, denial reason, cited criteria, and filing deadline.
2. Classify the denial as missing documentation, wrong channel, benefit exclusion, network/referral issue, service mismatch, clinical criteria issue, or untimely request.
3. Determine whether Anthem instructions support peer-to-peer, corrected packet, reconsideration, first-level appeal, second-level appeal, or external review.
4. Build an appeal packet that addresses the exact denial reason and includes relevant new or clarified documentation.
5. Confirm the submission channel and deadline from the denial notice, state portal, or current provider manual.
6. Route clinical rationale to the treating provider or qualified clinical reviewer.
7. Route coding, billing, compliance, or legal questions to qualified staff for final review.
8. Submit the appeal, store proof of submission, and track the decision due date.
9. Add the outcome and root cause to future Anthem denial-prevention rules.

The appeal should not promise an outcome. It should explain why the request should be reconsidered based on the member's plan, current payer criteria, and submitted documentation.

QuickAuth and QuickRCM operational fit

QuickAuth supports Anthem prior authorization by normalizing state-plan variation into one work queue. It can detect authorization requirements, determine whether a request should route to Anthem, Availity, Carelon, pharmacy, phone, or fax, organize documentation, monitor pends and decisions, and flag renewals or service mismatches.

QuickRCM connects the authorization outcome to claims and denial management. It stores the authorization number, approved dates, units, provider/facility limits, denial reason, appeal deadline, and renewal reminders so the billing team can stop a mismatched claim before submission.

The recommended operating pattern is review-based automation: QuickAuth performs intake, routing, packet assembly, submission tracking, renewal reminders, and appeal packet preparation; QuickRCM prevents downstream claim mismatches; qualified staff make final clinical, coding, appeal, and compliance decisions.

Frequently asked operational questions

Is Anthem the same as Elevance Health for prior authorization?

Elevance Health is the corporate parent, while Anthem remains the provider-facing brand for many Blue Cross Blue Shield products. Operationally, work the member's specific Anthem state plan, not the corporate parent name.

Does every Anthem imaging request go to Carelon?

No blanket rule is safe. Many specialty categories may route through Carelon or another delegated process, but routing depends on state, plan, product, service, and current payer configuration. Verify in the payer portal and confirm against the current source.

What should staff do if Anthem says more information is needed?

Capture the exact missing items, deadline, submission channel, and case number. Assign an owner, gather only relevant records, route clinical content to qualified staff, and upload through the specified channel.

What must be checked before an Anthem-authorized claim is released?

Confirm that the claim matches the authorization number, approved service code, units, date range, place of service, provider, facility, and diagnosis context. If the service changed, verify whether Anthem requires modification, renewal, or a new request.

Related resources

• Prior Authorization Automation: The Complete Guide
• Blue Cross Blue Shield Prior Authorization Guide
• How to Reduce Authorization-Related Denials
• The True Cost of Manual Prior Authorization
• Medical Necessity Denial Prevention
• Denial Appeal Templates and Strategies
• Aetna Prior Authorization Guide
• Cigna Prior Authorization Guide