RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →Here is a complete breakdown of the new rules, billing logic, and documentation requirements.
Manually tracking 2-15 days vs. 16-30 days and 10-19 min vs. 20+ min is a nightmare for billing staff and a high risk for denials. FairPath's "Compliance-as-Code" engine automates it all.
Effective for services on or after January 1, 2026, Medicare finalized two key additions to the Remote Physiologic Monitoring (RPM) family:
device(s) supply with daily recordings/programmed alerts when 2–15 days of data are captured in a 30-day period. The existing 99454 now explicitly covers 16–30 days. You report one or the other per 30 days (not both).first 10–19 minutes of RPM treatment management time in a calendar month (requires at least one real-time interactive communication). If you reach 20 minutes, you report 99457 instead. 99470 is not additive with 99457 in the same month.Here is how the new codes fit in with the existing ones.
Initial set-up and patient education (once per episode of care).
Device supply & transmission for 2–15 days in a 30-day period.
Device supply & transmission for 16–30 days in a 30-day period.
First 10–19 minutes of RPM management in a month (requires 1+ interactive communication).
First 20 minutes of RPM management in a month (requires 1+ interactive communication).
Each additional 20 minutes (add-on to 99457).
99445 (2-15 days) and 99454 (16-30 days) at the same national rate. This is due to CMS using OPPS hospital data to set rates, not just vendor-submitted costs. 99470 (10-19 min) is valued at roughly half of 99457 (20+ min).
This new logic creates two "either/or" choices for your billing team:
99458 for each additional 20 min)99445 vs. 99454.These 2026 CMS rules are only part of the story. Medicare payment policy and commercial payer coverage are not the same thing.
A new CMS code does not force commercial payers to cover it.
Example: UnitedHealthcare states that, beginning Jan 1, 2026, it will cover RPM only for heart failure and hypertensive disorders of pregnancy. Under that policy, RPM for other conditions (like diabetes or essential hypertension) will be denied as "not medically necessary."
This means you could perfectly follow all the new rules for 99445 and 99470... and still have the claim denied because the patient's diagnosis isn't covered by their specific plan.
FairPath's "Compliance-as-Code" engine is already programmed for the 2026 rules. We automatically select the correct device code, bill the correct time code, and check against payer-specific rules before you bill.
FairPath is built on operational work, not theory. We publish the playbooks and checklists we use to keep programs compliant and profitable. Use them whether you run FairPath or not.
Browse the Expert Library →The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.
Read the RTM Guide →Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.
Read the CCM Guide →The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.
Read the APCM Playbook →