Choosing a remote patient monitoring system is rarely a single decision. It is really three decisions bundled together — which connectivity method the hardware uses, whether the device carries the right FDA clearance, and whether the practice can actually document its way to CMS reimbursement. Arizona practices evaluating vendors for chronic-condition monitoring programs are finding that the connectivity question alone eliminates half the field before FDA status or billing logistics even come up.
The following breaks down what to check, in the order it actually matters to a practice standing up or expanding an RPM program.
Connectivity Is the First Filter, Not an Afterthought
Every RPM device relies on one of three transmission methods, and the choice determines how much staff time gets spent chasing missing readings. Devices with built-in cellular connectivity — a SIM card embedded in the device itself — transmit data automatically without requiring the patient to own a smartphone, configure Wi-Fi, or pair anything to a hub. That is a meaningful advantage for older patients or those in areas with inconsistent home internet, and it is increasingly treated as the default expectation for RPM hardware rather than a premium feature.
Bluetooth-paired devices are energy-efficient and work well for short-range transmission to a smartphone or dedicated hub, but they require the patient to keep both devices charged, in range, and correctly paired — a real point of failure in programs serving less tech-comfortable populations. Wi-Fi-connected devices lean on the patient’s existing home network, which works fine until the router password changes or the connection drops, at which point the practice has no visibility into why data stopped arriving.
Comparing the Three Connectivity Paths
| Connectivity | Setup burden on patient | Best fit |
|---|---|---|
| Cellular (built-in SIM) | Minimal — works out of the box | Older patients, rural or low-connectivity homes, high-compliance programs |
| Bluetooth | Moderate — pairing to phone or hub required | Tech-comfortable patients with a smartphone they use daily |
| Wi-Fi | Moderate to high — home network configuration required | Patients with stable, practice-verified home internet |
Whichever method a vendor proposes, the platform still needs to integrate with the practice’s EHR so readings land in the clinical workflow rather than a separate portal nobody checks.
FDA Clearance: What the Label Actually Means
Most RPM hardware — blood pressure cuffs, pulse oximeters, glucometers, connected scales — falls into the FDA’s Class II medical device category. These devices are typically described as "FDA-cleared" rather than "FDA-approved," a distinction worth knowing before a vendor conversation. Clearance means the manufacturer demonstrated substantial equivalence to an already-marketed device through the 510(k) premarket notification pathway, along with adherence to Quality System Regulations covering design, manufacturing, and post-market surveillance. FDA approval, by contrast, is the more rigorous process reserved for higher-risk Class III devices, which is not where most RPM hardware sits.
Any software layer that goes beyond displaying readings and generating clinician alerts — software that independently interprets or diagnoses — is classified as Software as a Medical Device and needs its own 510(k) or De Novo clearance. A practice evaluating a vendor should be able to ask for the 510(k) clearance letter, the classification code, and the device’s stated indications for use, and expect a straight answer.
CMS Billing Codes a Practice Has to Track
RPM reimbursement runs on a small set of CPT codes, each with its own trigger condition:
- 99453 covers initial device setup and patient education. It bills once per patient per episode of care, and requires at least two days of data transmission within a 30-day period before it can be submitted.
- 99454 covers supply of the connected device and its data transmission, and requires at least 16 days of automatic transmission within a 30-day billing period.
- A newer code covers device supply for patients who only reach 2–15 days of transmission in that 30-day window — it is mutually exclusive with 99454, so a practice bills one or the other for a given patient in a given period, never both.
- 99457 covers the first 20 minutes of monthly treatment management and interactive communication with the patient; 99458 covers each additional 20-minute increment.
Two requirements sit underneath all of these codes and cause most of the denials: data has to be recorded and transmitted automatically by the device, since manual patient entry generally does not qualify, and CMS expects an established patient-provider relationship before RPM services begin. Practices that get audited successfully tend to keep the same four things on file for every enrolled patient — automated transmission logs, proof of the device’s FDA clearance, documented medical necessity, and a record of the time spent on monthly management.
Data Security Sits Underneath All of This
RPM systems move protected health information continuously, which puts them squarely under HIPAA’s security and privacy requirements. Beyond the baseline compliance question, connected medical device manufacturers are increasingly expected to provide a software bill of materials, run threat modeling and risk assessments, maintain a vulnerability disclosure process, and define how security patches and end-of-life support work. A vendor that cannot answer basic questions about any of these is a vendor a practice should be cautious about onboarding, regardless of how good the hardware looks on a spec sheet.
The Practical Takeaway
None of these three evaluation layers — connectivity, FDA clearance, CMS billing fit — substitutes for the others. A cellular device with clean 510(k) documentation is still a bad fit if its data cadence cannot reliably clear the 16-day threshold for 99454. A well-documented billing workflow does not help if the connectivity method keeps failing for the patient population a practice actually serves. Matching the right hardware and platform to a specific practice’s patient mix, EHR, and billing capacity is exactly the kind of vendor-fit question worth working through with a neutral party rather than taking a single vendor’s pitch at face value.