RPM vs RTM: The Complete Guide for Healthcare Operators in 2026
March 16, 2026 · Mallard Research
Two programs, one common mistake
Remote Physiologic Monitoring and Remote Therapeutic Monitoring are distinct programs with overlapping names, adjacent billing codes, and very different clinical and operational requirements. Operators who treat them as interchangeable make costly errors: wrong device categories, wrong provider types, wrong CPT codes, and wrong documentation. Operators who understand the boundary between them can build programs that serve a broader patient population and stack multiple reimbursement streams correctly.
This guide covers everything: what each program is, who can bill it, what the 2026 CMS rule changes actually mean, how the codes work together, and where state-level rules diverge from federal baselines.
What RPM is
Remote Physiologic Monitoring (RPM) collects physiological data from patients outside of traditional clinical settings. The data types are specific: blood pressure, heart rate, blood glucose, oxygen saturation (SpO2), and body weight. These are objective measurements of the body's physical state, transmitted automatically from FDA-cleared devices to a monitoring platform where clinical staff review them and respond.
The FDA clearance requirement is not administrative formality. It defines the entire category. A consumer fitness tracker, even one that measures heart rate with high accuracy, does not qualify for RPM billing. The device must be FDA-cleared as a medical device under 21 CFR Part 880 or equivalent. This requirement excludes consumer wellness hardware entirely and constrains program design toward clinical-grade connected devices.
Data transmission must be automatic. CMS requires that RPM data be collected and transmitted by the device itself, without patient action beyond using the device. A patient who manually enters their blood pressure reading into a portal is not generating RPM-eligible data.
Clinically, RPM is designed for chronic disease management at scale. The conditions with the strongest evidence base and the widest deployment are congestive heart failure, type 2 diabetes, chronic obstructive pulmonary disease, and hypertension. These are conditions where daily physiologic variation is clinically meaningful, where decompensation can be caught early through remote data, and where early intervention reduces hospitalizations. RPM also applies to post-surgical monitoring, particularly in cardiovascular and orthopedic procedures where the first two weeks after discharge carry significant readmission risk.
Who can bill RPM: Physicians, nurse practitioners, and physician assistants. Licensed clinical social workers, physical therapists, occupational therapists, and speech-language pathologists cannot independently bill RPM codes. The billing provider must have an established relationship with the patient, meaning an RPM enrollment requires a clinical visit or telehealth encounter that establishes the monitoring plan.
RPM codes fall within the Evaluation and Management family. CPT 99453 covers initial device setup and patient education. CPT 99445 and 99454 cover device supply across short and standard monitoring periods. CPT 99470, 99457, and 99458 cover treatment management time.
What RTM is
Remote Therapeutic Monitoring (RTM) collects non-physiological therapeutic data. The data types include medication adherence, self-reported pain levels, mobility and functional status, therapy exercise compliance, and cognitive behavioral therapy (CBT) engagement. These are not objective physiologic measurements. They capture how a patient is responding to a therapeutic intervention.
The non-physiological definition has two important structural consequences.
First, self-reporting is permitted. A patient who logs their pain level each morning in a secure portal, reports whether they completed their home exercise program, or completes a PHQ-9 between therapy sessions is generating RTM-eligible data. The data does not need to be collected automatically by a device. This makes RTM accessible through software applications and patient-facing portals that do not require FDA-cleared hardware.
Second, the technology category is broader. RTM is compatible with Software as a Medical Device (SaMD): applications and digital therapeutics that meet FDA's software guidance without constituting physical hardware. A mobile application used for CBT or medication adherence tracking can anchor an RTM program. This dramatically lowers the capital cost of program launch compared to RPM, where every enrolled patient requires a physical device.
Clinical scope: RTM is organized around three domains. Respiratory therapeutic monitoring covers patients with asthma, COPD, and related conditions who are tracking inhaler adherence and symptom patterns. Musculoskeletal monitoring covers orthopedic, sports medicine, and physical rehabilitation patients tracking mobility, function, and exercise compliance. Cognitive and behavioral monitoring covers CBT-based programs, including behavioral health integration and mental health therapeutic protocols.
Who can bill RTM: RTM was designed with explicit breadth. Physicians, NPs, and PAs can bill RTM. So can physical therapists, occupational therapists, speech-language pathologists, and licensed clinical psychologists. This expanded provider eligibility reflects the therapeutic rather than physiologic nature of the data.
When therapists bill RTM, the rules change in a meaningful way. CMS classifies therapist-billed RTM as "always therapy," which triggers additional requirements: a written plan of care, therapy modifiers (GP for physical therapy, GO for occupational therapy, GN for speech-language pathology), and Multiple Procedure Payment Reduction (MPPR) rules. Multiple Procedure Payment Reduction applies a 50% reduction to the practice expense component of additional services billed in the same session. Operators building RTM programs that route through PT or OT practices need to account for this in revenue modeling.
RTM codes parallel the RPM family. CPT 98975 covers initial device setup. The device supply codes split by domain: 98976 and 98984 for respiratory, 98977 and 98985 for musculoskeletal, 98978 and 98986 for CBT. Management time codes are 98979, 98980, and 98981.
The 2026 CMS rule changes
The CY 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F), effective January 1, 2026, made structural changes to both RPM and RTM billing that are material to program economics.
Why the old thresholds failed
Before 2026, the core device supply codes for both RPM and RTM required patients to transmit data on at least 16 of every 30 calendar days. Management time codes required a minimum of 20 documented minutes of clinical interaction per month.
This created a binary billing structure. Either a patient crossed both thresholds in a given month, or the practice collected nothing while absorbing the full cost of hardware, connectivity, software licensing, and clinical labor. Two patient categories were structurally excluded:
Patients with inconsistent adherence. A diabetic patient who monitored for 12 days and then stopped transmitting produced a zero-revenue outcome for the practice, regardless of the clinical time spent reviewing data, placing calls, and managing alerts during those 12 days.
Short-duration clinical use cases. Post-discharge monitoring after a joint replacement. Blood pressure surveillance during a medication titration. Respiratory assessment following a COPD exacerbation. Monitoring a gestational hypertension patient between prenatal appointments. None of these generated RPM or RTM revenue under the old structure. The code design assumed chronic long-term monitoring only.
CMS received sustained feedback from health systems, physician groups, and technology companies about this mismatch. The 2025 AMA CPT Editorial Panel vote to approve new short-duration codes followed by CMS finalization in the November 2025 PFS rule was the direct result.
New device supply codes: short-duration tier
CMS created a new 2-to-15-day tier for device supply, sitting below the existing 16-to-30-day standard tier.
For RPM, CPT 99445 covers device supply when a patient transmits data on 2 to 15 days in a 30-day period. It is mutually exclusive with CPT 99454, the existing 16-day-minimum code. A practice bills one or the other each month, never both.
For RTM, the new short-duration device codes split by domain: CPT 98984 for respiratory (2 to 15 days), CPT 98985 for musculoskeletal (2 to 15 days), and CPT 98986 for CBT (2 to 15 days). Each is mutually exclusive with its long-duration counterpart: 98984 with 98976, 98985 with 98977, and 98986 with 98978.
CMS priced the new RPM short-duration code (99445) at parity with the existing 16-day code (99454). This reflects the agency's acknowledgment that the economics of device deployment are front-loaded. Provisioning a device, shipping it, onboarding the patient, and integrating data feeds costs approximately the same whether the patient transmits for 8 days or 24. Parity pricing is a policy judgment that practices should not be financially penalized for enrolling patients who have legitimate short-duration monitoring needs.
New management time codes: 10-to-19-minute tier
CMS created a parallel lower threshold for treatment management time.
For RPM, CPT 99470 covers management time of 10 to 19 minutes per month. It is mutually exclusive with CPT 99457, the existing first-20-minutes code. A practice bills one or the other, based on actual documented time.
For RTM, CPT 98979 covers management time of 10 to 19 minutes per month, mutually exclusive with CPT 98980.
Before this change, a clinical team that spent 14 minutes reviewing vitals, adjusting a care plan, and placing a check-in call generated no management billing. The work existed. The documentation existed. The clinical value existed. The billing value was zero. CPT 99470 and CPT 98979 capture that work.
Reimbursement parity between tiers
CMS finalized short-duration device codes at rates approximately equal to their long-duration counterparts. The short-duration management codes (99470 and 98979) are priced at roughly half the rate of their 20-minute counterparts, which is proportionate to the time threshold ratio.
CMS also exempted RPM and RTM from the efficiency adjustments applied to procedural services elsewhere in the 2026 rule, signaling that the agency views remote monitoring as an investment in reducing downstream costs rather than a service to be squeezed on valuation.
Full RPM code reference
The following rates are 2026 Medicare national estimates. Actual reimbursement varies by geographic locality, facility setting, and payer.
| Code | Description | Threshold | Est. National Rate | Key Constraints |
|---|---|---|---|---|
| 99453 | Initial device setup and patient education | One-time per episode | ~$21.71 | Once per episode of care |
| 99445 (NEW 2026) | Device supply, short-term | 2-15 transmission days/month | ~$47-52 | Mutually exclusive with 99454 |
| 99454 | Device supply, standard | 16-30 transmission days/month | ~$47-55 | Mutually exclusive with 99445 |
| 99470 (NEW 2026) | Treatment management, brief | 10-19 min/month | ~$26 | Mutually exclusive with 99457 |
| 99457 | Treatment management, standard | First 20 min/month | ~$48-52 | Mutually exclusive with 99470 |
| 99458 | Treatment management, additional | Each additional 20 min | ~$38-41 | Add-on to 99457 only |
Billing notes for RPM:
CPT 99453 is billed once per episode of care, not per calendar year. If a patient disenrolls and re-enrolls after a gap, a new 99453 may be billable for the new episode. If a patient remains continuously enrolled, 99453 is a one-time charge.
CPT 99445 and 99454 require the ordering physician to review the transmitted data. The review and resulting clinical response must be documented.
CPT 99457 requires at least 20 minutes of non-face-to-face time that includes interactive communication with the patient or caregiver. CPT 99458 stacks in increments of 20 additional minutes beyond the first 20.
CPT 99470 is new in 2026 and fills the gap for months where clinical time falls in the 10-to-19-minute range. It does not require interactive communication, though documentation of the clinical activities performed during that time is required.
Full RTM code reference
| Code | Description | Threshold | Est. National Rate | Key Constraints |
|---|---|---|---|---|
| 98975 | Initial device setup and patient education | One-time per episode | ~$21.71 | Once per episode of care |
| 98984 (NEW 2026) | Device supply, respiratory, short-term | 2-15 days/month | ~$40 | Mutually exclusive with 98976 |
| 98976 | Device supply, respiratory, standard | 16-30 days/month | ~$40-43 | Mutually exclusive with 98984 |
| 98985 (NEW 2026) | Device supply, musculoskeletal, short-term | 2-15 days/month | ~$40 | Mutually exclusive with 98977 |
| 98977 | Device supply, musculoskeletal, standard | 16-30 days/month | ~$40 | Mutually exclusive with 98985 |
| 98986 (NEW 2026) | Device supply, CBT, short-term | 2-15 days/month | Pending final valuation | Mutually exclusive with 98978 |
| 98978 | Device supply, CBT, standard | 16-30 days/month | Pending final valuation | Mutually exclusive with 98986 |
| 98979 (NEW 2026) | Treatment management, brief | 10-19 min/month | ~$26-27 | Mutually exclusive with 98980 |
| 98980 | Treatment management, standard | First 20 min/month | ~$53-54 | Mutually exclusive with 98979 |
| 98981 | Treatment management, additional | Each additional 20 min | ~$39-42 | Add-on to 98980 only |
Billing notes for RTM:
CMS placed the new 2026 RTM codes (98984, 98985, 98986, 98979) on the New Technology list with a three-year review period before permanent RVU assignment, scheduled for 2028. Rates for these codes may shift materially when the review concludes. Programs launching in 2026 should model conservatively on these specific codes.
When therapists bill RTM (physical therapists, occupational therapists, speech-language pathologists), therapy modifiers are required: GP for PT, GO for OT, GN for SLP. A plan of care is required. MPPR rules apply when multiple services are billed in the same session.
RTM is billed per domain, not per patient in aggregate. A patient enrolled in both respiratory and musculoskeletal RTM concurrently generates separate device supply codes for each domain (98976 or 98984 for respiratory, 98977 or 98985 for musculoskeletal). The management time codes (98979, 98980, 98981) cover both domains combined and are not billed separately per domain.
When RPM and RTM overlap
RPM and RTM are mutually exclusive for the same patient in the same calendar month. A practice cannot bill both RPM and RTM management codes for a single patient in a single month, even if the patient has qualifying conditions for both programs.
This constraint has practical implications for hybrid program design. A CHF patient recovering from surgery who would benefit from both physiologic monitoring (blood pressure, weight via RPM) and therapeutic monitoring (mobility and exercise compliance via RTM) requires a choice each month about which program generates the management billing. The device supply codes are technically separate (RPM device supply vs RTM device supply), but the management codes cannot both be billed.
The mutual exclusivity applies at the management code level, not at the device supply level. Some programs run both RPM and RTM device deployments simultaneously and select one management code per month based on where clinical time is actually being spent.
Stacking RPM and RTM with other programs
Both RPM and RTM can be billed concurrently with several other CMS care management programs in the same month, provided the clinical time and documented activities are distinct and tracked separately. Double-counting time is a compliance violation and an audit vulnerability.
Chronic Care Management (CCM). CPT 99490 and related CCM codes cover non-complex and complex chronic care management. A patient with diabetes and hypertension can be enrolled in both RPM (for blood pressure and glucose monitoring) and CCM (for medication reconciliation, care planning, and specialist coordination) simultaneously. The combined monthly reimbursement for an engaged patient can exceed $150 per month. The condition is strict documentation of separate clinical activities for each program.
Principal Care Management (PCM). CPT 99424-99427 cover care management for a single complex chronic condition. PCM can run concurrently with RPM or RTM under the same separate-time rules.
Transitional Care Management (TCM). TCM codes (CPT 99495, 99496) cover care management in the 30 days after a hospital or facility discharge. RPM deployed at discharge can be billed alongside TCM, but the clinical activities billed under each must be documented as distinct.
Behavioral Health Integration (BHI). RTM is particularly compatible with BHI programs given the CBT domain codes. CPT 99484 and the Collaborative Care Model codes (CPT 99492-99494) can run alongside RTM. Time cannot be double-counted.
Caregiver Planning and Management (CPM). New in 2026, CPM codes cover caregiver engagement in care planning. CPM can run concurrently with both RPM and RTM under the same distinct-activities requirement.
The key operational requirement across all concurrent billing is time tracking at the individual patient and program level. A clinical note that says "30 minutes spent on care management" does not satisfy the documentation requirements when multiple care management codes are billed in the same month. The notes must show which activities were performed under which program during which time windows.
The Telehealth Modernization Act of 2025
The Telehealth Modernization Act of 2025, enacted as part of the Consolidated Appropriations Act, 2026, signed January 22, 2026, extends Medicare telehealth flexibilities through December 31, 2027. The extended flexibilities include geographic restriction waivers allowing telehealth visits from patient homes in non-rural areas, audio-only visit allowances, expanded eligible provider lists including physical and occupational therapists, and FQHC and rural health clinic distant site permissions.
RPM and RTM billing codes are structurally different from telehealth waivers. They are permanent components of the Medicare Physician Fee Schedule, published through notice-and-comment rulemaking, and do not require annual extension. This distinction matters for program infrastructure investment. Programs built on permanent fee schedule authority carry less regulatory risk over a multi-year planning horizon than programs built on waiver-dependent billing modalities.
The 43-day government shutdown in late 2025, during which telehealth waivers lapsed entirely, illustrated the operational risk of waiver dependence. Remote monitoring programs anchored to RPM and RTM CPT codes continued billing through the shutdown without interruption. Programs relying on waiver-based billing for the same patient interactions had no legal authority to bill during that window.
Georgia Medicaid specifics
Georgia's Medicaid program applies more restrictive RPM coverage than the federal Medicare baseline, with several features that affect program design for Georgia-focused operators.
Covered conditions. Georgia Medicaid RPM coverage is explicitly limited to four conditions: congestive heart failure, pediatric asthma, hypertension, and gestational diabetes. RPM for type 2 diabetes, COPD, or any condition outside this list is not covered under Georgia Medicaid. Operators building programs for Georgia Medicaid populations must design patient selection criteria around this condition list, not the broader federal eligibility framework.
Provider enrollment requirements. Georgia Medicaid RPM claims require provider type 08 with specialty codes 085 or 086 in the GAMMIS enrollment system. Claims submitted without these specific enrollment designations are denied. Provider enrollment for RPM must be confirmed before claims are submitted, not after a denial.
Place of service codes. Georgia Medicaid distinguishes between POS 02 (telehealth provided in a facility setting) and POS 10 (telehealth provided at the patient's home). The correct POS code on an RPM claim affects both reimbursement rate and claim adjudication. POS 10 is the appropriate code when the patient uses the monitoring device from home.
RTM status. Georgia Medicaid RTM coverage is restricted and in several domains ambiguous. Operators seeking to build RTM programs for Georgia Medicaid populations should not assume federal RTM eligibility rules translate directly to Georgia coverage. Independent verification of coverage policy for specific RTM codes is required before program enrollment.
BHI coverage. Georgia Medicaid has comparatively strong behavioral health integration coverage, making BHI an accessible concurrent program for Georgia practices serving high-acuity patients with behavioral health comorbidities.
Georgia Pathways to Coverage. The Georgia Pathways to Coverage Medicaid expansion program, which provides coverage for adults meeting work and community engagement requirements, is extended through December 2026. Operators serving populations enrolled through Pathways should verify RPM and RTM eligibility under Pathways-specific coverage policies, as they may differ from standard Georgia Medicaid rules.
Technology implications: FDA-cleared hardware versus SaMD
The technology requirements for RPM and RTM diverge in ways that affect capital requirements, deployment velocity, and scalability.
RPM requires FDA-cleared physical devices for every enrolled patient. Blood pressure cuffs, glucometers, pulse oximeters, and connected scales must each carry FDA clearance as medical devices. This creates per-patient capital costs ranging from $50 to $300 depending on device type and connectivity method (cellular, Bluetooth, Wi-Fi). At scale, device inventory management, shipping logistics, return processing, and battery replacement become significant operational functions.
RTM is compatible with Software as a Medical Device. A CBT application, a medication adherence portal, or a home exercise tracking app that meets FDA's SaMD framework can anchor an RTM program without physical hardware per patient. For musculoskeletal RTM, some programs use connected wearables for objective range-of-motion data, but patient-reported outcomes are explicitly permitted and sufficient for billing purposes.
This asymmetry means RTM programs can be launched at lower initial capital cost and scaled to larger patient populations more quickly than RPM programs. The tradeoff is data objectivity: patient-reported outcomes are inherently less precise than automated physiologic data, and adherence rates for self-reporting programs are typically lower than for automated device transmission.
The rise of SaMD in RTM also creates regulatory complexity. Software that qualifies as a medical device under FDA guidance is subject to FDA oversight, including classification, premarket review requirements for higher-risk functions, and post-market surveillance obligations. An application that is merely a communication tool does not require FDA clearance. An application that provides clinical decision support or analyzes patient data to inform treatment decisions may require it. The line between these categories has been an active area of FDA guidance development, and operators building RTM software solutions should maintain current awareness of FDA's SaMD policy.
The future of remote monitoring programs
Several trends are reshaping remote monitoring beyond the 2026 regulatory baseline.
AI-driven triage and clinical density. As patient panels grow, the clinical bottleneck shifts from data collection to data review. Programs managing thousands of concurrent monitoring patients cannot scale through linear clinical staff additions. AI-assisted alert triage, which filters low-acuity signals and surfaces clinically significant events for provider attention, is becoming a practical requirement for large-scale programs. FDA-cleared AI systems in remote cardiac monitoring have demonstrated measurable reductions in mortality and hospitalization in published outcome data. The financial case is direct: CPT 99470 and 99457 reimburse for clinical management time, and the margin on that time depends on clinical density per staff hour.
Digital therapeutics and RTM. The SaMD pathway creates a route for software-based therapeutic interventions to generate RTM reimbursement. Digital therapeutics that deliver CBT protocols, medication adherence coaching, or guided rehabilitation programs can be structured as RTM programs when they collect therapeutic response data and route it to supervising clinicians. This is an active area of commercial development, and reimbursement policy for specific digital therapeutic products continues to evolve.
Predictive analytics and risk stratification. The clinical value of RPM and RTM data is not limited to real-time alert response. Longitudinal physiologic and therapeutic data from enrolled patients creates a record that supports predictive risk modeling: identifying which patients are at elevated readmission risk before they decompensate, which RTM patients are not engaging sufficiently to benefit from the program, and which CHF patients need an urgent medication adjustment based on weight trend patterns. Programs that extract this predictive value from their monitoring data are using it more fully than programs that treat it as alert-response infrastructure only.
CMS valuation reviews. The new 2026 RTM codes (98984, 98985, 98986, 98979) are on a three-year new technology review with permanent RVU assignment scheduled for 2028. The outcome of that review will be shaped by utilization data, billing patterns, and outcome evidence generated during 2026-2028. Programs that deploy these codes correctly and generate strong documentation of clinical outcomes are contributing to the evidence base that will determine their long-term reimbursement rates.
Summary comparison
| Dimension | RPM | RTM |
|---|---|---|
| Data type | Physiological (BP, HR, glucose, SpO2, weight) | Therapeutic (adherence, pain, mobility, therapy compliance) |
| Data collection | Automatic only | Automatic or patient self-reported |
| Device requirement | FDA-cleared hardware required | SaMD (apps, portals) permitted |
| Clinical domains | Chronic disease, post-acute | Musculoskeletal, respiratory, CBT |
| Billing provider | Physician, NP, PA only | Physician, NP, PA, PT, OT, SLP, psychologist |
| Code family | E/M codes | General medicine codes |
| Short-duration code (NEW 2026) | 99445 (2-15 days) | 98984/98985/98986 (2-15 days) |
| Standard device supply code | 99454 (16-30 days) | 98976/98977/98978 (16-30 days) |
| Brief management code (NEW 2026) | 99470 (10-19 min) | 98979 (10-19 min) |
| Standard management code | 99457 (20+ min) | 98980 (20+ min) |
| Additional management | 99458 (+20 min increments) | 98981 (+20 min increments) |
| Concurrent billing | Can stack with CCM, PCM, TCM, CPM, BHI | Can stack with CCM, PCM, TCM, CPM, BHI |
| RPM/RTM concurrency | Mutually exclusive for same patient same month (management codes) | Mutually exclusive for same patient same month (management codes) |