Page History

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.

Overview

 CTP 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. 

...

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.

...

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

...