A Bluetooth medical device SDK for health apps.
Build a connected-device path into a healthcare product with the Ovok Native SDK. The documentation covers supported devices and Bluetooth workflows; the FHIR backend gives your app a record layer for supported measurements.
Move from device selection to app workflow
- 01
Select a documented device
Check the live supported-device catalogue for the models and measurement types your product needs.
Read the documentation - 02
Follow the Bluetooth guide
Use the Native SDK documentation to evaluate discovery and measurement-handling workflows.
Read the documentation - 03
Connect the product record
Build the patient and practitioner experience around the supported readings in your FHIR workflow.
Check coverage against the catalogue
Documented device range
The current public claim is 50+ supported devices. The live catalogue carries the current model and profile details.
Read the documentationCommon measurement groups
Coverage includes documented blood-pressure, sleep-radar, SpO₂, and urine-analyser devices, plus other supported devices.
React Native integration
The Native SDK is the mobile SDK path for teams building React Native healthcare applications.
Read the documentationSandbox evaluation and live device setup are separate
Developer sandbox
- Use test data to develop the app and evaluate the API.
- Live device ingestion is not enabled by sandbox data alone.
Live ingestion
- Requires setup with the Ovok team through the Ovok IoT Service.
- Confirm your target model and workflow against the catalogue.
Explore solutions for your team.
Compare startup validation, scaleup device workflows, enterprise architecture, and provider-led Hospital at Home, virtual-ward, or Spitex programmes.
Startup teams
Test the mobile and device integration surface before scoping production plans.
Read about Startup teamsScaleup teams
Review device coverage and enrollment choices for a growing monitoring product.
Read about Scaleup teamsStart with the documented Bluetooth path.
Review supported models and SDK requirements, then evaluate the app workflow in the Developer sandbox.