To reconcile authorized, scheduled, delivered, canceled, and remaining ABA units, use one versioned ledger with separate records for the payer line, appointment, rendered service, cancellation, charge, claim family, and payer counter. Match member, service, unit basis, provider, setting, and dates before calculating. Count a supported service once, preserve corrections, and show pending or disputed events. Reconcile differences to source evidence before schedule or billing release.

Define Nia's authorized scheduled delivered canceled and remaining unit reconciliation

Nia maintains a stable internal ID for every authorization line and downstream event. She can trace each unit in a dashboard back to a decision, appointment, actual service record, or exception. The multistate authorization unit ledger preserves authorization identity, clinical authorship, client access, payer evidence, dates, unit basis, open work, and downstream controls.

Build the fields Nia needs

The record captures ledger line and version, authorization source and amount, unit definition, provider and setting, effective dates, appointment ID and planned units, appointment status, cancellation source and reason, rendered-event ID and supported units, documentation state, charge ID, claim-family ID and active transaction, payer counter label and data-through date, correction, duplicate or overlap flag, remaining balance, schedule overrun, owner, reconciliation time, and unresolved exception. 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

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

Nia loads source events through the cutoff, links them by stable IDs, and calculates each state separately. She investigates orphaned, duplicated, mismatched, late, and disputed events before publishing the balance.

Define every unit state before adding it

Scheduled units describe future plans. Delivered units describe supported care. Canceled units describe events that did not occur. Billed and paid units describe financial states. Nia never adds these categories into one utilization numerator.

Record the calculation evidence and downstream effect

Nia uses net eligible delivered units for the remaining-authorization calculation. A corrected note changes the rendered event through a preserved version. A replacement or void changes the claim family without creating a second visit. Payer portal counters remain external evidence with a label, retrieval time, and data-through date. When the payer counter differs from the internal ledger, Nia compares included services, claims, dates, unit conversion, and pending adjudication. She leaves the difference open until its scope is understood.

Protect urgent action and current authority

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

Nia locks 34 ledgers. Twenty-six trace every unit state to a source and reconcile lines, dates, providers, settings, corrections, claims, counters, and exceptions. One counts a replacement twice, two add canceled units to delivery, one uses a stale portal counter, one loses a corrected note, and three retain orphaned events. Five repair. Three 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 Nia's measures honestly

Initial ledger integrity is 26 of 34, or 76.5%. Thirty-one ledgers validate, or 91.2%. Authorization lines, appointments, cancellations, rendered events, charges, claim families, counters, and units retain separate units.

Address the main authorized scheduled delivered canceled and remaining unit reconciliation risk

A single remaining-units cell can look precise while mixing scheduled service, unsupported notes, duplicates, corrections, claims, and a payer counter with a different cutoff.

Test Nia's artifact against hard cases

Nia tests cancellation, no-show, early end, late note, corrected note, replacement claim, void, payer lag, duplicate appointment, and orphaned service. 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

Nia confirms source scope, clinical ownership, client access, authorization line, downstream controls, and unresolved work. The authorized scheduled delivered canceled and remaining unit reconciliation 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

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

Control authorization information by purpose

Nia 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

Nia 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