6176 results for "get fc 26 coins Buyfc26coins.com is FC 26 coins official site..4xt1"

in 53.81 milliseconds.

• A panel of reference haplotypes for imputing complement component 4 (C4) gene structural variation

  Neuropsychiatric and autoimmune disorders have substantial epidemiological correlations (Benros et al., JAMA Psychiatry 2013, PMID: 23760347) and broad, genome-wide patterns of shared genetic risk (Pouget et al., Hum Mol Genet, PMID: 31211845; Tylee et al., Am J Med Genet B Neuropsychiatr Genet 2018, PMID: 30325587). Some cases of psychosis involve autoantibodies against the NMDA receptor, AMPA receptor, or other synaptic proteins (reviewed in Dalmau et al, Lancet Neurol 2011, PMID: 21163445). The related autoimmune conditions lupus and Sjogren's Syndrome also involve the development of autoantibodies. The possibility that neuropsychiatric disorders can have molecular mechanisms in common with autoimmune disorders - for example, that psychosis involves an inflammatory or autoimmune component in some patients, or that immune molecules are re-used in the brain to underlie other important biological activities (Stevens et al., Cell 2007, PMID: 18083105) - could open novel therapeutic possibilities for neuropsychiatric disorders. At a genetic level, the strongest genetic associations of schizophrenia, lupus, and Sjogren's Syndrome to common genetic variation involve associations to genetic markers in the Major Histocompatibility Complex (MHC) locus. Bipolar disorder in some studies also associates with variation in or near the MHC locus, though less strongly than schizophrenia does. Intriguingly, the same specific SNPs appear to associate strongly with schizophrenia, lupus, and Sjogren's; these strongly associating SNPs span a genomic segment that includes the HLA class II genes (which have an important role in antibody production) and the complement component 4 (C4) genes. The specific genes and alleles responsible for these associations need to be completely defined, and the extent to which they represent shared or distinct genetic influences in neuropsychiatric and autoimmune illnesses needs to be clarified. The complement component 4 (C4A and C4B) genes are present in the MHC locus, between the class I and class II HLA genes. C4A and C4B commonly vary in genomic copy number and encode complement proteins with distinct affinities for molecular targets. The complex genetic variation at C4 - arising from many alleles with different numbers of C4A and C4B genes - has been challenging to analyze in large cohorts. We recently developed an approach to this problem based on imputation: people share long haplotypes with the same combinations of SNP and C4 alleles, such that C4A and C4B gene copy numbers can be imputed from SNP data (Sekar et al., Nature 2016, PMID: 26814963). In the current work, to analyze C4 in large cohorts, we developed a way to identify C4 alleles from whole-genome sequence (WGS) data, then analyzed WGS data from 1,234 individuals to create a large multi-ancestry panel of 2,530 reference haplotypes of MHC SNPs and C4 alleles that can then be imputed into still-larger cohorts for which SNP data are available. With this dbGaP submission, we make this reference panel available for other studies. Protocols and software for imputing C4 alleles into genome-wide SNP data, and for performing molecular analyses on the C4 genes (such as direct measurement of copy number from genomic DNA), can be found on the McCarroll Lab web site (http://mccarrolllab.org/resources). We are also working to create additional reference panels for imputation of C4 alleles that will be based on still-larger and more diverse population samples; links to these will also be available on the McCarroll Lab web site as we create and validate them.

  Study phs001992

• Single Cell and Spatial Transcriptomic Profiling of Haemophilus ducreyi Infection

  We investigated the immune response in end-point pustules formed by Haemophilus ducreyi in volunteers using an experimental infection model. Six volunteers were infected in the skin of the upper arm at three sites with 41-85 CFU of H. ducreyi loaded on an allergy testing device; a sham-inoculated (e.g., wound) site was also performed. Five volunteers (4 men and 1 woman; 2 Asians and 3 Whites; aged 27-46 years) formed pustules 6-8 days post infection; 1 volunteer spontaneously resolved all sites. If a volunteer formed pustules, biopsies were performed to collect their pustule and wound sites. Biopsy pairs for all 5 pustule formers were subjected to single cell (sc) RNA-seq. Sequencing libraries were prepared using the 10X Genomics Single-cell 3' RNA-seq kit. Spatial transcriptomics was performed on biopsy pairs from 4 of the 5 pustule formers. Ten micron sections were placed on 10X Genomics Visium slides for fresh-frozen tissue, and libraries were prepared with the 10X Genomics Visium spatial 3' gene expression kit. All samples were sequenced on an Illumina NovaSeq 6000. Count tables were produced with CellRanger and SpaceRanger, respectively, and Seurat was used to analyze the data. We identified 13 major cell types by scRNA-seq; the proportion of some immune cell subsets was increased in pustules compared to wound sites. We also localized the major cell types within the tissue by using the scRNA-seq data to deconvolve the spatial transcriptomic data. The FASTQ files and count tables from CellRanger and SpaceRanger are provided.

  Study phs003754

• Frequent post-treatment monitoring of colorectal cancer using individualized ctDNA validated by multi-regional molecular profiling

  Purpose: Circulating tumor DNA (ctDNA) analysis has been proposed as an approach for prediction of post-treatment patient outcomes. However, whether a single platform will provide optimal information in all patients or alternatively a patient-specific monitoring approach based on assessment of mutations in the primary tumor from that patient remains an urgent question. Experimental Design: We conducted multiregional sequencing of 42 specimens of 14 colorectal tumors (Stage III and more) from 12 patients, including two double cancer cases, to identify the full spectrum of mutational heterogeneity and identify aberrations that could be used to develop personalized ctDNA assays. Results: ?Founder? mutations that occur in all regions of the sample were identified in 12/14 (85.7%) tumors. Subsequent phylogenetic analysis of each tumor showed that 12/14 tumors (85.7%) carried at least one ?truncal? mutation. Most founder and truncal mutations exhibited higher variant allele frequency (VAF) than ?non-founder? and ?branch? mutations. In addition, both founder and truncal mutations were more likely to be detected as ctDNA than non-founder and branch mutations. Synchronized ctDNA dynamics of multiple mutations suggested those mutations from the same clonal origin. For 10/12 patients (83.3%) with nearly 1,000 days of post-operative observation, the validity of frequent personalized ctDNA monitoring was confirmed in terms of early relapse prediction, treatment efficacy, and non-relapse corroboration. Conclusions: Personalized ctDNA monitoring based on aberrations with a high VAF in the primary tumor site should be explored in larger prospective clinical trials to determine the full clinical validity.

  Study JGAS000243

• Women's Environmental Cancer and Radiation Epidemiology (WECARE) Study

  Study population The WECARE Study is an international multicenter population-based case-control study of cases with asynchronous contralateral breast cancer (CBC) and individually matched controls with unilateral breast cancer (UBC). Recruitment and data collection for the WECARE Study were conducted in two phases, herein referred to as WECARE I (2001–2004) and WECARE II (2009–2012). The study design of the first phase (WECARE I) has been described in detail elsewhere [Bernstein JL, et al 2004, PMID: 15084244]; the second phase (WECARE II) employed a nearly identical approach [Langballe R, et al 2016, PMID: 27400983]. Participants in each phase were identified through eight population-based cancer registries, including six in the United States that contribute to the National Cancer Institute's Surveillance, Epidemiology, and End Results (SEER) program: Los Angeles County Cancer Surveillance Program; Cancer Surveillance System of the Fred Hutchinson Cancer Center (Seattle region, WA); State Health Registry of Iowa; Cancer Surveillance Program of Orange County/San Diego-Imperial Organization for Cancer Control (Orange County/San Diego, CA); the Greater Bay Area Cancer Registry (San Francisco Bay Area region and Santa Clara region, CA); and the Sacramento and Sierra Center Registry (Sacramento region, CA). Participants were additionally identified using the Ontario Cancer Registry (Canada) and the Danish Breast Cancer Cooperative Group Registry, supplemented by data from the Danish Cancer Registry. The study protocol was approved by the institutional review or regulatory ethics boards at each study site. Data collection Study participants were interviewed by telephone using a structured questionnaire aimed at evaluating known or suspected breast cancer risk factors, including personal demographics, medical history, menstrual and reproductive history, family history of cancer, use of hormones, smoking, and alcohol intake. Risk factor status was assessed during the period prior to first diagnosis, as well as between first diagnosis and reference date (i.e., the at-risk period for CBC). Detailed data on treatment and tumor characteristics were obtained directly from cancer registry records or by abstracting medical records, including pathology and surgical reports, radiation oncology clinic notes, and systemic adjuvant treatment data. Complete medical treatment history information was collected, and for all women who received radiotherapy, the radiation dose to the contralateral breast was reconstructed using radiotherapy records and radiation measurements. Biospecimens were collected from study participants for genotyping: blood collected from WECARE I women; and saliva collected from WECARE II women.

  Study phs003945

• eMERGE Network Study of the Genetic Determinants of Resistant Hypertension

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of five participating sites (Group Health Seattle, Marshfield Clinic, Mayo Clinic, Northwestern University, and Vanderbilt University) funded by the NHGRI to investigate the use of electronic medical record systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 19,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of resistant hypertension. Treatment resistant hypertension is a common health problem in the clinical setting. A basic definition of resistant hypertension included subjects with uncontrolled blood pressure despite use of three antihypertensive medications or subjects requiring four or more medications to maintain control. Other conditions, such as secondary causes of hypertension, were exclusions. Site and participants include: Vanderbilt University: BioVU, Vanderbilt's DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt's EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations. Marshfield Clinic: The Marshfield Clinic Personalized Medicine Research Project is a population-based biobank in central Wisconsin with more than 20,000 adult subjects who provided written, informed consent to access their medical records and provided a blood sample from which DNA was extracted and plasma and serum stored. In addition to an average of 30 years of medical history data, a questionnaire about environmental exposures, including a detailed food frequency questionnaire, is available to facilitate gene/environment studies. Northwestern University: The NUgene Project is a repository with longitudinal medical information from participating patients at affiliated hospitals and outpatient clinics from the Northwestern University Medical Center. Participants' DNA samples are coupled with data from a self-reported questionnaire and continuously updated data from our Electronic Medical Record (EMR) representing actual clinical care events. Northwestern has a state-of-the art, comprehensive inpatient and outpatient EMR system of over 2 million patients. NUgene has broad access to participant data for all outpatient visits as well as inpatient data via a consolidated data warehouse. NUgene participants consent to distribution and use of their coded DNA samples and data for a broad range of genetic research by third-party investigators. Group Health(GH)/University of Washington (UW): Aging and Dementia eMERGE study biorepository leverages rich population-based longitudinal data from both electronic medical records and in-depth research data to explore genome wide associations. Participants include Seattle-area members of GH (a large integrated health care system in Washington State) consented and enrolled in 1) the UW Alzheimer's Disease Patient Registry (ADPR) and 2) the Adult Changes in Thought (ACT) study. The ADPR (PI: Eric B. Larson; NIH/NIA U01 AG 006781) is a population-based registry of incident dementia cases designed to identify all new Alzheimer's Disease cases within GH from 1987 to 1996. Medical history, physical, laboratory testing, and neuropsychological testing were performed on all consenting potential cases for determination of dementia status by a consensus conference. The study base of the ADPR population was stable with an attrition rate of less than 1%/year. The ACT study (PI: Eric B. Larson; NIH/NIA U01 AG 006781) is an ongoing community-based cohort study of aging and dementia. The original cohort of 2,581 randomly selected dementia-free members age 65 and older was enrolled in 1994-1996 and expanded by 811 in 2000-2002. Continuous enrollment to maintain a cohort of 2,000 dementia free persons began in 2005. Participants receive biennial assessment including cognitive status determination. The ACT sub-sample is stable; for the original cohort, median enrollment in GH was 19 years prior to joining the ACT study, and 85% of the cohort has ≥ 10 years of GH enrollment. DNA for the ADPR participants were obtained through a companion study, Genetic Differences in Cases and Controls (PI: Walter Kukull; NIH/NIA R01 AG007584). DNA obtained through both studies were extracted from blood using Gentra Systems Puregene methods. DNA concentration is determined by UV optical density. All samples are checked for quality by 260/280 ratio. For long-term storage, samples are aliquoted and stored at -70°C. Mayo Clinic: The Mayo biobank is a disease-specific biobank for vascular diseases including peripheral arterial disease (PAD). PAD patients were identified from individuals referred to the non-invasive vascular laboratory for lower extremity arterial evaluation. Since 1997, laboratory findings have been recorded into an electronic database employing an in-house software package for data archiving and retrieval; this data becomes part of the Mayo EMR. Patients referred to the center with suspected PAD undergo a comprehensive non-invasive evaluation including the ankle-brachial index (ABI) - the ratio of blood pressure measured in the upper arms divided by blood pressure measured at the ankles. Controls subjects are identified from patients referred to the Cardiovascular Health Clinic for stress ECG. The prevalence of PAD in patients with normal exercise capacity who do not have inducible ischemia on the stress ECG, was <1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR.

  Study phs000297

• Implementation of the GDPR

  Data Protection 1 About the EGA The European Genome-phenome Archive (EGA) was formally launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. In late 2012, with the signing of a memorandum of understanding (and subsequent formal agreement in 2016) between EMBL-EBI and the Centre for Genomic Regulation (CRG), the EGA formally became a joint project of the two institutes. The two institutes work together to support the EGA services, including supporting submissions, web site, strategic leadership, and data infrastructure developments. 2 EMBL-EBI & GDPR The EGA is co-managed by EMBL-EBI and CRG. EMBL-EBI is an international organisation established by treaty and has certain privileges and immunities (e.g. exemptions from the application of national law) and also may self-regulate its activities (e.g. establish its own institutional legal framework) within the framework of its founding act of 1973. The General Data Protection Regulation (GDPR) is a European Union (EU) regulation that legislates how organisations can share and process personal data of EU citizens. EMBL places great value in maintaining collaboration with researchers who are subject to GDPR. For that reason, it is of utmost importance for EMBL to handle data received from those collaborators in a secure and responsible manner. Mindful of its public mandate and the sensitivity of the data it handles, EMBL has always ensured a high level of data protection in its activities. Since the introduction of GDPR in May 2018, EMBL has established its internal policy on General Data Protection (IP68), exercising its right to self-regulate its operations,., IP 68 establishes a robust personal data protection framework that provides for data protection principles, enforceable data subject rights and oversight and redress mechanisms offering a level of protection comparable with GDPR. 3 CRG & GDPR The Centre for Genomic Regulation (CRG) is an international biomedical research institute of excellence, created in July 2000 and mainly participated by the Catalan Government. It is a non-profit foundation and its mission is to discover and advance knowledge for the benefit of society, public health and economic prosperity. The CRG is a CERCA center. CERCA is the collective organisation for all research centres of excellence in Catalonia. CERCA ensures these centres develop successfully by promoting synergies and strategic cooperation improving their visibility and the impact of their research and promoting the dialogue amongst both public and private stakeholders. As a legal entity based in Spain and operating within the EU, the CRG ensures the compliance with the GDPR and the legal regulations on personal data protection applicable at the national level, as well as any other legislation that may replace, modify or supplement the above-mentioned in terms of personal data protection. 4 EGA & GDPR EGA GDPR Schema 4.1 Genetic and phenotypic data Within GDPR, there are two main actors: data controllers and data processors. Data controllers are persons or entities which determine the purposes and means that the personal data may be processed, e.g. companies, researchers, or universities. For EGA, the data controller is ultimately the data producer and the submitter(s) who submit the data to EGA. The data controller also creates a Data Access Committee (DAC) who will decide on data access permissions at EGA. Data processors are the persons or entities which process the data on behalf of a data controller. With regard to GDPR, EGA is a data processor as it processes data as instructed by the data controller. GDPR applies to any organisation which accesses personal data from an individual within the EU. Under GDPR, personal data is defined as any data that is identifiable, including names and email addresses as well as health-related and genetic data. EGA does not accept personally identifiable data except genetic and phenotypic data, so all other data submitted to EGA, such as names and addresses, must be pseudonymised. GDPR requires that data controllers implement data protection principles, such as data minimisation, to minimise the risk of data leakage, and protect the rights of the data subjects. As a data processor, EGA has a set of security policies that are followed to minimise the risk of unauthorised data access or data loss. In its role as a data processor, EGA requires all submitters to sign a Data Processing Agreement (DPA) when the submission account is first created. This agreement is only required to be signed once per submitter, and will remain valid for future submissions to EGA. 4.2 Other personal data The EGA also collects personal data as part of our interactions with submitters, data access committees, and researchers accessing data distributed by EGA. The below privacy notices explain what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. Privacy Notices for EGA Title Version Last Updated EGA Data Access Committee Account Privacy Notice for EGA Data Access Committee Account 1.0 February 6, 2019 EGA User Account Privacy Notice for EGA User Account 1.0 February 6, 2019 EGA Helpdesk Service Privacy Notice for EGA Helpdesk Service 1.0 February 6, 2019 EGA Website Service Privacy Notice for EGA Website Service 1.0 February 6, 2019 Documentation Title Version Description EGA Security Overview Security Document 1.1 The EGA Security Document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. EGA Data Processing Agreement Data Processing Agreement 1.5 The Data Processing Agreement must be completed and returned as part of the submission process. Please note that this document is non-negotiable. Authorised Submitters Authorised Submitters Formulary 1.0 The Authorised Submitters Form must be completed and returned as part of the submission process. Please list all those that should have access to the submission account in order to submit to the EGA should be detailed here. Dispute Resolution Any controversy or claim arising out of, or relating to, the DPA (including the enforceability or breach thereof, any question regarding its existence, validity or termination) or relating to the EGA Service shall be resolved using the internal dispute resolution mechanisms of EGA including those related to Data Protection. The EGA’s internal dispute resolution mechanism has the following procedure: EGA OPERATIONAL PHASE: Meetings between EGA staff and the Data Controller.LEGAL MANAGEMENT PHASE: Meetings between legal teams of EMBL, CRG and the Data Controller. DIRECTION MANAGEMENT PHASE: Negotiation between the legal representatives of EMBL, the CRG and the Data Controller. If the internal dispute resolution mechanism doesn’t resolve the controversy or claim the next phase is:ARBITRATION PHASE: Resolution by arbitration under the WIPO Expedited Arbitration Rules (“Rules”).

  Documentation about/privacy-notice

• Genomic Analyses of Germline and Somatic Variation in High-Grade Serous Ovarian Cancer

  The goal of this study was to identify and characterize germline and somatic genetic variation in women with high grade serous ovarian cancers treated at a single cancer center and their associations with relapse-free and overall survival. We conducted paired tumor/normal targeted next-generation sequencing of 577 genes in pathways of DNA repair, response to DNA damage, cell-cycle regulation, programmed cell death, MAPK, and P13K/AKT/MTOR signaling in 114 tumors from 71 women. In addition, we investigated single copy number alterations (SCNAs) and loss of heterozygosity in a subset of 61 tumors. We validated our results with data from ovarian tumors in TCGA. Our results were similar to other studies of high-grade serous carcinomas. As an example, we found that approximately one third of the tumors harbored loss of function variants in homologous recombination genes and that >90% had TP53 somatic mutations. Through GISTIC analysis of the OncoScan data on tumor DNA from 61 cases, we identified several regions of high copy number alterations including including NOTCH3 and PIK3R2 that were significantly associated with an increase in cancer recurrence and a reduction in overall survival. We identified few changes in mutation profiles where we had multiple tissues, either from multiple surgeries or from the primary site to metastatic sites within the same surgery. However, we did not investigate copy number alterations in multiple tissues from the same individuals, and so it may be that copy number alterations are more important. Data available through dbGAP will be the BAM files and the phenotypic data on the tumor samples, the age, race, ethnicity of the participants and their outcomes, and the Oncoscan OSCHP files.

  Study phs003198

• A Personalized Neoantigen Vaccine Generates Anti-Tumor Immunity in High-Risk Renal Cell Carcinoma

  Personalized cancer vaccines (PCVs) can generate circulating immune responses against predicted neoantigens. However, whether such responses can target cancer driver mutations, lead to immune recognition of a patient's tumor, and result in clinical activity are largely unknown, particularly in patients with lower mutation burden tumors. We conducted a phase I trial testing a neoantigen-targeting PCV in patients with high-risk, fully resected clear cell renal cell carcinoma (RCC; stage III or IV), with or without ipilimumab administered adjacent to the vaccine. At a median follow-up of 40.2 months from surgery, none of the 9 initial participants experienced a recurrence of RCC. No dose-limiting toxicities were observed. All patients generated T cell immune responses against PCV antigens, including RCC driver mutations in VHL, PBRM1, BAP1, KDM5C, and PIK3CA. Following vaccination, there was a durable expansion of peripheral T cell clones, and T cell reactivity against autologous tumor was detected in 7 of the 9 patients. Our results demonstrate that neoantigen-targeting PCVs in high-risk RCC are highly immunogenic, capable of targeting key driver mutations, and induce anti-tumor immunity. These observations, in conjunction with the absence of recurrence in all 9 vaccinated patients, highlights the promise of PCV as effective adjuvant therapy in RCC. We are submitting WES data from whole blood samples and tumor FFPE samples, and RNA-Seq data from tumor FFPE samples. We are also submitting RNA-Seq data from purified tumor samples. scRNA-seq data will be submitted for skin samples (vaccine site biopsies at Weeks 0, 4, and 13), tumor samples (including resected metastatic tumor samples for two patients), and normal kidney samples. Bulk TCR-seq data will be submitted for blood samples.

  Study phs003710

• Combining a Universal Telomerase Based Cancer Vaccine with Ipilimumab in Patients with Metastatic Melanoma - Five-year Follow up of a Phase I/IIa Trial

  Background Ipilimumab improves survival for patients with metastatic malignant melanoma. Combining a therapeutic cancer vaccine with ipilimumab may increase efficacy by providing enhanced anti-tumor immune responses. UV1 consists of three synthetic long peptides from human telomerase reverse transcriptase (hTERT). These peptides comprise epitopes recognized by T cells from cancer patients experiencing long-term survival following treatment with a first-generation hTERT vaccine, and generate long-lasting immune responses in cancer patients when used as monotherapy. The objective of this trial was to investigate the safety and efficacy of combining UV1 with ipilimumab in metastatic melanoma. Patients and methods In this phase I/IIa, single center trial [NCT02275416], patients with metastatic melanoma received repeated UV1 vaccinations, with GM-CSF as an adjuvant, in combination with ipilimumab. Patients were evaluated for safety, efficacy and immune response. Immune responses against vaccine peptides were monitored in peripheral blood by measuring antigen-specific proliferation and IFN-γ production. Results Twelve patients were recruited. Adverse events were mainly diarrhea, injection site reaction, pruritus, rash, nausea and fatigue. Ten patients showed a Th1 immune response to UV1 peptides, occurring early and after few vaccinations. Three patients obtained a partial response and one patient a complete response. Overall survival was 50% at 5 years. Conclusion Treatment was well tolerated. The rapid expansion of UV1-specific Th1 cells in the majority of patients indicates synergy between UV1 vaccine and CTLA-4 blockade. This may have translated into clinical benefit, encouraging the combination of UV1 vaccination with standard of care treatment regimes containing ipilimumab/CTLA-4 blocking antibodies.

  Study EGAS00001005253

