CMS 2026 Medicare Rule Cracks Open RPM With Shorter Codes

What happened

According to Circle Care's breakdown of the CMS 2026 Medicare proposed rule, CMS is removing frequency limits on Remote Physiologic Monitoring and adding shorter-duration codes covering 10 to 20 minute service periods and 2 to 15 day data collection windows, effective January 1, 2026. In parallel, Congress extended audio-only telehealth coverage through 2027, keeping a lifeline that expanded significantly during the pandemic.

Why it matters for hospital/HealthTech buyers

The practical effect is that RPM and RTM finally look like real, flexible tools instead of narrowly scoped billing categories. Shorter-duration codes let providers bill for the kind of lightweight, high-frequency touches that actually match how chronic care happens between visits: a quick blood pressure check-in, a medication adherence nudge, an early symptom review.

For HealthTech vendors, this reshapes the market for connected devices, patient engagement platforms, and virtual care software. Programs that were unprofitable under the old code structure become viable, and hospitals that had shelved RPM pilots because the reimbursement math did not work now have a reason to revisit them.

"CMS proposed to expand coverage for RPM and RTM codes, with the addition of shorter-duration monitoring options recognizing how providers are delivering care between visits." — Circle Care

Our take

CMS effectively admitted that clinical work has moved off the exam-room clock, and the code set is catching up. That is a big deal. It also raises the operational bar. Once you can bill for a ten-minute touchpoint, your entire workflow, staffing model, and documentation stack has to be built for volume, not for exceptions. Hospital operations leaders should be redesigning their RPM programs around the new code granularity now, not next year, because the organizations that instrument these workflows first will convert the reimbursement into margin instead of overhead. And vendors selling into that stack should be leading their pitches with the new code map, not with generic feature lists.