RTM CPT Codes and Billing Guide: What Practices Need to Know

What RTM is intended to cover

RTM is built for monitoring therapy response, therapy adherence, and non-physiologic treatment data in ongoing care. It is commonly discussed in musculoskeletal and respiratory workflows, but the operational logic is broader: if you are tracking how the patient is responding to treatment over time, RTM is often the more natural fit than RPM.

That is why so many buyers compare the two pathways. If you need the side-by-side framing first, start with Sensor Bio’s posts on remote therapeutic monitoring and remote patient monitoring.

The core RTM CPT code family

The RTM code set is easiest to understand in two blocks: onboarding and device supply, then treatment management.

Onboarding and setup

• 98975: initial setup and patient education on the use of equipment.

Operationally, this is the code that supports program launch. The chart should show that the patient was onboarded, educated, and equipped to participate.

Device supply and monitoring

• 98976: device supply for respiratory system monitoring, billed in monthly cycles.
• 98977: device supply for musculoskeletal system monitoring, billed in monthly cycles.

These are the codes most practices think about first, because they represent the recurring monitoring infrastructure. They depend on more than simply having an app installed. The documentation has to support a real monitored service tied to treatment response.

Treatment management

• 98980: RTM treatment management services, first 20 minutes in a calendar month, with at least one interactive communication with the patient or caregiver.
• 98981: each additional 20 minutes of RTM treatment management in that month.

This is where teams often leave money on the table. They collect data, but no one is capturing time, documenting management work, or recording the interactive communication requirement clearly enough.

2026 code expansion for therapy settings

CMS’s 2026 therapy-services update added 98979, 98984, and 98985 as RTM services designated as sometimes therapy [2]. For therapy-led programs, that change matters because it shows CMS is still maturing the RTM reimbursement framework rather than treating it as a side experiment.

Just as important, the 2026 CMS therapy page explicitly notes that 98979, 98984, and 98985 were added to the therapy code list while descriptors for existing RTM codes 98976 and 98977 were revised [2]. That is a useful signal for administrators: code policy around RTM is still evolving, so compliance teams should review annual updates instead of assuming last year’s cheat sheet is still enough.

The simplest way to think about RTM billing

A clean RTM claim model usually has four layers:

1. A medically necessary treatment plan
2. A documented setup and education event
3. A recurring monitoring stream tied to treatment response
4. Clinician time spent reviewing and managing the patient, including interactive communication where required

If any one of those layers is weak, billing gets brittle fast.

Documentation requirements that make or break RTM claims

1. Medical necessity must be explicit

Do not assume the diagnosis alone explains the program. The note should make clear why remote therapeutic monitoring is being ordered and what treatment question it is meant to answer.

Good documentation answers:

• What condition is being treated?
• What therapy or intervention is being monitored?
• Which patient-reported or device-derived signals will be reviewed?
• How will those signals affect the care plan?

2. The treatment plan has to be visible

This is not just a technology deployment. It is a treatment-response workflow. The chart should show the therapy or management plan the monitoring supports.

3. Setup and patient education should be traceable

If you bill setup, the record should show that setup actually happened. Include:

• date of onboarding,
• education provided,
• device or platform activated,
• patient understanding or successful use confirmation.

4. Monthly monitoring data should be attributable to the patient and date range

The record should show what was monitored during the month and how the team reviewed it. If a platform generates adherence, symptom, or response summaries, those need to be tied back to the patient’s plan of care.

5. Treatment management time must be logged

For 98980 and 98981, vague statements like “reviewed dashboard” are not enough. Use defensible time logs that identify:

• who performed the work,
• what was reviewed,
• what management decision followed,
• the cumulative time in that month,
• when the interactive communication occurred.

6. Interactive communication cannot be an afterthought

When the code requires interactive communication, chart it clearly. Date, modality, subject discussed, and resulting plan change should all be easy to find.

Reimbursement: how practices should think about payment

Here is the uncomfortable truth: there is no single national RTM reimbursement number you should hard-code into a forecast spreadsheet and forget about. Payment varies by year, locality, site of service, and payer.

CMS explains in its Physician Fee Schedule materials that Medicare payment rates are built from RVUs, a conversion factor, and geographic adjustments [1]. That means the right operational move is:

• use the current Medicare Physician Fee Schedule lookup or local MAC resources,
• confirm the exact year’s payment amount,
• separate facility and non-facility assumptions,
• and never rely on a static blog post for final fee schedule decisions.

For forecasting, most practices model RTM revenue as:

• one setup event,
• one monthly monitoring/supply event where applicable,
• one or more treatment-management time blocks.

That framework is more stable than memorizing dollar figures that may change in the next rule cycle.

How high-performing practices close the month for RTM

The practices that bill RTM consistently usually run a formal month-end close process. It tends to include:

• verifying that every active patient still has a documented treatment plan,
• confirming monitoring activity was actually captured during the billing month,
• reconciling platform logs with staff time logs,
• confirming interactive communication occurred where required,
• checking that management notes describe decisions, not just data review,
• holding questionable claims for QA before submission.

That sounds like revenue-cycle housekeeping, and it is. It is also where a lot of RTM margin is won or lost.