• Cross-site Concordance Evaluation of Tumor DNA and RNA Sequencing Platforms of CIMAC-CIDC Network

  The Cancer Immune Monitoring and Analysis Centers (CIMACs) and the Cancer Immunologic Data Commons (CIDC)  has engaged in efforts to harmonize Whole-exome (WES) and RNA-sequencing (RNA-seq) data from three different experimental platforms (MD Anderson, NCI MoCha lab, and Broad Institute) and are using a series of developed pipelines to process the early trial samples. To evaluate the consistency of tumor WES and RNA-seq profiling platforms across different centers, the CIMACs-CIDC conducted a systematic harmonization study. DNA and RNA were centrally extracted from fresh frozen (FF) and formalin-fixed paraffin-embedded (FFPE) non-small cell lung carcinoma (NSCLC) tumors and distributed to three centers for WES and RNA-seq profiling

  Study phs002295

• Atezolizumab Plus Personalized Neoantigen Vaccination in Patients with Urothelial Cancer: a Phase 1 Trial

  This is a phase 1 single center clinical trial evaluating a multi-peptide personalized neoantigen vaccine, PGV001, in combination with atezolizumab for patients with urothelial cancer. Patients were enrolled in either the adjuvant or metastatic setting. Those in the adjuvant setting included patients considered high risk of recurrence (pathological stage ypT2-T4 or ypN+ for those treated with prior neoadjuvant chemotherapy or pT3-T4 or pN+ for those not treated with prior neoadjuvant chemotherapy). Those in the metastatic setting included patients progressing after prior chemotherapy or those with at least stable disease after chemotherapy treated as “switch maintenance” therapy. The primary endpoint was feasibility (including the number of neoantigens identified per patient, vaccine production time, the proportion of patients consenting to the vaccine development phase for whom a vaccine product was prepared, and the proportion of patients eligible for the treatment phase who completed the priming cycle 1 of PGV001 plus atezolizumab) and safety. Secondary endpoints included the objective response rate, progression-free survival or disease-free survival, overall survival, and immunomodulatory effects of treatment. Urothelial tumor tissue and normal tissue or peripheral blood specimens were utilized for DNA sequencing. HLA typing was performed utilizing genomic DNA isolated from whole blood, and RNA sequencing was performed utilizing tumor tissue specimens. Neoantigen prediction and final selection for incorporation into the vaccine was determined by the OpenVax computational pipeline. 12 patients were initially enrolled into the vaccine development phase and 10 patients initiated the treatment phase. PGV001 was administered with poly-ICLC and tetanus peptide on subsequent days for up to 10 doses, including an initial priming cycle 1. Atezolizumab was administered every 3 weeks for up to 1 year in the adjuvant setting or 2 years in the metastatic setting. The vaccine was feasible and safe, the median vaccine production time was 20.3 weeks, and 100% of patients that initiated the treatment phase completed the priming cycle. The most common treatment-related adverse events were local grade 1 injection site reactions, fever, and fatigue. Three of the 4 patients in the adjuvant setting remained disease-free at median follow-up of 39.5 months. There was a 40% objective response rate among patients with measurable disease in the metastatic setting. The single patient treated as “switch maintenance” therapy remained with no evidence of disease at 39.4 month follow-up. All patients demonstrated on-treatment neoantigen-specific T cell reactivity, as measured by ELISPOT and flow cytometry assays. Overall, PGV001 plus atezolizumab was feasible, safe, and warrants further investigation. Whole exome sequencing from tumor tissue and normal tissue or whole blood specimens and RNA sequencing from tumor tissue specimens will be available through dbGaP.

  Study phs003922

• Genome-Wide Association Study of Patients with Coccidioidomycosis

  BackgroundValley Fever is typically an infection of the lungs caused by the fungi Coccidioides immitis and Coccidioides posadasii. The incidence of Coccidioidomycosis (CM), or infection with Coccidioides, has dramatically increased over the last 20 years. This is particularly true in the Southwest of the United States, where people often breathe fungal spores that arise from the soil. Reasons for increased infection rates are thought to include population growth and construction in these endemic regions, an increase in the number of people whose immune systems are compromised due to infection or treatment with drugs required for organ transplants, climate change, as well as improved testing practices and greater physician awareness. Mild CM most commonly presents itself with flu-like symptoms and rashes, which can last weeks to months. Individuals with compromised immune systems, specifically-- substantial suppression of the immune cells known as T cells, can develop severe pulmonary and disseminated disease. Infection that remains localized to the lungs is referred to as pulmonary disease, but when the infection spreads out of the lungs into other parts of the body it represents a more serious condition referred to as a disseminated disease, or disseminated CM. In nature, Coccidioides spp. exists as mold and lives in dust and soil. When the contaminated soil or dust is disturbed by human activity, animals, or weather, the Coccidiodies spores are released into the air. Airborne spores are taken up by breathing and settle in the lungs. Once in the moist and warm environment of the lung, spores transform into spherules, which divide and become filled with smaller spores, called endospores. When the spherules get large enough, they rupture and release these endospores, which can spread and disseminate to surrounding tissue. The cycle then repeats itself as these endospores develop into new spherules3. Different ethnic groups have been described to vary in their susceptibility to developing disseminated CM after initial infection with Coccidioides. For example, evidence suggests that African-American and Filipino patients suffer the disseminated disease at a greater rate than other ethnicities. The suggestion that race plays a role in the clinical expression of the disease is still a source of debate amongst the scientific community and any genetic mechanisms responsible for these differences have yet to be fully elucidated. If our genetic makeup influences our ability to limit the spread of infection, finding which DNA differences cause these variances could provide clues to how the body successfully fights infection, and provide opportunities to boost the body’s ability to do this. Further, if we are able to identify the specific genetic risk factors that correlate with the development of disseminated infection, physicians could perform genetic screenings to identify high-risk patients and provide them with preemptive antifungal therapy prior to developing disseminated disease.The genome, made up of DNA, contains all of the information needed for humans to develop and grow. Genome-wide association studies (GWAS) allow us to look for inherited differences that are more common between people who share a particular trait, for example, height or susceptibility to certain diseases, compared to those who do not share the trait. Although some traits and diseases are controlled by a single gene, the majority are influenced by contribution from several, or even many, different genes. To find evidence of genes that contribute to specific traits, GWAS typically compares genome information from large numbers of people who have a particular disease (referred to as “cases”) looking for DNA sequences that are common among these samples, and are different from DNA sequences seen in large numbers of people who lack the trait, but are as much like the cases as possible (referred to as “controls”). The DNA sequence data from each group, cases versus controls, are analyzed to see if there are specific genomic differences that tend to be associated with the disease. MethodsTwo separate GWAS approaches were taken to look for genetic differences that could be responsible for the observed differences between the different patient populations we are studying. The first method, known as genotyping, scans for differences at a set of positions across the genome, which includes both the genes that encode our proteins and the larger amount of DNA that does not. The second method, known as exome sequencing, allows us to compare the entire sequence of the portion of the genome that codes for proteins.  For this study, DNA from patients with either pulmonary or disseminated CM were genotyped and exome sequenced to look for DNA differences that are associated with one condition or the other. All patients were at least 18 years old, had no evidence of immunosuppression, and had proven or probable pulmonary coccidioidomycosis according to established diagnostic criteria. Of these patients, a subset demonstrated disseminated disease, i.e., they showed evidence of coccidioidal infection outside of the thorax by biopsy/aspiration, had radiographic imaging, and show positive coccidioidal serology. Our criteria for including patients with the pulmonary disease were that they must not require ongoing antifungal treatment or show evidence of active CM (in skin test positive patients), show no evidence of extrapulmonary dissemination, and have no evidence of ongoing pulmonary infection (pulmonary nodules are accepted) beyond six months from diagnosis.Patient DNA was purified from blood or from sputum samples by the labs of our collaborators, Drs. George Thompson (UC Davis School of Medicine) and John Galgiani (University of Arizona Health Sciences). Genome-wide association (GWAS) analysis was carried out to look for candidate loci associated with pulmonary versus disseminated disease, taking into account the population structure of the samples. Single nucleotide or insertion/deletion variants were identified from whole-exome sequences (WES) using the Picard/BWA/GATK pipeline. ResultsTable 1. Pulmonary versus Disseminated Cases of Coccidiomycosis for GWAS, Sorted by EthnicityEthnicityPulmonary CasesDisseminated CasesAsian85Black/African American1664Caucasian/White4015Filipino03Hispanic/Latino3414Indian21Mexican American1039Pacific Islander01Samoan03Vietnamese10Unknown16917More than one race02Total373134Table 1 shows the number of samples analyzed from patients with pulmonary versus disseminated disease, and patient ethnicity, where known. In all, we worked with 507 samples, including 134 samples from patients with disseminated disease and 373 samples from patients with pulmonary disease. Of these, 505 samples were genotyped using the Multi-Ethnic Global Array from Illumina Inc. In addition, we were able to generate whole-exome sequence from 498 patient samples. No significant associations were detected that differed between samples from patients with pulmonary versus disseminated disease; that is, no particular DNA sequences were found to be significantly enriched in patients with disseminated disease compared to patients with pulmonary disease. The ability to detect genetic association between specific sequences and genetically determined traits is influenced by several factors, including how many patient samples are available to compare, how many different genes contribute to the trait and how strong their contributions are. When the number of genes is small and the contribution of each gene is great, smaller numbers of patient samples are needed to detect an association. When more genes are involved, or the contribution from each gene is more modest, larger numbers of patient samples must be examined. While we were not able to detect any associated within this study, it does not mean that subsequent studies would not find this connection. Our study suggests significantly more samples should be analyzed in further studies.Whole-exome sequences were generated from 498 samples and were aligned to reference sequences to identify positions where the sequences differed from the reference. These data are being analyzed to determine if any variants are associated with pulmonary, versus disseminated, disease. 

  Study phs002170

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? TThe most suitable archive for your data is dependent on the type of data you are wishing to submit and whether the data require public or controlled access. Public access is defined as complete and open access to all submitted data. On the contrary, controlled access, exerted by the EGA, requires formal applications to be made to access the submitted data files and metadata. EGA only accepts human-derived data subject to controlled access. If your submission contains other types of data, please choose the appropriate repository for it (see image below): ENA, EVA, ArrayExpress, BioSD and GWAS catalog.  Should your submission be subjected to controlled access? Data access conditions are normally defined in the original informed consent agreements signed by the participants involved in your study. All data submitted to the EGA is subject to controlled access. These consents prevent the derived data files, potentially identifiable, from being dispersed by open and public access. Controlled access data often refers to human data derived from medical research and consortium projects. If in doubt, consult the informed consent agreements that apply to your study The EGA enables you to hold a submission before publication. What data types can be submitted to the EGA? Data types accepted by the EGA can be split into three categories: Sequences: both in generic and platform-specific formats. Array-based: from raw signal files to processed matrices. Phenotypes: all possible phenotype formats are accepted. All manufacturer-specific raw data formats derived from major next generation sequencing platforms are accepted. Also generic sequence formats: flat reads in a FASTQ file, aligned sequences (BAM or CRAM files) as well as sequence variation files in VCF format. All array-based technologies are accepted, including raw data, intensity and analysis files, without any restriction on data formats accepted. We also accept and distribute phenotype data (associated to the samples) in almost any format: from an image to a README file. How long does a submission take? Submissions to EGA come in a variety of formats and sizes, thus it is difficult for us to exactly predict how long a submission will take. We, therefore, advise all of our submitters to allow as much time as possible to make a submission. Based on previous records, we anticipate that the submission process may take at least one month. The submitter’s familiarity with the procedures, possible technical issues that may arise during submission and the amount of data that is being submitted are the main factors that will affect the length of the submission process. However, each step of a regular submission should be considered when estimating the time it would take: Encryption of the files Upload of the files Metadata submission Archival of the files Release of the study and datasets to EGA webpage For example, the upload of the files depends on the submission size, while metadata submission mainly relies on each submitter’s expertise. Further, some steps (e.g. answering to inquiries) depend on the EGA Helpdesk team, which may take some days to be processed during busy times Is data deposited in the EGA secure? The EGA set-up consists of a secure computing facility for data processing, a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website. Data is also copied in the Barcelona Supercomputing Center (BSC) infrastructure, where all stored and distributed data is encrypted Data is encrypted along the submission process and stored securely, granting its access to authorised users exclusively. During the download process, through our Python Client or Aspera, all requested data is downloaded over secure https connections. All data at the EGA is encrypted, and only accessible (for log-in and download) through secure protocols. For further information please, visit our security overview. What documentation do I need to provide? All submissions require policy’s documentation: 'Data Access Agreement (DAA)', 'Data Processing Agreement (DPA)' and 'Authorized Submitters Formulary'. The data processors (EGA) and the data owners will also sign the DPA. Will all metadata be public? Among the submitted metadata we need to make the distinction between identifiable and unidentifiable metadata: (1) the former may allow the identification of the human the sample derived from (e.g. detailed geographical providence, personal name, family ancestry…); (2) while the latter can be used to interpret the data without compromising the anonymity of the patients. The majority of the metadata submitted to the EGA corresponds to the unidentifiable category (e.g. sequencer's model). This type of metadata is publicly available on the EGA website and other EBI resources/partners’ websites. On the other hand, some parts samples’ metadata are subject to being identifiable, and thus only accessible by authorized data requesters, with the exception of: 5 submitter-defined attributes of the sample: alias, title, subject_id, gender and phenotype. It is the submitter’s responsibility not to submit sensitive metadata in these public fields. 3 anonymised fields that pinpoint the sample record in archivals: sample’s EGA stable ID (EGAN…), BioSample ID (SAMEA…) and submitter’s center name. During Submission Are there any sample specific requirements for EGA? All samples submitted to the EGA must include the attributes of biological sex, subject ID (anonymised individual identifier) and phenotype information. These are critical for data findability and its analysis, and we highly recommend using controlled ontology terms where applicable. For example: defining tumour and non-tumour samples and/or defining disease state. The EGA recommends using the Experimental Factor Ontology Database to find ontologized terms that describe your sample phenotypes. How do I get an accession number to use in my publication? You will receive your study accession number (EGAS…) upon complete your submission, either: Programmatically. As soon as the metadata is submitted and validated your study will be assigned an accession number that will be given in the submission’s response. Manually registering your study and relevant metadata using the online metadata submission tool: the EGA submitter Portal. How are files uploaded to the EGA? Data files are uploaded into private submission drop boxes (i.e. environments to which you are granted access and where you can transfer your files) using INBOX or FTP. These spaces are provided as part of the submission procedure. Before uploading any file, you must encrypt your files, . Only encrypted files shall be uploaded to the drop boxes. Why does data need to to encrypted for my submitted files? It is one of the security steps the EGA has implemented. In case of a security breach, people without the proper encryption key will not be able to read or use the information that could have been leaked. This measure is essential when working with sensitive data, such as controlled access human data. All submitters must use crypt4gh to create EGA compliant files prior to uploading them. This encryption is GPG-based, using EGA’s public key. Why are my files not available if I see them in the INBOX? There exists a time window between the data upload and the availability of such files via the Submitter Portal. For this reason, some metadata (run and analysis objects) cannot be registered until at least 24 hours after the files have been uploaded to your box. Why are MD5 sum values generated for my submitted files? We require pre- and post- encryption MD5 (message-digest) checksum values to be provided for all submitted files. These 128-bit values are computed using the content of each file, creating unique sequences that allow us to ensure that file integrity has been maintained during the transfer process. In other words, if the MD5 checksums we generate and those you generated match, we infer that the content of the transferred files is correct (i.e. files are not corrupted or truncated). MD5 checksums are computed automatically using the crypt4gh tool provided. Your submission will not be accepted and may be significantly delayed if you do not provide MD5 checksum values for all data files in the required format. How can I check if my files are correctly uploaded to the inbox? It is important to check the status pf your file so you know whether your files are in the inbox, being processed, or if there is any issue with one of them. In order to check this, you should: Look for the file locally. Drag and drop it to the file table. Then bars will appear on the table, which means that we are processing it. Green: The files checksum are correct and your file will move to “ingested files”. No further actions are needed from your end.. Red: The files checksum does not match and your file needs to be re-uploaded. Please re-upload relevant files to your inbox using the same path. After Submission How do I use my accession number in my publication? We suggest the use of the below template, using your study accession ID (EGAS…) : Data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found at https://ega-archive.org and "The European Genome-phenome Archive of human data consented for biomedical research" Your study ID will be the one that groups your whole submission, and thus its usage is recommended as such. Nevertheless, all metadata submitted to EGA hold a unique and persistent identifier (starting with EGA…) that can be used to identify specific records. For example, you could reference a specific dataset (EGAD…) or sample (EGAN…) in your publications (see full list of identifiers). How do I make my data searchable? Once you have finalized your submission, you can schedule the data release. Please take into account that the release process needs time for the files to be archived in our system, and for the Helpdesk team to validate your submission. Can I withdraw (meta)data from the EGA? We have methods in place for the secure removal of deposited (meta)data. Contact EGA-helpdesk for further details. EGA complies with FAIRness of (meta)data, and thus, even when the data is removed we keep an entry for their identifiers in our system. In other words, we execute a soft delete on canceled objects (e.g. a study): metadata is still stored in our systems, but it loses all links, cannot be queried and data files cannot be retrieved anymore. The reason behind this behaviour is so that queries using withdrawn data properly respond back (see example of a canceled study). What happens to the data once it has been submitted to the EGA? When the data is submitted, the submitter can choose either keep their data private or schedule the release of their data.

  Documentation submission/metadata/submission/FAQ

• NHLBI TOPMed: SubPopulations and InteRmediate Outcome Measures In COPD Study (SPIROMICS)

  Subpopulations and Intermediate Outcome Measures in COPD Study Description Subpopulations and intermediate outcome measures in COPD study (SPIROMICS) supports the prospective collection and analysis of phenotypic, biomarker, genetic, genomic, and clinical data from subjects with COPD for the purpose of identifying subpopulations and intermediate outcome measures. It is funded by the National Heart, Lung, and Blood Institute and is coordinated by the University of North Carolina at Chapel Hill. Molecular fingerprinting and extensive subject phenotyping will be performed to identify disease subpopulations and to identify and validate surrogate markers of disease severity, which will be useful as intermediate outcome measures for future clinical trials. Secondary aims are to clarify the natural history of COPD, to develop bioinformatic resources that will enable the utilization and sharing of data in studies of COPD and related diseases, and to create a collection of clinical, biomarker, radiographic, and genetic data that can be used by external investigators for other studies of COPD. Participating Institutions: Research participants for SPIROMICS will be enrolled, phenotyped, and followed at twelve SPIROMICS Clinical Centers: Columbia University, Temple University, Johns Hopkins University, Wake Forest University, University of Michigan, University of Illinois at Chicago, University of Iowa, University of Utah, National Jewish Health, University of California at San Francisco, and University of California at Los Angeles. The University of North Carolina at Chapel Hill serves as the Genomics and Informatics Center. The Radiology Reading Center is based at the University of Iowa. The PFT Reading Center is based at the University of California at Los Angeles. Study Design: SPIROMICS is a prospective cohort study that enrolled approximately 2,981 participants at twelve clinical centers over five years. Participants are distributed across four enrollment strata (i.e., Never-smokers, Smokers without COPD, Mild/Moderate COPD, and Severe COPD). Study Visits: Participants have up to four in-person visits (Baseline and Annual Clinic Visits at years 1, 2, 3 after Baseline). Study questionnaires and spirometry are completed at all main study visits. Blood and urine samples are collected at visits 1, 2, and 4. Sputum samples are collected at Visit 1. The CT scans are completed and Baseline and Visit 2. Participants also receive quarterly follow-up calls to assess health status and determine if an exacerbation has occurred. Substudies Bronchoscopy and Immunophenotyping Substudy The Bronchoscopy Substudy will enroll 50 subjects per site, for a total of 300 participants. These participants will be recruited across all four study strata. This substudy includes two study visits. During the first visit, sputum samples are collected for Immunophenotyping analysis at the Immunophenotyping Core Lab based at the University of Michigan. Participants then return for a second visit during which samples are collected via bronchoscopy, including bronchoalveolar lavage, epithelial brushings and bronchial biopsies. Immunophenotyping analysis is also conducted on BAL and blood collected during the bronchoscopy study visit. Repeatability Substudy The entire baseline clinic visit was repeated on 98 volunteers to determine reliability of measurement procedures. All baseline study-related procedures and questionnaires, including the CT scan, were re-administered and new samples of blood, urine, saliva, and sputum were collected. Field center staff processed these biospecimen samples according to the same protocol. Exacerbation Substudy The Exacerbation Substudy is a prospective, longitudinal observational study of up to 400 participants, which will allow the assessment of participant-driven health care utilization (HCU) events and symptom-defined exacerbation events over time. HCU-driven events are defined by change in medical treatment in response to a perceived COPD Exacerbation. Symptom-based events will be defined by using EXACT-PRO (EXacerbations of Chronic Pulmonary Disease Tool - Patient Reported Outcome), a daily symptom diary developed to measure the frequency, severity, and duration of exacerbations in clinical trials. All participants are provided with a PDA on which to complete the diary. Participants reporting a possible COPD exacerbation will be brought into the study clinic for a study visit to collect biological specimens and questionnaire data. The overall objectives of the Exacerbation Substudy are to: Obtain clinical data and specimens on SPIROMICS participants before and during an acute COPD exacerbation defined by Health care utilization triggered by the subject, or Symptomatic change (triggered by an EXACT defined threshold) Describe symptomatic changes occurring around HCU and symptom-defined (EXACT) events and their relationship to clinical and specimen data, Characterize the non-exacerbation "stable" state in COPD using the EXACT, including: Symptom variability (EXACT), Clinical data and specimen parameters during a stable state (baseline), The relationship between clinical and specimen data and symptom severity and variability. Explore the characteristics of stable patients, defined as those who do not experience HCU or symptom-defined (EXACT) events during the sub-study period, using baseline clinical data and specimens, and compare these characteristics with patients who experience HCU and/or symptom-defined events. Examine the relationship between HCU and symptom-defined exacerbation frequency during the first one-year period of follow-up for exacerbations and health outcomes, including 12-month change in lung function and COPD health status, and longer-term morbidity and mortality, with the latter derived from long-term data from the larger SPIROMICS study.

  Study phs001927

• Human Dorsal Root Ganglion RNA Landscape Profiling for Neuropathic and Chronic Pain

  Bulk and spatial RNA sequencing were performed on human Dorsal Root Ganglia (DRGs), peripheral sensory nerves and nodose ganglia and relative gene abundances were calculated. Various analyses were performed: Human DRG gene expression profiles were contrasted with a panel of gene expression profiles of relevant tissues in human and mouse (integrating, among other sources, datasets from ENCODE and GTex) in order to identify. DRG-enriched gene expression, co-expression modules of DRG-expressed genes, and key transcriptional regulators in humans. Contrasting the human and mouse DRG transcriptomes to identify DRG-enriched gene expression patterns that were conserved between human and mouse, identifying putative cell types of expression of these genes, and potential known drugs that might target the corresponding gene products. Characterization of non-coding RNA profile of human and mouse DRGs. Characterization of DRG-enriched alternative splicing and alternative transcription start site usage based transcript variants in humans and mouse, and the overlap between these two species. Contrasting of human DRG and GTex human tibial nerve samples to identify putative axonally transported mRNAs in sensory neurons. Human DRG and peripheral nerves transcriptomes from donors suffering from neuropathic and/or chronic pain were contrasted with controls to identify. Differentially expressed genes, pathways and regulators path play a potential role in neuronal plasticity, electrophysiological activity, immune signaling and response. Predictive models (Random Forests) were built to jointly predict the sex and pain state of samples based on information contained solely in autosomal gene expression profile. Gene co-expression modules were identified and gene set enrichment analysis performed.to identify sample - pathway associations, and to broadly characterize plasticity in human DRG cell types. Spatial transcriptomics was performed on human DRGs and nodose ganglia to obtain near single-neuron resolution. We identified distinct clusters of human DRG sensory neurons. We characterized the expression of different gene families (e.g., GPCRs, sodium channels, potassium channels, etc.). We investigated differences between male and female neurons.

  Study phs001158

• eMERGE Network Phase III Clinical Sequencing: eMERGEseq Panel

  The Electronic Medical Records and Genomics (eMERGE) Network is a National Institutes of Health (NIH)-organized and funded consortium of U.S. medical research institutions. The primary goal of the eMERGE Network is to develop, disseminate, and apply approaches to research that combine biorepositories with electronic medical record (EMR) systems for genomic discovery and genomic medicine implementation research. eMERGE was announced in September 2007 and began its third phase in September 2015. eMERGE III consists of nine study sites, two central sequencing and genotyping facilities, and a coordinating center. eMERGE Phase III aims to: 1) sequence and assess the phenotypic implication of rare variants in a custom designed eMERGEseq panel consisting of 109 genes (including 56 ACMG actionable finding list genes and the top 6 genes from each site relevant to their specific aims), as well as approximately 1400 SNPs; 2) assess the phenotypic implications of these variants by developing, validating and implementing new phenotype algorithms, 3) integrate genetic variants into EMRs to inform clinical care; and 4) create community resources. Included in this study are: ~24,000 eMERGE participants from 10 eMERGE III study sites. Corresponding demographics, body mass index measurements. Top PheWAS codes generated from a collated list of ICD codes from all study sites. Study sites and participants include: Cincinnati Children&#39;s Hospital Medical Center (CCHMC): Cincinnati Children&#39;s Hospital Medical Center (CCHMC) is a not-for-profit hospital and research center pioneering breakthrough treatments, providing outstanding family-centered patient care and training healthcare professionals for the future, and dedicated to improving health and welfare of children and to the shared purpose of discovery and practical application of new genomic information to the ordinary care of children. We bring a comprehensive electronic health record (EPIC), a deidentified i2b2 data warehouse of 680K patient records, a biobank with &#62;261,000 consents that allow return of results to &#62;84,000 patients and guardians who have provided DNA samples, and hundreds of faculty and senior staff who make genomics or informatics an active focus of their research. CCHMC will help the eMERGE III Steering Committee identify genes for the eMERGE III targeted sequencing panel, provide 3,000 DNA samples from CCHMC patients to be sequenced, review targeted gene panels from clinical care at CCHMC for somatic mosaicism and reinterpretation, and further develop and disseminate a software workflow suite for sequence analysis. We will also extend our work generating phenotype algorithms using heuristic and machine learning methods to many new childhood diseases. We will develop tools to evaluate adolescent return of results preferences, examine the ethical and legal obligations and potential to reanalyze results, and develop clinical decision support for phenotyping, test ordering, and returning sequencing results. Children&#39;s Hospital of Philadelphia (CHOP): The Center for Applied Genomics (CAG) is a specialized Center of Emphasis at the Children&#39;s Hospital of Philadelphia (CHOP), and one of the world&#39;s largest genetics research programs, with to state-of-the-art high-throughput sequencing and genotyping technology. Our primary goal is to translate basic research findings to medical innovations. We aim to develop new and better ways to diagnose and treat children affected by rare and complex medical disorders, including asthma, autism, epilepsy, pediatric cancer, learning disabilities, and a range of rare diseases. Ultimately, our objective is to generate new diagnostic tests and to guide physicians to the most appropriate therapies. Participants were recruited from the CAG biorepository (n&#62;450,000), specifically from &#62;100,000 CHOP pediatric patients and family members, which is enriched for rare-diseases (n&#62;12,000). Center for Applied Genomics, The Children&#39;s Hospital of Philadelphia We gratefully thank all the children and their families who enrolled in this study, and all individuals who donated blood samples for research purposes. Genotyping for this project was performed at the Center for Applied Genomics and supported by an Institutional Development Award from The Children&#39;s Hospital of Philadelphia. Sequencing was supported by the National Institutes of Health through an award from the National Human Genome Research Institute&#39;s Electronic Medical Records and Genomics (eMERGE) program (U01HG008684). Columbia University: The goal of the Columbia eMERGE III project is to develop methods for integrating genomic data in EHRs and to study the impact of such genomic informatics interventions on the health of a diverse, underserved urban adult English- and Spanish-speaking patient population in Northern Manhattan served by Columbia University Medical Center/New York-Presbyterian Hospital system. The study group is 2500 patients recruited from diverse clinics and community outreach centers of self-reported White (~61%), Asian (~11%), African-American (~11%), American Indian/Alaska Native (&#60;1%) racial and Hispanic (~33%) ethnic backgrounds. There are two subgroups in the study cohort - a retrospective group (N=1052) that includes patients from oncology and nephrology clinics, and a prospective one (N=1448) that includes healthy individuals as well as participants with diverse medical conditions. Confirmed pathogenic variants in 70 selected genes will be returned to participants and their healthcare providers through the EHR integration. Participants are able to choose the results they receive and will have the freedom to meet with a genetic counselor and a geneticist to review results. The impact of genetic testing on clinical care is determined by periodic monitoring of EHRs. Geisinger: Samples and phenotype data in this study were provided by the Geisinger MyCode&#174; Community Health Initiative. Participants are recruited across the Geisinger System via online consents or in-person consents at a hospital or clinic visit. Enrollment is ongoing with over 100,000 individuals currently consented. Partners Healthcare (Harvard University): The Partners HealthCare Biobank is a large research program designed to help researchers understand how people&#39;s health is affected by their genes, lifestyle, and environment. This large research data and sample repository provides access to high-quality, consented blood samples to help foster research, advance our understanding of the causes of common diseases, and advance the practice of medicine. For the Partners research community (Massachusetts General Hospital and Brigham and Women&#39;s Hospital), the Biobank provides: Banked samples (plasma, serum, and DNA) collected from consented patients Blood samples that were discarded after clinical testing in the Crimson Cores maintained in the Brigham and Women&#39;s Hospital and Massachusetts General Hospital Pathology Departments Sample handling and preparation services Link to the biobank data to the Partners Research Patient Data Registry (RPDR) a research instance of our electronic clinical chart Data access through our research portal. To date, over 70,000 Partners patients have given their consent to enroll, give a blood sample, receive research results and agreed to be re-contacted for additional research studies. The Biobank has enabled Partners investigators to compete for nationally recognized grants in personalized medicine such as a clinical electronic Medical Records and Genomics network (eMERGE) site and the national All of US program. The Biobank currently supports over 120 Partners investigators and over 130 million dollars in NIH research. Kaiser Permanente Washington/ (KPWA) / University of Washington (UW): KPWA participants were enrolled in the eMERGE Network through the Northwest Institute of Genetic Medicine (NWIGM) biorepository, and provided the appropriate consent to receive clinically relevant genetic results (N=2,500.) NWIGM is based at the University of Washington and co-managed by the University of Washington and KPWA. The purpose of the NWIGM biorepository is to build infrastructure and resources to carry out a broad range of future genetic research. KPWA members enrolled in the biorepository are asked to provide informed consent to providing a DNA sample for storage in the NWIGM biorepository. The consent is purposefully broad to serve the dual purpose of reducing the burden on researchers who wish to use this biorepository and the IRB committees who will be responsible for reviewing these requests in the future. Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in KPWA&#39;s integrated group practice, and had completed an online Health Risk Appraisal. The selection algorithm was based on several data sources from the EHR at KPWA. 1) Demographics - participants with self-reported race as Asian ancestry were prioritized and selected to enrich for non-European ancestry. The KPWA eMERGE cohort includes N=1,245 members of Asian ancestry. 2) Participants were also selected for a history of colorectal cancer (N=1,255), in order to allow us to enrich germline pathogenic variants. Mayo Clinic: The Return of Actionable Variants Empirical (RAVE) Study was approved by the Mayo Clinic IRB. We recruited 2537 participants from Mayo Clinic biobanks in Rochester, MN, who had hypercholesterolemia or colon polyps, thereby enriching for Familial hypercholesterolemia (FH) and monogenic causes of colorectal cancer (CRC). Additional eligibility criteria were: 1) residents of Southeast MN who were alive and aged 18-70 years; 2) LDL-C level &#62;155 or &#62;120 mg/dl while on lipid-lowering therapy; 3) no known cause of secondary hyperlipidemia; and 4) no cognitive impairment or dementia that would compromise their ability to give written informed consent. Based on these criteria, we identified 5270 eligible patients and obtained informed consent from 3030 participants. Recruitment was conducted in waves and utilized mailed recruitment packets consisting of a study brochure, a written informed consent form, a baseline psychosocial questionnaire, and a return postage-paid envelope. DNA of 2537 participants was sent for CLIA-certified targeted sequencing of 109 genes including genes associated with FH and CRC. Targeted sequencing and genotyping was performed in a Central Laboratory Improvement Amendment (CLIA)-certified laboratory. Northwestern University: Samples and data used in this study were obtained from patients from Northwestern Medicine, an integrated healthcare system, formed through a partnership of Northwestern Memorial HealthCare and Northwestern University Feinberg School of Medicine. Participants include a retrospective cohort from the Northwestern Pharmacogenomics Study, funded through the eMERGE II project, NHGRI (3U01HG006388-02S1) and a prospective cohort from the Genetic Testing and Your Health Study, funded through the eMERGE III project, NHGRI (U01HG008673). Patients were eligible to participate if they were18 years or older and see a physician at Northwestern Medicine. Patients consented to genetic testing and to allow their results to be placed in their electronic medical record. Vanderbilt University Medical Center: Vanderbilt University Medical Center (VUMC) participants were enrolled in the eMERGE Network through the Vanderbilt Genome-Electronic Records (VGER) project. Patients were provided the appropriate consent to receive clinically relevant genetic results (N=2,700). Participants were eligible if aged 21 or over, had a healthcare provider at VUMC, and visited the provider at least 3 times in the past 3 years. Meharry Medical College: Inclusion of ethnic groups in genomic research is critical to identify possible reasons for health disparities. African-Americans are being enrolled in various outpatient clinics of Nashville General Hospital at Meharry, an inner city hospital primary serving a poorer patient group. A total of 500 African Americans with four cancer types demonstrating health disparities in this population - prostate, colon, breast, lung are identified and approached by clinical research coordinators. The purpose of the study is to determine if any genetic information can be identified from these patients who have or are at high risk of one of these disparate cancers. All participants provide written informed consent and HIPAA authorization to provide blood samples for broad research use and permission to access data in their hospital electronic medical record for research now and in the future. An extensive demographic profile is obtained and entered into a REDCap database. Blood samples are obtained for a panel of alleles from extracted DNA at Baylor. In addition, de-identified coded samples are processed and stored in a central biorepository for further DNA, RNA and proteomic analyses. The survey and phlebotomy are performed at the time of the initial contact and agreement to participate. Nearly all patients approached willingly agree to participate for potential benefit to themselves, family members, or humankind. Little concern is voiced of providing samples for genetic analysis. Study investigators will share results with the participants and providers if testing does not indicate high risk. Results indicating increased risk or actionable alleles for the patient and/or family will be returned by a genetic counselor. Monitoring of the patients&#39; health in this cohort will continue to be followed in the EMR to identify any future associations that might explain health disparities in African Americans. Proposals will be reviewed from investigators to study the genetic or proteomic samples as well as the clinical and demographic information in the repository. Please note that this version of the dataset has a handful of mismatches between genotyped and provided sex. Data with the following IDs should be removed prior to analysis: 420252874213744142412243424569384245694642672223

  Study phs001616

