--- title: "MQTT for Remote Patient Monitoring (RPM) Data | ConnectMQ" description: "Move readings from home devices, hubs and bedside gateways to your RPM platform over MQTT, with TLS, per-device credentials and Last Will. Start for free." url: "https://connectmq.com/use-cases/remote-patient-monitoring/" language: "en" --- Use case # Get RPM readings to your care platform Blood pressure cuffs, pulse oximeters, scales and bedside monitors report through a home hub or a hospital gateway. ConnectMQ is the MQTT transport between those devices and the care platform you build and validate — encrypted, per device, and clear about which hub is offline. [Try it free](https://app.connectmq.com/signup) [See pricing](https://connectmq.com/pricing/) No card required Used in - [Healthcare](https://connectmq.com/industries/healthcare/) Example message PUBLISH rpm/clinic-north/pt-7f3a91/bp ``` {"sys":128,"dia":82,"pulse":71,"unit":"mmHg","dev":"bpm-0419","ts":"2026-10-22T07:41:12Z"} ``` QoS 1 · TLS 8883 · PUBACK The problem ## Readings that arrive late, twice or not at all An RPM program lives on data showing up: a home hub on patchy Wi-Fi or LTE, a gateway behind the hospital firewall, a device vendor cloud with its own upload interval. Teams end up stitching together HTTP uploads and vendor APIs, cannot tell a quiet patient from a dead hub, and spend engineering time running message infrastructure instead of the care platform. ## How it works 1. 1 ### Devices take a reading Bluetooth cuffs, oximeters, scales and glucose meters pair with a home hub or the patient app; bedside monitors connect to a hospital gateway. 2. 2 ### The gateway publishes over TLS The hub or gateway publishes each reading with QoS 1 under a pseudonymous patient reference, using its own credentials, and buffers while the connection is down. 3. 3 ### Your platform subscribes Your ingestion service subscribes, stores readings in your own validated systems and hands them to the EHR integration (for example HL7 FHIR) your team runs. 4. 4 ### Care teams follow up Your platform applies the clinical logic your organisation defines. ConnectMQ alerts cover the technical side, such as a hub that has stopped reporting. ConnectMQ ## What it needs from the broker ### Encryption in transit Every connection uses TLS — MQTT on port 8883 or secure WebSockets for web apps — so readings never cross the internet in clear text. ### Per-device credentials and ACLs Each hub or gateway gets its own username and password, limited by per-topic ACLs to its own topics. A lost hub is revoked without touching the rest. ### Delivery you can reason about QoS 1 and persistent sessions mean a reading published while your ingestion service restarts is delivered when it reconnects, not silently dropped. ### Knowing a hub is offline Last Will and a retained status topic tell your platform the moment a hub disconnects, so “no readings” and “no connection” are never confused. ## What you get - One standard transport for every device vendor and gateway - Readings reach your platform in seconds, not on an upload schedule - Offline hubs show up as connectivity issues, not as missing data - No broker to patch, scale or keep running yourself Example topics ``` rpm/clinic-north/pt-7f3a91/bp rpm/clinic-north/pt-7f3a91/spo2 rpm/clinic-north/hub-2231/status (retained) rpm/clinic-north/hub-2231/config (retained) ``` ## Industries that run this use case [![](https://connectmq.com/images/industries/hero/healthcare.webp) Healthcare](https://connectmq.com/industries/healthcare/) ## Related solutions [ ### Connected Products & Smart Hardware Smart devices you ship to your own customers Learn more](https://connectmq.com/connected-products/) ## Frequently asked questions Is MQTT secure enough for remote patient monitoring data? MQTT is a transport; its security depends on how it is set up. On ConnectMQ every connection is encrypted with TLS, each device or gateway has its own credentials, and per-topic ACLs limit what it can publish and read. Use pseudonymous IDs in topics and keep identifiable data in your own systems. Whether the whole solution meets your regulatory obligations is decided by your architecture and your validation, not by the broker alone. Does ConnectMQ make clinical decisions or store patient records? No. ConnectMQ moves messages between devices and your applications. Interpreting readings, clinical alerts, patient records and EHR integration belong to the platform you build and validate — ConnectMQ is one component of it. How do I connect Bluetooth medical devices to MQTT? Most Bluetooth devices cannot speak MQTT themselves. A home hub, a cellular gateway or the patient’s phone app reads the device over Bluetooth and publishes each reading over MQTT. Any standard MQTT library for Android, iOS, Python, Node.js or embedded Linux works with ConnectMQ. ## Build it on ConnectMQ Start on the Free plan — no card required — connect your first devices today and upgrade when you go live. [Get started](https://app.connectmq.com/signup) [See pricing](https://connectmq.com/pricing/) ## More use cases - [Predictive Maintenance](https://connectmq.com/use-cases/predictive-maintenance/) - [Asset Performance Tracking](https://connectmq.com/use-cases/asset-performance-tracking/) - [Industrial Agentic AI Operations](https://connectmq.com/use-cases/industrial-agentic-ai/) - [Energy Management](https://connectmq.com/use-cases/energy-management/) - [Connected Vehicles](https://connectmq.com/use-cases/connected-vehicles/) - [EV Charging Management](https://connectmq.com/use-cases/ev-charging-management/) - [Fleet Management](https://connectmq.com/use-cases/fleet-management/) - [Remote Asset Monitoring](https://connectmq.com/use-cases/remote-asset-monitoring/) - [Tank Level Monitoring](https://connectmq.com/use-cases/tank-level-monitoring/) - [Smart Metering](https://connectmq.com/use-cases/smart-metering/) - [Solar & Wind Farm Monitoring](https://connectmq.com/use-cases/solar-wind-farm-monitoring/) - [Cleanroom & GMP Environmental Monitoring](https://connectmq.com/use-cases/cleanroom-environmental-monitoring/) - [Cold Chain Monitoring](https://connectmq.com/use-cases/cold-chain-monitoring/) - [Hospital Equipment Monitoring & Tracking](https://connectmq.com/use-cases/medical-equipment-tracking/) - [Real-Time Notifications](https://connectmq.com/use-cases/real-time-notifications/) - [Smart Store Operations](https://connectmq.com/use-cases/smart-store-operations/) - [ATM & POS Terminal Monitoring](https://connectmq.com/use-cases/atm-pos-terminal-monitoring/) - [Telecom Network Equipment Monitoring](https://connectmq.com/use-cases/network-equipment-monitoring/) - [IoT Platform for Operators](https://connectmq.com/use-cases/iot-platform-for-operators/) - [Real-Time Market Data](https://connectmq.com/use-cases/real-time-market-data/) - [Agricultural Drones](https://connectmq.com/use-cases/agricultural-drones/) - [Greenhouse IoT Sensors](https://connectmq.com/use-cases/greenhouse-iot-sensors/) - [Data Center Monitoring](https://connectmq.com/data-centers/) - [Smart Irrigation](https://connectmq.com/smart-agriculture/) ## Articles [All articles](https://connectmq.com/blog/) Managed MQTT Cloud ### [How to Choose an IoT MQTT Broker: 12 Criteria and the Questions to Ask Your Vendor](https://connectmq.com/blog/how-to-choose-an-iot-mqtt-broker/) A practical 12-point checklist for choosing an IoT MQTT broker, a table of questions to ask every vendor, and a five-minute hands-on test you can run against broker.connectmq.com. September 21, 20269 min read MQTT Fundamentals ### [MQTT QoS Levels Explained: QoS 0, 1 and 2 with Packet Flows and Examples](https://connectmq.com/blog/mqtt-qos-levels-explained/) A practical guide to MQTT QoS: how QoS 0, 1 and 2 work on the wire, why the delivered QoS can be lower than you asked for, how sessions queue messages and which level to choose for each use case. August 20, 20269 min read MQTT Security ### [MQTT Security Best Practices: A 12-Point Checklist for IoT Teams](https://connectmq.com/blog/mqtt-security-best-practices/) A hands-on MQTT security checklist covering TLS, credentials, client IDs, topic design, payload validation, rate limits and certificate checks, plus how ConnectMQ handles each point. September 28, 202611 min read