How can an ABA practice enroll with West Virginia Medicaid and submit prior authorization? Enroll the organization and qualified professionals under current provider-participation rules, then configure Policy 519.23 for each member. Verify the age and diagnosis pathway, EPSDT referral, current diagnostic assessment, annual physician order, provider qualifications, setting, and telehealth rules. Obtain authorization before every ABA service and release claims from matching evidence.

Start with the controlling delivery route

West Virginia's Chapter 519 index and current Policy 519.23 are the main ABA program sources. The policy covers eligible members from 18 months through age 20, uses a primary ASD diagnosis made before age eight, and calls for an EPSDT referral. It requires prior authorization before all ABA services and bars backdating.

The statewide provider-manual index is the source-control page for Chapter 300 participation and other referenced chapters. The fee-schedule page supplies dated reimbursement inputs. Policy 519.23 also points telehealth users to the separate telehealth policy, so modality must be verified through both sources.

Keep enrollment and service gates separate

Maintain West Virginia rows by billing entity, qualified clinician or supervised role, location, member route, service, and modality. Track provider enrollment, professional authority, diagnosis-age evidence, current diagnostic assessment, EPSDT referral, annual physician order, authorization, telehealth compliance, claim profile, fee version, and revalidation. A portal receipt cannot replace authorization.

Use verified, pending, held, and expired as the four West Virginia workflow states. Each state should identify the decision owner, authoritative source, scope, effective period, last check, evidence, and next action. Automated checks can detect missing or conflicting values. Enrollment staff, plans, qualified clinicians, billing specialists, and legal or compliance owners make the decisions assigned to their roles.

Build the provider enrollment file

Build the enrollment file under current provider-participation requirements. Preserve ownership, tax identity, NPI and taxonomy, licenses or certifications, staff roles and supervision, service locations, screening, EFT, agreement, approval, and effective date. Add managed-care participation when the member route requires it. Confirm every rendering relationship and portal role. Test eligibility, prior-authorization, claim, and remittance access with approved test data before scheduling covered work.

42 CFR 455.410 requires state Medicaid agencies to screen enrolled providers and enroll covered ordering or referring professionals. 42 CFR 438.602(b) assigns state enrollment, screening, and periodic revalidation duties for managed-care network providers. Its one limited pending-network-agreement period can last up to 120 days, though it supplies no billing effective date or payment promise for a West Virginia provider. The CMS NPI fact sheet explains that an NPI identifies an individual or organization; licensing, credentialing, enrollment, contracting, roster status, authorization, and payment each need separate proof.

Make the configuration record usable

Give each West Virginia row a durable identifier. Use one row for every relevant combination of billing entity, rendering role, location, payer or program, product, service, setting, and submission route. Fields should cover legal name, NPI, tax identifier where needed, taxonomy, license or certification, state provider number, screening, revalidation, contract, credentialing, roster, directory, portal role, authorization receiver, claim receiver, effective dates, source version, and responsible owner. Attach the document or transaction supporting every release-critical field.

Build three operational views from the same West Virginia record. The launch view shows incomplete provider, plan, access, and claim-test work. The client release view joins member eligibility, delivery route, provider and location, qualified clinical decision, authorization, schedule, and units. The reconciliation view links the original claim, acknowledgments, adjudication, remittance, deposit, correction, refund, and recoupment. Restrict sensitive data by role, preserve change history, and hold only the affected configuration when evidence conflicts.

Configure authorization for the member

At intake, verify eligibility and the exact Policy 519.23 pathway. Capture diagnosis timing, the diagnostic assessment's date and required content, EPSDT referral, annual physician order, qualified assessment, individualized plan, provider, location, modality, requested dates and units, and supervision. Submit before service and preserve the receipt, questions, decision, approved scope, and renewal lead time. A missed authorization cannot be repaired by a later backdated request.

Release claims from the service record

West Virginia claim release should compare provider enrollment, member eligibility, all authorization prerequisites, provider and site, actual date and time, modality, code and modifier, units, supervision, and note. Use the manual and fee schedule effective on the service date. Reconcile rejection, adjudication, remittance, recoupment, and deposit separately. Send documentation changes through an attributable correction process with the original record preserved.

A fictional launch review

A fictional Charleston practice reviews 15 provider-member-route rows. Ten are ready. One clinician enrollment is pending, one diagnostic assessment is no longer current under the policy, one annual order is missing, one request was submitted after planned service, and one telehealth row lacks the referenced policy check. Readiness is 10 of 15, or 66.7%.

The West Virginia example fixes its denominator before review begins. A submitted application, user account, directory listing, unrelated approval, or successful claim at another site leaves the held row in the denominator. The owner records the exception, responsible person, due date, next action, and evidence required for release.

Monitor the live workflow

Review Policy 519.23, Chapter 300 and referenced policies, provider manuals, fee schedules, and notices monthly. Measure provider rows active over rows due, authorization packets submitted before service over packets due, diagnostic and order evidence current over cases due, telehealth configurations verified over telehealth rows due, and mature claims adjudicated without resubmission over mature first claims.

Use a West Virginia evidence-expiration calendar that starts well before the authorization renewal. Track diagnostic-assessment currentness, annual physician order, professional credentials, Medicaid revalidation, release forms or assurances, authorization end date, and any telehealth attestation. Assign the earliest expiring prerequisite to the renewal worklist. If updated clinical evidence changes the recommendation, let the qualified clinician revise the plan before operations resubmits the request.

Keep a dated West Virginia change register. For each new notice, manual, fee file, form, contract, or portal instruction, record whether it is current, future, proposed, superseded, or archived; identify affected configurations; test the change on approved fictional data; and document who approved production use. This keeps source maintenance observable instead of relying on staff memory.

Go/no-go review before covered service

  • Provider and staff enrollment are active for the service date.
  • Diagnosis, diagnostic assessment, EPSDT referral, and annual order meet current rules.
  • Authorization is issued before every scheduled ABA service.
  • Telehealth meets both ABA and modality-specific policy.
  • The claim uses the correct manual and fee-schedule version.

A go result applies only to the named West Virginia configuration and service period. When a license, enrollment, contract, roster, authorization, source, or claim control expires, pause new covered-service commitments for that row. Route current clients through qualified clinical, payer, access, and continuity review under the applicable rules.

Related resources

Sources