• How to use EGA Webin?

  EGA Webin EGA Webin serves as a platform for registering metadata for array based submissions, large scale sequence submission as well as for legacy EGA submission accounts (ega-box-XXXX). For large scale submitters of sequence data you have also the option to submit metadata via XMLS programmatic submission, while new submitters are advised to utilise the Submitter Portal for their submissions. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. WEBIN actions: Register metadata for a sequence submission Register study, samples, experiments, runs, DAC, policy and dataset/s after file upload. Register components for your array-based metadata submission Register study, samples, DAC or policy before uploading files. Edit existing submission metadata Change or update previously submitted metadata. Register metadata for a sequence submission Ensure that all sequence files have been encrypted before uploading them to your submission account using the EgaCryptor. Go to the EGA Webin and log in using your submission account name (ega-box-XXX) and password. Register components of your metadata submission Study Samples Data Access Committee (DAC) Data access policy Dataset For array-base submissions: Study, Samples, Data Access Committee (DAC) and Data access policy may all be registered BEFORE file upload and dataset registration through the array-base template. Register your Study Go to the “Studies (Projects)” box Click on “Register Study” and fill in the information related to your study. Click on “Submit”, this will save the information and generate an EGA study ID. To use the study accession number in a publication, the study has to be previously released on the EGA website, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX.Further information about EGA can be found on https://ega-archive.org and “The European Genome-phenome Archive in 202 "(10.1093/nar/gkab1059)" Register your Samples Go to the “Samples” box Click on “Register Samples” Select “Download spreadsheet to register samples” and customise your template, there is a default EGA template (EGA default checklist) but more attributes can be added if required. For the EGA default checklist, there are mandatory,recommended and optional attributes. As well custom fields which can be added if required. Mandatory attributes Field Name Description tax_id Taxonomy ID of the organism as in the NCBI Taxonomy database. Entries in the NCBI Taxonomy database have integer taxon IDs. See our tips for sample taxonomy here scientific_name Scientific name of the organism as in the NCBI Taxonomy database. Scientific names typically follow the binomial nomenclature. For example, the scientific name for humans is Homo sapiens. sample_alias Unique name of the sample. If not selected system will auto generate an unique alias sample_title Title of the sample sample_description Description of the sample phenotype *** Where possible, please use the Experimental Factor Ontology (EFO) to describe your phenotypes. Recommended attributes Field Name Description subject_id Identifier for the subject where the sample has been derived from gender * Sex Optional attributes Field Name Description sex sex of the organism from which the sample was obtained disease_site Affected organ sample type Affected organ donor_id ** Identifier of the donor where the sample has been derived from *Gender should be described as 'male', 'female' or 'unknown'. If 'unknown' due to a known sex chromosome aneuploidy, please create a user defined attribute called 'Sex chromosome karyotype' and add the appropriate value, for example, 'XXY'. **Donor id (Subject id) should be a de-identified subject handle. If unknown, please add 'unknown' to the field. ***Phenotypes should, where possible, be an Experimental Factor Ontology accession. If a term cannot be found to describe your phenotype please use free text. All sample phenotypes considered important for further analysis of the data should be provided (for example, tumour type), additional phenotype attributes can be created by defining your own attributes; use the notion 'phenotype2', 'phenotype3', etc. After you have customised the fields for the sample submission, download the template and fill in the information. Example of the sample template: Finally upload the sample template to get the EGA accession IDs for the samples. Register your Data Access Committee (DAC) Further information on the role of your DAC Go to the “Data Access” box Click on “Register Dacs” Input the information about the DAC and register at least one main DAC contact. Register your Data Access Policy Your Data Access Policy provides the terms and conditions of data use, this is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAC). Go to the “Data Access” box Click on “Register Policies” Select the DAC to which this policy will be linked to and fill in the policy information. Submitting your Runs and Analyses This section is only for sequence data submission, for array-based submission it can be skipped. Please refer to our Submitting array based metadata Runs Registration Go to the “Raw Reads (Experiments and Runs)” box Click on “Submit Reads” Select “Download spreadsheet template for Read submission” Select the template corresponding to your submission type For the templates you have the option to customise the optional fields. To check their description click on “Show Description “ Download the template and fill in the required information. Example of the runs template: We recommend that Fastq, BAM, and CRAM read files are submitted using Webin-CLI When using this interface instead of Webin-CLI, raw sequences must be uploaded in one of the supported data formats before they can be submitted. The files can be uploaded using FTP or Aspera. The study and the sequenced samples must be pre-registered before the raw reads are submitted. Please note that each individual study and sample should be registered only once. You will be asked to provide information about the sequencing libraries and instruments. Submitting your Dataset This section is only for sequence data submissions, for array based submissions it can be skipped. Please refer to our Submitting array based metadata The dataset describes the data files, defined by the run (EGARXXXXXXXXXXX) and analysis (EGAZXXXXXXXXXXX) accessions that make up the dataset and links the collection of data files to a specified Data Access Committee and Data Access Policy. As a result, you must have registered your Reads and experiments, Data Access Committee (DAC) and Data access policy before submitting your Dataset. Please consider the number of datasets that your submission consists of, for example, a case control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Please contact EGA Helpdesk for further assistance. Go to the “Data Access” box Click on “Register Dataset” Select the Data Access Committee (DAC) and Data access policy Register your dataset After submitting your dataset you should contact the EGA Helpdesk to provide a release date for your dataset. Datasets are automatically held (i.e. not released) unless they are affiliated to a study that has already been released. Edit/update existing submission metadata Go to the “Report” section of the object you would like to edit. Locate the object and click on the arrow under action. An option menu will be displayed. Objects can be edited through their XML or with the WEBIN menu. After an object has been edited, changes would be available on the website until the submission is released again. Please contact the EGA Helpdesk if you require further assistance.

  Documentation submission/metadata/submission/EGA_webin

