Program Stacking
RPM + RTM.
CMS permits billing both RPM and RTM for the same patient in the same calendar month — but only for different conditions. This combination produces the highest estimated two-program revenue at $280–390 per patient per month, pairing physiologic device monitoring with therapeutic outcome tracking. The critical compliance rule: RPM and RTM cannot be billed for the same condition.
Side by Side
Feature comparison.
Analysis
Key considerations.
CRITICAL: Must be billed for different conditions
Unlike RPM + CCM or RPM + BHI, RPM and RTM cannot be billed for the same condition in the same month. A patient receiving RPM for hypertension (blood pressure monitoring) can receive RTM for musculoskeletal rehab (therapy adherence), but cannot receive both RPM and RTM for the same respiratory condition. This is the most important compliance rule for this stack.
Highest two-program revenue combination
RPM (~$160–220) plus RTM (~$120–170) produces an estimated combined revenue of $280–390+ per patient per month — the highest of any two-program stack. This is because both programs include device/data supply codes and clinical review codes, unlike CCM or BHI which are purely time-based.
Different data domains support billing separation
RPM collects objective physiologic data from medical devices (blood pressure, weight, glucose). RTM collects therapeutic data including patient-reported outcomes, therapy adherence, pain levels, and functional status. The distinct data types make it straightforward to document that each program addresses a different condition.
RTM extends monitoring beyond traditional vital signs
Adding RTM to an RPM program expands clinical monitoring into therapy adherence and functional outcomes — areas that physiologic devices cannot measure. This creates a more complete picture of patient health, covering both the chronic condition being monitored by RPM and the rehabilitation or therapy being tracked by RTM.
Guidance
When to stack.
Stack RPM + RTM when
The patient has a chronic physiologic condition requiring device monitoring AND a separate condition requiring therapeutic monitoring. Example combinations: hypertension (RPM — BP monitor) + post-knee replacement rehab (RTM — therapy adherence), diabetes (RPM — glucose monitor) + chronic low back pain therapy (RTM — pain/mobility tracking), heart failure (RPM — weight monitoring) + pulmonary rehab (RTM — respiratory therapy adherence).
Do not stack when
Both the RPM and RTM conditions overlap or are clinically the same condition. COPD monitored via RPM pulse oximetry cannot also be billed via RTM respiratory therapy codes for the same patient in the same month. Additionally, do not stack if the patient does not have a genuine separate therapeutic condition — forcing an RTM enrollment for revenue without clinical need creates significant audit risk.
Ideal patient profiles
The strongest candidates are patients with a well-established chronic condition managed by RPM who also have a distinct musculoskeletal, respiratory therapy, or behavioral condition managed through RTM. Examples: a 72-year-old with hypertension (RPM — BP monitoring) recovering from hip replacement (RTM — PT adherence tracking), or a diabetic patient (RPM — glucose monitoring) undergoing physical therapy for chronic shoulder pain (RTM — exercise adherence and pain tracking).
FAQ
Common questions.
Can RPM and RTM be billed for the same patient?
Yes, but only for different conditions. CMS does not allow RPM and RTM billing for the same condition in the same month. If a patient has hypertension (RPM) and is undergoing musculoskeletal rehab (RTM), concurrent billing is permitted because the conditions are distinct.
How much revenue can RPM + RTM generate combined?
Estimated combined revenue reaches $280–390+ per patient per month — the highest of any two-program combination. RPM contributes ~$160–220 (99453, 99454, 99457, 99458) and RTM contributes ~$120–170 (98975, 98976/98977, 98980, 98981). Both programs include device/data supply and clinical review components.
What is the most common RPM + RTM patient scenario?
The most common scenario is a patient with a chronic cardiovascular condition (hypertension or heart failure) managed via RPM blood pressure or weight monitoring, who is also undergoing physical therapy or musculoskeletal rehabilitation monitored via RTM therapy adherence tracking. Orthopedic post-surgical patients with pre-existing chronic conditions are natural dual-enrollment candidates.
Can the same clinical staff manage both RPM and RTM?
RPM can be managed by physicians and qualified clinical staff. RTM has a broader scope — physicians, physical therapists (PTs), occupational therapists (OTs), and speech-language pathologists (SLPs) can furnish RTM services. In practice, the clinical staff managing each program may differ based on the condition being monitored.
Do RPM and RTM both require 16 days of data transmission?
Yes. Both RPM (99454) and RTM (98976/98977) require data collection or transmission on at least 16 days within a 30-day period. For RPM this means 16 days of physiologic device readings. For RTM this means 16 days of therapeutic data collection, which can include app-based surveys, therapy logs, or digital tool interactions.
Quick Answer
The short version.
Yes, RPM and RTM can be billed together for the same patient — but only for different conditions. CMS prohibits billing both programs for the same condition in the same month. When properly applied to separate conditions, this combination produces the highest estimated two-program revenue at $280–390+ per patient per month. A common scenario pairs RPM blood pressure monitoring for hypertension with RTM therapy adherence tracking for musculoskeletal rehabilitation.
More Comparisons
Also compare.
CCM vs RPM
Compare Chronic Care Management (CCM) and Remote Patient Monitoring (RPM): billing codes, patient eligibility, reimbursement, and when to use each.
CGM vs Glucose Meter
Compare continuous glucose monitors (CGMs) and traditional glucose meters for remote patient monitoring: data frequency, cost, patient experience, and clinical use cases.
Facility EHR vs Practice EHR
Compare facility EHRs (PointClickCare, ALIS) with practice EHRs (athenahealth, Epic) for RPM integration: workflows, data flow, and implementation considerations.
RPM vs RTM
Compare Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM): CPT codes, eligible conditions, device requirements, and when to use each program.
BHI vs CCM
Compare Behavioral Health Integration (BHI) and Chronic Care Management (CCM): eligibility, billing codes, clinical workflows, and when to combine both programs.
RPM + CCM
Learn how to combine RPM and CCM for the same patient to maximize revenue and clinical outcomes. Requirements, billing rules, and implementation best practices.
RPM + BHI
RPM + BHI combined stacking for patients with chronic physical and behavioral health conditions. Billing rules, revenue potential, and compliance guidance.
CCM + BHI
CCM + BHI combined stacking for patients with chronic physical and behavioral health conditions. Billing requirements and revenue potential.
RPM + PCM
Learn how to combine RPM and PCM for patients with a single complex chronic condition. Billing rules, revenue stacking, and key difference from CCM.
CCM + RTM
CCM + RTM combined stacking for the same patient. Billing rules, revenue estimates, eligible patient profiles, and compliance requirements.
CCM + PCM
CCM and PCM cannot be billed for the same patient in the same month. Why they are mutually exclusive, how to choose, and when to switch.
BHI + RTM
BHI + RTM combined stacking for the same patient. Billing rules, revenue estimates, and implementation guidance for behavioral and therapeutic care.
PCM + RTM
Learn how to combine Principal Care Management (PCM) and Remote Therapeutic Monitoring (RTM) for the same patient. Billing rules, eligible conditions, revenue estimates, and implementation best practices.
Cellular vs Bluetooth
Compare cellular and Bluetooth blood pressure monitors for remote patient monitoring: data reliability, patient experience, connectivity, and clinical outcomes.
Contactless (Radar) vs Wearable Devices
Compare radar-based contactless monitoring with traditional wearable RPM devices: patient experience, data types, compliance, and ideal care settings.