Build a CHF remote monitoring platform
Build a mobile experience for people living with congestive heart failure (CHF), paired with a clinician dashboard for reviewing reported symptoms and home measurements. This example uses a Viatom BP2 blood pressure monitor and connected weighing scales. Device availability and data mapping depend on the integrations enabled for your Ovok project.
1. Set up the project and care workflow
Create an Ovok project for the service. Decide how people are enrolled, who reviews their readings, which measurements are collected, and how a care team responds to a reading that needs attention. Keep the care pathway and escalation rules with the clinical team responsible for the service.
2. Build the patient app
Use @ovok/native for a React Native app and @ovok/core for shared Ovok authentication, API, and data workflows. Create a focused daily flow for taking a blood pressure measurement, recording weight, and completing any symptom check-in your care team has approved.
Show patients whether each reading was received and when it was last synced. Make device setup, measurement instructions, and support easy to find so a missing reading can be resolved before it becomes a care-team blind spot.
3. Connect the monitor and scales
Configure the supported ingestion path for the Viatom BP2 and weighing scales. Associate each device with the correct patient, and confirm that the incoming measurements are normalized as FHIR Device and Observation data in the intended project.
Use a small set of known test readings to verify units, timestamps, patient association, and duplicate handling before inviting patients. Do not rely on a device label alone to infer a measurement's meaning or unit.
4. Add the clinician dashboard
Build a dashboard for the care team to review patient enrollment, recent blood pressure and weight readings, symptom check-ins, and measurement history. Give each reading its timestamp and source, and make it possible to move from an alert or trend to the underlying observations.
5. Route vital data through Signals
Vital-sign data is sent to Signals for alert evaluation. Ovok surfaces the resulting alert decisions so the care workflow can present them to the appropriate clinician. Configure thresholds and response procedures with the clinical team; this guide does not prescribe values or treatment actions.
6. Validate the end-to-end journey
Test enrollment, device pairing, offline capture, sync recovery, dashboard review, and alert visibility with representative test accounts. Confirm consent, access policies, and operational ownership before using the workflow with patients.
Suggested first release
Start with one patient workflow: enroll, take a reading, sync it, review it in the dashboard, and handle a Signals decision. Add reminders and broader symptom tracking after the care team has validated the first loop.