ZDoggMD on Remote Patient Monitoring: What RPM Actually Delivers and When It Falls Short

This article discusses ideas from ZDoggMD — Dr. Zubin Damania, MD , Stanford/UCSF-trained internist, founder of the Health 3.0 movement. Full archive: zdoggmd.com | YouTube @zdoggmd

Remote patient monitoring — using connected devices to track blood pressure, weight, glucose, oxygen saturation, and other biometrics between clinical visits — is one of the more promising applications of digital health technology. ZDoggMD has engaged with RPM with measured enthusiasm: the technology is real, the implementation challenges are equally real.

Where RPM Works

The strongest evidence for RPM is in heart failure management: daily weight monitoring with automated alerts for early fluid retention has been shown to reduce hospitalizations in studies including the CHAMPION trial (implantable pulmonary artery pressure monitoring) and multiple home monitoring trials. Blood pressure monitoring with remote titration protocols has demonstrated better hypertension control than office-based monitoring alone in some populations. For diabetes management, continuous glucose monitoring has transformed insulin management for type 1 and select type 2 patients.

ZDoggMD's assessment of the evidence: RPM works best when it's integrated into care workflows that can actually respond to the data it generates, for conditions where the biometric being monitored is a reliable leading indicator of clinical decompensation, and for patients with the digital literacy and device access to use it consistently.

The Data Deluge Problem

The most common RPM failure mode is not technology — it's workflow. A physician practice that enrolls 200 patients in RPM without adequate clinical staffing to review the incoming data, triage alerts, and act on findings has generated a data stream that nobody is effectively monitoring. The technology works; the care delivery model didn't adapt to support it. RPM without workflow redesign produces data without action, which is not the same thing as care.

Documentation Is Its Own Data Problem

RPM generates data. Clinical encounters generate notes. Both are only useful if processed effectively. NoPajamaTime handles the note automatically so you can focus on the data that actually needs clinical attention.