Follow the end-to-end data flow

The two apps do not call each other. Ovok is the shared backend boundary between the patient-facing mobile experience and the practitioner dashboard.

Patient write path

In the mobile workspace, src/bluetooth.tsx receives supported device results. The app passes a validated diary entry into src/care-store.tsx, which persists it locally and then calls the write functions in src/ovok.ts when an authenticated Patient session is active.

Demo records remain local. Patient saves use the signed-in profile and are kept separate from demo history. A failed write is surfaced as a retryable state; this example does not promise unattended background delivery.

Practitioner read path

The dashboard's patientData.ts loads Patient measurements and QuestionnaireResponses through the SDK. PatientReviewPage.tsx displays readings, timestamps, source labels, and recent activity. Sandbox access is enforced by the project and practitioner policy, not by a client-side relationship check.

For separate app-specific setup and source tours, continue to the mobile app and clinician dashboard.