RTM vs RPM: The Key Differences Every PT and Biller Needs to Know in 2026

Quick answer: rtm vs rpm billing depends on whether the program monitors therapy response data or physiologic measurements.

If you run a PT, OT, or multidisciplinary practice, the RTM vs RPM question is not academic. It determines who can bill, what data you can monitor, what device rules apply, and whether your claims logic makes sense before the first patient is enrolled. In plain English, remote therapeutic monitoring vs remote patient monitoring comes down to this: RPM is built for physiologic vital signs captured by connected medical devices, while RTM is built for non-physiologic therapeutic data such as adherence, pain, and function ^{10 13}. That single split drives the rest of the answer.

What is the difference between RTM and RPM?

The fastest answer to what is the difference between RTM and RPM is the type of data being collected, and who is allowed to bill for it. RPM collects physiologic data such as blood pressure, blood glucose, weight, oxygen saturation, and heart rate from connected medical devices that electronically transmit data ^{12 16}. RTM collects non-physiologic data tied to treatment response, including therapy adherence, musculoskeletal status, respiratory therapy response, pain, and function, and it allows patient-reported inputs within the Medicare framework ^{15 14}.

That distinction matters because physical therapists and occupational therapists can bill RTM, but they cannot bill RPM under their own therapy billing pathway ^{13 14}. It also matters because RPM generally fits physician-led chronic disease workflows, while RTM fits rehab, recovery, and therapy-led monitoring programs ^{11 10}.

RTM vs RPM side by side

For billers, this RTM vs RPM difference is the operational heart of the decision. If the program is about vitals and medical-device transmission, start with RPM. If the program is about therapeutic response, home-exercise adherence, symptom trends, or recovery progress, start with RTM ^{11 13}.

What is remote therapeutic monitoring?

Remote therapeutic monitoring is Medicare’s framework for monitoring non-physiologic data related to treatment response. In practice, that usually means tracking whether a patient is following a therapy plan, whether pain or function is changing between visits, or whether a respiratory or musculoskeletal program is working as expected ^{15 10}. RTM was introduced in 2022, which is why it still feels newer and less familiar than RPM in many billing departments.

For rehab-led practices, RTM matters because it created a reimbursement path that RPM never offered. A physical therapist managing post-op knee recovery, a respiratory program monitoring inhaler adherence, or a pain clinic tracking patient-reported status changes can structure a remote monitoring workflow around RTM rather than trying to fit a therapeutic program into a physiologic billing model ^{13 14}.

The evidence base for RTM is promising but still maturing. Reviews in musculoskeletal and pain settings suggest high feasibility, strong patient engagement, and a clear operational role for monitoring between visits, but they do not yet show a uniform pattern of superior hard outcomes over standard care across every use case ^{10 15}. That is the right tone for this topic: useful, reimbursable, and increasingly relevant, but not something to oversell.

What is remote patient monitoring?

Remote patient monitoring is the older, more established program. RPM is built for physiologic metrics such as blood pressure, oxygen saturation, weight, heart rate, and glucose, and it fits chronic disease management best ^{11 19}. If a physician-led practice is trying to detect deterioration in heart failure, hypertension, COPD, or diabetes, RPM is usually the right framework because the monitored signals are objective physiologic measures with clearer ties to medical management ^{12 16}.

RPM also has the stronger outcomes literature. Systematic reviews show benefit in selected chronic disease populations, particularly for acute care utilization and disease control metrics, though the effect size varies by program design and population ^{11 12}. That stronger evidence base is one reason commercial payers are often more willing to define RPM coverage criteria around specific high-cost conditions than they are to broadly reimburse RTM.

The 5 RTM vs RPM differences that matter most

1. Data type: physiologic vs non-physiologic

This is the foundational RTM vs RPM difference. RPM asks, what is happening in the body right now at the physiologic level? RTM asks, how is the patient responding to therapy over time? Oxygen saturation and glucose belong on the RPM side. Pain trends, adherence to a home program, and functional recovery belong on the RTM side ^{19 13}.

That split is also why RTM is so relevant to PT and OT workflows. Many therapy decisions rely on patterns that matter clinically but are not pure vital signs. Function, compliance, and symptom response are often the real drivers of intervention between visits ^{13 15}.

2. Device and workflow requirements

RPM programs are tied to physiologic monitoring workflows and are less flexible operationally. RTM is more naturally aligned with therapeutic software workflows, guided protocols, and patient-reported symptom capture ^{12 10}.

