Remote Therapeutic Monitoring (RTM): Billing, Compliance, and Workflow Guide
A practical reference for running RTM across musculoskeletal, respiratory, and CBT/digital therapeutic programs—code selection, therapy modifiers, supervision rules, documentation requirements, and 2026 code changes.
How to use this page: Treat this as operational guidance and documentation checklists (not legal advice). Confirm payer-specific coverage, modifiers, and contractor pricing before scaling.
One-page summary
Overview
RTM is used to monitor therapeutic adherence and response between visits—home exercise completion, pain/function scores, inhaler adherence, CBT homework and symptom logs. Unlike RPM, RTM can include patient self-reported data, but the data must live inside an FDA-defined medical device or qualified software as a medical device (SaMD) with exportable timestamps.
This page is structured as an operator reference: how to classify an episode (therapy vs non-therapy), select device codes based on day thresholds, document time and live interaction for management, and assemble an audit-ready “RTM packet.”
Section index / navigation map
- RTM vs RPM: scope and mutual exclusion
- What counts as RTM data of record
- 16-day rule and short-duration options
- Code map (baseline + 2026 changes)
- “Sometimes therapy” routing and modifiers
- Workflow playbook (enroll → monitor → bill → offboard)
- Documentation & audit packet checklist
- Payer coverage variability and controls
- Common denials and appeals posture
Key takeaways
- RTM and RPM are mutually exclusive for the same patient in the same 30-day period.
- Device supply coding is a day-threshold selection problem (full-month vs short-duration).
- Management coding is a time + live interaction requirement; asynchronous messages do not satisfy the interaction requirement.
- CBT/digital therapeutic device supply is often payer- and MAC-dependent; confirm coverage before forecasting.
- “Sometimes therapy” is the most common operational failure mode: wrong modifier, missing plan of care, or wrong setting assumptions.
- General supervision rules make physician-led RTM scalable, but therapist billing follows therapy supervision/assistant rules.
- Audit strength comes from an assembled packet: order/medical necessity, device details, day counts, time logs, and interaction note content.
RTM vs. RPM: Scope, Data Type, and Mutual Exclusion
RTM focuses on therapeutic adherence and response (musculoskeletal rehab, respiratory adherence, CBT/digital therapeutics). It can use patient-reported data, but the data must be captured inside an FDA-defined medical device or qualified SaMD. RPM is limited to automatically collected physiologic data (blood pressure, SpO₂, weight). You cannot bill RTM and RPM together for the same patient in the same 30-day period.
Scope
RTM is used by therapy-driven or condition-specific programs (PT, OT, SLP, orthopedics, pulmonary, and CBT/digital therapeutic workflows).
Data type
RTM tracks therapy adherence, symptom/function scores, inhaler use, and digital CBT engagement inside an RTM-eligible device or SaMD.
Mutual exclusion
Only one remote monitoring family (RTM or RPM) can be billed per patient per 30-day period, even if multiple devices or conditions are involved.
RTM CBT device supply (CPT 98978) is contractor-priced by Medicare; coverage and rates for CBT-focused RTM vary by MAC and commercial payer.
RTM Data of Record: What Counts and What Does Not
- RTM can include subjective patient inputs (pain scores, adherence logs, CBT homework), but the data must be captured inside an RTM eligible device or SaMD with timestamped records you can export.
- SMS and voice prompts are fine as nudges, but texts or emails are not the medical device record. The medical device record is the app or device system that stores the data.
- Software only RTM: perform SaMD diligence (device identification, FDA definition alignment, BAA coverage, exportable day counts, and audit retention).
- CBT device codes are contractor priced and payer dependent; require explicit coverage verification before forecasting.
SaMD diligence checklist (software-only RTM)
- Device identity: name the app/device in the chart and in your internal billing packet.
- FDA definition alignment: document why it qualifies as a medical device (avoid generic wellness tools).
- Security: confirm HIPAA controls and a BAA with the vendor.
- Auditability: exportable day-count report with timestamps for the billed period.
- Retention: ensure you can retain/export the record for audit timelines (not just a live dashboard).
The 16-Day Rule — and What 2026 Actually Changes
- Device supply codes in the 16-30 day tier require 16 days of recorded data in the 30-day period.
- 2026 adds an explicit 2-15 day tier (98984 to 98986). The 16 day threshold does not disappear; it becomes a tier selection problem.
- Management codes do not require 16 days, but operators should treat months with very low data as medically fragile and document why management was needed.
Operator note: handle partial cycles explicitly (new enrollments, discontinuations, device failures). Your billing workflow should record the monitoring start date, the counted data days, and the selected device code tier for that cycle.
RTM Codes and Requirements: 2025 Baseline
Setup & Education · 98975
One time per episode of care. Covers initial configuration and patient education. Operational rule: bill only after the patient has generated at least knowable, auditable device days for the episode. In Medicare baseline guidance, treat 98975 like other RTM device family requirements and do not bill it until you can produce a 16 day usage report for the monitoring period. Practical operations: hold 98975 until day 17 so you are not forced to rebill or retract if the patient stalls at day 15.
Device Supply · 98976–98978
Monthly device supply. For the full reimbursement rate, 98976 (respiratory) and 98977 (MSK) require 16+ days of data. However, new "rescue codes" (98984–98986) now allow you to bill for 2–15 days of monitoring if the full threshold is missed.
Treatment Management · 98980–98981
Monthly RTM treatment-management time. 98980 covers the first 20+ minutes in a calendar month (with at least one real-time interaction), and 98981 covers each additional 20 minutes. The 16-day device rule does not apply to these management codes, but you still need legitimate RTM data and documented interaction.
| Category | Code(s) | Threshold | Hard requirement | Notes (what auditors check) |
|---|---|---|---|---|
| Setup and education | 98975 | Once per episode | Hold until device day evidence is present (baseline: treat as 16 day aligned) | Episode definition, device day audit trail, and documented patient education. |
| Device supply respiratory | 98976 (16-30 days), 98984 (2-15 days, 2026) | 16–30 days or 2–15 days | Recorded device data days in the 30-day period | Day counts, device identification, and month selection logic. |
| Device supply MSK | 98977 (16-30 days), 98985 (2-15 days, 2026) | 16–30 days or 2–15 days | Recorded device data days in the 30-day period | Day counts, device identification, and coverage alignment. |
| Device supply CBT | 98978 (16-30 days, contractor priced), 98986 (2-15 days, 2026 contractor priced) | 16–30 days or 2–15 days | Recorded device data days in the 30-day period | SaMD qualification, contractor pricing, and payer coverage checks. |
| Management entry | 98979 (10 to 19 minutes, 2026, requires one real time interaction, cannot be billed with 98980) | 10–19 minutes | One real-time interaction and documented time | Time logs, interaction mode, and mutual exclusion with 98980. |
| Management standard | 98980 (20 minutes, requires one real time interaction) | 20 minutes | One real-time interaction and documented time | Time logs, interaction mode, and data linkage. |
| Management add on | 98981 (each additional 20 minutes, requires documentation of incremental time) | Each additional 20 minutes | Incremental time documentation and additional interactive contact | Incremental time totals and evidence of additional interactive contact. |
Device code selection (per 30-day cycle)
- Confirm the domain: respiratory vs MSK vs CBT (drives device code family).
- Count documented days with data in the cycle.
- Select short-duration (2–15) vs full-duration (16–30) device code.
- Document the day-count report in the monthly billing packet.
RTM cannot be billed in the same period as RPM for the same patient. It can be billed alongside CCM/PCM/TCM/BHI/APCM when time and work are not double-counted.
What Changes in 2026: Shorter Episodes, New Time Buckets
Beginning January 1, 2026, RTM becomes more flexible. CPT and CMS introduce new codes for shorter monitoring periods and shorter management time, instead of a single “16 days or nothing” device threshold and a single 20-minute management bucket.
2–15 Day Device Supply · 98984–98986
New codes for shorter episodes of respiratory, musculoskeletal, and CBT RTM. Financial Insight: Pricing is payer and locality dependent; do not assume parity without confirming the current fee schedule.
New 10–19 Minute Management · 98979
98979 covers 10–19 minutes of RTM management (with one live interaction). Note: You cannot bill 98979 and 98980 in the same month. Use 98979 for "maintenance" patients who require brief check-ins, and 98980 for patients requiring standard 20+ minute review.
In 2026, 98976/98977/98978 are updated to represent 16–30 days of monitoring; 98984/98985/98986 represent 2–15 days. The 16-day requirement does not “go away”--it is joined by a short-duration option.
Operational impact
- Short episodes become billable: build your billing gates so “missed 16 days” routes to the short-duration option instead of a write-off, when appropriate.
- Light-touch months become billable: route 10–19 minute months to the 98979 pathway instead of forcing a 20-minute threshold.
- Documentation must show selection logic: auditors will ask why a code tier was chosen; store the day count and time log with the claim packet.
Sometimes Therapy: Modifier, Plan of Care, and Setting Rules
- RTM is “sometimes therapy.” If furnished as therapy (PT, OT, SLP), it is treated as therapy for billing purposes and requires the appropriate therapy modifier (GP, GO, GN) and an active therapy plan of care with required certifications.
- Physician and NP/PA furnished RTM can still become “therapy coded” when the underlying service is therapy specific (musculoskeletal rehab workflows). Document plan of care linkage rather than trying to route around therapy rules.
- Assistant involvement rules (therapy settings): follow the 10% de minimis concept and the CQ/CO modifier and payment reduction when applicable. Device supply codes are practice expense only and are not impacted the same way as professional time codes.
- Operational gate: if your practice cannot reliably determine whether an RTM episode is “therapy,” you will miscode modifiers and invite denials. Build a routing rule up front.
Who Can Bill RTM and Who Can Do the Work
- Physician, NP, PA can bill RTM and can delegate many tasks to clinical staff under general supervision (post 2023 policy change). The billing provider remains accountable and needs oversight notes.
- PT, OT, SLP can bill RTM within scope, but therapist billing does not use "incident-to" rules the way physician practices do. Keep the rule simple: therapists should assume the therapist and therapy team are the rendering entity and must follow therapy supervision and assistant rules.
- One practitioner per patient per 30-day period: make it a hard operational rule to avoid duplicate billing and denials.
Pharmacy and Clinical Pharmacist Integration in RTM
Pharmacists, as medication experts, can play a key role in RTM — particularly for medication-intensive conditions. While pharmacists cannot independently bill RTM codes under Medicare, they can provide RTM services incident to a billing practitioner.[17]
Medication Adherence Monitoring
Smart pill bottles or apps report whether patients have taken their medication. A pharmacist-run RTM program might enroll patients with respiratory conditions to track inhaler adherence and symptom scores, or patients with musculoskeletal conditions to monitor pain levels and exercise compliance. Pharmacists review reports and follow up with counseling or dose adjustments under collaborative practice agreements, where state law permits.[17]
Respiratory Therapy Monitoring
Smart inhaler attachments track rescue inhaler use vs. controller medication adherence. When data reveals a patient is overusing their rescue inhaler, the pharmacist can intervene with education and alert the physician, potentially prompting a regimen change. Programs like this aim to reduce COPD flare-ups and asthma-related ER visits.[17]
Case Study: Osteoarthritis RTM
A community pharmacy enrolled osteoarthritis patients in an RTM program using an app where patients logged daily pain and activity after starting a new NSAID therapy. One patient's data showed no improvement after two weeks plus reports of stomach upset. The pharmacist consulted the prescriber and they jointly switched the patient to an alternative regimen — avoiding an unnecessary follow-up visit and a potential ulcer. This illustrates RTM's value: real-time tracking of therapy effectiveness lets the care team optimize treatment before complications escalate.[17]
Workflow playbook: enroll → monitor → bill → offboard
A concrete operating model that produces clean claims and a defensible audit trail.
Enrollment & setup
- Classify the episode: therapy vs non-therapy (drives modifiers, plan-of-care, staffing rules).
- Order + medical necessity: record why RTM is needed and what signals will change decisions.
- Consent: document consent to remote monitoring and expected patient responsibilities.
- Device + training: document device/app identity, setup steps, and the education delivered.
In-cycle operations
- Engagement checkpoint: at mid-cycle, intervene if the patient is trending below the day threshold.
- Alert protocol: define what triggers outreach (worsening pain scores, low adherence, rescue inhaler spikes, etc.).
- Time capture: log review time and interaction time as you go; do not reconstruct at month-end.
- Live interaction: schedule at least one synchronous interaction in the month for management codes.
Month-end billing gates
- Device tier selection: store the day count report and select the correct device code tier.
- Management threshold: select the correct time bucket and confirm a live interaction occurred.
- Therapy compliance: modifiers present, plan of care present, assistant involvement rules handled.
- One practitioner rule: confirm no overlapping RTM/RPM billing by another provider.
Offboarding
- Define stopping rules: goals met, non-adherence, or condition stabilized.
- Close the episode: document the discharge rationale and any transitions to other programs.
- Device recovery/licensing: inventory or subscription cleanup and record retention.
How FairPath Helps You Run In-House RTM
Step 1: Capture RTM-Eligible Data
FairPath and our agents prompt patients to record therapy adherence, symptom scores, and other RTM data inside a medical-device-qualified app. Prompts may be delivered by SMS or voice, but the clinical system of record is an RTM-eligible device or SaMD, maintaining alignment with RTM device rules.
Step 2: Accelerate Cash Flow
We count RTM days and treatment management minutes in the background. For 2026, the big operational unlock is that short duration device supply codes (98984 to 98986) let you bill a defensible device month even when the patient does not reach 16 days. Separately, we track when the episode is mature enough to bill setup and education based on your documented device day evidence and payer rules.
Step 3: Produce Clean, Defensible Claims
Our compliance engine encodes RTM-specific rules: day thresholds for device codes, one-practitioner-per-period limits, incident-to rules for physician practices, therapy plan-of-care and de minimis rules for PT/OT/SLP teams, and coordination with RPM and care-management codes to prevent double-counted time. The result is a clear, exportable audit trail for every RTM claim.
Domain-Specific RTM: How it Looks in Practice
RTM isn't one-size-fits-all. The data captured must be therapeutic and specific to the condition treated.
Musculoskeletal
Target: Post-op joint replacement, chronic back pain.
Data Signals: Range of motion (ROM), exercise repetition counts, and pain scores.
Goal: Identify under-performance due to pain or over-activity that risks injury.
Respiratory
Target: Asthma, COPD.
Data Signals: Inhaler usage frequency (adherence), rescue inhaler spikes, and environmental triggers.
Goal: Detect "rescue" overuse early to prevent exacerbations and ER visits.
Cognitive (CBT)
Target: Depression, Anxiety, Insomnia.
Data Signals: Homework completion, mood scoring, sleep logs.
Compliance Alert: Not all health apps qualify. To bill 98978 (or 98986), the software must meet the FDA definition of a medical device (SaMD). Generic "wellness" apps do not qualify.
Documentation & audit packet
If you cannot export this packet for a billed month, assume you cannot defend the claim.
Minimum packet contents
- Order / plan statement: why RTM is medically necessary and what it is intended to change.
- Device identity: name of device/app + why it qualifies as a medical device/SaMD.
- Day-count report: dates with data for the billed cycle (and the selected device code tier).
- Time log: dated entries that sum to the billed management time bucket.
- Live interaction note: date, mode (phone/video), with whom, and the clinical substance.
- Therapy artifacts (when applicable): plan of care, certifications, modifiers, and assistant involvement handling.
Monthly RTM note template (copy/paste)
RTM Episode: [Respiratory | MSK | CBT] | Therapy? [Yes/No]
Device/App: [Name] | Device qualification note: [FDA definition / SaMD rationale]
Monitoring period: [Start date] – [End date]
Data-days recorded: [##] (attach/export day-count report)
Key signals reviewed:
- [Adherence metric]
- [Response metric]
- [Alerts / exceptions]
Interactive communication (required for management codes):
- Date/time: [ ]
- Mode: [Phone | Video]
- With: [Patient | Caregiver]
- Substance: [What was discussed + decisions]
Time log summary (RTM management time only):
- Data review: [##] min
- Patient/caregiver interaction: [##] min
- Care coordination / documentation: [##] min
Total RTM management minutes this month: [##]
Care plan adjustments / next steps:
- [Medication/therapy changes, escalation, follow-up plan]Payer coverage: build a verification gate
Medicare (FFS) and Medicare Advantage
- Medicare baseline payment follows CPT-defined requirements (device, days, minutes, live interaction).
- Medicare Advantage plans may add utilization management (prior auth, vendor preferences, episode limits).
- CBT/digital therapeutic device supply can be MAC- or payer-dependent; verify before scaling.
Commercial and Medicaid
- Commercial coverage is not uniform; build an eligibility + coverage check step before enrollment.
- Some Medicaid programs or MCOs may cover selectively; state and managed-care policies differ.
- If you cannot confirm coverage, document the financial responsibility pathway before the first billed cycle.
Common denials & appeals posture
- Not covered service: Run a coverage check workflow and communicate patient responsibility before enrollment.
- No prior auth (MA and commercial): Add a “verify auth” gate before enrollment.
- Insufficient days or insufficient minutes: No appeal if thresholds are truly missed; fix with gating before claim creation.
- Missing therapy modifiers or missing plan of care: Apply the correct modifier and attach plan of care documentation.
- Provider eligibility mismatch: Correct taxonomy, modifier, and payer system edits.
- Duplicate billing (RTM plus RPM, or two RTM billers): Assign ownership per patient per period.
Appeals posture: if the denial is purely numeric (missed days, missed minutes, missing live interaction), do not expect appeals to succeed. If the denial is policy/eligibility/modifier-related, appeals are often winnable with a complete documentation packet.
RTM Questions, Answered
Can PTs, OTs, and SLPs bill RTM?
Yes. RTM is “sometimes therapy.” Physical Therapists, Occupational Therapists, and Speech-Language Pathologists can bill RTM within their scope when it is delivered under a therapy plan of care. Physicians and other qualified health care professionals can also bill RTM. Use GP/GO/GN modifiers when RTM is provided as therapy under a plan of care, and follow your MAC’s supervision and documentation rules for the setting.
Does RTM require a medical device or can I use any app?
RTM requires that data be captured and transmitted by a medical device as defined by the FDA. That can include software as a medical device (SaMD), such as a qualified RTM app, but generic wellness apps or informal text messages are not sufficient. You can use SMS or voice to nudge patients, but the data of record must be entered into, or generated by, an RTM-eligible device or app that your billing team can name and document.
Do I always need 16 days of data in a 30-day period?
For 2025 device-supply codes 98976/98977 (and 98978 where covered), you generally need at least 16 days of RTM data in a 30-day period to bill. Management codes 98980/98981 do not have a 16-day requirement, but you still need legitimate RTM data and documented interaction.
Beginning in 2026, new codes 98984/98985/98986 allow you to bill for 2–15 days of monitoring, while 98976/98977/98978 are updated to explicitly cover 16–30 days.
What interactive communication is required for RTM management codes?
You must have at least one synchronous, real-time conversation (audio-only telephone or audio-video). Crucial Update: Automated nudges, text messages, AI chat, or portal messages do not count toward the interactive requirement or the clinical labor time.
Can two providers bill RTM for the same patient in the same period?
No. Only one practitioner can bill RTM (or RPM) services for a patient in a given 30-day period, even if multiple clinicians are involved and multiple devices are used. Practices should designate a single billing provider for each patient’s RTM episode and coordinate internally.
Can I bill RTM together with CCM, PCM, BHI, TCM, or APCM?
In many cases, yes. CMS allows RTM or RPM to be billed in the same month as CCM, PCM, TCM, BHI, chronic pain management, and APCM when the time and services are distinct and not counted twice. The key is that you do not use the same minutes or identical activities to support more than one code family. Your documentation should make the dividing lines clear.
Do I need an established patient to start RTM?
No. CMS requires an established relationship for RPM, but not for RTM. RTM services still must be medically reasonable and necessary, and you must be able to show how RTM data is used in the context of the patient’s care, but there is no explicit “established patient” requirement in RTM policy.
How does CBT fit into RTM?
CPT 98978 (and, beginning in 2026, 98986 for 2–15 days) support RTM device supply for cognitive-behavioral therapy–oriented digital therapeutics. These codes are contractor-priced and payer adoption is still evolving. If you provide CBT-aligned digital therapy, confirm your MAC and commercial payer policies before relying on RTM CBT codes in your financial planning.
Can assistants help with RTM workflows?
Assistant involvement is setting and discipline dependent. Follow your therapy supervision rules and de minimis policies, and confirm MAC guidance for private practice.
What documentation do auditors expect for RTM?
Auditors look for: documented patient consent; the specific RTM device or app (and its status as a medical device); the plan of care or episode definition; day-counts for device-supply codes; cumulative treatment-management time logs; dates, times, and modes of interactive communication; and notes showing how RTM data influenced clinical decisions. The more explicitly you connect RTM data to care-plan changes, the stronger your position in an audit.
What exactly changes for RTM in 2026?
For dates of service on or after January 1, 2026, RTM gains new device-supply codes for 2–15 days of monitoring (98984–98986) and a new 10–19 minute treatment-management code (98979). Existing device codes 98976/98977/98978 are revised to clearly represent 16–30 days of RTM in a 30-day period, and 98980/98981 continue to cover longer management time buckets. These changes give you more granular options for short episodes and shorter management engagements, while preserving the ability to bill longer, ongoing programs.
Can I bill RTM for multiple conditions (e.g., Respiratory and MSK)?
Yes, with caveats. You can bill multiple device codes (e.g., 98976 for respiratory and 98977 for MSK) if the patient has distinct medical needs for both. However, you can still only bill one set of management codes (98980/98981) per month, as management time is per-patient, not per-condition. Coordination is key to avoid "duplicate service" denials.
Do I need patient consent for RTM?
Consent is not spelled out for RTM as explicitly as it is for RPM, but you should treat it as required. You are collecting PHI remotely, many payers expect documented consent operationally, and it is one of the first items auditors look for. Obtain it at enrollment and record it in the chart.
Can RTM run during a surgical global period?
It depends on who bills it. The global surgical package limits what the operating surgeon can separately bill during the global period. A provider who is not paid under the global fee — for example, the PT managing post-op rehab — may bill RTM if the service is distinct and properly documented. Confirm the payer's position before relying on this.
References
- CMS Physician Fee Schedule rules and CMS guidance for RTM supervision and billing conditions.
- AMA CPT code descriptors and annual CPT updates (including 2026 additions).
- MAC guidance for contractor-priced behavioral health / digital therapeutic device supply (where applicable).
- Role of RTM in Value-Based Care — Pharmacy integration, case studies, and outcomes data for RTM programs. Source: RoleOfRTMInVBC.md (FairPath docs).
FairPath is designed to handle this complexity for you.
While most platforms simply record what happened, FairPath actively runs the program. It continuously monitors every patient, staff action, and billing rule across CCM, RPM, RTM, and APCM, intervening immediately when a requirement is missed.
This allows you to scale your own program without losing quality, breaking trust with physicians, or losing control of your revenue. We provide the precision of an automated medical director without the chaos.