UnitedHealthcare Virginia Cardinal Care ABA coverage follows DMAS rules and UHC's current Virginia authorization route. UHC's July 1, 2026 requirements direct behavioral-health code questions through the member's plan card and provider portal, while Virginia requires requested units for every planned ABA treatment code. Families should verify the product, provider configuration, complete request, approved services and dates, appeal deadline, and any continued-benefit filing.
Confirm the exact UHC Virginia product
Virginia lists UnitedHealthcare of the Mid-Atlantic, operating as UnitedHealthcare Community Plan, among its five current Cardinal Care options. Verify the member's exact Medicaid product, effective date, member number, other coverage, and card contact. Standard Cardinal Care, LTSS, Medicare, dual-eligible, employer, and exchange materials use different requirement sets. Keep only the record that matches this service.
Apply Virginia's current ABA framework
DMAS's ABA clarification covers qualified roles, delegation, initial assessment, setting justification, family involvement, telemedicine, individualized schedules, and documentation. The qualified clinician owns case-specific assessment and recommendations. UHC decides plan coverage. Families contribute goals, access needs, and practical constraints. Administrative systems can track evidence while preserving those decision owners.
List the codes and units before submission
Virginia's October 2025 bulletin requires requested units for each planned treatment code for current Cardinal Care authorizations. Ask the provider for the service code, unit total, frequency, dates, place of service, supervising role, and rendering role. Compare this schedule with the individualized plan and UHC decision. A total weekly hour figure alone cannot replace the code-level request.
Do not activate the July 2026 proposal early
DMAS's July 2026 policy notice says the proposed hour and diagnosis changes await CMS approval, final manual guidance, and a later effective-date announcement. The state explicitly keeps the current authorization process until then. Put the proposal on a dated watch list. Recheck DMAS and UHC before submission, start, and renewal, especially if the requested period extends into a possible implementation window.
Use the current July 2026 UHC source
UHC's Virginia prior-authorization page identifies the current Cardinal Care Medicaid and LTSS requirement lists effective July 1, 2026 and archives earlier versions. Choose the list matching the product and service date. Keep a dated copy or link in the request record. A later list should govern future dates only after its stated effective date, subject to applicable transition instructions.
Follow the behavioral-health routing instruction
The July 2026 standard Cardinal Care list tells providers to call the number on the member's card for specific behavioral-health codes and to use UHC's provider tools. The general list does not publish an ABA code table in that section. Ask the provider to document the code-specific result, representative or portal source, checked date, required route, and submission confirmation. Keep this beside the DMAS code-unit schedule.
Resolve a conflict between UHC sources
A family may hear one answer from the member card phone number while the provider portal shows another requirement or status. Record both answers with the product, service code, place of service, provider status, planned date, source, timestamp, representative, and reference number. Ask UHC to identify which current instruction controls that exact request and to connect any correction to the existing case. Avoid opening duplicate authorizations unless UHC directs that route, because parallel requests can obscure the original receipt date and decision history. If the conflict concerns a clinical fact, return it to the qualified clinician for clarification rather than asking administrative staff to alter the rationale. If it concerns a product, network, or technical field, the provider's authorization team can correct it while preserving the original clinical record. Close the conflict only when the portal, written response, or plan representative gives a documented resolution that the provider can use for scheduling. Keep any unresolved variance visible on the family's checklist.
Verify out-of-network and urgent-care rules
UHC's July list says out-of-network providers must request prior authorization for all procedures and services, while urgent and emergency care are treated separately. For planned ABA, verify the group, supervisor, rendering staff, service location, network status, enrollment, and applicable payment path. An authorization request for a nonparticipating provider does not by itself create a contract, opening, payment amount, or member-cost conclusion.
Create one request timeline
Track the member and product, assessment, individualized service plan, goals, codes, units, frequency, dates, settings, proposed team, progress evidence, and transition plan. Add the UHC requirement version, code lookup, submission route, confirmation, received date, complete-review date, evidence request, response, decision, and next review. Assign each unresolved item to the person who can actually answer it.
Keep communication access intact
Ask how the person communicates preferences, assent, withdrawal, pain, fatigue, and requests when applicable. Maintain speech, AAC, sign, gesture, typing, interpretation, and backup communication. ASHA's AAC portal says users should always have access to their tools or devices. Review school, health care, transportation, sleep, rest, family capacity, and community priorities before finalizing a schedule.
Read UHC's written decision precisely
Match the letter to the request: member, provider, service, code when shown, units, frequency, dates, setting, and conditions. Record approval, partial approval, pending evidence, and denial as distinct states. Prior authorization supports only the written scope. Provider capacity, clean-claim status, adjudication, payment, later renewal, and clinical outcome remain separate and need their own follow-up.
Use the UHC Cardinal Care appeal section
UHC's Virginia member handbook says a member may appeal an adverse benefit determination within 60 calendar days and describes authorized representatives and plan assistance. Current 42 CFR 438.402 supplies the federal structure. The actual notice provides the case reason, deadline, destination, expedited-review path, evidence rights, effective date, and state-hearing instructions. Preserve the complete notice.
Ask for continued benefits on time
When previously authorized services will be reduced, suspended, or terminated, ask UHC about continuation before the notice's effective date. 42 CFR 438.420 provides conditions and possible repayment consequences. Confirm whether the plan appeal and continuation request require separate actions. Save proof of each filing and keep the clinical team working on a safe continuity or transition plan.
Work through Talia's fictional packet
Talia is twelve and uses AAC and typing. Her family tracks eight gates for home ABA and a swim-club goal: active product, participating group, qualified supervisor, current plan, code-unit schedule, complete submission, written decision, and schedule match. Six are complete. UHC has not confirmed complete review, and the decision remains open. Release readiness is 6 of 8, or 75.0%.
Ask UHC only answerable questions
Which UHC Cardinal Care product and July 2026 list apply? What did the code-specific check show? Are the group, supervisor, rendering staff, and location eligible? When was the request received and marked complete? What evidence remains? Which codes, units, dates, and settings were approved? Which appeal, expedited-review, continued-benefit, and hearing instructions appear on the adverse notice? Record every source and reference number.
Join UHC's July source to the code-specific result
Run every planned ABA line through the current UHC route using Talia's exact Cardinal Care product, code, provider status, place of service, and date. Preserve the July requirement set, portal result or member-card call, representative and reference, and the provider's code-unit schedule. If the general list and code-specific answer differ, ask UHC which instruction controls and connect the resolution to the existing case.
Keep eight release gates for active product, participating group, qualified supervisor, current plan, code-unit schedule, complete submission, written decision, and schedule match. The completeness answer and decision remain open even after the other six gates are documented. Avoid parallel submissions unless UHC directs them. A duplicate request can obscure the first receipt, evidence history, and appeal record.
Build one UHC case that exposes provider and setting facts
Index Talia's AAC and typing, priorities, assessment, goals and baselines, codes, quantities, dates, home and swim-club settings, group, supervisor and rendering staff, supervision, coordination, transition plan, and signatures. Save the requirement version, lookup details, request route, attachments, receipt, case number, completeness status, and every supplemental request.
Verify the organization, supervisor, practitioners, home site, and swim-club location independently. For a nonparticipating configuration, ask which authorization and payment arrangement applies and whether a suitable in-network alternative is available. An out-of-network authorization rule does not itself create provider participation, a payment rate, open capacity, or a member-cost conclusion.
Convert UHC's letter into a usable swim-club plan
Create one row per service with quantity, frequency, dates, provider, rendering arrangement, setting, conditions, and outcome. Label approved, partially approved, denied, and pending lines. Add distinct evidence for active eligibility, provider and site recognition, staffing, calendar release, delivery, claim acceptance, and payment.
For home and the swim club, confirm host permission, qualified staff and supervision, AAC and typing access, a backup method, transport, privacy, water-safety boundaries, and fit with school, health, sleep, rest, and Talia's preferences. At day 10, compare approved, scheduled, and delivered services. At day 30, review Talia's experience, communication access, outcomes, cancellations, family effort, claims, and remaining units. Give UHC a dated access log when no usable provider is available and request a named option or written network solution.
Limits and next UHC actions
This guide cannot determine Talia's eligibility, provider or site status, medical necessity, completeness date, authorization, capacity, payment, or appeal outcome. UHC and DMAS can revise lists, portals, rosters, and notices. The current member record and written service-line determination govern the case.
Next, reconcile the July source and code-specific result, verify all eight gates, obtain completeness evidence, and map the decision to both settings. Assign the two open gates and schedule day-10, day-30, source-version, and renewal checks.
Sources
- Virginia Department of Medical Assistance Services, Current Cardinal Care Health Plans
- Virginia Department of Medical Assistance Services, Cardinal Care Managed Care Overview
- Virginia Medicaid, Applied Behavior Analysis Policy and Regulatory Clarifications
- Virginia Medicaid, ABA Service Authorization Update Effective October 15, 2025
- Virginia Medicaid, July 2026 ABA Policy Changes Notice
- UnitedHealthcare Community Plan of Virginia, Prior Authorization and Notification
- UnitedHealthcare Community Plan of Virginia, Cardinal Care Prior Authorization Requirements Effective July 1, 2026
- UnitedHealthcare Community Plan of Virginia, Cardinal Care Member Handbook
- American Speech-Language-Hearing Association, Augmentative and Alternative Communication
- Electronic Code of Federal Regulations, 42 CFR 438.402, Medicaid Managed Care Appeals
- Electronic Code of Federal Regulations, 42 CFR 438.420, Continuation of Benefits
Finni resources