Remote Patient Monitoring (RPM): The Complete Guide
Remote patient monitoring (RPM) lets a care team track a patient's physiologic data — glucose, blood pressure, weight, oxygen saturation, and more — between visits, using a connected device that transmits readings automatically. It is reimbursable under Medicare and many commercial payers, and it is one of the fastest-growing ways primary care and specialty practices close the gap between appointments. This guide is the hub for everything else on the site about RPM: what it is, who qualifies, how it is billed, what devices are used, and how a practice actually runs it.
What RPM is, in plain terms
A patient uses a device at home — a continuous glucose monitor, a connected blood pressure cuff, a pulse oximeter, a cellular scale — and the readings flow to the clinical team automatically, without the patient having to call in or transcribe anything. The care team reviews the data, reaches out when something looks off, and documents the time spent managing it. Medicare created specific CPT codes for exactly this workflow, which is what makes it billable rather than just a nice-to-have.
Who RPM is for
RPM is not disease-specific. It is used most often for chronic conditions where day-to-day trends matter more than a single office reading: diabetes and dysglycemia (via CGM), hypertension, heart failure, COPD, obesity, and chronic kidney disease among them. The common thread is a condition that fluctuates between visits and where earlier detection of a trend — not just a single bad number — changes what the clinician does next.
What's in this guide
- What is RPM?The plain-English definition, how the data flows, and how it differs from telehealth.
- RPM vs. CCM vs. RTMHow the three remote-care code families compare and when each applies.
- Which conditions qualifyThe chronic conditions RPM is most commonly used for, and why.
- RPM devices explainedCGMs, BP cuffs, pulse oximeters, scales — what qualifies and how data reaches the clinic.
- Patient consent & enrollmentWhat consent RPM requires, and how to document it correctly.
- RPM workflow in primary careHow a practice actually runs RPM day to day, step by step.
- Medicare RPM coverage in 2026Current CMS rules, the Physician Fee Schedule, and what changed.
- RPM vs. in-person visitsWhat RPM adds between appointments, and what it doesn't replace.
- RPM for chronic disease managementHow RPM fits into a broader population health strategy.
- Billing CGM as RPMThe four core CPT codes — 99453, 99454, 99457, 99458 — explained.
The core RPM CPT codes, at a glance
| Code | What it covers |
|---|---|
| 99453 | Initial set-up and patient education on the device. |
| 99454 | Device supply with daily recordings transmitted to the practice (needs ≥16 days of data per 30-day period). |
| 99457 | The first 20 minutes of interactive monitoring/treatment-management time per month. |
| 99458 | Each additional 20 minutes, as an add-on to 99457. |
The full breakdown — requirements, common mistakes, and how RPM relates to chronic care management (CCM) and remote therapeutic monitoring (RTM) — is in Billing CGM as RPM and RPM vs. CCM vs. RTM.
Where the friction usually is
The clinical case for RPM is well established, but the administrative load is real: enrolling patients, capturing device-days, reviewing trends, documenting interactive time, and mapping all of it to the correct code each month. That overhead is the reason many practices that qualify for RPM reimbursement never bill for it consistently. Automated decision support is built to close exactly that gap — it watches the data continuously, flags who needs attention, and charts the monitoring and time as it happens.
See what your panel qualifies for
Endobits auto-triages your monitored population and charts RPM time against the codes you already qualify for.
For clinical GPsRelated: Continuous glucose monitoring · CGM for type 2 diabetes in primary care · All resources