Build a type 2 diabetes management platform
Create a mobile workflow for recording blood glucose and weight, with a clinician dashboard that brings readings and follow-up into one place. This example uses a connected Taidoc blood glucose monitor and weighing scales. Confirm that the required device integration and measurement mapping are enabled for your Ovok project before rollout.
1. Set up your project and cohort
Create the Ovok project and define the patient enrollment process, care-team roles, and monitoring workflow. Agree with the clinical team which measurements are collected, how often they are reviewed, and what response follows a reading that needs attention.
2. Build the mobile experience
Use @ovok/native to build the React Native app and @ovok/core for shared Ovok API, authentication, and FHIR operations. Keep the main journey short: connect a device, take a measurement, confirm the reading arrived, and review the patient's progress over time.
Include space for the patient to record relevant context, such as a note or a care-team-approved check-in. Clearly distinguish a device measurement from information the patient entered themselves.
3. Connect the glucose monitor and scales
Configure ingestion for the Taidoc blood glucose monitor and weighing scales. Associate readings with the correct patient and validate the measurement type, units, timestamp, and source before exposing them in charts or workflows.
Store measurements as FHIR Observation resources and preserve their device source. Test values and edge cases with the device integration team; do not derive clinical meaning from an unverified unit or device label.
4. Create a clinician dashboard
Show recent and historical glucose and weight readings with clear units, timestamps, and measurement sources. Let clinicians review patient-reported context alongside readings, identify gaps in data collection, and open the underlying record when needed.
5. Send vital data to Signals
Vital-sign readings are sent to Signals for alert evaluation. Ovok surfaces the resulting decisions to the configured care workflow. Thresholds, review timing, and escalation actions should be set by the clinical team; this walkthrough does not define treatment targets.
6. Test the complete workflow
Validate enrollment, device pairing, repeat readings, offline sync, patient association, dashboard history, and visibility of Signals decisions. Test access policies with patient and clinician roles before the app is used in care.
Suggested first release
Start with glucose and weight capture, a patient history view, and a clinician review screen. Add reminders, education, or additional measurements only after the core data and alert workflow has been validated.