VA reimbursement intelligence
Virginia Medicaid & Medicare Reimbursement for RPM, CCM & TCM
Use this page as a structured planning reference for Virginia. Medicare code families provide a national baseline; Medicaid program, managed-care, provider-type, and setting rules require state and plan-level verification.
- Reviewed
- Refresh by
- Workbook
- File verified · 31.1 KB
Virginia policy summary. Virginia Medicaid continues to maintain a defined statewide remote patient monitoring pathway rather than a blanket mirror of Medicare. The January 5, 2026 Telehealth Services Supplement remains the current RPM policy baseline and requires an established provider-member relationship, service authorization and qualifying clinical criteria before billing the covered physiologic-monitoring codes 99091, 99453, 99454, 99457 and 99458. The current Virginia policy source set does not establish Medicaid payment for newer Medicare RPM codes 99445 or 99470, so those codes should not be modeled as Virginia Medicaid benefits without later DMAS authority. For 99453 and 99454, devices must automatically digitally upload physiologic data and the published pathway uses the 16-days-in-30-days monitoring threshold; providers should still verify current authorization, quantity, documentation and device requirements before claims submission. DMAS updated physician RBRVS rates effective July 1, 2026 and states that procedure-code rates should be taken from the current DMAS procedure fee files rather than a legacy workbook. The August 13 rate bulletin also notes that MCO reimbursement updates tied to FY2027 rates may require 30 to 60 days for plan system implementation and that affected claims may be automatically reprocessed, so organizations should verify date-of-service payment status before interpreting early remittances as final contracted economics. A separate August 24, 2026 DMAS bulletin adds an important authorization-timeliness control when Medicaid eligibility is granted retroactively: for services that require authorization, the provider must obtain retrospective service authorization before billing, request it within 90 calendar days of the individual's Medicaid eligibility determination date, and include it with the claim; requests outside that timeframe are denied for timeliness. Because Virginia RPM uses service authorization, organizations should build this rule into retroactive-eligibility workflows rather than assuming a newly granted coverage period automatically makes an earlier RPM claim payable. Provider enrollment remains a separate payment prerequisite: Virginia requires fee-for-service and MCO network providers, including applicable billing, servicing, ordering, referring and prescribing providers, to enroll and periodically revalidate through PRSS, and MCOs and DMAS may not pay claims to network providers who are not properly enrolled. In addition, DMAS issued a September 4, 2026 bulletin describing federally required eligibility changes: certain noncitizen, nonpregnant adult eligibility rules begin October 1, 2026, while work requirements and six-month eligibility redeterminations for Medicaid Expansion adults begin January 1, 2027. Those changes do not alter RPM procedure-code coverage, but they can affect member continuity, payer mix and realistic patient-volume projections. Before revenue modeling or billing, verify the member's current eligibility and Cardinal Care plan, active PRSS enrollment and revalidation, MCO network participation, authorization criteria, current code status, date-of-service fee schedule, documentation and any later DMAS bulletin. The legacy Virginia workbook remains planning material only when consistent with current DMAS policy and fee data.
Freshness window: recheck the official source by October 1, 2026, or sooner after a material payer change. Effective/source context: Virginia DMAS continues to use the January 5, 2026 Telehealth Services Supplement as the current RPM policy baseline, with physician RBRVS rates updated effective July 1, 2026. DMAS also requires retrospective service authorization for applicable services when Medicaid eligibility is approved retroactively: providers must obtain authorization before billing, request it within 90 calendar days of the eligibility determination date, and include it with the claim. A September 4, 2026 DMAS bulletin introduces near-term Medicaid eligibility changes beginning October 1, 2026 and January 1, 2027, which should be treated as member-eligibility and patient-volume risks rather than changes to RPM code coverage. A September 25, 2026 recheck of DMAS's H.R. 1 town-hall page confirms the September 24 health care provider session has concluded and the official provider recording is now posted. Treat October 1 implementation, any posted presentation materials, and any later FAQ or follow-up bulletin as the next verification checkpoints for the eligibility transition. Active PRSS enrollment, revalidation and MCO network participation remain separate billing-readiness controls. Primary reimbursement policy source: Virginia DMAS - Telehealth Services Supplement Update, January 5, 2026
Supporting sources checked Virginia DMAS - Resource Based Relative Value Scale (RBRVS) Rates Effective July 1, 2026 · Virginia DMAS - Retrospective Service Authorization Requests for Retroactive Eligibility, August 24, 2026 · Virginia DMAS - H.R. 1 Federal Work Requirement, Six-Month Renewals, and Medicaid Eligibility Changes, September 4, 2026 · Virginia DMAS - H.R. 1 town halls and posted health care provider recording, checked September 25, 2026 · Virginia DMAS - Noncitizen eligibility changes, member resources, presentation and FAQs for October 1, 2026 · Virginia DMAS - MCO Provider Network Resources and PRSS revalidation requirements · Virginia DMAS - Provider portal and revalidation guidance
September 25 provider-recording and eligibility checkpoint
Virginia DMAS provider town hall recording is now posted; September 24 authorization guidance is now current
Virginia DMAS's official H.R. 1 town-hall page was rechecked September 25 after the September 24 health care provider session. The provider-session recording is now linked on the page, while the page continues to state that recordings and presentation materials will be posted after each town hall. DMAS also issued a September 24 Service Authorization Appendix D update across multiple provider manuals, including Practitioner, Home Health and DMEPOS, adding the CMS Interoperability Rule mandate and MES single sign-on to Acentra Health's ANG platform. Separately, DMAS's current noncitizen information page already publishes an October 1 eligibility presentation, FAQs and recorded member-facing town hall; it states that nonpregnant adults must meet the narrower listed immigration-status categories to remain eligible for full-benefit Medicaid beginning October 1, while children and pregnant/postpartum members are not subject to this specific change and emergency-services coverage can remain available for otherwise eligible people who do not meet full-benefit immigration-status rules. This is an eligibility and renewal implementation checkpoint, not a new RPM, CCM, or TCM code-coverage rule. Until DMAS posts the provider materials or a later FAQ or bulletin, continue using the September 4 eligibility bulletin as the published implementation baseline and recheck member eligibility and payer assignment for October dates of service.
Virginia DMAS H.R. 1 town halls — provider session status checked September 25, 2026Legacy workbook check: matching VA workbook physically verified in the WordPress media library. The official policy source above has been checked; legacy workbook values still require value-level validation before operational use.
October 1, 2026 eligibility transition: verify the member on the date of service
Federal Medicaid and CHIP matching rules change for certain noncitizen eligibility categories beginning October 1, 2026. CMS instructed states to redetermine potentially affected current beneficiaries by that date. State implementation and any state-funded coverage pathways can differ, so this notice does not replace Virginia eligibility guidance. For RPM, CCM, and TCM collectibility, re-check the member's active eligibility, payer, delivery system, and managed-care assignment for the actual date of service rather than carrying a pre-transition result forward.
October 1, 2026 coding and claim-edit transition: use date-of-service rules
CMS has released FY 2027 ICD-10-CM codes for patient encounters from October 1, 2026 through September 30, 2027, plus the October 2026 HCPCS quarterly file, which CMS updated September 23, 2026. RPM, CCM, and TCM are billed with CPT/HCPCS service codes, but diagnosis coding and effective-dated HCPCS changes can affect medical-necessity edits, authorization, claim routing, risk adjustment, and claim acceptance. For dates of service on or after October 1, use the diagnosis and HCPCS sets applicable to that date and check Virginia Medicaid and the member's managed-care plan for any separate claims-system or companion-guide instructions.
CMS has also posted Medicare and Medicaid National Correct Coding Initiative updates effective October 1, 2026, with Q4 change files posted September 1, 2026 and Medicare practitioner and hospital PTP production files posted September 2. The October releases include procedure-to-procedure edits, medically unlikely edits, and Medicare add-on-code edits. Do not infer that an RPM, CCM, or TCM code became covered, noncovered, payable, or denied merely because it appears in an NCCI file; evaluate the exact code pair, units, modifier indicator, payer, provider, and date of service. CMS expressly notes that a code's presence in a Medicaid NCCI edit does not establish coverage by a state Medicaid program.
What to verify in Virginia
Build the reimbursement picture in layers
Medicare baseline
Confirm the applicable physician fee schedule, MAC/locality, clinician QP or non-QP status, code descriptors, supervision rules, device/data requirements, time thresholds, and any annual coding changes.
Virginia Medicaid program
Review the current fee schedule, provider manual, telehealth or remote-monitoring guidance, eligible provider types, places of service, and billing limitations.
Managed care
Do not assume state-level policy equals MCO payment. Verify plan contracts, prior authorization, care-management benefits, alternative payment methods, and value-based arrangements separately.
Claims lifecycle
Check timely-filing, clean-claim, corrected-claim, reconsideration, appeal, recoupment, and payer-specific denial-recovery windows before treating an otherwise covered service as collectible.
Eligibility & coordination
Verify member eligibility and plan assignment for the date of service, then confirm Medicare, commercial insurance, other third-party liability, crossover, and payer-of-last-resort rules when they apply.
Revenue model
Model payer mix, eligible patient volume, realistic utilization, staffing, device/platform expense, contract-specific reimbursement, denial leakage, and realistic collection timing only after the policy and claims assumptions are verified.
Verified Medicare baseline
CY 2026 national policy, checked
CMS finalized CY 2026 Physician Fee Schedule policy effective January 1, 2026. CMS currently describes Medicare RPM as connected-device monitoring for acute or chronic conditions, with digitally uploaded physiologic data and program-specific service requirements. CMS's current fraud-prevention guidance tells providers to furnish all three main RPM components — education/setup, device supply, and treatment management — rather than treating an isolated setup event as a complete monitoring program. The 2026 RPM code set added CPT 99445 and 99470 for lower-day and lower-time monitoring scenarios. CMS's current Medicare RPM guidance also says an ordering physician or other qualified health care provider is not required for RPM services and ordering-provider information is not required on the Medicare claim; do not carry that Medicare claim-field rule into Virginia Medicaid, an MCO, or an internal clinical protocol without confirming that payer's own ordering, referral, enrollment, and documentation requirements.
This Medicare baseline is national. It does not establish Virginia Medicaid or MCO coverage, payment, provider eligibility, or billing rules.
September 2026 CMS billing-risk signal
Apply claim-integrity checks before projecting RPM revenue
CMS's Healthcare Fraud Prevention Partnership September 2026 analysis reviewed high-risk RPM/RTM outliers from January 2025 through May 2026 and flagged patterns involving excessive frequency, initial setup without subsequent monitoring, and services billed during inpatient or skilled-nursing-facility stays. These are program-integrity risk signals, not new Virginia coverage rules. Use them as workflow controls, then apply the state and plan-specific rules above.
CMS HFPP September 2026 RPM/RTM analysis →Quarterly PFS timing safeguard
For a date of service of October 15, 2026, the applicable 2026 Medicare release is October 2026 (RVU26D / PFREV26D). Use the PFS release applicable to the actual date of service, not simply the newest file CMS has posted.
2027 Medicare policy watch · proposal only
Do not apply proposed CY 2027 RPM rules to 2026 dates of service
CMS's CY 2027 Physician Fee Schedule proposed rule would change remote-monitoring operations if finalized, including a separately reportable initiating visit when RPM or RTM begins, an established-patient requirement for RTM, and limits on payment when clinical-staff monitoring work is performed by contractors rather than staff employed by the billing practice. CMS also proposed valuation changes and sought comment on a possible future four-G-code bundled structure. The public comment period closed September 14, 2026; these provisions remain proposals unless CMS adopts them in a final rule. For current Virginia planning, keep using CY 2026 Medicare requirements plus the state and plan rules above for the actual date of service.
Code families
RPM, CCM, and TCM planning reference
These code families identify the services that should be checked against current Medicare and Virginia Medicaid rules. Inclusion here does not mean every code is payable by every payer or provider type.
Remote Patient Monitoring
99453 · 99454 · 99445 · 99457 · 99458 · 99470 · 99091
Verify device eligibility, data collection/transmission requirements, treatment-management time, interactive communication, supervision, and billing frequency. For 2026 Medicare planning, 99445 covers the 2-15-day device-supply tier and should not be reported with 99454 for the same monitoring period; verify payer-specific adoption before applying that rule to Medicaid or an MCO.
Chronic Care Management
99490 · 99439 · 99491 · 99437 · 99487 · 99489 · G0506
Verify patient eligibility, initiating-visit and comprehensive care-plan requirements, qualifying clinical staff time, complexity, add-on logic, consent, and overlapping-service rules. Medicare may allow HCPCS G0506 once with a qualifying initiating visit when the billing practitioner personally performs extensive assessment and care planning beyond the usual initiating-visit work; do not assume the same pathway applies to Medicaid or an MCO.
Transitional Care Management
99495 · 99496
Verify discharge eligibility, interactive contact timing, medical decision-making level, face-to-face visit timing, and payer-specific post-discharge requirements.
From reimbursement to implementation
Connect policy assumptions to a practical N9+ care workflow
Dr. Miltie can help organizations evaluate where remote physical examination, virtual clinician access, funding strategy, and reimbursement-supported care models fit together.