.jpg)
Key takeaways
-
A vendor's "cellular" label doesn't guarantee the patient-facing RPM device itself is cellular. It may be a Bluetooth device routed through a separate hub or gateway that's the only truly cellular component in the system.
-
A hub adds a second point of failure on top of the carrier-coverage dependency every cellular device shares: If the hub loses power or its connection, devices paired to it will go offline, interrupting monitoring.
-
CMS's Physician Fee Schedule final rule reduced the billing risk of short monitoring periods by adding a lower-threshold code (99445) paid at the same rate as 99454, but the bigger risk is missed monitoring days affecting patient safety and outcomes.
-
Ask any RPM vendor directly whether the patient-facing device itself is cellular; confirm architecture claims against technical documentation and not just marketing copy.
-
A hub's AC-power requirement means monitoring is more likely to lapse during travel than with a phone-paired Bluetooth device or a fully cellular device, neither of which needs to be plugged in to stay connected.
-
Rural patients with inconsistent coverage may benefit from a cellular device they can reposition or take into town for a stronger signal, an option a stationary, plugged-in hub doesn't allow.
Remote patient monitoring (RPM) vendors describing a device as "cellular" isn't always as straightforward as it sounds. Some devices are cellular end to end. Others are Bluetooth devices that pair to a hub, and only the hub is cellular-connected. Both can get marketed the same way, but they behave differently for a patient day to day, with real consequences for monitoring reliability. This post focuses on what to ask a vendor before taking their connectivity claims at face value, whether you're selecting a vendor for the first time or evaluating whether to switch device partners. Note: For a full breakdown of how cellular, Bluetooth, and hub-based devices compare, see Prevounce's guide to RPM device connectivity types.
What a "Cellular" Gateway Actually Is
A vendor may call this component a hub, a gateway, or just describe the whole system as cellular. Whatever the label, the mechanics are the same: It's a separate piece of hardware that connects to Bluetooth devices on one side and a cellular network on the other. The device a patient physically uses stays Bluetooth no matter how confidently a sales rep uses the word "cellular" to describe the system. That distinction doesn't always show up in marketing and sales copy, which might describe the system as cellular rather than specifying which component the term applies to.
Why This Is Worth Confirming Before Agreeing to a Contract
Every cellular device, whether a single device or a hub connecting several, depends on the same carrier network coverage. That dependency doesn't change based on architecture. What changes is how much a single failure affects. RPM exists to help a care team catch a concerning trend early, such as a blood pressure spike or unexplained weight gain that can signal fluid retention in heart failure patients. A hub that loses power can take every device paired to it offline at once. In addition, a patient who is out of the hub's range when using their device will not have their reading immediately transmitted to their clinician.
Billing carries a smaller version of this risk. CMS's Physician Fee Schedule (PFS) final rule expanded the RPM CPT code set. CPT 99454 still covers 16 to 30 days of transmitted data. The newer CPT 99445 covers 2 to 15 days at the same reimbursement rate, so a device only forfeits that month's reimbursement if transmission falls below 2 days entirely. That's a much lower bar than the old 16-day cliff, but a hub with an extended outage or a patient who does not bring the hub with them during extended travel can still cross it.
Questions to Ask an RPM Vendor About Connectivity
Ask an RPM device vendor these questions before you sign a contract:
-
Is the patient-facing device itself cellular, or does it pair to a separate hub that's the only cellular component? Ask for this in writing, not just on a sales call, since marketing pages often blur the distinction.
-
If there's a hub, what happens to device readings if the hub loses power or its connection?
-
How quickly does the vendor's platform flag a missed or interrupted connection to the care team? A hub failure, whether intentional (unplugged gateway) or unintentional, that goes unnoticed for days means a clinician isn't seeing the blood pressure spike or weight trend that RPM exists to catch.
-
Does the hub require AC power? This determines whether a patient can easily travel with the device or whether monitoring pauses every time they leave home without bringing and plugging in the gateway, for example during an extended stay with family, a rehab facility visit, or seasonal travel.
-
Can the device be repositioned to find a stronger signal, or is it fixed in place once it's plugged in? A cellular device can be moved to a window, a different room, or carried outside to improve reception. A hub tied to an AC outlet stays wherever it was set up. This matters most for rural patients dealing with inconsistent coverage, some of whom get better results carrying a cellular device into town rather than relying on a signal at home.
-
How is the hub prevented from picking up readings from nearby devices it isn't supposed to pair with? This matters most in shared spaces, such as multi-resident households or care facilities, where unrelated Bluetooth devices can be within range.
-
Where does the vendor's technical documentation, not just their marketing page, describe the connection type? Product spec sheets and FDA filings are usually more precise than landing page copy, and any discrepancy between the two is worth asking about directly.
-
Who's responsible for troubleshooting a dropped or unpaired hub, the vendor's support team or practice staff? A hub that needs regular re-pairing creates ongoing support work for someone, and it's worth knowing upfront whether that's you.
What This Means for Your RPM Program
A connectivity failure that delays a clinician from seeing a concerning reading is the real cost of getting RPM device selection wrong. The label "cellular" alone isn't enough information to evaluate an RPM device vendor on. A hub-based device can still work well, but only when two things are true: the patient population is comfortable enough with Bluetooth setup and re-pairing to manage it, or has reliable support when it's needed, and the vendor is transparent about the architecture and can back that up with documentation.
Prevounce's own Pylo device line, including blood pressure monitors, weight scales, blood glucose meters, and pulse oximeters, is built entirely on true cellular connectivity, with no hub, pairing step, or AC power requirement standing between the device and the network. All patients need to do is insert batteries and turn the device on to begin transmitting data. If your organization is actively comparing RPM vendors, see what to know about transitioning to a new RPM vendor for the broader evaluation process. To learn more about Pylo devices and Prevounce's RPM software, schedule your consultation.
Frequently Asked Questions About RPM Vendor Cellular Claims
How can I tell if an RPM device marketed as "cellular" is really Bluetooth on a hub?
Check the specific device model's FDA filing or spec sheet, not the vendor's general marketing pages, and ask the vendor directly whether the patient-facing device connects over cellular or only pairs to a separate hub or gateway.
How does hub-based RPM connectivity affect patients who travel?
A hub that requires AC power typically doesn't travel with a patient the way a phone-paired Bluetooth device or a fully cellular device does. A patient traveling for more than a few days, whether for a family visit, a hospital stay, or seasonal travel, may need to pack the hub, plug it in at the new location, and wait for it to reconnect before monitoring resumes, and staying somewhere with other people nearby can reintroduce the cross-talk risk covered above.
Does a hub-based RPM device still qualify for the same CMS billing codes as a fully cellular device?
Yes. CMS's RPM billing requirements don't specify a device's connectivity architecture; what matters is that the device is FDA-cleared and automatically transmits data. As of CMS's 2026 update, that means CPT 99454 (16 to 30 days of data) or the newer CPT 99445 (2 to 15 days, paid at the same rate). A hub-based device can qualify for either code the same as a fully cellular one, provided it reliably transmits enough days of data.
Should hub-based connectivity disqualify an RPM vendor?
Hub-based connectivity doesn't need to be disqualifying on its own. It can work well for non-rural patients who stay largely in one location and are comfortable with connecting Bluetooth devices. What matters more is whether a vendor discloses the architecture upfront and can answer specific questions about it with documentation, rather than describing every device simply as cellular.
What should I ask if I'm already using a hub-based RPM device?
Confirm how the vendor tracks hub uptime and what happens to monitoring continuity if a hub goes offline mid-month. Ask whether the vendor monitors for missed transmission days at the hub and device level, since a single hub outage can affect several devices at once.