Virginia Medicaid's 2026 ABA hour and diagnosis changes are pending. The July 28 DMAS bulletin says the state is seeking CMS approval and will announce an effective date later. Until approval and the Mental Health Services Manual update are final, DMAS says the current authorization process remains unchanged. Providers should prepare a disabled future configuration while continuing the current authorized route.

Current status for Virginia Medicaid ABA 20 hour limit diagnosis changes 2026

The Virginia Medicaid ABA 20 hour limit diagnosis changes 2026 package originates in the state's Appropriation Act. It directs DMAS to impose a cumulative 20-hour weekly ABA limit and require an autism diagnosis, with a one-year provisional diagnosis pathway for children age five and younger. The bulletin is equally clear that implementation awaits federal approval and later state guidance. Record the proposal source, checked date, approval state, future effective date, affected program, and recheck owner. A legislative direction does not supply the missing operational start date.

Keep current authorizations on the current route

DMAS says it will make no changes to the current authorization process until CMS approves the changes and the manual update is finalized. Continue to use the live fee-for-service or Cardinal Care source for each member, service, provider, date, request, and authorization. Avoid shortening plans, changing diagnoses, or denying scheduling solely because the future rule is being prepared. Preserve written payer instructions that affect a particular product.

Model the future weekly limit without applying it

The appropriation language describes a cumulative per-recipient limit of 20 ABA hours each week and allows the limit to be exceeded based on documented medical necessity under EPSDT. Build a test rule that aggregates the right member, benefit, services, dates, and units without double counting. Keep it disabled until DMAS defines the covered service set, week boundary, managed-care implementation, exception workflow, transition, and effective date.

Prepare the EPSDT exception as a clinical review path

CMS's EPSDT guidance explains the federal framework for medically necessary services for eligible people under 21. The Virginia bulletin specifically preserves a documented-medical-necessity route above the future cap. A qualified clinician should establish the individualized evidence; operations should track the required state form, payer route, dates, decision, notice, and appeal information once published. A calculated weekly total cannot decide medical necessity.

Build the future exception record around the decision that must be made. Identify the recipient, age on the service date, requested services and hours, assessment evidence, treatment goals, risk of an interruption, less intensive options considered, clinician author, submission artifact, receipt, decision, effective period, and next review. Keep the clinician's recommendation intact if a payer authorizes a different amount. The authorization decision and any notice belong in separate fields so staff can explain the difference accurately.

Separate diagnosis evidence from service need

The future eligibility language calls for an autism diagnosis or a provisional autism diagnosis for a child age five or younger under a DMAS-designated protocol. Do not infer the future diagnostic protocol, eligible evaluator, record age, or renewal rule. Keep diagnosis, referral, clinical assessment, treatment recommendation, authorization, and claim status as separate evidence. Preserve communication and transition planning for anyone whose current care may be affected.

Respect the school-based exclusion and payer boundaries

The appropriation language excludes behavior therapy furnished by local education agency providers through the fee-for-service Medicaid school-based services program. That exclusion does not automatically extend to every school setting or contracted provider. DMAS also notes that managed-care plans may use different guidance from fee for service. Classify program, provider type, service, setting, contract, and payer before applying any future rule.

Build an activation matrix by route

Create a row for fee for service and each Cardinal Care product that actually serves the practice's members. A row stays inactive until it has the controlling notice, effective service date, affected codes, weekly definition, transition rule, diagnosis protocol, exception route, notice path, and payer confirmation. A statewide announcement can start review without proving that every payer has configured the same date or workflow. Record conflicting instructions and obtain a written resolution before releasing affected requests or claims.

The bulletin also tells providers to keep enrollment, contact, license, and service-location information current in Virginia's provider system. Track that operational requirement separately from the future hour and diagnosis policy. An enrolled location does not establish clinical appropriateness, authorization, network participation, or capacity for a particular person.

Prepare continuity communication before activation

Identify current authorizations that could overlap a future effective date, but do not alter them while the current process remains in force. Prepare accessible notices that state what is final, what remains pending, who made each decision, and how the person or legally authorized representative can ask questions or use an appeal route. Record the person's communication method, interpreter or AAC access, assent or dissent when applicable, and any immediate continuity concern for qualified review. A future-rule inventory is an operational tool, not a reason to alarm families or preemptively reduce care.

A fictional readiness register

Leila's Virginia authorization team locks 29 future-change controls across status, member age, diagnosis evidence, weekly aggregation, EPSDT exception, school-program classification, managed-care variants, notices, testing, and family communication. Twenty-two have a source, owner, system location, test case, and recheck trigger. Readiness is 22 of 29, or 75.9%. Seven remain disabled. The measure does not establish CMS approval, an effective date, eligibility, authorization, or payment.

Use a two-state release checklist

For current work, verify the live manual, member, product, authorization, service, provider, setting, and date. For future preparation, verify CMS approval, the DMAS implementation notice, manual revision, effective date, transition, affected codes, weekly definition, diagnosis protocol, EPSDT exception, MCO instructions, notice and appeal path, training, and tested configuration. Keep the two states visibly separate.

Related resources

Sources