BLOGS 
NEWSROOM 
CASE STUDIES 
WEBINARS 
PODCASTS 
ASSET HUB 
EVENT CALENDAR 
TL;DR
- This is a categorized reference of every major RPM device type available in 2026, organized by clinical category and connectivity type.
- Each entry covers what the device measures, how its data moves, whether it meets CMS 99454 billing requirements, and the company behind it.
- Mindbowser’s engineering team has integrated 23 different devices and wearables into RPM platforms across BLE, cellular, WiFi, and HealthKit protocols.
- This guide is compiled from that integration experience and verified by the review team.
Over the past three years, Mindbowser has integrated 23 medical devices and consumer wearables into RPM platforms across BLE, cellular, WiFi, and HealthKit protocols.
The device spec sheet rarely predicted which integrations would succeed in production.
Devices that performed cleanly in vendor demos often broke in production environments. Devices with less polished documentation sometimes delivered the most reliable data pipelines.
The single biggest predictor of integration success had nothing to do with the device itself. It was whether the data reached the care team in a format they could act on between patient visits.
This guide covers every major RPM device category in 2026. Unlike standard vendor lists, each device entry includes:
- Company background and scale
- Connectivity method
- CMS billing eligibility
- Production integration considerations
How to Read This Device Guide
RPM devices are organized along two axes.
Clinical Category
What the device monitors:
- Blood pressure
- Glucose
- Oxygen saturation
- Cardiac rhythm
- Weight
- Activity
- Respiratory function
Device Tier
- Clinical-grade: FDA-cleared or clinically validated devices designed for monitoring programs and eligible for CMS 99454 billing
- Consumer wearable: Consumer products with FDA-cleared features such as Apple Watch ECG or Fitbit irregular rhythm detection. Billing eligibility depends on how the data flows into the RPM platform
- Emerging or investigational: Clinically promising devices not yet validated for reimbursed RPM workflows
Connectivity Types
- Cellular: Data transmits over a cellular network without requiring a patient’s smartphone
- BLE (Bluetooth Low Energy): Device connects to a patient’s smartphone and syncs through an app
- Hub-based: BLE devices connect to a home gateway that relays data through WiFi or cellular
- Cloud API: Data already exists in the manufacturer’s cloud and is pulled into the RPM platform via API
Each device entry below explains:
- What the device measures
- How the data moves
- Whether CMS reimburses for it
- What Mindbowser learned from production integrations
Blood Pressure Monitors
Hypertension remains the largest RPM use case by patient volume, affecting approximately 119.9 million Americans or 47.7% of adults.
The blood pressure cuff is still the most widely deployed RPM device category.
For clinical protocols and reimbursement guidance, read our Remote Blood Pressure Monitoring Guide.
| Device | Type | Connectivity | Readings | FDA | CMS 99454 | Estimated Cost |
|---|---|---|---|---|---|---|
| Omron Complete (BP + ECG) | Clinical | BLE | On-demand | Cleared | Yes | $100–130 |
| Omron Platinum | Clinical | BLE | On-demand | Cleared | Yes | $60–80 |
| Tenovi BP Cuff | Clinical | Cellular | On-demand | Cleared | Yes | $80–120 |
| BodyTrace BP | Clinical | Cellular | On-demand | Cleared | Yes | $90–130 |
| Withings BPM Connect | Clinical | BLE + WiFi | On-demand | Cleared | Yes | $100–130 |
| iHealth Track | Clinical | BLE | On-demand | Cleared | Yes | $30–50 |
| Omron EVOLV (Wrist) | Emerging | BLE | On-demand | Cleared | Pending Validation | $130–170 |
| Samsung Galaxy Watch BP | Consumer | BLE | On-demand | Select Markets | No (US) | $250–400 |
Company Intelligence
Omron Healthcare
Subsidiary of Omron Corporation (TYO: 6645)
Omron is the dominant global brand in home blood pressure monitoring. Its devices are widely trusted by both providers and patients, making them a default choice for large-scale RPM deployments.
Tenovi
Private company, Series A
Tenovi specializes in cellular-connected RPM devices that do not require patient smartphones. This makes the company especially valuable for elderly populations and low-tech patient cohorts.
Withings
Private company
Withings offers one of the most developer-friendly APIs in the RPM ecosystem. BPM Connect consistently performs well in production integrations and is commonly paired with connected scales and sleep devices.
Continuous Glucose Monitors (CGMs)
Diabetes remains one of the largest RPM revenue opportunities. CGMs generate continuous patient data streams, with some devices producing up to 288 readings per day.
For clinical outcomes and integration architecture, see our Diabetes Remote Patient Monitoring Guide.
| Device | Type | Connectivity | Readings | Sensor Wear | FDA | CMS 99454 | Estimated Monthly Cost |
|---|---|---|---|---|---|---|---|
| Dexcom G7 | Clinical | BLE to Phone → Cloud API | Every 5 minutes | 10 days | Cleared | Yes | $75–100 |
| Abbott FreeStyle Libre 3 | Clinical | BLE to Phone → Cloud | Every 1 minute | 14 days | Cleared | Yes | $65–85 |
| Medtronic Guardian 4 | Clinical | BLE to Pump/Phone | Every 5 minutes | 7 days | Cleared | Yes | $80–120 |
| Dexcom Stelo | Consumer OTC | BLE to Phone → Cloud API | Every 5 minutes | 15 days | OTC Cleared | Yes | $49–99 |
Company Intelligence
Dexcom
Dexcom remains the CGM market leader with one of the strongest developer ecosystems in healthcare. Its API infrastructure supports near real-time glucose data access and integrates cleanly into RPM workflows.
Abbott
Abbott’s FreeStyle Libre product line is one of the most widely deployed CGMs globally. Libre 3 delivers high-frequency readings and lower per-sensor costs, making it attractive for enterprise-scale RPM programs.
Medtronic
Medtronic’s Guardian platform is tightly integrated with insulin pump systems. The ecosystem works well for closed-loop diabetes care but is more siloed than Dexcom or Abbott.
Pulse Oximeters and Respiratory Monitors
COPD remains one of the largest chronic RPM categories by patient volume. SpO2 is among the most predictive biomarkers for detecting COPD exacerbation risk remotely.
Read our COPD Remote Patient Monitoring Guide for clinical thresholds and care workflows.
| Device | Type | Connectivity | Monitoring Mode | FDA | CMS 99454 | Estimated Cost |
|---|---|---|---|---|---|---|
| Masimo MightySat | Clinical | BLE | Spot-check + Continuous | Cleared | Yes | $300–400 |
| Nonin 3230 | Clinical | BLE | Spot-check | Cleared | Yes | $200–300 |
| Wellue O2Ring | Clinical | BLE | Overnight Continuous | Cleared | Yes | $100–160 |
| Strados RESP Biosensor | Clinical | BLE | Continuous Lung Sounds | Cleared | Yes | ~$500 |
| Vitalograph Lung Monitor | Clinical | BLE | Spirometry | Cleared | Yes | $200–400 |
| NuvoAir Air Next | Clinical | BLE | Spirometry | Cleared | Yes | $50–80 |
| Propeller Health | Clinical | BLE | Medication Adherence | Cleared | Yes | $30–80 |
Consumer Wearables with Clinical Applications
Consumer wearables occupy a middle ground between wellness products and clinical monitoring devices.
The core RPM question is whether wearable data can flow into a clinical monitoring platform in a billable, actionable format.
For RPM platforms, Apple HealthKit and Google Health Connect are often the fastest integration paths because they aggregate data from multiple consumer devices into a single interface.
Cellular vs Bluetooth vs Hub vs Cloud API
The connectivity decision affects:
- Patient compliance
- Data reliability
- Support burden
- Integration architecture
Based on Mindbowser’s production experience:
- Cellular devices perform best for patients over 60
- BLE works well for digital-native users
- Cloud APIs are ideal when patients already own devices
- Hub-based systems remain relevant for multi-device home monitoring
- Device Aggregation APIs: Terra, Validic, and Native Integration
Supporting multiple RPM devices means supporting multiple integration points, protocols, and data formats.
Aggregation APIs normalize those data streams into a single pipeline.
Terra API
Terra supports Apple HealthKit, Google Health Connect, Garmin, Fitbit, Oura, WHOOP, Samsung, Polar, and other wearable ecosystems.
It is best suited for startups and digital health companies building multi-wearable platforms.
Validic
Validic supports more than 600 connected devices and includes EHR integration capabilities for enterprise healthcare deployments.
It is commonly selected by health systems that need enterprise-scale device aggregation.
Apple HealthKit and Google Health Connect
These native frameworks aggregate consumer health data directly on the patient device.
HealthKit remains one of the fastest paths to multi-device integration when an RPM platform already has a patient-facing mobile app.
When to Use Aggregation vs Native Integration
- Consumer wearables: Use aggregation APIs
- Clinical-grade devices: Native integration often gives better reliability and control
- CGMs: Native integration is usually preferred for near real-time glucose workflows
ConnectHealth is Mindbowser’s normalization layer for aggregated and native device data, standardizing timestamps, sampling rates, and patient monitoring views.
Read more in our upcoming Terra vs Validic Deep Dive.
Which Devices Map to Which Conditions?
Most RPM programs underestimate the complexity of multi-condition monitoring.
A patient with diabetes, hypertension, and CKD may require glucose, blood pressure, and weight data flowing into a unified clinical dashboard with multiple alert thresholds.
What Makes a Device CMS 99454 Eligible?
CMS does not maintain a published list of approved RPM devices.
Instead, eligibility depends on whether the device digitally transmits health data to the practitioner’s monitoring system.
1. Digital Data Transmission
The device must transmit data electronically. Manual logging does not qualify.
2. Daily Recording Capability
For CPT 99454, the device must support at least 16 days of recorded data within a 30-day period.
The 2026 short-duration RPM code 99445 lowers this threshold to 2–15 days.
3. Practitioner Access
The data must reach the practitioner’s monitoring platform.
This is why data flow architecture matters for consumer wearables such as Apple Watch or Fitbit.
FDA clearance is not mandatory for RPM reimbursement, but clinically validated devices reduce operational and liability risk.
The Device Is Commodity. The Integration Is the Product.
Every RPM device will continue becoming cheaper, smaller, and more accurate.
The harder problem is not selecting the device. It is deciding what happens after the reading leaves the device.
- Does the data reach the care team in time to change a clinical decision?
- Does it flow into the EHR where physicians already work?
- Does it generate reimbursable RPM events under the correct CPT codes?
For healthcare organizations evaluating RPM infrastructure and device integrations, Mindbowser provides implementation guidance based on real production deployments across clinical and consumer ecosystems.
Conclusion
RPM success is no longer defined by the device alone. Blood pressure cuffs, CGMs, pulse oximeters, ECG patches, connected scales, and consumer wearables are becoming more accessible, more accurate, and easier to deploy.
The real differentiator is what happens after the reading is captured.
For a remote patient monitoring program to work, device data must move reliably from the patient to the care team, appear in a usable clinical workflow, support timely intervention, and meet CMS billing requirements. A device that collects accurate data but fails to deliver it into the practitioner’s monitoring system creates operational burden instead of clinical value.
That is why integration architecture matters. Cellular devices may work best for older or low-tech populations. BLE devices may fit digitally engaged patients. Cloud APIs may be ideal when patients already own CGMs or wearables. Aggregation layers such as HealthKit, Google Health Connect, Terra, and Validic can simplify multi-device programs, but only when the data is normalized and actionable.
For providers and digital health companies building RPM programs in 2026, the priority should be clear: choose devices based on patient population, clinical protocol, reimbursement fit, and integration reliability.
The device is only the starting point. The RPM platform, data pipeline, alert logic, EHR workflow, and care team dashboard are what turn remote readings into measurable outcomes.
