Skip to main content
This guide is for teams connecting Stealthera to a hospital information system (HIS), electronic medical record (EMR), or a monitoring dashboard.

​
Integration model

Stealthera is a pull-based API. Your platform calls the endpoints on a schedule and stores or displays the results. Stealthera handles all device communication and data normalization — you only consume the REST endpoints.
Prefer the grouped endpoints so you fetch related metrics in a single call rather than one request per metric.

​
Polling cadence

Sampling and upload intervals are configurable per deployment. As a starting point:
The updateTime / lastSeen field tells you when a device last reported. If it stops advancing, the device is offline or out of coverage — surface this in your dashboard.

​
Device-to-patient mapping

Each device is identified by its deviceId (the watch IMEI). In this version, map deviceId to a patient record on your side and keep the assignment history in your system, so historical readings stay attributed to the correct patient. A nickname field is available as a human-readable label.
A built-in patient registry and assignment-history workflow is planned for a future version. Until then, treat deviceId as the stable key.

​
Handling alarms and SOS

For emergency response, poll GET /api/alarms (or the per-device GET /api/device/{deviceId}/safety) on a short interval and route events by type. Critical types include Fall, SOS, Heart rate warning, Blood pressure warning, and Blood oxygen warning. SOS events from GET /api/device/{deviceId}/sos include the location and any associated call logs.

​
Timestamps and empty states

  • All timestamps are India Standard Time (UTC+05:30), formatted YYYY-MM-DD HH:mm:ss.
  • A metric with no data for the requested day returns an empty array ([]) for list fields and null for summary values, with a 200 status. Empty states are not errors — see Error Codes.