RPM Reimbursement Coding Guide 2026: What Clinics Need to Know

For 2026, Medicare reimburses remote patient monitoring under CPT codes 99453, 99454, 99457, and 99458, with the same foundational structure as prior years: one code for setup, one for device supply and data transmission, and two codes for professional time reviewing and managing transmitted data. The headline figures for CY 2026 under the Physician Fee Schedule are roughly $19–20 for initial setup (99453), $48–52 for the first 15 days of device supply each 30-day period (99454), $50–53 for the first 20 minutes of interactive time per month (99457), and approximately $12–13 for each additional 20 minutes (99458). These are national unadjusted figures; your actual payment varies by geographic practice cost index, so most practices see payments within roughly 10–15% of these amounts either way. The codes remain payable by Medicare, most commercial payers have aligned with them, and Medicaid coverage varies by state. What makes the 2026 cycle genuinely different is not the payment amounts but the documentation and technology requirements: CMS has tightened its position on how monitoring devices are supplied, who may furnish the interactive time, and how clinical staff must be involved, while the proposed CY 2027 rule signals further disruption that practices should understand now rather than later.

Also worth reading: What Are the Remote Monitoring Reimbursement Codes for 2026 and How Will CMS Changes Affect Clinics? · Is Your Clinic Ready for RPM Reimbursement in 2026, and What Must You Fix First? · What Is the Definitive RPM Coding Compliance Checklist for Healthcare Clinics in 2027?

This guide walks through the current 2026 coding structure, the time and documentation thresholds you must document to survive an audit, how the CY 2027 proposed changes will alter your operations, and the practical mistakes that cause the most claim denials. The numbers cited here reflect the CY 2026 Medicare Physician Fee Schedule final rule published in late 2025 and the CY 2027 proposed rule released in July 2026; always verify your local Medicare Administrative Contractor guidance before finalizing billing workflows, because contractor-level edits change without much fanfare.

The Core CPT Code Set for Remote Patient Monitoring in 2026

Remote patient monitoring in 2026 rests on four CPT codes that must be billed together as a package for each 30-day period in which you intend to be paid. Code 99453 covers the initial setup and patient education on equipment use, payable once per episode of care, not once per lifetime — a distinction that matters if a patient disengages and re-enrolls months later. Code 99454 covers supply of the monitoring device(s) and daily treatment management during days 1 through 15 of each 30-day period, and it also pays an additional amount for days 16 through 30 when a second submission occurs. Code 99457 pays for the first 20 minutes of live interactive communication between the billing practitioner and the patient or caregiver during the calendar month, and code 99458 pays for each additional 20 minutes, billable in units without a hard cap.

Several structural rules apply across the whole set. Data must be transmitted automatically (not entered manually by the patient into a portal or app), because CMS requires device-generated data flows. The monitoring program must be part of an established practitioner-patient relationship and tied to the management of at least one physiological condition. Notably, CMS stopped requiring the monitoring service to be initiated only by physicians after 2019's restrictive rule was replaced; in 2026, a broad range of practitioners — physicians, NPs, PAs, clinical psychologists, clinical social workers, PTs, OTs, and SLPs — can bill these codes under general supervision where applicable. Incident-to rules apply to staff-performed portions of 99453 and 99454, meaning the supervising practitioner must maintain overall oversight, though general supervision (not direct or personal) is generally sufficient for the technical components.

Time Thresholds and Documentation Requirements You Cannot Skirt

The single most common audit failure in RPM is inadequate time documentation. For 99457, you must document at least 20 minutes of live, interactive communication in the calendar month — live means synchronous voice, video, or real-time two-way interaction; asynchronous review of dashboard data does not count toward 99457. For 99458, each additional unit requires another documented 20 minutes, and the total minutes across all units must be itemized with dates, duration, and the nature of the interaction. CMS expects contemporaneous or near-contemporaneous documentation — a summary note written at the end of the month reconstructing call times is a red flag in an audit.

