What are the RPM billing CPT codes for Medicare in 2026, and how should clinics bill remote patient monitoring correctly?

Remote patient monitoring (RPM) billing under CPT codes 99453, 99454, 99457, and 99458 remains one of the most reliable recurring-revenue streams available to ambulatory practices in 2026, but the rules have tightened considerably since CMS first introduced reimbursement in 2019. This guide walks through each code, its requirements, current payment expectations, documentation standards, and the proposed CY 2027 changes that every clinic administrator should be tracking now. The short version: RPM is still billable, still profitable for well-run programs, and increasingly dependent on clean data trails, verified device readings, and defensible time logs.

The Core RPM CPT Codes Explained

Also worth reading: What are the real pulse monitoring integration costs for clinics and care networks in 2026? · How do remote monitoring compliance tiers compare for B2B care coordination platforms in 2026? · What are the official RPM and CCM billing time log requirements for Medicare providers in 2026?

Medicare reimburses four principal CPT codes for remote physiologic monitoring, and understanding what each covers is the foundation of any compliant program. CPT 99453 covers the initial setup and patient education on the monitoring equipment; it is billed once per episode of care per device supply order. CPT 99454 covers the supply of the device itself with daily recording and programmed alerts or transmissions, billed once per thirty days. CPT 99457 covers the first twenty minutes of interactive communication between clinical staff and the patient (or caregiver) during a calendar month, requiring at least one minute of that time to occur on the day of the communication. CPT 99458 is an add-on code covering each additional twenty minutes of clinical staff time beyond the initial twenty minutes in the same month.

Payment amounts shift annually with the Medicare Physician Fee Schedule conversion factor, but as of 2026 clinics can generally expect national averages in these ranges: roughly $19–$20 for 99453, $50–$60 for 99454, $50–$55 for 99457, and $40–$45 for 99458. A fully compliant patient generating all four codes across a month produces approximately $160–$180 in gross Medicare revenue before geographic adjustments. That figure sounds attractive, but the real economics depend on adherence rates, staffing costs for the time-based codes, and platform fees — topics covered later in this guide.

Eligibility Requirements: Who Can Be Billed for RPM

RPM under Medicare requires an established patient-physician relationship, meaning the ordering practitioner must have furnished at least one professional service to the patient within the previous twelve months (or another practitioner of the same specialty in the same group). The monitoring must relate to a physiologic parameter — weight, blood pressure, blood glucose, pulse oximetry, respiratory flow rate, or similar data — collected digitally and automatically transmitted to the provider. Manual patient-entered data does not qualify unless it flows through an FDA-defined medical device capable of automatic transmission.

The devices themselves must meet the FDA definition of a medical device, which excludes consumer-grade wearables like standard fitness trackers unless they are cleared or approved for the specific physiologic measurement being billed. Consent is mandatory: the practice must obtain and document the patient's verbal or written consent to receive RPM services, though unlike Chronic Care Management, consent need not be obtained in person. Finally, RPM must not duplicate other services — you cannot bill RPM time and Chronic Care Management (CCM) time for the same minute of staff work, and careful time-allocation policies are essential when running both programs concurrently.

The 16-Day Rule and Data Collection Thresholds

The single most common compliance failure in RPM billing is the sixteen-day minimum. To bill 99454 in a given month, the patient's device must transmit physiologic data on at least sixteen days within that thirty-day period. Readings taken on two days do not count double if multiple measurements occur — only unique days count toward the threshold. If a patient transmits on fifteen days, the practice cannot bill 99454 for that month, period. There is no proration and no exception for partial months initiated mid-cycle, although CMS clarified that the sixteen-day requirement applies within any rolling thirty-day period rather than strictly calendar months, giving practices modest scheduling flexibility.

This threshold has real operational consequences. Industry adherence studies consistently show that 20–35% of enrolled RPM patients fall below the sixteen-day mark in any given month, particularly after the third month of enrollment when novelty wears off. Practices that bill 99454 without verifying day counts face audit exposure, recoupment demands, and potential False Claims Act liability. Any credible RPM workflow therefore includes automated transmission-count verification before claims submission — a function that purpose-built platforms handle natively but that spreadsheet-based workflows routinely get wrong.

Time-Based Billing: 99457 and 99458 Documentation

The interactive communication codes are where RPM revenue concentrates and where audits concentrate too. CPT 99457 requires at least twenty minutes of RPM-related interactive communication with the patient or caregiver during the month, performed by a physician, qualified healthcare professional, or clinical staff under general supervision. General supervision means the work need not happen in the office or under direct observation, but the supervising practitioner must remain accountable. At least one minute of the billed time must occur on the date of service claimed, and the total monthly time must be documented contemporaneously — not reconstructed at month-end from memory.

Documentation should capture the date, duration, modality (phone, video, portal message), the individual performing the service, and a substantive summary of the interaction tied to the monitored data. Vague entries like "checked in with patient" will not survive an audit. Each additional twenty-minute increment supports one unit of 99458, so a forty-five-minute cumulative month supports 99457 plus one unit of 99458. Practices should also note that time spent purely on device troubleshooting or technical support generally does not count toward interactive communication time — the interaction must involve management of the patient's care based on their physiologic data.

Proposed CY 2027 Changes: What Clinics Need to Watch

