NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

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

Compare with Current View Page History

« Previous Version 5 Next »

This document is geared towards providing common templates for using CTP to submit data to NBIA.  For more information about configuring CTP pipelines please refer to the RSNA's CTP pipeline wiki section at: http://mircwiki.rsna.org/index.php?title=CTP-The_RSNA_Clinical_Trial_Processor#Pipelines.

 *please note, this page is under development and is not yet complete*

Overview

 CTP functions both as a client and server for transmitting data to NBIA.  In a typical installation of NBIA you will configure CTP clients for each submitting site that is sending data to your NBIA server.  At your server location you will have a CTP server to receive the data sent by the CTP clients.  In general you should not need to make any changes to the CTP server component as that is configured during the installation of NBIA.  However there are some scenarios where you will need to make changes to the CTP clients in order to meet the needs of the submitters providing you with data. 

Below are some common scenarios along with configuration file templates that will help you easily setup CTP clients for each situation.  Once you've downloaded the correct config.xml file based on your submitter's situation make a backup of any existing config.xml in your CTP root directory (if you had one already) and replace it with this copy.  Please keep in mind that you will need to update the HTTP Export information appropriately with the server and port of your NBIA server. 

 Images stored in PACS

In the scenario where the submitter's image data is all stored on their PACS you would leverage CTP's ability to import data directly via a DICOM send from the PACS.  Your configuration pipeline would be setup to process objects in the following manner: DICOM Import --> IDMap --> Anonymization --> HTTP Export.

  • Here is an example config.xml which you can use to achieve this: *attach file here*

 Images stored on HDD/CD

In a scenario where the submitter's data is stored on a hard drive or CD you will need an additional tool called FileSender.  Once you have downloaded and extracted FileSender you will use it to select the files from your computer to send them to the CTP client.

In this situation your configuration pipeline would be setup to process objects in the following manner: HTTP Import --> IDMap --> Anonymization --> Export.

  • Here is an example config.xml which you can use to achieve this: *attach file here*
  • In addition to having to update the HTTP Export information in the config.xml file you will also have to verify that FileSender is pointing to the correct server and port as indicated in the HTTP Import section of the config.xml file
  • No labels