TL;DR
- Core distinction: RPM = physiologic data (BP, glucose, weight) from connected devices. RTM = non-physiologic data (musculoskeletal status, respiratory function, therapy adherence) from patient-reported input.
- Billing eligibility is the real filter: RPM only routes through physicians/NPPs. RTM opened billing to PTs, OTs, SLPs, and psychologists none of whom can bill RPM. A PT-led practice with no physician can run RTM but can’t run RPM at all, regardless of clinical need.
- Mutual exclusivity: Can’t bill both for the same patient in the same month CMS treats them as the same service category. But a practice can run both across different patients (e.g., RPM for cardiac, RTM for post-surgical rehab) simultaneously.
- Who should start with which: Ortho/PT (post-surgical rehab), pulmonology (respiratory adherence), behavioral health → RTM. Cardiology, endocrinology, primary care (chronic disease vitals) → RPM. 2026 short-window codes (2-15 days) make RTM a stronger fit now for shorter rehab episodes.
- Software angle: closes on Mindbowser building routing logic that checks both data type and billing-provider eligibility before enrolling a patient, so mismatches don’t slip through.
Practices researching remote monitoring almost always start with the wrong question. They ask “what is RTM” or “what is RPM” as if picking one is a definitional exercise, when the real decision in front of most of them is narrower and more practical: given the patients this practice actually sees, which program should get built first, and does the answer change once a second program becomes worth adding.
I sat in on a strategy conversation earlier this year where an orthopedic group spent most of an hour debating RPM vendors before anyone asked whether the group could even bill RPM. It couldn’t, not without adding a physician role to a workflow built entirely around its PT staff. The group ended up building RTM instead, which fit both the clinical work and the existing team, and the whole detour could have been skipped by asking the billing-eligibility question first instead of last.
Epic-Approved Vendor · HIPAA and SOC 2 controls built into every build · 50+ healthcare solutions shipped
The Core Distinction: Physiologic vs. Non-Physiologic Data
Remote Patient Monitoring (RPM) covers physiologic data, blood pressure, glucose, weight, oxygen saturation, the kind of vitals a device measures automatically. Remote Therapeutic Monitoring (RTM) covers non-physiologic data instead: musculoskeletal status, respiratory function, therapy adherence, and cognitive behavioral markers, information that typically requires the patient’s own input rather than a device reading alone.
| RPM | RTM | |
|---|---|---|
| Data type | Physiologic (vitals) | Non-physiologic (musculoskeletal, respiratory, adherence) |
| Typical source | Connected device (BP cuff, glucometer, scale) | Patient-reported input, app-based exercise or symptom tracking |
| Common clinical use | Chronic disease monitoring (hypertension, diabetes, heart failure) | Post-surgical rehab, pulmonary therapy, behavioral health adherence |
the fastest way to tell which program a patient’s monitoring plan needs is to ask whether the data comes from a device measuring the body directly, or from the patient reporting on a therapy they’re actively doing.
Who Can Bill Each One
This is the distinction most comparison content skips, and it matters more than the data-type difference for practices deciding whether either program is even accessible to them. RPM billing routes through a physician or non-physician practitioner. RTM opened billing eligibility directly to physical therapists, occupational therapists, speech-language pathologists, and psychologists, none of whom can bill RPM. A physical therapy practice with no physician on staff can run RTM. It cannot run RPM at all, regardless of clinical need, because the billing structure doesn’t support it.
This single fact resolves a lot of “which program should we build” confusion on its own. A pulmonology or orthopedic practice built around PT/OT delivery is often RTM-eligible in a way it simply isn’t RPM-eligible.
The reverse case matters just as much and gets missed more often. A cardiology or endocrinology practice with no PT or OT on staff can still bill RPM cleanly through its physicians and NPPs, and adding RTM to that same practice would mean either bringing on a therapy role that doesn’t currently exist or routing RTM billing through a physician instead, which is allowed but underuses the program’s actual design. Practices sometimes assume both programs are equally accessible once they understand the data-type distinction, then discover mid-planning that their actual staffing model only cleanly supports one of the two without a structural change to who’s on the care team.
Can You Run Both?
No, not for the same patient in the same month. RTM and RPM are mutually exclusive despite monitoring different data types, because CMS treats them as the same category of remote-monitoring service for concurrent-billing purposes. A patient’s monitoring plan for a given month has to pick one or the other, chosen based on which data type the clinical situation actually calls for.
For the full mutual-exclusivity matrix across all Medicare care management programs, see Mindbowser’s program stacking rules guide.
Find Out Which Remote Monitoring Program Fits Your Panel!
Which Practices Should Start With RTM
Orthopedic and physical therapy practices monitoring post-surgical rehabilitation progress are the clearest RTM fit, since the data, exercise completion, pain levels, functional range of motion, is exactly what RTM was built to capture and PT billing eligibility makes it directly accessible. Pulmonology practices tracking respiratory therapy adherence and behavioral health practices monitoring cognitive behavioral therapy engagement fit the same pattern: the clinical work is therapy-adherence-driven, not vitals-driven, and the billing structure matches the actual care team delivering it.
The 2026 short-window codes make RTM a stronger fit than it was even a year ago for practices with shorter treatment episodes. Post-surgical rehab protocols often run under the 16-day window the original codes required, which meant a full month of monitoring had to elapse before the program was billable at all, a poor match for a 3-week recovery plan. The new 2-15 day codes let a practice bill RTM against exactly the kind of short, intensive rehab episode orthopedic and post-surgical PT commonly involves, closing a gap that made RTM a worse fit for this population than the underlying clinical need actually justified.
Which Practices Should Start With RPM
Cardiology, endocrinology, and primary care practices managing chronic conditions through vitals, hypertension, diabetes, heart failure, are the clearest RPM fit. The data is physiologic by nature, connected devices already exist for most of these measurements, and the billing routes cleanly through the physician or NPP already managing the patient’s chronic disease.
RPM’s ongoing, month-over-month monitoring model also fits these specialties’ actual clinical rhythm better than RTM’s would. A hypertension or heart failure patient isn’t working through a defined recovery episode with a natural end point, they’re being monitored indefinitely as part of managing a chronic condition, which is exactly the open-ended structure RPM’s billing was designed around. RTM’s shorter-window codes, useful for RTM’s own episodic rehab population, would be a mismatch here, not because the codes don’t exist for longer monitoring but because the underlying clinical need in these specialties never really has a natural close-out date the way a rehab protocol does.
Running Both Across a Panel, Not Both Per Patient
The mutual-exclusivity rule applies per patient, per month, not across a practice’s entire panel. A multispecialty practice or a health system running both cardiology and orthopedic services can legitimately run RPM for its cardiac patients and RTM for its post-surgical rehab patients simultaneously, as two separate programs serving two separate patient populations.
A patient who transitions between populations, a cardiac patient who also needs post-surgical rehab after an unrelated procedure, simply switches which program applies to them for that month, the same way any patient moving between mutually exclusive programs does.
Building Software That Routes Patients to the Right Program
The distinction between RTM and RPM isn’t complicated once it’s named clearly, but eligibility logic that defaults every remote-monitoring patient into one program regardless of data type or billing-provider eligibility will misroute a real share of a mixed-specialty panel. Mindbowser builds the routing logic that checks both the clinical data type and the billing provider’s eligibility before enrolling a patient in either program, so a PT-led rehab patient doesn’t get evaluated against RPM’s physician-routed billing rule by mistake.
No, they’re mutually exclusive in the same calendar month for the same patient, even though they monitor different data types.
No. RPM billing routes through a physician or non-physician practitioner. Physical therapists can bill RTM directly, which is often the more accessible program for PT-led practices.
RPM monitors physiologic data, vitals like blood pressure and glucose. RTM monitors non-physiologic data, musculoskeletal status, respiratory function, and therapy adherence.
Yes, across different patients. A multispecialty practice can run RPM for its cardiology patients and RTM for its orthopedic rehab patients concurrently, since the exclusivity rule applies per patient, not per practice.









BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 



















