Revenue Cycle & Payer Strategy

Verification of benefits and prior authorization

Verification, authorization, and utilization review are one operational chain, not three departments. Where they are run separately, the failures land downstream as denials nobody can trace back.

AuthorAava Healthcare Management Group Editorial Team
ReviewerReviewed for operational accuracy by Dr. Rayan Aava, PsyD, MBA (c.)
Published
Last reviewed
What this page covers

The pre-billing workflow that determines whether billing can work at all.

This page covers eligibility and benefit verification, prior authorization, continued-stay authorization, utilization-review coordination, clinical and administrative handoffs, payer communication, deadline and status tracking, documentation readiness, and escalation and reporting. They are treated as one page because operators treat them as one problem — the same staff, the same handoffs, the same calendar, and the same failure modes.

This workflow sits upstream of denial management. Strengthening it addresses preventable defects before they become claims; denial work alone cannot remediate every upstream failure. Verification and authorization failures are recurring upstream causes of denials that organizations later spend time and money correcting or appealing.

State this plainly

What verification and authorization do not mean.

These four statements should be understood by every person in an organization who touches this workflow. Admissions decisions made on the opposite assumption are one of the more expensive recurring errors in behavioral-health operations.

  • Verification of benefits is not a guarantee of coverage or payment.
  • Authorization is not a guarantee of reimbursement.
  • Benefits, authorization, and medical-necessity decisions remain subject to the applicable plan, payer, policy, clinical facts, and governing requirements.
  • Aava supports operational workflow and management systems; it does not replace payer determinations, qualified clinical judgment, legal advice, or facility-specific compliance review.
The combined workflow

One chain, one owner, one calendar.

Eligibility and benefit verification

Two separate questions that can be collapsed into one. Is the policy active, and are these services — at this level of care, this facility, this network status — a benefit under it? A verification process that answers only the first produces admissions nobody can bill.

Prior authorization

Requirement identified, request assembled with the clinical information the payer will actually evaluate, submitted through the correct channel, and tracked to a determination with a dated owner.

Continued-stay authorization

A high-cost failure point, because care may already be underway. Concurrent review runs on the payer's calendar, not the organization's, and a review that slips by a day can render a clinically appropriate stay unauthorized.

Utilization-review coordination

The interface between clinical judgement and payer process. Aava coordinates the workflow, timing, evidence assembly, and escalation. Aava does not make clinical determinations.

Clinical and administrative handoffs

A recurring structural defect: clinical staff may hold the information the payer needs, administrative staff may hold the deadline, and no one owns the handoff. Authorization losses can arise in that gap.

Payer communication

Dated, documented, attributed. Verbal guidance nobody recorded is not evidence, and it is precisely what an appeal or a payer dispute will later turn on.

Deadline and status tracking

Every pending request in one governed view with an owner and a next action. Authorization is a calendar discipline before it is a clinical one.

Documentation readiness

The clinical record has to support the level of care being requested at the time it is requested, not retrospectively assembled after a denial.

Escalation and reporting

Defined triggers, named escalation paths, and reporting that shows leadership where requests stall — by payer, by level of care, and by owning function.

Why these stay on one page. Splitting verification, authorization, and utilization review into separate operations is exactly what creates the handoff gaps that lose authorizations. The functions share staff, information, deadlines, and consequences. Aava keeps them combined unless query or operating evidence later shows a genuine reason to separate them.
Scope-limited regulatory context

Where federal timeframes exist — and where they do not apply.

The rules below bind only the payers and plans named. They do not describe commercial payers generally, any particular plan, or any state programme. Other payers may operate under different contractual, regulatory, or administrative requirements. Confirm what governs a specific plan with that payer.

  • ERISA-governed group health plans — pre-service determinations. Under 29 CFR 2560.503-1, where a plan conditions a benefit on advance approval, the request is a pre-service claim. The plan must notify the claimant of its determination within a reasonable period appropriate to the medical circumstances and no later than 15 days after receipt, extendable once by up to 15 days in defined circumstances. Where the claimant must supply further information, they must be given at least 45 days to do so.
  • Urgent-care claims. Within that same scope, a claim involving urgent care must be decided as soon as possible taking account of the medical exigencies, and no later than 72 hours after receipt. Where the claimant has not supplied enough information, the plan must say what is needed within 24 hours and allow at least 48 hours to provide it.
  • Concurrent care — the continued-stay provision. This is a provision directly relevant to behavioral-health levels of care. Where a plan has approved an ongoing course of treatment over a period or number of treatments, a reduction or termination of that course before it ends is itself an adverse benefit determination, and the plan must give notice sufficiently in advance to allow an appeal and a determination before the benefit is reduced. A request to extend a course of treatment that involves urgent care must be decided within 24 hours, provided the request is made at least 24 hours before the approved period expires. That 24-hour condition is an operational deadline: when the extension request is made later, the request does not qualify for this specific 24-hour concurrent-care timeframe under 29 CFR 2560.503-1. Other applicable plan terms or urgent-care procedures may still apply.
  • CMS-0057-F — and exactly whom it covers. The CMS Interoperability and Prior Authorization Final Rule, released January 17, 2024, imposes prior-authorization process and data-exchange obligations on a defined set of impacted payers: Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programmes, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the Federally Facilitated Exchanges. Certain provisions applied from January 1, 2026, with API requirements dated later. It is not a general commercial prior-authorization rule, and treating it as one is a planning error.
