OVOKby ACTIMI
Read the docsStart free

A remote patient monitoring API for product teams.

Bring supported measurements, patient check-ins, and care-team workflows into a FHIR-backed product for remote monitoring, Hospital at Home, virtual wards, or Spitex. Ovok supplies backend and SDK building blocks, while your team decides how the service works for patients and practitioners.

Start free Read the docs
ovok.com/console/fhir/Patient
Lena HoffmannPatient
Observations
TemperatureDr. Weber°CNo alert
Blood glucoseDr. Webermmol/LNo alert
Check-inVitalivaSameNot evaluated
Blood pressureVitalivammHgNo alert
WeightVitalivakgNo alert
Oxygen saturationVitaliva%Alert sent
TemperatureDr. Weber°CNo alert
9:41
Home
Blood pressuremmHg
Oxygen saturation%
Weightkg
Blood glucosemmol/L
Temperature°C
Check-inHow are you feeling today?
BetterSameWorse
Send
Medication
Ramipril 5 mg08:00
Mark as takenTaken
Lena Hoffmann
WDr. Weber
Blood glucosemmol/L
Temperature°C
Save

From measurement to a product workflow

Use a consistent record foundation and make the alert-evaluation path explicit in your own architecture.

  1. 01

    Collect supported data

    Build around supported device measurements and the inputs your application collects.

  2. 02

    Keep the record in FHIR

    Use the FHIR backend as the shared record layer for patient and practitioner experiences.

  3. 03

    Add Signals where it fits

    Teams choose enrollment per patient; only eligible vital-sign readings from enrolled patients are sent for alert evaluation.

  4. 04

    Shape the care-team experience

    Your product decides how people review records, questionnaires, and returned alert decisions.

Start from the product you are building

Out-of-the-box RPM experience

Use the available RPM experience as a starting point while evaluating the backend and SDKs for your own product.

Condition-specific examples

Read the CHF remote-monitoring and type 2 diabetes guides for example build paths, not clinical-outcome claims.

Read the documentation

Questionnaires and check-ins

The React Native SDK documents FHIR Questionnaire forms that can support app-owned check-in flows.

Read the documentation

Cloud wearables

Patients can connect Oura, WHOOP, Strava, Withings, Polar, Suunto or Ultrahuman accounts with your project's own provider apps. Ovok syncs daily and on provider webhooks, and stores the readings as FHIR Observations. Wearable data is not sent to Signals.

Read the documentation

Monitoring is an application workflow

Ovok provides

  • FHIR R4 backend capabilities and SDKs.
  • Supported device workflows and optional Signals evaluation.

Your team defines

  • The intended use, patient journey, and practitioner workflow.
  • How records and alert decisions are presented and acted on.

Signals in your stack

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.

Read the documentation

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.

Read the documentation

Explore solutions for your team.

Compare startup validation, scaleup device workflows, enterprise architecture, and provider-led Hospital at Home, virtual-ward, or Spitex programmes.

Hospital at Home, virtual wards, and Spitex

Explore infrastructure for provider-led care-at-home programmes and their digital-health partners.

Read about Hospital at Home, virtual wards, and Spitex

Scaleup product teams

Review device coverage and configure Signals enrollment at the patient level.

Read about Scaleup product teams

Enterprise evaluation

Assess hosting, access, and commercial terms with your architecture and procurement teams.

Read about Enterprise evaluation

Prototype the monitoring workflow you need.

Start in the Developer sandbox, then review the supported-device and deployment details for your target product.

Start free Read the docs