> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://blueprint.ziro.health/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://blueprint.ziro.health/_mcp/server.

# Patient Monitoring

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 Code | Description                         | Typical Reimbursement |
| -------- | ----------------------------------- | --------------------- |
| 99453    | RPM setup and patient education     | \$20-30 (one-time)    |
| 99454    | Device supply with daily monitoring | \$50-70/month         |
| 99457    | RPM management (first 20 min)       | \$50-60/month         |
| 99458    | Additional 20 min increments        | \$35-45 each          |

## Device Connectivity Patterns

| Connectivity    | Pros                          | Cons                                     |
| --------------- | ----------------------------- | ---------------------------------------- |
| Bluetooth LE    | Low power, direct to phone    | Requires patient phone proximity         |
| Cellular        | Always connected, independent | Higher cost, battery impact              |
| API integration | Works with existing devices   | Requires device ecosystem support        |
| Manual entry    | Universal compatibility       | High 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

***

## Related Blueprint Chapters

* [Chronic Care Playbook](/playbooks/chronic-care) — Long-term monitoring for chronic conditions
* [Cybersecurity Framework](/technical-architecture/cybersecurity) — Securing device data
* [API Design & FHIR](/technical-architecture/api-design-fhir) — Monitoring data integration