What is Medicare Reimbursement for Remote Monitoring?

learn about the 2023 Medicare Reimbursement policy for Remote Monitoring

Medicare reimbursement for remote patient monitoring pays care teams for collecting and acting on patient health data between office visits. Remote patient monitoring (RPM) uses connected devices to send readings such as blood pressure, weight, and blood glucose to clinicians. Medicare began paying for the core RPM codes in 2019. The rules have changed almost every year since.

That pace is the reason this guide focuses on how RPM reimbursement works instead of one year’s numbers. The code structure, billing requirements, and update cycle stay fairly stable. Payment amounts do not. Once you understand the framework, you can check current rates in minutes.

The purpose of RPM is proactive, preventive care. A rising blood pressure trend or sudden weight gain can be caught early, before it becomes an emergency visit. Reimbursement exists to support that clinical work. Programs built around patient need also hold up best when payers review them.

Medicare Reimbursement for Remote Patient Monitoring

Medicare reimbursement for remote patient monitoring is set through the Medicare Physician Fee Schedule (PFS). The Centers for Medicare & Medicaid Services (CMS) updates the PFS every calendar year. The process follows a predictable rhythm.

  1. Proposed rule in summer. CMS usually releases the proposed PFS rule in July. It lays out new codes, policy changes, and draft payment values.
  2. Public comment period. Providers, technology companies, and associations have about 60 days to submit comments. CMS reviews them before finalizing anything.
  3. Final rule in fall. CMS typically publishes the final rule in early November.
  4. Effective date of January 1. New codes, rules, and rates take effect at the start of the calendar year.

Following this cycle is the simplest way to stay current. A proposal is still only a proposal until it appears in the final rule. Changes can soften, shift, or drop out entirely between July and November.

How Payment Rates Are Calculated

Each RPM code carries relative value units (RVUs) for physician work, practice expense, and malpractice cost. CMS multiplies those RVUs by a dollar amount called the conversion factor. A geographic adjustment then raises or lowers payment by locality. This is why the same code pays one amount in Boston and another in rural Kansas.

Setting matters too. RPM device codes are usually paid at the non-facility rate, such as a physician office. Published national averages are only a starting point. To see the rate for your locality and year, use the CMS Look-Up Tool.

RPM CPT Codes Covered by Medicare

Medicare groups RPM services into setup, device supply, and treatment management. A separate code covers physician time spent interpreting data. Each of the current RPM CPT codes fits into one of these groups.

Reimbursement information is provided for educational purposes only and is not legal, compliance, billing, coding, or reimbursement advice. Coding, coverage, and payment vary by payer and locality and are subject to change. Coverage or payment is not guaranteed; consult applicable payer guidance and qualified advisors. CPT® is a registered trademark of the American Medical Association.

Device Setup and Patient Education

CPT 99453 covers initial device setup and teaching the patient how to use the equipment. It is reported once per episode of care, not every month. This step deserves more attention than it gets. A patient who takes a blood pressure reading with the cuff on the wrong arm position produces data no one can trust.

Device Supply and Data Transmission

Two codes cover the device and the data it sends. CPT 99454 applies when a patient transmits data on 16 to 30 days in a 30-day period. CPT 99445, added for 2026, covers 2 to 15 days of data in the same window. The two codes are mutually exclusive. You report one or the other based on how many days of data the patient sent.

The shorter window fits patients whose needs change from month to month. A patient adjusting to a new blood pressure medication may need close monitoring for a week or two. So may someone recently discharged from the hospital.

Only one practitioner can bill device supply for a patient during a 30-day period. This holds true even when the patient uses more than one device.

Treatment Management Time

Three codes cover time that clinical staff, physicians, or other qualified health care professionals spend managing care based on the data.

  • CPT 99470 covers the first 10 minutes in a calendar month. CMS added it for 2026.
  • CPT 99457 covers the first 20 minutes in a calendar month.
  • CPT 99458 covers each additional 20 minutes after the first 20.

Each management code requires at least one real-time, interactive communication with the patient or caregiver during the month. CPT 99470 and 99457 are not reported together for the same month.

Physician Data Collection and Interpretation

CPT 99091 pays for at least 30 minutes a month of data collection and interpretation. The physician or qualified health care professional must perform this time personally. It is not reported alongside 99457 for the same patient and period.

Medicare Billing Requirements for RPM

Codes are only part of the picture. Medicare reimbursement for remote patient monitoring also depends on core requirements that have held steady across recent rule cycles.

  • The device must meet the FDA definition of a medical device.
  • Data must be collected and transmitted automatically. Readings a patient types in or reports by phone do not qualify.
  • The data must be physiologic, such as weight, blood pressure, pulse oximetry, blood glucose, or respiratory flow rate.
  • The patient must have an established relationship with the billing practitioner.
  • The patient must consent to the service, and the consent should be documented.
  • RPM and remote therapeutic monitoring (RTM) cannot both be billed for the same patient in the same period.
  • RPM can be billed alongside care management services such as chronic care management (CCM), as long as time is not counted twice.

Documentation carries a lot of weight in RPM reimbursement. Keep clear records of transmission days, management minutes, interactive communication dates, and medical necessity. Federal oversight is rising. An OIG report found that about 43 percent of Medicare enrollees who received RPM did not receive all three service components. Those components are setup and education, device supply, and treatment management.

