Read the docsStart free

FHIR backend for remote monitoring

Build your ownmedical apps.

Supported-device data is stored in FHIR. Your team configures Signals enrollment per patient; only eligible vital-sign readings from enrolled patients are sent to Signals for alert evaluation.

Start freeRead the docs

Supported devices

  • BP monitors
  • Sleep radars
  • SpO₂ monitors
  • Urine analysers & wearables
FHIR backend
Signals

Example destinations

  • Your app
  • Clinician dashboard
  • EHR
  • Other systems
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

Actimi network

Ovok is an Actimi product.

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

Features and benefits

Build the medical app. Start with the foundations.

Explore the RPM experience, then build the web and mobile workflows your product needs with Ovok SDKs and platform services.

01

Supported device data

Bring readings from 50+ supported devices, including BP monitors, sleep radars, SpO₂ monitors, urine analysers, and wearables.

05

Vital-sign alert decisions

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

Solutions for every stage

A foundation that grows with your team.

Start with a hands-on evaluation, build for growth, or review the details for an enterprise deployment.

Startups

Evaluate the FHIR foundation and supported device data hands-on in the Developer sandbox.

Explore startup solutions

Scaleups

Build on supported measurements and Signals as your remote monitoring product grows.

Explore scaleup solutions

Enterprises

Review Frankfurt hosting, per-patient pricing, and commercial terms with Actimi.

Explore enterprise solutions

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.

FHIR resource reference
02In the docs

Medications

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

Medication reminder guide
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.

FHIR R4 docs
05Available

SDKs & modules

Use the web SDK or React Native SDK; optional native imports let your app include only the integrations it needs.

Web SDK React Native SDK
06In the docs

Third-party tools

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

Video-call docs

Start building at your own pace.

Pricing is per monitored patient. Every paid plan includes a data processing agreement.

View pricing details Read the docs