A Regence Washington commercial ABA workflow starts by reading both sides of the current member card and confirming the exact health plan, product, network, group arrangement and coverage dates in an authenticated inquiry. Regence BlueShield, a self-funded ASO group, Regence Group Administrators, Uniform Medical Plan, a jointly administered group and an out-of-area BlueCard member can use different benefit, authorization, claim and appeal paths. Keep participation, authorization and payment evidence separate. Regence member identification

Decode the card before choosing a Regence workflow

Regence serves several arrangements that can appear related without being operationally interchangeable. A Washington office may encounter Regence BlueShield group or Individual coverage, a self-funded employer for which Regence supplies administrative services, Regence Group Administrators, Uniform Medical Plan, a jointly administered group, or a member whose home Blue Plan is elsewhere. Regence large-group and administrator products The office should not choose a portal queue, reviewer, payer routing value or deadline from the logo alone.

The product record should capture the current front and back of the card, the member number and prefix, group identifier, exact plan and network wording, employer or administrator notice, coverage dates, and the authenticated eligibility and benefit response. Regence says its cards help identify the health plan, network, product, coverage type, filing route and contact path; Availity can confirm eligibility dates and benefit details for most members. Regence member identification A search for a Regence Washington commercial ABA provider should still resolve to the member's verified network rather than a generic brand result. Store the inquiry date and inputs as well as the response.

The funding and administration distinction changes the controls. Regence explains that an Administrative Services Only group designs its own benefits while Regence performs administration, and that some such groups do not follow every Regence administrative guideline. Regence ASO guidance Regence Group Administrators uses its own portal selection, transaction identifiers, authorization contacts and claim destination. Regence Group Administrators A saved ordinary-Regence workflow cannot stand in for either arrangement.

BlueCard is another independent lane. The prefix, suitcase or product indicator, service location and the provider's applicable agreement help determine the local or home-plan path. Regence's BlueCard filing instructions include shared-county and telehealth location rules and warn that incorrectly routed claims can be rejected. Regence BlueCard claim filing Preserve the evidence used to select the lane rather than translating every blue card into a Regence BlueShield Washington case.

This page is therefore separate from the protected Premera and LifeWise Washington commercial hubs. Those organizations have their own cards, networks, contracts and tools. Shared geography and Blue-system infrastructure do not transfer participation, authorization or payment proof.

Prove the organization, practitioners and locations independently

Participation should be assembled as a chain, not reduced to a single status. Link the legal business name and TIN, billing and rendering NPIs, practitioner specialty and license, each service address, credentialing application, agreement, network attachment, provider loading, directory display and written effective date. A gap in one link should remain visible.

Regence's onboarding sequence requires credentialing, Availity registration, electronic funds transfer enrollment and tax documentation. It also provides an Onboarding Tracker and describes a participation confirmation after agreement signing. Regence provider onboarding Those steps are useful controls, but an application receipt is not credentialing approval, and credentialing approval is not a signed network agreement.

The current credentialing page says Regence began using CAQH for initial and recurring practitioner credentialing on June 15, 2026. It calls for current practice information, supporting documents, authorization for Regence access and periodic recredentialing. Regence credentialing Preserve the CAQH attestation, the exact TIN evidence, requested supplements, committee result and any adverse-decision notice. Do not substitute a national certification profile for the payer's completed review.

Contracting is its own event. Regence states that all required onboarding tasks must be complete before agreement documents are issued and that a provider joining an existing contracted TIN may be added without signing a new agreement. Regence contracting The controlling evidence is the actual organization, network, provider and site effective date, not the appearance of a DocuSign email or an old group roster.

Network additions also need explicit evidence. Regence says a network added after the original agreement requires another agreement and recent 147C documentation. Regence provider networks Directory information must be validated at least every 90 days, yet a directory listing remains only one signal. Regence provider directory guidance Keep directory evidence, written participation, practitioner loading and site loading separate so one does not silently cure another.

Identify the ABA benefit, requirement and decision-maker for this member

Regence's public medical-policy index lists separate policies for ABA treatment and the initial ABA assessment, both shown with an August 1, 2025 effective date. Regence medical-policy index The index establishes that current plan-specific policy material exists; it does not prove that a particular member has the benefit, that authorization applies, or that any code, intensity, setting or rate will be approved.

Member-specific commercial evidence should come first. Regence's commercial preauthorization page covers group, Individual, ASO and joint-administration products, but it repeatedly directs offices to eligibility, network and contract evidence and says some contracts apply different requirements. It also states that preauthorization does not guarantee payment. Regence commercial preauthorization Capture the product selected, code or service checked, provider and location inputs, result, timestamp and any route to a partner.

The electronic authorization tool can report that a service is excluded, does not require authorization, requires Regence review or routes to a vendor such as Carelon or eviCore. Regence electronic authorization That is why a partner name on a public page should not be promoted to a universal ABA rule. The authenticated result for the exact member, provider, service and date is the routing evidence.

Behavioral-health resources add another important boundary. Regence publishes an ABA forms path and a clinical-support line while distinguishing claims and network questions from clinical support. Its FEP subsection routes Washington FEP work to Premera; that narrow instruction does not transfer ordinary Regence commercial ABA to Premera. Regence behavioral-health provider resources Follow the current card and applicable plan instructions.

Authorization evidence should have discrete milestones: requirement check, selected current form or electronic case, clinician-approved supporting record, secure transmission, transaction response, payer or vendor receipt, request for additional information, response, and written determination. An Availity upload is not a completed clinical review. A reference number is not approval. Approval does not prove network status, coding accuracy or reimbursement.

Keep Washington authority and clinical judgment outside the administrative lane

Washington's credential structure assigns different authority to the LBA, LABA and CBT roles. The Department of Health explains the requirements for each credential. Washington ABA licensing requirements State law in chapter 18.380 RCW provides the broader professional framework. Washington applied behavior analysis law National certification, state authority, supervision, Regence credentialing, network participation, authorization and billing recognition are related controls, not one interchangeable credential.

The qualified clinician owns diagnosis and assessment interpretation, functional findings, goals, treatment intensity, setting, caregiver participation, supervision, coordination, progress measurement, transition and discharge decisions. Administrative personnel may check completeness, organize source records, transmit an approved packet and follow open items. They should not invent symptoms, select an intensity to fit a payer screen, alter a signed record, or create a clinical rationale from a template.

Regence says behavioral-health providers must maintain adequate, secure clinical records and supply clinical data when requested for utilization or quality review. Regence behavioral-health resources That recordkeeping expectation does not turn the payer into the treating clinician. It also does not mean every internal note belongs in every submission. Use the current request and minimum necessary information, then preserve what was actually sent.

When reading the public medical policies, preserve their role. They guide coverage review within contract terms; they are not a substitute for the member's governing plan or a written determination. Code presence does not establish a benefit or rate. A medically necessary conclusion does not remove eligibility, network, authorization, documentation, coding or contract conditions.

Service delivery should remain traceable to the determination without being written backward from the claim. For each date, retain the actual provider and supervisor, location or modality, work performed, member response, caregiver or coordination activity when applicable, signatures and transparent corrections. If the card, product, entity, clinician, location, setting, code, quantity or approved period changes, reopen only the affected controls and preserve the prior state.

Turn a decision into a bounded operational record

A useful authorization abstraction records more than “approved.” Compare the written determination with the request and capture the member and product, case number, servicing provider and location, covered service, code scope if stated, date span, units or frequency, setting or modality constraints, continuation requirements and any partial denial. Assign an owner to every mismatch before scheduling or billing proceeds.

The source determination belongs with the abstraction. The commercial page warns that missing a required preauthorization can create an administrative denial and provider write-off, while the electronic tool can route cases to different reviewers. Regence commercial preauthorization A spreadsheet cell without the current determination cannot prove what the payer decided.

The Availity dashboard can display submitted, pending and completed cases and determination letters. Regence electronic authorization Save the case identifier and the letter, not just a screenshot of a colored status. If a vendor handled review, preserve both the vendor case and the Regence or plan evidence that assigned responsibility.

Extensions and modifications need explicit change control. A clinician should approve any clinical update. An administrative operator can compare remaining units, dates and documentation requirements, prepare the current form, secure the clinician's approval and confirm receipt. Never backdate a continuation request or silently treat a new site as covered because the same organization was named earlier.

Eligibility, benefits, participation and authorization should be refreshed at sensible checkpoints: when a new card arrives, before a new episode or material treatment change, at authorization renewal, and when the provider or location changes. The refresh is evidence gathering, not a promise of payment. Document unresolved questions and route them to the payer, clinician, contracting specialist or counsel who owns the decision.

Trace each claim through the correct Regence-related entity

Regence requires contracted providers to use Availity, submit claims electronically and receive payment electronically. Regence Availity resources Its claims page supports standard 270/271, 276/277, 277CA, 837, 835 and 999 transactions. Regence claims submission Those transaction types describe stops in the chain; they do not make an intermediary acknowledgment equal to payer receipt or adjudication.

