- 01
Supported BP monitor
Confirm the exact model and measurement fields in the live device catalog.
- 02
@ovok/native over Bluetooth
Use the documented mobile integration for supported-device discovery and measurement callbacks.
- 03
Normalized measurement
The SDK maps supported device output into the measurement shape used by the example workflow.
- 04
Ovok FHIR backend
Save the reading as a FHIR Observation and retrieve it for the app's history and review screens.
- 05
Patient history and practitioner review
Your app decides how to present provenance, context and follow-up. It does not gain clinical interpretation automatically.
Use case / Product architecture
Build a connected blood-pressure monitoring product.
Move readings from supported monitors into a FHIR-backed product, then design how patients see their measurements and how practitioners review them.
01
Device-to-record
A specific path from BLE to FHIR Observation.
The published Blood Pressure RPM guide demonstrates this implementation pattern with the Native SDK and supported devices.
02
Patient experience
Pair, measure, save, and show the record.
These are app flows built with documented SDK primitives, not a ready-made clinical application.
Device setup
Build the device list and pairing instructions for the selected supported model; compatibility can depend on model variant and firmware.
Check device compatibilityReading and history
The guide saves supported measurements as Observations and reads them back into the patient app. Trend rules and interpretation belong to your product.
Reliable mobile use
Review the SDK's documented background-sync behavior and test Bluetooth with a physical device. The simulator does not reproduce the full BLE workflow.
Read about Reliable mobile use03
Practitioner workflow
Keep review and response in the product you build.
Longitudinal readings
FHIR Observations provide a record your practitioner interface can query and display with source details.
Read about Longitudinal readingsProtected access
Configure Access Policies for the project roles that read or update patient data. A FHIR relationship alone does not grant access.
Read about Protected accessFollow-up
Your clinical and product teams define how to review a reading and what happens next. Ovok does not diagnose, titrate medication or define thresholds.
04
Implementation guide
Build the working example from end to end.
The guide uses real Native SDK primitives to connect a supported device, save FHIR data and display it in an app workflow.
Blood Pressure RPM App
BLE → normalized measurement → Ovok → FHIR Observation → patient UI, with a practitioner-facing example. The guide illustrates a technical pattern; it does not set thresholds or interpret readings.
Open the Blood Pressure RPM guide05
Relevant documentation
Check coverage before choosing a device or flow.
06
Signals
Use Signals only where it fits your enrollment model.
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.