Skip to main content

DicomAnonymizer

Python package to anonymize DICOM files. The anonymization answer to the standard . More information about dicom fields for anonymization can be found here.

The default behaviour of this package is to anonymize DICOM fields referenced in dicomfields.

Dicom fields are separated into different groups. Each groups will be anonymized in a different way.

Group Action Action definition
D_TAGS replace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
Z_TAGS empty Replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**
X_TAGS delete Completely remove the tag
U_TAGS replaceUID Replace all UID's number with a random one in order to keep consistent. Same UID will have the same replaced value
Z_D_TAGS emptyOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
X_Z_TAGS deleteOrEmpty Replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**
X_D_TAGS deleteOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
X_Z_D_TAGS deleteOrEmptyOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
X_Z_U_STAR_TAGS deleteOrEmptyOrReplaceUID If it's a UID, then all numbers are randomly replaced. Else, replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**

How to build it ?

The sources files can be packaged by using: python .\setup.py bdist_wheel

This command will generate a wheel package in dist folder which can be then installed as a python package using pip install .\dist\DicomAnonymizer-0.0.1-py2.py3-none-any.whl

Installing this package will also install an executable named dicom-anonymizer. In order to use it, please refer to the next section.

How to use it ?

This package allows to anonymize a selection of DICOM field (defined or overrided). The way on how the DICOM fields are anonymized can also be overrided.

[required] InputPath = Full path to a single DICOM image or to a folder which contains dicom files [required] OutputPath = Full path to the anonymized DICOM image or to a folder. This folder has to exist. **[optional] **ActionName = Defined an action name that will be applied to the DICOM tag. [optional] Dictionary = Path to a JSON file which defines actions that will be applied on specific dicom tags (see below)

Default behaviour

You can use the default anonymization behaviour describe above.

dicom-anonymizer Input Output

Custom rules

You can manually add new rules in order to have different behaviors with certain tags. This will allow you to override default rules :

Executable:

dicom-anonymizer InputFilePath OutputFilePath -t '(0x0001, 0x0001)' ActionName -t '(0x0001, 0x0005)' ActionName2

This will apply the ActionName to the tag '(0x0001, 0x0001)' and ActionName2 to '(0x0001, 0x0005)'

Note: ActionName has to be defined in actions list

For example, the default behavior of the patient's ID is to be replaced by an empty or null value. If you want to keep this value, then you'll have to run :

python anonymizer.py InputFilePath OutputFilePath -t '(0x0010, 0x0020)' keep

This command will override the default behavior executed on this tag and the patient's ID will be kept.

Custom rules with dictionary file

Instead of having a big command line with several new actions, you can create your own dictionary by creating a json file dictionary.json :

{
    "(0x0002, 0x0002)": "ActionName",
    "(0x0003, 0x0003)": "ActionName",
    "(0x0004, 0x0004)": "ActionName",
    "(0x0005, 0x0005)": "ActionName"
}

Same as before, the ActionName has to be defined in the actions list.

dicom-anonymizer InputFilePath OutputFilePath --dictionary dictionary.json

Custom actions from dictionary file

If you use the file anonymizer.py, then you can add custom actions:

{
    "(0x0002, 0x0002)": "ActionNameNotReferenced",
    "(0x0003, 0x0003)": "ActionNameNotReferenced",
    "(0x0004, 0x0004)": "ActionNameNotReferenced1",
    "(0x0005, 0x0005)": "ActionNameNotReferenced2"
}

Then, modify your file anonymizerUser.py :

import dicomanonymizer.anonymizer

# Functions need to have in input a dataset and a tag
def ActionNameNotReferenced(dataset, tag):
    # Extract the element from the dataset :
    element = dataset.get(tag)
    # You can update the value as here :
    element.value = ''
	print('custom action')
def ActionNameNotReferenced1(dataset, tag):
	print('custom action 1')
def ActionNameNotReferenced2(dataset, tag):
	print('custom action 2')

actionsTagMap = {
	(0x0001, 0x0001): "keep", #will use the default method in the dicom anonymizer
	(0x0002, 0x0002): ActionNameNotReferenced,
	(0x0003, 0x0003): ActionNameNotReferenced2
}

# Generate a custom dictionary that will be override the default one
actionsMap = dicomanonymizer.anonymizer.generateActionsDictionary(actionsTagMap)

# Send the map to the main function
dicomanonymizer.anonymizer.anonymize(actionsMap)

In your own file, you'll have to define:

  • Your custom functions. Be careful, your functions always have in inputs a dataset and a tag
  • A dictionary which map your functions to a string

Overrides actions for default tags

You can have the need to keep some tags, for example UID. Then, instead of replace it (replaceUID action) then you can override it :

UIDActionMap = dicomanonymizer.simpledicomanonymizer.generateActions(dicomanonymizer.dicomfields.U_TAGS, "keep")
dicomanonymizer.anonymizer.anonymize(inFile, outFile, actionsMap)

All the listed actions below can be used with generateActions function by using a string. If the second parameter of the generateActions actions is a string and doesn't belong to the actions list, then the default behaviour will be to keep the tag.

Actions list

Action Action definition
empty Replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**
delete Completely remove the tag
keep Do nothing on the tag
clean Don't use it for now. This is not implemented
replaceUID Replace all UID's number with a random one in order to keep consistent. Same UID will have the same replaced value
emptyOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
deleteOrEmpty Replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**
deleteOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
deleteOrEmplyOrReplace Replace with a non-zero length value that may be a dummy value and consistent with the VR**
deleteOrEmptyOrReplaceUID If it's a UID, then all numbers are randomly replaced. Else, replace with a zero length value, or a non-zero length value that may be a dummy value and consistent with the VR**

** VR: Value Representation

Work originally done by Edern Haumont

Metadata

Release files for dicom-anonymizer 1.0.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dicom-anonymizer 1.0.4
File Size Uploaded Provenance Actions
dicom_anonymizer-1.0.4.tar.gz 11.5 kB Without provenance Details for dicom_anonymizer-1.0.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dicom-anonymizer 1.0.4
File Interpreter ABI Platform Actions
dicom_anonymizer-1.0.4-py2.py3-none-any.whl Python 3, Python 2 none any Details for dicom_anonymizer-1.0.4-py2.py3-none-any.whl

Total release size: 23.4 kB

Release files / dicom_anonymizer-1.0.4.tar.gz

Download URL dicom_anonymizer-1.0.4.tar.gz
Size 11.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9eab47b3be848d8fa27b61f379c231ff33f1d37ac7931eac457053da1adb7856
BLAKE2b-256 checksum
How to use checksums
b45a3eb3853b8b9a749457e3e540306b537b64f8866de7758719cdf539e7176b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.8.0

Release files / dicom_anonymizer-1.0.4-py2.py3-none-any.whl

Download URL dicom_anonymizer-1.0.4-py2.py3-none-any.whl
Size 11.9 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
c874f679d6cabf1469c8d5a57d6c90d7fff528ce85a37a562003d3f44d10fe61
BLAKE2b-256 checksum
How to use checksums
79b192ceed73b318bbd6ded3fc13438fedcf8d9f0bfdc2f19d6165c07ac32b01
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.1.0 requests-toolbelt/0.9.1 tqdm/4.42.0 CPython/3.8.0

Security for dicom-anonymizer 1.0.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page