Build digital health on one platform
Ovok gives digital health teams a single place to ship: a FHIR-native API for clinical and consumer apps, a Console for configuring projects and members, and a Data Dashboard for working with the data your products produce.
One platform. Three release tiers. Two operator surfaces. No custom backend to maintain.
What you can build
- Patient-facing apps — sign-up, intake, longitudinal records, remote monitoring, secure messaging.
- Clinical workflows — care plans, encounters, observations, diagnostic reports, scheduling.
- Partner integrations — device fleets, EHR bridges, payer pipelines, analytics exports.
If it lives in a digital health product, you can build it on Ovok without standing up a new server.
How the surfaces fit together
The same API powers every product surface — the Console you sign in to, the Data Dashboard you curate from, and the apps your customers use. There is no second API.
Pick a release tier
Every URL on this site honours the release tier you've selected in the top-right navbar. New visitors land on alpha by default.
dev
https://api.sandbox.ovok.com| Tier | Maturity | When to use it |
|---|---|---|
| alpha | Preview | Building against a capability before it ships. Expect change. |
| beta | Pre-release | Integration tests, partner walkthroughs, contract validation. |
| final | Production | Production traffic. The supported contract. |
What's next
- Read the platform overview for the one-page mental model.
- Skim the public API map for route families.
- Skim the release tiers page to choose the surface you'll build against.
- Operators — jump to the Console.
- Analysts and clinicians — head for the Data Dashboard.
- Builders — pick an API surface:
- High Level API — auth, projects, content, billing, devices, signals. The convenience layer.
- FHIR API — every FHIR R5 resource, served with the standard FHIR REST interactions.