- Veteran Owned
- (800) 441-0730
This FAQ provide general questions and answers about Remote Patient Monitoring, including discussions of how it works, when it should be applied, and how it is funded by CMS.
Remote Patient Monitoring (RPM) is a Medicare-reimbursable care model that uses connected medical devices to collect patient health data outside traditional clinical settings. Providers monitor chronic conditions such as hypertension and diabetes using digital tools, improving outcomes while reducing hospitalizations and total cost of care.
RPM enables continuous monitoring of vital signs, allowing earlier clinical intervention. Studies show RPM improves blood pressure control, diabetes management, and medication adherence, leading to fewer emergency department visits and hospital admissions.
RPM is most commonly used for hypertension, diabetes, heart failure, COPD, obesity, and post-discharge monitoring. These conditions benefit from frequent monitoring and proactive care coordination.
RPM programs typically generate positive ROI through Medicare reimbursement and reduced total cost of care. Practices can generate recurring monthly revenue per patient while improving quality scores tied to value-based care incentives.
RPM supports early detection of clinical deterioration, reducing emergency department visits, hospitalizations, and complications associated with chronic conditions. This lowers overall healthcare expenditures.
Revenue varies by patient volume and payer mix. Medicare reimbursement typically includes monthly payments for device setup, data transmission, and clinical monitoring services. A good rule of thumb is that a practice can be reimbursed about $100 per patient per month.
Common CPT codes for RPM include 99453 (device setup), 99454 (device supply), 99457 (treatment management), and 99458 (additional monitoring time).
Yes. RPM can often be billed alongside CCM when services are distinct and medically necessary. Providers must ensure documentation supports each service, and the time spent on RPM and CCM must be tracked and measured separately.
RPM improves HEDIS measures such as blood pressure control and diabetes management by enabling continuous monitoring and timely clinical intervention. It helps get more readings, and helps those readings be within desired limits.
Regular monitoring and patient engagement increase adherence rates by providing reminders, feedback, and care coordination support.
Common metrics include blood pressure, blood glucose, weight, pulse oximetry, heart rate, and activity levels.
Most RPM programs can be launched within 30–60 days depending on technology integration, staffing availability, and patient enrollment processes.
RPM platforms include connected medical devices, patient engagement software, clinical dashboards, and EHR integrations.
Full-service RPM vendors typically provide devices, patient onboarding, care coordination, billing support, and analytics reporting.
Key CMS requirements include:
A typical RPM model includes:
Clinical staff may deliver RPM services under physician supervision.
Yes. Patient consent is required and must be documented (verbal or written depending on payer).
Minimum requirements include:
Patients can be enrolled through:
Documentation must include:
No. Only one provider per patient per 30-day period can bill RPM services.
Key criteria: