Connected medical devices, hospital equipment, medication fridges and remote monitoring kits publish over MQTT; your device cloud, RPM platform, CMMS and facility dashboards subscribe. ConnectMQ carries the data — your validated systems decide what to do with it.
No card required
Infusion pumps, monitors, fridges, imaging systems and building systems each report to their own vendor console. Biomedical engineering sees part of the fleet, and nobody sees all of it in one place.
Staff spend time hunting for pumps and wheelchairs, and a medication fridge drifting out of range overnight is often found on the morning round.
Remote monitoring kits sit on home Wi-Fi and cellular links that come and go. A device maker needs messaging that copes with that — without building and running broker infrastructure next to a regulated product.
ConnectMQ is a private MQTT broker you don’t have to operate: devices and gateways publish, your applications subscribe. What you build on top — and how you validate it — stays in your hands.
Each customer gets an isolated broker instance. Your engineers build the device, the gateway and the application — not broker clusters.
TLS on every connection, a username and password per device or gateway, and per-topic ACLs, so a device publishes only its own data and an app reads only what it is allowed to.
Persistent sessions and QoS 1 deliver queued messages when a device reconnects, Last Will tells your platform when one goes offline, and retained config is waiting at every reconnect.
Threshold rules notify facilities or biomed when a vaccine fridge warms, a medical gas pressure drops or a device goes silent — operational alerts, not clinical alarms.
Healthcare teams start where data is operational: remote monitoring data pipes, equipment tracking, cold storage for medicines and vaccines, and the server rooms behind it all.
Readings from home devices, hubs and bedside gateways delivered to your care platform over secure MQTT
Explore the use caseLocation and status of infusion pumps, beds and medication fridges from RTLS gateways and sensors, in one live view
Explore the use caseTemperature, door and location data from reefers, cold rooms and pharma shipments, with alerts on every excursion
Explore the use casePDU, UPS, cooling and rack sensor data for your DCIM and NOC
Explore the use casehospital/north/pharmacy/fridge-07/temperature
hospital/north/rtls/pump-0142/location
devices/{device-id}/telemetry
devices/{device-id}/status (retained)MQTT over TLS with per-device credentials and per-topic ACLs is a solid transport, and ConnectMQ provides those on an isolated broker instance. Whether your solution meets HIPAA, GDPR or medical device requirements depends on the whole system, your contracts and your processes — assess that with your compliance team. Many teams keep identifying patient information out of MQTT payloads and use pseudonymous device IDs.
Devices or a home hub publish readings over MQTT; your RPM platform subscribes, checks and stores them, and an integration engine passes results to the EHR, typically as HL7 v2 messages or FHIR resources. ConnectMQ handles the device-to-platform leg; the clinical logic and the EHR interface are yours.
Yes — many connected devices use MQTT for telemetry, status and configuration. ConnectMQ gives you per-device credentials, retained config and Last Will without running the broker yourself. The device’s regulatory status and the validation of your software stay with you as the manufacturer.
Connect temperature probes to a gateway or Wi-Fi sensor that publishes to topics such as hospital/north/pharmacy/fridge-07/temperature. Threshold rules alert the pharmacy team, retained messages show the last reading on every screen, and your monitoring system subscribes to keep the log.
Start on the Free plan — no card required. Connect a ward, a fridge fleet or your first devices, test it end to end, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
