Somewhere in every practice, there’s a patient like this: hypertension that won’t quite behave, a blood pressure cuff sitting in a closet, and a physician who finds out the numbers were bad three weeks later, at the next scheduled visit. Remote patient monitoring systems exist to close that exact gap. Although the concept is not new, it began to resemble standard chronic care in 2026 and ceased to be a test project for a few tech-forward providers.
This is the useful version if you’re considering creating a program or if you currently have one and would like to know what has changed.
What remote patient monitoring actually means
RPM is easy after the branding is removed. The patient has some connected devices at home, such as a blood pressure cuff, a pulse oximeter, a glucose meter or a scale. And the values are sent automatically to the clinic. One of your team looks at the data, usually with software that flags any deviations from a given range, then looks to see if anything looks off.
Well, that’s the whole idea. This is not the same as a scheduled, synchronous telehealth visit. RPM systems catch problems that a monthly once-over won’t, because it’s always there, in the background, between checkups. It also works best for diseases such as diabetes, heart failure, COPD and hypertension that do change day-to-day. Often the arrangement is not worth the trouble for a diagnosis which changes little from month to month.
Why healthcare providers are adopting it now
Some of it is just math. According to Fortune Business Insights, the global market for these devices is expected to expand from around $71 billion this year to roughly $290 billion by 2034, with providers, rather than patients or insurers, making up the majority of customers. In 2024, there were over 75 million patients being actively monitored via remote platforms, compared to just 48 million three years prior. Over the past several years, CMS has also worked to make remote care more manageable, supporting hospital-at-home programs that are already in place in more than 300 hospitals around the country.
But the real reason is more boring, and more convincing: chronic disease doesn’t happen in fifteen-minute appointments every few months. It happens in the gaps between them. Blood pressure creeping up over two weeks, or blood sugar swinging after a medication change, is exactly what RPM is built to catch before it turns into an ER visit.
How RPM billing actually works in 2026
The CPT codes you’ll use most
Medicare reimbursement for RPM runs through a small set of CPT codes that have stayed fairly stable for a few years:
- 99453 covers device setup and patient education, billed once, at roughly $22.
- 99454 covers the device and data transmission for 16 or more days in a month, at around $47.
- 99457 covers the first 20 minutes of staff time reviewing data and talking to the patient, at roughly $52.
- 99458 covers each additional 20 minutes, at about $41, and it can be billed more than once if the time is genuinely there.
What changed this year
The 2026 Medicare Physician Fee Schedule added two codes that fix a real gap. Before this year, if a patient only transmitted readings for, say, 10 days that month, or your staff spent 15 minutes managing their care instead of 20, you billed nothing. The threshold had to be met, or the work went unpaid.
Now there’s 99445, covering 2 to 15 days of data at the same rate as 99454, and 99470, covering the first 10 minutes of management time at about $26. Neither stacks with its longer counterpart; you bill one or the other. Together, they mean lighter-touch monitoring finally gets reimbursed instead of falling through the cracks. Rates shift by location and by payer, so treat these as national averages, not what will show up on your remittance.
What makes an RPM program actually work
Compliance is the real bottleneck
All dashboards are good in the demo. The programs that hold up typically choose the most basic device that does the task, instead of the devices with the largest feature list, and spend actual time onboarding.
Alert fatigue will bury your staff
If every reading pings someone’s inbox, your team stops looking within a few weeks. Programs that last have sensible thresholds and, more importantly, an actual person whose job includes triaging that data, not a nurse squeezing it in between everything else on their plate.
If it doesn’t talk to your EHR, it’s not saving anyone time
A platform that lives entirely outside your existing workflow means someone is manually copying numbers between two systems. That’s manageable for five patients. It falls apart at fifty.
How to choose remote patient monitoring systems
Skip the feature list and ask harder questions instead. Is it a bespoke project or does it come pre-integrated with your EHR? When a device won’t pair, who takes the troubleshooting call, your staff or theirs? And what does this cost per patient per month once you add up the device, the platform fee, and the staff time to run it, not just the number on the sales sheet?
Cellular-connected devices deserve a specific mention here. A meter that just works over cell data means one less “let’s walk through your Wi-Fi settings” call with an 80-year-old patient. That saves more time, day to day, than most items on a feature comparison chart.
Is it actually worth it?
For most practices managing chronic disease, yes, though it’s not automatic. RPM pays reasonably well, Medicaid now covers it in 42 states, and more commercial payers are following. It also genuinely catches problems early, which is the part that’s easy to forget once you’re buried in billing codes. However, if dealing with the billing codes is an issue, you can take help from expert services such as Tellihealth.
None of that happens just by buying remote patient monitoring systems, though. It happens when a practice treats RPM as a change to how care gets delivered, with someone accountable for actually watching the data, instead of a device bolted onto business as usual.
