Choosing a remote patient monitoring company is a bigger decision than most practices treat it as. The vendor you pick determines which devices your patients can actually use, whether monitoring data lands in your EHR or in yet another portal, who performs the clinical work, and whether your documentation would survive an audit. Under the 2026 billing rules — where the number of days a device transmits now selects between two different device-supply codes — vendor quality is directly a revenue variable.
This checklist walks through the evaluation criteria that separate durable RPM partnerships from the ones practices quietly abandon after a year.
Cellular or Bluetooth devices — which should you require?
Device connectivity is the first fork in the road, and it drives patient engagement more than any other technical choice.
Cellular devices transmit readings automatically over a built-in cellular connection. The patient takes a blood pressure reading; the reading appears in the platform. No smartphone, no app, no Wi-Fi password, no Bluetooth pairing. For Medicare populations — where technology comfort varies widely — cellular devices consistently produce more transmission days with less staff troubleshooting.
Bluetooth devices pair with a smartphone app that relays the data. They are typically cheaper and can capture richer app-based engagement, but every link in the chain — phone charged, app installed, Bluetooth on, pairing intact — is a place where transmission silently stops.
The billing rules are why this matters more than it used to. Device-supply billing under the 2026 structure depends on transmission days: 16–30 days in a 30-day period bills CPT 99454, and 2–15 days bills the newer 99445. A connectivity model that quietly costs your panel a few transmission days per month moves patients between codes — or out of billability entirely. Ask vendors for real transmission-day distributions from comparable patient populations, not marketing claims.
How deep does the EHR integration actually go?
"We integrate with your EHR" is the most elastic sentence in RPM sales. Pin it down:
- Bidirectional integration means monitoring data, documentation, and time logs flow into the patient's chart as structured data, and patient context flows back to the monitoring platform. This is the standard worth demanding.
- Document-push integration drops a PDF summary into the chart. Better than nothing; invisible to anything that consumes structured data.
- CSV export means a staff member downloads spreadsheets and uploads them somewhere. This is not integration; it is a manual process with extra steps.
Ask specifically: which EHRs are live today — not on the roadmap — and can the vendor demonstrate the integration in your EHR during the demo? Ask where the monthly time log and the transmission-day record land, because those two artifacts are what an auditor will ask for.
Who performs the monitoring: the vendor's clinical team or your own staff?
RPM companies offer two basic staffing models, and both are legitimate. The right answer depends on your practice, not on ideology.
A vendor clinical team reviews readings, calls patients, and logs management time on your behalf. The appeal is turnkey scale: no hiring, no coverage gaps, predictable capacity as the panel grows. The evaluation questions are about oversight and continuity — how the vendor's staff coordinate with your practitioners, how escalations reach you, and how the documentation trail shows your practice's involvement in management decisions.
Your own clinical staff on the vendor's platform keeps the monitoring work with the nurses and medical assistants who already know your patients, using the vendor's software for alerting, time tracking, and documentation. The appeal is continuity and control; the evaluation questions are about capacity — whether your staffing can absorb the monthly management workload as enrollment grows, and whether the platform makes their time efficient.
Some practices run hybrids — vendor coverage for after-hours or overflow, practice staff for their own panel. Whichever model you choose, insist on seeing exactly how the platform documents who did what, when, and for how long.
What billing support should you expect?
RPM billing rewards precision, and the vendor's job is to make precision easy. Minimum expectations:
- Transmission-day reports per 30-day period, accurate and archivable, since the day count now selects between 99445 and 99454.
- Per-calendar-month time logs with dated entries, activities, and the staff member who performed them.
- Code-selection logic that reflects the 2026 rules, including the pairing prohibitions — never both device-supply codes in one period, never both management codes in one month.
- Claim-ready outputs and denial support, including what the vendor provides when a payer asks for records.
A useful test: ask the vendor to walk through how their reporting handles a month where a patient transmitted 14 days and received 12 minutes of management. If the answer is not immediate and specific, the billing support is thinner than the brochure. For the full code-level detail your billing team will need regardless of vendor, see the current 2026 rule changes overview.
What should alert workflows look like?
Monitoring without a disciplined response pathway is liability, not care. Evaluate:
- Configurable thresholds per patient, not one-size-fits-all defaults.
- A defined triage path — who sees the alert first, how it escalates to a practitioner, and within what timeframe.
- Documentation of the response, so the chart shows what was done about the reading, not just that it arrived.
- Noise management. Ask what fraction of alerts in comparable practices are actionable. Platforms that page staff for every borderline reading train everyone to ignore alerts.
How will patients get enrolled and stay engaged?
Enrollment is where RPM programs stall. Ask who identifies eligible patients, who obtains and documents consent, who educates the patient on the device, and — most predictive of long-term results — what happens when a patient stops transmitting. A vendor with a real engagement operation can describe its outreach cadence for non-transmitting patients and show re-engagement numbers. A vendor without one will describe the dashboard where you can see the problem yourself.
How are RPM companies priced?
Common structures include per-patient-per-month platform fees, device purchase versus device-included models, and tiers based on service level (software only versus software plus clinical staffing). Rather than comparing list prices, compare total cost per successfully billed patient-month — a cheap platform that produces fewer billable months is not cheap. Ask every finalist to model your expected panel with their real adherence numbers, and check how the contract handles patients who disenroll or stop transmitting.
What implementation and audit support should you expect?
The contract signing is the midpoint of vendor evaluation, not the end. Ask what the first ninety days look like: who configures alert thresholds and documentation templates, who trains your staff and on what schedule, whether the vendor supports a deliberate first cohort before full-panel enrollment, and who is accountable when the first claims cycle surfaces gaps between the platform's reports and your billing system.
Then ask the audit question directly: if a payer requests complete records for one patient-month two years from now, what can the vendor produce, how fast, and in what format? The answer should be a single coherent package — transmission-day report, dated time log, alert history with responses, consent documentation — not a scavenger hunt across dashboards. Ask how long records are retained after a patient disenrolls or the contract ends, and get the export rights in writing.
What red flags should end the conversation?
Some answers should stop an evaluation regardless of price:
- Guaranteed revenue claims. Any vendor promising specific reimbursement amounts is either ignoring adherence reality or inviting you to.
- Enrollment without your practitioners. Programs where the vendor identifies and enrolls patients with minimal involvement from the treating practitioner are a compliance posture problem, whatever the paperwork says.
- Vague answers about who performs clinical work. If you cannot get a clear statement of who reviews readings and logs time under each staffing model, the documentation trail will be equally unclear.
- Integration answers that start with "roadmap." Live means demonstrable today, in your EHR.
- No references in your specialty and size range. A vendor who cannot produce comparable references is asking you to be one.
What questions should you ask in every demo?
- Which EHRs are live today, and can you show mine, now?
- What is the actual distribution of transmission days across your current patients?
- Show me the audit trail for one patient-month: transmission days, time log, alert responses.
- Who performs clinical monitoring in each of your staffing models, and how is our practitioner's oversight documented?
- How does your platform prevent billing both codes of a pairing — 99445 with 99454, or the two management codes — in the same period?
- What is your patient re-engagement process, and what are its results?
- What happens to our data and devices if we terminate?
- Which references can I call at practices of my size and specialty?
Where does Neuvora fit?
Neuvora is one of the options worth evaluating against this checklist, and we would rather be measured by it than exempted from it. The platform runs on cellular devices, integrates bidirectionally with Tebra, PrognoCIS, and eClinicalWorks today, and supports both staffing models — practices whose own nurses and medical assistants run monitoring inside the software with full time tracking and documentation, and practices that want clinical support behind the platform. The program is physician-led, and the RPM service overview describes how it works in practice.
If you are building a shortlist, our partners page shows the ecosystem we work in, and you can talk to our team — ideally with this checklist in hand.
The bottom line
The right RPM company is the one whose devices your patients will actually use, whose data lands in your EHR as structured, auditable records, whose staffing model fits your practice, and whose reporting makes the 2026 billing rules easy to follow rather than easy to violate. Run every vendor — including us — through the same questions, and weight real transmission and engagement data over any demo's polish.
This article is general billing information, not billing, legal, or medical advice. Verify current rates and payer policies against the CMS Physician Fee Schedule and your MAC before billing.