Recent Changes to the RPM Code Set

The CY 2026 final rule added CPT 99445 and CPT 99470, effective January 1, 2026. They were the first new RPM codes in several years.

Both codes respond to a long-standing gap. Before 2026, a patient who sent data on 15 days could not support a device supply claim. A month with 15 minutes of management time had the same problem. Clinical work happened, but the codes did not reflect it. The new codes give care teams a way to match billing to what each patient needed that month.

Proposed RPM Changes Under Review

On July 14, 2026, CMS released the CY 2027 proposed rule. It includes a significant set of RPM and RTM proposals that would take effect January 1, 2027, if finalized. The main proposals include the following.

  • Clinical staff furnishing RPM and RTM services would need to be direct employees of the billing practitioner or practice.
  • RPM and RTM would require a face-to-face initiating visit, in person or by telehealth. The visit would include discussing the monitoring plan and obtaining patient consent.
  • Practice expense values for setup, device supply, and management codes would be revalued downward.
  • CMS also asked for comments on bundling RPM and RTM codes into four new HCPCS G-codes.

The comment period closed September 14, 2026. CMS is expected to publish the final rule in early November. Review the final language before changing staffing, contracts, or workflows. We will update this guide once the final rule is published.

How to Keep an RPM Program Ready for Each Year’s Changes

RPM reimbursement will keep evolving. These habits help a program adjust without disrupting patient care.

  1. Watch July and November. Read the proposed rule in summer and the final rule in fall. Plan changes for January 1.
  2. Check local rates every January. Look up each code you bill in the CMS tool for your locality.
  3. Track days and minutes automatically. Manual tallies invite errors. Your platform should log every transmission date and management minute.
  4. Match the code to clinical need. Choose monitoring intensity based on the patient’s condition, not on a billing threshold.
  5. Document consent and cost sharing. Patients should understand what RPM involves and what they may owe.
  6. Review rules beyond traditional Medicare. Medicare Advantage plans, state Medicaid programs, and commercial payers set their own RPM policies.

What to Look for in RPM Device Technology

The right technology makes compliance easier for staff and patients. Look for FDA-cleared devices that transmit readings automatically, without patient setup steps. Cellular connectivity matters because many patients do not have reliable Wi-Fi or a smartphone. Every reading should arrive time-stamped, so transmission days are easy to verify.

Integration matters as well. Device data should flow into the RPM software or electronic health record (EHR) your team already uses. Fulfillment, device replacement, and technical support also affect how many patients stay engaged month after month.

Medicare Reimbursement for Remote Patient Monitoring FAQs

This section answers common questions about Medicare reimbursement for remote patient monitoring. It covers what Medicare pays for, how often rates change, where to find current rates, and what patients may owe.

1) What does Medicare reimbursement for remote patient monitoring cover?

Medicare reimbursement for remote patient monitoring covers device setup and patient education, device supply with data transmission, and treatment management time. A separate code covers physician time spent collecting and interpreting data. Each service has its own CPT code and requirements.

2) How often do Medicare RPM payment rates change?

Medicare RPM payment rates change every calendar year through the Physician Fee Schedule. CMS proposes changes in summer, finalizes them in fall, and applies them on January 1. Rates can also shift when the conversion factor or code values change.

3) Where can I find current RPM reimbursement rates for my area?

Use the CMS Physician Fee Schedule Look-Up Tool. Select the year, enter the CPT code, and choose your Medicare locality. The tool shows the payment amount for facility and non-facility settings.

4) Can RPM be billed if a patient sends data fewer than 16 days in a month?

Yes, starting in 2026. CPT 99445 covers 2 to 15 days of data in a 30-day period. CPT 99454 still applies for 16 to 30 days, and the two codes cannot be billed together.

5) Do patients pay anything for remote patient monitoring under Medicare?

RPM is a Medicare Part B service, so the Part B deductible and coinsurance generally apply. Some patients have supplemental coverage that pays part or all of that cost. Discuss cost sharing with the patient when obtaining consent.

6) Can a practice bill RPM and RTM for the same patient?

Not in the same period. Medicare does not allow RPM and remote therapeutic monitoring to be billed together for the same patient. The care team should choose the service that fits the patient’s clinical need.

Understanding Medicare Reimbursement for Remote Patient Monitoring

Medicare reimbursement for remote patient monitoring follows a steady framework, even as rates and rules change each year. Setup, device supply, and treatment management codes cover distinct parts of the service. Core requirements such as FDA-defined devices, automatic data transmission, and patient consent remain constant. CMS updates the details through a yearly cycle of proposed and final rules. Care teams that watch that cycle, check local rates, and document carefully are best positioned to keep patients supported between visits.

Tenovi provides cellular-connected remote patient monitoring and remote therapeutic monitoring infrastructure for RPM software companies, chronic care management companies, telehealth platforms, health systems, payers, and pharmacies. Our standalone cellular devices and Bluetooth devices that connect through the Tenovi Cellular Gateway send readings automatically, with no Wi-Fi or smartphone required. Contact us for a free demo and consultation.

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.

Want to dig deeper? Get our FREE quick start guide to understanding RPM.

Learn how remote patient monitoring works, device and platform features, and how to seamlessly connect with fulfillment and data APIs. 

Download the RPM Quick Start guide by filling out the form below.