• HTAN MCL Pre-Cancer Atlas Pilot Project - Targeted Sequencing Development Study

  The HTAN-MCL Pre-Cancer Atlas Pilot Project (PCAPP) is the result of a collaboration between the seven members of the MCL consortium. Across four organ types, PCAPP's goal is to collect and profile pre-malignant lesions for gene expression, DNA mutations, single-cell gene expression and immune-environment. Most PML are small in size and only available come from formalin fixed paraffin embedded archived tissue. The primary goal of PCAPP is to 1) understand the logistical challenges of PML specimen collection, 2) document technical limitations of the assays that are specific to the PML and 3) overcome them to support the generation of a more comprehensive Pre-Cancer Atlas in the future. The current upload provides RNA and DNA sequencing from participants with DCIS who were studied at the University of San Diego and the University of Vermont. Description of the overall study: A. Background/Significance One of the critical barriers to developing new approaches for cancer detection and prevention is the lack of understanding of the key molecular and cellular changes that cause cancer initiation and progression. Unlike the extensive work that has been done profiling advanced stage tumors, few studies have comprehensively profiled the molecular alterations found in precancerous tissues. Premalignant lesions are currently characterized by histologic changes that precede the development of invasive carcinoma1,2.These lesions can often be identified in regions surrounding an invasive tumor or in biopsies taken from patients undergoing diagnostic evaluation for suspicion of cancer. Currently, limited metrics exist to identify lesions that will likely progress to carcinoma and require intervention from those that will naturally regress or remain stable3,4. Characterization of the molecular alterations in premalignant lesions and the corresponding changes in the microenvironment would hasten the development of biomarkers for early detection and risk stratification as well as suggest preventive interventions to reverse or delay the development of cancer. Our pilot study will establish the feasibility of transcriptomic, genomic and immune profiling of FFPE premalignant lesions from multiple organ sites, collected and profiled with uniform SOPs across multiple institutions within the MCL consortium. We will characterize the molecular alterations in precancerous lesions and the corresponding microenvironment in four major organ sites, in order to uncover the molecular and cellular determinants of premalignancy, and establish standardized sequencing and immunohistochemistry protocols on FFPE precancerous tissue. We will also evaluate the technical feasibility of single nuclei sequencing of small FFPE pre-cancer lesions. Successful completion of the proposed pilot study will set the stage for expansion and development of a comprehensive Pre-Cancer Atlas (PCA) as part of the NCI's moonshot.B. Specific Aims Aim 1: Collect premalignant lesions (PML) and their associated microenvironment via LCM from FFPE tissue across four organ sites (breast, lung, pancreas &amp; prostate). Aim 2: Perform bulk RNA and DNA seq on premalignant FFPE samples (and flash frozen tissue where available) and compare the genomic/transcriptomic alterations within and across organ sites. C. ApproachAim 1: Collect premalignant lesions (PML) and their associated microenvironment via LCM from FFPE tissue across four organ sites (breast, lung, pancreas &amp; prostate). MethodsI. Patient Population/Sample Collection: Overview of the sites collecting PML tissue from the respective organs is provided in Table 1 and a full description of the biospecimens to be obtained is described in detail for each organ type below. Table 1. Breakdown of cohort by tissue type and collection site.Organ siteBreastLungPancreasProstateType of PMLDCISAAH, Squamous Dysplasia/CISIPMNsPINCollection of PatientsUCSF/UCSDUVMBU*/UCLAVanderbilt/MoffittMDACC*JHUStanford*# of Patients201920 (10 of each type)20 (10 of each type)242020Total patients per Organ39402440Note: single nuclei/cell RNA-Seq will be performed on 4-5 FFPE samples from each of the organ types 1. DCIS lesions from breast tissue: DCIS lesions will be collected from 39 patients (20 from UCSF/UCSD &amp; 19 from UVM) with primary low or high-grade DCIS diagnosed from a breast core biopsy. Subsequent resected lumpectomy or mastectomy tissues will be prospectively sampled in the vicinity of the prior biopsy site using multiple approaches: 1) Live cells (heterogeneous mix) will be obtained as a cell scrape slurry from the lesion surface or by fine needle aspirate (FNA); 2) For a subset of specimens where size is sufficient, a block of breast tissue with DCIS will be fresh-frozen; 3) The remainder of the specimen will be taken for routine formalin-fixation and paraffin-embedding (FFPE). The FFPE sample will be annotated to identify the matched FFPE tissue block adjacent to the fresh-frozen sample and will be sectioned for use in bulk and single nuclei sequencing . We will dissect DCIS, adjacent normal and when available, associated carcinoma. In addition, when possible, normal tissue will be collected from a tissue block lacking lesions as well as collection of blood. A subset of patients (n = 5 | FFPE, flash frozen and fresh) will be sent to the Broad Institute for single nuclei/cell sequencing.2. AAH and squamous dysplastic/CIS lesions from airway and lung tissue: For squamous cell lung cancer, we will collect endobronchial biopsies from abnormal airway regions identified on autofluroscence bronchoscopy or identify PMLs in the margins of resected lung tissue. We will study 20 patients (5 each from BU/UCLA/Vanderbilt/Moffitt) with pre-invasive squamous lesions (moderate-severe dysplasia or carcinoma in situ (CIS)) identified on pathologic examination. LCM of the premalignant region and adjacent normal epithelium will be performed as well as the invasive tumor for those collected from the resection margin (n=5 from UCLA). On a subset of lesions collected at bronchoscopy (n=5), we will collect additional biopsies that will be flash frozen and fresh for single nuclei and cell sequencing, respectively, performed at the Broad Institute. In parallel to the work at the Broad, BU will perform single cell RNA-seq on these freshly cell sorted tissues (n = 5). Blood will be collected on all patients for genomic studies. For lung adenocarcinoma, we will collect resected FFPE lung tissues from 20 patients (10 from UCLA and 10 from Vanderbilt/Moffitt) with early stage lung adenocarcinoma that harbor atypical adenomatous (AAH) premalignant lesions in the resection margin. We will LCM multiple AAH regions (3-5 per patient) as well as adjacent regions of normal epithelium and invasive adenocarcinoma. In addition, blood will be collected on all patients for genomic studies. 3. IPMNs from pancreatic tissue: For pancreatic cancer PML, we will collect low and high grade lesions from 24 patients representing macroscopic Intraductal Papillary Mucinous Neoplasms (IPMN) (n=24) from surgically resected specimens along with blood samples. Archival FFPE specimens of microscopic PanIN lesions, occurring multi-focally adjacent to invasive PDAC, and archival IPMN lesions (with or without associated invasive cancer), along with the adjacent normal tissue, will undergo LCM and utilized for bulk DNA and RNA sequencing. If matched frozen tissues are available for a subset of these FFPE samples, we will bank for comparison of profiles. Because IPMNs are macroscopic lesions, they provide an opportunity for obtaining the samples fresh and therefore can be used for single cell sequencing (in contrast to PanINs). Therefore, 5 freshly obtained IPMNs will be used for the single cell RNA sequencing studies performed at both the Broad Institute and MDACC, and the matched FFPE and/or frozen sections from these lesions (obtained from the adjacent PML) will be sent to Broad Institute as a pilot to assess "single nuclei" RNA sequencing.4. PINs from prostate tissue: For prostate cancer PML, there will be 40 samples of Prostatic Intraepithelial Neoplasia (PIN) collected between the Stanford and JHU sites (20 cases per site). At the Stanford site, 20 prostate specimens detected by PSA screening who have/will undergo surgery (radical prostatectomy) for clinically localized disease will make up the final cohort. The age range of the participants would be 40-75, and we anticipate that 18 will be Caucasian, 1 Asian and 1 Latino or African American based on the practice demographics practice at Stanford. Clinical and MRI data will also be collected for these samples. We will collect low grade (e.g. Gleason score of 6/Grade group 1; n=10) and high grade (Gleason score 4+3=7 or higher/Grade group 3 or higher; n=10) PINs from FFPE samples that have prostate carcinoma. In addition to obtaining LCM archival samples of low and high grade PIN, we will also obtain normal prostatic epithelial from the peripheral, central and transition zones as well as multiple samples of prostate carcinoma in order to obtain the spectrum of Gleason grades in the carcinoma as needed. LCM samples will be used for bulk DNA and RNA sequencing. In addition, single cells will be dissected from FFPE samples to prepare single cell RNA seq libraries using techniques developed at Stanford, and FFPE tissue will be sent to the Broad for single nuclei sequencing. When available, flash frozen and fresh samples from these prostates will be archived and prepared for single nuclei and cell sequencing, respectively, at the Broad Institute and at Stanford (single cell only). JHU will also capture 10 cases (5 grade group 1 and 5 grade group 2) of high grade PIN, normal and invasive adenocarcinoma using frozen sections from fresh frozen tissues. When possible these will be from the same patients as the FFPE samples. Since frozen sections can be quite challenging to morphologically determine high grade PIN from normal epithelium, for these samples we will perform a number of additional tissue-based characterizations. These will include a multicolor combined basal cells (p63 and CK903) and PIN/carcinoma markers (AMACR) referred to in the cocktail as "PIN4", c-MYC (referred to as MYC) protein5, by IHC and mRNA by in situ hybridization (AM De Marzo, Q Zheng unpublished observations), telomere length by in situ hybridization6 and the 5'ETS/45S rRNA7. For these slides, the whole slides will be scanned with a Hammamatsu Nanozoomer with a 40x objective and regions of interest will be annotated as a guide for LCM.II. Laser-capture microdissection (LCM): FFPE tissue blocks will be sectioned at 7&#956;m thickness and serial sections will be stained with H&amp;E. LCM will be performed utilizing standard LCM systems, such as Leica LMD7000 and ArcturusXT at each site. Regions of premalignancy will be dissected and RNA/DNA will be extracted from microdissected cells using the Qiagen All Prep DNA/RNA FFPE Kit. Aim 2: Perform bulk RNA and DNA seq on premalignant FFPE samples and compare the genomic/transcriptomic alterations within and across organ sites. Rationale: There have been limited studies characterizing the genomic and transcriptomic landscape of premalignant lesions associated with breast, pancreatic, lung or prostate cancers. Characterizing the molecular determinants of premalignant disease that are unique and shared across multiple organs will enable new candidate biomarkers for early detection and novel therapeutic strategies for early intervention. MethodsBulk RNA-seq of LCM FFPE tissue: All participating sites will perform bulk RNA-seq in accordance with SOPs developed at BU. In brief, total RNA will be isolated from LCM'd lesion and associated microenvironment tissue using the Qiagen All Prep DNA/RNA FFPE Kit and quality will be assessed with the Agilent Bioanalyzer. Libraries will be generated with the Illumina TruSeq Access kit (for FFPE samples). They will be sequenced on the Illumina HiSeq2500 with 75base-pair paired-end reads. Quality of FASTQ files will be assessed with FastQC. Reads will be aligned to the human genome with STAR and gene-level and isoform-level expression will be quantified with RSEM. Splice junction saturation, transcript integrity, and biotype distributions will be calculated for each sample with RSeQC. DESeq2 and EdgeR will be used to identify associations between gene expression profiles and clinical variables while controlling for confounding covariates. BU will serve as an RNA-seq Core to assess reproducibility of FFPE RNA-seq methods across sites. We will perform RNA-seq according to the SOP listed above on a subset of samples for each organ type (total n ~ 20). Bulk seq of DNA from FFPE tissue: All participating sites will perform targeted or whole exome-seq (WES) in accordance with SOPs. In brief, DNA from laser captured material will be isolated using the Qiagen All Prep DNA/RNA FFPE Kit and undergo stringent quality control to ensure high quality input material for genomic profiling. Purified DNA (ideally 100-200 ng) will be used for library preparation and amplification, followed by next generation sequencing using standard protocols distributed by CDMG. Exome-seq methods are considered standardized, thus we will not need a DNA-seq Core to assess reproducibility across sites. We anticipate local centers will use Illumina paired end reads, following the following general approach. 1) DNA library preparation: Paired-end libraries will be prepared following the manufacturer's protocols (Illumina and Agilent), fragmented to 150-200 bp 2) Capture of targeted exome: Whole exome capture will be carried out using the protocol for Agilent's SureSelect Human All Exon kit. Purified capture products will be amplified using the SureSelect GA PCR primers (Agilent) for 12 cycles. 3) Sequencing will be carried out for the captured libraries using at least 100 bp paired-end reads. To achieve high level sensitivity and accuracy for detecting all the mutations in the whole exome, each sample will be sequenced at 200X mean depth. 4) Read mapping and alignment and variant analysis: Sequence short reads will be aligned to a reference genome (NCBI human genome assembly build 38) using BWA-MEM. Local realignment of aligned reads will be performed using Genome Analysis Toolkit (GATK).Data QC: To ensure scientific rigor and consistency among sites in RNA and DNA processing we will include a preliminary analysis of steps in processing and analysis. Protocols for extraction of high quality RNA and DNA from formalin fixed paraffin embedded (FFPE) tissues, which will be used extensively in these studies continue to improve and may have variable implementation among the sites participating in this study. To evaluate consistency of preliminary steps in processing and downstream analyses, we will initially distribute slides from one large FFPE fixed cancer of origin from prostate, breast, lung and pancreatic cancer. Analysis of these samples will allow us to review the DNA and RNA characteristics (yield, purity and strand length) among sites. Downstream analysis of these same samples will also allow us to compare among sites the consistency of variant calls among centers. We will be able to identify if there are some times of calls (such as small insertion deletions) that are more variable among centers versus other types of calls (such as relative gene expression or single base pair substitutions) that we expect to be less variable and to characterize the reliability of findings across sites. We are also including a 5% blind duplicate analysis of RNA sequencing. Samples will be analysed by the participating genomics cores without knowledge of the phenotype. RNA seq and CNA analyses are normalized for batch effects. We will also compare the observed sex to the self-reported sex as based on RNA profiles and exome sequencing of X chromosome genes as another check for processing accuracy and sample management. D. References 1. Wacholder, S. Precursors in Cancer Epidemiology: Aligning Definition and Function. Cancer Epidemiol. Prev. Biomark. 22, 521-527 (2013). PMID: 23549395.2. Berman, J. J. Precancer: The Beginning and the End of Cancer. (Jones &amp; Bartlett Learning, 2011).3. Nasiell, K., Nasiell, M. &amp; Va&#263;lavinkov&#225;, V. Behavior of moderate cervical dysplasia during long-term follow-up. Obstet. Gynecol. 61, 609-614 (1983). PMID: 6835614.4. Merrick, D. T. et al. Persistence of Bronchial Dysplasia Is Associated with Development of Invasive Squamous Cell Carcinoma. Cancer Prev. Res. (Phila. Pa.) 9, 96-104 (2016). PMID: 26542061.5. Gurel, B. et al. Nuclear MYC protein overexpression is an early alteration in human prostate carcinogenesis. Mod. Pathol. Off. J. U. S. Can. Acad. Pathol. Inc 21, 1156-1167 (2008). PMID: 18567993.6. Meeker, A. K. et al. Telomere shortening is an early somatic DNA alteration in human prostate tumorigenesis. Cancer Res. 62, 6405-6409 (2002). PMID: 12438224.7. Guner, G. et al. Novel Assay to Detect RNA Polymerase I Activity In Vivo. Mol. Cancer Res. MCR 15, 577-584 (2017). PMID: 28119429.

  Study phs002225

• Privacy Notice for EGA Web user

  Privacy Notice for EGA Public Website This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by Mallory Freeberg, by: email at: mfreeberg@ebi.ac.uk , or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org , or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? For providing you access to the website and for offering support whilst using the website, we need your consent under Article 5 (2) of the IP 68 (equivalent to Article 6 (1)(a) of the GDPR). For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: IP addressesDate and time of a visit to the service website Operating systemAmount of data transmittedBrowserEmail address (only when support is requested by the user) The data controller will use your personal data for the following purposes: To provide the user access to the serviceTo better understand the needs of the users and guide future improvements of the serviceTo monitor website activities according to and in compliance with the Terms of UseTo better understand the needs of the website visitors and guide future improvements of the serviceTo conduct and monitor website security activitiesTo create anonymous usage statistics 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? There are no personal data transfers to third countries or international organisations. 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration.Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period.Request information to understand data processing activities when the results of these activities are applied to you.Object at any time to the processing of your personal data unless we can demonstrate that we have legitimate reasons to process your personal data.Request free of charge and without excessive delay rectification or erasure of your personal data if we have not been processing it respecting the data protection policies of the respective controllers. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. 9. CookiesWe use cookies and similar technologies that are strictly necessary for the correct functioning and security of the EGA website (for example, to enable core site features and to help protect the service). These cookies do not store information that directly identifies you.You can set your browser to block or delete cookies. Please note that if you disable strictly necessary cookies, parts of the website may not function properly.Published on February 6, 2019

  Documentation data-protection/privacy-notice/ega-website

• Resuscitation Outcomes Consortium (ROC) Amiodarone, Lidocaine or Neither for Out-Of-Hospital Cardiac Arrest Due to Ventricular Fibrillation or Ventricular Tachycardia (ALPS)(ROC-ALPS-BioLINCC)

  Accessing Data Please refer to &#8220;Authorized Access&#8221; below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP. Objective To compare the effects of amiodarone, lidocaine, and placebo on survival to hospital discharge after out-of-hospital cardiac arrest due to shock-refractory ventricular fibrillation or pulseless ventricular tachycardia. Background Ventricular fibrillation (VF) or pulseless ventricular tachycardia (VT) are common causes of out-of-hospital cardiac arrest, but are considered the most responsive to shock and therefore the most treatable. Nonetheless, most defibrillation attempts do not result in sustained return of spontaneous circulation, and VF or VT may persist or recur after shock. There is also evidence that longer durations of VF or VT are associated with decreases in the likelihood of resuscitation. Amiodarone and lidocaine are commonly used to promote successful defibrillation of shock-refractory VF or VT and prevent recurrences. Previous trials have shown amiodarone to be more effective than placebo or lidocaine for return of spontaneous circulation and survival at hospital admittance. This study sought to further extend the research and examine whether amiodarone would improve survival to hospital discharge and neurologic outcomes, as compared to placebo or lidocaine. Participants 3,026 eligible participants were enrolled, with 974 assigned to amiodarone, 993 assigned to lidocaine, and 1,059 assigned to placebo. An additional 1,627 participants that received a study intervention, but did not meet eligibility criteria, were included in analysis of the intention-to-treat population. Design The study interventions (amiodarone, lidocaine, and saline) were packaged in indistinguishable sealed kits and randomly distributed in to Emergency Medical Services (EMS) providers in a 1:1:1 ratio, stratified by participating site and agency. Each kit contained three syringes, and each syringe held 3 ml of colorless fluid containing 150 mg of amiodarone, 60 mg of lidocaine, or normal saline. Participants with out-of-hospital cardiac arrest were treated in accordance with local EMS protocols, in compliance with American Heart Association (AHA) guidelines. If VF or VT persisted or recurred after one or more shocks, eligible participants received a vasopressor and the masked kit containing amiodarone, lidocaine, or placebo. Approximating current clinical practice, the initial dose consisted of two syringes administered by rapid bolus. If the estimated body weight of the patient was less than 100 lbs., then one syringe was used. If VF or VT persisted, standard resuscitation measures, additional shocks, and an additional syringe of the study drug were administered. At that point the trial interventions were completed and standard interventions for advanced life support were employed. Upon arrival at the hospital, providers were notified of the patient's enrollment in the trial and encouraged to provide usual care in accordance with AHA guidelines, including open-label amiodarone or lidocaine if necessary. Components of hospital care were monitored but not standardized by the trial protocol. Participants, providers, and trial personnel were blinded to the trial drug assignments, with the exception of treating physicians if emergency un-blinding was required for care. Data from pre-hospital patient care records, CPR process measures, and hospital medical records were collected. The primary outcome of the trial was survival to hospital discharge, and the secondary outcome was survival with favorable neurologic status at discharge, defined as a score on the modified Rankin scale of 3 or less. Conclusions Neither amiodarone nor lidocaine resulted in a significantly higher rate of survival to hospital discharge or favorable neurologic outcome, as compared to placebo, among participants with out-of-hospital cardiac arrest due to initial shock-refractory ventricular fibrillation or pulseless ventricular tachycardia.

  Study phs003784

• Submitter Portal

  Submitter Portal The Submitter Portal does not support array submissions! Please refer to the array documentationAny new objects registered in the Submitter Portal will not be available for use in an array submission For further information please check our Submission FAQs, submission quickguide as well as submission terms! The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. Submitter Portal Index Previous steps Access to Submitter Portal Start a Submission Take The Tour Tutorial Previous steps Create your EGA account To submit data, you first need to create your EGA user. Then, once your account has been verified by the Help Desk team, you will be able to request a submitter role and send the EGA Data Processing Agreement (DPA). In the case you already have an EGA account, or an ega-box (submission account), you can skip this step. Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role and added your public key to your profile, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find relevant information in the DAC Portal Guide. Access to Submitter Portal 1. Request Submitter Role Once you have created your EGA user, request a Submitter Role and complete relevant information such as submission type and size. 2. Signature of the Data Processing Agreement The Data Processing Agreement (DPA) signed by CRG and EMBL-EBI (Joint Data Processors for the EGA) can be downloaded to the submitter for its signature. Further information related to the DPA can be in the Privacy Notice section. The DPA should be signed by a legal representative of the submitter with power of attorney/appointment duly authorised to sign contracts on behalf of the institution. The submitter will return a fully-executed copy of the DPA to us. Please note that due to the high volume of submissions to EGA the DPA is non-negotiable. Once you have completed all the information and attached the DPA signed, send your Submitter request and the EGA Helpdesk Team will validate it and send a confirmation to start submitting your metadata. Start a Submission The steps below will show you how to start a submission and are accompanied with a tutorial and the Take the tour of Submitter Portal. 1. Login Go to the Submitter Portal interface and log in using your EGA account credentials. 2. Create a submission The Submitter Portal interface will show you any already existing open submission. To start a new submission click on “Create a Submission”.In this phase you have the option to add any collaborator(s) as well as their permissions (“Read only” or “Read & Write”). If you want to invite all the collaborators from a previous submission, you can add them by selecting said submission.In the event that the submission has been closed, you will need to reopen it. To do this, you will need to modify one of the objects in the submission, for example, copy and paste the title. Once the submission is open, you can add a collaborator. Further information can be found in the Submission Tour 3. Create Study Click on add Study and complete the form with the relevant information. The fields with an asterisk (*) are mandatory. Further information can be found in the Submission Tour4. Create Sample Sample registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with information about the sequencing samples. Upload the samples.csv and the sample will be created.Add single sample: complete the mandatory fields with the metadata information of your sample.  Further information can be found in the Submission Tour5. Create Experiment Register an experiment with ​information about the sequencing methods, protocols and machines. Experiments generate the connection between samples and study. Further information can be found in the Submission Tour6. Create Run Samples, experiments and files are linked through runs. To register a run, you will be asked to select the appropriate experiment and the file format. Run registration can be done either individually or in batch by using a template. Batch upload: download the template and complete it with the sample - file linkage. Upload the run.csv and the runs will register.As the INBOX is a directory, bear in mind to include the file path (/). Example: /filename.c4gh. Add single run: select the file format, sample and experiment from the drop box. For re-using submitted samples, please use the EGA accession ID (EGANXXX). Please note that files must be uploaded in your inbox before linking your files and samples. Further information can be found in the Submission Tour7. Create Analysis Analysis should be only used for BAM/BAI or CRAM/CRAI pair, VCF and phenotype linkage to samples. The analysis is an EGA specific metadata object that links samples to files. This object also stores some metadata about your experiments, such as the experiment type, genome reference, or the platform used. **If only BAM or CRAM alignment files are submitted but not the original unaligned FASTQ files, then please make sure that the BAM or CRAM files also contain the unaligned reads. This is critical to enable primary re-analysis and re-alignment of the dataset using new tools or future genome assemblies.** Start by selecting the samples to be linked to the file, and then populate the required attribute fields. Please be aware of the existence of mandatory fields that must be populated.When populating the chromosome field (mandatory), please select the chromosomes from the checkbox. Please take in consideration that EGA allows for the re-use of any registered metadata. Therefore, a previously registered study or samples can be referenced for the analysis in the current data submission.Further information can be found in the Submission Tour 8. Create Dataset Dataset contains the collection of runs/analysis data files subjected to controlled access by being associated with a Policy. Complete the mandatory fields such as title, description, type and policy. Please, take in consideration that DAC and Policy must be registered in advance in the DAC Portal. Similar to other metadata objects, you can re-use previous runs or analyses, using their EGA accessions IDs (runs - EGAR, analyses - EGAZ). Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested please delete them from your SFTP INBOX before finalising your submission. This will prevent the files from reappearing in your Submitter Portal Inbox. Once you have completed your submission, click on the Finalise button, and schedule an estimated release date. Afterwards, your submission will be sent to Helpdesk for approval. Please note that once the Helpdesk has approved your submission, you will receive the identifiers for your data. See the Frequently Asked Questions (FAQ) for more information. 10. Update closed submission If you want to append more file to a closed submission, you will need to re-open the submission where the dataset was registered. Find the Submission: go to the Submitter Portal Menu -> Datasets section and find the submission id (EGA0XXX).  Reopen the submission where the dataset is located: to reopen a submission, you must edit any object within the submission. For example, you can copy and paste the title. Take The Tour The Submitter Portal Take The Tour is a visual guidance of all the steps described previously about how to start a submission. Tutorial In this tutorial we will show you how to use the Submitter Portal to register your metadata. Please note the video focuses on the run-based submission (for raw files - fastq - and aligned data - BAM/CRAM) and analysis-based submission (for your BAM/BAI pairs, variation -VCF - and phenotype files).

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal

