 |
Page History
...
Using CTP for local de-identification
Sample config.xml: LocalDeId-config.xml
- 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
There are two common ways which you may wish to configure CTP to send data to NBIA.
- De-identification with local QC review - This is useful if the submitter wishes to do their own review of the de-identified data prior to providing it to the NBIA host. The NBIA host can subsequently choose to perform additional quality control reviews when the data reaches their server.
- De-identification with central NBIA QC review - This is useful if the group performing the submission is the same as the people managing the NBIA server. In this scenario the users can leverage NBIA's built in quality control tools to review the data before making it "visible" to end users of the NBIA
...
- site.
Sample configurations for both scenarios are described below, along with pointers to which information will need to be filled in based on your particular use case.
De-identification with local QC review
Sample config.xml: LocalDeId-NBIA-config.xml
Customizations required for use:
De-identification with central NBIA QC review
Sample config.xml: LocalDeId-Automated-NBIA-config.xml
- 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
Using CTP to submit to XNAT
Sample config.xml: (still needs to be written)
- Submitting directly to XNAT
- follow CTP installation steps above
- utilize/tweak XNAT centric config.xml (provide link)
- Submitting to XNAT after local de-identification
- editing your existing config.xml to add an XNAT export service
- sending your de-identified data to the export service
