To coordinate ABA authorization across primary and secondary coverage, determine coverage order from current member and payer sources, then create a separate route for each plan. Verify benefits, network, provider status, authorization, dates, units, documentation, other-coverage reporting, claim sequence, remittance evidence, cost-share handling, appeal, and correction rules. Link both routes to the same service episode without copying one plan's decision into the other.

Define Imani's primary-and-secondary coverage authorization

Imani records which coverage is expected to process first and who confirmed that order. She rechecks after employment, custody, birthday-rule, Medicare, Medicaid, or other coverage changes instead of treating order as permanent. The coverage-order and request-state ledger preserves entity roles, source authority, effective dates, decisions, communications, and unresolved work.

Build the fields Imani needs

The record captures episode ID, member and service dates, every coverage and product, subscriber relationship, effective dates, coverage-order source and decision, primary benefit network provider authorization and claim route, secondary benefit network provider authorization and claim route, other-insurance reporting, required primary remittance, cost-share and noncovered handling, timely filing, denial and appeal, correction and refund route, privacy permissions, 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 Imani's workflow

Imani verifies coverage order and independently checks authorization with each plan. She submits or holds claims under the correct sequence and preserves every primary response needed by the secondary. Clinical documentation remains one attributable record, while payer-specific forms, units, notices, claims, and appeals stay separate.

Protect the primary-and-secondary coverage authorization boundary

The CMS coordination-of-benefits page explains Medicare coordination concepts and does not create a universal order for two commercial plans, Medicaid, TRICARE, or every ABA episode. Imani uses the actual plans, programs, employer facts, state rules, and qualified payer guidance. One plan's authorization never establishes the other's coverage or payment.

Keep service release and claims behind their own gates

Imani 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

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

Imani locks 24 fictional dual-coverage episodes. Eighteen contain a sourced order and separate benefit, network, authorization, claim, remittance, cost, and appeal states. One copies primary units to secondary, one reverses order, one lacks other-insurance reporting, two omit required primary remittance, and one has changed employment. 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 Imani's measures honestly

Initial episode readiness is 18 of 24, or 75.0%. Twenty-two episodes validate, or 91.7%. Episodes, coverages, authorizations, claims, remittances, cost shares, and appeals retain separate units.

Address the main primary-and-secondary coverage authorization risk

Blending two coverages can cause missing authorization, reversed claims, duplicate payment, wrong patient balance, or an appeal filed with the wrong plan.

Test Imani's route against hard cases

Imani tests two commercial plans, employer change, Medicaid secondary, TRICARE other coverage, expired primary, retro eligibility, primary denial, coordination update, duplicate payment, and refund. Each test retains its source, effective period, affected entity, member and provider state, expected safeguard, observed result, correction owner, retest, and final disposition.

Run Imani's release test

Imani asks a reviewer to trace one service date from coverage order through both authorization records and the planned claim sequence. The reviewer removes one coverage and changes an effective date to test recalculation. The workflow fails when a copied decision survives, when the secondary lacks required primary evidence, or when cost-share treatment appears before both payer states are known.

Close the route with open work visible

Imani confirms the legal plan or program, product, delegates, network, authorization and appeal owners, provider path, claim receiver, access, communication, and unresolved work. The primary-and-secondary coverage 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

Imani 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. Imani 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. Imani 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. Imani 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. Imani 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. Imani verifies the member's actual program, region, coverage order, and current source.

Control information and preserve access

Imani 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