RPM CPT Codes 2026: What Each One Pays and Who Bills It

The most consequential change to remote patient monitoring billing in years is not a rate adjustment, it is a structural rewrite of the time and duration thresholds that have governed the program since its inception. For health IT directors and telehealth operations teams, the RPM CPT codes 2026 schedule introduces two new codes and lowers the data-collection floor that previously sat at 16 days. That single change reshapes which patient encounters become billable, which in turn changes how monitoring data must be captured, time-stamped, and routed through the EHR. Understanding each code, its 2026 dollar value, and the documentation trigger behind it is now a prerequisite for any team configuring an RPM technology stack.

"The 2026 Medicare Physician Fee Schedule Final Rule, released November 5, 2025 and effective January 1, 2026, adds two new RPM codes (99445 and 99470) and lowers the minimum data-transmission requirement from 16 days to as few as 2 days within a 30-day period.", Centers for Medicare and Medicaid Services, CY 2026 Physician Fee Schedule Final Rule

Decoding the RPM CPT Codes 2026 Schedule

Remote patient monitoring reimbursement is built from three functional buckets: setup and education, device supply and data transmission, and clinical management time. The RPM CPT codes 2026 update keeps that three-part architecture intact but adds short-duration siblings to the supply and management families. The result is a more granular code set that pays providers for monitoring episodes that previously fell below the billing threshold and went uncompensated.

The practical implication for integration teams is that the EHR can no longer treat 16 days as a hard gate. A device that transmits readings on just 2 to 15 days now maps to a billable code, which means the data pipeline, the calendar logic, and the time-tracking layer all need to recognize shorter windows. Each code below carries its own documentation trigger, and missing that trigger is the single most common reason RPM claims are denied.

CPT Code	What It Covers	2026 Est. Rate	Billing Frequency	Documentation Trigger	Who Bills It
99453	Initial setup and patient education on device use	~$22	Once per episode of care	Minimum 2 days of data transmitted (lowered from 16)	Physician/QHCP, often via clinical staff
99454	Device supply with daily recording, 16-30 days	~$52/month	Every 30 days	At least 16 days of readings in a 30-day period	Physician/QHCP (supply furnished under their order)
99445 (NEW)	Device supply, 2-15 days within a 30-day period	~$52/month	Every 30 days	2 to 15 days of readings in a 30-day period	Physician/QHCP
99457	First 20 minutes of management/treatment, with interactive communication	~$52/month	Once per month	20 minutes of clinical staff time plus live patient interaction	Clinical staff under general supervision
99458	Each additional 20 minutes of management	~$41/month	Add-on, multiple times	Each additional full 20-minute block documented	Clinical staff under general supervision
99470 (NEW)	First 10 minutes of management/treatment	~$26	Once per month	10 minutes of clinical staff time plus interaction	Clinical staff under general supervision

A few structural relationships matter for anyone configuring claim logic:

• 99445 and 99454 are mutually exclusive for the same 30-day period. The system bills one based on how many days of data arrived, not both.
• 99470 and 99457 are also alternatives. If management time crosses the 20-minute mark, 99457 applies; if it lands between 10 and 19 minutes, 99470 captures it.
• 99458 only stacks on top of 99457, never on 99470. Add-on logic in the EHR must enforce that dependency.
• 99453 is a one-time code per episode, and the new 2-day minimum means setup can be billed far earlier in the patient relationship.

How CMS RPM reimbursement technology triggers map to workflow

The codes themselves are only half the equation. Each one is tied to a measurable event that the underlying CMS RPM reimbursement technology must capture automatically, because manual reconstruction of these triggers at month-end is where revenue leaks. The 99453 99454 99457 99458 family, now joined by 99445 and 99470, depends on accurate day counts and time tracking that survive an audit.

Device supply codes: counting days, not readings

For 99454 and the new 99445, the billable unit is the number of distinct calendar days on which the device transmitted a qualifying reading, not the total number of readings. A patient who records three blood pressure values on a single day still contributes one day toward the threshold. Integration teams need a data model that deduplicates by date and flags when a 30-day window has accumulated either 2-15 days (99445) or 16 or more days (99454). FHIR Observation resources timestamped at the source make this calculation deterministic rather than estimated.

Management codes: defensible time capture