That does not mean RTM is casual or lightweight. It means the program is tracking a different category of clinically relevant signal. For a rehab practice, the important question is often whether the patient is doing the work, responding, and trending toward recovery. Protect the signal, and the workflow becomes more actionable.

3. Who can bill

For most readers searching rpm vs rtm billing, this is the decisive section. Physicians and qualified practitioners in physician-led models can bill RPM. PTs, OTs, and SLPs can bill RTM, which is why therapy-led practices finally have a remote monitoring pathway that maps to the actual care they deliver ^{13 14}.

If you are a rehab operator asking about rtm vs rpm eligibility, the answer is usually straightforward. If your program is therapy-led and your monitored data is therapeutic rather than physiologic, RTM is the relevant lane. If your model depends on physician-supervised vital-sign monitoring, RPM is the relevant lane.

4. Clinical fit

RPM fits chronic disease populations where physiologic deterioration can be detected before an acute event. That includes hypertension, diabetes, COPD, and heart failure, which is consistent with the stronger literature and with how commercial payer policies are typically written ^{11 16}.

RTM fits musculoskeletal care, respiratory therapy adherence, post-surgical recovery, pain programs, and other settings where the real question is whether treatment is working between visits ^{10 14}. This is why remote therapeutic monitoring vs remote patient monitoring is really a workflow decision before it is a code decision.

5. They cannot run together for the same patient in the same month

One of the most important compliance points in the RTM vs RPM discussion is mutual exclusivity. You should not plan to bill both programs for the same patient in the same calendar month. Different patients in the same practice can be enrolled in different programs, and the same patient may move from one model to the other in a different month if the clinical context changes, but the programs are not meant to stack simultaneously for a single patient ¹¹.

2026 code updates: why this year matters

A big reason search volume is rising for terms like rtm vs rpm billing and rtm vs rpm difference is that 2026 changed the structure meaningfully. New codes created shorter-duration billing options for both frameworks, which matters for episodic care, post-discharge windows, and patients who do not cleanly fit a 16-day-plus monitoring cadence.

RTM CPT comparison for 2026

National average rates. Actual payment varies by geography, payer, and participation model. Verify current rates with the CMS Physician Fee Schedule Look-Up Tool.

For PTs and billers, the biggest practical shift is the lower threshold. Shorter monitoring windows can now make more operational sense for episodic musculoskeletal and recovery programs, which is part of why RTM is becoming easier to justify in post-op and short-duration rehab workflows ^{10 14}.

RPM CPT comparison for 2026

National average rates. Actual payment varies by geography, payer, and participation model. Verify current rates with the CMS Physician Fee Schedule Look-Up Tool.

For clinics comparing rpm vs rtm billing, the important point is not just the codes themselves. It is that CMS is making both frameworks more flexible, while still keeping their use cases distinct.

RTM reimbursement potential for rehab-led programs

If your practice is evaluating RTM first, the economics are one reason interest is rising. Sensor Bio’s approved revenue framing places RTM reimbursement potential at roughly $89 to $130 per enrolled patient per month at full utilization, using setup, device supply, and review code combinations. Device supply alone is commonly framed around roughly $52 per month in the approved corpus.

That does not mean reimbursement is guaranteed, and it definitely does not mean every payer will treat the program the same way. It does mean RTM has moved from experimental curiosity to an operationally relevant care model for practices that can support enrollment, documentation, and follow-up. Know when to act. Know how to respond.

When RTM is the right fit

RTM is usually the better fit when:

• Your practice is PT, OT, SLP, pain, or rehab led
• The monitored information is adherence, pain, function, recovery progress, or therapy response
• Your patient population includes musculoskeletal, post-surgical, respiratory adherence, or recovery workflows
• You need a remote care model aligned to therapeutic rather than physiologic tracking
• You want a care model that supports continuous monitoring of how treatment is working between visits

This is the most common real-world answer to the rtm vs rpm eligibility question for therapy-led groups. If the practice is built around treatment response, RTM is usually the correct starting point ^{13 15}.

When RPM is the right fit

RPM is usually the better fit when:

• Your practice is physician led
• The monitored data is blood pressure, glucose, oxygen saturation, weight, or another physiologic metric
• Your patients are being managed for chronic diseases such as hypertension, diabetes, COPD, or heart failure
• The goal is early detection of physiologic deterioration, not just tracking treatment adherence
• Your workflow already supports structured medical management around those biometric signals

