A LifeWise Washington commercial ABA workflow should identify the exact legal plan, individual or employer-group product, network and current member card before choosing a portal or phone number. LifeWise directs individual-plan work to Evolent or Identifi and group-plan work to Availity, with different authorization forms and contacts. Preserve the member-specific benefit result, clinician-approved request, secure submission, payer receipt and written determination as separate evidence. LifeWise utilization review

Start with the LifeWise product, not a familiar affiliate workflow

LifeWise Health Plan of Washington publishes one provider website for individual and employer-based group plans, but the shared website does not make their operating routes interchangeable. LifeWise provider home The case file should begin with both sides of the current card, the exact legal plan name, product and network, member and group identifiers, coverage dates, funding or administrator evidence when available, and the governing benefit document.

For a LifeWise Washington commercial ABA provider, that distinction matters immediately. LifeWise sends individual-plan users to Evolent for eligibility, benefits and claim information and to Identifi for prior authorization. Group-plan users generally work in Availity. Its education page maintains separate individual and group training materials for plan, network and member-card interpretation. LifeWise provider education and training A saved Premera workflow, Availity result or affiliate logo is not proof that it belongs to this LifeWise member.

Network evidence is also product-specific. LifeWise's directory tells users to know the network and use the member card or authenticated account before searching. LifeWise provider directory Preserve the search inputs, date, result and any uncertainty. A directory result is useful evidence, but it does not by itself establish the ABA benefit, authorization requirement, effective participation for every location or final payment.

This guide is therefore distinct from the protected Premera Washington commercial guide. The organizations may share infrastructure, provider relations and electronic transaction conventions, yet the current LifeWise card, legal entity, product, authenticated tool and contract remain controlling. The Washington Apple Health payer guides are separate Medicaid workflows as well.

Build participation evidence around the actual entity and service location

A reliable participation record connects the contracting entity, TIN, billing and rendering NPIs, practitioner type, each service address, credentialing record, agreement, network terms, roster or provider loading, directory result and written effective date. Those events should remain separate. Application submission is not credentialing approval; credentialing is not an executed agreement; an executed agreement is not proof that every clinician and site is loaded for the member's network.

LifeWise says a provider must be credentialed before requesting a contract and that a contract is not effective until it is signed, returned and countersigned. It uses CAQH and Certify for practitioner credentialing, with separate information requests for facilities and contract changes. LifeWise network participation steps Preserve the CAQH attestation date, Certify application and signature status, correspondence, agreement version, countersignature and network attachment rather than replacing them with a portal screenshot.

The portal evidence is especially date-sensitive. LifeWise announced an updated CertifyOS credentialing portal beginning September 1, 2026. It advised users to finish in-progress applications before the upgrade, reset passwords at first login and bookmark the new portal. LifeWise September 2026 credentialing portal change Record the actual access email, URL, status and submission evidence used on the case.

Contract terms are transitioning too. LifeWise says its updated standard agreement applies across Washington LifeWise plans and lines of business, usually beginning in November 2026 for existing providers while new-provider dates begin during the summer. Exact start dates and phased operational provisions belong to the provider's delivered agreement. LifeWise 2026 provider agreement FAQ A public FAQ is not the clinic's contract or fee schedule.

Professional authority is a different layer. Washington distinguishes licensed behavior analysts, licensed assistant behavior analysts and certified behavior technicians. Washington ABA licensing requirements Chapter 18.380 RCW supplies the state framework. Washington applied behavior analysis law National certification, state authority, professional supervision, LifeWise credentialing, contracting and claim recognition should not be collapsed into one approval.

Route authorization by individual or group plan

LifeWise explicitly says individual and group plans use different utilization-review tools, code lists and forms. Individual-plan requests use Identifi; the public page says portal registration can take one to five business days and supplies an individual fax alternative during that wait. Group-plan requests use Availity, while the public group code-check tool is not member-specific. LifeWise utilization review

That separation belongs in the record. Capture the card and plan type, member-specific requirement lookup, code and service question, selected portal or current form, clinician-approved supporting material, secure transmission, reference number, payer receipt, additional-information request and response, and final written decision. A registration confirmation, successful upload or fax transmission does not prove LifeWise received a complete request or approved the service.