For 99454, the patient must transmit physiological data on at least 16 days within the 30-day period, and the days cannot all cluster in one week. This 16-day minimum is the numeric threshold that trips up the largest number of claims: if a patient transmits on 12 days, you cannot bill 99454 at all, yet many practices bill routinely based on device deployment rather than actual transmission. You should also document the setup interaction for 99453 with evidence of patient education on the device, consent to participate, and the clinical rationale linking monitoring to at least one managed condition. CMS does not mandate a specific consent form, but your documentation should show the patient understood data will be transmitted and how it will be used in their care.

A final documentation point: the reviewing practitioner must be involved in a meaningful way. CMS has signaled repeatedly (most recently in the CY 2027 proposed rule discussion) that fully outsourced monitoring with a token physician signature is a target for enforcement. The practitioner does not need to personally touch every reading, but the care plan, the escalation protocol, and the monthly clinical summary must reflect actual practitioner judgment.

Proposed CY 2027 Changes: What the July 2026 Rule Signals

The CY 2027 proposed rule, released in July 2026 with a comment period running into September, contains the most consequential proposed restructuring of RPM since the codes were introduced. Three proposals matter most. First, CMS proposed requiring that the practitioner who bills 99457/99458 either personally furnish the interactive time or directly supervise the furnishing practitioner in real time — a move aimed at closing the gap created by third-party vendors that furnish monitoring services with minimal physician involvement. Industry reporting (including Fierce Healthcare coverage of vendor reaction) indicates this could force many clinics to bring monitoring operations in-house or restructure vendor contracts. Second, CMS proposed tightening the definition of the qualifying device, narrowing which equipment configurations count as automatically transmitting physiological data and excluding certain apps and patient-entered data pathways that some programs currently rely on.

Third, and potentially most interesting, CMS issued a Request for Information on whether and how to separately pay for software-as-a-service platforms that support care coordination and monitoring — the first formal signal that CMS recognizes platform costs as distinct from device costs. Nothing in the RFI changes 2026 payment, but it suggests the long-term direction: payment may eventually shift away from device-supply economics toward platform and clinical-workflow economics. The comment period for the proposed rule closed in early September 2026, and a final rule is expected in November 2026 with an effective date of January 1, 2027. Practices running vendor-dependent programs should not wait for the final rule; contract negotiations initiated now will determine whether a program is compliant by January or scrambling.

RPM vs. RTM vs. CCM: How the Codes Compare

RPM is frequently confused with remote therapeutic monitoring (RTM) and with chronic care management (CCM), and billing them incorrectly is expensive. RTM (codes 98975–98981) covers non-physiological data such as musculoskeletal and respiratory therapy adherence, and it can be billed by physical and occupational therapists more readily than RPM. CCM (99490 and related codes) pays for care coordination time that does not involve device data at all. RPM can be billed concurrently with CCM and with transitional care management in the same month, provided time is not double-counted — 20 minutes spent on a call that counts toward 99457 cannot also count toward a CCM code.

The comparison table above highlights why many clinics pair RPM with CCM: a hypertensive diabetic patient on a cellular BP cuff and glucose monitor can generate both a 99454 and a 99490 in the same month legitimately, with RPM time on clinical data review and CCM time on coordination activities. The worst combination is RPM and RTM billed for the same device data without clear separation of data types and time — that pattern is a common trigger for CERT audits.

Practical Steps to Build a Compliant 2026 Billing Workflow

Building a compliant RPM billing operation starts before a single device ships. Step one is eligibility screening: identify patients with at least one managed condition where physiological data would change management — CMS requires the service to be reasonable and necessary, so a patient enrolled with no clear clinical use case is an audit liability even if the data flows. Step two is consent and setup documentation, capturing patient agreement, device education, and enrollment date, which anchors the 99453 claim and establishes the episode. Step three is verifying your device configuration qualifies as automatic transmission; if your workflow depends on patients entering readings into an app, the data does not support 99454 under current rules.

Step four is the operational core: a system that tracks transmission days per patient in real time, flags patients who fall below the 16-day trajectory, and logs every interactive minute with date, duration, staff member, and clinical content. Practices using care-coordination platforms should confirm the platform generates an audit-ready time log export — a spreadsheet assembled retrospectively from call records is weaker evidence than a contemporaneous system log. Step five is the monthly clinical review: a practitioner (not just staff) reviews the data, documents findings, and the interactive communication occurs. Step six is claim submission with correct modifiers where required (some MACs expect modifier notes for incident-to services) and a reconciliation process that voids or adjusts claims for patients who fail the 16-day threshold before the 99454 submission window closes. Practices that automate steps four and six typically see denial rates on RPM claims below 5%; practices doing it manually often see 15–25%.