• Implementation, Adoption, and Utility of Family History in Diverse Care Settings

  The purpose of this study is to address the key question of whether and how family health history (FHH) is adopted as a tool to more efficiently manage patients at risk for breast, colon, ovarian, and hereditary cancer syndromes as well as thrombophilia and coronary heart disease (CHD) and to provide evidence supporting clinical utility -- improved health behaviors in patients and physician screening recommendations. Five health care delivery organizations will participate in this demonstration project: Duke University, the Medical College of Wisconsin, the Air Force, Essentia Health, University of North Texas. Duke will serve as a coordinating center for this project (Pro00043372) as well as a site. Healthcare Effectiveness Data and Information Set (HEDIS) measures as intermediate clinical effectiveness measures for Coronary Heart Disease (CHD) and selected cancers as well as survey/formative data and electronic medical record (EMR) data will be used as outcomes measures. The research model is purposely designed to mimic clinical delivery as an important step toward widespread implementation and sustainability. In addition, a cost-effectiveness analysis comparing usual care to the FHH guided preventive health model will be used. The completion of this project will result in an optimal strategy for integration of FHH data collection and clinical decision support (CDS) tools into an EMR and demonstrate the utility of the FHH intervention among diverse primary care patients, their settings, their providers, and the health systems that deliver their care. Specific Aim 1: To optimize the collection of patient entered FHH in diverse clinical environments for coronary heart disease, thrombosis, and selected cancers Specific Aim 2: To export FHH data to an open clinical decision support (open CDS) platform and return CDS results to providers and patients (and to EMRs where relevant). To explore the integration of genetic risk and FHH data at selected sites. Specific Aim 3: To assess the clinical and personal utility of FHH using a pragmatic observational study design to assess reach, adoption, integrity, exposure, and sustainability, and to capture, analyze, and report effectiveness outcomes at each stakeholder level: patient, provider, and clinic/system. Specific Aim 4: To take a leadership role in the dissemination of guidelines for a FHH intervention across in diverse practice settings. AAA Hypertension Lupus Multiple sclerosis Obesity Osteoporosis Thyroid disease Rheumatoid arthritis Blood clotting (6): Blood Clot (high risk features) Factor V PT mutation AT III deficiency Protein S deficiency Protein C deficiency Brain Disorders (5): Dementia Hemorrhagic stroke Ischemic stroke Macrocephaly Seizure Cancer/Adenomas (32): Bone cancer Brain cancer Breast cancer Colon cancer Adrenal cortex tumor Neuroendocrine tumor Paraganglioma Pheochromoctyoma Pituitary adenoma Medullary thyroid cancer Non-medullary (follicular or papillary) thyroid cancer Don&#39;t know type of thyroid cancer Thyroid nodule Other type of endocrine cancer Esophageal cancer Kidney cancer Leukemia Lipoma Liver cancer Muscle cancer Ovarian cancer Pancreatic cancer Prostate cancer Rectal cancer Retinoblastoma Melanoma Non-melanoma skin cancer Do not know type of skin cancer Small bowel cancer Stomach cancer Uterine cancer Other type of cancer Cardiovascular/heart/artery disease (5): Atrial fibrillation Carotid stenosis Heart attack/coronary artery disease Peripheral arterial disease Other heart disease Diabetes (3): Gestational diabetes Diabetes type I Diabetes type 2 Digestive Disorders (5): Colon polyp Crohn&#39;s disease Irritable bowel syndrome Ulcerative colitis Other digestive disorder Eye Disorder (3): Blindness Glaucoma Macular degeneration Hereditary Cancer Syndromes (22): Birt-Hogg-Dube syndrome Cowden syndrome Familial adenomatous polyposis Hereditary breast and ovarian cancer syndrome Hereditary diffuse gastric cancer Hereditary leiomyomatosis and renal cell carcinoma syndrome Hereditary melenoma Hereditary papillary renal cancer syndrome Hereditary paraganglioma-pheochromocytoma syndrome Hereditary retinoblastoma Juvenile polyposis Li-Fraumeni syndrome Lynch syndrome Mutyh-associated polyposis Malignant hyperthermia susceptibility Multiple endocrine neoplasia type 1 Multiple endocrine neoplasia type 2 Nevoid basal cell carcinoma syndrome Peutz-Jeghers syndrome Tuberous Sclerosis complex Von-Hippel Lindau syndrome Other hereditary cancer Hereditary Cardiovascular syndromes (10): Long qt Brugada Catecholaminergic polymorphic ventricular tachycardia Hypertrophic cardiomyopathy Dilated cardiomyopathy Left ventricular non-compaction syndrome Arrhythmogenic right ventricular dysplasia Ehlers-Danlos syndrome Marfan syndrome Other hereditary cardiovascular syndrome High cholesterol (2): Hyperlipidemia Familial hypercholesterolemia Kidney Disease (6): Cystic kidney disease Diabetic kidney disease Kidney nephrosis Nephritis Nephrotic syndrome Other kidney disease Liver Disease (6): Alpha 1 antitrypsinase deficiency Auto-immune hepatitis Hereditary hemochromatosis Primary biliary cirrhosis Sclerosing cholangitis Wilson&#39;s disease Lung Disease (3): Asthma COPD/chronic bronchitis/emphysema Other lung disease Psychological disorder (14): Addiction ADHD Autism Bipolar Depression Eating disorder Intellectual disability Obsessive compulsive disorder Panic disorder Personality disorder PTSD Schizophrenia Social phobia Sickle cell/thalassemia (3): Sickle cell disease Sickle cell trait Thalassemia

  Study phs001641

