What is RPM (Remote patient monitoring)?

Remote patient monitoring (RPM), which Medicare bills as remote physiologic monitoring, uses a connected medical device to collect a patient's physiologic data, such as blood pressure, oxygen saturation, blood sugar, or weight, and transmit it automatically to a practitioner who uses it to manage an acute or chronic condition.

CMS treats RPM as one of two kinds of remote monitoring, alongside remote therapeutic monitoring (RTM). Its Medicare requirements shape how RPM software has to work:

  • The patient must have an established relationship with the billing practitioner, and must consent at the time RPM services are provided.
  • The device must meet FDA's definition of a medical device, and data must be collected electronically and uploaded automatically to a secure location for review.
  • Data must be collected for 2 to 15, or 16 or more, days in a 30-day period, depending on the code. Treatment management codes 99457 and 99458 do not have a day requirement.
  • Only one practitioner can bill remote monitoring for a patient in a 30-day period, and RPM and RTM cannot be billed together.
  • RPM can be billed alongside chronic care management and similar services as long as time is not counted twice.

CMS describes three components, each building on the one before: patient education and device setup, device supply, and treatment management, where the practitioner reviews the data to improve the patient's outcomes. Auxiliary personnel can provide the services under the billing practitioner's general supervision. Home health agencies report RPM separately on their claims with HCPCS code G0322, as one line showing the start date and the number of monitoring days.

Which CPT codes cover RPM?

Medicare pays for RPM with CPT codes 99453, 99454, 99457 and 99458, and CMS's CY 2021 rule also addressed 99091. 99453 and 99454 are the codes tied to the data-day requirement. 99457 and 99458 are the treatment management codes: they need 20 minutes of staff time, which can include care management time, and real-time interactive communication with the patient. The American Medical Association maintains CPT codes and descriptors, so read the current descriptors before writing billing rules around a code.

What must RPM software track?

RPM software has to record each billing condition as it happens, because none of them can be rebuilt reliably at month end. For each patient, that means:

  • Consent with its date, and the established relationship with the billing practitioner.
  • The device and its FDA status, with every counted reading uploaded from it automatically. Self-reported values do not count.
  • Data days: distinct calendar days with at least one valid reading, counted over a 30-day period that starts on a stored date.
  • Treatment management time by staff member and activity, with each real-time conversation with the patient recorded as its own event.
  • One named billing practitioner per 30-day period, no RTM billed for the same period, and no minutes counted toward both RPM and chronic care management.
  • From January 1, 2027, a separately reportable initiating visit linked to the start of monitoring.

Our article on RPM CPT codes and Medicare billing rules lists the checks a billing engine should run before a claim goes out. Our guide to RPM alert design covers the other hard part: turning a stream of readings into alerts clinicians act on.