Use case / Product architecture

Build remote patient monitoring around one FHIR foundation.

Bring supported device measurements, patient data and care-team workflows into the monitoring product your team owns. Ovok provides the healthcare infrastructure underneath; you define the app and the care model.

Start free Build the RPM guide

Architecture

One patient record, several intentional data paths.

An RPM product can combine device readings with information people enter and records they choose to share. The routes below are composable; not every source uses the same SDK or goes through Signals.

01
Data sources
Supported Bluetooth devices, selected HealthKit or Health Connect records, patient-entered information and questionnaire responses.
02
SDK and ingestion paths
Use @ovok/native for supported mobile Bluetooth workflows; use the documented ingestion service for connected systems and the Native SDK for health-platform imports.
03
FHIR R4 patient record
Store the records your product uses in the Ovok FHIR backend, including supported measurements as Observations.
04
Your patient and practitioner apps
Build onboarding, device setup, recent-reading views, questionnaires and care-team review in the experiences your product owns.

As a monitoring product grows beyond its first rollout, review the FHIR and device infrastructure for health scaleups.

Patient and care team

The application remains yours.

Ovok supplies backend and SDK capabilities. Your team turns them into the screens and operational workflow that fit the product's intended use.

Patient app

Your app can handle sign-in, pairing, taking and saving a reading, recent history, check-ins and access to education content. The UI and instructions are product-owned.

Out-of-the-box RPM experience

The platform includes an out-of-the-box RPM experience. Your team still owns the application it ships, its intended use and its care workflow.

Practitioner experience

Use FHIR-backed patient data and practitioner identity to build lists, measurement history and review screens. Ovok does not provide a finished EHR or a care-team dashboard.

Additional interactions

Documented building blocks include questionnaires, CMS content and video calls. Appointment design, communication policy and follow-up remain in your product.

Sources and ingestion

Choose the path that matches the source.

Device compatibility is model-specific. Check the catalog and the selected device's measurement fields before committing to a product workflow.

50+ supported devices

The current public device claim covers supported devices across categories such as blood-pressure monitors, sleep radars, SpO₂ monitors, urine analysers and wearables.

Open supported-device catalog

Mobile Bluetooth

The Native SDK exposes supported-device Bluetooth primitives and measurement callbacks. The mobile app owns the pairing and measurement experience; a physical iOS or Android device is needed to evaluate BLE.

Read about Mobile Bluetooth

Health platforms and connected systems

HealthKit and Health Connect imports depend on permissions and available source records. Connected-system ingestion is a separate, configured path.

Read about Health platforms and connected systems

Product boundary

Infrastructure underneath; product decisions above it.

Ovok provides

FHIR R4 backend and patient/practitioner identity
Supported measurement ingestion and SDK primitives
Access Policies, questionnaires, CMS and video-call capabilities
Optional, patient-level Signals evaluation

Your product team owns

Intended use, patient experience and practitioner workflow
Enrollment, consent and the data each product sends
Clinical interpretation, thresholds and escalation policy
Regulatory strategy and product-specific business logic

Build from a working example

Start with a concrete device-to-FHIR implementation.

These published guides show specific product compositions; they are examples, not preconfigured RPM care pathways.

Blood Pressure RPM

Follow the documented flow from supported Bluetooth measurement to normalized data, FHIR Observation and app display.

Read about Blood Pressure RPM

Medication Reminder

See a medication plan represented with FHIR and reminders scheduled locally by the example app; Ovok does not schedule those reminders.

Read about Medication Reminder

Type 2 Diabetes Risk Screening

See a questionnaire-led screening example with a supported measurement workflow; it does not diagnose diabetes or interpret glucose readings as advice.

Read about Type 2 Diabetes Risk Screening

Whole-Person Healthspan

Explore selected HealthKit or Health Connect records, reflections and goals in a separate wellness example.

Read about Whole-Person Healthspan

Relevant capabilities

Follow the APIs that match your first slice.

Signals

An explicit branch for enrolled patients.

Evaluate the product pattern

Build against the infrastructure your team will use.

Start in the Developer sandbox with test data, then validate supported-device and workflow requirements against the current docs.

Start free Read the RPM guide

Data sources

SDK and ingestion paths

FHIR R4 patient record

Your patient and practitioner apps