Programs / RPM
Remote Phys. Monitoring

Remote Patient Monitoring

RPM Period: Rolling 30-day cycle Source: CMS-1827-F (CY 2026 PFS Final Rule); OIG OEI-02-23-00260 (Sept 2024)

What it is

Remote Patient Monitoring (RPM) is the collection and interpretation of physiologic data (e.g., blood pressure, weight, glucose, SpO₂) from an FDA-cleared connected device, with treatment management between visits.

RPM bills on a rolling 30-day cycle anchored to the device-setup date (the 99453 bill date) — not the calendar month. Each cycle is evaluated independently for the device-data and management-time codes. Willowbridge handles device pairing and reading thresholds.

Who qualifies

Codes & when to bill them

How the minutes add upEach 30-day cycle has two parts. Device supply: bill 99454 once ≥ 16 days of readings transmit (or 99445 for 2–15 days). Management time: bill 99457 at 20 minutes with one interactive call (or 99470 for 10–19 min), then 99458 for each additional 20 minutes. 99453 is billed once, at setup.

Each billable code, with the requirements that must be on file to bill it.

Documentation required every cycle

Each 30-day cycle must show:

  1. Device certification — FDA-cleared device, type, serial, 510(k) on file.
  2. ≥ 16 days of device data transmitted within the cycle (gates 99454).
  3. Interactive communication log — at least one live (phone/video) interaction with the patient/caregiver in the cycle (gates 99457/99458/99470).
  4. Device-data snapshot for the cycle (readings evidence).
  5. Patient consent with copay disclosure on file.
  6. Billing-provider sign-off.

What's new in CY 2026

CY 2026 adds a short-cycle device-supply code (99445) for 2–15 days of data, mutually exclusive with 99454, and a short-management code (99470) for 10–19 minutes of treatment management with interactive communication.

Built-in patient consentWillowbridge exclusive

Every program ships with compliant, CY-2026 patient consent language — read verbatim into the in-app consent capture flow, captured with date + modality, and version-pinned to each claim, so the consent on file always matches the consent that was billed. No more chasing signatures or re-papering when the rule changes.