To forecast ABA authorization unit exhaustion without changing clinical dosage, calculate each authorization line separately from supported delivered units, future eligible appointments, the verified unit basis, remaining quantity, and remaining dates. Use more than one delivery assumption and show data through time, exclusions, and uncertainty. The forecast is an operational alert. A qualified clinician decides whether care changes, while authorization and scheduling owners address payer or capacity conflicts.

Define Mako's authorization unit exhaustion forecasting

Mako forecasts the first date when delivered plus expected eligible service may reach the approved quantity. He uses current source data and preserves pending notes, cancellations, schedule changes, and corrections as visible exceptions. The authorization-line exhaustion forecast preserves authorization identity, clinical authorship, client access, payer evidence, dates, unit basis, open work, and downstream controls.

Build the fields Mako needs

The record captures forecast ID, authorization line and version, unit basis, approved and net delivered units, pending documentation, scheduled eligible units, canceled and blocked units, comparable delivery window, delivery numerator and denominator, remaining units and days, base high and low assumptions, forecast exhaustion date, confidence and exclusions, clinical-plan comparison, provider and setting constraints, alert threshold, client impact, authorization action, owner, as-of time, and validation. 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

Mako 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 Mako's workflow

Mako freezes an as-of snapshot, reconciles corrections once, and runs base, higher-delivery, and lower-delivery scenarios. He routes approaching exhaustion to clinical, scheduling, and payer owners with enough time for a qualified response.

Use net delivered service instead of raw claims

A submitted, denied, replaced, or voided claim is a financial transaction. Mako bases care utilization on the final supported rendered event and uses the active claim-family state only for claim reconciliation. Raw claim totals can double-count one service.

Record the calculation evidence and downstream effect

Mako calculates remaining approved units as approved quantity minus net eligible rendered units for the same line. Future scheduled units are multiplied by a stated delivery ratio only when the comparison window is suitable. He reports the scheduled-overrun test separately: delivered plus future scheduled minus approved. A positive result triggers review before affected service. A low forecast prompts a cause review covering access, staffing, health, preference, cancellations, plan change, and data quality. Neither result automatically changes dosage or compresses missed care into longer visits.

Protect urgent action and current authority

Mako 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 Mako's fictional example

Mako locks 30 forecasts. Twenty-three use reconciled lines, supported service, clear as-of times, three scenarios, uncertainty, clinical comparison, and owner actions. One sums replacement claims, two mix unit bases, one hides pending notes, one uses an undefined delivery window, and two trigger automatic dosage changes. 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 Mako's measures honestly

Initial forecast integrity is 23 of 30, or 76.7%. Twenty-eight forecasts validate, or 93.3%. Lines, services, claims, units, days, scenarios, and alerts retain separate units.

Address the main authorization unit exhaustion forecasting risk

An opaque burn-rate projection can create unnecessary schedule changes, missed care, or excess service when its source events, unit basis, and uncertainty are unclear.

Test Mako's artifact against hard cases

Mako tests replacement claim, pending note, mixed units, late start, cancellation spike, added staff, changed plan, changed authorization, early exhaustion, and low utilization. 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

Mako confirms source scope, clinical ownership, client access, authorization line, downstream controls, and unresolved work. The authorization unit exhaustion forecasting 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

Mako 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. Mako 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. Mako 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. Mako 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. Mako keeps code, NPI, licensure, competence, enrollment, contract, roster, authorization, and payment distinct.

Control authorization information by purpose

Mako 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

Mako 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

Sources