To configure Virginia Medicaid ABA telehealth and MCO controls, preserve the in-person initial assessment and build telemedicine into the authorized individual service plan. Verify clinical appropriateness, the in-person fallback, provider authority, family participation readiness, MCO or fee-for-service route, authorization, documentation, and billing. Virginia's December 2025 clarification makes these telemedicine details part of ABA compliance.

Define a Virginia telehealth release

Petronilla treats telehealth as a service-date configuration. One row identifies the member, program or plan, service, billing and rendering providers, supervisor when applicable, member and practitioner locations, modality, authorization, clinical decision, access supports, platform, note, claim rule, and emergency plan. The row receives a new version when any controlling fact changes.

Read the current Virginia Medicaid ABA authority

Virginia Medicaid's December 2025 ABA clarification says initial ABA assessments must occur in person. When ABA uses telemedicine, the ISP must state when remote and in-person services will occur, provide clinical evidence for the amount, duration, and scope, and explain how in-person needs will be met. It also requires evidence that the youth and parent or caregiver can participate meaningfully and safely.

Separate program coverage from payer routing

The current Telehealth Services Supplement supplies general delivery and billing requirements. Petronilla also checks the 2026 memo index and provider library for superseding material. Acentra or the responsible Cardinal Care MCO remains a separate authorization and claim route; one receiver's response does not control another.

Use one release gate for every required fact

Petronilla requires current member payer route; in-person initial assessment; current ISP with telemedicine schedule, clinical rationale and in-person fallback; provider license, delegation and payer status; both locations; modality; family participation readiness; choice; consent and assent when applicable; authorization; access; note; claim setup; and emergency plan. A failed gate holds the session or claim at the affected point. The register shows the source, owner, checked time, effective period, exception path, and next action. Clinical, legal, payer, technical, and claim facts retain separate owners and evidence.

Keep clinical decisions with qualified clinicians

Petronilla routes case-specific modality, risk, treatment, supervision, and clinical-fit decisions to an appropriately qualified clinician. Operations verifies evidence, coordinates scheduling, and surfaces conflicts. Software can check fields and deadlines. A payer coverage action remains separate from the treating clinician's recommendation.

Verify location at every encounter

The member and practitioner locations can change between sessions. Petronilla asks for the member's physical location at check-in and records the practitioner's physical location from the responsible professional. Those facts drive licensure, payer, emergency, privacy, and place-of-service analysis. Profiles and prior visits serve as reference data rather than the current encounter record.

Preserve choice, consent, assent, and communication

Petronilla gives the person an understandable modality choice when the governing source allows it and records required consent from the legally authorized person. Assent is monitored when applicable. Speech, AAC, sign, gesture, writing, interpreters, captions, and other effective forms remain available. The person has an accessible way to request a pause or another supported setting.

Decide whether the session can work remotely

A qualified clinician reviews the purpose, response forms, observation needs, prompting, caregiver role, safety, privacy, environment, technology, fatigue, and alternatives. Petronilla identifies which components need direct observation or in-person care and when to switch. Staffing pressure, distance, or payer approval supplies no clinical-fit conclusion.

Build technical and emergency readiness

Petronilla tests the approved platform, audio, video when required, device power, bandwidth, camera view, communication system, backup contact, privacy, and outage route. The record names the person's physical location, local emergency contact, responsible adult when applicable, nearest response route, and stop condition. Staff pause when a connection failure prevents safe or meaningful care.

Match authorization and documentation

Petronilla compares the authorized service, provider, setting, modality, dates, units, and stated conditions with the planned encounter. The note records actual locations, modality, start and stop time when required, participants, accessible communication, interventions, responses, interruptions, supervision, and clinically relevant outcome. The record describes the delivered session.

Release the claim from completed evidence

Petronilla derives code, units, modifier, place of service, rendering and billing identities, location, authorization reference, and payer route from verified records and current instructions. A telehealth flag supplies one field, while the completed source record supplies the claim evidence. Claim acceptance, adjudication, remittance, and payment remain later states.

Work through Petronilla's fictional cohort

Petronilla locks 21 fictional Richmond sessions across fee-for-service and two MCO routes. Thirteen initially include the in-person assessment, complete ISP telemedicine evidence, provider authority, both locations, participant readiness, authorization, access, note, claim route, and emergency plan. One initial assessment is remote, two ISPs lack an in-person fallback, one uses another MCO's approval, one note omits participant readiness, and three lack detailed telemedicine justification. Six repair. Two remain held. The example is synthetic. It tests release and denominator logic and establishes no coverage, authorization, clinical, legal, privacy, licensure, claim, or payment conclusion for a real person or practice.

Calculate Petronilla's measures

Virginia ABA telemedicine readiness is 13 of 21, or 61.9%. Nineteen sessions reach release or accountable hold, or 19 of 21, or 90.5%. Report holds by coverage, authority, location, choice, consent, assent, access, clinical fit, technology, authorization, documentation, claim, and emergency reason. Preserve counts beside percentages and age every unresolved item from its defined start event. Every failed or pending item remains visible in its declared cohort.

Address the main Virginia failure mode

The central risk is treating a video-capable service as an authorized telemedicine plan. Petronilla requires the clinical schedule, amount, duration, scope, fallback, participation readiness, payer route, and service authorization before scheduling. Annual assessment review and every ISP revision receive their own due date and qualified owner.

Test Petronilla's controls

Petronilla tests in-person initial assessment, telemedicine reassessment, incomplete ISP, missing fallback, fee-for-service, two MCOs, provider delegation, failed video, inaccessible communication, and missing location. Each scenario records the starting facts, expected action, source, observed result, owner, correction, retest, and disposition. A successful connection proves technical access for that test. Coverage, clinical fit, authorization, documentation, and payment need their own acceptance evidence.

Run independent acceptance

Petronilla gives an independent reviewer the locked cohort, sources, locations, provider records, authorizations, clinical decisions, access plans, consent and assent evidence, platform results, notes, claims, and payer responses. The reviewer reproduces one release and one hold. A changed cohort, hidden failure, unsupported rule, or unexplained calculation fails acceptance.

Maintain the Virginia Medicaid ABA telemedicine ISP and payer register

Petronilla reviews sources monthly and after program, plan, law, rule, manual, code, modifier, place-of-service, form, platform, authorization, contract, or contact changes. Each source keeps an owner, effective and checked dates, scope, supersession state, and next review. This Virginia page remains draft and noindex until every named expert review finishes.

Related resources

Sources