Not every important healthcare signal is a vital sign
Remote physiologic monitoring focuses on measurements such as blood pressure, weight, oxygen saturation, or glucose. Many treatment programs need different information: Is the patient following the therapy? Are symptoms improving? Is treatment causing problems? Can the patient complete the prescribed activity?
That is the territory of remote therapeutic monitoring, or RTM.
What is RTM?
RTM is a Medicare coding and care framework for monitoring information related to a patient's therapy and response outside a traditional encounter. Current code descriptors include therapy adherence, therapy response, and digital therapeutic intervention, with device-supply codes for respiratory and musculoskeletal systems among the established categories.
Coverage, eligible professionals, code selection, device requirements, time thresholds, and plan-of-care rules depend on the service and current policy. Organizations should validate them for each program rather than treating RTM as a generic reimbursement label.
RPM and RTM are complementary
| RPM | RTM |
|---|---|
| Physiologic measurements | Therapeutic information |
| Connected medical-device data | Therapy adherence or response data |
| Example: blood pressure | Example: exercise adherence |
| Example: weight | Example: musculoskeletal response |
This is a useful architectural distinction, not a complete billing rule. Exact Medicare requirements differ and evolve.
The shared infrastructure
Both models can use a common operating layer:
Whether the input is a blood-pressure reading or therapy-response information, the platform still needs patient identity, consent, workflow, communication, longitudinal context, clinical rules, provider access, documentation, and analytics.
Engagement is central
RTM is particularly useful where treatment success depends on what happens between appointments. A patient may be asked to complete exercises, use a therapeutic device, follow a care plan, report symptoms, or track response.
Without visibility between visits, clinicians may not know whether a poor outcome reflects the therapy, adherence, tolerance, access barriers, or another issue. Structured digital monitoring can add context, provided that the program avoids overstating what self-reported or device-generated data proves.
AI can help maintain continuity
A governed agent may remind a patient, collect structured feedback, identify missed activities, summarize response, detect a configured exception, or prepare a review packet.
These actions need clear boundaries. The system should distinguish a reminder from clinical advice, preserve the source of each statement, route safety concerns to an approved escalation path, and require human review for clinical decisions.
One remote-care infrastructure
RPM and RTM are different clinical and reimbursement models, but they do not require separate patient experiences. A program may combine remote measurements, therapeutic engagement, telehealth, diagnostics, and medication management.
The patient should not need five disconnected applications simply because healthcare uses five service categories. A shared longitudinal record and workflow layer can keep the experience coherent while preserving the requirements of each service.
From episodic treatment to continuous visibility
Healthcare historically observes the patient during encounters. Digital infrastructure can provide clinically appropriate visibility between encounters, creating opportunities for earlier support and more informed follow-up.
The goal is not continuous surveillance or automated clinical judgment. It is structured continuity: the right information, collected with consent, presented to the right person, at the right time, with an auditable next step.
Primary sources
- 1.Therapy Services and 2026 RTM code updates — Centers for Medicare & Medicaid Services. Accessed 2026-08-24.
- 2.CMS Change Request 14250: RTM code descriptors — Centers for Medicare & Medicaid Services. Accessed 2026-08-24.