What are the key RPM vs RTM billing differences for Medicare in 2026?

Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM) are two distinct Medicare reimbursement pathways that clinics and care networks frequently confuse, and the confusion costs practices real revenue every year. As of August 2026, the distinction matters more than ever because CMS has been actively reshaping both programs through the Physician Fee Schedule rulemaking cycle, including proposed changes to supervision requirements, device supply definitions, and even a request for information on how software-as-a-service platforms should be reimbursed. This guide breaks down the definitive differences between the two billing frameworks, where they overlap, where they diverge, and what care-coordination teams need to do differently depending on which pathway their monitoring program falls under.

The Direct Answer: What Separates RPM from RTM

Also worth reading: What are the actual billing differences between Transitional Care Management (TCM) and Chronic Care Management (CCM) in 2026? · How will the 2027 Medicare fee schedule changes impact RPM billing for small clinics? · What is the RADV audit preparation timeline for Medicare Advantage plans in 2026?

The core difference comes down to what is being monitored. RPM (CPT codes 99453, 99454, 99457, 99458) covers physiologic data — blood pressure, blood glucose, weight, pulse oximetry, respiratory flow rate, and similar biometric measurements collected by an FDA-defined medical device. RTM (CPT codes 98975, 98976, 98977, 98980, 98981) covers non-physiologic data related to a patient's response to therapy: musculoskeletal system status, respiratory system status, medication adherence, and therapy response data. A connected blood pressure cuff generating systolic/diastolic readings is RPM territory; a sensor tracking whether a patient completed their prescribed physical therapy exercises or took their inhaler as scheduled is RTM territory.

This distinction drives everything downstream: who can bill, what devices qualify, how much time must be documented, and what clinical staff categories can perform the work. RPM requires the data to come from a medical device that meets the FDA definition of such, while RTM permits software or applications that collect self-reported or digitally captured therapeutic data without necessarily qualifying as a regulated medical device. For a multi-specialty clinic network deciding where to invest, that single definitional fork determines whether cardiology and endocrinology programs route through RPM while orthopedics, pulmonology rehabilitation, and behavioral adherence programs route through RTM.

Billing Codes and Reimbursement Structure Compared

The two programs use entirely separate code families with different time thresholds and payment amounts. RPM's established code set has been stable since 2019-2021, while RTM's codes were introduced effective January 2023, making it the newer and less mature program. The table below summarizes the structural comparison:

Two numbers deserve emphasis. First, RPM's 99454 pays roughly three times what RTM's 98976/98977 pays for the monthly supply component, reflecting CMS's view that physiologic device data carries higher resource costs. Second, RTM's treatment-management codes (98980/98981) pay substantially less than RPM's 99457/99458 because CMS assumes less interactive clinician time is needed to interpret therapy-adherence data than to act on abnormal vitals. Practices that model RTM economics using RPM assumptions routinely overestimate revenue by 40-60 percent on the management side.

Who Can Bill: Practitioner Eligibility Differences

Eligibility is one of the most consequential differences between the two programs. RPM billing is restricted to physicians and specific non-physician practitioners: nurse practitioners, physician assistants, clinical nurse specialists, certified nurse midwives, clinical psychologists, and clinical social workers. Physical therapists, occupational therapists, and speech-language pathologists cannot bill RPM codes at all, even when they supervise patients using connected devices.

RTM opens the door to those therapy disciplines. Because musculoskeletal and respiratory therapy monitoring sits squarely within PT/OT/SLP scope of practice, CMS deliberately included them as eligible RTM billers. For hospital-owned therapy groups and outpatient rehab networks, this was the entire point of the RTM program — it created a first-ever remote-monitoring reimbursement lane for allied health professionals. However, incident-to billing rules still apply: auxiliary personnel performing monitoring services must work under appropriate supervision, and the billing practitioner must initiate the plan of care. Clinics should also note that RTM does not require the condition being monitored to be chronic in the way many RPM implementations assume; acute post-surgical recovery monitoring fits RTM naturally, which is why orthopedic practices were early adopters.

Time Requirements, Documentation, and Compliance Traps

Both programs require meaningful interaction time, but the mechanics differ. RPM's 99457 requires at least 20 minutes of cumulative treatment-management services per calendar month, with 99458 billed for each additional 20 minutes. Critically, CMS allows this time to be performed by clinical staff (medical assistants, nurses) under general supervision, not solely by the billing practitioner — but the time must be documented contemporaneously and attributable to qualified personnel. The 2026 rulemaking cycle has included proposals to tighten documentation expectations here, and Wilson Sonsini and McGuireWoods analyses of recent proposed rules flagged CMS's continued scrutiny of whether practices are genuinely meeting the 20-minute floor versus backfilling time records after the fact.

RTM's 98980 similarly requires 20 minutes of treatment-management services, but CMS clarified that the time may include non-interactive activities like reviewing adherence dashboards, whereas RPM's interactive requirement has historically pushed auditors toward expecting live patient communication somewhere in the month. The most common compliance failures we see across both programs include: billing 99454 when fewer than 16 days of readings occurred in the 30-day period; counting device-readiness checks toward interactive time; enrolling patients who never consented in writing; and using devices that transmit automatically but lack the required ability to upload data independently of the patient (a requirement CMS has debated relaxing in recent proposed rules). Any clinic running a hybrid RPM-plus-RTM program needs separate audit trails per program, because an auditor will evaluate each code family against its own rules.

Device and Software Requirements: Where the Programs Diverge Sharply

