6. Configuration and Profiles
Anonymization rules are defined in JSON-based profiles. The selected profile controls how DICOM metadata and clinical metadata are retained, removed, generalized, replaced, or pseudonymized.
| Profile | Label | Description |
|---|---|---|
light.json |
Light-touch | Applies minimal anonymization to key identifiers while retaining more metadata where appropriate. |
default.json |
Balanced (recommended) | Recommended default profile. Removes or replaces direct identifiers, pseudonymizes key identifiers, and retains clinically useful fields according to the configured rules. |
strict.json |
Max-safe | Applies the most restrictive anonymization rules and removes or clears more fields that may contain direct or indirect identifiers. |
The selected profile is shown in the interface. Users can click View Rules to review the exact JSON rules before running anonymization.
Identifier fields such as Patient_ID, Study_ID, and
DICOM UIDs are pseudonymized consistently so that anonymized DICOM files and
anonymized clinical metadata can still be linked for analysis.
Date, age, demographic, and clinical fields are handled according to the selected profile. The JSON profile is the authoritative source for the exact field handling.
Local anonymization logs and mapping files may be generated in the output folder for institute review and traceability. These files remain local and must not be uploaded to the ZODIAC platform.