Compliance

Signed manifest of a batch run

Sign one manifest that lists every file a batch run wrote, every file it did not, and whether the run is complete.

Desktop app only, 1.6.0 or newerdcmage pro

Problem

A sponsor or IRB receiving an anonymized cohort needs to know what they were given: which files are in it, whether any file changed after the run, and which files were left out and why. A folder of files says none of that.

Steps

  1. Run Anonymize a Folder… until the result appears.

  2. Choose Write signed record. dcmage reads each written file back from the output folder and compares it with the hash it took when it wrote that file. If a file cannot be read or has changed, dcmage names it by number and signs nothing.

  3. Send the output folder. dcmage-run-manifest.jws.json is in it, beside the files. It is signed with your signing identity (ES256), and the record note shows the signer’s fingerprint.

  4. Check it on the receiving side. Any JWS library can check the signature against the public key in the manifest. Compare that key’s fingerprint with the one the sender gave you, then hash each file and compare it with the manifest.

Result

The manifest lists the path, byte length and SHA-256 hash of each written file, each file not written with its number and reason, the settings, the run’s audit lines, and whether the session audit chain checked out. It records complete: false for a cancelled run, and for a run with any file failed, held for burned-in text, or not processed.

Limits

  • The manifest identifies source files by number, never by source path, and holds no patient values from them.
  • A valid signature says who signed the record and that it has not changed. It does not say that the images are free of burned-in text.
  • A recipient checks the manifest and the folder with Verify, which is free, or with any JWS library.
  • The command line does not write a record.