Remote Therapeutic Monitoring

What it is

Remote Therapeutic Monitoring (RTM) is the collection and interpretation of non-physiologic, therapeutic data — respiratory system status (e.g., peak flow) and medication / therapy adherence and response — from a connected device, with treatment management between visits.

RTM is RPM's therapeutic twin: it bills on the same rolling 30-day cycle anchored to the device-setup date (the 98975 bill date), and is mutually exclusive with RPM for the same patient in the same month. Unlike RPM, RTM may be ordered and billed by a broader set of practitioners (including therapists).

Who qualifies

• Patient has ≥ 1 condition appropriate for therapeutic monitoring (v1: COPD, asthma — respiratory; plus medication-adherence / therapy-response monitoring).
• A connected device of an approved type is assigned (v1: respiratory peak-flow / spirometer).
• Established patient — a prior E/M within ~12 months satisfies CMS.
• Consent captured (verbal or written) with copay disclosure.
• RTM and RPM are mutually exclusive for the same patient in the same month.

Codes & when to bill them

Each billable code, with the requirements that must be on file to bill it.

• 98975RTM setup and patient education on use of the device(s). One-time, billed contemporaneously with enrollment.
  RequirementsOne-time per monitoring episode; device set up and patient educated.
• 98976RTM device supply with scheduled recording / programmed alert transmission to monitor respiratory system, each 30 days.
  Requirements≥ 16 days of device data transmitted within the 30-day cycle.
• 98980RTM treatment management, first 20 minutes of clinical staff/QHP time per calendar month, with interactive communication.
  Requirements≥ 20 min management time in the cycle AND ≥ 1 interactive communication.
• 98981RTM treatment management, each additional 20 minutes (list separately in addition to 98980).
  RequirementsAdd-on to 98980; each additional full 20 min.

Documentation required every cycle

Each 30-day cycle must show:

1. Device certification — device, type, serial on file.
2. ≥ 16 days of device data transmitted within the cycle (gates 98976).
3. Interactive communication log — at least one live (phone/video) interaction with the patient/caregiver in the cycle (gates 98980/98981).
4. Device-data snapshot for the cycle (readings evidence).
5. Patient consent with copay disclosure on file.
6. Billing-provider sign-off.

Built-in patient consentWillowbridge exclusive

Every program ships with compliant, CY-2026 patient consent language — read verbatim into the in-app consent capture flow, captured with date + modality, and version-pinned to each claim, so the consent on file always matches the consent that was billed. No more chasing signatures or re-papering when the rule changes.