OVOK · A platform by ACTIMI

API-first.Built for digital health.

Build your patient and practitioner experience on an FHIR R4 foundation. Connect supported devices, manage clinical data and add optional Signals evaluation — with the team behind ACTIMI.

ovok.com/console/fhir/Patient
Lena HoffmannPatient
Observations
TemperatureDr. Weber°CNo alert
Blood glucoseDr. Webermmol/LNo alert
Heart rateSleep radarbpmNo alert
Respiratory rateSleep radar/minAlert sent
Sleep sessionSleep radarhNot evaluated
Blood pressureVitalivammHgNo alert
WeightVitalivakgNo alert
9:41
Home
Blood pressuremmHg
Oxygen saturation%
Weightkg
Blood glucosemmol/L
Temperature°C
Check-in
Send
Medication
Ramipril 5 mg08:00
Mark as takenTaken
Sleep radar
7.21458
23:4006:55
Lena Hoffmann
WDr. Weber
Blood glucosemmol/L
Temperature°C
Save
Signals enrollment is configurable per patient. Ovok stores device data in FHIR and forwards eligible vital-sign readings only for enrolled patients, for alert evaluation.
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
gematik ISiK Stufe 5Basis, Vitalparameter and Labor tests passed. gematik confirmation pending.

Actimi network

Ovok is an Actimi product.

Actimi works with the research, healthcare, and innovation organizations shown here.

OVOK · A platform by ACTIMI

The foundation. Your care experience.

Bring the platform capabilities from ACTIMI into your own product. Start with the backend and SDKs, then connect the workflows your application needs.

Clinical records

FHIR R4 resources, care plans and questionnaires keep patient data structured and connected, with real-time updates over WebSocket Subscriptions and FHIRcast.

Device data

Bring readings from supported medical devices and from Oura, WHOOP, Strava, Withings, Polar, Suunto and Ultrahuman accounts into a shared data foundation.

Teams and access

Projects, sub-projects and Access Policies define how teams work with resources and operations.

Care workflows

Connect appointments, video calls, tasks and patient-facing content to your application.

Your app, your stack

Use web and mobile SDKs or work directly with the APIs. Your team owns the interface and business logic.

Hosted in Germany

AWS Frankfurt hosting with production plans and dedicated deployment options for larger requirements.

Products built with the ACTIMI platform

From remote monitoring to respiratory care and pregnancy support: explore applications featured by ACTIMI.

Features and benefits

Build the digital health product. Start with the foundations.

Explore our remote patient monitoring use case, then build the web and mobile workflows your product needs with Ovok SDKs and platform services. We share new FHIR and connected- health articles on the Ovok blog as they publish.

02

SDKs for web, mobile, Java, Python and Flutter

Build web apps with the React SDK and @ovok/core, or use the React Native SDK for mobile UI and integrations. Java, Python and Flutter install commands are below.

  • Java SDKimplementation("com.ovok:ovok-sdk:0.1.0")
  • Python SDKpip install ovok-sdk==0.1.0
  • Flutter SDKflutter pub add ovok_sdk:0.1.0 ovok_flutter:0.1.0
05

Vital-sign alert decisions

Signals evaluates eligible vital-sign readings for enrolled patients. Enrollment is configurable. Signals is MDR Class IIa.

06

AI agents

Connect Claude, ChatGPT, Cursor or any other MCP client to your project with one sign-in, then let it set up FHIR data, CMS content and settings through 27 named tools. Start on the Console MCP page or read the AI agents guide.

Signals in your stack

Alert decisions that reach your systems.

For enrolled patients, Signals results come back to your product as signed webhooks and FHIR resources. Signals is MDR Class IIa; Ovok itself is not certified.

Signed webhooks

Receive alert, episode, reading, patient and webhook-status events, with redelivery and signing-secret rotation.

Write-back to FHIR

Alerts are stored as DetectedIssue and episodes as Flag, and the alerting Observation gets an interpretation and reference range.

Per-patient settings

Configure Signals for each patient, switch episodes on per tenant, and use manager and submitter client apps with the Signals API.

The Ovok Console

See the project you build on.

Every project comes with the Console: explore FHIR data, follow each request, connect Signals, edit content and manage billing in one place.

The Console FHIR Explorer listing synthetic test records

FHIR Explorer

Browse, filter, edit and create resources, and read each version's history.

The Console request log with synthetic API requests

Events

Follow every request, open its trace and compare operation metrics.

The Console Signals webhooks list with synthetic subscribers

Signals webhooks

Add webhook subscribers, choose their events and rotate signing secrets.

The Console CMS studio with synthetic content entries

CMS studio

Edit content, content types, translations, media and CMS API keys.

The Console billing page with a plan and usage for a synthetic project

Usage and billing

Track usage, change plans and review invoices.

Start free

For product teams and care providers

Build for your product stage and care setting.

Start with the FHIR and device infrastructure for digital-health startups, explore the platform for growing teams in our scaleup solution, or review the details for an enterprise deployment.

Healthcare ecosystem

What exists today, and what your team builds.

Status labels distinguish available capabilities, documented implementation guidance, and roadmap work. Project capabilities and app-specific integrations still matter.

01In the docs

Labs

FHIR references cover lab orders and results; check your project’s CapabilityStatement for enabled interactions. The docs describe resource patterns, not a ready-made lab connector.

02In the docs

Medications

The medication guide covers plans, adherence, and local reminders. Ovok provides medication resources; your app schedules device notifications.

03Roadmap

Billing & RCM

Patient billing and RCM APIs are not available today. Billing support is deferred until a developer contract exists; no delivery date is published.

04Available

FHIR interoperability

FHIR R4 APIs are available. The interactions enabled for your project are listed in its CapabilityStatement.

05Available

SDKs & modules

Build with the React, React Native, Java, Python or Flutter SDK. Optional native imports let apps include only the integrations they need.

06In the docs

Third-party tools

The LiveKit video-call API is documented. Scheduling, imaging, CRM, and other external systems need app-specific integrations.

Start building at your own pace.

Pricing is per monitored patient. Review per-patient pricing and plan details; every paid plan includes a data processing agreement.