[DRAFT] Feature/hm 111

[TheoAtTechStack]

Summary of Sync Logic Changes

Previously, the app's sync function would fetch all data from the server and completely overwrite the local database. We've replaced this with a more intelligent incremental merge strategy.

Now, when a sync is initiated:

1. Incoming data is compared to local data. The app fetches the latest records from the server and compares them against the records already stored on the device, using the resource_id to match them.

2. Updates are based on a timestamp. An updated_at timestamp is used to determine if a change is needed. An existing record is only updated if the incoming version is newer. This prevents unnecessary database writes and improves performance.

3. A single "upsert" operation handles changes. We use the existing cacheFhirResources function to efficiently handle both creating new records (if the ID doesn't exist locally) and updating existing ones (if the incoming record is newer).

In short, the sync logic no longer blindly replaces data. It now performs a smart, row-by-row merge that preserves your local database, adds new records, updates only what has changed, ensuring data is always consistent and up-to-date without unnecessary data loss.

[mihaipop-tsa]

LGTM

Didn't realise this was a draft, will review again once it's done.