The workflow differences between RTM and RPM matter for revenue integrity

This is where strategy meets billing.

RPM is built around connected physiologic monitoring and CMS explicitly says RPM devices must meet the FDA definition of a medical device and digitally upload data [4]. RTM is different. It exists for treatment-response monitoring workflows that often look more like therapy management than classic vital-sign telemetry.

If your organization keeps trying to force every remote care program into RPM, you will usually end up with one of two bad outcomes:

• weak compliance logic, or
• a care model that does not match the code family.

That is why RTM is the commercial home for Sensor Bio’s monitoring story. It matches how many real-world digital therapeutics and response-tracking programs actually function.

Common RTM billing mistakes

Mistake 1: billing technology instead of clinical service

If the documentation only shows that a patient used an app, you do not have a strong RTM claim. The note needs to show monitoring in support of treatment.

Mistake 2: no documented management work

Teams often collect beautiful data and document almost nothing about the decisions made from it.

Mistake 3: weak time capture

Monthly cumulative time should not be reconstructed from memory at month end.

Mistake 4: separating monitoring from the plan of care

RTM should read like part of treatment, not like an unrelated digital add-on.

Mistake 5: unclear patient communication

If interactive communication is required, chart it. Do not assume the platform log speaks for itself.

Mistake 6: confusing RPM rules with RTM rules

The two frameworks overlap conceptually, but they are not interchangeable. Train billing, clinical, and product teams on the difference.

Mistake 7: leaving compliance ownership ambiguous

RTM claims touch clinical operations, documentation, product configuration, and revenue cycle. If nobody owns the full workflow, errors hide in the handoffs. The safest model is to give one operational lead responsibility for charting standards, monthly QA, and payer-feedback review.

What a clean RTM operating model looks like

A mature RTM program usually includes:

• clear patient selection criteria,
• standardized onboarding,
• a documented therapy plan,
• monthly monitoring summaries,
• structured time logging,
• clinician review and escalation protocols,
• revenue-cycle QA before claims submission.

This is not glamorous work, but it is what turns a promising pilot into a scalable reimbursement program.

An implementation checklist for the first 90 days

For teams launching RTM from scratch, the first 90 days should focus on operational repeatability more than scale. A sensible checklist includes selecting the target population, standardizing documentation templates, training staff on monthly time capture, validating platform reporting, running a dry billing cycle, and reviewing denials or edits before expanding enrollment.

That early discipline usually pays for itself. It is much easier to scale a clean RTM workflow than to unwind a messy one.

How Sensor Bio should position itself

Sensor Bio’s message here should be direct: we support RTM-compatible monitoring workflows and infrastructure. That is the right positioning for programs centered on longitudinal treatment response, symptom evolution, adherence, and therapy-driven engagement.

It is also the honest positioning.

Trying to stretch that story into RPM would be weaker clinically and riskier commercially. RTM is where the fit is real.

FAQ

What are the main RTM CPT codes?

The core RTM code family typically includes 98975 for setup, 98976 and 98977 for monthly monitoring/device supply categories, and 98980 plus 98981 for treatment-management time [2].

Does RTM require documentation of clinician time?

Yes. For treatment-management services, defensible monthly time capture is essential.

Do I need interactive communication for RTM?

For treatment-management codes such as 98980, at least one interactive communication with the patient or caregiver is a key requirement and should be clearly documented.

Are RTM reimbursement rates fixed nationally?

No. Medicare payment varies by year, locality, site of service, and payer rules. Practices should verify current values through the Physician Fee Schedule and local payer guidance [1].

What changed in 2026 for RTM?

CMS updated its 2026 therapy-services code list to add 98979, 98984, and 98985 as RTM services designated as sometimes therapy [2,3].

References

1. Centers for Medicare & Medicaid Services. Calendar Year (CY) 2024 Medicare Physician Fee Schedule Final Rule. November 2, 2023. https://www.cms.gov/newsroom/fact-sheets/calendar-year-cy-2024-medicare-physician-fee-schedule-final-rule
2. Centers for Medicare & Medicaid Services. Therapy Services. 2026 update referencing RTM code additions 98979, 98984, and 98985. https://www.cms.gov/medicare/coding-billing/therapy-services
3. Centers for Medicare & Medicaid Services. Annual Therapy Update and 2026 Therapy Code List and Dispositions. https://www.cms.gov/medicare/coding-billing/therapy-services/annual-therapy-update
4. Centers for Medicare & Medicaid Services. Remote Patient Monitoring. March 4, 2026. https://www.cms.gov/medicare/coverage/telehealth/remote-patient-monitoring

References

References

1. Centers for Medicare & Medicaid Services. CY 2022 Physician Fee Schedule Final Rule: Remote Therapeutic Monitoring services.
2. Centers for Medicare & Medicaid Services. CY 2024 Physician Fee Schedule Final Rule: care management, RPM, and RTM policy updates.
3. American Medical Association. CPT 2026 Professional Edition: Remote Therapeutic Monitoring code descriptors.
4. American Physical Therapy Association. Remote Therapeutic Monitoring practice and billing guidance.
5. Centers for Medicare & Medicaid Services. Medicare Learning Network guidance on remote monitoring and care management services.