Audit & provenance
Keep a DICOM audit trail with file provenance.
Review an ordered record of edits, anonymization actions and exports. Session hashes make later changes to the log detectable, while file lineage connects each derived file to its source.
audit · chain verified
What it covers
A complete record of every change.
Every edit, anonymization, and export is logged and chained with SHA-256 session hashes — a complete, ordered record of what was done to a dataset that you can export for IRB and compliance review.
- Hash-chained log SHA-256 hash chain over the session log.
- Full provenance original → derived lineage for every file.
- Exportable CSV / JSON trails for IRB and audit.
- Non-destructive originals are never modified in place.
Workflow
How it works
- 01
Work normally
Tag edits, anonymization actions and exports are added to the session audit log as they happen.
- 02
Review the sequence
Inspect who performed each action, when it happened and which file or study it affected.
- 03
Check integrity
Verify the SHA-256 hash chain to detect whether an earlier entry has changed.
- 04
Export the record
Save the available audit data for review with the derived files and their provenance.
Before you rely on the output
Checks that still need judgment
- A tamper-evident record can reveal later changes; it does not prove that every operator action was correct.
- Keep exported audit data with the files and procedures it describes so reviewers have the needed context.