Medicare’s 2026 and Proposed 2027 RPM Changes: What Lower Monitoring Thresholds Mean for Practices

Policy note: This article addresses Original Medicare fee-for-service policy effective January 1, 2026. Other payers and care settings may differ. The CY 2027 provisions discussed below remained proposals as of September 3, 2026.

Medicare’s 2026 remote patient monitoring changes give practices more flexibility, especially for patients who do not need—or cannot reasonably complete—a high-frequency monitoring schedule.

Two new CPT pathways allow reporting at lower thresholds: 99445 for device supply when qualifying physiologic data are transmitted on 2–15 days within an applicable 30-day period, and 99470 for the first 10 minutes of treatment management in a calendar month.

But a lower billing threshold is not a clinical protocol. It does not establish medical necessity, prove that two days of data are meaningful, or replace the practitioner’s responsibility to decide what should be measured, how often, and what action should follow.

The right principle is simple: the clinical question determines the monitoring plan; the code follows the service actually delivered.

What changed for Medicare RPM in 2026

The CPT Editorial Panel created the new and revised remote-monitoring codes, and CMS adopted them for Medicare payment beginning January 1, 2026.

The two device codes are alternatives, not add-ons. The two initial treatment-management codes are also alternatives. Additional 20-minute increments under 99458 follow the 20-minute pathway when its requirements are met; 99458 is not a way to extend 99470.

The device and treatment-management thresholds measure different things. Device codes count days with qualifying data transmission during a 30-day reporting period. Treatment-management codes count qualifying time during a calendar month. The shorter device code and shorter time code do not have to be paired.

“Data day” is useful shorthand, but it is not a CMS-defined term. Multiple readings on one date do not become multiple transmitted days. Practices should verify current CPT instructions and payer guidance rather than assume how delayed or batched transmissions count.

The required live interaction is synchronous, real-time communication with the patient or caregiver; it does not inherently require video or an in-person encounter. Automated prompts, asynchronous messages, and dashboards can support a program, but they do not replace that interaction.

The lower thresholds did not change Medicare’s baseline requirements, including an established patient relationship, medical necessity, consent, a qualifying connected medical device with automatic data transmission, and applicable restrictions on which practitioner may bill. Under current 2026 policy, setup and device functions may be furnished by auxiliary personnel under general supervision, while treatment-management work is furnished by the physician/QHP or qualifying clinical staff under the applicable supervision rules.

The threshold is not the protocol

The most important mistake would be to translate “2–15 transmitted days” into “two days of monitoring are clinically enough.” Medicare’s threshold determines whether a service may be reportable. It does not tell a clinician how much information is sufficient to diagnose, reassess, or safely manage a patient.

A defensible lower-frequency plan should answer four questions:

• What is the clinical question? State the decision the data are intended to support.
• What protocol can answer it? Match the number and timing of measurements to the condition, patient, and risk.
• What happens when data are abnormal—or absent? Define thresholds, symptoms, missed-reading workflows, and escalation routes.
• Can the practice show the complete loop? Connect medical necessity, consent, setup, transmission, review, live interaction, action, and claim.

Days, readings, minutes, and episode length are not interchangeable. A patient may transmit several readings on one day, and an RPM episode may continue beyond one reporting period. A billing threshold can also be reached even when measurements are too sparse or inconsistent to answer the clinical question.

Hypertension shows why measurement quality matters

Home blood pressure is the clearest example of a short, structured measurement window—and of why the code should not define the protocol.

The 2025 AHA/ACC multisociety hypertension guideline recommends home BP monitoring to help confirm hypertension and support medication titration. Its structured approach uses two readings in the morning and two in the evening for at least three days, with seven days preferred.

A supporting study of 316 community-dwelling adults who were not taking antihypertensive medication found that averaging morning and evening readings over three days reliably estimated mean home BP in that population. The study did not validate a two- or three-day RPM program, treated patients, or post-titration safety monitoring. Its narrower lesson is that several properly obtained measurements over several days may answer a defined question.

Device quality and technique still matter. Meeting the FDA statutory definition of a medical device is not the same as being clinically validated for a particular use. A sound home-BP protocol should account for a validated upper-arm device, correct cuff size, positioning, rest, repeat measurements, and a clear pathway for symptoms or severely abnormal readings.

Where a lower-threshold pathway may—and may not—fit

A lower-frequency plan may fit a structured home-BP assessment, a planned reassessment after a treatment change, or follow-up for a stable chronic condition when the practitioner can explain why the cadence is sufficient. It may also support a defined acute-condition or care-transition question in an established patient when RPM is medically reasonable and necessary and does not duplicate another service.

It is a poor fit when sparse or delayed review could put the patient at risk. Unstable heart-failure symptoms or weight trends, high-risk oxygen desaturation, symptomatic or severely elevated blood pressure, and situations requiring urgent assessment need a different level of attention.

