Care teams pair virtual visits with home monitoring every day, so one question keeps coming up: is remote patient monitoring considered telehealth? Sorting out remote patient monitoring vs telehealth matters because Medicare pays for the two under separate authority, with separate rules. Clinically, both models keep patients connected to their care team between office visits. For billing and compliance, they sit in different categories.
This article explains how the Centers for Medicare and Medicaid Services (CMS) classifies each service, what that means for practices in 2026, and how the two work together in a well-run program. It also covers the current remote patient monitoring (RPM) code set, the rules that apply to every claim, and the changes CMS has proposed for 2027.
What Remote Patient Monitoring Is
Remote patient monitoring tracks a patient’s physiologic data outside a clinical setting. Patients use connected devices at home to record blood pressure, weight, blood glucose, pulse oximetry, and other measurements. Those readings transmit to the care team, where clinical staff review trends and respond when a value falls outside an ordered threshold.
The service is built around ongoing data, not a scheduled appointment. Common RPM use cases include hypertension, congestive heart failure, diabetes, and chronic obstructive pulmonary disease (COPD). A patient with heart failure who gains three pounds over two days gives the care team something to act on before symptoms send that patient to the emergency department.
Data collection is continuous, and clinical review happens on the care team’s schedule. That design is exactly why CMS treats RPM differently from a virtual visit.
What Telehealth Covers
Telehealth is a broader category of care delivered through technology. It includes live video appointments, e-consults between clinicians, store-and-forward transmission of images, and audio-only visits in certain circumstances. In each case, the technology stands in for an encounter that would otherwise happen face to face.
In everyday conversation, most clinicians use telehealth as an umbrella term and place remote monitoring under it. That usage is reasonable. It just does not match the definition CMS applies when it pays a claim.
How CMS Classifies RPM and Telehealth Separately
Medicare telehealth is defined in statute, under Section 1834(m) of the Social Security Act. That section covers services ordinarily furnished in person and instead delivered through two-way, interactive telecommunications. Because the authority is statutory, changes to Medicare telehealth policy require action from Congress.
CMS has stated its position on remote monitoring plainly. Services that are inherently non-face-to-face, including care management and remote monitoring, are not ordinarily furnished in person. They fall outside the statutory definition of a Medicare telehealth service and do not appear on the Medicare Telehealth Services List.
So the answer to the original question is no, not in the payment sense. RPM is paid as a care management service under the Physician Fee Schedule, on CMS rulemaking authority rather than the telehealth statute. Providers still describe it as virtual care, and patients experience it that way. The billing pathway is simply its own.
Remote Patient Monitoring vs Telehealth at a Glance
| Remote patient monitoring | Medicare telehealth | |
|---|---|---|
| Legal authority | CMS rulemaking under the Physician Fee Schedule | Section 1834(m) of the Social Security Act |
| Interaction type | Device data plus clinical review and at least one interactive communication per month | Real-time visit that substitutes for an in-person encounter |
| Timing | Continuous data across a 30-day period | Scheduled encounter |
| Geographic limits | None tied to the telehealth statute | Currently waived through December 31, 2027 |
| Typical codes | 99453, 99445, 99454, 99470, 99457, 99458, 99091 | Office and outpatient E/M codes billed with a telehealth place of service |
Why the Distinction Works in Providers’ Favor
The separation between the two categories gives RPM programs a steadier footing. Telehealth flexibilities have run on short extensions for years. They lapsed on October 1, 2025, then returned retroactively when Congress passed a continuing resolution in November 2025. The Consolidated Appropriations Act, 2026, signed February 3, 2026, extended the major flexibilities through December 31, 2027, including home as an originating site, no geographic restriction, and an expanded list of eligible practitioners.
Remote patient monitoring was not part of that cliff. Because RPM sits outside Section 1834(m), the geographic and originating site rules that govern telehealth never applied to it. A patient in a dense suburb qualifies for RPM on the same terms as a patient in a rural county. Practices that built monitoring programs kept billing them through the 2025 lapse while telehealth claims were held.
For care teams, that stability is practical. Chronic condition management depends on continuity, and patients enrolled in monitoring should not have their care interrupted by a legislative calendar.
The 2026 Remote Patient Monitoring Code Set
CMS finalized changes to the remote monitoring code family in the CY 2026 Physician Fee Schedule final rule, effective January 1, 2026. Two new RPM codes joined the set, both aimed at shorter monitoring periods and shorter management time.
- 99453: initial device setup and patient education, billed once per episode of care.
- 99445 (new for 2026): device supply with daily recording or alert transmission, 2 to 15 days in a 30-day period.
- 99454: device supply with daily recording or alert transmission, 16 to 30 days in a 30-day period.
- 99470 (new for 2026): treatment management time of 10 to 19 minutes in a calendar month, with at least one interactive communication.
- 99457: first 20 minutes of treatment management time in a calendar month, with at least one interactive communication.
- 99458: each additional 20 minutes of treatment management time.
- 99091: collection and interpretation of physiologic data, 30 minutes or more per 30 days.
The 2026 additions matter clinically as much as financially. Before 99445 and 99470, a patient who transmitted 12 days of readings produced no billable device code, even though the care team reviewed the data and acted on it. Shorter thresholds mean programs can support patients who are still building a routine instead of dropping them for falling short of 16 days.
Remote therapeutic monitoring (RTM) gained parallel flexibility in the same rule, with new codes 98984, 98985, 98986, and 98979 describing shorter monitoring windows and a 10-minute management increment. For a fuller breakdown of rates and claim mechanics, see our guide to remote patient monitoring reimbursement.
This material is provided for general informational and educational purposes only and does not constitute legal, compliance, billing, coding, or reimbursement advice. CPT® codes, descriptions, and Medicare payment rates referenced here are drawn from publicly available sources, are subject to change, and may vary by payer, locality, and patient circumstances. Tenovi makes no representation or guarantee regarding coverage, payment, or the appropriateness of any code for a particular patient or service, and any presented are illustrative only. Providers are solely responsible for independently determining medical necessity and applicable coding, coverage, documentation, and billing requirements and for submitting accurate claims. Consult applicable payer guidance and qualified billing, coding, compliance, or legal professionals before making billing decisions. CPT® is a registered trademark of the American Medical Association.
What Practices Still Need for Compliant RPM
Falling outside the telehealth statute does not mean RPM has fewer requirements. It has its own, and they are specific.
- An established patient relationship. CMS ended the pandemic-era allowance for new patients, so RPM is billable for established patients. The visit that establishes the relationship may be in person or conducted by telehealth.
- A physician order and documented patient consent. Consent is recorded once and kept in the chart.
- Medical necessity tied to a condition. The monitoring plan should show what is being tracked and why.
- A device that meets the FDA definition of a medical device. Readings must be recorded and transmitted automatically, not entered by hand.
- Days of data that match the code billed. Two to 15 days supports 99445, and 16 or more supports 99454.
- Time logs and at least one interactive communication. Management codes require documented clinical time and live contact with the patient or caregiver during the month.
Practices should also watch the CY 2027 Physician Fee Schedule proposed rule, released July 14, 2026. CMS proposed limiting RTM to established patients, requiring a separately reportable initiating visit before RPM or RTM begins, and paying only when the services are furnished by clinical staff employed by the practice. CMS also asked for comment on replacing the 17 current RPM and RTM CPT codes with four bundled HCPCS G-codes. None of that is final, and the comment record will shape it, but partners and practices should plan for tighter documentation.
How Care Teams Use RPM and Telehealth Together
In practice, the two services complement each other. Device data shows what is happening between visits, and a virtual visit gives the clinician a place to discuss it. A patient with uncontrolled hypertension might submit daily blood pressure readings, then join a video visit two weeks later to review a medication change against the trend line.
That combination is what patients notice. Fewer trips for a reading that a home cuff could capture, earlier intervention when numbers drift, and a care team that already has the data before the appointment starts. Programs that catch problems early tend to reduce avoidable admissions, which is where cost savings come from in the first place.
Billing the two correctly is a documentation exercise. RPM codes and telehealth E/M visits are separately payable when each service meets its own requirements, and clinical time counted toward one cannot be counted toward the other.
Frequently Asked Questions
1) Is remote patient monitoring considered telehealth by CMS?
No. CMS considers remote monitoring an inherently non-face-to-face service, so it falls outside the statutory telehealth definition in Section 1834(m) and does not appear on the Medicare Telehealth Services List. It is paid as a care management service under the Physician Fee Schedule instead.
2) Does remote patient monitoring require a live video visit?
No. RPM requires automatic transmission of physiologic data and, for the management codes, at least one interactive communication with the patient or caregiver during the calendar month. That communication can be a phone call. Video is optional.
3) Do Medicare telehealth expiration dates affect RPM billing?
They do not. The geographic and originating site rules that expire and get extended apply to Section 1834(m) telehealth services. RPM sits outside that section, so monitoring programs continued through the 2025 lapse while telehealth claims were held.
4) Can a practice bill RPM and a telehealth visit in the same month?
Yes, when each service independently meets its requirements and the documentation supports both. Clinical time applied to an RPM management code cannot also be counted toward the visit. Payer policies vary, so confirm rules with each plan.
5) Does a patient need an in-person visit before starting RPM?
Medicare requires an established patient relationship, and that relationship can be established in person or through a telehealth visit. For CY 2027, CMS has proposed requiring a separately reportable initiating visit before RPM or RTM begins, which would tighten the current standard if finalized.
6) What is the difference between RPM and RTM?
RPM covers physiologic data such as blood pressure, weight, and blood glucose. RTM covers non-physiologic data such as therapy adherence and response, including musculoskeletal, respiratory, and cognitive behavioral therapy monitoring. The two use separate code families and cannot be billed for the same patient in the same period.
Understanding Whether Remote Patient Monitoring Is Considered Telehealth
Remote patient monitoring and telehealth both deliver care to patients where they live, and most clinicians reasonably group them together. CMS does not. Telehealth is defined in statute and depends on periodic action from Congress, while RPM is paid as a care management service under CMS rulemaking and carries no geographic limits. That difference gives monitoring programs a stable footing, and it also means RPM has its own requirements: an established patient, an order and documented consent, an FDA-defined device with automatic transmission, days of data matching the code billed, and documented clinical time with at least one interactive communication each month. The 2026 code set added shorter thresholds through 99445 and 99470, and the CY 2027 proposed rule signals closer attention to who furnishes the service and how it is documented.
Tenovi builds the cellular-connected devices and data infrastructure behind remote patient monitoring programs. The Tenovi Gateway collects readings from FDA-cleared devices in the patient’s home with no app, Wi-Fi setup, or Bluetooth pairing, and delivers that data to our partners’ platforms through a single API. If you are evaluating how to launch or scale an RPM program, contact us for a free demo and consultation.