LifeWise's contact page lists different clinical-review phone and fax routes for individual and group plans. LifeWise contact directory Use the card and authenticated product instruction to select the lane; do not keep a fax number as a universal ABA rule. The forms page likewise separates individual and group materials and should be rechecked when a saved form is reused. LifeWise provider forms and appeals

LifeWise lists Carelon and other healthcare benefit managers, but its partner page describes categories of work rather than assigning every service for every member to one company. LifeWise healthcare benefit managers The utilization page names Carelon for advanced imaging and eviCore for group outpatient rehabilitation. It does not establish either as the universal ABA administrator. A staff member should confirm current ABA responsibility from the exact member and product evidence before transmitting protected information.

Treat the ABA policy and public webpage conflict as a verification stop

LifeWise's current policy 3.01.510 is effective May 1, 2026 and revised April 27, 2026. It describes diagnosis, service categories, settings, provider types, supervision, coding and benefit application. It also says some plans may apply additional or different criteria and directs providers to member contract language and other plan information. LifeWise ABA medical policy 3.01.510 The policy is a guide, not a member-specific coverage decision or payment promise.

There is a material public-source conflict that should not be hidden. The current policy says ABA services may be delivered in person, by secure real-time audio and video, or in a combination. The current LifeWise behavioral-health webpage says direct ABA by telehealth is not medically necessary and not covered, while allowing some remote supervision. LifeWise behavioral-health provider guide The medical-policy index separately warns that benefit plans control coverage and that medical necessity does not guarantee coverage. LifeWise medical-policy disclaimer

Do not choose whichever statement is more convenient. Before scheduling or billing telehealth, preserve the member's benefit language, current plan-specific policy version, authenticated requirement result and a dated written or reference-numbered LifeWise clarification. Escalate the conflict to the responsible payer and qualified clinical or legal reviewer. This article does not resolve it and does not authorize telehealth.

Clinical decisions remain clinician-owned. Diagnosis, assessment interpretation, functional findings, goals, intensity, setting, caregiver work, supervision, coordination, progress, transition and discharge must reflect the actual member. Administrative staff may assemble records, flag missing evidence and transmit clinician-approved material. They should not invent clinical facts, backdate signatures or rewrite a plan to imitate payer wording.

The behavioral-health page also discusses LABA billing under a supervising LBA, separate notes when supervision and direct treatment occur together, treatment-plan updates, team meetings and school-related boundaries. LifeWise behavioral-health provider guide Each point still needs reconciliation with Washington scope, the contract, current product evidence and the actual encounter.

Convert the determination into narrow service controls

When a written determination arrives, compare it with the request rather than recording only "approved." The working record should identify the member and product, request number, provider and site if specified, service or code scope, approved dates, units or quantities, frequency, setting, conditions, continuation requirements and any difference from the clinician's request. Assign each mismatch before the schedule or claim assumes broader authority.

Authorization does not prove network participation, professional authority, correct coding or payment. The rendered record should identify who actually provided and supervised the service, the date and setting, the work performed, member response, relevant caregiver or coordination activity, signatures and any transparent correction. The claim should be derived from that record, not the other way around.

LifeWise's payment-policy disclaimer keeps eligibility, benefit limits, medical policy, adjudication edits, professional scope and the applicable fee schedule as separate payment conditions. LifeWise payment policies A code appearing in the ABA policy therefore does not establish a rate, benefit, authorization or payment.

Change control should be specific. A new card, product, network, legal entity, TIN, clinician, location, setting, code, quantity or date range may reopen only the affected questions. Preserve the former evidence and the fact that changed. Clinical revisions require the qualified clinician; payer-routing or authorization-scope changes require current LifeWise confirmation.

Trace claims through LifeWise rather than through an affiliate assumption

LifeWise's electronic-transactions page lists professional and institutional claim payer ID 00430, but it tells providers to verify payer IDs with their clearinghouse because the clearinghouse may require a different routing value. LifeWise electronic funds and claims The member card, product, receiver instructions and actual agreement should still be reconciled before release.

