Does Medicare Cover RPM? Coverage, Costs, and CPT Codes
Does Medicare cover RPM? Yes, Medicare has covered remote patient monitoring under Part B since 2018, yet a surprising number of patients and even some clinical staff aren’t aware the benefit exists, let alone how to use it. At RemoteHCS, the team fields this question from patients, caregivers, and care coordinators every single week, and the answer is almost always the same: your Medicare plan covers more than you think.
This article walks through everything you need to know to act on that coverage: who qualifies, what Medicare actually pays for, how the 2026 CPT codes stack together, what patients owe out of pocket, and what documentation needs to be in place before a claim goes out the door.
Does Medicare Cover RPM? Who Qualifies in 2026
CMS covers remote patient monitoring, sometimes called remote physiologic monitoring, for both chronic and acute conditions, which is broader than most people expect. Medicare RPM coverage isn’t tied to a narrow list of diagnoses. Instead, the anchor is medical necessity: the patient has a condition that requires ongoing monitoring, and monitoring at home serves their care plan. Whether that condition is hypertension, heart failure, COPD, diabetes, or a post-surgical recovery situation, the eligibility question is whether monitoring is clinically warranted, not whether the diagnosis appears on an approved list.
The patient eligibility requirements
Three conditions must be in place before RPM billing can begin. First, the patient needs an established relationship with the billing practitioner. CMS reinstated this requirement after the end of the COVID-19 public health emergency, so providers cannot initiate RPM with a brand-new patient they’ve never seen. Second, a practitioner order must be issued and documented in the chart. Third, the device must transmit physiologic data on a minimum number of days within each 30-day period: at least 2 days for the lower-threshold billing code, or 16 or more days for the traditional higher-threshold code.
Medical necessity documentation isn’t a formality. It’s the foundation the entire claim rests on and the first thing an auditor will examine, weak or vague necessity statements are among the most common reasons RPM claims are flagged during review.
What counts as an eligible RPM device
The device must meet the FDA’s definition of a medical device and must digitally transmit data automatically. A patient manually typing readings into a portal does not meet this standard. Qualifying connected devices include blood pressure cuffs, glucometers, pulse oximeters, and weight scales that upload readings without requiring the patient to transcribe anything. The automatic transmission requirement exists because the clinical value of RPM depends on complete, unaltered physiologic data flowing to the care team in real time.
The three RPM service types Medicare actually pays for
Before getting into specific codes, it helps to understand that Medicare organizes RPM billing into three distinct service categories. Each category has its own code, its own billing threshold, and its own documentation requirements. Understanding the three categories first makes the code breakdown significantly easier to follow.
Device setup and patient education
This covers the one-time onboarding at the start of an RPM episode, including setting up the connected device and training the patient or caregiver to use it correctly. It is billed once at the start of the monitoring relationship, not repeatedly each month. The documentation for this component needs to include the date training was provided and who received it, whether that was the patient, a spouse, or another caregiver.
Ongoing device supply and data transmission
This is the monthly component that covers the device itself and the ongoing transmission of physiologic readings to the care team. CMS uses a two-tier threshold structure here. The traditional higher-threshold code applies when the patient transmits readings on 16 or more days in a 30-day period. A lower-threshold code, added by CMS for 2026, covers patients who transmit on 2 to 15 days, recognizing that consistent daily adherence isn’t always realistic for every patient population.
Clinical treatment management time
This is the time a licensed clinician or care team member spends reviewing transmitted data, identifying changes in the patient’s condition, and communicating with the patient or caregiver. It is billed on a time basis each calendar month. Only one practitioner bills RPM management for a given patient in a given 30-day period, so care team coordination matters when multiple providers are involved in a patient’s chronic care.
Does Medicare Cover RPM? 2026 CPT Codes and Reimbursement Rates
Four CPT codes make up the core RPM billing structure under Medicare Part B. A typical RPM month combines 99454 for the device supply component with 99457 for the first block of management time. For patients with more complex needs who require additional clinician attention, 99458 is added for each extra 20-minute block. The initial setup code, 99453, is billed once at the start of the monitoring episode.
Code-by-code breakdown: 99453, 99454, 99457, and 99458
| CPT Code | Service Description | 2026 Medicare Rate |
|---|---|---|
| 99453 | Initial setup and patient education | $21.71 |
| 99454 | Device supply with 16+ days of readings per 30-day period | $52.11 |
| 99457 | Treatment management, first 20 minutes per calendar month | $51.77 |
| 99458 | Each additional 20 minutes of treatment management | $41.42 |
A straightforward RPM month with the core two codes (99454 plus 99457) totals $103.88 in Medicare-approved reimbursement. Add one 99458 for additional management time and that reaches $145.30. These figures represent what Medicare pays; the patient’s cost-sharing comes out of this approved amount, not on top of it.
The 2026 lower-threshold codes to watch
CMS added two new codes effective January 1, 2026: 99445 for device supply when readings are collected on 2 to 15 days in a 30-day period, and 99470 for a shorter clinical management threshold of 10 minutes per month. Based on the 2026 Medicare Physician Fee Schedule, reimbursement rates are approximately $47 to $52 for 99445 and approximately $26 for 99470, though exact figures vary by Medicare Administrative Contractor. Providers should verify these codes and their local rates with their MAC before billing them. These additions reflect CMS’s recognition that lower-adherence patients still benefit from structured monitoring.
Consent and documentation requirements for RPM claims
Medicare billing without solid documentation is a liability, and RPM claims draw real scrutiny. CMS requires that consent be obtained and documented before monitoring services begin. What goes into the chart determines whether a claim holds up or generates an audit finding.
Patient consent: what CMS requires vs. what auditors expect
CMS allows verbal consent documented in the medical record. A signed form is not formally required by CMS policy. In practice, however, Medicare contractor audits have flagged claims where consent documentation was vague or missing entirely. The safest compliance posture is to document consent clearly in the chart with a date and the method of consent, and to retain a signed beneficiary consent form when workflow allows. That written record is much easier to produce during an audit than a verbal notation buried in a progress note.
The audit-ready RPM documentation package
For each RPM patient, maintain the following in the record before submitting claims:
- The practitioner’s RPM order and the diagnosis driving the monitoring
- A statement of medical necessity explaining why RPM is appropriate for this patient
- Device type, FDA clearance status, and setup or delivery date
- Patient education note with the date training was completed and who was trained
- Transmission or data log showing the number of days readings were collected in the period
- Time log and interaction notes for management codes (99457, 99458, 99470)
- Claim elements: CPT code, ICD-10 diagnosis code, date(s) of service, place of service, and billing NPI
Each element in this package maps to a specific audit question. If any element is missing, the claim is vulnerable. Building this documentation into your RPM workflow from day one is far less painful than reconstructing records during an audit response.
What RPM actually costs the patient under Medicare Part B
Patients often assume remote monitoring is an expensive add-on billed separately from their regular care. It isn’t. Under Medicare Part B, RPM follows the same cost-sharing structure as other covered outpatient services. The patient meets the annual Part B deductible (set at $283 for 2026), and after that, Medicare pays 80% of the approved amount while the patient owes the remaining 20% coinsurance.
How the 20% coinsurance applies to RPM services
Using the 99454 rate as a concrete example: the Medicare-approved amount is $52.11, which means the patient’s coinsurance for that component is roughly $10.42 for the month. Add the 99457 management component and the patient’s total coinsurance on a standard RPM month (99454 plus 99457) comes to about $20.78. For most patients who have already met their Part B deductible, a full month of remote monitoring costs less than $25 out of pocket. That’s roughly what most patients pay for a single specialist visit copay, but here it covers a full month of continuous daily monitoring.
When supplemental coverage or Medicaid reduces the patient share
Three common situations bring patient costs to near zero. Medigap or supplemental insurance plans that cover Part B coinsurance will pay the 20% that Original Medicare leaves to the patient. Dual-eligible patients covered by both Medicare and Medicaid often have their Part B cost-sharing covered by Medicaid entirely. Patients with Qualified Medicare Beneficiary (QMB) status typically have Part B cost-sharing eliminated altogether. Patients should check their specific supplemental plan, since commercial plans set their own rules and may handle RPM differently than traditional Medigap policies.
How RPM differs from remote therapeutic monitoring
Remote therapeutic monitoring (RTM) has become a source of genuine confusion because it sounds similar to RPM and shares some billing logic. The distinction matters clinically and financially: the two programs cover different data types, allow different billing practitioners, and cannot be billed simultaneously for the same patient in the same month.
The key clinical and billing differences between RPM and RTM
RPM covers physiologic data, blood pressure, glucose, SpO2, weight, and similar measurements captured automatically by an FDA-cleared connected device. RTM covers non-physiologic and therapy-related data, including pain levels, exercise adherence, respiratory therapy response, and patient-reported outcomes. RTM can also include patient self-reported data, which RPM cannot.
The billing practitioner pool also differs: RPM is billed by physicians and certain non-physician practitioners, while RTM opens billing to physical therapists, occupational therapists, and speech-language pathologists. The two programs use separate CPT code families (RPM: 99453 through 99458; RTM: 98975 through 98981), and CMS does not allow billing the device-supply codes from both programs for the same patient in the same 30-day period.
How to get started with Medicare RPM
Many patients are surprised to find that starting RPM involves fewer steps than they assumed. The provider issues an RPM order, the patient is consented and educated, a connected device is supplied, and the monitoring cycle begins. Physiologic data flows to the care team daily, and a licensed clinician reviews that data and reaches out when readings fall outside the patient’s target range.
For patients managing chronic conditions like hypertension, diabetes, COPD, or heart failure, RemoteHCS is built specifically around this model. The program uses HIPAA-encrypted data transmission, licensed clinicians who review readings daily, and nationwide availability across all 50 states. RemoteHCS is currently preparing to open enrollment, and patients or caregivers who want to get on the waitlist can do so at RemoteHCS.com. If you’re a care coordinator or provider looking to refer patients into a Medicare-compatible RPM program, the same page is the right starting point.
The bottom line on Medicare RPM coverage
If you’ve been asking, “Does Medicare cover RPM?”, the answer is yes, and the coverage is more accessible than most patients realize. Medicare Part B covers remote patient monitoring for a wide range of chronic and acute conditions based on medical necessity, not a limited diagnosis list. For providers, the priority before submitting a first claim is having the documentation structure in place: consent, a clear medical necessity statement, and a verified transmission log. Get those elements right from the start, and RPM becomes a sustainable, audit-resilient part of your chronic care workflow. For patients, the financial barrier is low, typically under $25 per month after the deductible, and often lower still with supplemental coverage. The coverage exists. The next step is using it.
