A well-run Remote Patient Monitoring (RPM) program only pays for itself if the billing behind it is done correctly. Most practices that struggle to make RPM financially viable are not failing on the clinical side — they are failing on the remote patient monitoring CPT codes side, where a missed monitoring day or an undocumented minute of staff time can turn a billable month into an unbillable one. This guide breaks down the current CPT code set, including two lower-threshold codes added for 2026, and where reimbursement most commonly slips through the cracks.
The Core RPM CPT Codes and What Each One Requires
Medicare’s RPM billing structure is built around a small set of CPT codes, each tied to a specific activity and a specific threshold. Getting the threshold wrong is the single most common reason a claim is denied or a service goes unbilled entirely.
- CPT 99453 covers the initial patient set-up and education on how to use the monitoring device. It is billed once per episode of care and requires the patient to record at least 16 days of data within a 30-day period before it can be submitted.
- CPT 99454 covers the device supply and the data transmission itself, and is billed monthly. It requires 16 to 30 days of transmitted readings within a 30-day period.
- CPT 99457 covers the first 20 minutes of clinical staff time spent on treatment management — reviewing data, adjusting care, and communicating with the patient — in a calendar month. It requires at least one real-time, synchronous interaction with the patient or caregiver during that month.
- CPT 99458 is an add-on code to 99457, billed for each additional 20-minute increment of treatment management time. There is no cap on how many increments can be billed in a month, provided the time is documented.
- CPT 99091 covers the collection and interpretation of physiologic data — readings like blood pressure, glucose, or ECG — by a physician or qualified healthcare professional, and requires a minimum of 30 minutes of dedicated time. It can be billed once every 30 days.
What’s New for 2026: Two Codes That Lower the Bar
CMS expanded the RPM code set for 2026 specifically to capture partial-month monitoring that previously went unbilled. Two new codes fill gaps that existed under the older 16-day and 20-minute thresholds:
- A new device/transmission code now covers 2 to 15 days of data transmission within a 30-day period — below the 16-day floor that CPT 99454 requires. Practices whose patients transmit inconsistently, or who are mid-onboarding partway through a month, now have a billable pathway instead of forfeiting the month entirely.
- A new treatment-management code covers 10 to 19 minutes of clinical monitoring time in a calendar month — below the 20-minute floor that CPT 99457 requires. This captures shorter but still clinically meaningful check-ins that previously fell into a documentation gap between "billable" and "not worth logging."
Both additions matter more for revenue capture than for clinical practice: they don’t change what care looks like, they change how much of that care a practice can actually get paid for.
RPM CPT Codes at a Glance
| CPT Code | What It Covers | Threshold to Bill | Billing Frequency |
|---|---|---|---|
| 99453 | Initial set-up & patient education | 16+ days of data in 30 days | Once per episode |
| 99454 | Device supply & data transmission | 16–30 days of data in 30 days | Monthly |
| New 2026 code | Device supply & data transmission (lower threshold) | 2–15 days of data in 30 days | Monthly |
| 99457 | First 20 min of treatment management | 1+ real-time interaction/month | Monthly |
| 99458 | Each additional 20-min increment | Add-on to 99457, uncapped | Monthly |
| New 2026 code | Treatment management (lower threshold) | 10–19 minutes/month | Monthly |
| 99091 | Physiologic data collection & interpretation | 30+ minutes | Every 30 days |
Where RPM Billing Breaks Down in Practice
Three failure points account for most of the reimbursement a practice leaves on the table:
- Eligibility mismatch. RPM billing under these codes applies to patients covered by Medicare Part B with an acute or chronic condition — billing a patient outside that scope, or without the underlying condition documented, invites a denial regardless of how clean the monitoring data looks.
- Device compliance gaps. The device itself must be FDA-cleared and must transmit data digitally rather than rely on manual patient entry. A practice using a non-cleared consumer device, however accurate, has no billable claim under these codes.
- Undocumented time. CPT 99457, 99458, and the new sub-20-minute code all hinge on time actually logged by clinical staff. Programs that monitor diligently but don’t timestamp the review-and-communication work lose the treatment-management codes even when the underlying care happened.
Staffing, Supervision, and Where a Vendor Fits
A physician or other provider with an NPI must direct the RPM program, but the day-to-day monitoring can be performed by clinical staff under general supervision — which is exactly why most practices don’t run RPM billing entirely in-house. The combination of device provisioning, daily data monitoring, time-logging discipline, and CPT-specific claim submission is closer to a revenue-cycle function than a clinical one, and it’s the reason RPM program vendors and medical billing specialists so often get bundled into the same conversation. A practice evaluating an RPM setup should ask any prospective vendor how they handle the threshold logic above by default — specifically whether their platform automatically routes a patient’s month to the correct code (including the new lower-threshold options) rather than defaulting to a single fixed code regardless of actual data volume.
Getting the Match Right
The 2026 code changes make RPM more forgiving of real-world monitoring gaps, but they also add complexity: a practice now needs its device platform, its staffing model, and its billing workflow to correctly classify every patient-month across seven possible codes instead of five. That’s a due-diligence question worth asking before signing with any RPM or RCM vendor, not after the first denied claim. Matching the clinical workflow to a vendor that already handles this threshold logic — rather than retrofitting it after go-live — is usually the difference between an RPM program that pays for itself and one that quietly under-bills every month.