A Node.js serverless system, architected on AWS Infrastructure, which is responsible for communication between itself and third-party integrators as well as provide and receive data to/from the iOS devices.

For the sake of simplicity, we are going to explain how SureTrac works using two examples:

Qualis, LLC - a company in the Hospice space that contracts with vendors who deliver durable medical equipment to patients as their home or in hospice facilities.

Revive, Inc - a recovery clinic that provides help and services to recovering drug and alcohol patients.

Step 1

The third party client (Qualis and Revive) requests a SureTrac account from AZ Tech.

Currently this is in the form of an email or other non-automated transaction.

If AZ Tech approves, the client receives a link (again via email or otherwise) that allows the client to sign up for an account with an email address and password.

Once the account is created, the client is given a token, which is to be given to the client’s software development team.

This token grants access to the SureTrac GraphQL API as well as authenticates the client.

Step 2

The software development team integrates the client’s software stack with the SureTrac API.

For example:

The Qualis developers would program a connection that uses the SureTrac API to:

Create a new tracking device every time a new driver comes on board
Create a Point of Interest whenever a new order is placed in the system using the shipping address of the order.

The Revive developers would program a connection that uses the SureTrac API to:

Create a new tracking device every time they onboard a new patient in their system
Create a Point of Interest for known “danger zones” their patients like to visit (bars, night clubs, etc)

Additionally, both development teams would write code to respond to messages from SureTrac as well as code to respond to actions taken on the device.

When the system integration creates a Point of Interest, the SureTrac API allows the client to specify a type of distance (Time away in Minutes or Distance away in Miles) and a threshold (5 minutes, 2 miles) and also a URL that SureTrac notifies when there is a breach.

Using Revive as an example, when one of their patients gets within 5 minutes of The Drinker’s Lounge, SureTrac will ping https://revive.com/notify?userId=4&poi=4&distance=4&distanceType=minutes

The URL is completely controlled by Revive, so when SureTrac hits that URL, Revive can:

Do Nothing and respond with a blank message
Log the notification or update the patient record in their system and respond with a blank message
Do Nothing and respond with a message for SureTrac
Log the notification or update the patient record in their system and respond with a message for SureTrac

The optional message must have a Title, Body and Options (each option does something different).

If such a message is provided, the SureTrac app will present the message with the options to the patient.

For Revive, this maybe something like:

Title: Do you need a call?
Body: Bob, we noticed that you are getting close to The Drinker’s Lounge. Would you like to talk to a councilor?
Options: “Yes”, “No”

For Qualis, this maybe something like:

Title: Delivery Notification
Body: Are you delivering an order to 153 NE Sagamore Terrace?
Options: “Yes”, “No”

SureTrac will relay which option was selected back to the client’s system who can take whatever action they want based on the selection.

For example, if the Revive user selects “Yes”, the Revive System can notify a councilor who can then call Bob.

For Qualis, if the driver selects “Yes”, the Qualis system can link the driver to a web page and display a list of items to be delivered and ask the driver to select which items were delivered.