For years, billing Medicare for remote patient monitoring meant clearing a 16-day bar. A patient had to transmit readings on 16 separate days inside a 30-day window. Twelve days of blood pressure readings produced nothing billable, no matter how useful those twelve days were clinically.
That rule is no longer the only one on the books.
The 2026 CPT code set, effective January 1, added codes built around shorter monitoring windows and less management time. For practices that looked at an RPM program two years ago and decided the math did not work, the math is different now.
What Changed for Remote Patient Monitoring in 2026
The American Medical Association released the CPT 2026 code set with 288 new codes, effective January 1, 2026. Two changes in that batch matter for anyone running or considering an RPM program.
Five new codes cover monitoring periods of 2 to 15 days within a 30-day window. The old 16-day requirement did not disappear, but it is no longer the only door.
Two new treatment-management codes carry a 10-minute-per-calendar-month threshold, down from the previous 20-minute minimum.
| Before 2026 | Added for 2026 | |
|---|---|---|
| Device data required | 16 days in a 30-day period | 2 to 15 days in a 30-day period |
| Management time required | 20 minutes per calendar month | 10 minutes per calendar month |
In a practice administrator’s terms: a patient who stops transmitting on day 11 is no longer automatically unbillable, and a month in which your care team spent 12 focused minutes reviewing a patient’s data is no longer a write-off.
CMS finalized payment for the new remote monitoring codes in the CY 2026 Physician Fee Schedule, setting their values from hospital outpatient cost data rather than the standard practice expense methodology. Same effective date.
Why the 16-Day Rule Left Both Patients and Revenue Behind
The old thresholds were not a paperwork problem. They were a mismatch between how billing rules were written and how people actually live.
Patients travel. They get sick. They forget the cuff for four days and then remember.
A threshold assuming near-daily adherence for more than half the month was always going to leave real clinical work uncompensated.
The billing data shows how tight the fit was. A serial cross-sectional analysis of Medicare RPM claims in JMIR mHealth and uHealth found that 69% of monthly management reimbursements were billed at the minimum 20-minute increment, with only 31% exceeding it.
That is the number worth sitting with. The 20-minute minimum was not a comfortable floor most practices cleared with room to spare. It was the number two-thirds of them were pinned to.
Which is why cutting the threshold to 10 minutes changes the arithmetic of remote patient monitoring rather than trimming its edges.
The same analysis tracked the category’s growth: Medicare RPM payments rose from $5.5 million in 2019 to more than $101 million in 2021, with new patients climbing from 20,640 to 123,476. For practices managing chronic conditions, RPM sits alongside the chronic care management services many already run.
What Practices That Adopted RPM Actually Saw
A 2025 Health Affairs study of 754 primary care practices that began billing remote physiologic monitoring between 2019 and 2021 found their Medicare revenue rose 20.0% through 2023, compared with matched practices that did not adopt.
Two details make that more useful than the headline alone.
The revenue did not come from RPM billing by itself. It came from direct RPM billing plus additional outpatient visits plus care management services. Monitoring surfaced reasons to see patients, and those visits were billable.
And the growth was not bought with headcount. Billing provider numbers rose only 2.7%, meaning increases were, in the study’s words, “predominantly driven by increased activity per provider.”
One honest caveat: these practices adopted under the harder thresholds. The study describes what the category returned before the 2026 changes, not after.
What a Reading Caught That an Office Visit Did Not
Numbers make the case in aggregate. A single patient makes it faster.
Naveed Hasan, M.D., FCCP, practices pulmonology, sleep medicine and critical care at Breathe 360 in Newark, Delaware, where the team uses healow Remote Patient Monitoring. One of his patients had been wearing a pulse oximeter at home.
“She said, ‘Doc, I would have never known that my heart rate was jumping up to 130, 140.’ Once she put on her pulse oximeter and brought it to her cardiologist, who had also missed that before, they found she’d been running into AFib with rapid ventricular rate.”
The readings led to a diagnosis and an avoided hospital admission, according to the Breathe 360 customer story.
An office visit observes a patient on the day they happen to be in the room. Episodes that come and go on the other days are invisible to it, not because anyone was careless, but because nobody was watching on those days.
It is also a reminder that remote patient monitoring is not only a blood-pressure-and-glucose program for primary care. Here it was a pulmonology practice and a pulse oximeter.
From Blood Pressure Reading to Billable Encounter
In practice, remote patient monitoring runs from a home device to a claim in five steps.
- The patient takes a reading on a connected device. Blood pressure cuffs, glucometers, scales and pulse oximeters are the common categories, over cellular or Bluetooth. FDA-compliant devices are required.
- The reading transmits automatically.
- It lands in a dashboard and a work queue, where the care team reviews trends rather than individual data points. healow RPM shows 7-day, 14-day, 30-day and 90-day progress indicators, plus adherence tracking that makes it visible when a patient has stopped transmitting.
- Someone acts on what the data shows. A call, a medication adjustment, a visit.
- The time spent and the clinical action are documented, and the encounter becomes billable.
Step three is where most programs live or die, and the reason is alert fatigue.
Set thresholds too tightly and a nurse opens the queue to 200 out-of-range flags on a Monday morning, learns within a month that most are noise, and stops opening it. Custom alert thresholds exist to prevent that. Set them deliberately at the start, per patient population, rather than accepting the defaults.
No two patients are the same, and the thresholds should not be either. A newly diagnosed hypertensive patient being titrated onto a new medication needs a tighter range than someone whose blood pressure has been stable for two years. Thresholds can be set per patient and adjusted as the clinical picture changes, so the alerts that reach the care team are the ones worth acting on.
What to Check Before You Bill Remote Patient Monitoring in 2026
Confirm which codes your payers recognize. The CPT code set and Medicare are not the entire payer landscape. Commercial coverage of the new short-duration and 10-minute codes will vary, and that is a faster conversation to have now than after the first denial.
Confirm your consent and enrollment documentation. Settle requirements before the first device ships, not afterward.
Decide who owns the work queue. RPM data with no named owner is the most common failure mode in the category. It is not a technology problem and no vendor can solve it for you.
Set alert thresholds on purpose. Defaults are a starting point, not a decision.
The Thresholds Are Not What They Were
Plenty of practices ran the numbers on remote patient monitoring in 2023 or 2024, found the 16-day and 20-minute bars did not fit their patients, and set the idea aside. That was a reasonable conclusion given the rules at the time.
The rules are different now. Shorter monitoring windows and a lower management-time threshold both have codes attached, and the peer-reviewed evidence on what adoption returned came from practices working under the stricter version.
If your practice manages chronic conditions and shelved RPM once already, run the arithmetic again against the 2026 thresholds rather than the ones you rejected.
See how healow Remote Patient Monitoring fits your practice.