RPM Billing in 2026: What Practices Actually Get Paid For

Remote patient monitoring has moved from pilot project to standard line item for primary care, cardiology and endocrinology. The billing rules, however, have not become friendlier. Most denials we see are not clinical — they are structural. A device was shipped without consent, a month had fourteen days of readings instead of sixteen, or the time log lived in a spreadsheet nobody could audit.

The four codes, in order

RPM reimbursement is built from four CPT codes, and each one needs its own evidence trail.

• 99453 — setup and patient education. Billed once per episode of care, when the device is set up and the patient is taught how to use it. This is a one-time code; billing it again for the same patient requires a new episode and a documented reason.
• 99454 — device supply and data transmission. Billed once per 30-day period, and it requires at least 16 days of readings in that period. This is the single most common failure point.
• 99457 — treatment management, first 20 minutes. Clinical staff time spent reviewing data, adjusting the care plan and communicating with the patient.
• 99458 — each additional 20 minutes. Added time in the same calendar month, when the work is documented.

> The 16-day rule is not a suggestion. If a patient transmits on fifteen days, 99454 is not billable for that month — even if the clinical work was excellent.

Consent is a billing document

Before the first device ships, the patient needs to consent to remote monitoring, in writing, with a signature and a date. That consent is part of the medical record. When a payer requests documentation, an unsigned consent form is treated the same as no consent at all.

Practices that get this right usually standardize on a single intake packet: consent, device assignment, education checklist and the first transmission date, all captured in one place.

Time is the other ledger

99457 and 99458 are time-based. The minutes must come from clinical staff — not from an automated dashboard, and not from the patient's own logging. A care manager reviewing alerts, calling the patient about a rising blood pressure trend and updating the plan is exactly the work these codes describe.

Two habits keep this clean:

1. Log time at the moment it happens, not at the end of the month.
2. Keep the note specific. "Reviewed RPM data, called patient re: weight gain, plan updated" beats "RPM management" every time.

Where programs usually leak revenue

In our reviews of practice programs, three patterns account for most lost revenue: patients who never activate their device, months that fall one or two days short of the transmission threshold, and follow-up calls that happen but are never documented.

Each of these is an operations problem, not a billing problem. A weekly activation report, a transmission dashboard that flags patients at day 20 with fewer than 12 days of data, and a one-screen time log solve most of it.

If you want a second set of eyes on your current setup, our team can map your workflow against the codes you are already using.