-
Notifications
You must be signed in to change notification settings - Fork 1
Test Import Quarantine
Home | Installation Guide | User Guide | Admin Guide | User Tests
The “protocol” determines what type of data is allowed into the hospital project of DASHER. Only allowed files will be available for anonymisation and synchronisation – other files will be sent to a quarantine project. This mechanism can be utilised for instance to prevent data from modalities that are known to burn patient data into the images (such as some ultrasound machines) to inadvertently being insufficiently anonymised. At the moment DASHER only pseudonymises header information and not pixel data directly.
For this test we will be using MR data which is known not to have patient information burnt into the image data. Hence moving it out of the QUARANTINE project can be safely done.
- Modify the protocol such that it sends data from a Siemens Magnetom “Aera” into the quarantine project as described here. Edit the protocol of DASHER so that it has the following contents:
0008,0060 Modality ALL
0008,1090 ManufacturersModelName Aera
- Restart the tomcat server and leave sufficient time for the changes to take effect.
- Import the MR-dataset available in the folder
[user_test_data_dir]/importForQuarantine
either via the observed import folder or via a DICOM push into DASHER. - Monitor the import progress in the prearchive and see how the incoming data is destined for the QUARANTINE project.
- When the session was successfully archived into the QUARANTINE project, navigate to that session.
- In a realistic clinical workflow at this stage you would validate that the image data contained in the quarantined session does not contain burnt-in patient information. Here we know that this is not the case and can proceed.
- To move the quarantined session out of the QUARANTINE project into the hospital project, [follow the instructions provided here](Admin%20The QUARANTINE Project). Note, that the subject will remain listed in the QUARANTINE project, but without any session.
- Now, please revert the behaviour of DASHER to its default, i.e. no data is being sent to the QUARANTINE project. To do this modify the protocol as described here such that its contents is:
0008,0060 Modality ALL
0008,1090 ManufacturersModelName ALLOW ALL
- Restart the tomcat server and leave sufficient time for the changes to take effect. Usually 30 minutes.
- Verify that MR-data are now directly sent to the hospital project by importing the MR-dataset available in the folder
[user_test_data_dir]/importForQuarantine_part2
either via the observed import folder or via a DICOM push into DASHER. - Navigate to the hospital project and identify both MR sessions which are labelled RTMAC-TRAIN-023 and RTMAC-TRAIN-024.
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