If your business model touches remote patient monitoring or remote therapeutic monitoring, 2026 is the year the billing rules under your revenue model actually moved. CMS finalized changes in the CY 2026 Medicare Physician Fee Schedule described as one of the most consequential rulemaking cycles for remote monitoring since the original RPM codes were created. Anyone with a reimbursement thesis built on the old thresholds needs to re-underwrite it.

Why the old code structure was breaking

RPM and RTM codes were originally built around fixed thresholds: a minimum number of monitored days per 30-day period, and a minimum number of minutes of clinical staff time spent reviewing the data, to trigger billing. Technology moved past that structure years ago. Continuous monitoring devices, AI-assisted review, and asynchronous data review models did not map cleanly onto codes written for a much more manual workflow. As the 2026 code update addresses this structural limitation, the mismatch between how monitoring actually works today and how it gets billed had been building for years.

What actually changed

The AMA's CPT 2026 code set added 288 new codes across medical, surgical, and diagnostic services, with a meaningful subset touching remote monitoring and digital health workflows specifically. On the Medicare side, two billing thresholds in particular have been the focus of scrutiny: the minimum-day requirement for RPM data collection, and the minimum-minute requirement for treatment management time, both of which practices have historically left real clinical work uncompensated under.

Practical implications for a startup's billing model:

  • Threshold structures are shifting toward better reflecting partial-month and lower-intensity monitoring, which matters if your device or program serves patients who do not hit a full 16-day monitoring threshold every month.
  • Code definitions increasingly separate device supply from clinical time, which affects whether your company should bill directly, bill through a partner clinician group, or structure revenue as a technology fee to a provider organization that bills Medicare itself.
  • RTM codes, originally created for therapy and behavioral health monitoring use cases, continue to expand in scope, and startups building outside strict RPM physiologic monitoring should check whether their use case now fits an RTM code more precisely than a generic RPM code.

The build-around-billing mistake

I see two versions of this mistake constantly. The first: startups design the clinical workflow first and try to retrofit a CPT code onto it after the fact, discovering too late that their minute-count or day-count does not cleanly hit a billable threshold. The second: startups over-anchor on Medicare fee-for-service codes for a population that is actually commercially insured or in a value-based contract, where the CPT code matters far less than the underlying risk arrangement.

Before you build a reimbursement model around any CPT code:

  1. Confirm which specific payer, Medicare fee-for-service, Medicare Advantage, commercial, or Medicaid, actually reimburses that code in your target market. Coverage policy varies more than founders expect.
  2. Map your actual clinical workflow's time and data thresholds against the current code descriptors, not last year's descriptors.
  3. Decide early whether you are billing directly as a provider entity, or supplying technology to a provider who bills. This decision affects almost everything else in your go-to-market, from your BAA structure to your sales cycle.
  4. Build a compliance process for time and day documentation from day one. Audits of RPM and RTM billing have increased as the codes have expanded, and clean documentation is the difference between a defensible claim and a clawback.

Why this is a moving target, not a one-time fix

CPT and CMS fee schedule updates happen annually, and remote monitoring has been one of the most actively revised categories for several consecutive cycles. A reimbursement model is not something you build once and file away. The startups doing this well treat their billing and coding logic as a piece of the product that gets a review cycle every year alongside the annual CMS final rule, not a static assumption baked into a Series A deck from two years ago.

The takeaway

The 2026 CPT changes are not a minor coding update, they are CMS acknowledging that remote monitoring's billing structure had fallen behind the technology. If your revenue model depends on RPM or RTM reimbursement, rebuild your billing assumptions against the current code descriptors this quarter, confirm payer-specific coverage in your actual target market, and put a documentation process in place before your first audit, not after.