Anonymization

Keep an encrypted file that links pseudonyms to patients

Save which patient each pseudonym stands for, encrypted under your own passphrase, and look one up later.

Desktop app only, 1.6.0 or newerdcmage pro

Problem

A site has to be able to find the patient behind a pseudonym, for example after a safety finding, and the link must not travel with the anonymized data.

Steps

  1. Run Anonymize a Folder… to the end.

  2. Enter a passphrase twice and choose Save re-link file…. It must be at least 12 characters.

  3. Save it somewhere other than the output folder. dcmage refuses a place inside the output folder, because that folder is what gets handed on.

  4. To look one up later, open Anonymize a Folder…, open Look up a pseudonym in a re-link file, enter the pseudonym and the passphrase, and choose the file.

Limits

  • The file can be made only while the result of the run is on screen. It cannot be made after you close the dialog.
  • dcmage cannot recover a lost passphrase.
  • The file lists only the patients the run wrote at least one file for. A patient whose files were all held or failed is not in it, because no file in the output carries that pseudonym.
  • Whether a pseudonym counts as de-identified under your rules, while a re-link file exists, is a question for your privacy officer.
  • The audit log records that a file was saved or opened, and how many patients it covers. It does not record who was looked up.

The file format

You do not need dcmage to read the file. It is JSON with format, version, kdf (PBKDF2 with SHA-256, with its iterations and hex salt), cipher (AES-GCM with its hex nonce) and ciphertext in hex, with the 16-byte tag at the end. The key is 256 bits. The plain text is JSON holding runId, ts and rows, and each row has source and code (the pseudonym). source is the Patient ID. For a file with no Patient ID it is the Patient Name, or study: and the study’s UID when the name is missing too.

See also