Domain Playbooks

Patient Monitoring

Designing remote monitoring for better health outcomes
View as Markdown

Remote Patient Monitoring (RPM) is one of the fastest-growing segments in digital health. Effective monitoring requires thoughtful design across patient devices, clinician dashboards, and data pipelines.

RPM Reimbursement

RPM has established CPT codes that make it one of the most viable digital health business models:

CPT CodeDescriptionTypical Reimbursement
99453RPM setup and patient education$20-30 (one-time)
99454Device supply with daily monitoring$50-70/month
99457RPM management (first 20 min)$50-60/month
99458Additional 20 min increments$35-45 each

Device Connectivity Patterns

ConnectivityProsCons
Bluetooth LELow power, direct to phoneRequires patient phone proximity
CellularAlways connected, independentHigher cost, battery impact
API integrationWorks with existing devicesRequires device ecosystem support
Manual entryUniversal compatibilityHigh patient burden, data quality issues

Alert Design — Avoiding Alarm Fatigue

Alert design is critical for clinical adoption:

  • Tiered alerts: Urgent (red) vs. non-urgent (yellow) vs. informational (blue)
  • Context-aware: Consider patient history, not just single readings
  • Actionable: Every alert should have a clear recommended action
  • Escalation path: Define what happens if alerts are not acknowledged
  • Quiet hours: Respect patient and clinician sleep schedules

Clinician Dashboard UX

Clinicians need to assess patient status at a glance:

  • Patient list: Sortable by urgency, last reading, days since last contact
  • Patient detail: Trend view, recent readings, alerts, care plan adherence
  • Bulk actions: Message multiple patients, batch alert acknowledgment
  • Population view: Aggregate metrics for panel management