# HTAN Checklist for Acceptance of Data When an HTAN Data Contributor is considering contribution of data to the HTAN DCC, this checklist should be used by the Data Contributor to determine if the data meets basic HTAN contribution requirements. !!! All HTAN centers must have an executed Human Tumor Atlas Network DMSA (Internal Data and Materials Sharing Agreement) (HTAN DMSA) with Sage Bionetworks prior to contributing data to the HTAN Data Coordinating Center (DCC). Sean Hanlon from the NCI will be reaching out to new Centers to coordinate collection of DMSA signatures. !!! | Checklist of Requirements | Agreement / Policy Reference | |---------------------------|------------------------------| | The data meets my data quality control standards and those established by the HTAN DCC. | HTAN DMSA Section 2.a: “Contributor will transfer to the HTAN-DCC De-identified Datasets generated as part of the HTAN that either pass the QC standards that are in effect for HTAN at the time, or pass the Contributor’s QC standards in cases where HTAN standards do not exist.” | | The data contribution includes all extra information needed to interpret and understand the data. | HTAN DMSA Section 2.b: “Supporting information including the Data annotation manifest necessary to interpret the submitted Data must be included with the submission and will be reviewed by the HTAN-DCC for completeness.”| |The data are de-identified according to the current standards for HTAN. See [Data De-identification](../data_submission/Data_Deidentification.md).| HTAN DMSA Section 6.a: “The Parties agree that all Data disclosed to and from the Parties shall be De-identified so that Data Subjects cannot be ascertained directly or through secondary data use in accordance with HIPAA.” | | The data were collected according to protocols approved by an IRB or its equivalent. | HTAN DMSA Section 6.b: “Contributor represents that all Data and Material derived from HTAN that Contributor provides to Recipient were collected pursuant to and in accordance with protocols approved by an IRB or its equivalent;[...]”| | The contribution of the data is consistent with applicable U.S. laws, regulations, and its institutional policies. | HTAN DMSA Section 6.c: “Contributor represents that the Data and Material submission to the HTAN-DCC and/or Recipient are consistent with applicable U.S. laws, regulations, and its institutional policies;[...]”| | I affirm that an IRB or its equivalent assures that the data and sharing of the data is consistent with the Informed Consent of the Data Subject(s) from whom the Data and Materials were obtained. | HTAN DMSA Section 6.d: “The Contributor represents that an IRB/Privacy Board or equivalent body, as applicable, has assured that submission and subsequent sharing of Data and Materials are consistent with the Informed Consent of the Data Subject(s) from whom the Data and Materials were obtained.” | | The data contribution includes acceptable HTAN data types: clinical data, biospecimen data, genomic sequencing data and/or multiplex imaging, contextual assay metadata and/or assay data files. | [HTAN Data Model](../data_model/overview.md) | | I understand the data I contribute will be hosted and shared via the HTAN-DCC Portal or other HTAN-designated repositories and will be subject to and governed by all the terms and conditions of this Agreement, the NIH Data Sharing Policy and NIH Genomic Data Sharing Policy. | HTAN DMSA Section 3.a: ”Any Data that Contributor generates as part of the HTAN Project will be hosted and shared using the HTAN-DCC Portal or other HTAN-designated repositories and will be subject to and governed by all the terms and conditions of this Agreement, the NIH Data Sharing Policy and NIH Genomic Data Sharing Policy.”| | I understand that if the data are found to include PHI, then the data will be removed from the HTAN-DCC Portal and that it is my responsibility to remove the PHI and re-submit the data to the HTAN-DCC as soon as possible.|HTAN DMSA Section 2.c: “The HTAN-DCC and the Data Contributor will review Data after submission, before it is released, to verify that no PHI has been submitted accidentally. If there is presence of PHI, i. HTAN-DCC will notify the Contributor of the presence of PHI and delete files that contain PHI from the HTAN-DCC Portal, ii. Contributor will resubmit Data without PHI. Data quality corrections will be submitted as soon as possible. [...]”| |I understand that if data quality corrections for the data are required, then I am responsible for removing the data from the HTAN-DCC Portal, making corrections, and re-submitting the data as soon as possible. | HTAN DMSA 2.c: “[...] Data quality corrections will be submitted as soon as possible.” | If the Data Contributor is able to affirm their understanding of this checklist and that the data meet the criteria in this checklist, then the Data Contributor may engage their HTAN [Data Liaison](../data_submission/Data_Liaisons.md) to begin the data contribution process. If the Data Contributor has concerns about the acceptability of their data contribution, the Data Contributor may contact the HTAN DCC to request Data Contribution Support via the HTAN Help Desk: https://sagebionetworks.jira.com/servicedesk/customer/portal/1 When necessary, a final determination regarding acceptability of data to HTAN DCC will be at the discretion of NCI and the HTAN DCC PIs. If the decision is that the data should not be shared with the HTAN DCC, Sage can work with the Data Contributor to share the data elsewhere in Synapse.