RPM's device definition has been a persistent friction point. CMS requires that RPM data originate from a medical device meeting the FDA definition — meaning it must be intended for a medical purpose and capable of automatic transmission of patient data to the provider. Manual patient entry of blood pressure values into an app generally fails this test unless the app itself qualifies as the medical device. This constraint shaped the entire RPM hardware market around cellular-connected cuffs, glucometers, and scales.

RTM relaxes this considerably. CMS explicitly stated in the 2022 final rule that RTM data can be collected by software applications, including apps where patients self-report symptoms, pain scores, medication adherence, or complete guided exercises tracked by smartphone sensors. That flexibility is why RTM adoption has grown fastest among digital-therapeutics companies and behavioral-health programs rather than traditional device manufacturers. It also connects directly to CMS's request for information on reimbursing SaaS-based monitoring platforms: if CMS eventually creates a payment mechanism recognizing platform fees separately from device supply, RTM-style software-first programs stand to benefit more than hardware-dependent RPM programs. Vendors and clinic buyers watching the proposed-rule comment cycles should treat this as the single biggest open variable in 2026 monitoring economics.

Practical Steps for Choosing Between RPM and RTM

Start by mapping your clinical use case to the data type. If the monitoring question is 'what are the patient's vital signs doing,' you are in RPM. If it is 'is the patient following the care plan and responding to therapy,' you are in RTM. Next, verify your billing practitioners: a cardiology clinic with only physicians and APPs can run either program, but a physical-therapy-led recovery program can only bill RTM. Third, inventory your technology — if you already own FDA-cleared connected devices, RPM's higher supply-code payment makes the hardware investment easier to justify; if your solution is an app capturing self-reported outcomes, RTM is likely your only compliant path.

Operationally, build the workflow before enrollment begins. Both programs require written patient consent, a defined 30-day measurement period, and documented time logs. Set enrollment targets conservatively: industry experience shows 25-45 percent of enrolled RPM patients fail to generate 16 days of readings in a given month, and those months cannot be billed for 99454. Design outreach cadences that trigger at day 8-10 of low transmission rather than waiting until month-end. Finally, decide whether to run both programs in parallel — many care networks do, using RPM for chronic-disease panels and RTM for post-discharge surgical recovery, with shared intake infrastructure but segregated billing workflows.

Common Mistakes and How Auditors Catch Them

The highest-frequency error remains the 16-day threshold violation on RPM. Practices enroll a patient mid-month, the patient transmits for 11 days, and someone bills 99454 anyway. OIG work plans and MAC audits have targeted exactly this pattern since 2022. The second-most-common mistake is double-dipping time: counting the same 20 minutes toward both 99457 and Chronic Care Management (99490) in the same month. CMS permits concurrent RPM and CCM billing, but the time counted toward each must be distinct — a rule that requires disciplined time-tracking systems rather than good intentions.

On the RTM side, the classic error is treating 98976/98977 as interchangeable with 99454 and billing it for physiologic data. Auditors also flag RTM claims where the underlying condition is not a musculoskeletal or respiratory diagnosis, since those are the only body systems RTM currently covers. A third category of risk involves third-party vendors: some remote-monitoring IDTF-style entities have marketed turnkey programs promising passive revenue, and Reed Smith's analysis of proposed rule changes highlights regulatory uncertainty around whether qualified third parties can continue supporting these arrangements if CMS tightens supervision and ownership requirements. Practices should contractually require vendors to warrant coding compliance and to provide raw time-and-transmission logs, not just summary invoices.

When to Act and What the 2026 Rule Cycle Means

Timing matters because the ground is moving. CMS's proposed rule activity covered in analyses from McDermott+, Foley & Lardner, and McGuireWoods includes potential changes to RPM device-supply definitions, supervision standards, and a formal information-gathering process on SaaS reimbursement. None of these proposals is finalized as of August 2026, which means current billing rules remain in effect, but practices building multi-year vendor contracts should negotiate flexibility clauses tied to rule changes. If CMS finalizes a SaaS payment pathway, software-first RTM platforms could see materially improved economics; if it tightens the medical-device definition further, some RPM hardware categories could face disruption.

For clinics not yet billing either program, the practical answer is to start now under current rules rather than wait for clarity. RPM has five years of settled guidance and predictable audit patterns; RTM has three years and growing payer acceptance beyond Medicare, with several commercial insurers adding RTM coverage in 2025-2026. The learning curve — consent workflows, transmission monitoring, time documentation — takes a quarter to get right regardless of when you start, and starting earlier means your team reaches competence before any new requirements land. Care networks evaluating platforms should prioritize vendors that support both code families natively, maintain audit-ready logs, and publish their position on pending rule changes rather than leaving clients to interpret Federal Register text alone.

Cost and Revenue Modeling Reality Check

Gross Medicare reimbursement for a fully compliant RPM patient runs approximately $120-140 per month (setup amortized), combining 99453, 99454, and 99457. A fully compliant RTM patient generates roughly $60-85 per month. Those gross figures shrink quickly: device acquisition or lease costs typically consume $15-40 per patient per month on the RPM side, platform fees add another $10-25, and staffing for the 20-minute interaction requirement plus enrollment outreach consumes the largest share. Net margins of $30-70 per RPM patient per month are realistic for well-run programs; poorly run programs lose money once you account for the 25-45 percent of enrollees who never hit transmission thresholds.

RTM's lower payments are partially offset by near-zero hardware cost when the 'device' is a smartphone app, so net margins per engaged patient can approach RPM levels despite the smaller gross. The strategic takeaway for B2B decision-makers is that neither program is a windfall; both are modest-margin service lines whose value compounds when integrated into broader care-coordination workflows alongside CCM, TCM, and annual wellness visits. Clinics chasing monitoring revenue as a standalone profit center consistently underperform clinics that embed it into existing chronic-care operations.