Remote patient monitoring (RPM) technology can track blood pressure, blood sugar, weight, and oxygen levels from home, yet most doctors still aren't using it as part of standard care. The gap between what RPM can do and how it actually gets used in clinics reveals a fundamental problem: the technology works, but the systems around it don't.

RPM involves connected devices like blood pressure cuffs, weight scales, pulse oximeters, and glucose monitors that send readings to a clinical dashboard where care teams can spot concerning trends and alert patients before problems escalate. The Centers for Medicare and Medicaid Services (CMS) recognizes RPM under billing codes like 99453, 99454, 99457, 99458, and 99091, meaning insurers will reimburse practices for monitoring patients remotely.

So why isn't every primary care office using it? The answer isn't that the devices don't work. It's that RPM fails when it becomes a separate silo disconnected from how doctors actually practice medicine.

What Makes Remote Monitoring Fail in Real Clinics?

When RPM programs collapse, it's rarely because the blood pressure cuff malfunctions. Instead, the breakdown happens in the workflow. A practice enrolls patients, devices ship out, readings arrive, but then nobody knows who's supposed to review them, who calls the patient about abnormal trends, where the clinical time gets documented, or how the practice proves it deserves reimbursement.

Drew Schiller, CEO and co-founder of Validic, a health data integration company, has warned that RPM programs fail when data lives in a separate point-solution dashboard. His argument is straightforward: programs scale better when remote data becomes part of the clinical workflow, not an extra task layered on top of it.

The American Medical Association's RPM implementation playbook reinforces this insight, noting that teams need to understand the workflow from "the perspective of the patient, providers and caregivers" before improving it. Without that perspective, RPM becomes another data stream that overwhelms busy clinicians instead of helping them.

How to Build an RPM Program That Actually Works?

• Integrate with existing EHR systems: Remote monitoring data must flow directly into the electronic health record (EHR) that doctors already use daily, not into a separate dashboard that requires switching between screens.
• Define clear escalation rules: Establish who reviews readings, what triggers an alert, who contacts the patient, and how that interaction gets documented for billing and quality tracking.
• Connect RPM to broader care management: RPM works best when it's part of a larger care management strategy that includes chronic care management (CCM), transitional care management (TCM), and other reimbursable services under one platform.
• Simplify device logistics: Reduce the burden on patients and staff by handling device shipping, setup support, and troubleshooting centrally rather than asking practices to manage it themselves.
• Align billing with documentation: Ensure the platform automatically tracks the time and data collection required to meet CMS billing requirements, so practices don't have to manually prove they deserve reimbursement.

Which Patients Benefit Most From Remote Monitoring?

RPM works across multiple chronic conditions. Practices have successfully deployed remote monitoring for patients with hypertension, diabetes, congestive heart failure (CHF), chronic obstructive pulmonary disease (COPD), obesity, and those recovering from hospitalization. The key is matching the right RPM platform to the practice's specific needs and patient population.

For example, cardiac device companies like Medtronic have deep expertise in monitoring patients with implanted pacemakers and defibrillators, while other platforms excel at managing primary care populations with multiple chronic conditions. Senior-focused practices with low-tech patient populations may prioritize simplicity over customization, whereas large health systems need enterprise-grade infrastructure and EHR integration.

The real barrier to RPM adoption isn't clinical evidence or reimbursement codes. It's the operational complexity of fitting remote monitoring into the daily rhythm of a busy clinic. Practices that succeed are those that treat RPM not as a standalone device program but as a core part of how they deliver and document care.

"RPM programs fail when data lives in a separate point-solution dashboard. Programs scale better when remote data becomes part of the clinical workflow," noted Drew Schiller, CEO and co-founder of Validic.

Drew Schiller, CEO and co-founder of Validic

As healthcare continues to shift toward value-based care and remote monitoring becomes more common, the practices that thrive will be those that integrate RPM deeply into their operations, not those that bolt it on as an afterthought.