Before sending the transaction, compare four clusters: the member and card with the service dates; the contracted organization with its TIN; the billing, rendering, taxonomy and place-of-service identifiers; and the encounter's diagnosis, procedure, modifier, units and charge. Each cluster should reconcile to the rendered documentation and authorization evidence. LifeWise supports 837 claims and describes frequency code 7 for replacements and 8 for voids, with the original LifeWise claim number in the transaction. Those are transaction instructions, not permission to correct the clinical record silently.

Build the trace in chronological stops. Archive the exact 837 sent; then the intermediary's accept or reject response; next LifeWise's recorded receipt and status; after that the adjudication and explanation of payment; and finally any offset, refund, EFT or deposit. An intermediary acknowledgment is not LifeWise receipt. An adjudication is not proof of deposit. A paid claim does not retroactively establish participation or medical necessity for a different service.

The public contact and electronic-claims pages display different paper addresses for different functions. Current LifeWise contact page Use the current notice and product-specific instruction rather than treating one address as universal. EDI questions can be routed through the published LifeWise EDI contact, but a support conversation should be preserved with its date, reference and unresolved items.

Timely filing is contract-sensitive. The 2026 agreement FAQ describes 90-day claim submission and 60-day coordination-of-benefits timing under the updated agreement, with provider-specific effective dates and phased system implementation. LifeWise 2026 provider agreement FAQ Calculate from the agreement and claim circumstance actually in force; never select a longer deadline merely because an older workflow allowed it.

Classify the adverse event before selecting a form

A rejection, denial, underpayment or recoupment should first be classified. Eligibility, benefit exclusion, network status, missing authorization, medical necessity, coding, duplicate submission, missing documentation, corrected claim, timely filing, coordination of benefits, overpayment, provider appeal and member appeal do not share one remedy.

LifeWise's forms page separates corrected claims, supporting documentation, coding-policy reconsideration and provider appeals. For group-plan appeals it currently identifies 425-918-5592 as the main fax and notes different routes for clinical and general appeals. LifeWise provider forms and appeals The contact page tells individual-plan providers to use the number on the member's card for physician and provider appeals, while it publishes a group mailing address. LifeWise provider contacts The actual notice, product, contract, standing and deadline control.

Member authorization is another independent issue. The provider appeal form embeds authorization for a provider acting on the member's behalf. Preserve the signed authorization when required, the exact decision challenged, filing destination, transmitted packet, payer receipt and response. Do not turn a member-rights appeal into a billing correction or submit protected material through an unverified lane.

A concise issue memo can keep the process honest: what happened, which evidence supports that classification, which record or term controls, who owns the next decision, when the deadline expires and what proof of filing is required. If the classification changes, preserve why. An operational team can organize the record without deciding legal standing or promising reversal.

Maintain a LifeWise-specific case map

A practical LifeWise case map has four linked but independent strands. The product strand preserves the current card, legal entity, individual or group plan, network, coverage dates and authenticated benefits. The participation strand preserves entity, clinicians, sites, credentialing, agreement and effective loading. The authorization strand links the member-specific requirement and clinician-approved packet to submission, receipt and determination. The revenue strand follows the rendered service through claim, adjudication, remittance and deposit.

Imagine a fictional Washington ABA practice receiving a LifeWise card. Staff identify it as an employer-group product rather than borrowing an individual or Premera route. They prove that the entity, clinician and location are effective for the card's network; then they use the member-specific Availity path, flag the public telehealth conflict, obtain a dated LifeWise clarification and preserve the clinician-approved request. After the written determination, they open only the authorized boundary and trace each rendered service to the correct claim receiver and remittance. No one portal response substitutes for the other strands.

The new provider agreement and CertifyOS portal transition remain dated operational evidence in that map. Preserve the agreement delivered to the practice, its exact effective date, current application status and any phase-in notice. Public summaries help identify questions, but they do not replace those records.

Finni publicly presents credentialing, billing and operational services for ABA practices. Finni provider services In a LifeWise workflow, bounded support may organize evidence, follow open items and reconcile status. It cannot decide whether a LifeWise Health Plan of Washington or LifeWise Assurance Company benefit applies, make individual and group routes interchangeable, grant Washington authority, determine care, approve authorization, set a fee, guarantee payment or choose appeal standing. Write the work order so its permitted records, safeguards and escalation owners are explicit.

Related resources

Sources