-
Notifications
You must be signed in to change notification settings - Fork 1
Admin Setting Quarantine Protocol
Home | Installation Guide | User Guide | Admin Guide | User Tests
See The QUARANTINE Project for more details about what the QUARANTINE project is, how it is used. [How to move data out of the QUARANTINE project is described here](Guide%20The QUARANTINE%20Project#moving-data-out-of-the-quarantine-project). This page explains how to control what data is sent into the QUARANTINE project.
The modalities and scanner models that will be sent to the QUARANTINE project are specified in a text file, protocol.txt. If you have not installed DASHER, you can edit the file [install_dir]/scripts/protocol.txt to set the protocol. If you wish to make changes to an existing installation, make changes to [storage_path]/scripts1/protocol.txt. Note: Whenever changes are made to the protocol of an existing installation, the tomcat server within the containers needs to be restarted for the changes to take effect.
An example of the contents of this file is:
0008,0060 Modality ALL
0008,1090 ManufacturersModelName ALLOW ALL
The first line specifies which modalities are allowed into the hospital project. Note - this is an Included list, i.e. the modalities that are listed ARE allowed into the hospital project - any modalities which are not listed will be sent to the QUARANTINE project. To allow all modalities into the hospital project use the ALL keyword as in the example above.
The second line specifies which scanner models are not allowed in the hospital project. Note - this is an Excluded list, i.e. the models that are listed are NOT allowed in the hospital project and will instead be sent to the QUARANTINE project. If there are no models that should be sent to the QUARANTINE project the the ALLOW ALL keywords should be used as in the example above.
I.e. the example protocol above will not send any data to the QUARANTINE project. Another two examples are shown below:
0008,0060 Modality CT, RTSTRUCT, RTPLAN, RTDOSE
0008,1090 ManufacturersModelName ALLOW ALL
0008,0060 Modality ALL
0008,1090 ManufacturersModelName Pretend_Model_Name
In the first example above only DICOM files that have the Modality tag in their header set to CT, RTSTRUCT, RTPLAN, or RTDOSE will be allowed into the hospital project, all other will go to the QUARANTINE project.
In the second example DICOM files that have the ManufacturersModelName tag in their header set to Pretend_Model_Name will be sent to the QUARANTINE project, all other DICOM files will go to the hospital project.
Navigate: Home | Installation Guide | User Guide | Admin Guide | User Tests
New Pages:
- Test Release Version 4 Notes
- First time install on Windows
- First time install on Linux
- Updating DASHER on Windows
- Updating DASHER on Linux
- Editing xnat.cfg
- Building DASHER on Windows
- Building DASHER on Linux
- Installing the Processing Pipelines
- Setting up XSync
- Troubleshooting
- Logging in to the Servers
- Overview of DASHER
- Importing Data into DASHER
- Pseudonymising Data
- Uploading Data to a Remote Server
- Exporting Data from DASHER
- The QUARANTINE Project
- Create and Edit Users
- Adding Clinical Trials
- Managing the QUARANTINE Project
- Setting Quarantine Protocol
- Adding a Project for Local Research
- Adding a Project for a Remote Server
- Changing the Pseudonymisation
- Installing SSL Certificates
- Maintenance
- Download Test Data
- Installing DASHER
- Installing Plugins
- Adding Clinical Trial
- Creating a New User
- Importing Data into DASHER
- Pseudonymising Data 1
- Export Pseudonymised Data Locally
- Upload Data (XSync)
- Import - DICOM push
- Import - Duplicate
- Import - Single RTSTRUCT
- Import - Quarantine
- Pseudonymise - Edits
- Pseudonymise - Missing structure
- Pseudonymise - Local research
- Restarting Docker