Stel was built to simplify remote patient monitoring for patients and care teams. Stel’s cellular vitals hub transmits data from wireless home vitals devices to care team workflows.

Stel aims to simplify integration for IT teams as well through an API-first, No-PHI Integration. Each Hub has a randomly generated 10-character ID that care teams can associate to a patient. That association is only known by the care team allowing a secure and simple way for Stel to group vitals readings while not requiring PHI or customer data.

High Level Data Flow

https://embed.notionlytics.com/wt/ZXlKd1lXZGxTV1FpT2lJelpXSmlNbVZtTmpsa1lXWTBaV1k0WVRBeE9XUTFPREZoTURVeU9URXdNaUlzSW5kdmNtdHpjR0ZqWlZSeVlXTnJaWEpKWkNJNklrMUhNRUp3Vmt0cloyeG1hV2hHZEdwNE4yeDNJbjA9

Messages sent to the customer’s endpoint contain:

• Hub ID,
• Measurement Type,
• Value, Time, and
• other relevant device information.

Technical Integration Details

Accepting RPM Data from Stel

In order to receive these measurements, Stel’s clients typically expose a JSON-based REST endpoint. This endpoint should have a valid, commercially-signed SSL certificate with a suitable Subject or Subject Alternative Name to match the corresponding DNS address. In order to secure this endpoint, Stel recommends the use of a random alphanumeric token that will be passed along in each of the requests. An example endpoint might look something like https://example.com/stel?token=ABC12345.

Endpoint Requirements

1. HTTPs, with a valid commercially-signed SSL certificate (e.g. DigiCert, Entrust, Let’s Encrypt)

2. Accepts an authentication token in one of the following formats:

   • Header
   • Query String Parameter

3. Responds to POST messages with a 200 or 201 status code and a valid JSON response body if the request is serviced successfully (e.g. {"status":"ok"} or {})

   • If the token is incorrect or cannot be verified, the endpoint should respond with a 401 or 403 status code
   • If the measurement cannot be accepted due to other reasons (e.g. system is under maintenance or otherwise unavailable), an appropriate status code and error message should be returned

4. Responds within 10 seconds. After 10 seconds the request will timeout and will be considered unsuccessful.

   <aside> 💡 If Stel receives an unsuccessful response from the endpoint (including timeouts), the request will be retried up to 6 times. If all 6 retry attempts fail, Stel will stop trying to send the measurement. In this case, please reach out to Stel customer support to resolve the issue.

   </aside>