Need Help?

Arcagen - NET / NEC G3

Arcagen is an EORTC/SPECTA pan-European project that aims to recruit 1000 rare cancer patients from different tumour domains of EURACAN. This study collected samples from advanced or metastatic rare cancer from patients older than 12, and analysed them using Foundation Medicine next-generation sequencing (NGS) panels (FoundationOne CDx for FFPE samples or FoundationOne Liquid CDx for blood samples). Here were are submitting the dataset that contains NGS files in .BAM format from 85 patients with extra-pulmonary neuroendocrine tumour or cancer grade 3 (NET / NEC G3).

Request Access

EORTC Data Sharing POL008

https://www.eortc.org/data-sharing/ https://www.eortc.org/app/uploads/2017/03/pol008.pdf Data Sharing Policy 008 1 PURPOSE To define the terms and conditions under which electronic records of individual data from all or from subsets of the patients from EORTC studies may be shared with other organizations or individual researchers for the purpose of scientific research projects or may be posted on data repositories. 2 SCOPE This policy applies whenever electronic records of individual data from all or from subsets of the patients from EORTC studies are shared with individual researchers not employed by EORTC Headquarters or with other academic or non-academic (including for profit) organizations; except for the routine safety reports to authorities and for contractually agreed data transfers to third parties during the course of a trial. This policy does not apply when data of their own patients are transferred back to an EORTC site or when data of the patients from an academic Group that contributed to an intergroup study managed at EORTC are transferred back to that Group, since this requires no specific approval beyond the study intergroup agreement. The shared data may include data generated from EORTC translational research projects. However, only requests for data available to the EORTC Headquarters are covered by this policy. Requests for access and use of Human Biological Material (HBM) are covered by a separate policy (EORTC POL020). Requests for additional data collection usually require further ethical committee and/or other regulatory bodies to review the project and may also require obtaining additional patient consent and/or authorization. Consequently, the information obtained is often incomplete. Retrospective collection of data is expensive and time consuming for the EORTC. Therefore, requests for projects necessitating further data collection must be submitted for review to the EORTC using the appropriate channels (see Policy 016). 3 DEFINITIONS ♦ Coded data: Refers to the result of the process of replacing personal identifiers linked to data or HBM by a code for confidentiality and privacy reasons (also, known as "linked anonymized" or "pseudonymized"). To be distinguished from “anonymized” that refers to when the link between the data and human biological material is irreversibly broken. ♦ EORTC data: All and any electronic records of human clinical and biological data (included but not limited to genetic, any -omic or other molecular data) or centrally stored imaging data in Digital Imaging and Communications in Medicine (DICOM) file format obtained from patients entered in EORTC studies; i.e. individual patient data. Data does not include human biological material samples. As EORTC works exclusively with coded data, the term "EORTC data" in the present document refer exclusively to coded EORTC data. ♦ Data applicant: The person seeking access to EORTC data. ♦ External research project (ERP): A research project that uses EORTC data, the statistical analyses and publications of which are not centralized at the EORTC Headquarters, and thus requires these data to be released outside EORTC Headquarters. ♦ EORTC Research project (EORTC-RP): An EORTC research project that uses EORTC data and the statistical analyses and publications of which are centralized at the EORTC Headquarters but that may require that data be released outside EORTC Headquarters to partner researchers or research organizations. ♦ Data Sharing Coordinator: The EORTC staff member responsible for reviewing, approving and following up the data sharing agreements. ♦ Data Access Committee (DAC) Coordinator: The EORTC Headquarters staff member who is member of the different EORTC DACs. He/she is responsible for executing the decisions of the ODAC regarding EORTC genetic, any -omic and other molecular data stored on access controlled external repositories and approve the posting of data by investigators on public repositories. He/she is also responsible for following-up the decisions of the IDAC regarding the release of EORTC images stored on access controlled imaging platforms in relationship with the EORTC Headquarters expert in imaging translational research. ♦ EORTC OMICS Data Access Committee (ODAC): The EORTC DAC responsible for making decisions regarding the access to EORTC genetic, any -omic and other molecular data that are stored in access controlled external repositories and for granting authorization to post data on public repositories. Inside the EORTC Headquarters, the ODAC functions under the hierarchical supervision of the Medical Director and it reports to the chair of the Translational Research Committee at the EORTC organization level. The ODAC is composed of at least the DAC Coordinator, the Head of the EORTC Translational Research, radiotherapy, and imaging department (or delegate) and at least one more staff member from the Translational Research, Radiotherapy, and Imaging department of the EORTC Headquarters. ♦ EORTC Imaging Data Access Committee (IDAC): The EORTC DAC responsible for making decisions regarding the access to EORTC radiological images that are stored in access controlled imaging platforms. Inside the EORTC Headquarters, the IDAC functions under the hierarchical supervision of the Medical Director and it reports to the chair of the Translational Research Committee at the EORTC organization level. The IDAC is composed of at least the DAC Coordinator, the Head of the EORTC Translational Research, radiotherapy, and imaging department (or delegate) and at least one more staff member from the Translational Research, Radiotherapy, and Imaging department of the EORTC Headquarters. 4 POLICY EORTC is committed to ensuring that the data generated from its studies be put to good use by the cancer research community and, whenever possible, are translated to deliver patient benefit. It is therefore EORTC's policy to consider for sharing upon request from qualified scientific and medical researchers all data generated from its research whilst safeguarding intellectual property, the privacy of patients and confidentiality. Considering that ongoing research contributing to the completion of datasets must not be compromised by premature or opportunistic sharing and analysis of data, the EORTC will not release the data of its study until the primary study results have been published; unless authorization for release has been granted according to the terms of EORTC Policy 009. Whilst EORTC complies with the OECD Principles and Guidelines for Access to Research Data from Public Funding and with the National Institutes of Health Final Statement on Sharing Research Data released on February 26, 2003; it is committed to do so within the limits needed to guarantee the protection of personal data in accordance with the EU data protection rules and other applicable European legislation. Upon explicit approval of EORTC, coded individual patient data that were generated in the framework of translational research studies may be deposited in online public repositories or databases with or without restrictions on access. Authorization for posting data will be granted by the ODAC according to the type and level of the data, and the potential risk associated to the data release. Restricted controlled access to the posted data will then be under the management of the ODAC, unless a specific process/committee exists for the repository to which the ODAC would already have delegated responsibilities. EORTC also reserves itself the right to refuse sharing of data if it judges that the data repository in question does not offer sufficient system protection. 5 HOW TO REQUEST EORTC DATA Data applicants are required to submit a research proposal to document the legitimacy of the research question and the qualifications of the requestor. Research proposals should include, and will be evaluated against the following: a description of the data being requested, including the hypothesis to be tested; the rationale for the proposed research; the analysis plan; a publication and posting plan; qualifications and experience of the proposed research team; and the source of any research funding. Some projects that are performed outside the premises of the EORTC Headquarters and thus require data sharing are however conducted in close collaboration with EORTC Headquarters staff or EORTC Groups, so that the resulting publication(s) will be co-authored by an EORTC staff and/or be published on behalf of EORTC. Such circumstances must be declared upfront in the data submission form so that appropriate terms of use are agreed upon upfront. EORTC may also request to be associated to the research when it finds it relevant. Whenever this was not agreed upfront, and/or there is no EORTC co-author, but the publication appears 'on behalf of EORTC' or if “EORTC” appears in the title, then the use of that mention will require an additional approval from EORTC to modify the initially agreed terms of use. Instructions and a request form are available at http://www.eortc.org/investigators/data-sharing/. All questions concerning EORTC data sharing should be addressed to DataSharing@eortc.be. 6 REVIEW AND APPROVAL OF DATA ACCESS REQUESTS Review of the requests by the relevant EORTC bodies is coordinated by the Data Sharing Coordinator. The scientific merit of each specific request will be evaluated as well as its feasibility: whether there is sufficient data to provide adequate information for analysis, the availability of the required data and the potential costs. Any release of data will also consider individual patient's rights to privacy. The authorization for release will be granted by the Data Sharing Coordinator once all reviewers (detailed in the sections below) have approved the request, and provided legal and contractual agreements allow it. In case of disagreement among study coordinators and/or steering committees of the studies for which data is requested, the chairpersons of the EORTC groups who conducted the trial will arbitrate their positions. EORTC reserves itself the right to deny access to data if similar research is already being conducted by EORTC itself. The EORTC will notify the data applicant of the final decision by e-mail within two (2) months of the application and will inform of the reasons for rejection, whenever data access is not granted. The timing of the data release will be decided by the study statistician for the databases located at EORTC Headquarters. The timing for granting access to genetic, any -omic and other molecular data stored on access controlled external depositories, and to images stored on access controlled imaging platforms will be decided by the DAC Coordinator in order to maintain the study integrity, in accordance with EORTC POL009. The possibility of transferring any EORTC data will be checked against the terms of the Patient Informed Consent. The review process is adapted to the nature of the data that is requested, of the research purpose and of whether the data applicant is from academia as explained below. 6.1 Release of data for projects not yet approved by EORTC The proposal will be reviewed by the steering committee or study coordinator of the studies for which data is sought and by the chairpersons of the EORTC groups who conducted the trial; by the study statistician(s), and by the EORTC Data Sharing Coordinator, as well as by the EORTC staff or EORTC members that are identified as future co-authors of the resulting publication(s). Whenever the request concerns data from the quality of life studies (field studies and the like) the proposal will be approved by representatives of the Quality of Life Group through the Quality of Life Unit (see 6.6). Additionally, when such requests involve EORTC genetic, any -omic or other molecular data stored on access controlled external repositories or EORTC images stored on access controlled imaging platforms, review and approval of the ODAC or IDAC, respectively, is also needed. Finally, release of data collected in a clinical or translational research study conducted under a binding agreement between EORTC and a pharmaceutical/biotechnology company must be in compliance with the terms of this agreement and must be approved by both EORTC and the company. The terms of use in Section 7 apply. 6.2 Release of data for projects already approved by EORTC Specific projects linked to EORTC studies or research projects for example but not limited to translational research projects may involve sending clinical data to other locations, such as to the institution performing the lab work, for analysis. As such, the necessary data exchanges required for conducting such projects may be already approved by the EORTC. If the specific data required and a summary of the analysis plans were clearly described in the study protocol approved by EORTC then data requests for these projects will be approved without further scientific review. The terms of use in Section 7 still apply. If the specific data required and a summary of the analysis plans were clearly described in a research project that was already approved by EORTC Translational Research Advisory Committee or if the data request concerns data release related to an EORTC-RP then the data request will be approved without further scientific review. The terms of use in section 7 still apply Additionally, when such requests involve EORTC genetic, any -omic or other molecular data stored on access controlled external repositories or EORTC images on access controlled imaging platforms, review and approval of the ODAC or IDAC, respectively, is also needed. The terms of use in Section 7 apply. If the requested data or the planned analyses go beyond what EORTC has already agreed then the request must be reviewed by the EORTC, as described in Section 6.1 above. 6.3 Requests for data sets to use for illustration of statistical methodology Requests for data sets to use for illustration of statistical methods in papers intended for publication in the statistical literature follow a simplified path. The Data Sharing Coordinator will assess with the Heads of the statistics department if the data set appears to be appropriate for the project. If so, the Data Sharing Coordinator can approve the request without further review. However, when such requests involve data from studies fully supported by a pharmaceutical company, the necessary approval from the company will be obtained, in accordance with the contractual agreements between EORTC and that company. The study coordinators of the studies involved and the chairpersons of the EORTC groups who conducted the trial(s) will be informed that the data is being used for that purpose. The terms of use in Section 7 still apply. 6.4 Requests for accessing only genetic, any -omic and other molecular data that are stored on access controlled external repositories Such requests will be handled through ODAC which will seek approval of the relevant trial steering committee. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.5 Requests for accessing imaging data in DICOM file format Such requests will be handled through the IDAC which will seek approval of the relevant trial steering committee. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.6 Requests for accessing data of Quality of Life studies Such requests will be handled through the EORTC Quality of Life department which will seek approval of the QLG Group steering committee and the study PI. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.7 Requests from commercial entities or with commercial purpose Requests emanating from non-academic researchers or from for-profit organizations will follow the review path described in sections 6.1 to 6.5 above. They will additionally be reviewed by the EORTC Directors. Fees may apply and will be calculated on a case by case basis. The feasibility of transferring the data for non-academic research will also be checked against the terms of the Patient Informed Consent. 7 TERMS OF USE Upon submission of the request, the data applicant must agree to the Terms of Use specified in the application form The EORTC must be acknowledged for sharing the data for the research. Unless an EORTC staff is co-authoring the publication or if it was agreed upfront that the publication would be "on behalf of EORTC" or as "EORTC research", the publication must contain the following disclosure “The contents of this publication and methods used are solely the responsibility of the authors and do not necessarily represent the official views of the EORTC ". Additionally, for all projects, the data applicant commits to provide EORTC with references of any publication resulting from research that used EORTC data within two (2) months of the publication; unless the publication is made "on behalf of EORTC" or if "EORTC appears in the study title" in which case the data applicant must submit the publication to DataSharing@eortc.be prior to presentation and/or submission of the results for publication. EORTC reserves itself the right to request the establishment of a formal contract in addition to the above terms of use, when sharing particularly sensitive data and/or for requests in the scope of section 6.5. 8 TERMINATION OF THE AGREEMENT The data applicant must notify EORTC of the completion of the project. This is best done by an email addressed to DataSharing@eortc.be. EORTC reserves itself the right to cease data sharing agreements upon breach of the agreed terms and conditions for use. Requests for extension of existing data sharing agreement must be requested online using the data request form (see section 5). The data request must clearly stipulate that the demand is an extension of an existing agreement and provide reference to that former agreement. Review and approval of extensions follow the rules specified in section 6 above. 9 QUESTIONS Questions regarding the present policy or data sharing should be addressed by email to DataSharing@eortc.be.

