Virginia Medicaid PRSS Manage Revalidation Panel: 2026

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Confirm access at the right account level

The panel is useful only when the user has the authorized role for the Provider Account Holder and the relevant locations are attached correctly. Inventory the base ID, location IDs, legal entity, NPIs, provider types, Authorized Administrator, backup user, and password-recovery route. A local spreadsheet can note who should appear, but PRSS and the provider notice remain the operational evidence. Resolve missing or duplicate locations before a deadline approaches.

Reconcile notices to application tracking numbers

Virginia sends an initial notice about 90 days before the revalidation date and reminders at 60 and 30 days through the recorded email and mail channels. Link each notice to the correct ATN and location in the panel. Save received date, due date, application status, deficiency, response, and final decision. A Resume or Revalidate link indicates a workflow action; it does not establish that the application has been submitted or approved.

Treat due date and any grace description carefully

The main DMAS page warns that failure to revalidate by the due date leads to termination from fee-for-service and managed care until successful re-enrollment or revalidation. The Virginia provider FAQ also describes a possible period after a compliance date. Do not promise a grace period from generalized FAQ language. Preserve the provider's notice and live PRSS state, and obtain written DMAS direction when the dates appear inconsistent.

Keep managed-care credentialing separate

Virginia requires applicable managed-care network providers to enroll with the state, while plan contracting, credentialing, roster acceptance, effective date, and authorization remain distinct. Use the DMAS managed-care provider page to map the state requirement, then verify every MCO configuration separately. An active plan roster cannot cure a terminated state record, and a successful PRSS revalidation cannot prove a plan location is active.

Build a base-ID location register

For each location, record service address, billing and rendering roles, NPI and taxonomy, provider type, licenses, ownership and control disclosures, exclusions, contact channels, notice dates, ATN, panel state, due date, state decision, MCO rosters, claim holds, and continuity owner. Avoid one practice-wide completed flag. A base ID may show several locations at different points in the process.

A fictional Virginia panel reconciliation

Aaliyah locks 40 PRSS location records. Thirty-one are matched to an ATN or documented no-notice state and have a current administrator, due date, evidence owner, MCO cross-check, contingency owner, and recheck date. Reconciliation completeness is 31 of 40, or 77.5%. Four locations lack an ATN match, three have stale contact information, and two show a panel state that conflicts with saved notices. All nine remain assigned.

Use panel metrics with explicit units

Report location reconciliation as locations with a verified notice and ATN state divided by all active locations in the locked base-ID inventory. Report timely submission as matured due locations submitted by their notice date divided by locations whose due date matured. Show no-notice, deficient, terminated, re-enrolled, and MCO-pending states separately. Counting ATNs alone can overstate coverage because one location can have more than one transaction.

Virginia control checklist

Verify the current DMAS page and federal baseline, Provider Account Holder, base ID, location, administrator, NPI and taxonomy, notice channels, 90-, 60-, and 30-day notices, due date, ATN, Resume or Revalidate action, submission receipt, deficiency, final state, MCO contract and roster, authorization, claim hold, continuity response, appeal route, and next source check. Preserve screenshots with timestamps when the panel changes.

Questions for conflicting states

Ask which location the notice covers, whether the ATN represents revalidation or another transaction, which date DMAS will enforce, what evidence shows submission, how termination affects active claims and authorizations, and which MCOs must be notified. Route clinical continuity to qualified clinicians and administrative coverage questions to the plan and DMAS. Avoid describing a pending application as active enrollment.

Related resources

• Minnesota EIDBI Provider Revalidation Results and Appeals: 2026.
• Washington Apple Health Two-Year Provider Revalidation Initiative: 2026.
• New Jersey Medicaid Two-Year High-Risk Provider Revalidation Strategy: 2026.
• MassHealth Two-Year Off-Cycle Provider Revalidation Strategy: 2026.

Sources

• Virginia Department of Medical Assistance Services, Provider Enrollment and Revalidation.
• Virginia Department of Medical Assistance Services, Managed Care Network Providers.
• Virginia Medicaid, Provider Enrollment Frequently Asked Questions.
• Electronic Code of Federal Regulations, 42 CFR 455.414.