Open Wearables alternative

An Open Wearables alternative that writes FHIR

Open Wearables unifies wearable data on a server you host. Ovok syncs Oura, WHOOP, Strava, Withings, Polar, Suunto and Ultrahuman into FHIR R4 Observations in the patient’s record, next to readings from 800+ supported devices, managed in AWS Frankfurt, with ACTIMI Signals, an MDR Class IIa medical device, deciding alerts on vital signs from medical devices.

ovok.com/console/fhir/Patient
Lena HoffmannPatient
Observations
WeightVitalivakgAlert sent
Blood pressureVitalivammHgNo alert
Oxygen saturationWithings%Not evaluated
Heart rateWHOOPbpmNot evaluated
Sleep sessionOurahNot evaluated
WeightVitalivakgNo alert
Blood pressureVitalivammHgAlert sent
9:41
Home
Blood pressuremmHg
Weightkg
Oxygen saturation%
Heart ratebpm
Blood glucosemmol/L
Check-in
Send
Medication
Ramipril 5 mg08:00
Mark as takenTaken
WearablesSynced
Sleep sessionh
Heart ratebpm
Oxygen saturation%
AWS Frankfurt hosting
Priced per monitored patient
Signals is MDR Class IIaOvok is not a certified medical-device product.UDI-DI: 42700031203-API-XG · EUDAMED search

01

At a glance

Ovok and Open Wearables, side by side

What each one gives you, from the data model to who makes the alert decision.

Ovok and Open Wearables compared
OvokOpen Wearables
Data modelFHIR R4 API with search and WebSocket subscriptionsIts own unified schema in PostgreSQL, not FHIR
HostingManaged in AWS Frankfurt; dedicated deployments on EnterpriseSelf-hosted in your cloud account; no hosted version
PricingFree Developer sandbox; paid plans priced per monitored patient, with Signals in Growth and Scale and a DPA on every oneMIT-licensed core you run yourself; paid Pro and Enterprise modules
Medical devices800+ Bluetooth catalogue entries through the React Native SDK, saved as FHIRPhone health apps; medical-grade devices on request
WearablesOura, WHOOP, Strava, Withings, Polar, Suunto and Ultrahuman sync as FHIR Observations; Apple Health and Health Connect import on the phoneGarmin, Oura, WHOOP, Polar, Suunto, Withings, Strava, Ultrahuman and more, plus Apple Health, Health Connect and Samsung Health
Alert decisionsACTIMI Signals, an MDR Class IIa medical device, for enrolled patients’ vital signsWebhooks on new data and a paid alerting module; no medical-device certification
App building blocksReact, React Native, Java, Python and Flutter SDKs; Access Policies, CMS, video calls and an MCP server for AI agentsiOS, Android, Flutter and React Native SDKs and an MCP server

Compared from each vendor’s public documentation in November 2026. Check the current details with Open Wearables before you decide; product names are trademarks of their owners.

02

What Ovok adds

What you would otherwise build next to Open Wearables

FHIR from the first sync

Every synced reading is a FHIR R4 Observation about the patient, with standard codes, next to device readings. One query reads both; a source tag keeps them apart.

Medical devices beside the wearables

800+ Bluetooth catalogue entries, from blood-pressure monitors and scales to pulse oximeters, glucose meters and ECG recorders, plus Apple Health and Health Connect import, through the React Native SDK.

Managed, under your name

Ovok runs the OAuth flows, token refresh, 30-day backfill and daily sync in AWS Frankfurt. Each project brings its own provider apps, so patients see your app on the consent page.

Alert decisions where they belong

ACTIMI Signals, MDR Class IIa, evaluates enrolled patients’ vital signs from medical devices. Wearable readings stay in the record and are never sent to Signals.

03

ACTIMI Signals

Alert decisions from an MDR Class IIa medical device

A backend stores the reading. Deciding whether it needs the care team is a medical-device function, and on Ovok, Signals makes that decision for the patients you enroll.

Enrolled per patient

You choose which patients Signals evaluates. Everyone else keeps using the FHIR backend; their readings are stored, never evaluated.

Vital signs, not wellness data

Eligible vital-sign readings go to Signals as they land, whether a device or your code wrote them. Wearable data, check-ins and notes stay in the record and are not evaluated.

Decisions come back as FHIR

Signals results return to your product as FHIR resources and signed webhooks, so your app and the care team act on the same alert.

ACTIMI Signals is an MDR Class IIa medical device. Ovok’s FHIR backend is not itself a certified medical device, and using Signals does not automatically certify your application. Review intended use and integration requirements with ACTIMI. What MDR Class IIa means

04

Switching

Moving from Open Wearables

  1. 01

    Save your provider apps

    Use the apps you registered at each provider for Open Wearables, or register new ones, and save their credentials in the Console.

  2. 02

    Reconnect patients

    Patients connect their accounts from your app. Ovok backfills the last 30 days and syncs every day after that.

  3. 03

    Read FHIR

    Read the patient’s Observations with the FHIR API or an SDK, and filter by the source tag when you need only wearable or only device readings.

05

Honest fit

When to choose which

Ovok fits best

  • You build remote monitoring for patients in Europe and want the data hosted in Frankfurt.
  • Alert decisions should come from a certified medical device, not from code you validate yourself.
  • Readings come from Bluetooth devices, wearable accounts and phone health apps.
  • You want pricing per monitored patient and no FHIR server to operate.

Open Wearables fits best

  • You want MIT-licensed code you host and change yourself.
  • You need Garmin, Samsung Health or other sources Ovok does not sync today.
  • Wellness data is the product, and you need neither FHIR nor a medical-device layer.
  • All data must stay inside your own cloud account.

Developer sandbox

Try Ovok with your own data

Create a free project, write FHIR R4 resources and connect a device or a wearable. Paid plans are priced per monitored patient and include a DPA.