To request ABA continuity of care during a network transition, document the exact network or contract event, affected member and product, current provider and treatment, clinical and safety implications, member preference, applicable continuity, transition, or out-of-network route, requested period and services, provider terms, authorization, cost, records, communication, and exit plan. Verify current law, plan documents, contract terms, and payer instructions.

Define Jonah's network-transition continuity authorization

Jonah opens a continuity record as soon as a provider termination, product change, network change, or member transition becomes known. He separates clinical continuity from legal entitlement and payer contracting. The continuity request and exit plan preserves entity roles, source authority, effective dates, decisions, communications, and unresolved work.

Build the fields Jonah needs

The record captures request ID, transition event and evidence, notice dates, member product and effective dates, current provider relationship, treatment plan authorization and service status, clinical risk and safe transition needs, client preference and access, applicable state program plan contract or continuity source, requested provider services period and terms, records and handoff, cost and notice, authorization and claim route, payer and provider contacts, appeal escalation and deadline, alternate providers, exit criteria, owner, and validation. Structured fields make role changes and route conflicts visible. Narrative preserves clinical reasoning, member experience, uncertainty, disagreement, legal deferral, corrections, and source limits.

Apply Jonah's workflow

Jonah verifies the event and deadlines, asks the clinician to document person-specific continuity and safe-transition needs, and asks payer, contracting, legal, and access owners to establish the available route. He communicates confirmed facts and options to the person or family. Current care and future scheduling follow documented authority rather than assumptions about a grace period.

Protect the network-transition continuity authorization boundary

Medicaid managed-care rules in 42 CFR 438.208 address coordination between settings, entities, FFS Medicaid, and community supports. Section 438.206 supplies a scoped out-of-network access protection. Neither section creates one universal transition period for every plan. Fully insured, self-funded, Marketplace, TRICARE, and state Medicaid routes require their own sources.

Keep service release and claims behind their own gates

Jonah releases scheduling only after the applicable clinical, member, provider, setting, payer, authorization, access, and safety evidence is current. Claims remain separate and require actual service, documentation, correct configuration, and the applicable payer route. A verified authorization can still coexist with a later denial or different member cost.

Communicate confirmed facts and open questions

Jonah tells the person or family which entity and product were verified, what the payer confirmed, which assumptions shape the estimate, what remains unresolved, and when the route will be checked again. Accessible channels, interpreters, AAC, and a usable correction path are part of the communication record.

Work through Jonah's fictional example

Jonah locks 22 fictional continuity requests after a network contract ends. Sixteen document the event, current care, client choice, clinical need, route, requested period, terms, cost, authorization, handoff, and exit plan. One assumes a grace period, one lacks notice evidence, one omits member cost, one has no alternate search, and two await written payer terms. Four repair. Two remain held. This synthetic example tests workflow and denominator logic. It supplies no clinical, payer, ERISA, Medicaid, TRICARE, privacy, coverage, claim, cost, payment, or legal conclusion for a real person or plan.

Calculate Jonah's measures honestly

Initial request readiness is 16 of 22, or 72.7%. Twenty requests validate, or 90.9%. Transition events, members, providers, continuity requests, terms, authorizations, claims, and exit plans retain separate units.

Address the main network-transition continuity authorization risk

A continuity promise without a sourced route can expose a family to abrupt disruption or unexpected cost while delaying a clinically safe handoff.

Test Jonah's route against hard cases

Jonah tests provider termination, product change, member move, plan switch, Medicaid MCO change, single-case period, appeal, cost disclosure, record transfer, and no alternate provider. Each test retains its source, effective period, affected entity, member and provider state, expected safeguard, observed result, correction owner, retest, and final disposition.

Run Jonah's release test

Jonah asks a reviewer to trace the transition event, notice dates, requested continuity period, provider terms, member cost, authorization, claim setup, and exit trigger. The reviewer also simulates a denial and an earlier provider end date. The request fails if clinical need is treated as legal entitlement, if cost is unknown but described as covered, or if no safe alternative path is active.

Close the route with open work visible

Jonah confirms the legal plan or program, product, delegates, network, authorization and appeal owners, provider path, claim receiver, access, communication, and unresolved work. The network-transition continuity authorization remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, deadline, and escalation route.

Keep payer routing separate from clinical authorship

Jonah uses the CASP ABA Practice Guidelines Version 3.0 public summary only for high-level autism-treatment context and the BACB Ethics Code for covered behavior analysts' competence, client involvement, consent and assent when applicable, assessment, intervention, documentation, and billing duties. Plan and contract interpretation belongs to authorized payer, benefits, legal, or program roles.

Preserve the authorization and payment boundary

The HealthCare.gov preauthorization glossary says preauthorization may be required and is not a promise that a plan will cover cost. Jonah keeps eligibility, benefit, network, prior authorization, clinical recommendation, provider authority, claim acceptance, adjudication, cost share, and payment as separate states.

Classify the coverage before selecting the route

HealthCare.gov distinguishes a self-insured plan, an individual insurance policy, and a qualified health plan. Jonah records the actual legal plan or program, product, plan year, administrator, issuer, and evidence instead of choosing a workflow from an insurance brand or employer name.

Use federal plan-process sources within scope

The DOL employer guide to benefit claims addresses ERISA-covered group health and disability plans, including insured and self-funded arrangements, and excludes several government and other arrangements from that framework. The CMS-0057-F fact sheet has its own named payer classes and non-drug scope. Jonah never merges those authorities.

Keep Medicaid access and coordination duties scoped

Current 42 CFR 438.206 addresses network, out-of-network, timely-access, and accessibility duties for covered Medicaid managed-care entities. 42 CFR 438.208 addresses care coordination within its scope. Jonah applies them only to the relevant state contract and enrollee and never treats them as proof of provider contracting or payment.

Use TRICARE and coordination examples only where they govern

The TRICARE ACD page and TRICARE West clinical-necessity page supply program and regional evidence, not general commercial or Medicaid rules. The CMS coordination-of-benefits page is Medicare-oriented. Jonah verifies the member's actual program, region, coverage order, and current source.

Control information and preserve access

Jonah applies HHS treatment, payment, and healthcare-operations guidance only within its entity, relationship, purpose, and other-law conditions. The DOJ Title III overview addresses public-access duties within scope. The ASHA AAC Practice Portal says AAC users should always have access to their tools. Routing preserves privacy, communication, and accessibility.

Related resources

Sources