Skip to main content

Local data and sync in the RPM app

Ovok Care separates synthetic Demo entries from Patient entries. The demo stays on the phone and the upload function rejects it. A Patient entry is persisted locally before the app attempts the server write, so a temporary network failure can remain visible and retryable.

What sync does and does not mean​

  • Demo: stored locally; never uploaded.
  • Patient entry: saved to the local patient diary first, then sent through the configured Ovok client.
  • Needs sync: local data exists, but the server save has not succeeded. The app exposes a retry action.
  • Diary history: shows entries captured on this phone. It is not a complete server history across devices.
  • Delivery: sync is foreground-driven. This sample does not provide background monitoring or emergency response.

These boundaries are part of the example's behavior, not guarantees for every Ovok application. Design retention, offline delivery, and patient handover policies for your own product.

Explore the source: care-store.tsx handles local entries and sync states; storage.ts separates demo storage and secure Patient storage; device-readings.ts supports retry after a device reading arrives.

For the remote write boundary, continue to FHIR persistence. For more general durable delivery patterns, see React SDK offline measurements and the Mobile SDK background sync guide.