Allocate Approved ABA Units Across an Authorization Period

Define Liora's approved-unit allocation across an authorization period

Liora builds an allocation that tests whether the current plan can fit inside the actual authorization and available calendar. The plan exposes conflicts early and retains the clinician's rationale independently from the payer quantity. The authorization-line allocation plan preserves authorization identity, clinical authorship, client access, payer evidence, dates, unit basis, open work, and downstream controls.

Build the fields Liora needs

The record captures allocation ID and version, authorization line and source, clinical-plan version, approved and recommended quantity, unit definition, period and eligible days, frequency or daily constraints, provider and setting, client availability and preferences, communication and access supports, staffing and supervision, holidays and known absences, planned service by week, unallocated balance, forecast uncertainty, gap or overrun flag, clinical review, payer action, client discussion, effective date, owner, and next review. Structured fields make decisions, authorization lines, dates, units, appointments, services, exceptions, and owners searchable. Narrative preserves clinical reasoning, client perspective, source conflicts, uncertainty, corrections, and limits.

Keep clinical authorization service and financial states distinct

Liora separates client choice, clinical recommendation, payer decision, authorization configuration, scheduling, rendered service, documentation, charge, claim, adjudication, payment, appeal, and closure. Software can compare sourced fields and enforce gates. Qualified people retain their actual decision authority.

Apply Liora's workflow

Liora converts all time to the verified unit basis, lays out eligible weeks, and models base, reduced-access, and improved-access schedules. The qualified clinician decides whether the recommended plan changes. Operations documents feasibility and authorization conflicts.

Keep approval capacity separate from dosage

An approved maximum describes a payer state. Liora never asks a team to add clinically unnecessary time merely to consume the approval. When authorized capacity falls below the recommendation, the clinician and payer owner address the mismatch through the appropriate review, appeal, or continuity path.

Record the calculation evidence and downstream effect

Liora records how the allocation handles late starts and uneven periods. A first week with only two eligible days cannot support a full-week assumption. A school break, provider leave, or family travel changes feasibility without changing clinical need by itself. Every scenario names the included dates, eligible-day denominator, scheduled-unit numerator, staffing assumption, and authorization line. The allocation is recalculated after material changes instead of spreading a stale weekly average across the remaining period.

Protect urgent action and current authority

Liora routes imminent danger, medical emergency, urgent clinical need, suspected abuse or neglect, privacy incidents, and other time-sensitive duties through current authorized paths. A payer workflow never delays emergency action. Changes to the member, product, provider, service, plan, setting, decision, date, unit, or source reopen affected gates.

Work through Liora's fictional example

Liora locks 28 allocation plans. Twenty-one align the clinical plan, authorization lines, eligible dates, unit basis, client access, staffing, scenarios, and review triggers. One treats approval as dosage, two mix service lines, one ignores a late start, one omits family availability, and two use an undefined weekly denominator. Five repair. Two remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, payer, authorization, privacy, coverage, claim, payment, or legal conclusion for a real person or plan.

Calculate Liora's measures honestly

Initial allocation integrity is 21 of 28, or 75.0%. Twenty-six plans validate, or 92.9%. Authorizations, clinical plans, service lines, weeks, eligible days, scheduled events, and units retain separate units.

Address the main approved-unit allocation across an authorization period risk

A simple approved-units-divided-by-weeks calculation can hide late starts, access barriers, separate service lines, daily limits, and a clinical recommendation that differs from payer capacity.

Test Liora's artifact against hard cases

Liora tests late start, partial first week, school break, provider leave, family travel, separate services, daily cap, location limit, authorization shortage, and unneeded approved capacity. Each case retains its source, affected person, current state, qualified owner, clock, communication, decision, validation, and next action.

Close the exact state with open work visible

Liora confirms source scope, clinical ownership, client access, authorization line, downstream controls, and unresolved work. The approved-unit allocation across an authorization period remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, deadline, and escalation route.

Keep clinical decisions and authorization states separate

Liora uses the CASP ABA Practice Guidelines Version 3.0 public summary only for high-level autism-treatment context and the current BACB Ethics Code for covered behavior analysts' competence, client involvement, consent and assent when applicable, assessment, intervention, documentation, and billing duties. These sources do not create payer approval, coverage, or payment.

Treat prior authorization as a coverage process

The HealthCare.gov preauthorization glossary describes preauthorization as a plan decision made before certain nonemergency services and explains that it is not a promise the plan will cover cost. Liora therefore keeps authorization, eligibility, benefits, clinical recommendation, service, claim acceptance, adjudication, and payment as separate states.

Use the CMS interoperability rule within its payer scope

The CMS-0057-F fact sheet applies its Prior Authorization API requirements to listed impacted payer classes for medical items and services excluding drugs, generally beginning January 1, 2027. It says the response communicates approval and the end date or circumstance, denial and reason, or a request for more information. Liora treats that as scoped federal process context, not proof that a payer endpoint, authorization, or ABA service is supported.

Use a state program only as a scoped field example

The current Texas Medicaid prior-authorization chapter states that prior authorization is not a guarantee of payment and, for its specified claims, identifies authorization number, NPI, procedure code, dates, required modifiers, and units from the authorization letter. Its claims-filing chapter supplies program-specific claim routes. Liora uses those fields as a concrete Texas example and verifies every other payer independently.

Separate code and provider identifiers from authority

The CMS coding overview explains that a code's existence does not determine coverage or payment. The current CMS NPI fact sheet says an NPI identifies a provider and does not validate licensure or credentialing, enroll a provider, or guarantee payment. Liora keeps code, NPI, licensure, competence, enrollment, contract, roster, authorization, and payment distinct.

Control authorization information by purpose

Liora applies HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming the entity, relationship, purpose, and applicable exception. Role-limited configurations and audit samples use the information needed for their task while preserving full source evidence in the authorized record.

Keep compliance and access controls visible

Liora uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for risk assessment, auditing, reporting, incentives, and corrective action. The DOJ Title III overview applies within its public-accommodation scope. The ASHA AAC Practice Portal says AAC users should always have their communication tools or devices. Scheduling, notices, choices, and continuity preserve usable access.

Related resources

• Forecast ABA Authorization Unit Exhaustion Without Changing Clinical Dosage.
• Release an ABA Authorization Decision to Scheduling and Billing.
• Reconcile Authorized, Scheduled, Delivered, Canceled, and Remaining ABA Units.
• Verify a Written ABA Authorization Decision Before Service Release.

Sources

• Council of Autism Service Providers, ABA Practice Guidelines Version 3.0 public summary.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• HealthCare.gov, Preauthorization glossary.
• Centers for Medicare and Medicaid Services, Interoperability and Prior Authorization Final Rule CMS-0057-F fact sheet.
• Texas Medicaid Provider Procedures Manual, Prior Authorizations.
• Texas Medicaid Provider Procedures Manual, Claims Filing.
• Centers for Medicare and Medicaid Services, Coding and Classification Systems overview.
• Centers for Medicare and Medicaid Services, National Provider Identifier fact sheet.
• U.S. Department of Health and Human Services, Uses and Disclosures for Treatment, Payment, and Health Care Operations.
• U.S. Department of Health and Human Services, Minimum Necessary Requirement.
• U.S. Department of Health and Human Services Office of Inspector General, General Compliance Program Guidance.
• U.S. Department of Justice, Businesses That Are Open to the Public.
• American Speech-Language-Hearing Association, Augmentative and Alternative Communication.