CliniGA CRO

CliniGA CRO Blog

Offline Synchronisation: When Two Valid Edits Conflict

Resolve conflicting offline records using authority, source evidence and change history rather than arrival order alone.

Representative research photograph: Offline Synchronisation: When Two Valid Edits Conflict
Photo: SuSanA Secretariat · License: CC BY 2.0 · Cropped and resized.
Published
Updated

An offline application can create multiple versions of the same record. Automatically choosing the last version received may discard a more accurate or authoritative correction simply because its device connected earlier.

Preserve the meaning of data

Separate the device recording time, server acceptance time and editor authority in the synchronisation rules. Clock settings and delayed connections may make the actual editing sequence uncertain. Define situations in which two different values for one field cannot be resolved automatically. Keep conflicting versions explainable while the authorised review remains open.

Worked example

For example, site staff correct a visit comment offline while another authorised person makes a different correction centrally. The second device reconnects later. Instead of silently overwriting the central record with an older value, the application displays a conflict. A reviewer uses the source rationale to choose the value and retains evidence of both edits.

Review checks

  • Test simultaneous changes to the same field on different devices.
  • Include incorrect device clocks and delayed reconnection scenarios.
  • Record the reason and responsible person for each conflict resolution.

Acceptance and boundaries

Acceptance means no authorised change disappears without explanation and the resolved value can be linked to its source. Human review may not be necessary for every field; boundaries for low-impact automatic merging should be defined beforehand. Assess silent overwriting particularly carefully for clinically important fields. A successful synchronisation message should not imply that every conflict has been resolved.

Frequently asked questions

Does the latest timestamp identify the correct version?
Not always. Device time, connection delays and authoritative source context must be considered together.
When can a conflict be closed?
Close it through the authorised process when the selected value, rationale and status of affected outputs are explainable.

Sources

  1. FDA — Electronic systems, records and signatures in clinical investigations
  2. MHRA — Guidance on GxP data integrity