Studies are experimental investigations of a particular phenomenon, e.g., case-control studies on a particular trait or cancer research projects reporting matching cancer normal genomes from patients.

Study ID Study Title Study Type
EGAS50000000644 Exome Sequencing

This table displays only public information pertaining to the files in the dataset. If you wish to access this dataset, please submit a request. If you already have access to these data files, please consult the download documentation.

ID File Type Size Located in
EGAF50000217039 bai 2.6 MB
EGAF50000217040 bam 11.2 GB
EGAF50000217041 bai 4.3 MB
EGAF50000217042 bam 2.4 GB
EGAF50000217043 bai 2.6 MB
EGAF50000217044 bam 9.3 GB
EGAF50000217045 bai 2.9 MB
EGAF50000217046 bam 12.3 GB
EGAF50000217047 bai 2.8 MB
EGAF50000217048 bam 15.2 GB
EGAF50000217049 bai 4.4 MB
EGAF50000217050 bai 2.6 MB
EGAF50000217051 bam 2.4 GB
EGAF50000217052 bam 2.5 GB
EGAF50000217053 bai 4.2 MB
EGAF50000217054 bam 2.4 GB
EGAF50000217055 bai 2.7 MB
EGAF50000217056 bai 4.2 MB
EGAF50000217057 bai 4.4 MB
EGAF50000217058 bam 2.6 GB
EGAF50000217059 bai 4.0 MB
EGAF50000217060 bai 4.0 MB
EGAF50000217061 bam 2.6 GB
EGAF50000217062 bam 2.1 GB
EGAF50000217063 bai 2.6 MB
EGAF50000217064 bam 2.5 GB
EGAF50000217065 bai 2.8 MB
EGAF50000217066 bai 2.6 MB
EGAF50000217067 bam 10.2 GB
EGAF50000217068 bai 4.4 MB
EGAF50000217069 bai 4.4 MB
EGAF50000217070 bai 4.5 MB
EGAF50000217071 bai 4.5 MB
EGAF50000217072 bam 2.4 GB
EGAF50000217073 bai 4.4 MB
EGAF50000217074 bam 14.9 GB
EGAF50000217075 bai 4.6 MB
EGAF50000217076 bam 2.1 GB
EGAF50000217077 bai 4.5 MB
EGAF50000217078 bai 4.3 MB
EGAF50000217079 bam 2.3 GB
EGAF50000217080 bai 4.4 MB
EGAF50000217081 bam 2.4 GB
EGAF50000217082 bai 4.2 MB
EGAF50000217083 bam 12.5 GB
EGAF50000217084 bai 4.5 MB
EGAF50000217085 bam 2.4 GB
EGAF50000217086 bai 4.4 MB
EGAF50000217087 bam 2.3 GB
EGAF50000217088 bam 2.6 GB
EGAF50000217089 bai 4.3 MB
EGAF50000217090 bai 4.5 MB
EGAF50000217091 bam 17.4 GB
EGAF50000217092 bai 3.0 MB
EGAF50000217093 bam 2.4 GB
EGAF50000217094 bai 4.2 MB
EGAF50000217095 bai 2.8 MB
EGAF50000217096 bam 2.1 GB
EGAF50000217097 bai 4.4 MB
EGAF50000217098 bam 2.3 GB
EGAF50000217099 bai 4.6 MB
EGAF50000217100 bam 17.6 GB
EGAF50000217101 bai 2.8 MB
EGAF50000217102 bai 3.0 MB
EGAF50000217103 bam 16.4 GB
EGAF50000217104 bai 2.8 MB
EGAF50000217105 bai 4.6 MB
EGAF50000217106 bam 16.2 GB
EGAF50000217107 bam 2.1 GB
EGAF50000217108 bai 4.4 MB
EGAF50000217109 bam 2.4 GB
EGAF50000217110 bai 4.6 MB
EGAF50000217111 bam 2.2 GB
EGAF50000217112 bai 4.5 MB
EGAF50000217113 bam 2.2 GB
EGAF50000217114 bai 4.4 MB
EGAF50000217115 bam 2.5 GB
EGAF50000217116 bai 4.4 MB
EGAF50000217117 bai 4.1 MB
EGAF50000217118 bam 2.4 GB
EGAF50000217119 bai 4.4 MB
EGAF50000217120 bam 3.2 GB
EGAF50000217121 bai 4.5 MB
EGAF50000217122 bam 3.3 GB
EGAF50000217123 bam 3.2 GB
EGAF50000217124 bai 4.6 MB
EGAF50000217125 bam 2.9 GB
EGAF50000217126 bai 4.3 MB
EGAF50000217127 bam 2.3 GB
EGAF50000217128 bai 4.5 MB
EGAF50000217129 bam 2.3 GB
EGAF50000217130 bam 3.1 GB
EGAF50000217131 bai 3.0 MB
EGAF50000217132 bam 17.9 GB
EGAF50000217133 bai 4.4 MB
EGAF50000217134 bam 2.2 GB
EGAF50000217135 bai 4.3 MB
EGAF50000217136 bam 3.1 GB
EGAF50000217137 bam 2.2 GB
EGAF50000217138 bam 2.2 GB
EGAF50000217139 bam 2.4 GB
EGAF50000217140 bam 17.1 GB
EGAF50000217141 bai 2.8 MB
EGAF50000217142 bai 4.4 MB
EGAF50000217143 bam 3.2 GB
EGAF50000217144 bai 4.5 MB
EGAF50000217145 bai 4.5 MB
EGAF50000217146 bam 3.2 GB
EGAF50000217147 bai 2.9 MB
EGAF50000217148 bam 17.1 GB
EGAF50000217149 bai 4.4 MB
EGAF50000217150 bam 2.1 GB
EGAF50000217151 bai 4.2 MB
EGAF50000217152 bam 2.1 GB
EGAF50000217153 bam 9.3 GB
EGAF50000217154 bam 9.9 GB
EGAF50000217155 bai 2.9 MB
EGAF50000217156 bam 2.1 GB
EGAF50000217157 bai 4.3 MB
EGAF50000217158 bam 2.4 GB
EGAF50000217159 bai 4.3 MB
EGAF50000217160 bai 2.7 MB
EGAF50000217161 bam 2.0 GB
EGAF50000217162 bai 4.5 MB
EGAF50000217163 bai 4.5 MB
EGAF50000217164 bam 2.2 GB
EGAF50000217165 bam 2.3 GB
EGAF50000217166 bam 14.1 GB
EGAF50000217167 bai 4.0 MB
EGAF50000217168 bai 4.6 MB
EGAF50000217169 bai 4.5 MB
EGAF50000217170 bai 4.4 MB
EGAF50000217171 bam 21.5 GB
EGAF50000217172 bam 3.1 GB
EGAF50000217173 bai 4.4 MB
EGAF50000217174 bai 4.3 MB
EGAF50000217175 bam 3.1 GB
EGAF50000217176 bam 16.9 GB
EGAF50000217177 bam 3.5 GB
EGAF50000217178 bai 4.4 MB
EGAF50000217179 bam 2.7 GB
EGAF50000217180 bam 2.3 GB
EGAF50000217181 bam 2.0 GB
EGAF50000217182 bam 2.5 GB
EGAF50000217183 bam 2.0 GB
EGAF50000217184 bam 2.5 GB
EGAF50000217185 bam 16.5 GB
EGAF50000217186 bai 2.7 MB
EGAF50000217187 bai 4.5 MB
EGAF50000217188 bam 2.8 GB
EGAF50000217189 bai 2.8 MB
EGAF50000217190 bam 2.5 GB
EGAF50000217191 bai 4.2 MB
EGAF50000217192 bai 2.7 MB
EGAF50000217193 bam 11.7 GB
EGAF50000217194 bai 4.5 MB
EGAF50000217195 bam 2.4 GB
EGAF50000217196 bai 2.9 MB
EGAF50000217197 bai 2.6 MB
EGAF50000217198 bam 2.1 GB
EGAF50000217199 bam 14.3 GB
EGAF50000217200 bam 12.5 GB
EGAF50000217201 bam 16.7 GB
EGAF50000217202 bai 4.5 MB
EGAF50000217203 bam 2.0 GB
EGAF50000217204 bai 2.9 MB
EGAF50000217205 bai 3.9 MB
EGAF50000217206 bam 2.7 GB
EGAF50000217207 bai 4.2 MB
EGAF50000217208 bam 2.3 GB
170 Files (500.2 GB)