Data ingestion
Send device and connected-system data into Ovok through the OVOK IoT Service.
Device and connected-system data enters Ovok through the OVOK IoT Service at iot.ovok.com. The service uses mutual TLS (mTLS) to protect the connection.
The Ovok team will help you set up the service and coordinate the connection for your project.
Data path
- A connected device or system sends data through the OVOK IoT Service.
- Ovok associates and stores the data in your project as FHIR resources.
- Your application reads the data through Ovok APIs. For Patients enrolled in Signals, Ovok also forwards eligible vital-sign readings according to the documented Signals forwarding behavior. Do not infer which measurements are forwarded; check the Signals documentation and the IoT service details.
Get set up
Start with the OVOK IoT Service page, then contact your Ovok team to plan and complete the setup. They will guide the connection requirements and help configure the service for your project.
- 1The table lists each device with its linked patient and last update.
- 2Filter by status to narrow the project device list.
Cloud wearables
Patients can also connect their own Oura, WHOOP, Strava, Withings, Polar, Ultrahuman, Suunto or Huawei account. Ovok pulls those readings from the provider's cloud rather than through the IoT Service, and does not forward them to Signals. See Cloud wearables.
Last updated on
Download binary file (deprecated)
Deprecated. Download a file by redirect to a short-lived signed URL, with a bearer token or a public token. Use GET /v1/document/:id or GET /v1/document/public/:token instead.
OVOK IoT Service
Ingest device data through iot.ovok.com, protected by mutual TLS with setup support from the Ovok team.