• DNA Methylation Analysis of Prostate Cancer Cell Lines and Tissues Using Next Generation Sequencing

  Aberrant DNA methylation changes are known to occur during prostate cancer progression beginning with precursor lesions. Utilizing fifty nanograms of genomic DNA in Methylplex-Next Generation Sequencing (M-NGS) we mapped the global DNA methylation patterns in prostate tissues (n=17) and cells (n=2). Peaks were located from mapped reads obtained in each sequencing run using a Hidden Markov Model (HMM)-based algorithm previously used for Chip-Seq data analysis(http://www.sph.umich.edu/csg/qin/HPeak). The total methylation events in intergenic/intronic regions between benign adjacent and cancer tissues were comparable. Promoter CGI methylation gradually increased from -12.6% in benign samples to 19.3% and 21.8% in localized and metastatic cancer tissues and approximately 20% of all CpG islands (CGIs) (68,508) were methylated in tissues. We observed distinct patterns in promoter methylation around transcription start sites, where methylation occurred directly on the CGIs, flanking regions and on CGI sparse promoters. Among the 6,691 methylated promoters in prostate tissues, 2481 differentially methylated regions (DMRs) are cancer specific and several previously studied targets were among them. A novel cancer specific DMR in WFDC2 promoter showed 77% methylation in cancer (17/22), 100% methylation in transformed prostate cell lines (6/6), none in the benign tissues (0/10) and normal PrEC cells. Integration of LNCaP DNA methylation and H3K4me3 data suggested a role for DNA methylation in alternate transcription start site utilization. While methylated promoters containing CGIs had mutually exclusive H3K4me3 modification, the histone mark was absent in CGI sparse promoters. Finally, we observed difference in methylation of LINE-1 elements between transcription factor ERG positive and negative cancers. The comprehensive methylome map presented here will further our understanding of epigenetic regulation of the prostate cancer genome. Overall Design: We mapped the global DNA methylation patterns in prostate tissues (n=17) and cells (n=2) from fifty nanograms of genomic DNA using Methylplex-Next Generation Sequencing (M-NGS). For replicate analysis in cell lines, a total of 4 runs were completed for PrEC prostate normal cell line, and 5 runs were completed for LNCaP prostate cancer cell line. For tissue samples, 2 benign prostate samples were sequenced twice on Illumina next generation sequencing platform to access overall repeatability of M-NGS.

  Study phs000597

• Osteoporotic Fractures in Men (MrOS)

  The Osteoporotic Fractures in Men Study (MrOS) is a multi-center prospective, longitudinal, observational study of risk factors for vertebral and all non-vertebral fractures in older men, and of the sequelae of fractures in men. The original specific aims of the study include: (1) to define the skeletal determinants of fracture risk in older men, (2) to define lifestyle and medical factors related to fracture risk, (3) to establish the contribution of fall frequency to fracture risk in older men, (4) to determine to what extent androgen and estrogen concentrations influence fracture risk, (5) to examine the effects of fractures on quality of life, (6) to identify sex differences in the predictors and outcomes of fracture, (7) to collect and store serum, urine and DNA for future analyses as directed by emerging evidence in the fields of aging and skeletal health, and (8) define the extent to which bone mass/fracture risk and prostate diseases are linked. The MrOS study population consists of 5,994 community dwelling, ambulatory men aged 65 years or older from six communities in the United States (Birmingham, AL; Minneapolis, MN; Palo Alto, CA; Monongahela Valley near Pittsburgh, PA; Portland, OR; and San Diego, CA). Inclusion criteria were designed to provide a study cohort that is representative of the broad population of older men. The inclusion criteria were: (1) ability to walk without the assistance of another, (2) absence of bilateral hip replacements, (3) ability to provide self-reported data, (4) residence near a clinical site for the duration of the study, (5) absence of a medical condition that (in the judgment of the investigator) would result in imminent death, and (6) ability to understand and sign an informed consent. To qualify as an enrollee, the participant had to provide written informed consent, complete the self-administered questionnaire (SAQ), attend the clinic visit, and complete at least the anthropometric, DEXA, and vertebral X-ray procedures. There were no other exclusion criteria. The baseline examination was completed over a 25-month period from March 2000 to April 2002. Participants completed questionnaires regarding medical history, medications, physical activity, diet, alcohol intake, and cigarette smoking. Objective measures of anthropometric, neuromuscular, vision, strength, and cognitive variables were obtained at a clinic visit. Skeletal assessments included DEXA, calcaneal ultrasound, and vertebral radiographs. Vertebral and proximal femoral QCT was performed on a subset (65%) of participants. Serum, urine, and whole blood specimens were collected. During the study period, participants complete a tri-annual questionnaire every four months that obtains information concerning the occurrence of incident falls and fractures. Follow-up is over 99% complete. All reported fractures are confirmed using physician review of radiology reports or study radiologist review of x-rays. All deaths are also centrally adjudicated using death certificates and recent hospitalization records. In additional to the baseline study visit and tri-annual questionnaires, all surviving active participants were invited to follow-up visits and questionnaires. A second comprehensive clinic visit was completed between March 2005 and May 2006 or about 4.5 years after baseline. Most baseline measures, including vertebral radiographs, were repeated at the second visit. A third comprehensive clinic visit was completed between March 2007 and March 2009 or about 7.0 years after baseline. Many baseline measures were repeated at the third visit. A measure of energy expenditure was also obtained utilizing an accelerometer based armband device. Surviving participants have also completed two extensive mailed questionnaires designed to updated information obtained at clinic visits. The first questionnaire was mailed between baseline and visit 2 between July 2002 and March 2004. The second questionnaire was mailed after the third questionnaire between March 2009 and February 2011. The MrOS Sleep Study, an ancillary study of the parent MrOS cohort, was conducted between December 2003 and March 2005 and recruited 3,135 MrOS participants for a comprehensive sleep assessment. Men were screened for nightly use of mechanical devices during sleep including pressure mask for sleep apnea (CPAP or BiPAP), mouthpiece for snoring or sleep apnea, or oxygen therapy and were generally excluded. The sleep visit included objective measures of sleep using actigraphy and polysomnography. Other measures at the sleep visit include neuropsychiatric measures, performance measures, health related questionnaires, routine exam measures previously completed at MrOS clinic visits and a urine and serum specimen collection. During the sleep study period, participants complete a tri-annual questionnaire every four months that contains information about incident cardiovascular events. All reported events are centrally adjudicated utilizing hospital records, study ECGs and other supporting documentation. The Hip Osteoarthritis study, another ancillary study of the parent MrOS cohort, was completed at the second clinic visit between March 2005 and May 2006. Participants were asked for consent for a hip x-ray and osteoarthritis measurements were obtained from these x-rays. DNA was extracted from baseline whole blood samples for use in genetic research. Consent for use of DNA was obtained through written consent. Raw GWAS data is housed at the study&#39;s coordinating center and not released as part of the dbGAP release. The raw data can be requested from the study&#39;s coordinating center. Only QC cleaned Plink files are available on dbGAP.

  Study phs000373

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• ICGC Data Access Compliance Office

  To access Controlled Access ICGC data at the EGA you must first apply for access on the DACO form. Instructions on this process is available from this web site: http://docs.icgc.org/portal/access/

  Dac EGAC00001000010

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Transcriptome of CD4+ T cells and CD8+ T cells in glioblastoma multiforme

  Patients included in this study were over 18 years of age and had a histology-confirmed diagnosis of glioblastoma multiforme (GBM). Exclusion criteria were the previous administration of any anti-tumor therapy including radiation therapy. All patients gave written informed consent. The study was approved by the local ethics committee (TUM Medical school) and conducted following the Declaration of Helsinki. During resection of the tumors, tumor tissue and tissue from normal appearing brain within the operative channel was collected. Blood was drawn during the surgical procedure. Single cell suspensions were prepared from the tumor tissue, the normal appearing brain, and the blood. CD4+ T cells and CD8+ T cells were sorted by flow cytometry. Only patients with a complete set of specimens (CD4+ tumor infiltrating lymphocytes (TIL), CD8+ TIL, CD4+ T cells from normal appearing brain, CD8+ T cells from normal appearing brain, blood-derived CD4+ and CD8+ T cells) containing a minimum of 1000 cells in each sorted sample were further analyzed (n=9). Total RNA was isolated from sorted cell populations using the RNAeasy Plus micro kit (Qiagen, 74034). Quality and integrity of total RNA was controlled on a Bioanalyzer 2100 (Agilent Technologies). Library preparation for bulk-sequencing of poly(A)-RNA was done as described previously (Parekh et al., 2016). Briefly, barcoded cDNA of each sample was generated with a Maxima RT polymerase (ThermoFisher Scientific, EP0742) using oligo-dT primer containing barcodes, unique molecular identifiers (UMIs) and an adaptor. Ends of the cDNAs were extended by a template switch oligo (TSO) and full-length cDNA was amplified with primers binding to the TSO-site and the adaptor. NEB UltraII FS kit was used to fragment cDNA. After end repair and A-tailing, a TruSeq adapter was ligated and 3'-end-fragments were finally amplified using primers with Illumina P5 and P7 overhangs. In comparison to previous descriptions (Parekh et al., 2016), the P5 and P7 sites were exchanged to allow sequencing of the cDNA in read 1 and barcodes and UMIs in read 2 to achieve a better cluster recognition. The library was sequenced on a NextSeq 500 (Illumina) with 59 cycles for the cDNA in read 1 and 16 cycles for the barcodes and UMIs in read 2. Data were processed using the published Drop-seq pipeline (v1.0) to generate sample- and gene-wise UMI tables (Macosko et al., 2015). Reference genome (GRCh38) was used for alignment. Transcript and gene definitions were used according to the Genecode Annotation Version 35.

  Study EGAS50000000156

• ELLIPSE Prostate Cancer Meta-Analysis and Genotyping

  The ELLIPSE Consortium is an international effort to discover risk loci for prostate cancer. It includes the meta-analysis of existing GWAS data as well as novel GWAS, exome, and iCOGS genotyping. The GWAS meta-analysis includes the following cases and controls from studies of European ancestry: UK GWAS stage 1 (Illumina Infinium HumanHap 550 Array: 1854 cases and 1894 controls), UK GWAS stage 2 (Illumina iSELECT: 3706 cases and 3884 controls), CAPS1 (Affymetrix GeneChip 500K: 474 cases and 482 controls), CAPS2 (Affymetrix GeneChip 5.0K: 1458 cases and 512 controls), BPC3 (Illumina Human610 Illumina: 2068 cases and 3011 controls), PEGASUS (HumanOmni2.5: 4600 cases and 2941 controls). The OMNI 2.5M genotyping was conducted for 977 prostate cancer cases from UKGPCS. The Exome SNP array genotyping was conducted for 4741 subjects from UKGPCS. The iCOGs genotyping was conducted for 10366 subjects which includes the Multiethnic Cohort (n=1648) and UKGPCS (n=8718). Below is a description of each study that contributed to the meta-analysis of men of European ancestry. Information about the studies that contributed to the multiethnic meta-analysis can be found on the associated study page and also in Conti et al (Nature Genetics, PMID:33398198).&nbsp;&nbsp; UK GWAS Stage 1 (UK1) and Stage 2 (UK2): The UK Genetic Prostate Cancer Study (UKGPCS) was first established in 1993 and is the largest prostate cancer study of its kind in the UK, involving nearly 189 hospitals. We are based at The Institute of Cancer Research in Sutton, Surrey, and collaborate with the Royal Marsden NHS Foundation Trust. Our aim is to find genetic changes which are associated with prostate cancer risk. Our target is to recruit 26,000 gentlemen into the UKGPCS by 2017. Men are eligible to take part if they fit into at least one of the following groups: They have been diagnosed with prostate cancer at 60 years of age or under (up to their 61st birthday). They have been diagnosed with prostate cancer and a first, second or third degree relative where at least one of these men were diagnosed with prostate cancer at 65 years of age or under. They are affected and have 3 or more cases of prostate cancer on one side of their family. They are a prostate cancer patient at the Royal Marsden NHS Foundation Trust. We have to date recruited around 16,000 men on whom we have germline DNA and clinical data at diagnosis. The UK GWAS is based on genotyping of 541,129 SNPs in 1,854 individuals with clinically detected (non-PSA-screened) prostate cancer (cases) and 1,894 controls. 43,671 SNPs showing strong evidence of association in stage 1 were followed up by genotyping a further 3,268 cases and 3,366 controls from UK and Melbourne in stage2. CAPS1 and CAPS2: The CAPS (Cancer of the Prostate in Sweden) study represents a large Swedish population-based cancer study, comprising 3,161 cases and 2,149 controls, recruited between 2001 and 2003. Biopsy confirmed prostate cancer cases were identified and recruited from four out of six regional cancer registries in Sweden, diagnosed between July 2001 and October 2003. Clinical data including TNM stage, Gleason grade and PSA levels at time for diagnosis were retrieved through record linkage to the National Prostate Cancer Registry. Control subjects, who were recruited concurrently with case subjects, were randomly selected from the Swedish Population Registry and matched according to the expected age distribution of cases (groups of 5-year intervals) and geographic region. Whole blood was collected from all individuals for extraction of genomic DNA. A GWAS was conducted in two parts. In the first phase (CAPS1) 498 cases and 502 controls were genotyped, in the second phase 1,483 cases and 519 controls were genotyped. Genotyping was performed using the GeneChip Human Mapping 500K (CAPS1) and 5.0K (CAPS2) Array Set from Affymetrix (Santa Clara, CA). The National Cancer Institute Breast and Prostate Cancer Cohort Consortium, BPC3: BPC3 was a consortium of prospective cohort studies investigating genetic and gene-environmental risk factors for breast and prostate cancer. Each study selected cases and controls for this study as described below. The clinical criteria defining advanced prostate cancer (Gleason = 8 or stage C/D) were either obtained from medical records or cancer registries. The Gleason score source was either surgical specimens (radical prostatectomy or autopsy) or the diagnostic biopsy (needle biopsy or TURP). When multiple Gleason scores were available the surgical value was used. PLCO was removed from the analysis as the samples were included in the Pegasus GWAS described below. In total 2,473 advanced prostate cancer cases and 3,534 controls were included in the analysis following QC. ATBC, Alpha-Tocopherol, Beta-Carotene Cancer Prevention Study: ATBC was a randomized, placebo-controlled primary prevention trial to investigate whether &#945;-tocopherol or &#223;-carotene supplementation reduced the incidence of lung or other cancers in male smokers. Between 1985 and 1988, 29,133 men ages 50 to 69 years were enrolled in the trial from Finland and randomized to supplementation (50 mg &#945;-tocopherol, 20mg &#223;-carotene, or both) or placebo. Men with a prior history of cancer, other than non-melanoma skin cancer or carcinoma in situ, were excluded from participating. Incident cancer cases are identified through linkage with the Finnish Cancer Registry, which has ~100% ascertainment of cancer cases nationwide. Cases included 249 men diagnosed with advanced prostate cancer (Gleason = 8 or stage C/D) from 1985 to 2003 with DNA available. Controls were 1,271 men selected previously for a GWAS of lung cancer in ATBC without a diagnosis of prostate cancer. CPSII, Cancer Prevention Study II: CPSII is a cohort study started in 1982 to investigate the relationship between dietary, lifestyle and other etiologic factors and cancer mortality. Approximately 1.2 million men and women enrolled in the study from 50 states in the U.S. In 1992, a subset of these participants (n= ~184,000) were enrolled in the CPSII Nutrition Cohort to examine the relationship between dietary and other exposures and cancer incidence. Blood samples were drawn from approximately 39,376 members of the Nutritional Cohort from 1998 to 2001, and buccal cells were collected from 69,467 members from 2001 to 2002. Cancer cases are identified by self-report through follow-up questionnaires followed by verification through medical records and/or linkage to state cancer registries as well as death certificates. A total of 660 advanced prostate cancer cases (Gleason = 8 or stage III/IV) with a source of DNA were identified for this study. Controls were 660 men matched on ethnicity, date of birth, sample collection date and DNA type. EPIC, European Prospective Investigation into Cancer and Nutrition: EPIC is a prospective study designed to investigate both genetic and non-genetic risk factors for different forms of cancer. Study participants were almost all white Europeans. Approximately 500,000 individuals (150,000 men) in EPIC were recruited between 1992 and 2000, from 23 centers in 10 European countries. Overall approximately 400,000 subjects also provided a blood sample at recruitment. The methods of recruitment and details of the study design are described in detail elsewhere. In brief, study participants completed an extensive questionnaire on both dietary and nondietary data at recruitment. The present study includes subjects from advanced prostate cancer cases (Gleason = 8 or stage III/IV) matched to controls based on study center, length of follow-up, age at enrollment (&#177; 6 months), fasting and time of day of blood collection (&#177; 1 hour). The advanced prostate cancer subjects were from 8 of the 10 participating countries: Denmark, Germany, Greece, Italy, the Netherlands, Spain, Sweden and the United Kingdom (UK). France and Norway were not included in the current study because these cohorts only included female subjects. All participants gave written consent for the research and approval for the study was obtained from the ethical review board from all local institutions in the regions where participants had been recruited for the EPIC study. HPFS, Health Professionals Follow-up Study: HPFS began in 1986 and is an ongoing prospective cohort study of 51,529 United States male dentists, optometrists, osteopaths, podiatrists, pharmacists, and veterinarians 40 to 75 years of age. The baseline questionnaire provided information on age, marital status, height and weight, ancestry, medications, smoking history, disease history, physical activity, and diet. At baseline the cohort was 97% white, 2% Asian American, and 1% African American. The median follow-up through 2005 was 10.5 years (range 2-19 years). Self-reported prostate cancer diagnoses were confirmed by obtaining medical and/or pathology records. Prostate cancer deaths are either reported by family members in response to follow-up questionnaires, discovered by the postal system, or the National Death Index. Questionnaires are sent every two years to surviving men to update exposure and medical history. In 1993 and 1994, a blood specimen was collected from 18,018 men without a prior diagnosis of cancer. Prostate cancer cases are matched to controls on birth year (+/-1) and ethnicity. Controls are selected from those who are cancer-free at the time of the case&#8217;s diagnosis, and had a prostate-specific antigen test after the date of blood draw.&nbsp;&nbsp; MEC, Multiethnic Cohort: The Multiethnic Cohort Study is a population-based prospective cohort study that was initiated between 1993 and 1996 and includes subjects from various ethnic groups - African Americans and Latinos primarily from Californian (great Los Angeles area) and Native Hawaiians, Japanese-Americans, and European Americans primarily from Hawaii. State drivers&#8217; license files were the primary sources used to identify study subjects in Hawaii and California. Additionally, in Hawaii, state voter&#8217;s registration files were used, and, in California, Health Care Financing Administration (HCFA) files were used to identify additional African American men. All participants (n=215,251) returned a 26-page self-administered baseline questionnaire that obtained general demographic, medical and risk factor information. In the cohort, incident cancer cases are identified annually through cohort linkage to population-based cancer Surveillance, Epidemiology, and End Results (SEER) registries in Hawaii and Los Angeles County as well as to the California State cancer registry. Information on stage and grade of disease are also obtained through the SEER registries. Blood sample collection in the MEC began in 1994 and targeted incident prostate cancer cases and a random sample of study participants to serve as controls for genetic analyses. PHS, Physicians Health Study:PHS was a randomized trial of aspirin and &#223; carotene for cardiovascular disease and cancer among 22,071 U.S. male physicians ages 40-84 years at randomization; none had a cancer diagnosis at baseline. The original trial ended, but the men are followed. From 1982 to 1984, blood samples were collected from 14,916 physicians before randomization. Participants are sent yearly questionnaires to ascertain endpoints. Whenever a physician reports cancer, we request permission to obtain the medical records, and cancers are confirmed by pathology report. We obtain death certificates and pertinent medical records for all deaths. Follow-up for nonfatal outcomes in PHS is over 97% complete, and for mortality, over 99%. PLCO, Prostate, Lung, Colorectal and Ovarian Cancer Screening Trial:PLCO is a multicenter, randomized trial to evaluate screening methods for the early detection of prostate, lung, colorectal and ovarian cancer. Between 1993 and 2001, over 150,000 men and women ages 55-74 years were recruited from ten centers in the United States (Birmingham, AL; Denver, CO; Detroit, MI; Honolulu, HI; Marshfield, WI; Minneapolis, MN; Pittsburgh, PA; Salt Lake City, UT; St. Louis, MO; and Washington, D.C.). Men randomized to the screening arm underwent prostate cancer screening with prostate-specific antigen (PSA) annually for six years and digital rectal exam annually for four years. Blood specimens were collected from participants randomized to the screening arm of the trial, and buccal cell specimens were obtained from participants randomized to the control arm. Cases included 754 men diagnosed with advanced prostate cancer (Gleason = 8 or stage III/IV) from either arm of the trial. Of these cases, 317 were genotyped previously as part of Cancer Genetic Markers of Susceptibility (CGEMS), a GWAS for prostate cancer. Controls included 1,491 men without a diagnosis of prostate cancer from the screening arm of the PLCO trial. All subjects provided informed consent to participate in genetic etiology studies of cancer and other traits. This study was approved by the institutional review boards at the ten centers and the National Cancer Institute. PLCO was removed from the meta-analysis of the BPC3 studies as a consequence of PEGASUS below. PEGASUS, Prostate cancer Genome-wide Association Study of Uncommon Susceptibility loci: Pegasus is a genome-wide association nested within the Prostate, Lung, Colorectal and Ovarian (PLCO) Cancer Screening Trial. PLCO is a multicenter, randomized trial to evaluate screening methods for the early detection of prostate, lung, colorectal and ovarian cancer. Between 1993 and 2001, over 150,000 men and women ages 55-74 years were recruited from ten centers in the United States (Birmingham, AL; Denver, CO; Detroit, MI; Honolulu, HI; Marshfield, WI; Minneapolis, MN; Pittsburgh, PA; Salt Lake City, UT; St. Louis, MO; and Washington, D.C.). Men randomized to the screening arm underwent prostate cancer screening with prostate-specific antigen annually for six years and digital rectal exam annually for four years. Blood specimens were collected from participants randomized to the screening arm of the trial, and buccal cell specimens were obtained from participants randomized to the control arm. Cases included 4,598 men of European ancestry diagnosed with prostate cancer from either arm of the trial and controls included 2,941 men of European ancestry without a diagnosis of cancer from the screening arm, matched on age and year of randomization. All subjects provided informed consent, and the study approved by the institutional review board at the National Cancer Institute. Funding:This work was supported by the GAME-ON U19 initiative for prostate cancer (ELLIPSE): U19 CA148537. The BPC3 was supported by the U.S. National Institutes of Health, National Cancer Institute (cooperative agreements U01-CA98233, U01-CA98710, U01-CA98216, and U01-CA98758, and Intramural Research Program of NIH/National Cancer Institute, Division of Cancer Epidemiology and Genetics). The ATBC study and PEGASUS was supported in part by the Intramural Research Program of the NIH and the National Cancer Institute. Additionally, this research was supported by U.S. Public Health Service contracts N01-CN-45165, N01-RC-45035, N01-RC-37004 and HHSN261201000006C from the National Cancer Institute, Department of Health and Human Services. CAPS: The Department of Medical Epidemiology and Biostatistics, Karolinska Institute, Stockholm, Sweden was supported by the Cancer Risk Prediction Center (CRisP; www.crispcenter.org), a Linneus Centre (Contract ID 70867902) financed by the Swedish Research Council, Swedish Research Council (grant: K2010-70X-20430-04-3), the Swedish Cancer Foundation (grant: 09-0677), the Hedlund Foundation, the S&#246;derberg Foundation, the Enqvist Foundation, ALF funds from the Stockholm County Council. Stiftelsen Johanna Hagstrand och Sigfrid Linn&#233;r&#8217;s Minne, Karlsson&#8217;s Fund for urological and surgical research. We thank and acknowledge all of the participants in the Stockholm-1 study. We thank Carin Cavalli-Bj&#246;rkman and Ami R&#246;nnberg Karlsson for their dedicated work in the collection of data. Michael Broms is acknowledged for his skillful work with the databases. KI Biobank is acknowledged for handling the samples and for DNA extraction. Hans Wallinder at Aleris Medilab and Sven Gustafsson at Karolinska University Laboratory are thanked for their good cooperation in providing historical laboratory results. UKGPCS would like to acknowledge the NCRN nurses and Consultants for their work in the UKGPCS study. We thank all the patients who took part in this study. This work was supported by Cancer Research UK (grants: C5047/A7357, C1287/A10118, C1287/A5260, C5047/A3354, C5047/A10692, C16913/A6135 and C16913/A6835). We would also like to thank the following for funding support: Prostate Research Campaign UK (now Prostate Cancer UK), The Institute of Cancer Research and The Everyman Campaign, The National Cancer Research Network UK, The National Cancer Research Institute (NCRI) UK. We are grateful for support of NIHR funding to the NIHR Biomedical Research Centre at The Institute of Cancer Research and The Royal Marsden NHS Foundation Trust. The MEC was supported by NIH grants CA63464, CA54281 and CA098758.&nbsp;

  Study phs001120

• OncoArray: Prostate Cancer

  Original description of the study: From ELLIPSE (linked to the PRACTICAL consortium), we contributed ~78,000 SNPs to the OncoArray. A large fraction of the content was derived from the GWAS meta-analyses in European ancestry populations (overall and aggressive disease; ~27K SNPs). We also selected just over 10,000 SNPs from the meta-analyses in the non-European populations, with a majority of these SNPs coming from the analysis of overall prostate cancer in African ancestry populations as well as from the multiethnic meta-analysis. A substantial fraction of SNPs (~28,000) were also selected for fine-mapping of 53 loci not included in the common fine-mapping regions (tagging at r2&#62;0.9 across &#177;500kb regions). We also selected a few thousand SNPs related with PSA levels and/or disease survival as well as SNPs from candidate lists provided by study collaborators, as well as from meta-analyses of exome SNP chip data from the Multiethnic Cohort and UK studies. The Contributing Studies: Aarhus: Hospital-based, Retrospective, Observational. Source of cases: Patients treated for prostate adenocarcinoma at Department of Urology, Aarhus University Hospital, Skejby (Aarhus, Denmark). Source of controls: Age-matched males treated for myocardial infarction or undergoing coronary angioplasty, but with no prostate cancer diagnosis based on information retrieved from the Danish Cancer Register and the Danish Cause of Death Register. AHS: Nested case-control study within prospective cohort. Source of cases: linkage to cancer registries in study states. Source of controls: matched controls from cohort ATBC: Prospective, nested case-control. Source of cases: Finnish male smokers aged 50-69 years at baseline. Source of controls: Finnish male smokers aged 50-69 years at baseline BioVu: Cases identified in a biobank linked to electronic health records. Source of cases: A total of 214 cases were identified in the VUMC de-identified electronic health records database (the Synthetic Derivative) and shipped to USC for genotyping in April 2014. The following criteria were used to identify cases: Age 18 or greater; male; African Americans (Black) only. Note that African ancestry is not self-identified, it is administratively or third-party assigned (which has been shown to be highly correlated with genetic ancestry for African Americans in BioVU; see references). Source of controls: Controls were identified in the de-identified electronic health record. Unfortunately, they were not age matched to the cases, and therefore cannot be used for this study. Canary PASS: Prospective, Multi-site, Observational Active Surveillance Study. Source of cases: clinic based from Beth Israel Deaconness Medical Center, Eastern Virginia Medical School, University of California at San Francisco, University of Texas Health Sciences Center San Antonio, University of Washington, VA Puget Sound. Source of controls: N/A CCI: Case series, Hospital-based. Source of cases: Cases identified through clinics at the Cross Cancer Institute. Source of controls: N/A CerePP French Prostate Cancer Case-Control Study (ProGene): Case-Control, Prospective, Observational, Hospital-based. Source of cases: Patients, treated in French departments of Urology, who had histologically confirmed prostate cancer. Source of controls: Controls were recruited as participating in a systematic health screening program and found unaffected (normal digital rectal examination and total PSA &#60; 4 ng/ml, or negative biopsy if PSA &#62; 4 ng/ml). COH: hospital-based cases and controls from outside. Source of cases: Consented prostate cancer cases at City of Hope. Source of controls: Consented unaffected males that were part of other studies where they consented to have their DNA used for other research studies. COSM: Population-based cohort. Source of cases: General population. Source of controls: General population CPCS1: Case-control - Denmark. Source of cases: Hospital referrals. Source of controls: Copenhagen General Population Study CPCS2: Source of cases: Hospital referrals. Source of controls: Copenhagen General Population Study CPDR: Retrospective cohort. Source of cases: Walter Reed National Military Medical Center. Source of controls: Walter Reed National Military Medical Center ACS_CPS-II: Nested case-control derived from a prospective cohort study. Source of cases: Identified through self-report on follow-up questionnaires and verified through medical records or cancer registries, identified through cancer registries or the National Death Index (with prostate cancer as the primary cause of death). Source of controls: Cohort participants who were cancer-free at the time of diagnosis of the matched case, also matched on age (&#177;6 mo) and date of biospecimen donation (&#177;6 mo). EPIC: Case-control - Germany, Greece, Italy, Netherlands, Spain, Sweden, UK. Source of cases: Identified through record linkage with population-based cancer registries in Italy, the Netherlands, Spain, Sweden and UK. In Germany and Greece, follow-up is active and achieved through checks of insurance records and cancer and pathology registries as well as via self-reported questionnaires; self-reported incident cancers are verified through medical records. Source of controls: Cohort participants without a diagnosis of cancer EPICAP: Case-control, Population-based, ages less than 75 years at diagnosis, H&#233;rault, France. Source of cases: Prostate cancer cases in all public hospitals and private urology clinics of d&#233;partement of H&#233;rault in France. Cases validation by the H&#233;rault Cancer Registry. Source of controls: Population-based controls, frequency age matched (5-year groups). Quotas by socio-economic status (SES) in order to obtain a distribution by SES among controls identical to the SES distribution among general population men, conditionally to age. ERSPC: Population-based randomized trial. Source of cases: Men with PrCa from screening arm ERSPC Rotterdam. Source of controls: Men without PrCa from screening arm ERSPC Rotterdam ESTHER: Case-control, Prospective, Observational, Population-based. Source of cases: Prostate cancer cases in all hospitals in the state of Saarland, from 2001-2003. Source of controls: Random sample of participants from routine health check-up in Saarland, in 2000-2002 FHCRC: Population-based, case-control, ages 35-74 years at diagnosis, King County, WA, USA. Source of cases: Identified through the Seattle-Puget Sound SEER cancer registry. Source of controls: Randomly selected, age-frequency matched residents from the same county as cases Gene-PARE: Hospital-based. Source of cases: Patients that received radiotherapy for treatment of prostate cancer. Source of controls: n/a Hamburg-Zagreb: Hospital-based, Prospective. Source of cases: Prostate cancer cases seen at the Department of Oncology, University Hospital Center Zagreb, Croatia. Source of controls: Population-based (Croatia), healthy men, older than 50, with no medical record of cancer, and no family history of cancer (1st &#38; 2nd degree relatives) HPFS: Nested case-control. Source of cases: Participants of the HPFS cohort. Source of controls: Participants of the HPFS cohort IMPACT: Observational. Source of cases: Carriers and non-carriers (with a known mutation in the family) of the BRCA1 and BRCA2 genes, aged between 40 and 69, who are undergoing prostate screening with annual PSA testing. This cohort has been diagnosed with prostate cancer during the study. Source of controls: Carriers and non-carriers (with a known mutation in the family) of the BRCA1 and BRCA2 genes, aged between 40 and 69, who are undergoing prostate screening with annual PSA testing. This cohort has not been diagnosed with prostate cancer during the study. IPO-Porto: Hospital-based. Source of cases: Early onset and/or familial prostate cancer. Source of controls: Blood donors Karuprostate: Case-control, Retrospective, Population-based. Source of cases: From FWI (Guadeloupe): 237 consecutive incident patients with histologically confirmed prostate cancer attending public and private urology clinics; From Democratic Republic of Congo: 148 consecutive incident patients with histologically confirmed prostate cancer attending the University Clinic of Kinshasa. Source of controls: From FWI (Guadeloupe): 277 controls recruited from men participating in a free systematic health screening program open to the general population; From Democratic Republic of Congo: 134 controls recruited from subjects attending the University Clinic of Kinshasa KULEUVEN: Hospital-based, Prospective, Observational. Source of cases: Prostate cancer cases recruited at the University Hospital Leuven. Source of controls: Healthy males with no history of prostate cancer recruited at the University Hospitals, Leuven. LAAPC: Subjects were participants in a population-based case-control study of aggressive prostate cancer conducted in Los Angeles County. Cases were identified through the Los Angeles County Cancer Surveillance Program rapid case ascertainment system. Eligible cases included African American, Hispanic, and non-Hispanic White men diagnosed with a first primary prostate cancer between January 1, 1999 and December 31, 2003. Eligible cases also had (a) prostatectomy with documented tumor extension outside the prostate, (b) metastatic prostate cancer in sites other than prostate, (c) needle biopsy of the prostate with Gleason grade &#8805;8, or (d) needle biopsy with Gleason grade 7 and tumor in more than two thirds of the biopsy cores. Eligible controls were men never diagnosed with prostate cancer, living in the same neighborhood as a case, and were frequency matched to cases on age (&#177; 5 y) and race/ethnicity. Controls were identified by a neighborhood walk algorithm, which proceeds through an obligatory sequence of adjacent houses or residential units beginning at a specific residence that has a specific geographic relationship to the residence where the case lived at diagnosis. Malaysia: Case-control. Source of cases: Patients attended the outpatient urology or uro-onco clinic at University Malaya Medical Center. Source of controls: Population-based, age matched (5-year groups), ascertained through electoral register, Subang Jaya, Selangor, Malaysia MCC-Spain: Case-control. Source of cases: Identified through the urology departments of the participating hospitals. Source of controls: Population-based, frequency age and region matched, ascertained through the rosters of the primary health care centers MCCS: Nested case-control, Melbourne, Victoria. Source of cases: Identified by linkage to the Victorian Cancer Registry. Source of controls: Cohort participants without a diagnosis of cancer MD Anderson: Participants in this study were identified from epidemiological prostate cancer studies conducted at the University of Texas MD Anderson Cancer Center in the Houston Metropolitan area. Cases were accrued in the Houston Medical Center and were not restricted with respect to Gleason score, stage or PSA. Controls were identified via random-digit-dialing or among hospital visitors and they were frequency matched to cases on age and race. Lifestyle, demographic, and family history data were collected using a standardized questionnaire. MDACC_AS: A prospective cohort study. Source of cases: Men with clinically organ-confined prostate cancer meeting eligibility criteria for a prospective cohort study of active surveillance at MD Anderson Cancer Center. Source of controls: N/A MEC: The Multiethnic Cohort (MEC) is comprised of over 215,000 men and women recruited from Hawaii and the Los Angeles area between 1993 and 1996. Between 1995 and 2006, over 65,000 blood samples were collected from participants for genetic analyses. To identify incident cancer cases, the MEC was cross-linked with the population-based Surveillance, Epidemiology and End Results (SEER) registries in California and Hawaii, and unaffected cohort participants with blood samples were selected as controls MIAMI (WFPCS): Prostate cancer cases and controls were recruited from the Departments of Urology and Internal Medicine of the Wake Forest University School of Medicine using sequential patient populations as described previously (PMID:15342424). All study subjects received a detailed description of the study protocol and signed their informed consent, as approved by the medical center&#39;s Institutional Review Board. The general eligibility criteria were (i) able to comprehend informed consent and (ii) without previously diagnosed cancer. The exclusion criteria were (i) clinical diagnosis of autoimmune diseases; (ii) chronic inflammatory conditions; and (iii) infections within the past 6 weeks. Blood samples were collected from all subjects. MOFFITT: Hospital-based. Source of cases: clinic based from Moffitt Cancer Center. Source of controls: Moffitt Cancer Center affiliated Lifetime cancer screening center NMHS: Case-control, clinic based, Nashville TN. Source of cases: All urology clinics in Nashville, TN. Source of controls: Men without prostate cancer at prostate biopsy. PCaP: The North Carolina-Louisiana Prostate Cancer Project (PCaP) is a multidisciplinary population-based case-only study designed to address racial differences in prostate cancer through a comprehensive evaluation of social, individual and tumor level influences on prostate cancer aggressiveness. PCaP enrolled approximately equal numbers of African Americans and Caucasian Americans with newly-diagnosed prostate cancer from North Carolina (42 counties) and Louisiana (30 parishes) identified through state tumor registries. African American PCaP subjects with DNA, who agreed to future use of specimens for research, participated in OncoArray analysis. PCMUS: Case-control - Sofia, Bulgaria. Source of cases: Patients of Clinic of Urology, Alexandrovska University Hospital, Sofia, Bulgaria, PrCa histopathologically confirmed. Source of controls: 72 patients with verified BPH and PSA&#60;3,5; 78 healthy controls from the MMC Biobank, no history of PrCa PHS: Nested case-control. Source of cases: Participants of the PHS1 trial/cohort. Source of controls: Participants of the PHS1 trial/cohort PLCO: Nested case-control. Source of cases: Men with a confirmed diagnosis of prostate cancer from the PLCO Cancer Screening Trial. Source of controls: Controls were men enrolled in the PLCO Cancer Screening Trial without a diagnosis of cancer at the time of case ascertainment. Poland: Case-control. Source of cases: men with unselected prostate cancer, diagnosed in north-western Poland at the University Hospital in Szczecin. Source of controls: cancer-free men from the same population, taken from the healthy adult patients of family doctors in the Szczecin region PROCAP: Population-based, Retrospective, Observational. Source of cases: Cases were ascertained from the National Prostate Cancer Register of Sweden Follow-Up Study, a retrospective nationwide cohort study of patients with localized prostate cancer. Source of controls: Controls were selected among men referred for PSA testing in laboratories in Stockholm County, Sweden, between 2010 and 2012. PROGReSS: Hospital-based, Prospective, Observational. Source of cases: Prostate cancer cases from the Hospital Cl&#237;nico Universitario de Santiago de Compostela, Galicia, Spain. Source of controls: Cancer-free men from the same population ProMPT: A study to collect samples and data from subjects with and without prostate cancer. Retrospective, Experimental. Source of cases: Subjects attending outpatient clinics in hospitals. Source of controls: Subjects attending outpatient clinics in hospitals ProtecT: Trial of treatment. Samples taken from subjects invited for PSA testing from the community at nine centers across United Kingdom. Source of cases: Subjects who have a proven diagnosis of prostate cancer following testing. Source of controls: Identified through invitation of subjects in the community. PROtEuS: Case-control, population-based. Source of cases: All new histologically-confirmed cases, aged less or equal to 75 years, diagnosed between 2005 and 2009, actively ascertained across Montreal French hospitals. Source of controls: Randomly selected from the Provincial electoral list of French-speaking men between 2005 and 2009, from the same area of residence as cases and frequency-matched on age. QLD: Case-control. Source of cases: A longitudinal cohort study (Prostate Cancer Supportive Care and Patient Outcomes Project: ProsCan) conducted in Queensland, through which men newly diagnosed with prostate cancer from 26 private practices and 10 public hospitals were directly referred to ProsCan at the time of diagnosis by their treating clinician (age range 43-88 years). All cases had histopathologically confirmed prostate cancer, following presentation with an abnormal serum PSA and/or lower urinary tract symptoms. Source of controls: Controls comprised healthy male blood donors with no personal history of prostate cancer, recruited through (i) the Australian Red Cross Blood Services in Brisbane (age range 19-76 years) and (ii) the Australian Electoral Commission (AEC) (age and post-code/ area matched to ProsCan, age range 54-90 years). RAPPER: Multi-centre, hospital based blood sample collection study in patients enrolled in clinical trials with prospective collection of radiotherapy toxicity data. Source of cases: Prostate cancer patients enrolled in radiotherapy trials: CHHiP, RT01, Dose Escalation, RADICALS, Pelvic IMRT, PIVOTAL. Source of controls: N/A SABOR: Prostate Cancer Screening Cohort. Source of cases: Men &#62;45 yrs of age participating in annual PSA screening. Source of controls: Males participating in annual PSA prostate cancer risk evaluations (funded by NCI biomarkers discovery and validation grant), recruited through University of Texas Health Science Center at San Antonio and affiliated sites or through study advertisements, enrolment open to the community SCCS: Case-control in cohort, Southeastern USA. Prospective, Observational, Population-based. Source of cases: SCCS entry population. Source of controls: SCCS entry population SCPCS: Population-based, Retrospective, Observational. Source of cases: South Carolina Central Cancer Registry. Source of controls: Health Care Financing Administration beneficiary file SEARCH: Case-control - East Anglia, UK. Source of cases: Men &#60; 70 years of age registered with prostate cancer at the population-based cancer registry, Eastern Cancer Registration and Information Centre, East Anglia, UK. Source of controls: Men attending general practice in East Anglia with no known prostate cancer diagnosis, frequency matched to cases by age and geographic region SNP_Prostate_Ghent: Hospital-based, Retrospective, Observational. Source of cases: Men treated with IMRT as primary or postoperative treatment for prostate cancer at the Ghent University Hospital between 2000 and 2010. Source of controls: Employees of the University hospital and members of social activity clubs, without a history of any cancer. SPAG: Hospital-based, Retrospective, Observational. Source of cases: Guernsey. Source of controls: Guernsey STHM2: Population-based, Retrospective, Observational. Source of cases: Cases were selected among men referred for PSA testing in laboratories in Stockholm County, Sweden, between 2010 and 2012. Source of controls: Controls were selected among men referred for PSA testing in laboratories in Stockholm County, Sweden, between 2010 and 2012. PCPT: Case-control from a randomized clinical trial. Source of cases: Randomized clinical trial. Source of controls: Randomized clinical trial SELECT: Case-cohort from a randomized clinical trial. Source of cases: Randomized clinical trial. Source of controls: Randomized clinical trial TAMPERE: Case-control - Finland, Retrospective, Observational, Population-based. Source of cases: Identified through linkage to the Finnish Cancer Registry and patient records; and the Finnish arm of the ERSPC study. Source of controls: Cohort participants without a diagnosis of cancer UGANDA: Uganda Prostate Cancer Study: Uganda is a case-control study of prostate cancer in Kampala Uganda that was initiated in 2011. Men with prostate cancer were enrolled from the Urology unit at Mulago Hospital and men without prostate cancer (i.e. controls) were enrolled from other clinics (i.e. surgery) at the hospital. UKGPCS: ICR, UK. Source of cases: Cases identified through clinics at the Royal Marsden hospital and nationwide NCRN hospitals. Source of controls: Ken Muir&#39;s control- 2000 ULM: Case-control - Germany. Source of cases: familial cases (n=162): identified through questionnaires for family history by collaborating urologists all over Germany; sporadic cases (n=308): prostatectomy series performed in the Clinic of Urology Ulm between 2012 and 2014. Source of controls: age-matched controls (n=188): age-matched men without prostate cancer and negative family history collected in hospitals of Ulm WUGS/WUPCS: Cases Series, USA. Source of cases: Identified through clinics at Washington University in St. Louis. Source of controls: Men diagnosed and managed with prostate cancer in University based clinic. Acknowledgement Statements: Aarhus: This study was supported by the Danish Strategic Research Council (now Innovation Fund Denmark) and the Danish Cancer Society. The Danish Cancer Biobank (DCB) is acknowledged for biological material. AHS: This work was supported by the Intramural Research Program of the NIH, National Cancer Institute, Division of Cancer Epidemiology and Genetics (Z01CP010119). ATBC: This research was supported in part by the Intramural Research Program of the NIH and the National Cancer Institute. Additionally, this research was supported by U.S. Public Health Service contracts N01-CN-45165, N01-RC-45035, N01-RC-37004, HHSN261201000006C, and HHSN261201500005C from the National Cancer Institute, Department of Health and Human Services. BioVu: The dataset(s) used for the analyses described were obtained from Vanderbilt University Medical Center&#39;s BioVU which is supported by institutional funding and by the National Center for Research Resources, Grant UL1 RR024975-01 (which is now at the National Center for Advancing Translational Sciences, Grant 2 UL1 TR000445-06). Canary PASS: PASS was supported by Canary Foundation and the National Cancer Institute&#39;s Early Detection Research Network (U01 CA086402) CCI: This work was awarded by Prostate Cancer Canada and is proudly funded by the Movember Foundation - Grant # D2013-36.The CCI group would like to thank David Murray, Razmik Mirzayans, and April Scott for their contribution to this work. CerePP French Prostate Cancer Case-Control Study (ProGene): None reported COH: SLN is partially supported by the Morris and Horowitz Families Endowed Professorship COSM: The Swedish Research Council, the Swedish Cancer Foundation CPCS1 &#38; CPCS2: Department of Clinical Biochemistry, Herlev and Gentofte Hospital, Copenhagen University Hospital, Herlev Ringvej 75, DK-2730 Herlev, DenmarkCPCS1 would like to thank the participants and staff of the Copenhagen General Population Study for their important contributions. CPDR: Uniformed Services University for the Health Sciences HU0001-10-2-0002 (PI: David G. McLeod, MD) CPS-II: The American Cancer Society funds the creation, maintenance, and updating of the Cancer Prevention Study II cohort. CPS-II thanks the participants and Study Management Group for their invaluable contributions to this research. We would also like to acknowledge the contribution to this study from central cancer registries supported through the Centers for Disease Control and Prevention National Program of Cancer Registries, and cancer registries supported by the National Cancer Institute Surveillance Epidemiology and End Results program. EPIC: The coordination of EPIC is financially supported by the European Commission (DG-SANCO) and the International Agency for Research on Cancer. The national cohorts are supported by the Danish Cancer Society (Denmark); the Deutsche Krebshilfe, Deutsches Krebsforschungszentrum and Federal Ministry of Education and Research (Germany); the Hellenic Health Foundation, Greek Ministry of Health; Greek Ministry of Education (Greece); the Italian Association for Research on Cancer (AIRC) and National Research Council (Italy); the Dutch Ministry of Public Health, Welfare and Sports (VWS), Netherlands Cancer Registry (NKR), LK Research Funds, Dutch Prevention Funds, Dutch ZON (Zorg Onderzoek Nederland), World Cancer Research Fund (WCRF); the Statistics Netherlands (The Netherlands); the Health Research Fund (FIS), Regional Governments of Andaluc&#237;a, Asturias, Basque Country, Murcia and Navarra, Spanish Ministry of Health ISCIII RETIC (RD06/0020), Red de Centros RCESP, C03/09 (Spain); the Swedish Cancer Society, Swedish Scientific Council and Regional Government of Sk&#229;ne and V&#228;sterbotten, Fundacion Federico SA (Sweden); the Cancer Research UK, Medical Research Council (United Kingdom). EPICAP: The EPICAP study was supported by grants from Ligue Nationale Contre le Cancer, Ligue d&#233;partementale du Val de Marne; Fondation de France; Agence Nationale de s&#233;curit&#233; sanitaire de l&#39;alimentation, de l&#39;environnement et du travail (ANSES). The EPICAP study group would like to thank all urologists, Antoinette Anger and Hasina Randrianasolo (study monitors), Anne-Laure Astolfi, Coline Bernard, Oriane Noyer, Marie-H&#233;l&#232;ne De Campo, Sandrine Margaroline, Louise N&#39;Diaye, and Sabine Perrier-Bonnet (Clinical Research nurses). ERSPC: This study was supported by the DutchCancerSociety (KWF94-869,98-1657,2002-277,2006-3518, 2010-4800), The Netherlands Organisation for Health Research and Development (ZonMW-002822820, 22000106, 50-50110-98-311, 62300035), The Dutch Cancer Research Foundation (SWOP), and an unconditional grant from Beckman-Coulter-HybritechInc. ESTHER: The ESTHER study was supported by a grant from the Baden W&#252;rttemberg Ministry of Science, Research and Arts. The ESTHER group would like to thank Hartwig Ziegler, Sonja Wolf, Volker Hermann, Heiko M&#252;ller, Karina Dieffenbach, Katja Butterbach for valuable contributions to the study. FHCRC: The FHCRC studies were supported by grants R01-CA056678, R01-CA082664, and R01-CA092579 from the US National Cancer Institute, National Institutes of Health, with additional support from the Fred Hutchinson Cancer Research Center. FHCRC would like to thank all the men who participated in these studies. Gene-PARE: The Gene-PARE study was supported by grants 1R01CA134444 from the U.S. National Institutes of Health, PC074201 and W81XWH-15-1-0680 from the Prostate Cancer Research Program of the Department of Defense and RSGT-05-200-01-CCE from the American Cancer Society. Hamburg-Zagreb: None reported HPFS: The Health Professionals Follow-up Study was supported by grants UM1CA167552, CA133891, CA141298, and P01CA055075. HPFS are grateful to the participants and staff of the Physicians&#39; Health Study and Health Professionals Follow-Up Study for their valuable contributions, as well as the following state cancer registries for their help: AL, AZ, AR, CA, CO, CT, DE, FL, GA, ID, IL, IN, IA, KY, LA, ME, MD, MA, MI, NE, NH, NJ, NY, NC, ND, OH, OK, OR, PA, RI, SC, TN, TX, VA, WA, and WY. IMPACT: The IMPACT study was funded by The Ronald and Rita McAulay Foundation, CR-UK Project grant (C5047/A1232), Cancer Australia, AICR Netherlands A10-0227, Cancer Australia and Cancer Council Tasmania, NIHR, EU Framework 6, Cancer Councils of Victoria and South Australia, and Philanthropic donation to Northshore University Health System. We acknowledge support from the National Institute for Health Research (NIHR) to the Biomedical Research Centre at The Institute of Cancer Research and Royal Marsden Foundation NHS Trust. IMPACT acknowledges the IMPACT study steering committee, collaborating centres, and participants. IPO-Porto: The IPO-Porto study was funded by Funda&#231;&#228;o para a Ci&#234;ncia e a Tecnologia (FCT; UID/DTP/00776/2013 and PTDC/DTP-PIC/1308/2014) and by IPO-Porto Research Center (CI-IPOP-16-2012 and CI-IPOP-24-2015). MC and MPS are research fellows from Liga Portuguesa Contra o Cancro, N&#250;cleo Regional do Norte. SM is a research fellow from FCT (SFRH/BD/71397/2010). IPO-Porto would like to express our gratitude to all patients and families who have participated in this study. Karuprostate: The Karuprostate study was supported by the the Frech National Health Directorate and by the Association pour la Recherche sur les Tumeurs de la ProstateKarusprostate thanks S&#233;verine Ferdinand. KULEUVEN: F.C. and S.J. are holders of grants from FWO Vlaanderen (G.0684.12N and G.0830.13N), the Belgian federal government (National Cancer Plan KPC_29_023), and a Concerted Research Action of the KU Leuven (GOA/15/017). TVDB is holder of a doctoral fellowship of the FWO. LAAPC: This study was funded by grant R01CA84979 (to S.A. Ingles) from the National Cancer Institute, National Institutes of Health. Malaysia: The study was funded by the University Malaya High Impact Research Grant (HIR/MOHE/MED/35). Malaysia thanks all associates in the Urology Unit, University of Malaya, Cancer Research Initiatives Foundation (CARIF) and the Malaysian Men&#39;s Health Initiative (MMHI). MCCS: MCCS cohort recruitment was funded by VicHealth and Cancer Council Victoria. The MCCS was further supported by Australian NHMRC grants 209057, 251553, and 504711, and by infrastructure provided by Cancer Council Victoria. Cases and their vital status were ascertained through the Victorian Cancer Registry (VCR) and the Australian Institute of Health and Welfare (AIHW), including the National Death Index and the Australian Cancer Database. MCC-Spain: The study was partially funded by the Accion Transversal del Cancer, approved on the Spanish Ministry Council on the 11th October 2007, by the Instituto de Salud Carlos III-FEDER (PI08/1770, PI09/00773-Cantabria, PI11/01889-FEDER, PI12/00265, PI12/01270, and PI12/00715), by the Fundaci&#243;n Marqu&#233;s de Valdecilla (API 10/09), by the Spanish Association Against Cancer (AECC) Scientific Foundation and by the Catalan Government DURSI grant 2009SGR1489. Samples: Biological samples were stored at the Parc de Salut MAR Biobank (MARBiobanc; Barcelona) which is supported by Instituto de Salud Carlos III FEDER (RD09/0076/00036). Also sample collection was supported by the Xarxa de Bancs de Tumors de Catalunya sponsored by Pla Director d&#39;Oncologia de Catalunya (XBTC). MCC-Spain acknowledges the contribution from Esther Gracia-Lavedan in preparing the data. We thank all the subjects who participated in the study and all MCC-Spain collaborators. MD Anderson: Prostate Cancer Case-Control Studies at MD Anderson (MDA) supported by grants CA68578, ES007784, DAMD W81XWH-07-1-0645, and CA140388. MDACC_AS: None reported MEC: Funding provided by NIH grant U19CA148537 and grant U01CA164973. MIAMI (WFPCS): ACS MOFFITT: The Moffitt group was supported by the US National Cancer Institute (R01CA128813, PI: J.Y. Park). NMHS: Funding for the Nashville Men&#39;s Health Study (NMHS) was provided by the National Institutes of Health Grant numbers: RO1CA121060. PCaP only data: The North Carolina - Louisiana Prostate Cancer Project (PCaP) is carried out as a collaborative study supported by the Department of Defense contract DAMD 17-03-2-0052. For HCaP-NC follow-up data: The Health Care Access and Prostate Cancer Treatment in North Carolina (HCaP-NC) study is carried out as a collaborative study supported by the American Cancer Society award RSGT-08-008-01-CPHPS. For studies using both PCaP and HCaP-NC follow-up data please use: The North Carolina - Louisiana Prostate Cancer Project (PCaP) and the Health Care Access and Prostate Cancer Treatment in North Carolina (HCaP-NC) study are carried out as collaborative studies supported by the Department of Defense contract DAMD 17-03-2-0052 and the American Cancer Society award RSGT-08-008-01-CPHPS, respectively. For any PCaP data, please include: The authors thank the staff, advisory committees and research subjects participating in the PCaP study for their important contributions. For studies using PCaP DNA/genotyping data, please include: We would like to acknowledge the UNC BioSpecimen Facility and LSUHSC Pathology Lab for our DNA extractions, blood processing, storage and sample disbursement (https://genome.unc.edu/bsp). For studies using PCaP tissue, please include: We would like to acknowledge the RPCI Department of Urology Tissue Microarray and Immunoanalysis Core for our tissue processing, storage and sample disbursement. For studies using HCaP-NC follow-up data, please use: The Health Care Access and Prostate Cancer Treatment in North Carolina (HCaP-NC) study is carried out as a collaborative study supported by the American Cancer Society award RSGT-08-008-01-CPHPS. The authors thank the staff, advisory committees and research subjects participating in the HCaP-NC study for their important contributions. For studies that use both PCaP and HCaP-NC, please use: The authors thank the staff, advisory committees and research subjects participating in the PCaP and HCaP-NC studies for their important contributions. PCMUS: The PCMUS study was supported by the Bulgarian National Science Fund, Ministry of Education and Science (contract DOO-119/2009; DUNK01/2-2009; DFNI-B01/28/2012) with additional support from the Science Fund of Medical University - Sofia (contract 51/2009; 8I/2009; 28/2010). PHS: The Physicians&#39; Health Study was supported by grants CA34944, CA40360, CA097193, HL26490, and HL34595. PHS members are grateful to the participants and staff of the Physicians&#39; Health Study and Health Professionals Follow-Up Study for their valuable contributions, as well as the following state cancer registries for their help: AL, AZ, AR, CA, CO, CT, DE, FL, GA, ID, IL, IN, IA, KY, LA, ME, MD, MA, MI, NE, NH, NJ, NY, NC, ND, OH, OK, OR, PA, RI, SC, TN, TX, VA, WA, and WY. PLCO: This PLCO study was supported by the Intramural Research Program of the Division of Cancer Epidemiology and Genetics, National Cancer Institute, NIHPLCO thanks Drs. Christine Berg and Philip Prorok, Division of Cancer Prevention at the National Cancer Institute, the screening center investigators and staff of the PLCO Cancer Screening Trial for their contributions to the PLCO Cancer Screening Trial. We thank Mr. Thomas Riley, Mr. Craig Williams, Mr. Matthew Moore, and Ms. Shannon Merkle at Information Management Services, Inc., for their management of the data and Ms. Barbara O&#39;Brien and staff at Westat, Inc. for their contributions to the PLCO Cancer Screening Trial. We also thank the PLCO study participants for their contributions to making this study possible. Poland: None reported PROCAP: PROCAP was supported by the Swedish Cancer Foundation (08-708, 09-0677). PROCAP thanks and acknowledges all of the participants in the PROCAP study. We thank Carin Cavalli-Bj&#246;rkman and Ami R&#246;nnberg Karlsson for their dedicated work in the collection of data. Michael Broms is acknowledged for his skilful work with the databases. KI Biobank is acknowledged for handling the samples and for DNA extraction. We acknowledge The NPCR steering group: P&#228;r Stattin (chair), Anders Widmark, Stefan Karlsson, Magnus T&#246;rnblom, Jan Adolfsson, Anna Bill-Axelson, Ove Andr&#233;n, David Robinson, Bill Pettersson, Jonas Hugosson, Jan-Erik Damber, Ola Bratt, G&#246;ran Ahlgren, Lars Egevad, and Roy Ehrnstr&#246;m. PROGReSS: The PROGReSS study is founded by grants from the Spanish Ministry of Health (INT15/00070; INT16/00154; FIS PI10/00164, FIS PI13/02030; FIS PI16/00046); the Spanish Ministry of Economy and Competitiveness (PTA2014-10228-I), and Fondo Europeo de Desarrollo Regional (FEDER 2007-2013). ProMPT: Founded by CRUK, NIHR, MRC, Cambride Biomedical Research Centre ProtecT: Founded by NIHR. ProtecT and ProMPT would like to acknowledge the support of The University of Cambridge, Cancer Research UK. Cancer Research UK grants (C8197/A10123) and (C8197/A10865) supported the genotyping team. We would also like to acknowledge the support of the National Institute for Health Research which funds the Cambridge Bio-medical Research Centre, Cambridge, UK. We would also like to acknowledge the support of the National Cancer Research Prostate Cancer: Mechanisms of Progression and Treatment (PROMPT) collaborative (grant code G0500966/75466) which has funded tissue and urine collections in Cambridge. We are grateful to staff at the Welcome Trust Clinical Research Facility, Addenbrooke&#39;s Clinical Research Centre, Cambridge, UK for their help in conducting the ProtecT study. We also acknowledge the support of the NIHR Cambridge Biomedical Research Centre, the DOH HTA (ProtecT grant), and the NCRI/MRC (ProMPT grant) for help with the bio-repository. The UK Department of Health funded the ProtecT study through the NIHR Health Technology Assessment Programme (projects 96/20/06, 96/20/99). The ProtecT trial and its linked ProMPT and CAP (Comparison Arm for ProtecT) studies are supported by Department of Health, England; Cancer Research UK grant number C522/A8649, Medical Research Council of England grant number G0500966, ID 75466, and The NCRI, UK. The epidemiological data for ProtecT were generated though funding from the Southwest National Health Service Research and Development. DNA extraction in ProtecT was supported by USA Dept of Defense award W81XWH-04-1-0280, Yorkshire Cancer Research and Cancer Research UK. The authors would like to acknowledge the contribution of all members of the ProtecT study research group. The views and opinions expressed therein are those of the authors and do not necessarily reflect those of the Department of Health of England. The bio-repository from ProtecT is supported by the NCRI (ProMPT) Prostate Cancer Collaborative and the Cambridge BMRC grant from NIHR. We thank the National Institute for Health Research, Hutchison Whampoa Limited, the Human Research Tissue Bank (Addenbrooke&#39;s Hospital), and Cancer Research UK. PROtEuS: PROtEuS was supported financially through grants from the Canadian Cancer Society (13149, 19500, 19864, 19865) and the Cancer Research Society, in partnership with the Minist&#232;re de l&#39;enseignement sup&#233;rieur, de la recherche, de la science et de la technologie du Qu&#233;bec, and the Fonds de la recherche du Qu&#233;bec - Sant&#233;.PROtEuS would like to thank its collaborators and research personnel, and the urologists involved in subjects recruitment. We also wish to acknowledge the special contribution made by Ann Hsing and Anand Chokkalingam to the conception of the genetic component of PROtEuS. QLD: The QLD research is supported by The National Health and Medical Research Council (NHMRC) Australia Project Grants (390130, 1009458) and NHMRC Career Development Fellowship and Cancer Australia PdCCRS funding to J Batra. The QLD team would like to acknowledge and sincerely thank the urologists, pathologists, data managers and patient participants who have generously and altruistically supported the QLD cohort. RAPPER: RAPPER is funded by Cancer Research UK (C1094/A11728; C1094/A18504) and Experimental Cancer Medicine Centre funding (C1467/A7286). The RAPPER group thank Rebecca Elliott for project management. SABOR: The SABOR research is supported by NIH/NCI Early Detection Research Network, grant U01 CA0866402-12. Also supported by the Cancer Center Support Grant to the Cancer Therapy and Research Center from the National Cancer Institute (US) P30 CA054174. SCCS: SCCS is funded by NIH grant R01 CA092447, and SCCS sample preparation was conducted at the Epidemiology Biospecimen Core Lab that is supported in part by the Vanderbilt-Ingram Cancer Center (P30 CA68485). Data on SCCS cancer cases used in this publication were provided by the Alabama Statewide Cancer Registry; Kentucky Cancer Registry, Lexington, KY; Tennessee Department of Health, Office of Cancer Surveillance; Florida Cancer Data System; North Carolina Central Cancer Registry, North Carolina Division of Public Health; Georgia Comprehensive Cancer Registry; Louisiana Tumor Registry; Mississippi Cancer Registry; South Carolina Central Cancer Registry; Virginia Department of Health, Virginia Cancer Registry; Arkansas Department of Health, Cancer Registry, 4815 W. Markham, Little Rock, AR 72205. The Arkansas Central Cancer Registry is fully funded by a grant from National Program of Cancer Registries, Centers for Disease Control and Prevention (CDC). Data on SCCS cancer cases from Mississippi were collected by the Mississippi Cancer Registry which participates in the National Program of Cancer Registries (NPCR) of the Centers for Disease Control and Prevention (CDC). The contents of this publication are solely the responsibility of the authors and do not necessarily represent the official views of the CDC or the Mississippi Cancer Registry. SCPCS: SCPCS is funded by CDC grant S1135-19/19, and SCPCS sample preparation was conducted at the Epidemiology Biospecimen Core Lab that is supported in part by the Vanderbilt-Ingram Cancer Center (P30 CA68485). SEARCH: SEARCH is funded by a program grant from Cancer Research UK (C490/A10124) and supported by the UK National Institute for Health Research Biomedical Research Centre at the University of Cambridge. SNP_Prostate_Ghent: The study was supported by the National Cancer Plan, financed by the Federal Office of Health and Social Affairs, Belgium. SPAG: Wessex Medical ResearchHope for Guernsey, MUG, HSSD, MSG, Roger Allsopp STHM2: STHM2 was supported by grants from The Strategic Research Programme on Cancer (StratCan), Karolinska Institutet; the Linn&#233; Centre for Breast and Prostate Cancer (CRISP, number 70867901), Karolinska Institutet; The Swedish Research Council (number K2010-70X-20430-04-3) and The Swedish Cancer Society (numbers 11-0287 and 11-0624); Stiftelsen Johanna Hagstrand och Sigfrid Linn&#233;rs minne; Swedish Council for Working Life and Social Research (FAS), number 2012-0073STHM2 acknowledges the Karolinska University Laboratory, Aleris Medilab, Unilabs and the Regional Prostate Cancer Registry for performing analyses and help to retrieve data. Carin Cavalli-Bj&#246;rkman and Britt-Marie Hune for their enthusiastic work as research nurses. Astrid Bj&#246;rklund for skilful data management. We wish to thank the BBMRI.se biobank facility at Karolinska Institutet for biobank services. PCPT &#38; SELECT are funded by Public Health Service grants U10CA37429 and 5UM1CA182883 from the National Cancer Institute. SWOG and SELECT thank the site investigators and staff and, most importantly, the participants who donated their time to this trial. TAMPERE: The Tampere (Finland) study was supported by the Academy of Finland (251074), The Finnish Cancer Organisations, Sigrid Juselius Foundation, and the Competitive Research Funding of the Tampere University Hospital (X51003). The PSA screening samples were collected by the Finnish part of ERSPC (European Study of Screening for Prostate Cancer). TAMPERE would like to thank Riina Liikanen, Liisa Maeaettaenen and Kirsi Talala for their work on samples and databases. UGANDA: None reported UKGPCS: UKGPCS would also like to thank the following for funding support: The Institute of Cancer Research and The Everyman Campaign, The Prostate Cancer Research Foundation, Prostate Research Campaign UK (now Prostate Action), The Orchid Cancer Appeal, The National Cancer Research Network UK, The National Cancer Research Institute (NCRI) UK. We are grateful for support of NIHR funding to the NIHR Biomedical Research Centre at The Institute of Cancer Research and The Royal Marsden NHS Foundation Trust. UKGPCS should also like to acknowledge the NCRN nurses, data managers, and consultants for their work in the UKGPCS study. UKGPCS would like to thank all urologists and other persons involved in the planning, coordination, and data collection of the study. ULM: The Ulm group received funds from the German Cancer Aid (Deutsche Krebshilfe). WUGS/WUPCS: WUGS would like to thank the following for funding support: The Anthony DeNovi Fund, the Donald C. McGraw Foundation, and the St. Louis Men&#39;s Group Against Cancer.

  Study phs001391

• ARGO_GWAS

  Osteoarthritis (OA) is the most common form of arthritis affecting ~40% of people over the age of 70. OA is characterised by cartilage degeneration in the synovial joints and presents one of the leading causes of chronic disability and impaired quality of life in the developed world.The ARGO study is an ongoing collection of well-phenotyped OA patients undergoing total joint replacement and is based in Greece.

  Study EGAS00001000917

• Multiple_Malignancy_Familial_Comparison

  Patient (who has had multiple malignancies) has previously been found to harbour a pathogenic p53 variant which is probably mosaic. This finding is based on exome sequencing performed elsewhere. In this study we will resequence the locus in question to ascertain whether the variant is indeed mosaic.

  Study EGAS00001000333

• eMERGE Network Imputed GWAS for 41 Phenotypes

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of ten participating sites (Cincinnati Children&#39;s Hospital Medical Center/Boston Children&#39;s Hospital, Children&#39;s Hospital of Philadelphia, Essentia Institute of Rural Health, Marshfield Clinic Research Foundation and Pennsylvania State University, Geisinger Clinic, Group Health Cooperative/University of Washington, Mayo Clinic, Icahn School of Medicine at Mount Sinai, Northwestern University, Vanderbilt University Medical Center) funded by the NHGRI to investigate the use of electronic medical record (EMR) systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 55,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of over forty phenotypes, including Abdominal aortic aneurysm; Ace-Inhibitor/Cough; Attention Deficit Hyperactivity Disorder; Age-related macular disease; Appendicitis; Asthma; Atopic Dermatitis; Autism; Benign Prostatic Hyperplasia; Carotid artery disease as a Quantitative Measure; caMRSA; Cataract; Clostridium difficile colitis; Extreme Obesity; Chronic Kidney Disease; Chronic Kidney Disease and Type 2 Diabetes; Chronic Kidney Disease, Type 2 Diabetes and Hypertension; Colon Polyps; Cardiorespiratory Fitness; Dementia; Diverticulosis; Diabetic retinopathy; Gastroesophageal Reflux Disease; Glaucoma; Height; Heart failure; Hypothyroidism; Lipids; Ocular hypertension; Peripheral Arterial Disease; QRS duration; Red blood cell indices; Remission of Diabetes after ROUX-EN-Y gastric bypass surgery; Resistant hypertension; MACE while on Statins; Type 2 Diabetes; Venous Thromboembolism; White blood cell indices; and Zoster virus infection, as well as using the phenome-wide association study (PheWAS) paradigm to replicate and discover relationships between targeted genotypes with multiple phenotypes. Sites and participants include: Children&#39;s Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children&#39;s Hospital of Philadelphia (CHOP) is a high-throughput, highly automated genotyping and sequencing facility equipped with state-of-the-art genotyping and sequencing platforms. Children who are treated at the Children&#39;s Hospital Healthcare Network and their parents may be eligible to take part in a major initiative to collect more than 100,000 blood samples, covering a wide range of pediatric diseases. A large majority of participants consenting to prospective genomic analyses also consent to analysis of their de-identified electronic medical records (EMRs). EMRs are longitudinal, with a mean duration of 6.5 years. Cincinnati Children&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): Cincinnati Children&#39;s Hospital Medical Center (CCHMC) and Boston Children&#39;s Hospital (BCH) are pediatric institutions dedicated to improving health and welfare of children and to the shared purpose of discovery and practical application of new genomic information to the ordinary care of children. The CCHMC/BCH site has been built on a five-year history of collaboration, particularly in patient electronic record (ERM)-related informatics, the basis of much of eMERGE II. CCHMC and BCH together bring an extraordinary faculty to eMERGE II who are committed to diseases that afflict children, specifically phenotypes that focus upon diseases of children in ways that will leverage the available eMERGE adult GWAS and EMRs to discover meaningful use results. CCHMC/BCH plans to demonstrate real-time execution of phenotypic selection across their two distinct pediatric institutions as a model for ensuring phenotypic standardization and for national scalability. They will also look carefully at parents&#39; responses to results and use of their children&#39;s research results and better understand the factors that influence their decisions about learning incidental findings. In addition to patient and parent perceptions CCHMC/BCH will also explore clinician perceptions of pharmacogenetic research results after EMR integration. Geisinger Health System: A research cohort of adult Geisinger Clinic patients was enrolled from community-based primary care clinics of the Geisinger Health System. Patients were eligible for enrollment if they were a primary care patient of a Geisinger Clinic physician and were scheduled for a non-emergent clinic visit. All participants provided written informed consent and HIPAA authorization. Consenting patients agreed to provide blood samples for broad biomedical research use, and permission to access data in their Geisinger electronic medical record for research. The enrollment rate was 90% of patients approached. The demographics of the cohort approximate those of the Geisinger Clinic outpatient population. Research blood samples were collected during an outpatient clinical phlebotomy encounter. Research blood samples are coded and stored in a central biorepository. Samples are linkable to clinical data in a de-identified manner for research via an IRB-approved data broker process. For genomic analysis, DNA is extracted from EDTA-anticoagulated whole blood. Group Health(GH)/University of Washington (UW): GH participants for the PGx project were enrolled in the eMERGE Network through the Northwest Institute of Genetic Medicine (NWIGM) biorepository, and provided the appropriate consent to receive clinically relevant genetic results (N~6300.) Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in GH&#39;s integrated group practice, and had completed an online Health Risk Appraisal. The selection algorithm was based on several data sources from the EHR at Group Health: 1. Demographics - participants with self-reported race as Asian or African ancestry were prioritized and selected to enrich for non-European ancestry; 2. Diagnosis and procedure codes - participants were selected if found to have a history of hypertension, atrial fibrillation (AF), or congestive heart failure (CHF). Participants with a history of arrhythmia were added if the entire selection algorithm did not generate 900 individuals. We also enriched for participants with EHR evidence of actionable indications related to PGRNSeq genes. Participants were selected if found to have an ICD9 code for malignant hyperthermia, hypertension, atrial fibrillation, congestive heart failure or long QT syndrome (LQTS); 3. Laboratory values - if participants had any laboratory event of creatine kinase (CK) &#62;1000, and were dispensed statins within 6 months of the event, then they were selected; and 4. Medications - participants were excluded if ever on carbamazepine or had a current regimen of warfarin. Essentia Institute of Rural Health, Marshfield Clinic, Pennsylvania State University (Marshfield): The Marshfield Clinic Personalized Medicine Research Project is a population-based biobank in central Wisconsin with more than 20,000 adult subjects who provided written, informed consent to access their medical records and provided a blood sample from which DNA was extracted and plasma and serum stored. In addition to an average of 30 years of medical history data, a questionnaire about environmental exposures, including a detailed food frequency questionnaire, is available to facilitate gene/environment studies. Mayo Clinic: The Mayo biobank is a disease-specific biobank for vascular diseases including peripheral arterial disease (PAD). PAD patients were identified from individuals referred to the non-invasive vascular laboratory for lower extremity arterial evaluation. Since 1997, laboratory findings have been recorded into an electronic database employing an in-house software package for data archiving and retrieval; this data becomes part of the Mayo EMR. Patients referred to the center with suspected PAD undergo a comprehensive non-invasive evaluation including the ankle-brachial index (ABI) - the ratio of blood pressure measured in the upper arms divided by blood pressure measured at the ankles. Controls subjects are identified from patients referred to the Cardiovascular Health Clinic for stress ECG. The prevalence of PAD in patients with normal exercise capacity who do not have inducible ischemia on the stress ECG , was &#60;1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR. Icahn School of Medicine at Mount Sinai School (Mt. Sinai): The Institute for Personalized Medicine (IPM) Biobank Project is a consented, EMR-linked medical care setting biorepository of the Mount Sinai Medical Center (MSMC) drawing from a population of over 70,000 inpatients and 800,000 outpatient visits annually. MSMC serves diverse local communities of upper Manhattan, including Central Harlem (86% African American), East Harlem (88% Hispanic Latino), and Upper East Side (88% Caucasian/white) with broad health disparities. IPM Biobank populations include 28% African American (AA), 38% Hispanic Latino (HL) predominantly of Caribbean origin, 23% Caucasian/White (CW). IPM Biobank disease burden is reflective of health disparities with broad public health impact: average body mass index of 28.9 and frequencies of hypertension (55%), hypercholesterolemia (32%), diabetes (30%), coronary artery disease (25%), chronic kidney disease (23%), among others. Biobank operations are fully integrated in clinical care processes, including direct recruitment from clinical sites, waiting areas and phlebotomy stations by dedicated Biobank recruiters independent of clinical care providers, prior to or following a clinician standard of care visit. Recruitment currently occurs at a broad spectrum of over 30 clinical care sites. Northwestern University: The NUgene Project is a repository with longitudinal medical information from participating patients at affiliated hospitals and outpatient clinics from the Northwestern University Medical Center. Participants&#39; DNA samples are coupled with data from a self-reported questionnaire and continuously updated data from our Electronic Medical Record (EMR) representing actual clinical care events. Northwestern has a state-of-the art, comprehensive inpatient and outpatient EMR system of over 2 million patients. NUgene has broad access to participant data for all outpatient visits as well as inpatient data via a consolidated data warehouse. NUgene participants consent to distribution and use of their coded DNA samples and data for a broad range of genetic research by third-party investigators. Vanderbilt University: BioVU, Vanderbilt&#39;s DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt&#39;s EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations.

  Study phs000888

• Single cell analysis reveals new evolutionary complexity in uveal melanoma

  Uveal melanoma (UM) is a rare eye cancer that is highly aggressive and leads to metastatic death in up to half of patients. Here, we conduct droplet-based single-cell RNA sequencing of 59,915 neoplastic and non-neoplastic cells from 8 primary and 3 metastatic UMs. Single-cell VDJ sequencing of RNA is conducted to determine clonally expanded B/T- cell populations. Single-cell DNA sequencing of 1 primary and 1 metastasis is utilized.

  Study phs001861

• Synthetic - GDI synthetic data

  Synthetic - The Genomic Data Infrastructure (GDI) project is enabling access to genomic and related phenotypic and clinical data across Europe. It is doing this by establishing a federated, sustainable and secure infrastructure to access the data. In support of FAIRness in data sharing, this dataset is made freely available under the Creative Commons Licence (CC-BY). Please ensure the GDI project (funding: EC H2020 under grant agreement number 101081813) is acknowledged.

  Study EGAS50000000678

• EXCEED Study

  EXCEED is a longitudinal population-based cohort which facilitates investigation of genetic, environmental and lifestyle-related determinants of a broad range of diseases and of multiple morbidity through data collected at baseline and via electronic healthcare record linkage. Recruitment has taken place in Leicester, Leicestershire and Rutland since 2013 and is ongoing, with approximately 10,000 participants aged 30-69 to date. The population of Leicester is diverse and additional recruitment from the local South Asian community is ongoing.

  Study EGAS00001003499

• GOSH_Tumour_Embryology_Paediatric_Behjati_RNA_Managed_Access

  The aim of the study is to study thyroid development and function, and how this is altered in Down Syndrome and Thyroid Cancer.

  Study EGAS00001006737

• Gabriella Miller Kids First Pediatric Research Program in Enchondromatoses and Related Malignant Tumors

  Chondrosarcoma is a malignant tumor that originates from cartilaginous cells. It is the third most common primary malignancy of bone after myeloma and osteosarcoma. It accounts for about 20% of bone tumors and is diagnosed in approximately 600 patients each year in the United States. Up to 40% of the chondrosarcomas arise from an enchondroma. Enchondromas are benign, intramedullary cartilaginous tumors of bone. They can be solitary or multiple and are present in &gt;3% of the population. Enchondromatosis refers to a group of diseases characterized by multiple enchondromas including metachondromatosis (MC), Ollier disease (OD), and Maffucci syndrome (MS) among others. All have skeletal abnormalities with or without associated vascular anomalies that can cause severe limb deformities during early childhood. The risk for chondrosarcoma is up to 30% in OD and MS. Currently, the only treatment for patients with these disorders is surgical; there is no effective pharmacologic therapy. The molecular bases of these two conditions is not well understood.

  Study phs001987

• Genomic landscape of malignant peripheral nerve sheath tumor (MPNST)

  Neurofibromatosis type 1 (NF1) is the most common tumor predisposition syndrome, and is associated with an aggressive soft-tissue sarcoma, malignant peripheral nerve sheath tumours (MPNSTs), the greatest cause of morbidity and mortality in people with NF1. The only potentially curative therapy involves surgery which is not always possible. Even therapy with curative intent is associated with poor overall survival for both sporadic and NF1-related MPNSTs. The development of novel therapies has been largely hindered by a lack of understanding of the molecular events underpinning MPNST pathogenesis. This is a comprehensive multi-omic study of MPNST evolution based on whole genome sequencing and transcriptomic data.

  Study EGAS00001006069

• Single_Cell_Targeted_Sequence_Capture

  This study is to ascertain whether it is feasible to extract single cell from a tumour, perform amplification, generate a library and sequence a targeted pulldown.

  Study EGAS00001000435

• NHLBI TOPMed: Early-Onset Atrial Fibrillation in the Estonian Biobank

  The Estonian Biobank is the population-based biobank of the Estonian Genome Centre of University of Tartu. The biobank is conducted according to the Estonian Gene Research Act and all participants have signed broad informed consent. The cohort size is currently 51,535 people from 18 years of age and up.

  Study phs001606

• Metabolism and Genetics of Hypobetalipoproteinemia

  Hypobetalipoproteinemia is characterized by extremely low levels of low-density lipoprotein cholesterol. Familial hypobetalipoproteinemia (FHBL) is a monogenic form of hypobetalipoproteinemia caused by mutations in the APOB gene. There are cases of hypobetalipoproteinemia not caused by mutations in APOB, however. The purpose of this study is to identify novel genetic causes of hypobetalipoproteinemia.

  Study phs000561

• Long read transcriptome of DM1 patients whole blood

  DM1 is characterized by dysregulation of alternative mRNA splicing, to an quantitative as well as qualitative extend that is heterogenous between clinically similar patients. Hundreds of transcripts have been identified that can be misspliced in DM1, and for many of these it is still unclear whether they generate stable proteins in DM1 patients. We generated long-read transcriptome data of DM1 patients whole blood after hemoglobin depletion. Each sample is a mix of 5 patients of varying age.

  Study EGAS50000000196

• Cancer Single Cell Sequencing

  This study is to ascertain whether it is feasible to extract a single cell form a Cancer cell line, amplify it and sequence it.

  Study EGAS00001000003

• Pathogenesis and Immunity in Endemic Burkitt Lymphoma

  This genomic landscape of Burkitt lymphoma represents a multimodal sequencing of tumors and control tissues and individuals to better understand the etiology, and molecular pathogenesis of Burkitt lymphoma including the roles of the associated Plasmodium falciparum malaria and EBV infections. Comprehensive sequencing set includes genomic, transcriptomic, and epigenomic datasets in concert with variable clinical phenotypes and outcome information such as anatomical presentation site, in-hospital survival rates, and EBV genome type. This deposit includes additional small RNA-seq data from endemic BL (eBL) tumors and RNA-sequencing data from sorted NK cell subsets from the peripheral blood of eBL patients. The additional small RNA-seq data are from tumor specimens from 17 eBL cases, of the previously deposited polyA RNA-seq data from 28 eBL cases (phs1282.V1). The additional RNAseq data from Fluorescence-activated cell sorting (FACS) of NK cell subsets, isolated from the peripheral blood of 7 eBL cases. The additional RNAseq data are from eBL tumor samples of 5 eBL cases, BL cell lines established from these tumor samples and also NSG mouse tumors created by implanting the established BL cell lines into NSG mice. The dataset also includes RNAseq data of the NSG mouse tumors after treatment with Rituximab (RIT) and Phosphate buffered saline (PBS). The fifth batch of data includes mRNA-seq from different passages of a single eBL cell line that have variable EBV phenotypes (low passage with lytic EBV and high passage with latent EBV). This batch also includes lytic and latent lymphoblastoid cell line (LCL) clones from a single blood donor generated through infection with the strain of EBV isolated from the aforementioned eBL cell line. For initial transcriptome analysis see: Kaymaz et al. "Comprehensive Transcriptome and Mutational Profiling of Endemic Burkitt Lymphoma Reveals EBV Type-specific Difference." Molecular Cancer Research, 2017, PMID: 28465297. For initial microRNA analysis see: Oduor et al. "Human and Epstein-Barr Virus miRNA Profiling as Predictive Biomarkers for Endemic Burkitt Lymphoma." Frontiers in Microbiology 8, 2017, PMID: 28400759. For initial NK subsets RNA expression analysis see: Forconi et al. "A new hope for CD56negCD16pos NK cells as unconventional cytotoxic mediators: an adaptation to chronic diseases." Frontiers in Cellular and Infection Microbiology, 2020, PMID: 32373555.For initial eBL cell line and mouse avatar RNA expression analysis see: Saikumar et al. "Endemic Burkitt lymphoma avatar mouse models for exploring inter-patient tumor variation and testing targeted therapies." Life Science Alliance, 2023, PMID: 36878637. For general overview of cohort study see: Buckle et al. "Factors influencing survival among Kenyan children diagnosed with endemic Burkitt lymphoma between 2003 and 2011: A historical cohort study." Int J Cancer. 15:1231, 2016, PMID: 27136063.

  Study phs001282

• Illumina HumanCoreExome genotyping data from the British Society for Surgery of the Hand Genetics of Dupuytren’s Disease consortium (BSSH-GODD consortium) collection

  Dupuytren's Disease (DD - OMIM126900) is the most common heritable disorder of connective tissue. It is a fibroproliferative disorder of the palmer fascia, causing flexion contractures of affected digits. DD affects men more commonly than women. DD is an archetypal complex disease, with multiple genetic and environmental factors affecting the final expression of the disease phenotype. The incidence increases with age, and the prevalence of DD is therefore increasing as the UK population ages. Half of all patients present before age 60. DD causes significant functional impairment, and severe contractures can lead to permanent disability. The mainstay of current treatment is surgery, but recurrence and complications are both high. For severe contractures, the only suitable treatment option is amputation. The direct costs to the NHS are high, and underestimate the true economic costs to society. We collected salivary samples from adults in the UK who have had surgery for DD. We have genotyped these samples using the Illumina HumanCoreExome Beadchips. https://research.ndorms.ox.ac.uk/public/dupuytrens/what-is-dupuytrens-disease/

  Study EGAS00001001206

• Alveolar Rhabdomyosarcoma case report

  Rhabdomyosarcoma (RMS) is a mesenchymal malignancy phenocopying muscle and is among the leading causes of death from childhood cancer. Metastatic alveolar rhabdomyosarcoma is the most aggressive subtype with an 8% five-year disease-free survival rate when a chromosomal fusion is present, and 40% five-year disease-free survival rate when negative for a fusion event. The underlying biology of PAX-fusion negative alveolar rhabdomyosarcoma remains largely unexplored and is exceedingly rare in Li-Fraumeni syndrome patients. Here, we present the case of an 11-year old male with fusion-negative alveolar rhabdomyosarcoma studied at end of life with a comprehensive functional genomics characterization, resulting in identification of potential therapeutic targets for broader investigation.

  Study EGAS00001004828

• LungMAP: Molecular Atlas of Lung Development - Human Lung Tissue

  Mammalian fetal lung development is a complex biological process. Despite considerable progress, a comprehensive understanding of the dynamic regulatory networks that govern postnatal alveolar lung development is still lacking. The purpose of this study as part of the LungMAP consortium (www.lungmap.net) is to understand the transcriptional changes in the process of mammalian lung development.

  Study phs001961

• 16S-based fecal microbiota composition of the Milieu Intérieur Cohort

  The Milieu Intérieur project is a population-based study coordinated by the Institut Pasteur, Paris. The objective is to dissect the interplay between genetics and environment and their impact on the immune system. One of the primary goals of the project is to ascertain the role of the microbiota in regulating immune programs.

  Study EGAS00001003419