Computing

User Tools

Site Tools

Trace: • billing_report_archive • accounts_and_vpn • using_ogs_sge • asking_for_help
xnat

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
xnat [2018/03/02 23:28]
mgstauff [Uploading Data] 		xnat [2018/03/19 21:21] (current)
mgstauff [Projects]
Line 32: Line 32:
 XNAT organizes data by Project. Each Project has private control of its data and a user must be granted access to a Project to view or edit data. XNAT organizes data by Project. Each Project has private control of its data and a user must be granted access to a Project to view or edit data.
  
 +==== User Roles and Permissions ====
 +
 +XNAT users can have different permissions within a Project:
 +
 +**Project Owners**: If you define additional project owners, they will have all of the permissions on your project that you do. They can read, insert, modify, and delete anything (and everything) associated with your project. They can also add additional users to your project and modify the data types associated with your project.
 +
 +**Project Members**: Members have the ability to manage the data in your project. They can read, insert, and modify subjects and experiments in your project. They cannot modify the project users and data types.
 +
 +**Project Collaborators**: Collaborators have read-only access on all of the data in your project. They cannot insert or modify data owned by your project. They can download your data and use it within their projects.
 +
 +[[https://wiki.xnat.org/display/XNAT17/Understanding+User+Roles+and+Permissions|Full details are here.]]
 ==== Uploading Data ==== ==== Uploading Data ====
  
Line 51: Line 62:
 password: you XNAT password\\ password: you XNAT password\\
  
-=== Pushing Data from PACS/Sectre or Research Scanner ===+See below for handling anonymization.
  
-XNAT can receive data directly from PACS/Sectre and from scanners such as the Stellar-Chance research scanner. This is typically called 'pushing' data to a 'DICOM (SCP) Receiver', or to an 'AE Title'. Please contact the admins for details.+=== Pushing Data from PACS/Sectra or a Scanner === 
 + 
 +XNAT can receive data directly from PACS/Sectra, from clinical scanners, and from research scanners such as the Stellar-Chance scanner. This is typically called 'pushing' data to a 'DICOM (SCP) Receiver', or to an 'AE Title', or simply 'to XNAT'. Please contact the admins for details.
  
 == Prearchive or Archive as Final Destination == == Prearchive or Archive as Final Destination ==
  
-Data can end up in either Archive or Prearchive at the completion of the upload/push process from a scanner or PACS/Sectre. This depends on project-specific settings. Namely, within a project's 'Manage' tab, it's set under 'Define Prearchive Settings'. Data always 'goes through' Prearchive briefly even if its final destination is Archive.+Data can end up in either Archive or Prearchive at the completion of the upload/push process from a scanner or PACS/Sectra. This depends on project-specific settings. Namely, within a project's 'Manage' tab, it's set under 'Define Prearchive Settings'. Data always 'goes through' Prearchive briefly even if its final destination is Archive. 
 + 
 +__We recommend__ setting this option to leave data in Prearchive, so your group knows it needs to be reviewed and probably have PHI removed before moving to Archive. The setting's label reads: 
 + 
 +  All image data should be placed in a temporary location (prearchive) before being manually transferred into the permanent archive.
  
 === Data Anonymization - IMPORTANT === === Data Anonymization - IMPORTANT ===
Line 71: Line 88:
 When data is moved from prearchive to archive, a Project-specific anon script is run, if one is set. Each Project can define its own anonymization script if the site-wide script is insufficient. When data is moved from prearchive to archive, a Project-specific anon script is run, if one is set. Each Project can define its own anonymization script if the site-wide script is insufficient.
  
-== Fields That Are NOT Anonymized - IMPORTANT == +== 'NA' Fields That Are NOT Automatically Anonymized == 
-When pushed from PACS/Sectre, the site-wide anon script does not remove DICOM 'Study Description', 'Patient Name', or 'Patient ID' ("SPP fields", for convenience). Thus it's up to the user to change these as needed to protect PHI. +**IMPORTANT** The site-wide anon script **does not remove** these fields:
  
-When pushed from a scanner that allows the user to modify the DICOM 'Patient Comments' or 'Study Comments' field before pushing the data, the user has the option to assign metadata that XNAT will use to new assign values to the SPP fields during import. Otherwise, the SPP fields be preserved as in a push from PACS. +**Non-Anonymized (NA) Fields** 
-https://wiki.xnat.org/pages/viewpage.action?pageId=36373129+^DICOM Tag ^ DICOM Tag Name ^ XNAT Field ^ 
 +|(0008,0050)    | Accession Number | <No direct map to XNAT> | 
 +|(0008,1030) | Study Description | Project ID | 
 +|(0010,0010) | Patient Name | Subject Label | 
 +|(0010,0020) | Patient ID | Session Label | 
 + 
 +__Note on Accession Number__: XNAT generates its own Accession Numbers ('Expt ID') in the format ''PICSL_xnat_<xyz>''. These are generated for Subjects and for Sessions, and are shown in the XNAT database, but are not used to modify DICOM headers. Yes, it can be confusing. 
 + 
 +The above 'NA' fields are not anonymized because they are used by users to identify data within XNAT before it can be given whatever kind of unique, anonymized identifiers that a research group's study protocol specifies. Before data is pushed from PACS/Sectra and clinical scanners, the DICOM header info cannot be modified, so this information must be preserved upon entry into XNAT. 
 + 
 +__It's up to the user to change these 'NA Fields' as needed to protect PHI.__ 
 + 
 +== Modifying NA Fields on the Research Scanner == 
 + 
 +When pushing data from the research scanner (which allows the user to modify the DICOM 'Patient Comments' or 'Study Comments' field before pushing the data), the user has the option to assign metadata that XNAT will use to new assign values to the some of the NA fields during import. Otherwise, the NA fields be preserved as in a push from PACS/Sectra. [[https://wiki.xnat.org/pages/viewpage.action?pageId=36373129|See here for details.]] 
 + 
 +== Modifying NA Fields During Move to Archive == 
 + 
 +If the user moves data manually from Prearchive to Archive (recommended), they have two options:
  
-If the user moves data manually from prearchive to archive, they have two options: 
 1) 'Review and Archive' - user is prompted to change the XNAT Subject (DICOM field 'Patient Name') and XNAT Session (DICOM field 'Patient ID') fields. 1) 'Review and Archive' - user is prompted to change the XNAT Subject (DICOM field 'Patient Name') and XNAT Session (DICOM field 'Patient ID') fields.
 +
 2) 'Archive' - data is archived without prompting user to change anything 2) 'Archive' - data is archived without prompting user to change anything
  
-When using the XNAT Desktop Upload Assistant (client-side tool for manual uploading), data goes straight to project archive. However after the data first enters prearchive, the user is prompted to change the Subject and Session fields before it's moved to archive.+== XNAT Upload Assistant and Anonymization == 
 +When using the XNAT Desktop Upload Assistant (client-side tool for manual uploading), data goes straight to project archive. However after the data first enters Prearchive, the user is prompted to change the Subject and Session fields before it's moved to Archive.
  
  
xnat.1520033302.txt.gz · Last modified: 2018/03/02 23:28 by mgstauff

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki