Compliance

Check a batch run against its signed record

Choose the folder a batch run wrote to and check every file and the report against the signed record inside it. Free, in the browser and the desktop app.

Browser: available nowDesktop app: 1.6.0 or newer

Problem

Someone sent you a folder of anonymized files with a signed record. You need to know that the files are the ones the record lists, and you may not have dcmage pro.

Steps

  1. Open dcmage. You do not need to load a file, and the check does not need dcmage pro.

  2. Choose Verify a signed file or batch run on the empty screen. With a file loaded, the same dialog is under Export.

  3. Choose Batch run, then Choose folder. Pick the folder the run wrote to, with dcmage-run-manifest.jws.json inside it.

  4. Compare the thumbprint with the one the sender gave you. The key travels with the record, so anyone can sign a record with a key of their own.

Result

dcmage checks the signature, then the SHA-256 of every file the record lists and of the report. It gives one of three results:

  • Verified. Every file and the report match.
  • Files match, with notes. Every file matches, and there is something to read: a file in the folder that the record does not cover, a run recorded as incomplete, images unchecked for burned-in text, a pseudonym covering more than one Patient Name, or an audit chain that did not check out.
  • Failed. The signature does not hold, or a file is changed, missing or unreadable. Each such file is named.

Limits

  • A match means the files are unchanged since this key signed the record. It does not show who holds the key.
  • It does not show that the files are correctly anonymized or free of burned-in text.
  • On Windows, a browser cannot read a file whose full path is longer than 260 characters, and lists it as unreadable. Move the folder somewhere shorter, or check it in the desktop app, which reads past that limit.
  • The check reads the files on your computer. Nothing is sent anywhere.