Page History

...

It's possible you may not actually need to install anything prior to using CTP and there are only 2 potential things you may need to obtain prior to using CTP:

1. [Java|http://www.oracle.com/technetwork/java/javase/downloads/index.html] 1.Java 1.5 (or better) JRE must be present on the system. Java 1.6 is recommended.  Note that only the JRE is required, not the JDK, and therefore this is already installed on most typical computers.
2. If you wish to utilize some of CTP's advanced functionality you must also install the Java Advanced Imaging ImageIO Tools. Note that this is not required if all you wish to do is use CTP to de-identify DICOM images or submit de-identified images to NBIA.

...

Once you've installed CTP you must setup some configuration options prior to running it. All of these options are specified with the config.xml file located in the root of the CTP installation directory. This can be easily modified using any text editor and is divided into several key sections"pipeline stages" for importing, processing, and exporting your data. The rest of this section explains the basic structure of the config.xml file. For practical ready-to-use config.xml files tailored to for common use cases please skip continue on to the next section on Example use cases and configuration files.

...

1. Anonymizers - These can be used to systematically de-identify the contents of DICOM header elements, or of XML metadata.
2. Filters - Very similar to Anonymizers, these can be used to check for specific conditions within DICOM or XML. If the conditions are met these can be "filtered" out for further review prior to processing.
3. IDMap - This pipeline stage can be used to generate a mapping of identified and de-identified values of important DICOM elements such as PatientID, UIDs, or accession numbers.
4. DatabaseVerifier - This is mainly utilized in conjunction with NBIA. It allows CTP to keep a record of every object sent to the remote NBIA server and subsequently query the NBIA database to ensure it was received to verify no images were lost in transit.

Exporting your data

The most common ways of exporting the data which you've processed in CTP include:

1. DICOM export - This is useful for sending your processed data back to a PACS
2. HTTP(s) export - This is the method typically utilized to submit your data to an NBIA server (or potentially XNAT - testing needs to be performed to see how this would work)
3. Hard drive export - This is called a Storage Service in CTP, which can simply store the processed data to a specified location on a hard drive.

Full details relating to how each of these can be customized along with the other export methods can be found on the RSNA wiki in the Export Services section and the Storage Service section respectively.

4. Example use cases and configuration files

Using CTP for local de-identification

• running the jar file
• sending your source data to CTP
  • Archive Import
  • File Sender
  • PACS
• going to the browser
• viewing status page
• troubleshooting
  • quarantines
  • log files

Using CTP to submit to NBIA

• Submitting directly to NBIA
  • follow CTP installation steps above
  • utilize/tweak NBIA centric config.xml (provide link)
• Submitting to NBIA after local de-identification
  • editing your existing config.xml to add an NBIA export service
  • sending your de-identified data to the export service