In other words, if your clinical question is whether the patient’s physiology is destabilizing, RPM usually makes more sense than RTM ^{11 12}.

Payer coverage is where many billing assumptions break

This is the section most comparison articles miss. Medicare fee-for-service may cover both frameworks when requirements are met, but commercial payer behavior is not automatically aligned. That matters because many practices read a Medicare explainer and assume the same rules apply to every commercial plan.

They do not. Commercial payer coverage varies materially, and some policies are far more restrictive. Cigna’s current commercial policy language is especially important because it explicitly limits RPM to specific condition pathways and excludes RTM codes from coverage for commercial indications. That means a practice can be clinically right about RTM and still face denial risk if the payer policy does not support it.

Here is the practical takeaway for billers:

For an awareness-stage article, the cleanest way to say this is simple: always verify payer policy, especially for RTM. That is not just a compliance footnote. It is central to safe program design.

FAQ

Can a physical therapist bill RPM?

No, not in the same way they can bill RTM. For most therapy-led practices, RPM is not the right reimbursement lane. RTM was the important expansion because it opened remote monitoring to therapy-relevant workflows and billing pathways ¹³.

What is the main RTM vs RPM difference?

The main difference is the data type. RPM is for physiologic data. RTM is for non-physiologic therapeutic data such as adherence, pain, and function ^{19 13}.

Can RTM and RPM be billed together?

Not for the same patient in the same calendar month. Practices can run both programs across different patient groups, but they should not plan to stack them for one patient at the same time ¹¹.

Does RTM require the same type of device model as RPM?

No. RTM workflows are more flexible because the monitored information is therapeutic rather than purely physiologic. That is one reason RTM works better for rehab-led care models ¹⁰.

Why are more people asking about rpm vs rtm billing in 2026?

Because the 2026 code changes made the categories more practical for shorter monitoring windows, and because more PT and rehab groups are evaluating remote monitoring as a real operational program rather than a future concept.

How should a practice choose between remote therapeutic monitoring vs remote patient monitoring?

Start with three questions: what data are you collecting, who is billing, and what clinical workflow are you supporting? If the answers are therapeutic data, rehab-led care, and treatment-response monitoring, RTM is usually the right path. If the answers are physiologic vitals, physician-led care, and chronic disease monitoring, RPM is usually the right path.

RTM and RPM are not competing labels for the same service. They are two distinct reimbursement frameworks built for different kinds of signal, different care teams, and different clinical decisions. For PTs, OTs, and rehab-focused operators, RTM is usually the more relevant path because it reflects how therapy actually works between visits. For physician-led chronic disease programs, RPM remains the better fit. The smartest next step is not to memorize every code. It is to map the program to the right clinical workflow first, then build billing and documentation around that choice. Sensor Bio supports the RTM care model with continuous biometric infrastructure designed to help teams know when to act, and know how to respond.

RTM vs RPM: qualifying data types and device rules

The first dividing line in the rtm vs rpm comparison is what the device actually measures. RPM (Remote Physiologic Monitoring) under CPT codes 99453–99454 requires a medical device that collects and transmits physiologic data — blood pressure, pulse oximetry, weight, or blood glucose are the most common examples. The device must be FDA-cleared for the physiologic parameter being reported, and the data must be transmitted electronically to the clinical team. RTM (Remote Therapeutic Monitoring) under CPT codes 98975–98977 and 98980–98981 is designed for software-based tools that collect therapeutic outcome data: pain level, functional status, medication adherence, respiratory therapy adherence, or musculoskeletal status. A tablet app that logs pain scores is an RTM device; a wrist cuff that transmits blood pressure readings is an RPM device.

Device classification shapes every downstream billing decision in the rtm vs rpm framework. An RPM device must meet FDA 510(k) clearance or equivalent for the specific physiologic parameter being monitored — a general wellness tracker does not qualify. An RTM software platform does not require FDA device clearance in the same way, but it must be designed to collect and transmit the therapeutic data described in the CPT descriptor. When a practice evaluates a new monitoring vendor, the first verification step is confirming the device classification and whether the data type maps to the correct code family. Misclassifying a software wellness app as an RPM device is a common audit exposure.

RTM vs RPM CPT code families: setup, supply, and management

