To identify plan, TPA, and delegated UM roles in ABA authorization, map the legal plan or program, administrator, issuer or funding entity, network, credentialing owner, utilization reviewer, portal operator, correspondence sender, decision maker, appeal owner, claims processor, payment entity, privacy relationship, and escalation contact. Record the source and scope of each delegation. One logo, phone number, or portal cannot establish every role.

Define Gia's plan, TPA, and delegated-UM authorization

Gia treats organizations as role holders rather than one payer blob. An entity can receive a packet while another applies criteria, signs the notice, hears the appeal, or processes the later claim. The authorization role-and-authority matrix preserves entity roles, source authority, effective dates, decisions, communications, and unresolved work.

Build the fields Gia needs

The record captures route ID, member plan and product, legal plan or program, sponsor administrator issuer and funder, TPA, network, credentialing and roster owner, UM vendor and review scope, portal and data recipient, correspondence sender, decision authority, peer-review route, appeal and external-review owner, claims processor and payer ID, remittance and payment entity, privacy and business-associate route when applicable, contract and delegation evidence, dates, conflicts, escalation, 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 Gia's workflow

Gia collects plan, contract, provider, portal, notice, and call evidence, then assigns every workflow action to an entity and role. She asks for written clarification where artifacts conflict. Staff route clinical questions to qualified reviewers, legal authority questions to the plan or counsel, and technical portal problems to the operator without collapsing those answers.

Protect the plan, TPA, and delegated-UM authorization boundary

Delegation can be narrow. Authority to host a portal does not necessarily include benefit interpretation, clinical decision, appeal adjudication, network contracting, claims, or payment. Gia records the action each entity can take, the product and dates covered, and the source that supports that assignment.

Keep service release and claims behind their own gates

Gia 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

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

Gia locks 32 fictional role maps. Twenty-five identify plan, administrator, network, credentialing, UM, portal, notice, appeal, claims, payment, and privacy roles. One treats the portal vendor as decision owner, two confuse network and UM, one sends appeal to claims, one misses a carve-out, and two have conflicting delegations. Five 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 Gia's measures honestly

Initial role-map readiness is 25 of 32, or 78.1%. Thirty maps validate, or 93.8%. Entities, roles, delegations, requests, notices, appeals, claims, and payments retain separate units.

Address the main plan, TPA, and delegated-UM authorization risk

A single payer field can hide a chain of limited delegates and cause misdirected submissions, appeals, disclosures, or claims.

Test Gia's route against hard cases

Gia tests new TPA, separate network, delegated UM, portal vendor, peer reviewer, appeal owner, claim receiver, payment entity, privacy incident, and contract conflict. Each test retains its source, effective period, affected entity, member and provider state, expected safeguard, observed result, correction owner, retest, and final disposition.

Run Gia's release test

Gia gives the matrix to a reviewer who must route an initial request, a portal outage, a peer-review question, an appeal, a claim, and a privacy incident to the proper entities. The test fails when the same contact is chosen by default or when a delegation lacks product and effective-date scope. Each wrong route becomes a targeted correction rather than a full rewrite.

Close the route with open work visible

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

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

Control information and preserve access

Gia 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