Navigating Payer Approval and Referral Requirements
A specialist visit has been scheduled, the patient’s coverage is active, and the appointment appears ready to proceed. Then someone discovers that the health plan requires a referral from the primary care provider. In another case, the referral is on file, but the requested imaging study needs prior authorization. These are different requirements, and missing either one can interrupt an otherwise routine visit.
Prior authorizations and referrals connect clinical decisions, health plan rules, scheduling, and claims processing. A strong front-end workflow identifies the applicable requirement early, obtains or tracks the necessary documentation, and makes sure the approval actually matches the planned service. It also recognizes when the answer is uncertain and who must resolve it before the account advances.
Two Approvals, Different Purposes
Prior authorization, also called preauthorization, prior approval, or precertification, is a health plan’s review or approval process that may be required before a particular item or service is furnished or covered. A payer may evaluate clinical information, coverage criteria, setting, provider, and other relevant details. The specific standard depends on the payer, benefit, and service. HealthCare.gov defines prior authorization as approval that may be required before care or medication is provided.
A referral is generally a request or direction from a primary care provider (PCP) or another treating clinician for a patient to see a specialist or receive certain services. In many HMO arrangements, a PCP referral is a plan requirement, while other plans may allow direct specialist access. A clinical referral can also be appropriate even when no insurance referral is required. HealthCare.gov explains referrals in the context of specialist care.
| Term | What it establishes | What it does not establish |
|---|---|---|
| Eligibility | Coverage information for the patient and relevant date | That every specific service is covered or authorized |
| Benefit verification | Service-specific benefits, applicable conditions, and cost-sharing information | A promise that a later claim will be paid |
| Referral | A clinician-directed request for specialist care; possibly a plan-required PCP referral | Payer approval for a service that separately requires authorization |
| Prior authorization | A payer decision or determination regarding a specified request | Final claim payment or the absence of all other billing requirements |
| Medical necessity | Clinical and coverage-related support for why a service is appropriate under applicable criteria | That a valid authorization, referral, or claim is automatically on file |
An order is not necessarily a referral, and a referral is not necessarily an authorization. These documents can overlap in an EHR, but staff must confirm their actual function rather than relying on a label. Likewise, an authorization reference number is useful only when it is associated with a verified decision and the correct request.
When These Requirements Enter the Workflow
The need for a referral or authorization is usually identified after the planned service, provider, and health plan are known and before the service occurs. Timing may be especially important for imaging, outpatient procedures, specialist visits, certain therapies, durable medical equipment, and selected medications. Requirements aren't universal across those categories.
Scheduling and preregistration
A scheduling request may trigger an eligibility check and a service-specific review of payer requirements. Staff should gather enough information to identify the planned service accurately, including the rendering provider, facility, procedure or service description, anticipated date, and plan. If the service isn't yet defined, the authorization requirement may remain unresolved.
Before the date of service
An authorization coordinator, referral specialist, ordering office, or another designated employee may assemble documentation, submit the request, check status, and resolve payer questions. A missing document discovered close to the appointment can limit the time available to respond. Tracking should therefore begin before the final check-in whenever feasible.
When the plan or the service changes
A new payer, revised procedure, different provider, relocated service, extended treatment course, or rescheduled appointment can invalidate assumptions made during the original review. A prior approval should not simply be copied forward because the patient or specialty remains the same.
After services are furnished
Staff may discover a missing, expired, or mismatched authorization during claim edits, payer adjudication, or AR follow-up. Post-service correction, retrospective review, reconsideration, or appeal may be available in limited circumstances, but it can't be assumed. Some requirements are expressly prospective, and emergency exceptions or continuity-of-care rules need separate assessment.
Who Is Involved and What Each Team Confirms
| Role or team | Typical contribution | Important boundary |
|---|---|---|
| Ordering or referring clinician | Establishes the clinical need, places orders/referrals, supplies records, responds to clinical questions | Administrative staff should not manufacture clinical justification |
| Scheduling / patient access | Identifies payer and plan, proposed service, facility, date, and missing clearance items | An appointment on the schedule does not prove approval |
| Authorization / utilization management team | Checks payer criteria, prepares requests, tracks determinations and dates, escalates issues | Only authorized clinical personnel should make clinical determinations or conduct peer-to-peer review |
| Primary care / referral office | Creates and transmits needed PCP referrals and relevant medical information | A specialist order alone may not satisfy an HMO plan referral rule |
| Payer / utilization review entity | Provides benefit rules, accepts requests, issues determinations and reference numbers | Its decision may apply to a specific plan, service, provider, facility, and time period |
| Billing / denial follow-up | Confirms claim authorization fields, investigates mismatches and payer outcomes | A claim correction does not retroactively create an approval |
Work allocation varies. A hospital may centralize authorizations, while a physician practice may ask a small scheduling team to coordinate with the ordering clinician. The important question is ownership: who must obtain the approval, who verifies the result, and who may decide whether the appointment can proceed if an item remains unresolved?
Information, Documents, and Systems Used
Authorization work is only as reliable as the identifying information behind it. A request for the wrong patient, coverage, provider, or service may be approved in a system but still fail to support the encounter that actually occurred.
| Data element | What to verify | Example of a mismatch |
|---|---|---|
| Patient and subscriber | Name, date of birth, member ID, policy and relevant relationship | Authorization filed under an old member identifier |
| Plan and date | Payer/product, effective dates, service date and benefit rules | Approval from a plan that terminated before the visit |
| Ordering and rendering providers | Clinician identity, NPI or other required identifiers, network status | Decision references a different specialist |
| Facility / place of service | Site, setting, location, inpatient/outpatient status | Request approved for office care but booked at a facility |
| Services and quantities | Code or description, number of visits/units, laterality when relevant | One unit authorized but multiple units planned |
| Authorization period | Start/end dates and any limits or conditions | Rescheduled visit falls outside valid dates |
| Clinical support | Notes, test results, conservative treatment history, diagnoses as applicable | Payer requests documentation not included with submission |
Common tools and records
- EHR and order management: clinical orders, referrals, encounter history, progress notes, diagnoses, and supporting records.
- Practice management or scheduling system: payer, provider, visit, account, and service data; flags indicating whether clearance is incomplete.
- Payer portals and utilization management vendors: current requirements, request entry, upload portals, status, determinations, and correspondence.
- Phone or secure communications: plan-specific inquiries when a portal answer is unclear, with call reference and representative details recorded as policy permits.
- Workqueues and tracking logs: assigned owner, submission date, pending items, follow-up date, decision status, authorization range, and escalation history.
- Electronic transactions: the HIPAA X12 278 is associated with referral certification and authorization transactions in applicable administrative workflows. Emerging FHIR-based interfaces are a related interoperability development, not a universal replacement already deployed by every plan.
The specific form fields and available functions are payer- and system-dependent. Staff should use the approved route for the request, handle protected health information according to policy, and retain the information needed to reconstruct the decision.
How to Complete a Prior Authorization Review
Step 1: Identify the exact proposed service
Begin with the order and scheduling record. Confirm the procedure, intended clinical setting, rendering and ordering provider, planned date, and the best available code detail. A broad description such as “scan” or “surgery” may not be enough to determine whether a plan requires review. If the order and schedule disagree, resolve the discrepancy before submitting a request.
Step 2: Confirm the applicable plan and requirements
Verify insurance for the expected date of service and identify the specific product. Consult the payer’s current authorization lookup tool, provider manual, plan materials, or authorized representative. Check whether the requirement changes by CPT/HCPCS code, diagnosis, network participation, place of service, or quantity. Record where the requirement came from, and its effective date if available.
Step 3: Determine who must submit the request
Some payers require the ordering practitioner to submit; others permit a servicing provider or facility. Some requests route to a delegated utilization management vendor. Sending correct records to the wrong entity or under the wrong clinician can delay the review. Clarify ownership and transfer the request using the approved process.
Step 4: Assemble sufficient, accurate documentation
Depending on the service and rules, the request may require the order, diagnosis information, relevant history, failed conservative treatment, prior results, medication information, proposed care plan, and urgency rationale. Documentation must reflect the actual record; administrative staff should identify missing material and request it from an authorized clinical source, not add unverified facts.
Step 5: Submit and capture confirmation
Submit via the required portal, transaction, secure fax, or other approved method. Save the submission confirmation, date/time, tracking number, payer or vendor, and any request for additional information. A confirmation that the material was received isn't equivalent to an approval.
Step 6: Monitor and respond to changes
Check whether the request is pending, needs additional records, is approved, partially approved, or denied. Follow up before the appointment or applicable decision deadline. If the plan seeks peer-to-peer review, route it promptly to the appropriate clinician. Where the patient’s condition requires an expedited review, use the payer’s defined urgent-request pathway rather than simply marking a routine request urgent.
Step 7: Validate the actual decision
Read the determination itself. Confirm the patient, plan, exact service, dates, provider/facility, units or visits, and approval conditions. Compare it with the final schedule and order. A partial approval for fewer visits or a different site must be addressed before relying on the number.
Step 8: Communicate, document, and confirm readiness
Update the appropriate workqueue or account fields, communicate any unresolved restrictions to scheduling and the ordering team, and follow the organization’s policy for rescheduling, clinical escalation, or proceeding. If the payer says authorization is not required, document how that was confirmed when policy requires it. Do not tell the patient that a service is guaranteed to be paid.
How a Referral Workflow Differs
A referral usually begins when a clinician directs the patient to another practitioner or service. The ordering or PCP office records the referral and may transfer supporting clinical information. The receiving office reviews whether the patient’s plan requires a formal insurance referral and, if so, who must generate it and what identifiers or approval record the plan expects.
- Verify the plan type and specialist access rule. HMO, POS, and other product rules may differ, including exceptions for specified services.
- Confirm the correct PCP or referring clinician. A referral may need to originate with the PCP assigned under the patient’s plan.
- Match the destination. Verify the receiving specialist, group, specialty, location, and date or visit range where applicable.
- Transmit and track. Send the clinical referral and any plan-required referral request through approved channels; ensure the receiving office can locate it.
- Recheck before the visit. Confirm acceptance and validity after changes in PCP assignment, provider, insurance product, or appointment timing.
Example: a referral that is clinically valid but administratively incomplete
A PCP orders a dermatology consultation and sends the patient’s note to the specialist. The specialist’s scheduler finds the referral in the chart, but the patient’s HMO plan requires a PCP-generated insurance referral number. The clinical referral explains why the visit is needed; it doesn't by itself prove that the plan’s administrative requirement was met. The scheduler contacts the PCP office, confirms the plan-specific process, and documents the result before the appointment.
How to Read Authorization and Referral Statuses
| Status | Meaning in practice | Next check |
|---|---|---|
| Not required | A reviewed source indicates no prior authorization for the defined request | Ensure plan, code, provider and date were correctly assessed |
| Submitted / received | Payer or vendor received a request | Confirm confirmation ID and next review date |
| Pending / in clinical review | No final favorable determination yet | Review time sensitivity and follow-up ownership |
| Additional information requested | Review cannot proceed or finish without specified material | Route exact missing items to the appropriate clinical team |
| Approved / authorized | Determination is favorable for defined services and conditions | Validate units, dates, site, provider and actual performed service |
| Partially approved / modified | Only part of request or a different arrangement is approved | Identify what is excluded and coordinate clinical and scheduling decisions |
| Denied / adverse decision | Payer did not approve requested authorization under its review | Read reason, deadlines, reconsideration or appeal rights and clinical escalation |
| Expired / exhausted | Date or visit/units limit no longer supports future care | Assess extension or new request prospectively |
A tracking log should record both status and evidence. “Approved” without a decision reference, valid range, or matching service detail can create false confidence. Conversely, “pending” doesn't necessarily mean the request is overdue; the applicable timeframe and urgency must be established.
Practical Scenarios: From Requirement to Resolution
Scenario A: approved imaging at the wrong facility
Illustrative example. An MRI is approved for an outpatient imaging location, but scheduling changes the appointment to a hospital outpatient department. The procedure and patient are unchanged. During the final review, the coordinator notices that the authorization decision identifies the original facility. Rather than assuming the number transfers, the coordinator checks the payer’s rules and requests a location update or new determination if required. The scheduling team is told whether the new site is cleared.
Scenario B: authorization covers fewer visits than ordered
Illustrative example. The clinician requests twelve therapy visits. The payer authorizes six visits within a stated date range. The authorization team logs the approved quantity as six, not twelve, and routes the partial determination to the clinical team. Further visits may need additional review, a new request, or an appeal according to the payer’s decision and plan rules. Billing must not use the number as if it covered the full treatment course.
Scenario C: plan changes between request and procedure
Illustrative example. A surgery is authorized under the patient’s existing plan. Before the procedure, the patient starts coverage with a different insurer. Even though the code and surgeon have not changed, staff verify the new plan’s eligibility, authorization requirement, network status, and submission process. The previous plan’s decision is retained in the history but not treated as proof of authorization under the new plan.
Scenario D: authorization denial due to missing clinical records
Illustrative example. A payer issues an unfavorable determination citing insufficient evidence of conservative treatment. The administrative reviewer identifies the exact missing documentation, routes the request to the ordering clinician, and checks whether the payer offers a permissible reconsideration, peer-to-peer process, or appeal. The appropriate clinician evaluates whether additional records already exist and whether the original request is clinically supportable. The team tracks the deadline and does not invent treatment history to obtain approval.
Scenario E: an urgent procedure with incomplete clearance
Illustrative example. A patient’s condition changes, and the clinician indicates that postponement could be harmful. Staff escalate the case through the organization’s urgent clinical and payer pathway, documenting the medical urgency and applicable exception rules. They do not substitute an administrative clearance decision for clinical judgment, and they do not assume emergency treatment should be delayed to finish routine paperwork.
Common Failures, Investigation, and Corrective Action
| Problem | How to investigate | Appropriate response |
|---|---|---|
| No authorization on file | Recheck requirement, service description, plan, vendor portals and correspondence | Obtain prospective request when required; escalate service timing per policy |
| Wrong member or plan | Compare coverage on the service date with submission and determination | Correct account identifiers and pursue required new review |
| Code or service changed | Compare final order/procedure with approved description and codes | Confirm whether amendment or new request is necessary |
| Provider or site mismatch | Check NPI, network, location, specialty, and determination conditions | Request permitted update or reassessment before relying on approval |
| Expired dates or depleted units | Compare service date and prior utilization against approval window/quantity | Request extension or additional visits when allowed |
| Missing clinical documentation | Read precise payer request, review source records and communication history | Obtain real records from authorized clinical staff and submit through proper pathway |
| Referral not received | Verify source office, plan referral number, receiving office and transmission status | Coordinate PCP or referral office correction; confirm receiving office has usable record |
| Denial despite a recorded authorization | Compare claim code, DOS, units, provider, authorization ID and actual remittance reason | Correct claim data if inaccurate or follow plan dispute process if adjudication conflicts with evidence |
Recognizing systemic patterns without confusing them with isolated errors
Repeated missing authorizations might involve a particular payer product, scheduling pathway, code group, interface, or location change. A report can point to a pattern, but it doesn't establish the root cause. A more advanced investigation would sample accounts, compare the requirement in force at the time, trace request ownership, and measure where information stopped or changed. That broader control analysis belongs in a dedicated revenue integrity or operational investigation.
Regulatory Requirements and Important Limits
2026 CMS prior authorization decision timeframes
Under CMS-0057-F, specified impacted payers are subject to operational prior authorization requirements beginning in 2026 for applicable medical items and services, excluding drugs. For covered requests, the general maximum is seven calendar days for standard decisions and 72 hours for expedited decisions, while decisions must also be made as quickly as the patient’s condition requires. The rule’s scope and exceptions matter: its specified timelines do not simply apply to every commercial plan, medication request, referral, or situation. CMS clarifies the covered payer categories and the exception for Qualified Health Plan issuers on federally facilitated exchanges. See CMS prior authorization process FAQs.
The same final rule establishes certain electronic interoperability and prior authorization API requirements with compliance dates generally beginning in 2027. These requirements are not evidence that every insurer currently offers the same electronic workflow. See CMS-0057-F fact sheet.
Traditional Medicare is not identical to Medicare Advantage
Original Medicare and Medicare Advantage operate under different administrative arrangements. Original Medicare does not universally require prior authorization for every covered service, but selected services or programs may require it. For example, CMS’s WISeR Model, active in selected states beginning in 2026, applies prior authorization or pre-payment review to specified Original Medicare items and services under the model’s rules. Staff should consult the program’s actual coverage, service list, geographic scope, and dates rather than broadly asserting that traditional Medicare never requires prior authorization. See CMS WISeR Model.
Authorization does not guarantee reimbursement
A payer may still adjudicate a claim for eligibility on the service date, provider participation, actual services furnished, coding, claim timing, benefit limits, applicable patient cost-sharing, and other requirements. HealthCare.gov explicitly notes that preauthorization is not a promise the insurer will cover the cost. A denial reason must be read carefully before deciding whether the issue is lack of authorization, lack of medical necessity, a data mismatch, or something else.
Operational Checklist for Authorization and Referral Readiness
Before submission
- ☐Confirm patient identity and coverage for the proposed date of service.
- ☐Match the planned service, code details, provider, facility, and setting to the order.
- ☐Determine whether a plan-required referral, prior authorization, both, or neither applies.
- ☐Identify the responsible office and correct payer or delegated vendor.
- ☐Obtain required, accurate supporting documentation.
While the request is active
- ☐Record submission method, reference number, date, owner, and next follow-up.
- ☐Track requests for additional information and any clinical review or peer-to-peer deadline.
- ☐Use expedited procedures only when the clinical criteria and applicable process support them.
- ☐Keep scheduling and clinical staff informed of unresolved restrictions.
Before the encounter or claim proceeds
- ☐Confirm the determination rather than assuming submission equals approval.
- ☐Validate the patient, plan, provider, location, exact service, units, and approved date range.
- ☐Recheck the requirement after a payer, provider, facility, code, or date change.
- ☐Document the approval, no-auth-required finding, partial decision, or unresolved issue.
- ☐Route adverse decisions and missing clearances to authorized staff before proceeding under organizational policy.
Connections to the Rest of the Revenue Cycle
Prior authorization and referral information starts at the front end, but its consequences can appear much later. Registration supplies accurate coverage and patient identifiers. Scheduling and clinical departments specify the proposed service. Utilization management handles review and medical records. Charge capture and coding record what was actually performed. Billing supplies required claim-level authorization information. Accounts receivable teams compare payer responses with what was approved and submitted.
A claim denied for authorization reasons may trace back to an omitted request, a changed site, an expired approval, or an incorrect claim field. The solution depends on which of those events actually occurred. The purpose of the foundational process is to establish a reliable chain of evidence, rather than repeatedly submitting the same account and hoping for a different outcome.
Detailed medical necessity standards, financial clearance, claim edits, appeals, and systematic denial or revenue leakage investigations are separate foundational or advanced topics. Their connections belong here, but they don't replace the actual authorization and referral workflow.
References and Further Learning
The sources below define key terms and support the selected regulatory points. Payer manuals and plan documents are still necessary when evaluating a specific patient and service. Requirements should be checked for current applicability and effective dates.
References
| Source | What it supports |
|---|---|
| HealthCare.gov: Prior Authorization | Consumer-facing definition of a plan approval requirement. |
| HealthCare.gov: Referral | Distinction between a PCP specialist referral and other plan requirements. |
| HealthCare.gov: Preauthorization | Terminology and the important limitation that preauthorization does not guarantee covered cost. |
| CMS: Interoperability and Prior Authorization Final Rule (CMS-0057-F) | Impacted payer categories, phased requirements, and the 2026/2027 implementation distinctions. |
| CMS: Improving Prior Authorization Processes FAQs | Detailed explanation of applicable decision timeframes and payer scope. |
| CMS: WISeR Model | Specific Original Medicare model involving selected services and states beginning in 2026. |
Additional Learning
| Resource | What you can explore |
|---|---|
| HealthCare.gov: HMO | Background on HMO care arrangements and plan restrictions. |
| CMS: WISeR Frequently Asked Questions | Model-specific operational questions about prior authorization and pre-payment review. |
| CMS: CMS-0057-F General FAQs | Implementation and interoperability requirements for impacted payers. |
| HealthCare.gov: How to Appeal an Insurance Company Decision | Consumer-facing starting point for understanding certain appeal rights and steps. |
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.