Medplum alternative

A Medplum alternative with MDR Class IIa alerts built in

Medplum gives you an open-source FHIR platform to build everything on. Ovok gives you a managed FHIR R4 backend in AWS Frankfurt with the remote-monitoring layer already there: 800+ supported devices, seven wearable clouds and ACTIMI Signals, an MDR Class IIa medical device that makes the alert decision you would otherwise write as a Bot and answer for.

ovok.com/console/fhir/Patient
Lena HoffmannPatient
Observations
WeightVitalivakgNo alert
Oxygen saturationVitaliva%Alert sent
Blood pressureFHIR APImmHgNo alert
WeightVitalivakgNo alert
Oxygen saturationVitaliva%No alert
Blood pressureFHIR APImmHgAlert sent
9:41
Home
Oxygen saturation%
Weightkg
Blood pressuremmHg
Heart ratebpm
Temperature°C
Check-in
Send
Medication
Ramipril 5 mg08:00
Mark as takenTaken
node
❯await ovok.fhir.create(vital)
201 Observation/599c 148/95 mmHg
❯await ovok.fhir.create(vital)
201 Observation/788b 126/81 mmHg
❯await ovok.fhir.create(vital)
201 Observation/977a 148/95 mmHg
❯await ovok.fhir.create(vital)
201 Observation/b669 126/81 mmHg
❯
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 Medplum, side by side

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

Ovok and Medplum compared
OvokMedplum
Data modelFHIR R4 API with search and WebSocket subscriptionsFHIR R4 API with search, subscriptions and GraphQL
HostingManaged in AWS Frankfurt; dedicated deployments on EnterpriseMedplum Cloud in the US, or self-hosted on AWS, Google Cloud, Azure or Ubuntu
PricingFree Developer sandbox; paid plans priced per monitored patient, with Signals in Growth and Scale and a DPA on every oneFree tier, then monthly platform plans with usage allowances
Medical devices800+ Bluetooth catalogue entries through the React Native SDK, saved as FHIRYour own device integration
WearablesOura, WHOOP, Strava, Withings, Polar, Suunto and Ultrahuman sync as FHIR Observations; Apple Health and Health Connect import on the phoneYour own wearable integration
Alert decisionsACTIMI Signals, an MDR Class IIa medical device, for enrolled patients’ vital signsYour own logic in Bots and subscriptions, validated by you
App building blocksReact, React Native, Java, Python and Flutter SDKs; Access Policies, CMS, video calls and an MCP server for AI agentsTypeScript client, React components and example apps; HL7 and e-prescribing as add-ons

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

02

What Ovok adds

What you would otherwise build next to Medplum

An alert decision that is a medical device

On Medplum, alert logic is a Bot you write, test and answer for. On Ovok, ACTIMI Signals, an MDR Class IIa medical device, evaluates enrolled patients’ vital signs and returns its decision as FHIR resources and signed webhooks.

Devices, already in the SDK

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.

Wearables, synced for you

Patients connect Oura, WHOOP, Strava, Withings, Polar, Suunto or Ultrahuman. Ovok runs the OAuth flow, syncs every day and writes FHIR Observations about the patient.

EU hosting, Signals in the plan

Ovok runs in AWS Frankfurt with a DPA on every paid plan. Growth and Scale include Signals and one supported device per monitored patient.

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 Medplum

  1. 01

    Open a sandbox project

    Sign up for the free Developer sandbox. Your project gets a FHIR R4 endpoint and API credentials.

  2. 02

    Bring your FHIR resources

    Ovok stores standard FHIR R4 on Medplum’s open-source server behind its own gateway, so your Patients, Observations and Questionnaires keep their shape. Load them through the FHIR API.

  3. 03

    Retire the Bots that did this work

    Enroll patients in Signals, pair devices with the React Native SDK and let patients connect their wearables.

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.

Medplum fits best

  • You want to self-host the open-source server and change its code.
  • You need US compliance today, such as a HIPAA BAA or an ONC-certified EHR.
  • You are building an EHR with e-prescribing, labs or claims.
  • You want monthly platform plans rather than pricing per monitored patient.

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.