Remote patient monitoring reimbursement through Medicare has never been simple. The codes have been clarified, adjusted, and augmented repeatedly since CMS first created dedicated RPM billing pathways in 2019. In 2026, the core structure is intact — but the details that determine whether you get paid, and how much, have shifted enough that practices running programs under 2023 or 2024 assumptions may be leaving money on the table, or worse, running compliance risk.

This isn't legal or billing advice. It's a working summary of what we see in practice, what documentation is frequently missing during audits, and where practices tend to make the same errors.

The Core CPT Codes

The four primary CPT codes for Medicare RPM billing remain 99453, 99454, 99457, and 99458. Each covers a distinct piece of the RPM service:

99453 covers patient education and device setup — billed once per patient at the start of a new RPM episode. The documentation requirement is straightforward: record that you educated the patient on device use and that the device was activated. Miss the documentation and the code is unbillable, even if the setup happened.

99454 covers device supply and daily monitoring — billed once per 30-day period when a medical device is supplied and data is transmitted at least 16 days out of 30. The 16-day threshold is where practices most often fall short. If a patient doesn't transmit for 14 days and then resumes, you cannot bill that month. Your platform should be surfacing this risk before the window closes, not after.

99457 covers the first 20 minutes of clinical staff time per calendar month — interactive communication with the patient is required. "Interactive" means synchronous, two-way contact. A portal message does not satisfy this requirement. A phone call does. Video does. The documentation must specify the duration and nature of the communication.

99458 covers each additional 20-minute increment beyond the first, billable up to twice per month. Most practices under-utilize this code because staff time isn't being tracked accurately during patient interactions.

The Physician Supervision Question

For 2026, CMS's position on who can bill RPM services continues to allow clinical staff acting under general supervision — meaning the billing physician does not need to be present or immediately available during the monitoring interaction. The supervising physician does need to have an established relationship with the patient and must be the billing provider.

Where practices run into problems: care coordinators documenting interactions without linking them to a supervising physician in the billing record. That gap can trigger audits and claim denials. Every 99457 and 99458 interaction needs a clear line from the staff member performing it to the physician under whose supervision the service is rendered.

State Medicaid and Commercial Payer Coverage

Medicare's RPM pathway is the most documented, but for most practices it's not the majority of their patient population. State Medicaid programs vary substantially. As of early 2026, 38 states have active RPM reimbursement policies under Medicaid, but coverage criteria, billing codes used, and documentation requirements differ widely. New York uses its own encounter-based billing structure. California's Medi-Cal has specific device eligibility criteria that exclude some consumer-grade devices.

Commercial payers are inconsistent in a different way: many have formal RPM policies that mirror Medicare on the surface, but embed clinical criteria — minimum disease severity scores, prior authorization requirements, or restricted qualifying diagnosis lists — that effectively limit coverage to a narrow subset of patients. Check each commercial payer's current policy, not their general telehealth coverage statement. The two are often different documents.

Documentation Patterns That Cause Denials

Across the practices we work with, four documentation issues account for the majority of RPM claim denials. First, missing patient consent — verbal or written consent to RPM enrollment must be documented in the medical record, and it must be specific to RPM, not just a general technology consent. Second, undocumented clinical decision-making — the monitoring data needs to connect to a clinical response. If a threshold was crossed and nothing happened, or what happened isn't documented, the service rationale is unclear. Third, timestamp ambiguities in staff time logs — if the same staff member logs 19 minutes for three different patients in overlapping windows, that's an audit flag. Fourth, failure to document the date monitoring was initiated — critical for 99453 billing and for establishing the episode start date for 99454 monthly billing.

Looking Forward

CMS has signaled interest in simplifying the RPM coding structure in upcoming rulemaking cycles, potentially consolidating some of the existing codes and adjusting valuation. Whether that improves or complicates reimbursement for individual practices will depend on the specifics. The underlying policy direction — paying for continuous monitoring as part of chronic care management — remains stable. The reimbursement math already works for many practices; the challenge is building the documentation infrastructure to capture what's owed.

If your billing team wants to walk through your current documentation workflows against the 2026 requirements, our clinical implementation team is available to do that. No charge, no commitment.