-
Notifications
You must be signed in to change notification settings - Fork 1
Test Pseudonymise Local research
Marc Modat edited this page Nov 20, 2020
·
1 revision
Home | Installation Guide | User Guide | Admin Guide | User Tests
In this test you will generate a project for local research in the pseudonymised XNAT and will perform several pseudonymisations into this project.
To perform the pseudonymisation in this test, you will need to have performed the following:
- In the non-anonymised XNAT a subject DECT_Phantom_Test has to have the session zzzDECTPhantom. This dataset was imported in this user test.
- In the non-anonymised XNAT a subject RTMAC-TRAIN-023 has to have the session RTMAC-TRAIN-023. This dataset was imported in this user test.
- In the non-anonymised XNAT a subject CtE_Lung_P_Planning_Exercise has to have the session CtE_Lung_P. This dataset was imported in this user test.
- The additional clinical trials have to be installed as done in this user test.
- Create a project with the name, running title, and ID as LOCAL for local research purposes. Follow these instructions.
- Set the permissions of the standard user created during the installation to member as described here.
- In the non-anonymised XNAT navigate to the session zzzDECTPhantom of subject DECT_Phantom_Test.
- Pseudonymise this with the following settings (as described here)
- Target project LOCAL
- And automatic ID generation
- Login to the pseudonymised XNAT, identify the newly added subject and session in the project LOCAL and follow the steps performed in this User Test to validate the pseudonymisation with your TPS.
- In the non-anonymised XNAT navigate to the session RTMAC-TRAIN-023 of subject RTMAC-TRAIN-023.
- Pseudonymise this with the following settings (as described here)
- Target project LOCAL
- And manual ID generation
- Clinical tial name No Trial
- Subject ID: localMRSubject
- Session ID: localMRSession
- Login to the pseudonymised XNAT, identify the newly added subject and session in the project LOCAL and follow the steps performed in this User Test to validate the pseudonymisation with your TPS.
- In the non-anonymised XNAT navigate to the session CtE_Lung_P of subject CtE_Lung_P_Planning_Exercise.
- Pseudonymise this with the following settings (as described here)
- Target project LOCAL
- And manual ID generation
- Clinical tial name trial_testLung
- Subject ID: lungSubject
- Session ID: sessionAccordingToTrial
- Login to the pseudonymised XNAT, identify the newly added subject and session in the project LOCAL and follow the steps performed in this User Test to validate the pseudonymisation with your TPS.
- You may have noted, that the edits in the structure label names were no longer required, since DASHER saved these changes to your subject. Also DASHER suggested the subject name that was used in the trial (c.f. this user test)
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