Proof & binder
Export an inspection-ready binder (.docx) of your completed logs and recalls for a date range. Each export is recorded with its file's integrity hash; the audit chain below is verified on this device.
Backup & restore
Records live in this browser. A binder is a report; only a backup can rebuild them on another device or after site data is cleared.
No backup taken on this device yet. The file is unencrypted. It holds your log sheets and, if any recall has one, a patient reference, so store it the way you store the rest of the practice's records.
Past exports
No exports yet. Generated binders are recorded here with their integrity hash.
Records & retention
Checking what's on this device…
The retention clock runs from the last entry in each log, so an active log book never becomes disposable.
Integrity is detective, not preventive: the hash chain makes an edit on this device detectable, but the local store is user-writable and timestamps are device-claimed. On its own the chain is unkeyed, so it can only confirm the records here agree with each other. Checking them against your cloud backups is what compares them to a copy this tablet cannot rewrite, and that reaches back only as far as your last backup. Backing up regularly is what makes the window small. It still does not make the timestamps independent, which would need a server to stamp them as they are written. The binder contains no patient identifiers.