Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This section provides guidance on how to use XNAT to create an anonymization script that meets your requirements. XNAT depends on DicomEdit to provide anonymization capabilities. The operations performed during anonymization are determined by the contents of a script written in a custom DicomEdit Language.  See  DicomEdit 6.0 Language Reference and DicomEdit 4.2 Language Reference for details on script syntax.  For details on all the places anonymiztion occurs in XNAT, see Where Anonymization Happens in XNAT.  For details on how to provide your script to XNAT, see Site-wide Session Upload and Anonymization Settings and Project Data Import and Anonymization Settings. But, how do you use XNAT to create a correct script in the first place?

There are two aspects to writing a valid script: syntax and semantics.

Getting the Syntax Right

The DicomEdit script must be written to conform with the rules of the language. We currently do not have a tool that will automatically validate a script. We must resort to trial and error. Sending data to XNAT through an invalid script will cause the underlying DicomEdit to throw errors. These errors will be captured in XNAT's log files. Of particular interest are dicom.log and anon.log.

Getting the Semantics Right

Even if the script is valid syntax, does it really do what you intend it to do?  Here, there is no substitute for running test data through your script and manually verifying that the contents of the transformed DICOM objects are as intended.  XNAT provides a number of places that provide access to a "DICOM Dump". This is a view of all the attributes that exist in the DICOM object and their values.

  • No labels