Relay · Developer guide

Clinical devices and wearables, one integration.

Relay connects Scanbo D8, supported wearables, and health platforms to the applications and workflows your team already uses.

Overview

Relay is the data transport layer for connected clinical devices and wearables. It receives authorized readings, normalizes them into a consistent structure, and makes them available to your application through an API or webhook.

Relay does not diagnose, interpret, or make clinical decisions. Your application and clinical team remain responsible for how readings are displayed, reviewed, and used.

1. Authorized connection

The patient authorizes Scanbo D8 or a supported wearable before data is connected. Relay uses that authorization to establish the permitted connection and receive the selected readings.

Scanbo D8AuthorizedSupported wearableAuthorized

Only the data required for the connected workflow should be requested. Your application should clearly communicate what device data is being connected and why.

2. Standardized data

Different devices can describe the same measurement in different ways. Relay maps supported readings into a consistent structure so your application does not need a separate integration for every device.

Readings can be delivered as JSON or as HL7 FHIR R4 Observations. A simplified JSON example looks like this:

{
  "reading": "blood pressure",
  "systolic": 118,
  "diastolic": 76,
  "unit": "mmHg",
  "patient": "demo-patient-0042"
}

Real payloads may include additional identifiers, timestamps, device metadata, units, and provenance required by the connected workflow.

3. API and webhook delivery

Use webhooks when your application should be notified as soon as a new reading is available. Your endpoint receives an event and can then retrieve the associated record.

Use the API when your application needs to query readings on demand, synchronize records, or retrieve data for a specific patient or device connection.

Typical flowAuthorize connection → receive event → query record → display or route the reading in your application.

relay.vital.receivedWebhook event for a new reading

getReportAPI query for the connected record

externalPatientIdYour application’s patient reference

4. Your application

Your application is responsible for authenticating requests, validating incoming data, handling retries, and deciding how readings move through your workflow.

Verify webhook signatures and reject unauthorized requests.
Store only the data your workflow requires.
Handle duplicate events and temporary delivery failures safely.
Show timestamps, units, and source information where appropriate.
Keep clinical review and decisions with qualified professionals.

Launching soonDeveloper access details, credentials, and endpoint documentation will be available at launch.