Arizona practices weighing a remote monitoring program often assume "RPM" is a catch-all term covering everything from blood pressure cuffs to physical-therapy adherence tracking. It isn't. Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM) are billed under two separate CPT code families, with different eligible billers, different supervision rules, and a specific Medicare restriction that blocks billing both programs for the same patient in the same calendar month. Understanding which family fits a given patient population is the first decision a practice has to get right before it evaluates any monitoring vendor or builds a billing workflow.
Two Different Data Streams, Two Different Code Families
RPM covers physiologic data — vital-sign-style readings captured by FDA-cleared devices, such as blood pressure, weight, blood glucose, and pulse oximetry. It is billed under CPT codes 99453, 99454, 99457, 99458, and 99091.
RTM covers non-physiologic data — musculoskeletal status, respiratory status, therapy adherence, and therapy response. This can include pain scores, range-of-motion measurements, and medication compliance, and critically, RTM data can be patient-reported rather than device-measured. RTM's core codes are 98975, 98976, 98977, 98980, and 98981, with newer shorter-duration codes (98979, 98984, 98985) filling in gaps for partial-month monitoring.
This distinction determines everything downstream: which specialty naturally owns the program, who on staff can bill for it, and how a practice should evaluate a monitoring platform or billing partner.
The CPT Code Ladder, Side by Side
| Function | RPM Code | RTM Code |
|---|---|---|
| Initial setup & patient education | 99453 | 98975 |
| Device supply, 16+ days of data in 30 days | 99454 | 98976 / 98977 (by system monitored) |
| Device supply, 2–15 days of data (partial month) | — | 98984 / 98985 |
| Treatment management, first 20 minutes | 99457 | 98980 |
| Treatment management, each additional 20 minutes | 99458 | 98981 |
| Physician-only data review, no patient contact required | 99091 | No RTM equivalent |
Both programs share a baseline requirement: a minimum of two days of data transmission within a 30-day period just to bill the setup and device codes at all. The "full" device-supply codes (99454 for RPM; 98976/98977 for RTM) require at least 16 days of transmission in that window — commonly called the 16-day rule. RTM's newer 98984 and 98985 codes exist specifically to let practices bill for patients who transmit data on 2 to 15 days, capturing partial-month monitoring that used to go unbilled entirely.
Who Can Actually Bill Each Code
RPM can be billed by physicians and other qualified healthcare professionals, with clinical staff performing the day-to-day monitoring work incident-to the billing provider under general supervision — meaning the supervising provider does not need to be physically present. CPT 99091 is the one exception in the RPM family: it can only be billed directly by a physician or qualified healthcare professional, not delegated to clinical staff.
RTM shares that same physician/QHP base, but explicitly extends billing eligibility to physical therapists, occupational therapists, and speech-language pathologists. That is a meaningfully wider set of billing practitioners than RPM allows, and it is the practical reason a physical therapy or orthopedic practice often finds RTM the better structural fit even when the condition being monitored looks similar to something RPM would otherwise cover.
General supervision applies broadly across both programs' monitoring and management codes today, but practices building or renewing a monitoring program should track a proposed CMS change for 2027 that would require RPM and RTM monitoring staff to be direct employees of the billing practice — a shift that would end the fully outsourced monitoring-vendor model as it currently operates for many practices.
The Rule That Trips Up New Programs
Same patient, same calendar month: a practice has to pick one program, not both. Medicare does not allow concurrent billing of RPM and RTM codes for the same patient in the same month. For a patient managing both a chronic physiologic condition, such as hypertension, and a musculoskeletal recovery plan, that is a real clinical and billing decision every month — not something a scheduling system should default silently.
The cheapest place to catch this is at enrollment, not at claims submission. Practices that build the RPM-versus-RTM decision into their intake workflow avoid the far more expensive problem of unwinding a denied claim after the monitoring month has already closed.
Choosing Between the Two for ROI
Because RPM and RTM sit in different code families with different billing structures, the return-on-investment math differs by patient population, not simply by which device gets shipped to the patient's home. A cardiology or endocrinology practice tracking blood pressure or glucose trends over time is squarely in RPM territory. A physical therapy, orthopedic, or behavioral-health practice tracking exercise adherence, pain response, or symptom trends is squarely in RTM territory — and RTM's broader list of eligible billing providers means a PT-led practice does not need a supervising physician to touch every claim in the chain.
Practices evaluating monitoring vendors or billing partners for either program should ask directly which code family the platform and its documentation templates are actually built around. Device certification, reporting cadence, and claim documentation requirements differ enough between RPM and RTM that a vendor built primarily for one does not automatically translate to the other.
Match the Code Family to the Data First
RPM and RTM look similar from a distance — both are monthly, device-driven, CPT-coded monitoring programs run largely under general supervision. But the underlying CPT codes, the list of providers who can bill them, and the CMS rule against billing both in the same month diverge enough that treating them as interchangeable is a fast way to generate denied claims. Arizona practices standing up either program should start by matching the code family to the type of data actually being collected, then evaluate monitoring vendors and billing workflows against that choice — not the other way around.