To close an ABA authorization period with open services and claims visible, stop future release under the expired line while preserving delivered care, documentation, corrections, charges, claims, appeals, client communication, and continuity work as separate states. Reconcile the final unit ledger, identify every appointment and transaction crossing the boundary, confirm next-period authority, and assign each unresolved item an owner and deadline. Closure ends the payer period, not the historical record.

Define Rhea's authorization period closeout

Rhea defines closure narrowly: the old authorization can no longer release new routine service. Delivered events, late documentation, corrected claims, pending appeals, refunds, and client questions continue through their own governed workflows. The authorization-period closure record preserves authorization identity, clinical authorship, client access, payer evidence, dates, unit basis, open work, and downstream controls.

Build the fields Rhea needs

The record captures closeout ID, authorization line and version, end date and timezone, final approved amount, net delivered and remaining units, future appointments, crossing appointments, pending notes, corrected service records, charges, claim families and payer states, retroactive or appeal cases, refunds or patient balances, next-period request and decision, continuity plan, client notice and access, source conflicts, system deactivation, report retention, owner, due date, validation, and final closure. 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

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

Rhea freezes the old line for new service, inventories every dependent record, and assigns open work without deleting the source configuration. She tests that a post-end appointment cannot release under the old line and that historical records remain retrievable.

Separate operational closure from financial finality

A claim can adjudicate or be corrected after the authorization ends. Rhea keeps claim families and financial actions open until their own disposition. She does not reopen service authority merely because a financial transaction remains active.

Record the calculation evidence and downstream effect

Rhea checks appointments on both sides of the boundary, including overnight or cross-time-zone records where relevant. She reconciles remaining units without treating unused approval as lost clinical value or a reason to add service. If continuation is pending, the clinician and client receive a clear continuity plan based on current authority and resources. The next-period configuration receives a new identity even when the payer reuses an authorization number. That prevents later corrections from contaminating the wrong period.

Protect urgent action and current authority

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

Rhea locks 30 closeouts. Twenty-three freeze the old line, reconcile units, preserve delivered work, identify future appointments, keep claims and appeals visible, confirm continuity, and validate next-period identity. One deletes history, two hide pending notes, one releases a crossing visit, one merges periods, and two lack client updates. 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 Rhea's measures honestly

Initial closeout integrity is 23 of 30, or 76.7%. Twenty-eight closeouts validate, or 93.3%. Authorization periods, appointments, services, notes, claim families, appeals, and next-period records retain separate units.

Address the main authorization period closeout risk

A broad closed status can orphan appointments, late documentation, corrections, claims, appeals, and client communications or let expired authority keep releasing new care.

Test Rhea's artifact against hard cases

Rhea tests future appointment, crossing date, late note, corrected service, open claim, appeal pending, remaining units, reused authorization number, next-period denial, and client transition. 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

Rhea confirms source scope, clinical ownership, client access, authorization line, downstream controls, and unresolved work. The authorization period closeout 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

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

Control authorization information by purpose

Rhea 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

Rhea 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