Need Help?

Intellance-2: TruSight Tumor 170 panel based DNA-seq

Intellance-2: TruSight Tumor 170 panel based DNA-seq

Request Access

DUO:0000019
version: 2021-02-23

publication required

This data use modifier indicates that requestor agrees to make results of studies using the data available to the larger scientific community.

DUO:0000021
version: 2021-02-23

ethics approval required

This data use modifier indicates that the requestor must provide documentation of local IRB/ERB approval.

DUO:0000026
version: 2021-02-23

user specific restriction

This data use modifier indicates that use is limited to use by approved users.

DUO:0000027
version: 2021-02-23

project specific restriction

This data use modifier indicates that use is limited to use within an approved project.

DUO:0000028
version: 2021-02-23

institution specific restriction

This data use modifier indicates that use is limited to use within an approved institution.

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
EGAS00001005437 Other

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 Quality Report
Located in
EGAF00005406000 bam 552.5 MB Report
EGAF00005406001 bam 802.8 MB Report
EGAF00005406002 bam 645.3 MB Report
EGAF00005406003 bam 1.1 GB Report
EGAF00005406004 bam 336.4 MB Report
EGAF00005406005 bam 1.8 GB Report
EGAF00005406006 bam 914.2 MB Report
EGAF00005406007 bam 750.5 MB Report
EGAF00005406008 bam 1.1 GB Report
EGAF00005406009 bam 385.0 MB Report
EGAF00005406010 bam 1.1 GB Report
EGAF00005406011 bam 527.1 MB Report
EGAF00005406012 bam 621.7 MB Report
EGAF00005406013 bam 982.6 MB Report
EGAF00005406014 bam 875.0 MB Report
EGAF00005406015 bam 1.1 GB Report
EGAF00005406016 bam 620.4 MB Report
EGAF00005406017 bam 632.3 MB Report
EGAF00005406018 bam 632.2 MB Report
EGAF00005406019 bam 1.5 GB Report
EGAF00005406020 bam 817.4 MB Report
EGAF00005406021 bam 539.3 MB Report
EGAF00005406022 bam 774.0 MB Report
EGAF00005406023 bam 894.5 MB Report
EGAF00005406024 bam 946.0 MB Report
EGAF00005406025 bam 994.5 MB Report
EGAF00005406026 bam 483.1 MB Report
EGAF00005406027 bam 735.9 MB Report
EGAF00005406028 bam 854.0 MB Report
EGAF00005406029 bam 581.1 MB Report
EGAF00005406030 bam 662.3 MB Report
EGAF00005406031 bam 647.1 MB Report
EGAF00005406032 bam 689.5 MB Report
EGAF00005406033 bam 645.7 MB Report
EGAF00005406034 bam 609.7 MB Report
EGAF00005406035 bam 640.6 MB Report
EGAF00005406036 bam 494.0 MB Report
EGAF00005406037 bam 958.8 MB Report
EGAF00005406038 bam 702.4 MB Report
EGAF00005406039 bam 884.3 MB Report
EGAF00005406040 bam 789.0 MB Report
EGAF00005406041 bam 897.7 MB Report
EGAF00005406042 bam 812.2 MB Report
EGAF00005406043 bam 774.7 MB Report
EGAF00005406044 bam 557.8 MB Report
EGAF00005406045 bam 660.4 MB Report
EGAF00005406046 bam 647.5 MB Report
EGAF00005406047 bam 694.9 MB Report
EGAF00005406048 bam 811.0 MB Report
EGAF00005406049 bam 744.5 MB Report
EGAF00005406050 bam 773.3 MB Report
EGAF00005406051 bam 678.2 MB Report
EGAF00005406052 bam 854.4 MB Report
EGAF00005406053 bam 1.5 GB Report
EGAF00005406054 bam 389.3 MB Report
EGAF00005406055 bam 783.6 MB Report
EGAF00005406056 bam 472.6 MB Report
EGAF00005406057 bam 862.1 MB Report
EGAF00005406058 bam 491.5 MB Report
EGAF00005406059 bam 904.4 MB Report
EGAF00005406060 bam 946.4 MB Report
EGAF00005406061 bam 1.0 GB Report
EGAF00005406062 bam 930.4 MB Report
EGAF00005406063 bam 696.3 MB Report
EGAF00005406064 bam 622.0 MB Report
EGAF00005406065 bam 752.6 MB Report
EGAF00005406066 bam 753.8 MB Report
EGAF00005406067 bam 701.5 MB Report
EGAF00005406068 bam 625.5 MB Report
EGAF00005406069 bam 472.8 MB Report
EGAF00005406070 bam 698.8 MB Report
EGAF00005406071 bam 849.1 MB Report
EGAF00005406072 bam 855.5 MB Report
EGAF00005406073 bam 1.2 GB Report
EGAF00005406074 bam 835.8 MB Report
EGAF00005406075 bam 695.6 MB Report
EGAF00005406076 bam 618.1 MB Report
EGAF00005406077 bam 655.3 MB Report
EGAF00005406078 bam 732.2 MB Report
EGAF00005406079 bam 768.1 MB Report
EGAF00005406080 bam 935.7 MB Report
EGAF00005406081 bam 695.0 MB Report
EGAF00005406082 bam 898.1 MB Report
EGAF00005406083 bam 492.9 MB Report
EGAF00005406084 bam 643.7 MB Report
EGAF00005406085 bam 710.0 MB Report
EGAF00005406086 bam 713.5 MB Report
EGAF00005406087 bam 779.9 MB Report
EGAF00005406088 bam 460.8 MB Report
EGAF00005406089 bam 974.5 MB Report
EGAF00005406090 bam 1.1 GB Report
EGAF00005406091 bam 660.6 MB Report
EGAF00005406092 bam 783.4 MB Report
EGAF00005406093 bam 648.0 MB Report
EGAF00005406094 bam 796.6 MB Report
EGAF00005406095 bam 618.6 MB Report
EGAF00005406096 bam 613.8 MB Report
EGAF00005406097 bam 752.0 MB Report
EGAF00005406098 bam 910.4 MB Report
EGAF00005406099 bam 505.1 MB Report
EGAF00005406100 bam 776.0 MB Report
EGAF00005406101 bam 994.6 MB Report
EGAF00005406102 bam 689.6 MB Report
EGAF00005406103 bam 965.1 MB Report
EGAF00005406104 bam 582.3 MB Report
EGAF00005406105 bam 743.6 MB Report
EGAF00005406106 bam 1.1 GB Report
EGAF00005406107 bam 586.9 MB Report
EGAF00005406108 bam 476.2 MB Report
EGAF00005406109 bam 639.4 MB Report
EGAF00005406110 bam 376.4 MB Report
EGAF00005406111 bam 752.9 MB Report
EGAF00005406112 bam 813.0 MB Report
EGAF00005406113 bam 811.6 MB Report
EGAF00005406114 bam 612.2 MB Report
EGAF00005406115 bam 566.5 MB Report
EGAF00005406116 bam 579.8 MB Report
EGAF00005406117 bam 554.4 MB Report
EGAF00005406118 bam 579.4 MB Report
EGAF00005406119 bam 629.6 MB Report
EGAF00005406120 bam 778.7 MB Report
EGAF00005406121 bam 863.7 MB Report
EGAF00005406122 bam 962.4 MB Report
EGAF00005406123 bam 1.0 GB Report
EGAF00005406124 bam 951.0 MB Report
EGAF00005406125 bam 921.1 MB Report
EGAF00005406126 bam 534.1 MB Report
EGAF00005406127 bam 659.1 MB Report
EGAF00005406128 bam 732.5 MB Report
EGAF00005406129 bam 738.9 MB Report
EGAF00005406130 bam 651.1 MB Report
EGAF00005406131 bam 590.3 MB Report
EGAF00005406132 bam 765.6 MB Report
EGAF00005406133 bam 838.1 MB Report
EGAF00005406134 bam 427.2 MB Report
EGAF00005406135 bam 860.0 MB Report
EGAF00005406136 bam 375.1 MB Report
EGAF00005406137 bam 784.7 MB Report
EGAF00005406138 bam 847.0 MB Report
EGAF00005406139 bam 728.9 MB Report
EGAF00005406140 bam 1.0 GB Report
EGAF00005406141 bam 707.2 MB Report
EGAF00005406142 bam 560.8 MB Report
EGAF00005406143 bam 655.4 MB Report
EGAF00005406144 bam 737.5 MB Report
EGAF00005406145 bam 678.1 MB Report
EGAF00005406146 bam 606.1 MB Report
EGAF00005406147 bam 765.8 MB Report
EGAF00005406148 bam 701.8 MB Report
EGAF00005406149 bam 1.0 GB Report
EGAF00005406150 bam 539.2 MB Report
EGAF00005406151 bam 839.8 MB Report
EGAF00005406152 bam 716.7 MB Report
EGAF00005406153 bam 422.2 MB Report
EGAF00005406154 bam 599.0 MB Report
EGAF00005406155 bam 687.7 MB Report
EGAF00005406156 bam 576.7 MB Report
EGAF00005406157 bam 652.2 MB Report
EGAF00005406158 bam 144.0 MB Report
EGAF00005406159 bam 614.2 MB Report
EGAF00005406160 bam 946.6 MB Report
EGAF00005406161 bam 786.1 MB Report
EGAF00005406162 bam 335.7 MB Report
EGAF00005406163 bam 795.4 MB Report
EGAF00005406164 bam 569.3 MB Report
EGAF00005406165 bam 926.0 MB Report
EGAF00005406166 bam 977.3 MB Report
EGAF00005406167 bam 735.9 MB Report
EGAF00005406168 bam 739.1 MB Report
EGAF00005406169 bam 782.7 MB Report
EGAF00005406170 bam 478.9 MB Report
EGAF00005406171 bam 943.2 MB Report
EGAF00005406172 bam 657.0 MB Report
EGAF00005406173 bam 921.2 MB Report
EGAF00005406174 bam 1.0 GB Report
EGAF00005406175 bam 595.3 MB Report
EGAF00005406176 bam 592.0 MB Report
EGAF00005406177 bam 1.0 GB Report
EGAF00005406178 bam 667.3 MB Report
EGAF00005406179 bam 963.3 MB Report
EGAF00005406180 bam 728.7 MB Report
EGAF00005406181 bam 756.2 MB Report
EGAF00005406182 bam 652.9 MB Report
EGAF00005406183 bam 712.3 MB Report
EGAF00005406184 bam 655.3 MB Report
EGAF00005406185 bam 505.8 MB Report
EGAF00005406186 bam 630.5 MB Report
EGAF00005406187 bam 816.6 MB Report
EGAF00005406188 bam 1.0 GB Report
EGAF00005406189 bam 603.5 MB Report
EGAF00005406190 bam 1.2 GB Report
EGAF00005406191 bam 807.1 MB Report
EGAF00005406192 bam 1.1 GB Report
EGAF00005406193 bam 641.1 MB Report
EGAF00005406194 bam 708.4 MB Report
EGAF00005406195 bam 999.2 MB Report
EGAF00005406196 bam 762.9 MB Report
EGAF00005406197 bam 418.0 MB Report
EGAF00005406198 bam 850.8 MB Report
EGAF00005406199 bam 710.1 MB Report
EGAF00005406200 bam 661.6 MB Report
EGAF00005406201 bam 707.1 MB Report
EGAF00005406202 bam 1.0 GB Report
EGAF00005406203 bam 860.9 MB Report
EGAF00005406204 bam 774.8 MB Report
EGAF00005406205 bam 779.5 MB Report
EGAF00005406206 bam 804.6 MB Report
EGAF00005406207 bam 620.6 MB Report
EGAF00005406208 bam 609.2 MB Report
EGAF00005406209 bam 435.0 MB Report
EGAF00005406210 bam 802.6 MB Report
EGAF00005406211 bam 646.7 MB Report
EGAF00005406212 bam 499.5 MB Report
EGAF00005406213 bam 742.3 MB Report
EGAF00005406214 bam 541.9 MB Report
EGAF00005406215 bam 697.0 MB Report
EGAF00005406216 bam 848.2 MB Report
EGAF00005406217 bam 566.6 MB Report
EGAF00005406218 bam 646.3 MB Report
219 Files (162.7 GB)