Before release, reconcile the member number and prefix, coverage dates and product with the entity TIN, billing and rendering NPIs, taxonomy, service location and the actual encounter's diagnosis, procedure, modifier, units and charge. Confirm the receiver from the card, authenticated instructions and clearinghouse setup. Do not copy a Premera, LifeWise, RGA, home-Blue or generic Blue identifier into an ordinary Regence claim.

The claim trace should retain the exact outbound file, submitter response, Regence or responsible administrator's receipt and claim status, remittance, adjustment or recovery, and deposit. Regence says remittance advices include line outcomes, adjustment reason information and provider adjustments, and that processed claims and payments are generated on a regular cycle. Regence payment information An 835 can explain adjudication, but deposit evidence remains a different record.

RGA is a practical exception worth naming. Regence tells offices to select Regence Group Administrators in Availity, use its listed transaction identifier for specified inquiries, seek authorization through RGA, and avoid sending RGA claims to ordinary Regence. Regence Group Administrators ASO arrangements may also have customized requirements. Regence ASO guidance Preserve the card and authenticated group evidence that selected the exception.

BlueCard filing depends on service location, product type, prefix and contracts. Regence's instructions address shared counties, telehealth location, home infusion and medical-record requests. Regence BlueCard claim filing Apply those rules only to the verified BlueCard case. Timely filing, correction and coordination periods should be calculated from the actual agreement, plan and notice; this guide does not invent one universal Regence deadline.

Classify a problem before choosing correction, dispute or appeal

A failed transaction, denied claim and adverse clinical determination are not the same event. First classify eligibility, benefit exclusion, network, missing authorization, medical necessity, claim rejection, coding edit, duplicate, corrected claim, documentation request, timely filing, coordination of benefits, pricing dispute, underpayment, overpayment recovery, provider appeal or member appeal.

Regence explicitly separates pricing disputes from appeals and says post-service provider claims appeals and preauthorization determinations generally use the Appeals application in Availity. Regence pricing disputes and appeals The page also directs certain timely-filing, duplicate and additional-information questions to the Provider Contact Center. The actual denial or remittance, product, contract, standing and date determine the route.

Do not apply that ordinary lane to every related product. The ASO page supplies its own correspondence and appeal destination. RGA publishes a separate appeal workflow. BlueCard can involve the home plan. FEP and jointly administered groups may use distinct instructions. The card, notice and authenticated plan resource should settle the destination before protected information is transmitted.

A short issue record should contain the event, classification, supporting evidence, controlling notice or agreement, responsible owner, deadline calculation, current form or application, proof of filing and response. If the classification changes after payer contact, preserve the earlier theory and the dated reason for the change.

An administrative team can assemble the packet, reconcile exhibits and watch the calendar. It cannot decide legal standing, rewrite medical judgment, waive a member right, promise reversal or assume that a claim correction pauses an appeal period. Escalate uncertainty to the plan, qualified clinician, contracting owner or counsel appropriate to the question.

Operate one Regence case as several connected evidence streams

A durable case map keeps four streams separate. The product stream contains the card, plan or administrator, network, prefix, coverage and benefits. The participation stream contains entity, practitioners, sites, credentialing, agreements and effective loading. The clinical and authorization stream contains clinician-owned records, requirement lookup, submission, receipt and decision. The revenue stream contains the rendered record, claim, acknowledgments, adjudication, remittance and deposit.

Consider a fictional Washington practice receiving a card with a Regence-related name. Staff do not immediately open a generic Regence case. They verify whether the member is ordinary Regence BlueShield, ASO, RGA, UMP, joint administration or BlueCard. They then prove the entity, practitioner and service address for that network, obtain the member-specific ABA requirement, preserve the clinician-approved material and reviewer assignment, and open only the written decision's boundary. Billing follows the receiver and product evidence actually confirmed.

That workflow also protects nearby content. Premera and LifeWise Washington commercial guides cover different payer identities. Washington Apple Health pages cover Medicaid plans. State enrollment, claims, telehealth and fee-control guides address statewide processes. Family, clinical, licensing, startup and HR pages answer other questions. Useful overlap does not make one page a replacement for another.

Finni publicly describes administrative services for ABA practices. Finni provider services In this Regence workflow, a bounded assignment could organize participation evidence, maintain requirement and authorization records, prepare clinician-approved submissions, reconcile claim status and flag deadlines. It cannot determine the member's product from a logo, transfer another Blue Plan's contract, grant Washington authority, decide care, approve authorization, select unsupported coding, set a fee, guarantee payment or choose legal standing.

The operating instruction should name permitted data, access controls, evidence checkpoints and escalation owners. The goal is not to make uncertainty disappear. It is to make the responsible decision-maker, current source and next safe action visible.

Related resources

Sources