Stel is designed to make it incredibly simple to get data from vitals devices to the people who need them. Patients are sent a Stel Vitals Hub with one or more devices. Stel’s patented passive-pairing OS, means most devices work right out of the box with the Stel hub. Patients simply use their devices and Stel delivers the data to the care teams monitoring those patients.
Best of all, Stel does not store or transmit any PHI. Only the receiving systems know which hubs belong to which patients and can properly associate the data.
https://embed.notionlytics.com/wt/ZXlKd1lXZGxTV1FpT2lKa09EUTNNVEl3TkRSaE1UYzBNR1JpWVRjellXSXhaVFUzWkdKaFpHVmxPU0lzSW5kdmNtdHpjR0ZqWlZSeVlXTnJaWEpKWkNJNklrMUhNRUp3Vmt0cloyeG1hV2hHZEdwNE4yeDNJbjA9
The Vitals Hub running Stel’s proprietary OS is like a gateway for Bluetooth-enabled vitals devices to be able to send data back to the Stel platform. The Hub uses Bluetooth to connect to devices and leverages cellular networks from all major carriers to send the data to Stel’s platform, where it can be routed to its intended destinations.
Vitals devices are used in the vicinity of the Hub to transmit collected data. They can be scales, blood pressure cuffs, thermometers, pulse oximeters, glucometers, spirometers, INR meters, and more! Stel integrates the best devices on the market and we are constantly adding more. Check out our current list of integrated devices. Stel is frequently adding additional devices. If there is a device you’re interested in that you don’t see on the list please contact [email protected].
Measures are the data values collected by devices. Each measure is a set of one or more discrete values collected from a device at a particular time. Measures carry metadata such as device information, the Hub ID, and relevant timestamps. Please see Payload Schemas for more information.
Stel transmits measures in real time to their destinations. To receive the measurements, the destination system must expose an HTTPS endpoint that meets a few simple requirements. To learn more about setting up an endpoint to integrate with Stel check out our Integration Guide. Once you’ve set up your endpoint you can configure it for your organization in our Customer Management Dashboard (CMD).
<aside> 💡 Read on about Hub Groups to understand how to make sure the measurements taken with Hubs get sent to the correct endpoints.
</aside>
Hub Groups are an important organizational concept in Stel. Each Hub must belong to exactly one hub group, no more or less. Hub Groups can have endpoints associated with them and when done so, all the measurements taken with the hubs in that hub group will get sent to those endpoints. Hub groups can be configured with multiple endpoints and measurements will be sent to all of them simultaneously, enabling you to send data to multiple systems, such as an EHR and care management platform.
When you create your Stel organization, you will start with a Default hub group. Whenever you purchase new hubs from Stel, they will be placed in your Default group ahead of delivery. From their you can move the hubs to other groups if desired.
Hub Groups are designed to be flexible and support many different operational workflows. One common use case is to have hub groups for different environments such as test and production, so that certain hubs can be reserved for testing. Another use case is to have separate hub groups for separate patient populations, particularly if they need their data sent to separate systems or processed in different ways, such that distinct endpoints are beneficial.
The default hub group can represent different operational constructs. It could simply be your “production” group (configured with a production endpoint) such that any hub delivered by Stel is ready to go “out of box”. It can also be used to represent a holding tank of inventory on hand with no endpoint configured at all. In that case hubs must be assigned to a different group before being deployed to a patient, but also protects hubs from being used in production unintentionally. The correct setup comes down to your desired clinical and operational workflow.