RTM vs. RPM: The "Signal" Difference Explained

The Bottom Line
  • The Core Difference: RPM is for physiological data (what the body is doing, e.g., BP, Glucose). RTM is for non-physiological data (what the patient is doing, e.g., Inhaler usage, Exercise adherence).
  • The Mistake: You cannot bill RTM codes (98975) for a blood pressure cuff. The device type must match the code family.
  • Self-Reporting: RPM generally requires automatic transmission. RTM allows for self-reported data (like pain scores or therapy completion logs) via a software app.
  • Musculoskeletal & Respiratory: RTM is currently limited to these two specific system buckets (plus a generic "Cognitive" category), whereas RPM covers any chronic condition.

The "Data Type" Cheat Sheet

The most common audit failure in Remote Therapeutic Monitoring (RTM) is "Code Mismatch." This happens when a practice tries to bill RTM codes for a device that is actually capturing physiological data (which should be RPM). Use this table to assign the correct device to the correct program.

Feature RPM (99453 / 99454) RTM (98975 / 9897x)
Data Type Physiological (Blood Pressure, Weight, Pulse, Glucose) Non-Physiological (Adherence, Response to Therapy, Pain Score)
Primary Use Case Chronic Disease Management (Hypertension, CHF, Diabetes). Musculoskeletal (PT/Ortho) & Respiratory (Asthma/COPD).
Transmission Must be automated/synced. Can be self-reported (e.g., app survey).
Staff Type Clinical Staff (General Supervision). PTs, OTs, Speech Pathologists (and MD/DO).

The "Therapy" Requirement

In RPM, the data itself is the endpoint (e.g., "Is BP high?"). In RTM, the data is a proxy for the therapy. For example, knowing a patient used their inhaler (RTM) is only valuable if it is tied to a specific therapeutic goal. You cannot bill RTM just for "watching" a patient; you must be monitoring their response to a specific treatment plan.


Video Transcript

0:00 RPM versus RTM. People mix these up all the time, but the difference is actually really simple if you look at the "Signal."

0:08 RPM (Remote Patient Monitoring) is for physiological data. This is what the body is doing inside. Blood pressure, heart rate, weight, blood sugar. If it's a vital sign, it's RPM.

0:20 RTM (Remote Therapeutic Monitoring) is for non-physiological data. This is usually about the patient's interaction with a therapy. Did they use their inhaler? Did they complete their physical therapy exercises? What is their pain score?

0:32 Why does this matter? Because you cannot bill an RTM code for a blood pressure cuff. And you cannot bill an RPM code for a pain survey app.

0:40 If you cross the streams, you get denied. Keep your "Vitals" in RPM (99454) and your "Adherence" in RTM (98975). That is how you stay safe.

Confused about which codes to use?

Download our comprehensive RTM Guide for Specialists to see the exact code breakdown for Respiratory and Musculoskeletal care.

Standard Operating Procedures

FairPath is built on operational work, not theory. We publish the playbooks and checklists we use to keep programs compliant and profitable. Use them whether you run FairPath or not.

Browse the Expert Library →

RPM Manual

The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.

Read the RPM Guide →

RTM Guide

How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.

Read the RTM Guide →

CCM Guide

Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.

Read the CCM Guide →

APCM Playbook

The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.

Read the APCM Playbook →