Batch anonymize DICOM medical images by removing patient sensitive information (name, ID, birth date) while preserving image data for research use. Trigger when users need to de-identify medical imaging data, prepare DICOM files for research sharing, or remove PHI from radiology/scanned images.
90
86%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
Passed
No known issues
Batch anonymization with audit log
pydicom used
100%
100%
Batch mode flag
0%
100%
Audit log generated
100%
100%
Audit log structure
80%
100%
PatientName is ANONYMOUS
0%
100%
PatientID hashed not cleared
0%
100%
AccessionNumber hashed
0%
100%
PatientSex preserved
0%
100%
PatientWeight preserved
0%
100%
Private tags removed
100%
100%
PatientBirthDate cleared
40%
100%
Without context: $0.4543 · 1m 52s · 23 turns · 23 in / 6,877 out tokens
With context: $0.7224 · 2m 19s · 24 turns · 29 in / 8,420 out tokens
Study linkage preservation with UID hashing
preserve-studies enabled
66%
100%
StudyInstanceUID hashed not regenerated
100%
100%
SeriesInstanceUID hashed
100%
100%
Different patients different UIDs
100%
100%
Pseudonym format ANON_XXXXXX
0%
100%
Same patient same pseudonym
100%
100%
PatientID hashed
50%
100%
Audit log present
70%
100%
Without context: $0.4930 · 1m 59s · 25 turns · 30 in / 7,574 out tokens
With context: $0.9336 · 3m 11s · 31 turns · 256 in / 11,549 out tokens
Selective tag preservation and compliance warnings
keep-tags option used
100%
100%
PatientWeight retained
100%
100%
PatientSize retained
100%
100%
PatientBirthDate cleared
60%
100%
SOPInstanceUID regenerated
100%
100%
StationName removed
75%
100%
DeviceSerialNumber removed
75%
100%
Burned-in annotation warning
100%
100%
Manual QA requirement noted
100%
100%
InstitutionName removed
70%
100%
Without context: $0.6710 · 2m 51s · 28 turns · 33 in / 9,569 out tokens
With context: $1.1037 · 4m 15s · 34 turns · 649 in / 14,327 out tokens
ca9aaa4
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.