Prior Authorization & Utilization Glossary

Treat the authorization as a scoped decision

An authorization number is a payer identifier for a request or decision. That identifier cannot establish that every linked claim is covered, clean, accepted, or payable.

The authorization effective period defines the dates or circumstances during which the decision applies. Record the start, end, service dates, decision date, any retroactive reach, and whether a discharge, benefit change, setting change, or quantity exhaustion ends the approval earlier.

Approved units are the quantity the payer authorizes under a defined unit. Preserve the code, modifier, time increment or visit definition, provider type, service, setting, and any frequency or daily limit. A payer's unit can differ from scheduled hours or the unit a clinical plan uses.

HealthCare.gov's preauthorization glossary says preauthorization is not a promise that a plan will cover the cost. Keep clinical recommendation, benefit, network, authorization, claim acceptance, adjudication, and payment separate.

Keep medical necessity review with the right authors

A medical necessity review is a payer or program's evaluation under its coverage criteria and governing sources. The treating clinician authors the clinical assessment, recommendation, goals, risk analysis, dosage rationale, and progress interpretation within scope. Administrative staff may collect requirements and assemble evidence without rewriting clinical content.

The CASP ABA Practice Guidelines public page provides high-level context for assessment, treatment planning, and evaluation in ABA behavioral health treatment of people diagnosed with autism. The detailed Version 3.0 guideline is licensed. Payers decide cases under their governing sources.

CASP's Organizational Guidelines public page describes business, clinical-operations, and risk-management scope. The authorization controls here are an editorial operating model.

Use expedited review for the defined urgency route

An expedited review is a faster payer or program process available when specified urgency criteria are met. Confirm who may request it, the clinical facts required, the submission route, decision clock, notice, appeal rights, and weekend or holiday treatment.

CMS-0057-F requires specified operational provisions for impacted payers. CMS says decision timeframes beginning in 2026 generally include 72 hours for expedited requests and seven calendar days for standard requests for medical items and services, with QHP issuers on Federally-facilitated Exchanges excluded from that particular timeframe requirement. Other laws or payer rules may be shorter.

Do not alter facts or label a request urgent merely to obtain a faster response. A qualified clinician supplies accurate urgency evidence. Immediate health or safety needs use the appropriate emergency route and should not wait for a routine payer decision.

Understand the 2027 API boundary

The CMS final-rule fact sheet applies to Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed-care plans, CHIP managed-care entities, and QHP issuers on Federally-facilitated Exchanges. Its Prior Authorization API covers medical items and services excluding drugs and generally begins January 1, 2027.

CMS's current general FAQ says other commercial and employer plans are outside the mandatory payer scope. An API requirement does not prove a payer endpoint is live, complete, current, or connected to the practice.

Release scheduling through exact gates

Before scheduling, match the approval to the member, product, service, provider, site, modality, dates, codes, unit definition, quantity, referral or order, clinical recommendation, consent, staff, supervision, and safe accessible setting.

Create alerts before period end or expected exhaustion, with enough lead time for assessment, family discussion, clinical review, documentation, and payer processing. A warning should name the affected services and owner. It should never auto-rewrite a plan or request.

Reconcile utilization without double counting

Track authorized, scheduled, delivered, documented, released, submitted, adjudicated, and paid units separately. Reconcile by member, authorization, service date, code, provider, site, and payer-defined unit.

If one authorization covers several services, do not pool quantities unless the artifact expressly does. Preserve voided visits, corrected claims, cancellations, denials, and late documentation as distinct events.

Review variance by cause. A difference between authorized and delivered units may reflect family choice, clinical change, illness, staffing, access, scheduling, payer delay, or data error. That difference cannot automatically represent unused capacity or lost revenue. Pair utilization with the client's goals, continuity, burden, outcomes, and the clinical reason for any service change.

Audit alerts by due cohort, including missed, delayed, duplicate, and false alerts. Record whether the responsible person acted and whether the issue reached final reconciliation.

A utilization example

A fictional practice locks 18 active authorizations for weekly review. Sixteen have a verified decision, period, unit definition, provider and site scope, quantity, and current source, or 16/18, 88.9%. Across those 16, 13 pass the scheduling-release gates, or 13/16, 81.3%.

The two incomplete records and three held releases remain visible by age and reason. The ratios show authorization evidence and operational readiness. They do not establish coverage or future payment.

Start or grow your ABA practice with Finni. Confirm current prior-authorization, utilization, payer-source, security, reporting, and human-review capabilities during diligence.