Skip to content

Quick Start

ATH IoT platform seamlessly and securely connects health devices to health records through cellular hub or mobile app without complex setup. Records exchange schema can be customized or comply with HL7 FHIR standard.

Sign In

Hub

  • The hub is like a Bluetooth small gateway that supports 4G backhaul, it can be connected to various medical monitoring devices, such as oximeters, blood pressure monitors, etc.
  • By adding a hub through the ATH IoT platform, patient data from these health devices can be collected in real time and sent to the endpoints configured on the platform for remote monitoring and management by healthcare teams.
  • The Hub Group column shows the Hub affiliation

Alt text

Add a hub

Both the ID and the group are mandatory.
Note: If the group is not clearly selected, the group will be classified into the Default group Alt text

Actions for each hub

Alt text

1. Ping

Detects the status of the hub

2. Messages and Bound Devices

On this page, you can view the hub’s most recent measurements, status, hub group and bounded devices.
Alt text

Device Message

1. Click the "Refresh" button to get the latest messages, double-click to auto refresh every 5 seconds
2. Click the "Fold" or "UnFold" button to view these message values more clearly

Alt text

Bound Devices

Automatic every 5 seconds

Alt text

3. Delete

Change a Hub’s Group

Enter the hub's detail page, and select the desired hub group to move the hub group into.

Alt text You will be prompted to confirm your changes and list the endpoints of the new hub group for you to verify.

  • Click "Confirm" to move the group, and then all measurements coming from this hub will now be sent to the following endpoints.
  • Alternatively, click "Cancel" to keep the Hub in it's original group, messages coming from this hub will continue be sent to original endpoints.

Alt text

Hub Group

A hub group is used as the control center to centrally associate and manage multiple hubs and endpoints. A hub group can be configured with multiple endpoints, and measurements are sent to all of them simultaneously, enabling you to send data to multiple systems.

There will always be a hub group named "Default", that all of your hubs will be assigned in by default.
Unless you move the group manually

Alt text

Here's what you should notice :

  1. A hub group can have multiple endpoints configured and also can be associated with multiple hubs.
  2. A hub will always belong to exactly one hub group. Therefore, when you add a hub, it will be placed in your default hub group prior to delivery.
  3. You cannot change or delete the "Default" group, but you can customize your other groups as your wish.

Add a group

Alt text

Associate Endpoints

Click the "Associate" icon under the Action column of any group in the table, Select endpoints and click "Confirm" to associate all of these selected endpoints to the group, and click "Cancel" to remain the old association Alt text

Endpoint

Measurement data from the hub will be delivered by the platform to these associated endpoint urls in real time. In order to receive these messages, ATH needs to set up a JSON-based REST endpoint.

Add an endpoint

For security reasons, it is recommended that you use a random alphanumeric token that will be passed in each request. An example endpoint might look like https://example.com/ath?token=ABC12345.

Header Token

Alt text

Query Param Token

Alt text

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

    This endpoint should have a valid, commercially signed SSL certificate with an appropriate Subject or Subject Alternative Name to match the corresponding DNS address.

    Note:

    If the endpoint creation fails, please make sure the url uses https and is accessible.

  • Accepts an authentication token in one of the following formats:

    Header Token (for example):

    {
  "Authorization": "Token ABCD1234"
}

    Query Param Token (for example):

    The param name and token value will be stitched together into a complete url like https://your.example.endpoint.com/?token=ABCD1234

  • If the request is successful, a successful status and response message are returned (e.g. {"status":"ok"} or {}).

To receive messages to your endpoint, it needs to be configured on a hub group. To learn more about how to configure, you can go back to the section of "Hub" and "Hub Group".

Endpoint logs

Alt text

Click the "Fold" or "UnFold" button to view these message values more clearly

Alt text

Resend

Select some messages and the table will display a "Resend" link, then you can resend these messages again.

  • Both success and failure messages can be resend.
  • Resending messages can only be sent to the endpoint that triggered the action.

Alt text