Four layers preserve context.
Server-controlled timestamps
The service records creation, update, correction, and finalization times on the server instead of trusting a browser-supplied audit time.
Day finalization
Finalizing a day locks direct edits to that day’s care records. The preview summarizes the exact day version before confirmation.
Append-only corrections
A finalized record is corrected by appending a reasoned revision. The previous revision remains in history rather than being silently replaced.
Linked hashes
Each stored revision hash covers canonical record content and its predecessor, creating a chain that helps detect later alteration.
What happens when a finalized record needs a correction?
- 1
The current record and version are fetched.
- 2
The proposed correction, reason, and changed fields are previewed.
- 3
A short-lived handle binds confirmation to that exact preview.
- 4
Confirmation appends a new revision only if the record is unchanged and the handle remains valid.
What these controls do not claim
- They do not make the service or exported files tamper-proof.
- They do not prove that user-entered content is true, complete, or independently verified.
- They do not guarantee that a record will be accepted by another person, institution, or proceeding.