To reverify ABA authorization after a member product or payer change, record the old and new coverage identities, effective dates, termination evidence, administrator, product, funding route, member identifiers, benefits, network, provider participation, referral, authorization requirements, and submission channel. Keep the old authorization attached to its original product. Build a new request path from current sources, explain timing and cost uncertainty accessibly, preserve clinical continuity and safety, and update scheduling and claims only after the selected route is supported.

Define Ulan's member product or payer transition reverification

Ulan treats an insurance card change as a coverage transition rather than a field edit. He identifies gaps, overlaps, primary and secondary order, delegated vendors, and requests already pending under the prior product. The coverage-transition authorization map preserves member and product identity, clinical authorship, client access, payer evidence, request lineage, decisions, open work, and downstream controls.

Build the fields Ulan needs

The record captures transition ID, client and member identifiers, reported change and evidence, old payer product administrator and termination, new payer product administrator and effective date, coordination order, benefit and exclusion, network enrollment contract and roster, provider and location, referral order and authorization, clinical recommendation, pending old request or appeal, new submission route, continuity and alternate funding, client notice and estimate, consent for selected financial path, schedule holds, claim cutoff and configuration, refund or recoupment route, owner, recheck, and closure. Structured fields make requests, people, products, sources, dates, versions, attempts, decisions, and holds searchable. Narrative preserves clinical reasoning, client perspective, uncertainty, disagreement, changed facts, corrections, and limits while original artifacts remain attributable.

Keep authorization states separate from care and payment

Ulan separates client choice, clinical recommendation, payer requirement, submission, receipt, information request, decision, scheduling, service, claim, adjudication, and payment. Tools can compare sourced fields and enforce release gates. They cannot create clinical judgment, authorization, lawful disclosure, appeal strategy, or coverage.

Apply Ulan's workflow

Ulan verifies each coverage independently, stops carrying old rules forward, and creates a dated overlap or gap map. Qualified clinical staff address continuity and safety. Payer and finance owners explain supported routes and uncertainty without pressuring the family into a financial choice.

Keep old and new authorization assets isolated

An approval belongs to its member, product, payer, provider, service, and period unless current evidence says otherwise. Ulan never copies its number or units into the new coverage record. He links the histories for continuity while preserving separate requests, decisions, schedules, claims, and patient-responsibility estimates.

Record the decisive evidence and downstream effect

Ulan creates a cutoff table for every coverage: last verified eligible date, first verified eligible date, authorization and referral state, network and provider state, claim release rule, and unresolved retroactivity. Services during an overlap or gap receive a named financial path before scheduling. The family sees the evidence, assumptions, estimated responsibility, and recheck trigger in accessible language. Pending requests under the former product remain in their own queue until formally decided, withdrawn, or closed. When the new payer responds, Ulan updates only the affected period and reconciles any service, claim, refund, recoupment, or patient-balance consequence with the authorized owner.

Control urgent and changed facts

Ulan routes imminent danger, medical emergency, urgent clinical need, suspected abuse or neglect, privacy incidents, and other time-sensitive duties through current authorized paths. Changes to member, product, provider, location, service, date, source, clinical plan, urgency, request, or payer decision reopen affected gates and preserve client communication.

Work through Ulan's fictional example

Ulan locks 34 coverage changes. Twenty-six contain old and new identity, dates, benefits, network, provider, authorization route, continuity, client notice, schedule, and claim controls. One copies an old approval, two miss termination, one omits secondary order, two use a payer-wide rule, one lacks an estimate, and one bills before verification. Five repair. Three remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, payer, coding, privacy, coverage, appeal, claim, payment, or legal conclusion for a real person or plan.

Calculate Ulan's measures honestly

Initial transition integrity is 26 of 34, or 76.5%. Thirty-one changes validate, or 91.2%. Members, products, payers, authorizations, services, schedules, and claims retain separate units.

Address the main member product or payer transition reverification risk

Copying an authorization across coverage can create unsupported service promises, denials, duplicate billing, incorrect patient responsibility, and lost continuity work.

Test Ulan's artifact against hard cases

Ulan tests new employer plan, Medicaid change, secondary addition, retro termination, overlap, gap, delegated vendor, pending old request, out-of-network route, and self-pay choice. Each case retains original evidence, affected people, current state, qualified owner, clock, decision, communication, correction, validation, and next action.

Close the exact state with open work visible

Ulan confirms request identity, source scope, clinical ownership, access, payer state, client impact, downstream controls, and unresolved work. The member product or payer transition reverification remains draft until every named reviewer finishes. Open items retain an owner, age, safeguard, due date, and escalation route.

Keep Ulan's clinical and payer decisions attributable

Ulan 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. Qualified clinicians author clinical content while payers decide authorization under their sources.

Scope the federal prior-authorization rule accurately

Ulan uses the CMS-0057-F fact sheet and CMS FAQ for impacted payer classes, non-drug scope, 2026 process provisions, and APIs generally beginning January 1, 2027. The 72-hour expedited and seven-calendar-day standard decision timeframes exclude QHP issuers on Federally facilitated Exchanges. Other commercial and employer plans require their own sources.

Keep approval and payment separate

Ulan uses the HealthCare.gov preauthorization glossary, which explains that preauthorization can be required before certain services and is not a promise that the plan will cover cost. Authorization, clinical appropriateness, scheduling, service, clean-claim status, adjudication, patient responsibility, and payment remain distinct.

Control authorization data by purpose

Ulan uses HHS treatment, payment, and healthcare-operations guidance and minimum-necessary guidance only after confirming entity, relationship, purpose, and exception scope. Payment and operations work use appropriate role-based limits. The treatment exception for provider disclosures and requests never creates broad authorization-team access.

Use compliance guidance within its boundary

Ulan uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for healthcare compliance, reporting, risk assessment, auditing, incentives, and corrective action. Current payer, product, contract, program, law, coding, and professional sources control the actual workflow.

Keep every payer interaction accessible

Ulan uses the DOJ Title III overview for covered public-accommodation duties within its scope and the ASHA AAC Practice Portal, which says AAC users should always have their tools or devices. Forms, updates, choices, notices, escalation, and review routes preserve usable language, communication, and disability access.

Related resources

Sources