Initial authorization

Initial describes the request's place in a sequence

An initial request typically comes before a continuation, concurrent review, renewal, modification, or appeal. Payers use different labels, so the practice should record the payer's exact transaction type rather than infer it from timing.

HealthCare.gov's preauthorization definition describes a plan decision that a service is medically necessary under its process and warns that preauthorization offers no promise of cost coverage. For ABA, the first request may concern an assessment, a treatment plan, or both in separate steps.

The clinical recommendation and payer decision have different owners

A qualified clinician assesses the person, involves the client and family, and recommends clinically appropriate care within scope. The payer applies its benefit, medical-necessity, provider, and utilization rules. Operations staff can assemble evidence, track requirements, and submit through the permitted route.

The CASP ABA Practice Guidelines public summary places assessment, treatment planning, implementation, and evaluation within ABA care for people diagnosed with autism. Its detailed guidelines require a license. The public page does not define a payer's initial-authorization packet or transfer clinical judgment to administrative staff.

Build the request from current source evidence

A practical initial-authorization record may include:

• member, product, eligibility, and benefit evidence
• requesting, billing, rendering, and supervising provider details
• referral, order, or diagnostic documentation when required
• assessment findings and client-centered clinical rationale
• measurable goals, service codes, units, frequency, setting, and duration
• risk, communication, health, coordination, and transition information
• required forms, signatures, attachments, and submission channel
• received date, reference number, status, due date, and escalation owner

Collect only what the payer and clinical process require. Preserve the submitted version and any later supplement so reviewers can reconstruct the decision.

CMS rules have a defined payer scope

The CMS Prior Authorization API FAQ explains that an API response can approve a request and state its duration, deny it with a specific reason, or request more information. Under CMS-0057-F, process requirements apply to named impacted payers and to medical items and services excluding drugs.

The CMS final-rule page identifies Medicare Advantage organizations, state Medicaid and CHIP programs, Medicaid and CHIP managed-care entities, and QHP issuers on Federally-facilitated Exchanges. It does not place every commercial or employer plan under one federal workflow. Check the specific plan's current rules.

Read the decision at field level

Capture approved and denied services separately. For each line, record service code, units, frequency, setting, provider, location, start and end dates, conditions, and decision reason. A broad “approved” status can hide a lower unit count, shorter period, different setting, or excluded provider.

Eligibility, authorization, clinical recommendation, scheduled care, claim acceptance, adjudication, member responsibility, and payment remain separate states. Recheck any state that can change before service.

A fictional initial request

Nia is a fictional intake coordinator reviewing an eleven-field packet for an ABA assessment. Nine fields are complete. The missing items are the payer's current assessment form and confirmation that the new clinic location is rostered.

Packet readiness is 9 of 11, or 81.8%. Both holds stay in the denominator with owners and due dates. The measure reflects submission readiness; it supplies no forecast of approval, clinical outcome, claim processing, or payment.

After submission, the payer requests one supplement. Staff log it as a new event rather than silently replacing the original packet.

If the request is denied or narrowed

Compare the notice with the submitted request and governing plan source. Identify whether the next route is correction, missing-information response, resubmission, peer-to-peer review, internal appeal, expedited review, external review, or another program process. Each route has its own clock and authority.

Share a plain-language update with the family. Include the decision scope, service dates, open work, and next deadline without presenting authorization as a clinical verdict.

Reconcile the decision before the first visit

Compare the payer response with the scheduled assessment or treatment. Confirm the approved service, provider, location, modality, units, start date, and expiration. A decision for an assessment cannot automatically release treatment, and an approval for one clinic location may exclude another.

Record any mismatch as a named hold with an owner. When the payer corrects a field, preserve the first response and the replacement. This history matters if a later claim, appeal, or utilization review asks which decision was active on the service date.

Give the request a stable identity with member, product, provider, service, code, units, setting, requested dates, payer route, receipt, missing-information events, decision, effective period, and appeal rights. Do not overwrite the initial decision when a corrected, reconsidered, or later concurrent request changes the episode.