RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM 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.
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.”
RTM is used by therapy-driven or condition-specific programs (PT, OT, SLP, orthopedics, pulmonary, and CBT/digital therapeutic workflows).
RTM tracks therapy adherence, symptom/function scores, inhaler use, and digital CBT engagement inside an RTM-eligible device or SaMD.
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.
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.
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.
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.
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 to 30 days), 98984 (2 to 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 to 30 days), 98985 (2 to 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 to 30 days, contractor priced), 98986 (2 to 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. |
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.
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.
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.
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.
A concrete operating model that produces clean claims and a defensible audit trail.
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.
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.
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.
RTM isn't one-size-fits-all. The data captured must be therapeutic and specific to the condition treated.
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.
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.
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.
If you cannot export this packet for a billed month, assume you cannot defend the claim.
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]
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.
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.
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.
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.
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.
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.
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.
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.
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.
Assistant involvement is setting and discipline dependent. Follow your therapy supervision rules and de minimis policies, and confirm MAC guidance for private practice.
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.
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.
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.
Not always emphasized the same way as RPM, but best practice is to obtain and document consent because you are collecting PHI remotely and many payers expect it operationally.
Generally the global package limits what the surgeon can separately bill, but RTM may be billable by a provider not paid under the global fee if it is distinct and properly documented; confirm payer rules.
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.
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 →The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.
Read the RTM Guide →Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.
Read the CCM Guide →The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.
Read the APCM Playbook →