Parity and utilization management: verify the posture before relying on it. Medical management standards limiting or excluding benefits on medical-necessity or medical-appropriateness grounds — the machinery of prior authorization and concurrent review — fall within the category of non-quantitative treatment limitations that MHPAEA addresses. But on May 15, 2025 the Departments of Labor, Health and Human Services, and the Treasury stated they will not enforce the 2024 MHPAEA Final Rule until a final decision in the pending ERISA Industry Committee litigation plus eighteen months, with that relief limited to what is new in the 2024 rule relative to the 2013 final rule. The Departments confirmed the statutory obligations as amended by the Consolidated Appropriations Act, 2021 remain in effect and that plans may continue to rely on the 2013 final rule and existing subregulatory guidance, and said they are reconsidering the 2024 rule including whether to rescind or modify it. Any operational position built on the 2024 rule’s new standards should be re-verified before it is relied on.
Scope boundaries

What Aava does — and what it does not.

  • Aava can design, staff, operate, and hold accountability for the verification, authorization, and utilization-review workflow, or oversee a vendor performing it.
  • Aava is not a payer and does not issue coverage, benefit, or authorization determinations.
  • Aava is not a utilization-management organization, and nothing on this page represents Aava as one.
  • Aava does not exercise clinical judgment or make level-of-care or medical-necessity decisions.
  • Aava is not a law firm and does not provide legal advice.
  • No eligibility, coverage, authorization, medical-necessity finding, network status, reimbursement, or payment outcome is guaranteed.
Official sources

Go directly to the primary source.

Links to federal agencies and regulations are provided for reference and do not imply affiliation, authorization, endorsement, or approval.

Related: revenue cycle & payer strategy · denial management · behavioral health billing · operations & clinical performance

Important Information and Disclaimer

This publication is provided by Aava Healthcare Management Group for general informational and operational-planning purposes only. It reflects information and official sources available as of the stated last-reviewed date. Federal, state, and local laws, regulations, licensing standards, accreditation requirements, agency interpretations, forms, procedures, and policies may change after publication.

This material is not intended to be—and should not be relied upon as—a complete or definitive statement of applicable law, regulation, policy, licensing requirements, accreditation standards, or facility-specific obligations. It does not constitute legal, regulatory, clinical, medical, tax, accounting, architectural, zoning, fire-code, or other professional advice.

Requirements may differ based on jurisdiction, facility type, ownership structure, services offered, level of care, payer participation, physical location, and other facts. Readers should independently verify current requirements with the appropriate federal, state, and local authorities and consult qualified legal or other professional advisers when necessary.

Aava Healthcare Management Group is not a government agency, accrediting organization, law firm, or healthcare provider. References or links to government agencies, statutes, regulations, forms, or accreditation organizations do not imply affiliation, authorization, endorsement, or approval.

Aava does not guarantee licensure, certification, accreditation, application acceptance, approval, processing time, eligibility, reimbursement, advertising approval, or any other outcome. Aava may assist organizations with operational planning, implementation readiness, management systems, and coordination with appropriate professionals, but contacting or engaging Aava does not replace confirmation with the responsible authority or advice from qualified counsel.

Readers should confirm current requirements directly with the responsible authority. Aava may assist with operational interpretation, readiness planning, implementation, and coordination with appropriate professional advisers.

Last reviewed: · Next scheduled review: October 22, 2026

Start a conversation

Tell us what needs to change.

Whether it is a single department or an entire enterprise, we will tell you plainly what we would operate, how, and what it would take.