Remote patient monitoring (RPM) uses connected devices to collect a patient’s health data between visits, then routes it to the care team so they can act before a small problem becomes a big one.
What data does RPM collect?
Common signals include blood pressure, blood glucose (including continuous glucose monitors), weight, pulse oximetry (SpO₂), heart rate and HRV, and activity. The best programs let patients use devices they already own rather than locking them into one vendor’s hardware.
Which conditions is it used for?
RPM is widely used for hypertension, diabetes and pre-diabetes, heart failure, weight management and GLP-1 programs, metabolic health and post-discharge care, anywhere between-visit data changes decisions.
How does RPM billing work?
In the US, Medicare reimburses RPM through specific CPT codes: 99453 (setup), 99454 (device supply with 16+ days of data), 99457 (first 20 minutes of management) and 99458 (each additional 20 minutes), with RTM codes 98975–98981 for therapeutic monitoring. Codes and payer rules change, so always verify the current set. This is not billing advice.
What to look for in RPM software
Device breadth (100+ integrations), longitudinal trends rather than point readings, thresholds and alerts, time-tracking to support billing, and ideally an AI copilot that surfaces what matters. See how Heads Up approaches it at /remote-patient-monitoring.
See how clinics use Heads Up
Unify labs, wearables and EHR data into one AI-assisted view. Book a walkthrough tailored to your practice.