RPM is also not automatically the correct service simply because a measurement occurs at home. Depending on the purpose, practices may need to consider continuous glucose monitoring, ambulatory blood-pressure monitoring, cardiac monitoring, or structured self-measured BP. The goal is to choose the service that accurately reflects the care furnished—not to fit every remote data stream into RPM.

The complete service still matters

The new flexibility arrives during increasing federal scrutiny. In 2024, HHS OIG reported that claims and encounter data for about 43% of Medicare RPM enrollees lacked a record for at least one of three components: education and setup, device supply, or treatment management.

That finding is an oversight signal, not proof that 43% received deficient care. OIG did not review medical records, CMS did not require all three components to be billed, and limited exceptions could explain some missing claims. In a 2025 follow-up, OIG reported approximately $536 million in 2024 Medicare fee-for-service and Medicare Advantage RPM payments and identified billing patterns that may warrant scrutiny. OIG cautioned that those measures do not, by themselves, prove fraud or noncompliance.

For practices, the durable lesson is to make the clinical and billing record understandable. A strong workflow should show:

• why the patient was selected and what question was being monitored;
• that an appropriate connected device was assigned, the patient was trained, and consent was documented;
• measurement and transmission dates, missing-data exceptions, review, and outreach;
• the required live interaction and qualifying time without duplication; and
• the clinical decision, escalation, or continuation plan that followed.

Before billing, verify that 99445 and 99454 were not both reported for the same device period, and that 99470 and 99457 were not both reported for the same calendar month. Setup and education under 99453 are generally reported once per episode. Only one device-supply service is generally reportable per patient per applicable 30-day period, even when multiple devices are used. Beneficiary cost sharing, concurrent-service rules, RPM/RTM exclusivity, global-period restrictions, and payer-specific requirements also remain relevant.

What CMS may change in 2027

CMS’s proposed CY 2027 Physician Fee Schedule would make substantial changes to remote monitoring. As of September 3, 2026, these provisions were proposals—not final policy—and comments were due September 14, 2026.

The proposal would require a separately reportable face-to-face initiating visit, conducted in person or by telehealth, at the start of RPM or RTM. It would also allow payment for RPM/RTM services furnished by clinical staff only when those staff are directly employed by the billing practitioner or practice.

That employment proposal is not a blanket ban on third-party technology vendors. Software, devices, logistics, and nonclinical operational support are distinct from clinical-staff-furnished services. Practices using embedded or outsourced teams should map who employs each person, which services that person furnishes, what work supports the claim, and how supervision is documented.

CMS is also considering a four-code framework that would bundle the remote-monitoring workflow more tightly, along with changes to remote-monitoring valuation. Whatever the final rule does, the durable operational requirement will remain: monitoring data must connect to a defined clinical purpose, a responsible care team, and an action.

Turning flexibility into a reliable care loop

Lower thresholds increase the need for operational precision. A practice should be able to distinguish the prescribed clinical cadence from the minimum reporting threshold, measurement count from transmitted dates, device transmission from clinician review, automated outreach from the required live interaction, and a captured reading from a completed care decision.

For Vironix, that is the practical value of the 2026 change. Technology and care operations can help practices execute a defined cadence, detect missing or abnormal data, document interaction, and close the loop with an appropriate action. They should not be positioned as determining medical necessity, selecting the correct code, or guaranteeing compliance.

Frequently asked questions

Can 99445 and 99454 be billed for the same 30-day period?

No. They are alternative device-supply pathways based on the number of days with qualifying data transmission.

Do two readings on the same day satisfy the 99445 threshold?

The formal code structure is based on days with data transmission, not simply the number of measurements. Two measurements on one date should not be described as two transmitted days.

Does billing 99445 require billing 99470 in the same month?

No. Device supply and treatment management are separate service components. Each reported service must independently satisfy its requirements.

Can 99458 be reported after 99470?

99458 represents additional 20-minute increments after the initial 20-minute pathway. It should not be used to extend 99470. Confirm current CPT instructions and payer edits before billing.

Sources

• CMS: Remote Patient Monitoring
• CMS MLN: Telehealth & Remote Monitoring
• CY 2026 Medicare Physician Fee Schedule Final Rule, CMS-1832-F
• CY 2021 Medicare Physician Fee Schedule Final Rule, CMS-1734-F
• HHS OIG: Additional Oversight of Remote Patient Monitoring in Medicare Is Needed
• HHS OIG: Billing for Remote Patient Monitoring
• 2025 AHA/ACC Multisociety Guideline for High Blood Pressure in Adults
• Bello et al.: Number of Measurements Needed to Obtain a Reliable Estimate of Home Blood Pressure
• CY 2027 Medicare Physician Fee Schedule Proposed Rule, CMS-1848-P