Concurrent authorization

Concurrent review happens during an active episode

A payer may authorize an initial period and ask for another review before that period ends. The concurrent request can cover the next portion of care, a change within the current period, or continued services while the payer evaluates updated evidence. The exact timing and effect come from the payer's current rule and decision.

The HealthCare.gov preauthorization glossary describes preauthorization as a plan decision that care is medically necessary under its terms and warns that preauthorization is no promise of payment. Concurrent authorization is one payer-specific form of prospective utilization review during active care.

Reauthorization and concurrent authorization can overlap in everyday language

Reauthorization commonly means a request for a new authorization period after or near the end of the current one. Concurrent authorization emphasizes review during the active course. A payer may use either label for a similar packet, or reserve each term for a different workflow.

Record the payer's exact request type, portal category, form, submission date, review period, current authorization, and resulting decision. The label should never determine the workflow by itself.

Clinical recommendations and coverage decisions have separate owners

The CASP ABA Practice Guidelines Version 3.0 public summary places assessment, treatment planning, implementation, and evaluation within ABA behavioral health treatment for people diagnosed with autism. The detailed guidelines require licensed access. The public summary supplies clinical context rather than payer authorization rules.

An appropriately qualified clinician determines clinical recommendations within scope and involves the client and authorized decision-maker as applicable. The payer decides coverage under its benefit and criteria. Operations can assemble the packet, confirm administrative requirements, track the response, and surface inconsistencies. Software and administrative staff should route clinical questions back to the qualified clinician.

Build the request from current evidence

A useful concurrent-review record identifies:

• member, product, payer, and provider configuration
• active authorization number, services, dates, units, and restrictions
• units delivered, remaining, scheduled, and held through the cutoff
• payer-defined review window, form, route, and due date
• current assessment, plan, progress evidence, and barriers required by the payer
• client and family priorities, communication access, burden, and relevant context
• requested service, dates, units, setting, modality, and clinical rationale
• submission evidence, payer receipt, requests for information, decision, and appeal route

The clinical record supports care. The authorization packet selects relevant evidence for a payer question. Preserve source authorship, dates, corrections, and the version actually submitted.

Current CMS rules cover named payer classes

The CMS Prior Authorization API FAQ says an episode of care can contain multiple prior-authorization requests and that required reporting counts each request individually. CMS-0057-F applies to named impacted payers and medical items and services excluding drugs.

The CMS rule page provides the final-rule context. Its process and API requirements do not create one ABA concurrent-review form, evidence standard, or approval rule for every plan. Other commercial and employer products may follow different sources.

A fictional concurrent review

Sol is a fictional fourteen-year-old with an authorization for 240 treatment units from August 1 through September 30. The payer requires a concurrent packet by September 10 for any request extending beyond September 30.

At the September 3 cutoff, 156 units have been delivered, 24 are scheduled before expiration, and 60 remain unscheduled. Those states total 240 units. The clinician reviews current data and recommends a separately defined next period. Operations submits the signed packet on September 8 and records payer receipt that day.

The payer later approves part of the requested period and denies part. The practice stores requested, approved, denied, and pending units separately. Sol's team reviews the clinical and scheduling effects with the family rather than treating the payer decision as the clinician's recommendation.

Measure each request and each authorization period

Useful measures include requests submitted by the payer window; receipt confirmed; additional-information requests answered by due date; decisions received before the active period ends; and approved, denied, withdrawn, or pending requests.

Track request count, member count, service count, units, and days separately. A late decision may affect continuity even when the eventual outcome is favorable, so decision timing and decision result need different fields.

Segment the measures by payer, product, request type, urgency, service, and submission route so one workflow does not mask another.

Age every open request from its defined submission or receipt event.

Set internal trigger dates before the active authorization ends. Track the payer receipt, missing-information request, submission, decision, effective period, approved units, and appeal route separately. If review remains pending, document the clinical continuity plan and who will explain financial uncertainty to the family.