RPM Billing Guide: Codes, the 16-Day Rule, and Documentation

Remote Patient Monitoring has four core CPT codes, and missing any one of their specific requirements is the most common reason RPM claims get denied or, worse, never submitted at all because a practice isn't confident they qualify.

The four codes

• 99453 — device setup and patient education, billed once per episode of care, not monthly.
• 99454 — device supply with daily recording or programmed alerts, billed per 30-day period, and requiring at least 16 days of readings within that period.
• 99457 — the first 20 minutes of monitoring and interactive communication with the patient in a calendar month.
• 99458 — each additional 20-minute increment of monitoring time in the same month.

The 16-day rule

This is the single most important operational number in RPM. To bill 99454 for a given 30-day period, the patient's device must have transmitted readings on at least 16 separate days. Fall short — even by one day — and that period isn't billable under 99454. This is why proactive adherence monitoring, not just device deployment, is the real operational job in RPM.

The interactive communication requirement

Codes 99457 and 99458 require at least one interactive communication with the patient (or caregiver) during the month — a live conversation, not just reviewing data silently. This conversation must be documented, including what was discussed and any changes made to the care plan.

Common documentation mistakes

• Billing 99454 without confirming the full 16-day transmission count for that specific period
• Missing documentation of the interactive communication required for 99457
• Billing 99453 more than once per episode of care
• Failing to document medical necessity for why RPM was ordered

How Elixir keeps this clean

Our RPM service tracks transmission compliance daily against the 16-day threshold, proactively reaches out to patients falling behind before the period closes, and documents every interactive communication in the format your billing team needs — turning RPM from a compliance risk into a reliable monthly revenue line.