If your hospital's patient monitoring strategy relies on nurses walking into rooms every hour, you're already behind—and not by much. That's not a sales pitch, that's a math problem. As of January 2025, a single fall in a 50-bed unit costs an average of $14,000 in unreimbursed care. A single central line infection can cost $45,000. Remote monitoring doesn't fix everything, but it's the single biggest leverage point for improving outcomes with the staff you already have.
I work in quality and compliance at a medical device company—Smiths Medical—where I review specifications for infusion pumps, respiratory devices, and monitoring components. I've reviewed roughly 200 unique device specifications in the past year, and I've rejected about 15% of first-round vendor submissions for not meeting our tolerance standards. I'm not a clinician, but I've seen what happens when specs are wrong versus when they're right.
The Big Misconception: 'We're Too Small for RPM'
When I first started digging into remote patient monitoring (RPM) back in 2022, I assumed it was a tool exclusively for large health systems with dedicated IT teams. You know, the kind that have entire floors dedicated to telemetry. I figured smaller hospitals—say, 50 to 150 beds—would get priced out or overwhelmed by the complexity. That's what the vendors told us, anyway. 'Our platform is designed for integrated delivery networks.'
Then I visited a critical access hospital in rural Kansas that was doing RPM for six patients with a single tablet and a Bluetooth pulse oximeter. They weren't using our equipment—they were using a consumer-grade system—but the principle was the same. And that's when I realized the assumption was dead wrong. The barrier isn't technology. It's procurement.
Small hospitals don't need a $500,000 RPM platform. They need a $5,000 starter kit and a willingness to change one workflow. (Should mention: by 'starter kit' I mean a hub device, 10-15 patient monitors, and a software subscription—not an enterprise EMR integration. You don't need the full Monty on day one.)
Where Smiths-Medical Devices Fit Into This Picture
This is where I have to be careful. I can't claim our devices are perfect—no medical device is—but I can tell you what we've learned from integrating our infusion pumps and patient monitoring components into small-scale RPM setups.
Our Medfusion 4000 syringe pump, for example, has a setting that logs infusion data to a serial port—not a fancy feature, just a practical one. In Q3 2024, one of our OEM partners built a bridge module that takes that serial data and pushes it to a cloud dashboard. The cost was around $800 for the module, plus $50 per month for the cloud service. That's not nothing, but compare that to the alternative: a nurse walking into the ICU every 15 minutes to check pump status, or a delay in noticing an occlusion.
I've seen this work in practice. On a 50,000-unit annual order for one of our catheter products, the feedback loop from remote monitoring data directly influenced the design of our strain relief—a detail most people wouldn't think about. But that's the point: integration creates data, and data creates better specs.
For smaller hospitals looking at RPM for the first time, I'd suggest starting with one device type and one patient population. Maybe it's continuous pulse oximetry for post-surgical patients on our CADD Solis pump. Maybe it's temperature monitoring for chemo patients. Don't try to do everything at once.
What I Got Wrong About Power Wheelchairs and RPM
Here's a confession: when people asked about remote monitoring for power wheelchairs, I used to dismiss it. 'A wheelchair's a mobility device, not a monitoring device,' I'd say. That was a bad take.
In Q1 2024, I ran a blind test with our rehab engineering team—same chair design with and without a basic sensor system that logged usage hours, battery status, and pressure distribution. 100% of clinicians identified the instrumented chair as 'more informative for care planning' without knowing which was which. The cost increase was $120 per unit. For a 200-unit fleet, that's $24,000 for data you can't get any other way.
The point isn't that power wheelchairs need to be online. The point is that if you're already buying wheelchairs, adding a $120 sensor is cheap compared to the long-term cost of pressure injuries or falls that go unnoticed. But I'll admit—I was wrong about it being a niche concern. It's actually a practical entry point for small facilities.
How a CT Scanner Works (And Why It's Not Relevant Here)
People sometimes ask me, 'How does a CT scanner work?' from a monitoring perspective—whether it can be integrated into RPM. The short answer: not really, and you probably don't want it to be.
CT scanners are diagnostic tools, not monitoring tools. They generate images, not continuous patient data. I'm not a radiologist, so I can't speak to the granulation of image acquisition, but from a device interoperability standpoint, a CT scanner talks to a PACS system, not to a patient monitoring dashboard. If a vendor tells you their RPM platform can 'integrate with any CT,' they're overselling the feature set.
What can be integrated is the patient's vitals during the scan—heart rate, SpO2, maybe blood pressure if the CT has a monitoring port. But that's not a CT function; that's a patient monitor that happens to be near the CT. Don't confuse the two.
(Should mention: this gets into device interoperability standards like HL7 and FHIR, which isn't my expertise. I'd recommend consulting your clinical engineering team before making any integration decisions.)
Practical Advice: Where to Start
If you're a small hospital, a clinic, or even a home health agency looking at RPM, here's what I'd recommend based on what I've seen work (and fail):
- Start with vitals monitoring for high-risk patients. Post-op, chronic disease, elderly. These are the patients where a 30-minute delay in noticing a change matters.
- Don't over-spec the first deployment. You don't need 12-lead ECG, invasive blood pressure, and capnography. You need SpO2, heart rate, and maybe temperature. That covers 80% of the monitoring needs. Add complexity later.
- Verify everything with your team. In Q3 2024, we tested four different consumer-grade pulse oximeters against our clinical-grade specs. Three out of four failed the SpO2 accuracy test at low perfusion—a known issue, but it's the kind of detail that kills a project.
- Budget for the subscription, not just the hardware. The hardware is a one-time cost; the software and cloud service are ongoing. I've seen projects die six months in because no one budgeted for the monthly fee.
The Limit of My Experience
A final caveat: my experience is based on about 200 device specification reviews, mostly in the U.S. domestic market. If you're working with international vendors or in a regulatory environment like the EU MDR, your experience might differ significantly—particularly around data privacy and device registration.
A lot of this advice also assumes you have at least one clinician who can interpret the data. Remote monitoring generates alerts, but alerts aren't diagnoses. If your facility is extremely small—like a 10-bed rural clinic—the ROI might not be there. I want to say it scales down well, but don't quote me on that without running your own patient volume numbers.
Prices as of January 2025; verify current rates at your preferred medical device distributor. And for the love of good procurement, don't let a vendor sell you a platform with features you'll never use.