99457, 99458, and 99470 are time-based and require interactive communication with the patient or caregiver during the calendar month. The documentation must show who performed the work, the cumulative minutes, and that a live interaction occurred. Time logged passively by a dashboard sitting open does not qualify. Operations teams typically tie a timer to discrete clinical actions inside the EHR so that minutes accrue against the patient record and roll up cleanly to 99470 at 10 minutes and 99457 at 20.

Setup code: the new early trigger

Because 99453 now requires only 2 days of transmitted data instead of 16, the setup code can be released much sooner. For high-volume programs, this changes onboarding cash flow, and the enrollment workflow should fire the 99453 eligibility check as soon as the second qualifying day posts.

Current research and evidence

Analysis of the CY 2026 Physician Fee Schedule by the law firm McDonald Hopkins (2025) confirms that CMS finalized lower time thresholds specifically to reimburse shorter, clinically meaningful monitoring episodes that the prior 16-day rule excluded. Their review notes that 99445 was created to pay for the 2-to-15-day window at parity with 99454, removing the all-or-nothing penalty that previously discouraged short-term post-discharge monitoring.

Industry billing analyses published by ThoroughCare (2025) and Rimidi (2025) place the 2026 national average values at roughly $22 for 99453, about $52 for both 99454 and 99457, near $41 for the 99458 add-on, and approximately $26 for the new 99470 short-duration management code. These figures move with the 2026 conversion factor, which CMS increased, producing proportional upward adjustments across the RPM family. Because Medicare rates are geographically adjusted, the published national averages are planning figures rather than guaranteed payments, and finance teams should localize them against their carrier locality.

The consistent finding across these analyses is operational, not clinical: programs that automate day-counting and time-capture realize the new codes, while programs relying on manual logs continue to under-bill and over-deny. The expansion of billable scenarios raises the value of clean, machine-readable data capture.

The Future of RPM CPT Codes

The 2026 changes signal a clear direction. CMS is unbundling monitoring into finer increments, which rewards precise measurement and penalizes coarse, manual tracking. Several trends follow from that trajectory.

• Shorter episodes become economically viable, opening RPM to acute post-discharge, medication-titration, and short-term diagnostic use cases rather than only chronic long-term enrollment.
• Documentation scrutiny rises as the number of billable permutations grows, making automated, source-timestamped data the audit defense of record.
• Code logic complexity increases, since systems must now arbitrate between 99445 and 99454, and between 99470 and 99457, based on real-time accumulation rather than month-end review.
• Interoperability becomes a billing function, not just a clinical one, because the day count and time log that justify a claim originate in the device-to-EHR pipeline.

Health systems that treat reimbursement logic as a property of their integration architecture, rather than a back-office reconciliation task, will capture the new codes with the least friction.

Frequently asked questions

What are the new RPM CPT codes for 2026? CMS finalized two new codes effective January 1, 2026: 99445 for device supply when data is transmitted on 2 to 15 days within a 30-day period, reimbursed at parity with 99454, and 99470 for the first 10 minutes of clinical management per month, estimated near $26. Both fill gaps left by the previous 16-day and 20-minute thresholds.

Did the 16-day data requirement go away in 2026? Not entirely. 99454 still requires at least 16 days of data in a 30-day period. The change is that monitoring on just 2 to 15 days is now billable under the new 99445 code, and 99453 setup now requires only 2 days of transmitted data instead of 16.

Who is allowed to bill RPM management codes 99457, 99458, and 99470? These time-based management codes are billed by the physician or qualified healthcare professional but may be performed by clinical staff under general supervision, provided the time and a live interactive communication with the patient are documented in the record.

How much does the full RPM code set pay per patient per month in 2026? A typical enrolled patient billed under 99454 plus 99457 yields roughly $104 per month in 2026 national-average terms, before geographic adjustment, with 99453 adding a one-time setup payment near $22 and 99458 adding about $41 for each additional 20 minutes of management.

Circadify is addressing this space by capturing RPM vital signs as source-timestamped, HL7 FHIR-compatible data that maps directly to the day-count and time-tracking triggers behind every 2026 code, so billing logic lives in the integration layer rather than a month-end spreadsheet. Health IT and telehealth operations teams evaluating billing-ready monitoring infrastructure can review the integration documentation and EHR guides at circadify.com/solutions/telehealth.