CMS's proposed rulemaking for Calendar Year 2027 introduces the most consequential changes to RPM since the program launched, and clinics building programs today should design around them. The proposals include tightening supervision requirements, clarifying that treatment-plan review must occur at defined intervals, and — most controversially — restricting payment pathways for RPM services delivered by third-party vendors that lack a direct treatment relationship with the patient. Industry analysis from law firms including Wilson Sonsini and Nixon Peabody highlights that CMS is signaling intent to curb arrangements where vendors furnish monitoring with minimal physician involvement, effectively unbundling the clinical relationship from the technology relationship.

Additional proposals address the interplay between RPM and Remote Therapeutic Monitoring (RTM) codes 98975–98981, which cover musculoskeletal and respiratory therapy adherence data rather than physiologic parameters. RTM differs from RPM in several ways worth noting: RTM permits some manually entered non-physiologic data such as therapy responses, and RTM time-based codes allow general supervision more broadly. The American Academy of Sleep Medicine has also published implementation guidance for remote monitoring in sleep medicine specifically, reflecting growing specialty-level adoption. Clinics should treat the CY 2027 proposed rules as a directional signal: documentation rigor, genuine clinician engagement, and vendor contracts structured around clinical accountability will define compliant programs going forward.

RPM vs. RTM vs. CCM: Choosing the Right Mix

Many practices conflate RPM with adjacent care-management codes, and choosing the wrong framework wastes both staff time and revenue opportunity. The table below compares the three dominant recurring-monitoring frameworks:

These programs stack, but never overlap in time. A heart-failure patient can receive RPM for daily weights and blood pressures plus CCM for monthly care-plan management, provided every minute of staff time is allocated to exactly one program. Practices running two or more programs simultaneously should invest in time-tracking software that tags each interaction to a specific billing category at the moment of service, because retrospective allocation is both labor-intensive and audit-vulnerable.

Common Billing Mistakes and Audit Triggers

Auditors and OIG work plans have flagged several recurring RPM failure patterns. First, billing 99454 without independently verifying the sixteen-day transmission threshold — the most frequent error found in contractor audits. Second, claiming setup code 99453 repeatedly for the same device or billing it for patients who never transmitted data afterward, which suggests the setup was never genuinely completed. Third, inflating time-based code usage: patterns showing nearly every enrolled patient receiving exactly twenty or forty minutes monthly draw statistical scrutiny. Fourth, enrolling patients without documented consent or without an established relationship. Fifth, using non-FDA-cleared consumer devices while billing as though they qualified.

Practices should also understand the financial exposure asymmetry. Because RPM claims are small individually, recovery actions tend to arrive as extrapolated overpayment demands based on sampled charts — meaning a 30% error rate in a sample can trigger repayment across the entire claim population plus interest. Defensible documentation, automated pre-billing validation, and periodic internal chart audits are far cheaper than post-payment remediation. Third-party billing companies unfamiliar with RPM-specific edits frequently miss the day-count check entirely, so practices outsourcing revenue cycle management should confirm their vendor performs transmission verification before claim scrubbing.

Economics: Costs, Margins, and Realistic Revenue Expectations

Gross potential revenue of roughly $170 per fully adherent patient-month understates the true economics. Platform costs for RPM software typically run $15–$60 per patient per month depending on device type and feature depth, cellular-connected devices add $10–$25 monthly in connectivity and logistics amortization, and clinical staff time for the interactive codes consumes meaningful labor hours — a medical assistant handling fifty active RPM patients may spend fifteen to twenty hours weekly on monitoring interactions and documentation. Net contribution per adherent patient often lands between $60 and $110 monthly, which is healthy at scale but thin for small enrollments.

Adherence decay is the dominant economic variable. Programs typically see strong engagement in months one and two, followed by attrition; sustaining sixteen-day compliance past month six usually requires structured outreach protocols, automated reminder cadences, and clinical staff empowered to troubleshoot devices proactively. Practices evaluating RPM should model revenue using conservative assumptions — perhaps 65–75% of enrolled patients meeting the sixteen-day threshold in steady state — rather than best-case projections. Care networks operating across multiple practices benefit from centralized monitoring hubs that concentrate clinical staff time and smooth volume variability across sites.

When to Act and How to Build a Compliant Program

Given the CY 2027 proposed changes, the practical window for launching or restructuring an RPM program is now, while current rules remain in force and while there is time to adapt workflows before final rules take effect. A sensible build sequence runs roughly ninety days: weeks one through four cover eligibility screening of the existing panel (hypertensive, diabetic, CHF, and COPD patients are the highest-yield cohorts), consent workflows, and device procurement; weeks five through eight cover platform configuration, staff training on time documentation, and integration with the EHR; weeks nine through twelve cover a pilot cohort of twenty to fifty patients with weekly adherence reviews before scaling.

Two structural decisions deserve early attention. First, whether to run monitoring in-house or through a vendor — and given CMS's signaled scrutiny of third-party arrangements, contracts should guarantee clinical oversight by the practice's own providers rather than delegating judgment to the vendor. Second, whether to pair RPM with CCM from day one; combined programs improve per-patient economics materially but demand disciplined time-allocation systems. Whichever path a clinic chooses, the durable principle is the same: bill only what the data trail proves, verify thresholds mechanically rather than trusting memory, and treat every documented minute as if an auditor will read it — because eventually, one will.