Ovok blog

Why Ovok is built on Medplum, and what we added for Europe

Ovok runs Medplum's open-source FHIR server as a managed EU platform: AWS Frankfurt on paid plans, a GDPR DPA, devices, wearables and ACTIMI Signals.

In the US, a team starting a health app often picks Medplum: an open-source, FHIR-native platform with a strong developer experience. We wanted that same foundation for products in Europe. So Ovok is built on Medplum's open-source FHIR server, and everything we added answers the questions European health products face next: where the data lives, which contract covers it, how readings from devices and wearables get in, and who makes the alert decision.

Key takeaways

  • Ovok uses Medplum's open-source FHIR server as its data layer, so your data is standard FHIR R4.
  • Paid plans run in AWS Frankfurt with a GDPR Article 28 data processing agreement. The free Developer sandbox runs in the EU too.
  • Ovok adds its own API gateway, authentication and Access Policies, SDKs for React, React Native, Java, Python and Flutter, a Console, and an MCP server for AI agents.
  • Remote monitoring is built in: 800+ Bluetooth catalogue entries through the React Native SDK, and seven wearable clouds synced as FHIR Observations.
  • ACTIMI Signals, an MDR Class IIa medical device, makes the alert decision for the patients you enroll. Ovok itself is not a medical device.

Why we started from Medplum

Building a FHIR server is a solved problem, and solving it again would have cost us years. We chose Medplum's server for three reasons:

  • FHIR-native. Every resource is a standard FHIR R4 resource. There is no proprietary data model to learn now or migrate out of later.
  • Open source. The server is Apache 2.0 licensed and written in TypeScript. You can read the code that stores your data.
  • Actively maintained. Medplum releases often, and the server covers FHIR search, references and subscriptions.

That let us spend our time on the parts a European health product needs around the server.

What "Medplum for Europe" means to us

Medplum's hosted service is designed for US healthcare. Its documentation says hosted customer data stays in the United States, and its certifications, such as HIPAA, ONC and HITRUST, are US frameworks. That is the right call for its market.

A European product starts with different questions, so for us the phrase means four things:

  1. EU hosting by default. Paid plans run in AWS Frankfurt (eu-central-1). Enterprise customers can have a dedicated deployment in Ovok's AWS Frankfurt account or in their own AWS account. The free Developer sandbox runs in the EU as well.
  2. Contracts that fit GDPR. Every paid plan includes a data processing agreement under GDPR Article 28. Ovok is built and operated by ACTIMI GmbH.
  3. Nothing to operate. No Postgres, Redis, upgrades or backups to run. You create a project in the Console and call the FHIR API.
  4. Built for remote monitoring. Devices, wearables and alert decisions come with the platform, not as a second project.

The website and Console are available in English, German, French and Spanish.

What we added around the server

A gateway, sign-in and Access Policies

Every request goes through Ovok's own API gateway. Ovok handles authentication for your patients, practitioners and backend services, and applies Access Policies scoped to your project, so a clinic only sees its own patients.

SDKs for the apps you ship

Ovok has SDKs for React, React Native, Java, Python and Flutter. They cover sign-in and FHIR reads and writes, and the React Native SDK adds the device flows below, so your app code talks to one platform.

Devices and wearables, saved as FHIR

The React Native SDK pairs 800+ Bluetooth catalogue entries, from blood-pressure monitors and scales to pulse oximeters, glucose meters and ECG recorders, and saves each reading as a FHIR Observation. Apple Health and Health Connect data can be imported on the phone. Patients can also connect Oura, WHOOP, Strava, Withings, Polar, Suunto or Ultrahuman: Ovok runs the OAuth flow, syncs every day and writes FHIR Observations about the patient.

Alert decisions from ACTIMI Signals

A backend stores the reading. Deciding whether it needs the care team is a medical-device function. On Ovok, ACTIMI Signals, an MDR Class IIa medical device, makes that decision for the patients you enroll. Signals returns its decisions to your product as FHIR resources and signed webhooks, so your app and the care team act on the same alert.

Ovok itself is not a medical device, and your app's regulatory status depends on its own intended purpose. Readings from patients you don't enroll are stored, never evaluated.

Console, CMS and AI agents

The Console is where you create projects and manage members, Access Policies and API keys. A built-in CMS holds your app's content and translations. An MCP server connects AI agents to your project.

What stays the same if you know Medplum

  • Your data is standard FHIR R4: Patients, Observations, Questionnaires and their references keep their shape.
  • FHIR search works the way the standard describes, and WebSocket subscriptions are available as a project feature.
  • You can load existing resources through the FHIR API.

What is different

  • Ovok has its own authentication, Access Policies, SDKs and Console in place of Medplum's. Plan for that layer when you move an app.
  • Paid plans are priced per monitored patient, and the Developer sandbox is free.

When to choose which

Ovok fits best when:

  • 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.

Medplum fits best when:

  • Your patients and customers are in the US, and you need a HIPAA BAA, SOC 2 or ONC certification today.
  • You want to self-host the open-source server and change its code.
  • You are building an EHR with e-prescribing, labs or claims.

For a side-by-side view, see Ovok and Medplum compared. For the hosting and GDPR details, read Medplum in Europe: where your data lives and what to check.

FAQ

Is Ovok affiliated with Medplum?

No. Ovok uses Medplum's open-source FHIR server under the Apache 2.0 licence. Ovok is a product of ACTIMI GmbH and is not affiliated with or endorsed by Medplum.

Where is my data stored?

On paid plans, in AWS Frankfurt (eu-central-1). Enterprise customers can choose a dedicated deployment in Ovok's AWS Frankfurt account or in their own AWS account. The free Developer sandbox runs in the EU.

Is Ovok a certified medical device?

No. ACTIMI Signals, the component that makes alert decisions for enrolled patients, is an MDR Class IIa medical device. Ovok itself is not, and your app's regulatory status depends on its own intended purpose.

How much does Ovok cost?

The Developer sandbox is free. Paid plans are priced per monitored patient and include a data processing agreement. See pricing and the startup programme.

Conclusion

If Medplum is the platform you would pick in the US, Ovok is built to be the one you pick in Europe: the same open-source FHIR server, run for you in Frankfurt, with devices, wearables and certified alert decisions around it. Create a free project in the Developer sandbox and read the Ovok docs to start.

Medplum is a trademark of its owner. Facts about Medplum come from its public website as of 20 November 2026.

Keep reading