.jpg)
Updated September 2026
Thinking about investing in a remote patient monitoring system, meaning the software and connected patient devices, for your organization? Remote patient monitoring, or RPM, has become one of the most established Medicare care management programs, with billing built around six CPT codes and coverage extending to both chronic and acute conditions. I've spent my career on both sides of remote care, as a remote patient monitoring coordinator running a program day to day, and now as director of client success at Prevounce helping organizations choose and launch their own programs. A pattern I often see is that practices which choose an RPM system based on price alone tend to regret it, while practices that answer a handful of practical questions upfront tend to build programs that stick.
Before choosing a remote patient monitoring system, I recommend answering these five questions.
Q1. What remote patient monitoring services do I want to offer?
Depending on your type of practice, this answer may be straightforward or more complicated. RPM can support the measurement of blood pressure, weight, blood sugar levels, and other vital signs. Specialty practices will want a system that collects and interprets their most pertinent patient data: blood pressure may matter most for cardiologists, while a gastroenterologist may focus on weight. General and family practices will want to base this decision on their target patient population and the conditions they want to manage.
It's common for practices to launch RPM around a single condition, then expand the program as staff and patients grow comfortable with the associated processes. If your practice also runs chronic care management (CCM) or advanced primary care management (APCM) programs, confirm your RPM vendor can support those on the same platform.
Q2. How difficult is it to set up and use the remote patient monitoring system?
A few variables affect this. Some RPM vendors hand practices the system and instructions and expect the practice to handle setup. Others take a more active role, which can speed up the process and catch problems early.
Setup is only part of the equation. Once a system is running, ease of use matters just as much. A system that's genuinely difficult to use will discourage staff and stall the program's growth. Complexity isn't automatically disqualifying if your team is tech-savvy or the vendor provides ongoing training and support, but it's worth confirming which is true before you commit.
Some platforms can be customized to fit your clinical workflow, produce the reports you want, and deliver notifications the way you prefer. When demoing a system, evaluate ease of use, customization options, and the availability of training and support. Also check whether the RPM system interfaces with your existing EHR or revenue cycle management/billing software. The vendor's available partners and integrations page is a good place to start if this functionality matters to your practice.
Q3. What are my options for remote patient monitoring equipment?
A program's success depends heavily on the devices patients actually use. Some vendors require their own devices; others allow a "bring your own device" model that lets you integrate equipment from other manufacturers. Devices may ship directly to patients, ship to the practice for distribution, or in some cases be purchased by patients themselves, though you'll want to confirm compatibility with your system either way. There are two separate things worth understanding here: how the equipment is sourced and supported, and how it connects.
Sourcing and support. Find out where support for patient setup comes from: Is troubleshooting your practice's responsibility, or does the vendor provide hands-on help?
Connectivity type. Decide whether you want cellular devices, Bluetooth devices, or a combination. Cellular devices typically only require a patient to insert batteries and turn the device on. Bluetooth devices require more setup steps and can be harder for less tech-savvy patients to manage. There's also a third option to ask about: Some vendors sell hub-based systems where the patient's device is Bluetooth and only a separate piece of hardware connects over cellular. If a vendor's answer to "is this cellular" isn't a straightforward yes about the device itself, press for specifics on what's actually cellular and what isn't. For the full breakdown of how these options compare, see Prevounce's guide to RPM device connectivity types, and for a checklist of what to ask any vendor to confirm which type you're actually getting, see how to vet an RPM vendor's connectivity claims.
In my time coordinating an RPM program, the biggest predictor of whether we caught a concerning trend early usually wasn't the software. It was whether a device reliably got a reading to us in the first place.
Q4. How are coding and billing completed?
RPM can be a meaningful revenue source when billed correctly. As of 2026, six CPT codes cover the program: a one-time setup code, two device-supply codes depending on how many days a patient transmits data in a 30-day period, and three time-based codes for clinical staff's monitoring and management work. Fully engaged patients can generate $100 to $180 or more per month, with newer, lower-threshold codes closing gaps that used to leave lighter-engagement patients underbilled. For a full breakdown of the current codes, see Prevounce's summary of the 2026 RPM CPT code changes.
How accurately and efficiently this billing gets done depends heavily on the system itself. When speaking with vendors, ask specifically how their system supports coding and billing. A good system streamlines this work, which minimizes staffing costs and helps your practice keep more of what it earns after vendor fees, which typically include devices, software hosting, support, and cellular service.
Q5. What service type of RPM program do I want for my practice?
The system you choose helps determine your program type, and vice versa. Programs generally break down into full-service, self-managed, or outsourced care management programs.
A full-service program typically means the vendor supplies devices (shipped to patients directly or through the practice), may offer device leasing to eliminate upfront costs, often uses cellular devices, and includes vendor-provided technical support. Monthly costs tend to run a higher percentage of reimbursement, but the practice avoids upfront device costs and spends less staff time managing the program.
A self-managed program typically means the practice maintains its own device supply, contracts with a vendor mainly for data management software, and handles patient technical support itself, which isn't billable time. Overall costs tend to run lower, but the practice takes on more upfront cost and operational responsibility.
Some vendors, like Prevounce, offer a middle option: staffed care management, meaning the vendor's own clinical staff handle patient enrollment and engagement directly, beyond supplying devices and technical support. This shifts more day-to-day work off your practice, at a corresponding cost. Ask directly whether a vendor offers this outsourcing care management tier if your staff capacity is limited or if you want to rapidly grow a program without needing to worry a lot about staffing levels.
Ready to Choose Your RPM System?
If your organization is ready to see what a remote patient monitoring system looks like in practice, schedule a no-obligation demo. Even if Prevounce isn't the right fit, we're happy to help you think through what to look for. For more, download this buyer's guide to remote patient monitoring software and devices.
Frequently Asked Questions About Choosing an RPM System
What's the difference between a full-service and self-managed RPM program?
A full-service program has the vendor handle device supply and technical support, usually at a higher percentage of reimbursement, while a self-managed program has the practice handle device supply and patient support itself, usually at a lower ongoing cost but higher upfront investment. Some vendors now offer a staffed care management tier in between, where the vendor's own clinical staff handle enrollment and engagement directly. Most practices choose based on staff capacity and how much operational work they're prepared to take on.
How much revenue can a practice expect from an RPM program?
As of 2026, fully engaged patients can generate roughly $100 to $150 or more per month across six CPT codes, covering device setup, device supply, and clinical staff time. Actual revenue depends on patient engagement, staffing capacity, and how consistently the practice bills all codes it's eligible for.
Should I choose an RPM vendor that lets me bring my own devices?
It depends on whether device flexibility matters more to your practice than the simplicity of a single, vendor-managed device ecosystem. A bring-your-own-device model offers more choice but can complicate support and compatibility; a vendor-supplied model simplifies both at the cost of flexibility.
What questions should I ask an RPM vendor about setup and support?
Ask who handles setup, whether support is available to patients directly or only through your staff, whether training is provided, and whether the system interfaces with your existing EHR. These answers affect both how quickly you can launch and how much ongoing staff time the program will require.