Common Billing Mistakes That Trigger Denials and Audits

The most frequent and expensive mistake is billing 99454 without 16 qualifying transmission days. Because payment posts before some MACs verify the day count, practices accrue recoupment debt months later when post-payment review catches the shortfall, and repeated patterns escalate to targeted audits. The second most common mistake is counting asynchronous data review toward the 99457 20-minute requirement; an auditors' letter asking for call recordings or synchronous-communication logs quickly exposes this. Third, practices frequently double-count time between RPM and CCM codes — a 22-minute coordination call cannot simultaneously fund a CCM unit and an RPM unit.

Fourth, some vendor-dependent programs bill under a supervising physician who has no documented involvement, which the CY 2027 proposed rule directly targets; even in 2026, this pattern is indefensible in an audit if the physician cannot describe the monitoring protocol or produce notes reflecting clinical judgment. Fifth, billing 99453 repeatedly without documentation of a new episode of care after a gap in service. Sixth, using devices that do not meet the automatic-transmission definition, especially weight scales or BP cuffs that store readings locally and upload later via patient action. A seventh mistake is assuming commercial payers follow Medicare rules exactly; several major payers impose their own 16-day interpretations, device lists, or prior-authorization requirements, so payer-specific verification is part of the workflow, not an afterthought.

When to Act: Timing Considerations Through 2026 and Into 2027

For clinics not yet offering RPM, the fourth quarter of 2026 is the sensible window to launch, because the current rule set is stable, payment rates are known, and you can build workflows against requirements that are unlikely to loosen in 2027. For clinics already running RPM programs, action items cluster into three dates. Between September and November 2026, when the CY 2027 final rule is expected, review your vendor contracts for who actually furnishes 99457 time and whether your arrangement survives the proposed supervision requirement. Before January 1, 2027, any needed restructuring — moving interactive time in-house, renegotiating vendor fees away from per-claim billing models, updating consent and documentation templates — should be complete, because the final rule's changes take effect on that date with no grace period in past cycles.

Also calendar the Merit-based Incentive Payment System implications: RPM services count toward Medicare Part B expenditure thresholds, and practices near the performance threshold should model how RPM revenue affects their MIPS trajectory. Finally, watch the SaaS RFI outcomes closely. If CMS creates a separate payment pathway for platform costs in a future rule, programs built on care-coordination software may gain a distinct revenue line; if it does not, platform costs remain overhead and should be modeled accordingly in your program economics.

Program Economics: What RPM Actually Pays and What It Costs

At maximum reasonable billing — 99453 once, 99454 both submissions, 99457, and two units of 99458 per month — national average Medicare payment is roughly $140–150 per patient per month after the first episode, with the setup month adding about $19. Real-world averages are far lower because the 16-day threshold and actual staff time constrain billing. Most well-run programs bill 99454 for 60–75% of enrolled patients and bill meaningful interactive time for 40–60%, yielding blended revenue closer to $60–90 per enrolled patient per month.

On the cost side, device expenses run roughly $5–15 per patient per month for cellular BP cuffs or weight scales amortized over a device life of two to three years, cellular connectivity adds $3–8 per month, and vendor per-patient fees for turnkey monitoring services commonly range from $25 to $60 per patient per month — a figure that consumes a large share of revenue and explains why the CY 2027 proposed restrictions on third-party furnishing have vendor-dependent clinics worried. In-house staffing costs, typically one care coordinator per 150–250 active monitoring patients at $45,000–$70,000 annually fully loaded, bring a mature in-house program to positive margin at roughly 100–150 actively billing patients. The economics are real but not spectacular; RPM is a modest-margin service whose value shows up more in avoided readmissions and better chronic-disease control than in billing revenue alone. Clinics evaluating programs should model net economics after all device, connectivity, staffing, and platform costs, not the gross figures that marketing materials lead with.