OVOKby ACTIMI
Read the docsStart free

A FHIR API for developers building healthcare products.

Give your engineering team an FHIR R4 backend to evaluate against real app requirements. Start with the resources your workflow needs, then connect the web or mobile SDK that matches your product.

Start free Read the docs
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

Explore the API with the app surface in view

A useful API evaluation answers more than whether a request succeeds. It shows how records, identity, and permissions fit together in your product.

FHIR R4 backend

Work from a healthcare data model while building the patient and practitioner flows your application needs.

React SDK and @ovok/core

Use the web SDK documentation to plan the frontend integration and supported app workflows.

Read the documentation

React Native SDK

Review the Native SDK documentation for mobile workflows, device support, and questionnaire forms.

Read the documentation

Access Policies

Check how project-member access to resources and operations is configured.

Read the documentation

Real-time FHIR

Bind a FHIR Subscription to a WebSocket with $get-ws-binding-token to receive changes as they happen, and use the FHIRcast hub’s subscribe, publish and context calls to keep apps in sync.

Read about Real-time FHIR

A practical developer evaluation

  1. 01

    Map one product workflow

    Choose a patient or practitioner task and identify the FHIR records it uses.

  2. 02

    Exercise it in the sandbox

    Build against test data and review the API and SDK documentation as you go.

  3. 03

    Check access and scale assumptions

    Review the permissions your project needs and compare current pricing by monitored-patient volume.

    Compare plans

Signals stays optional in the API path

FHIR workflow

  • The backend supports the app's FHIR records and product-owned workflows.
  • Patients can use the backend without Signals enrollment.

Alert evaluation

  • Teams configure enrollment per patient.
  • Only eligible vital-sign readings from enrolled patients go to Signals for evaluation.

Explore solutions for your team.

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

Startup evaluation

Validate the API and first product workflows in the Developer sandbox.

Read about Startup evaluation

Scaleup architecture review

Assess SDKs, access controls, and device workflows across a growing product.

Read about Scaleup architecture review

Test the API against your first workflow.

Start in the Developer sandbox and keep the documentation open as your team evaluates the integration.

Start free Read the docs