Definition

Remote Patient Monitoring (RPM)

Remote patient monitoring (RPM) is the collection of physiologic data, such as blood pressure, weight, blood glucose or oxygen saturation, from patients outside a clinical setting using connected devices, with data sent to clinicians who review it and manage care.

2 min readReviewed September 14, 2026

Also known as: Remote physiologic monitoring, RPM services, Remote monitoring

Key facts

Medicare billing codes
CPT 99453, 99454, 99457, 99458 and 99091
Device requirement
Must meet the FDA definition of a medical device
Data type
Physiologic data, collected and transmitted digitally
Related service
Remote therapeutic monitoring (RTM) for non-physiologic data
Medicare telehealth rules
RPM is not subject to Section 1834(m) telehealth limits

What is remote patient monitoring?

RPM lets a care team track a patient's condition between visits. The patient uses a device at home, such as a connected blood pressure cuff, scale, glucose meter or pulse oximeter, and readings flow automatically to the clinician's system. Staff review the data, contact the patient and adjust the care plan when readings change.

RPM is commonly used for chronic conditions such as hypertension, diabetes and heart failure, and after hospital discharge. It differs from a telehealth visit because the core service is ongoing data collection and management rather than a real-time encounter.

How Medicare pays for RPM

Medicare pays for RPM under the Physician Fee Schedule through several CPT codes:

  • 99453: initial device setup and patient education.
  • 99454: device supply with daily recordings or programmed alerts, billed per 30 days and requiring at least 16 days of data.
  • 99457 and 99458: treatment management services for the first 20 minutes and each additional 20 minutes in a calendar month, including interactive communication with the patient.
  • 99091: collection and interpretation of physiologic data by a physician or other qualified professional, requiring at least 30 minutes.
  • Conditions: the patient must consent, the device must meet the FDA medical device definition, and data must be collected automatically rather than self-reported.

Why remote patient monitoring matters

RPM has grown into a significant Medicare service line:

  • Provider strategy: RPM billing creates recurring monthly revenue for practices managing chronic disease populations.
  • Program integrity: the HHS Office of Inspector General (OIG) has reported rapid growth in Medicare RPM billing and called for more oversight, so compliance teams audit documentation closely.
  • Device and digital health companies: FDA device status and Medicare code requirements determine whether a product can support billable RPM.
  • Analytics: Medicare claims and utilization data for RPM codes show which practices and specialties have adopted remote monitoring.

RPM vs remote therapeutic monitoring

Remote therapeutic monitoring (RTM) uses a separate set of CPT codes for non-physiologic data, such as therapy adherence, therapy response and musculoskeletal or respiratory status, and it can include some self-reported data. RPM covers physiologic measurements only.

CMS revises both code families in its annual Physician Fee Schedule rules, so billing requirements should be checked for each year.

Sources

All glossary terms