When data is lost: an honest “we don’t know” beats invented progress

When photographs, settings or response notes are missing, teams are tempted to build an approximate history from memory and messages. That creates false precision. Separate verified facts, recollections and what remains unknown.

Mark the boundary of what is known immediately

Create a data-loss incident entry in the treatment record: which visit was affected, what fields were missing, when it was discovered, and who checked the sources. You cannot fill parameters with a typical shift value or copy a previous visit without proof. Even if the practitioner is sure, the memory is not equal to the device log or signed record.

The situation is explained to the client without shifting blame: “We did not keep part of the technical record of the last visit, so we will not pretend that we know it. Today we will re-evaluate the area and agree on a safe plan.” There is no need to force the client to remember numbers. Their description of sensations and reactions is valuable, but is labelled in the record as a client report.

Restore data only when its source is traceable

The team reviews approved sources: the device log, record system, secure photographs, service log, consumables and follow-up messages. Every recovered fact is linked to its source and time. A screenshot without context or a file with an unclear date does not become confirmation merely because it appears to fit.

The reconstructed record must not conceal the data gap. The wording “according to the client” is different from “confirmed by the device log.” If two versions diverge, both are saved with a note, rather than choosing the more convenient one. The goal of an investigation is not to create a perfect story, but to understand what data can be relied upon.

• Create a data-loss incident record before attempting to recover data.
• Separate confirmed source, client message, employee memory and unknown.
• Do not copy the parameters of a neighbouring visit or average the values.
• Notify the person responsible for privacy or incidents according to the local procedure.

Establish a new baseline

The next plan begins with an updated screening, inspection, current device IFU, and operator qualifications. The unknown past parameter is not guessed. If necessary, perform the test patch required by the device IFU and protocol, with documentation of the response. The test reduces risk but does not promise safety or results.

New photographs are taken according to the standard and designated as a new baseline, and not as a continuation of the ideal series. Client goals are discussed again. If the past response cannot be assessed, the team does not promise to compensate for the “lost progress” with a more intensive procedure. The decision may include deferral, additional assessment, or treatment area reduction.

Address the cause, not just the record

Trace how the data were lost: was a required field skipped, did synchronisation fail, was a photograph stored on a personal device, did access permissions remove data, or was the backup never verified? “The practitioner forgot” is rarely a sufficient explanation. Determine why the system allowed the appointment to close without the minimum documentation.

After making a change, test it through the real workflow: required fields, draft saving, handover with identifiers, backup recovery and the audit trail. Tell employees how to handle the newly identified gap. An honest “we don’t know” protects quality only when it leads to a safe decision and a process improvement.