Your RPM program probably started with a reasonable promise. Enroll your hypertension and diabetes patients, let connected devices do the watching, and bill the monitoring codes every month. Twelve weeks later, someone on your team spends the first hour of every morning in a dashboard full of flagged readings. They call patients whose cuffs stopped syncing and rebuild time logs on the last Friday of the month so the claims can go out.
Or you went the other way. You signed with a vendor that handles everything. Now a share of every RPM claim leaves your practice, and patients ask your front desk who the nurse was that called them on Tuesday.
Both outcomes trace back to the same decision. You chose between remote patient monitoring (RPM) software and an RPM service before anyone mapped who would do the daily work and who would answer for the claims.
This guide puts the vendor models side by side. It shows the workload and cost hidden inside each and gives you a three-layer test you can apply to any proposal on your desk. By the end, you will know which model your staff can actually sustain, and where a dedicated virtual medical assistant fits when neither pure option works.
What an RPM Program Looks Like at 7:40 on a Monday Morning
A three-physician internal medicine group in Georgia came to us after nine months on a software-only RPM platform. They had enrolled about 140 patients, mostly hypertension with some type 2 diabetes. One medical assistant owned the program, between rooming patients.
Her Monday started before the first patient arrived. The weekend had produced more than thirty flagged items. Fewer than ten were clinically meaningful readings. The rest were missed transmissions, a cellular hub with a dead battery, and one patient whose weight had “dropped” eleven pounds because he had moved his scale onto the bathroom rug.
None of that work was billable on its own, and all of it had to happen before anyone could get to the readings that mattered.
By day 22 of each month, she was watching the “days transmitted” column. She tried to reach patients who were drifting below the 16 days of readings that the standard device code requires. On the last Friday she exported the time report, found gaps, and reconstructed call durations from memory. The software did exactly what it promised. The problem was everything it never promised to do.
RPM Software vs RPM Service: The Three Vendor Models, Defined
Almost every RPM proposal you receive falls into one of three shapes. The devices are often identical across them; what changes is which tasks end up on your payroll and which end up on someone else’s.
Software-Only RPM Platform
An RPM software platform gives your practice the technology layer. That means a dashboard that receives device readings, configurable alert thresholds, built-in time tracking, and usually device procurement and shipping. Your own staff does the work. They review readings, call patients, document the interactive communication, and prepare claims. Pricing is typically a per-patient monthly fee or a license, and your practice keeps the remaining reimbursement.
Turnkey (Full-Service) RPM Service
A turnkey remote patient monitoring vendor supplies the devices, the software, and the monitoring staff. Your physicians order the service and your team enrolls patients. The vendor’s nurses or monitoring staff review readings and contact patients. Claims still go out under your practice’s billing. Pricing is usually a share of each month’s reimbursement or a higher per-patient fee that covers the vendor’s labor.
Hybrid: Your Platform, Dedicated Support Staff
In a hybrid model, your practice chooses and controls the platform and the clinical protocol. A dedicated assistant, either hired or contracted, does the protocol-driven daily work inside your systems. That covers onboarding calls, reading review against your thresholds, missed-reading outreach, and documentation in your EHR. Anything clinical escalates to your nurses or physicians. You pay the platform fee plus the staffing cost, with no revenue share.
| Software-only platform | Turnkey RPM service | Hybrid (platform + dedicated staff) | |
|---|---|---|---|
| Who chooses the platform | Your practice | The vendor | Your practice |
| Who reviews readings daily | Your staff | Vendor monitoring team | Dedicated assistant, under your protocol |
| Who calls patients | Your staff | Vendor staff | Dedicated assistant, escalating to your clinicians |
| Where notes live first | Platform, synced if integrated | Often the vendor’s portal | Your EHR |
| Typical pricing | Per-patient fee or license | Revenue share or higher per-patient fee | Platform fee plus staffing cost |
| Speed to launch | Depends on your staff capacity | Fastest | Moderate |
| Who answers for the claim | Your practice | Your practice | Your practice |
Why Practices Choose the Wrong RPM Model: They Compare Price Instead of Workload
A pricing page tells you what leaves your bank account each month. It says nothing about what lands on your staff’s desks, and that second number is usually what decides whether a program survives its first year.
The Work a Software-Only Contract Quietly Hands to Your Staff
When a practice licenses a platform, the platform’s job ends at the dashboard. Everything after that belongs to your team:
- Device troubleshooting calls. A cuff showing an error code, a hub unplugged to charge a phone, a scale that never paired.
- Missed-reading outreach. Patients who stopped measuring on day nine need a call before day 20, not after.
- Alert triage. Separating the dangerous reading from the patient who measured right after climbing the stairs.
- Interactive communication. Live conversations long enough to meet the management time requirement, documented with date and duration.
- Time-log reconciliation. Matching logged minutes to actual calls before claims go out.
- Paperwork at both ends. Consent and order documentation at enrollment, plus offboarding when patients leave the program.
In the practices we support, the non-clinical share of that list runs about 4-6 minutes per enrolled patient per week. Multiply that across a panel of 120 and you have hidden a part-time position inside a “software” purchase.
The Cost a Turnkey Contract Hides Inside Every Claim
Turnkey solves the workload problem by moving it out of your building. The price shows up in three places.
The first is margin. A revenue share is paid on every claim for as long as the contract runs, including the months when your own clinicians did most of the escalation work.
The second is the patient relationship. A cardiology practice in Texas called us after patients started phoning the front desk to ask who had called them about their blood pressure. The vendor’s staff introduced themselves as part of the care team, but the patients didn’t recognize the voice or the number.
The third is documentation. In that same practice, escalation notes landed first in the vendor’s portal. One medication adherence problem reached the physician only at the patient’s next quarterly visit. Nobody did anything wrong. The note simply lived in a system nobody in the clinic opened every day.
The Three-Layer Ownership Test: Technology, Labor, and Liability
When we review an RPM proposal with a practice, we set the pricing page aside and ask three ownership questions instead. Each vendor model answers the first two differently. None of them changes the answer to the third, and that is the one most proposals leave out.
Layer 1: Technology
Who owns the platform, the devices, and the data? Ask whether devices are bought, leased, or vendor-owned. Ask whether readings and time logs can be exported in a format your EHR can import. Ask whether the devices are cellular (closer to plug-and-play for older patients) or Bluetooth (cheaper, but dependent on a smartphone). A practice that owns this layer can change staffing arrangements later without re-onboarding every patient.
Layer 2: Labor
Who reviews readings each day, who calls patients, who documents, and under whose protocol? This is the layer that turnkey vendors sell and software vendors leave with you. The useful question is not “who does it” in general. It is “who does it at 8 AM on the Tuesday after a holiday weekend, and where does their note go?”
Layer 3: Liability
Who answers for the claim? Under every model, the physician order, the documented consent, the medical necessity, the supervision, and the accuracy of the time logs all trace back to your billing practice. Clinical staff time can be furnished under general supervision, which is what makes outside staff workable at all. But general supervision still means your supervision.
If a payer requests records, they will ask for time logs with dates, durations, and the name and credentials of whoever made each call. If those logs sit in a vendor’s portal, your contract needs to guarantee you can pull them on demand.
Turnkey moves layers one and two off your plate. Layer three stays with you. Code selection now adds another reason to keep visibility into the work: the 2026 updates added shorter-duration options, so month-end billing depends on exact day and minute counts. Our guide on how the 2026 short-duration RPM codes change month-end billing decisions walks through that logic.
A Five-Question Decision Guide for Choosing Your RPM Model
Work through these in order. The early questions rule options out quickly, so you never end up negotiating terms on a model your staff couldn’t sustain anyway.
1. How Many Patients Will Realistically Be Enrolled in Month Six?
Use enrolled-and-transmitting patients, not eligible patients. Most practices have far more eligible patients than they will ever enroll, and not every enrolled patient hits the data threshold every month. Some vendors set per-patient minimums that make small panels expensive. Below a few dozen active patients, the math for any model gets thin.
2. How Many Staff Hours Per Week Can You Actually Give RPM?
Count real hours, not “she’ll fit it in between patients.” Take your month-six panel and multiply by the handling time per patient. At 120 patients and 15 minutes of non-clinical handling each per month, that is 30 staff hours before a single clinical conversation. If nobody on your team has those hours, a software-only platform will stall, however good the software is.
3. How Much of the Patient Relationship Do You Want to Keep?
For heart failure, complex diabetes, or any program where your physicians adjust medications based on trends, continuity matters. Patients follow advice from voices they recognize. If outreach coming from your practice’s name and number is a priority, weigh that heavily against turnkey.
4. What Does the Contract Say About Leaving?
Read the term length, the auto-renewal language, device ownership, and the data export clause before you read the price. A cheaper contract you can’t leave can easily cost more over three years than a pricier one you can.
5. What Margin Makes RPM Worth Running for You?
Use one simple formula: average reimbursement actually collected per patient per month, minus vendor fees, minus internal staff minutes multiplied by loaded hourly cost. Run it with your real adherence rate, not the vendor’s best case. If the answer is thin under every model, fix enrollment and adherence before you pick a vendor.
How the answers usually map:
- Small panel and no spare staff hours: a turnkey vendor is a reasonable way to start, with a strong exit clause.
- Staff with protected time and a clinical lead who wants control: a software-only platform, run on a disciplined process. Our five-phase RPM workflow for clinics shows how to split those tasks.
- A panel that is growing, no spare staff hours, and margin and patient relationship both matter: the hybrid model.
That third profile is the one our remote patient monitoring support is built for. A dedicated, HIPAA-compliant Care VMA works inside the platform and EHR you already use. They handle device onboarding calls, morning reading review against your thresholds, missed-reading outreach, and same-day documentation. Every clinical escalation goes to your own nurses and physicians.
Five RPM Vendor Mistakes We See After the Contract Is Signed
Each of these surfaces months after go-live, usually at month-end close or on a renewal call. By then it costs the most to fix.
Signing Based on Eligible Patients Instead of Adherent Ones
Vendor projections often start from your eligible population. Your revenue starts from patients who transmit enough days and get their interactive call each month. Ask the vendor for adherence data from practices your size, then discount it for your own population.
Letting Escalation Notes Live Outside Your EHR
If the first record of a concerning reading sits in a vendor portal, your physicians will miss it. Require that escalations reach your EHR inbox the same day, written by whoever made the call.
Assuming the Vendor’s Time Logs Will Hold Up in an Audit
A time log that shows “RPM review, 22 minutes” without who did it and what was discussed is a weak defense. Ask to see a sample log during the demo. Confirm it includes staff names, credentials, dates, and call summaries, and that you can export it without filing a support ticket.
Treating “Turnkey” as “Hands-Off” for Your Physicians
Your physicians still order the service, set the thresholds, and own the clinical decisions. Practices that skip a monthly 15-minute review of the vendor’s escalation report tend to discover protocol drift only after something goes wrong.
Splitting RPM and CCM Across Two Vendors
When one vendor runs RPM and another runs chronic care management, the same patient may get two calls a week from two different voices, each documenting time in a separate system. If you offer both programs, read our guide on running CCM and RPM under one care team before you sign a second contract.
Planning Your Exit Before You Sign the RPM Contract
Exit terms cost nothing to negotiate before you sign and a great deal to discover afterward. Four areas deserve a line in the contract.
Data Portability
Ask for the full reading history, time logs, and communication notes in a standard format, and request a sample export during the demo. If the vendor can’t show one, assume the data will be hard to get when you leave.
Device Ownership and Reassignment
Vendor-owned cellular devices are often locked to that vendor’s platform. Switching then means shipping new kits, re-educating patients, and waiting for transmissions to resume.
A family practice in Ohio switched vendors after a two-year contract. They had to re-ship devices to about 90 patients. Billable transmission days dropped for part of the panel during the two months it took to get everyone back online. A device buyout clause or a bring-your-own-device option would have avoided most of that.
Whose Name the Patient Hears
Specify in writing how monitoring staff identify themselves. Specify the caller ID name and which number patients should call back. When the program moves, the patient relationship should already belong to your practice.
Moving From Turnkey to Hybrid Without a Billing Gap
Turnkey is often the right way to start and the wrong way to stay. An endocrinology practice we work with launched with a full-service vendor. Once their panel passed roughly 200 patients, they moved to their own platform with a dedicated VMA.
What made that move work was timing and sequencing. They started the migration 90 days before renewal and moved patients in cohorts by device type. They kept the old platform live until each cohort transmitted cleanly on the new one, so no month ever went unbilled for the whole panel.
Choose the RPM Model You Can Still Run in Year Three
There is no universally best answer to RPM software vs RPM service. If your panel is under 40 patients and nobody on your team has a free hour, a turnkey vendor may honestly be your best starting point, as long as you can leave cleanly. If you have protected staff time and a clinical lead who wants control, a software-only platform will give you the best margin.
Most of the independent practices we talk to sit between those two. They have a growing panel, a team already stretched at the front desk, and physicians who want patients to hear from their own practice. For them, keeping the technology and the liability in-house and adding a dedicated assistant for the daily labor tends to be the model that still works in year three.
If you want a second opinion on the RPM setup you have now, or a proposal sitting on your desk, book a free consultation with the Care VMA team. We will walk through the three layers with you and show you where a dedicated virtual medical assistant would and wouldn’t change the math.
Frequently Asked Questions
These are the questions practice managers raise most often when they are weighing RPM vendors.
What is the difference between RPM software and an RPM service?
RPM software gives your practice the platform, alert rules, and time tracking, while your own staff reviews readings and talks to patients. An RPM service, often called turnkey or full-service, adds the vendor’s monitoring staff on top of the devices and software. In both cases, your practice is still accountable for the claims.
Is turnkey remote patient monitoring worth it for a small practice?
It can be, especially when your panel is small and no one on staff has time for daily review. The trade-offs are lower margin per patient and less control over how patients experience the program. Negotiate data export and device terms before signing so you can change models as you grow.
Who is responsible for RPM billing compliance when a vendor does the monitoring?
Your billing practice is. The order, consent, supervision, and time documentation all support claims submitted under your practice. Make sure your contract gives you on-demand access to complete time logs and call notes.
Can we switch from a turnkey RPM vendor to our own platform mid-year?
Yes, but plan it in cohorts. Keep the existing platform active until each group of patients transmits reliably on the new devices, so you avoid a month in which no one meets the data threshold. Starting the process about 90 days before renewal gives you room to do this without pressure.
Can a virtual medical assistant handle RPM monitoring tasks?
A trained virtual medical assistant can handle the protocol-driven work: device onboarding calls, reading review against your thresholds, missed-reading outreach, documentation, and month-end billing preparation. Clinical judgment and treatment decisions stay with your nurses and physicians. The assistant escalates anything outside the protocol to them.
