OVOK IoT Service
Use the OVOK IoT Service to send device and connected-system data into your Ovok project.
| Service detail | Information |
|---|---|
| Host | iot.ovok.com |
| Connection protection | Mutual TLS (mTLS): the client and service authenticate each other during the TLS connection. |
| Setup | The Ovok team will help configure the connection and set it up for your project. |
How the service fits in
Measurements are stored in your Ovok project as FHIR data. Your application continues to use Ovok APIs to read and work with that data. For Patients enrolled in Signals, Ovok forwards eligible vital-sign readings according to the documented Signals forwarding behavior; your application reads the resulting alert decisions through Ovok. Do not infer which measurements are forwarded; check Signals for the current behavior.
Setup with the Ovok team
Contact your Ovok team to arrange onboarding. They will help with the service setup and the mTLS connection requirements for your project.
The IoT connection is mTLS protected. Do not treat iot.ovok.com as an unauthenticated public endpoint. The Ovok team will provide the project-specific connection setup; coordinate with them before sending production data.
What to discuss with the Ovok team
Bring the details of the devices or systems you want to connect and the Ovok project that should receive their data. The team can then work with you on the connection and confirm the project-specific setup.
For the overall ingestion flow, see Data ingestion. For Signals enrollment and alert APIs, see Working with Signals as a connected part of Ovok.