PS3.15 Basic Profile + UID coherence + a verbatim-cited GDPR/HIPAA compliance manifest. MIT-licensed Python CLI, runs offline, no telemetry, single dependency.
Every PS3.15 action (X / Z / U / D) that runs on your study is mapped to the literal text of the regulation that authorizes it — GDPR Art. 4(5), HIPAA Safe Harbor §164.514(b)(2), EU AI Act Art. 10. Re-verified against EUR-Lex / eCFR / gdpr-info.eu on 2026-05-13. SHA-256 chain over the audit log + manifest so an auditor can verify integrity from the JSON alone.
file_meta.MediaStorageSOPInstanceUID kept in sync so DICOMDIR and WADO-RS references survive.RequestAttributesSequence, ReferencedStudySequence, etc. is scrubbed, not silently skipped.--verify-output) using a separate PHI tag list curated from HHS OCR Safe Harbor + TCIA. Defeats the "tool vouches for itself" failure mode.pip install dcm-anonymizer # CLI command is `dcm-anon`. The PyPI dist name had to diverge # because `dcm-anon` collides with a legacy slug.
GDPR Art. 35 requires a DPIA for any large-scale processing of special-category health data. EDPB pseudonymisation guidelines and HHS OCR de-identification guidance both push de-id to the source site. Without a machine-verifiable mapping between technical action and regulatory clause, "we anonymized correctly" is hand-waving. dcm-anon emits that mapping.
The OSS CLI is and will stay free. A hosted batch service is in preparation for teams that want S3/GCS sources, private-tag profiles per vendor, DICOM SR content scanning, and retained audit logs. Indicative bands while I measure demand: €99 / €299 / €499 per month. No card required at this stage.
Drop me a line with a one-paragraph context: what you're trying to anonymize, what regulatory regime you're under, and what the gap is today. I read every one and reply within a week.
Or email plusultra.dev@proton.me directly.
This is an engineering tool. It implements PS3.15 correctly and produces auditable artifacts that your DPO / IRB / notified-body reviewer can verify. It is NOT legal advice and does NOT certify compliance — that's your QMS and counsel's call.
GDPR output classification: pseudonymous, not anonymous, per Art. 4(5). HIPAA mode: Safe Harbor only (§164.514(b)(2)); not a substitute for Expert Determination. Operated from the EU.
Built by César Pereiro · UPV biomed alumni · async only, no calls during validation phase.
GitHub · PyPI · HF Space · HN thread · Related TFG (fairness in SaMD)