The rtm vs rpm distinction becomes most concrete when mapping the CPT code families. RPM uses four primary codes: 99453 (device setup and patient education, once per episode), 99454 (device supply with daily recordings transmitted for at least 16 days in a 30-day period), 99457 (first 20 minutes of treatment management per calendar month), and 99458 (each additional 20 minutes). RTM uses a parallel structure: 98975 (setup), 98976–98977 (device supply, tiered by data type — musculoskeletal or respiratory), and 98980–98981 (treatment management, first 20 minutes and additional 20-minute increments). Both families require real-time interactive communication for the management codes; asynchronous data review alone does not meet the threshold.

Time-counting rules differ between the two families in the rtm vs rpm context. RPM treatment management time (99457–99458) is counted across the calendar month and can be accumulated by clinical staff under general supervision of a billing physician or NPP; direct supervision is not required for the time component. RTM treatment management time (98980–98981) requires the service to be performed by the treating practitioner or clinical staff under their direct supervision — a stricter rule that reflects RTM’s origin in therapy-based billing. Practices that employ both PTs and physicians managing the same patient may bill from both code families if the data types and providers meet separate qualifications, but the two programs cannot be billed for the same service encounter.

RTM vs RPM supervising-clinician and provider requirements

Provider eligibility is a core rtm vs rpm compliance question. RPM (99453–99458) is available to physicians, nurse practitioners, physician assistants, and other NPPs who can independently bill Medicare Part B. Clinical staff may perform the monitoring activities, but the billing must be attributed to an eligible supervising clinician. RTM (98975–98981) was designed specifically to open remote monitoring to physical therapists, occupational therapists, and speech-language pathologists, who cannot independently bill RPM codes. A PT practice can bill RTM for musculoskeletal or respiratory adherence data; that same PT practice cannot bill RPM because PTs are not eligible RPM providers under current CMS policy. The supervising-clinician rule governs which code family each practice can access.

When the rtm vs rpm question arises in a multi-disciplinary clinic, the answer often involves parallel billing rather than a single choice. A physician-supervised care coordinator managing a hypertension patient’s blood pressure device bills RPM. A PT in the same clinic tracking that patient’s home exercise adherence through a software app bills RTM. Both programs can coexist for the same patient in the same month, provided the services are distinct, the data types match the code descriptors, and documentation captures each program’s time and clinical decision-making separately. Payers vary in how they handle concurrent billing, so confirming plan-specific policy before submitting dual claims is standard practice management.

RTM vs RPM documentation and time requirements

Documentation in the rtm vs rpm comparison follows a similar structure for both programs but with program-specific thresholds. For RPM, the 99454 supply code requires evidence that the patient transmitted data on at least 16 days within the 30-day billing period; the chart note should record the device used, the physiologic parameter, the transmission days, and any clinical response to the data. For RTM, the 98976–98977 supply codes require data transmission on at least 16 days per 30-day period as well, but the data type must match the code — musculoskeletal data for 98976, respiratory therapy data for 98977. A single documentation template covering both programs is a compliance risk; each program’s note should address its own code-specific requirements.

Treatment-management notes for both rtm vs rpm families must document the time spent, the content of the clinical review, any interactive communication with the patient, and the clinical decision or recommendation that resulted from the review. Generic notes stating only “reviewed device data, no concerns” are insufficient under audit standards. Best practice is to record what the data showed, what the clinician assessed, and what action — whether a care-plan adjustment, a follow-up recommendation, or patient education — followed the review. Time documentation should be contemporaneous and should distinguish between synchronous interactive time and asynchronous review time, because only interactive communication counts toward the management code thresholds in most payer interpretations.

RTM vs RPM: when each program fits your practice

Choosing between rtm vs rpm ultimately comes down to three practice-level factors: the type of clinician delivering the service, the data type the monitoring platform captures, and the patient population’s primary care needs. Therapy-led practices — PT, OT, SLP — should default to RTM and confirm that their software platform meets the therapeutic-data requirements for the relevant code (musculoskeletal or respiratory). Physician and NPP practices monitoring chronic disease markers like blood pressure, weight, or oxygen saturation should default to RPM and verify that their device meets FDA clearance requirements for that parameter.

Mixed or evolving programs benefit from a structured rtm vs rpm audit at the start of each plan year. CMS updates coding guidance in the annual Physician Fee Schedule, and commercial payers sometimes add or withdraw coverage for one program while maintaining the other. A brief annual review — confirming device classification, provider eligibility, payer-specific coverage policies, and documentation templates — is the most efficient way to avoid retroactive denials or compliance exposure. For practices just launching a remote monitoring program, starting with one code family, building a compliant workflow, and then expanding is consistently lower-risk than launching both RPM and RTM simultaneously without clear program separation.