RPM CPT Codes 2026: Rates, New Codes, and Requirements

Remote patient monitoring (RPM) is billed through a small set of CPT codes covering device setup, device supply, data interpretation, and monthly treatment management. In 2026, that set grew: the CY 2026 Physician Fee Schedule final rule added two new codes, 99445 and 99470, that make shorter monitoring windows and lighter management months billable for the first time.

This cheat sheet covers every RPM code with its approximate 2026 rate, the billing requirements behind each one, what the new codes change operationally, and what a realistic month of RPM revenue looks like per patient.

2026 RPM CPT Codes and Rates

Approximate 2026 national non-facility Medicare amounts (RVU26A × non-QP conversion factor). Actual payment varies by locality, site of service, and payer; verify with the CMS Physician Fee Schedule look-up tool.

Note that 99445 reimburses at the same rate as 99454 ($47.43). CMS did not discount the short-window supply code. And 99091 carries exclusions against the RPM management codes in the same month, so it is generally an alternative pathway (physician/QHP data interpretation) rather than an add-on.

The New 2026 Codes: 99445 and 99470

Before 2026, RPM billing had hard floors: no device-supply payment under 16 transmission days, and no management payment under 20 minutes. A patient who transmitted readings on 12 days and needed one 15-minute clinical call generated real work and zero revenue. The CY 2026 final rule added a more usable low-intensity month pathway to fix exactly that.

CPT 99445: Device Supply for 2–15 Days

99445 covers device supply when a patient transmits data on 2 to 15 days within a 30-day period. Months that previously fell below the 99454 threshold (and were written off entirely) are now billable at $47.43.

CPT 99470: Management for the First 10 Minutes

99470 covers the first 10 minutes of treatment management in a calendar month and requires at least one real-time interactive communication with the patient or caregiver. It reimburses at $26.05, roughly half of 99457, for months where clinical attention was meaningful but brief.

What This Unlocks: Tiered Program Design

The practical significance is that RPM no longer has to be a single high-intensity program. Practices can now run tiered high-touch and low-touch tracks:

• Step-down monitoring. A post-discharge cardiac patient starts on daily transmissions and 99454/99457, then steps down to weekly readings on 99445/99470 as they stabilize, instead of being discharged from the program entirely.
• Mid-month starts. A patient enrolled on the 20th of the month can generate a billable partial month under 99445 rather than a free one.
• Realistic-adherence cohorts. Populations where daily transmission is never going to happen (and previously produced unbillable months more often than not) can be enrolled on a cadence that matches clinical reality.

The trade-off is tracking complexity: your workflow now has to count transmission days and clinical minutes precisely enough to select the correct tier every month, for every patient.

Billing Requirements to Get Right

• The 16-day rule vs. the short window. 99454 requires 16 or more days of transmitted data in a 30-day period; 99445 covers 2–15 days. Bill one or the other for a given 30-day period based on the actual day count. Accurate day-counting is now the difference between codes, not between payment and nothing.
• Interactive communication. 99457 requires interactive communication with the patient or caregiver as part of the 20 minutes. 99470 requires at least one real-time interactive communication. Document it; time logs alone are not enough.
• One practitioner per patient per month. Only one practitioner can bill RPM management for a given patient in a given calendar month. If a cardiologist and a primary care physician both monitor the same patient, sort out who bills before claims go out.
• 99453 is once per episode. Setup and education bills once at the start of an episode of care, not monthly.
• 99091 exclusions. The physician/QHP data-interpretation code has exclusions against the RPM management codes in the same month. Choose the pathway that fits how your clinicians actually engage with the data.

What RPM Pays Per Patient Per Month

Using the approximate 2026 rates above:

• Standard month: 99454 ($47.43) + 99457 ($51.77) = $99.20 per patient
• Engaged month: add one 99458: $99.20 + $41.42 = $140.62
• Low-touch month: 99445 ($47.43) + 99470 ($26.05) = $73.48
• First month: add one-time 99453 to a standard month: $21.71 + $99.20 = $120.91

At the standard-month rate, a patient who qualifies all twelve months generates $99.20 × 12 = $1,190.40 per year, before any 99458 add-ons, and with low-touch months now contributing $73.48 instead of $0. To see what this looks like across your panel size and payer mix, model your panel with our ROI calculator.

Running RPM Under the 2026 Structure

The 2026 codes reward programs that can do three things reliably: count transmission days per 30-day period, log clinical minutes against the right thresholds, and document interactive communication, then map all of it to the correct code tier each month.

CareTrack's remote patient monitoring program handles that end to end: device logistics, patient outreach, day and minute tracking, and code selection across both the standard and short-window tiers. Because CareTrack integrates with athenahealth, Epic, and Greenway, documentation and billing data land in the EHR your practice already uses. RPM patients are also frequently candidates for chronic care management, and running the programs together compounds both the clinical picture and the per-patient revenue.

Ready to see what the 2026 RPM codes are worth across your patient panel? Book a demo.