What is a medical device connectivity hub?

A simple definition

A medical device connectivity hub sits in the patient's home, near their devices. When the patient takes a measurement with a compatible device, such as a blood pressure monitor, a pulse oximeter or a scale, the hub collects the reading and sends it over the internet to the platform used by the care team.

In other words, the hub does the job that would otherwise fall to a patient app: receiving the reading from the device and passing it on.

What it changes for patients

• No app to install, update or sign in to.
• No pairing to repeat, and no phone that must stay nearby.
• No reading to send or confirm by hand.

After the initial setup, the routine is the device itself. That matters most for people who find smartphones difficult, and for anyone who simply forgets to open an app.

What it changes for organizations

For the team running the program, a hub concentrates technical work at the start instead of spreading it across every reading. For the platform receiving the data, a good hub delivers readings from different devices in one consistent format, so adding a device doesn't mean adding a new integration.

What a hub is not

A hub is not a clinical tool. It doesn't interpret readings or make care decisions; those stay with the care team and the platform they use. It also doesn't remove the need for setup: the hub, devices and internet connection are prepared once.

Questions to ask a provider

1. Which devices are compatible, and how is compatibility confirmed for exact models?
2. How does the hub connect to the internet in the home?
3. What does our platform receive, and is the format the same across devices?
4. How are readings associated with the right patient?
5. Who handles setup, replacements and support, and how is that documented?
6. What security and data requirements are covered in the integration review?