461 results for "fc 26 coins sale Besök Buyfc26coins.com Perfekt för att uppgradera mitt Ultimate Team..nc1F"

in 72.10 milliseconds.

• GA4GH

  Standards The EGA is a long-standing supporter of the Global Alliance for Genomics & Health (GA4GH) to enhance responsible sharing of human genetic data through the development of interoperable global standards for human data access. The EGA is one of the founding GA4GH Driver Projects and has contributed to the development and implementation of several GA4GH standards and APIs. Below is a list of the GA4GH standards and APIs that are currently available or planned for implementation at EGA. TechnicalStandards Purpose SpecificationVersion SupportedVersion Implementation Large Scale Genomics htsget A protocol for secure, efficient, and reliable access to sequencing read and variation data. V1.3.0 V1.0.0 Specification Documentation Endpoint Read File Formats (SAM/BAM/CRAM) Specifications for storing next-generation sequencing read data. V3.0.0 V3.0.0 Implementation Example of Usage Variation File Formats (VCF/BCF) The specifications for Variant Call Format Files (VCF) and its binary counterpart BCF. V4.0.0 V2.0.0 V4.0.0 V2.0.0 Implementation Example of Usage Crypt4GH v1.0 Enables direct byte-level compatible random access to encrypted genetic data stored in community standards (e.g. CRAM, VCF) V1.0 V1.0 Specification Documentation Endpoint refget API Enables access to reference sequences using an identifier derived from the sequence itself. V1.2.6 NA Specification RNAget API v1 Provides a means of retrieving data from several types of RNA experiments including (i) feature-level expression data from RNA-seq type measurements and (ii) coordinate-based signal/intensity data similar to a bigwig representation via a client/server model. V1.0.0 NA Documentation Discovery Beacon v2 Supports discovery of genomic variants, phenotypes, and individuals V1.0.1 V0.3 Web UI API Source Code Service Info API v1 The Service Info API is an endpoint for describing GA4GH service metadata, designed for extension and inclusion in other APIs. Service info is used to describe a single service, while Service Registry is used to describe multiple services. V1.0.0 NA Documentation Service Registry API v1 provides information about other GA4GH services, primarily for the purpose of organizing services into networks or groups and service discovery across organizational boundaries. V1.0.0 NA Documentation Data Use Researcher Identities Data Use Ontology (DUO) Allow users to semantically tag genomic datasets with usage restrictions, allowing them to become automatically discoverable based on a health, clinical, or biomedical researcher’s authorisation level or intended use. 2021-02-23 2021-02-23 Specification Documentation Endpoint Authentication & Authorization Infrastructure (AAI) The GA4GH AAI specification leverages OpenID Connect (OIDC) Servers for use in authenticating the identity of researchers desiring to access clinical and genomic resources from data holders adhering to GA4GH standards, and to enable data holders to obtain security-related attributes of those researchers. V1.2.0 V1.2.0 API URI: ega.ebi.ac.uk:8443 Documentation Repository Researcher IDs (passport, visa) Specify the collection of researchers that may access a dataset at any given time, and the credentials they must supply. V1.0.1 V1.0.1 Specification Documentation Endpoint Cloud Tool Registry Service API TRS is a standard API for exchanging tools and workflows to analyze, read, and manipulate genomic data. V2.0.1 NA Documentation Repostiory Data Repository Service API ​DRS API is a standard for building data repositories and adapting access tools to work with those repositories, works with other approved APIs from the GA4GH Cloud Work Stream to allow researchers to discover algorithms across different cloud environments and send them to datasets they wish to analyse. V1.0.3 NA Documentation Repostiory Workflow Execution Service API This API lets users run a single workflow (defined using CWL or WDL) on multiple different platforms, clouds, and environments, and be confident that it will work the same way. The API provides methods to request that a workflow be run, pass parameters to that workflow, get information about running workflows, and cancel a running workflow. V1.0.1 NA Documentation Repostiory Genomic Knowledge Standards Variation Representation v1 Provides a flexible framework of computational models, schemas, and algorithms to precisely and consistently exchange genetic variation data across communities. V1.3.0 EGA team is contributing to including it in in Beacon v2 Specification and Elixir Reference Implementation Documentation Repostiory Clin/ Pheno Data Capture Phenopackets Provides information models with different levels of complexity to enable high level clinical phenotype information as well as deep clinical phenotype information to be exchanged. V2.0.0 Included in Ongoing Submissions EGA team is contributing to including it in in Beacon v2 Specification and Elixir Reference Implementation Documentation Repostiory Driver Project The EGA, jointly coordinated by the EBI and the CRG, was announced, in 2017, to be one of the 15 Driver Projects for GA4GH. Driver Projects are international genomic data initiatives, focussed on real projects and challenges that will guide the development efforts in order to accelerate and enable completely responsible and standarised data sharing by 2022. All chosen Driver Projects make a cross-sectional effort by playing an important role across the different workstreams. Thomas Keane, Jordi Rambla, Mallory Freeberg, and Aina Jené have been named Driver Project Champions for the EGA. All Driver Project Champions will be leading this ambitious initiative for the following years.

  Documentation about/projects-and-funders/ga4gh

• University of Illinois at Chicago (UIC) Autism Centers of Excellence (ACE) Exome Sequencing Analysis

  Autism spectrum disorder (ASD) is highly heritable with recent sibling recurrence risk estimates of 19% overall and 26% in males. The heritable phenotype of hyperserotonemia, or elevated levels of platelet serotonin (5HT), in ~35% of people with ASD is a well-established biomarker. The efficacy of drugs like risperidone and potent serotonin transporter inhibitors at treating behaviors related to Insistence on Sameness, along with evidence of the contribution of hyperserotonemia to autism susceptibility collectively support the hypothesis that dysfunction in the 5HT system is a significant etiological target for investigation of the genetic component to autism. ASD genetic architecture is complex; common variants of large effect do not contribute substantially to overall ASD risk, but there are clearly common variants with small effects and rare genetic/genomic variation of larger effect among ASD genetic risk factors. The NIH ARRA Autism Sequencing Consortium, including Dr. Sutcliffe and Dr. Cook among others, has initiated exome sequencing studies to identify more of the rare variants contributing to ASD. Data from our group and others reveal numerous rare de novo and inherited sequence mutations, and the number of de novo and other functional mutations that are found to affect molecules encoding 5HT signaling and its regulation further reinforces our hypothesis that regulation of serotonin levels is important in autism genetic susceptibility. Integrin receptor signaling pathways were prominently featured among identified de novo mutations, thus defining a set of interrelated gene networks that control 5HT signaling. We propose to extend our findings to date by conducting exome sequencing on ACE subjects, for whom we also have 5HT biochemical data, to identify rare variants (including CNVs) in 5HT-related gene networks. In total we propose to have exome sequencing completed on 523 samples. The purpose of the proposed research is two-fold: 1) we will conduct more extensive investigations to determine the support for the hypothesis that genetic variation at genes regulating platelet serotonin levels affect susceptibility to ASD and 2) we will combine the exome sequence data from these studies with sequence data for autism being accumulated in a variety of other research projects to further the goal of identifying and characterizing the genetic component to ASD.

  Study phs000712

• A Genome-Wide Association Study in Patients Experiencing Breast Events While Receiving Adjuvant Aromatase Inhibitors for Early Breast Cancer on NCIC CTG Trial MA.27

  Source of patients:The source of the patients for this genome-wide case-control study was MA.27, which was conducted as a multi-cooperative group effort under the auspices of the NCI Breast Cancer Intergroup of North America. The NCIC Clinical Trials Group (CTG) serves as the coordinating group, with participation by the NCI-sponsored North Central Cancer Treatment Group, Eastern Cooperative Oncology Group (ECOG), Southwest Oncology Group, and Cancer and Leukemia Group B (CALGB). MA.27 involved postmenopausal women with histologically confirmed and completely resected invasive breast cancer with surgical margins clear of invasive carcinoma in the following TMN categories (AJCC Version 6): pT1, pT2, pT3; pNx, pN0, pN1, pN2, pN3 (only when the sole basis is presence of 10 or more involved axillary nodes); MO. The primary tumor must have been estrogen receptor (ER) and/or progesterone receptor positive. Patients were stratified by lymph node status at diagnosis, prior adjuvant chemotherapy, and trastuzumab use and were randomized to 5 years of adjuvant therapy with anastrozole or exemestane. The trial was activated on May 26, 2003, and reached its accrual objectives on July 31, 2008, after the randomization of 6827 North American patients, with the majority (79%) providing DNA and consent for genetic testing. Non-North American patients were also entered by the International Breast Cancer Study Group but they did not contribute DNA. From 2003 to December 21, 2004, patients also underwent a second randomization to celecoxib 400 mg twice daily or placebo but, after the entry of 1,622 patients, this treatment was discontinued because of reports of increased cardiovascular risk associated with celecoxib. The final results of this study have been published, see Goss et al., 2013 (23358971). The patients in this analysis came from three cohorts: Cohort 1 consisted of 870 patients genotyped on the Illumina Human610-Quad BeadChip studied in a GWAS with the phenotype of musculoskeletal adverse event, see Ingle et al., 2010 (20876420), Cohort 2 consisted of 882 patients genotyped on the Illumina OmniExpress platform studied in a GWAS with the phenotype of fragility fractures, see Liu et al., 2014 (25148458), and the remaining 2913 patients were genotyped with the Illumina OmniExpressExome platform.

  Study phs001043

• eIMPACT Trial: Modernized Collaborative Care to Reduce the Excess CVD Risk of Older Depressed Patients

  Cardiovascular disease (CVD) is the #1 killer of American men and women, and its economic burden is substantial and on the rise. Adults with depression are at elevated risk of CVD events and poor CVD prognosis. Unfortunately, past clinical trials of depression treatments have not observed the anticipated cardiovascular benefits. A novel explanation for these null results is that the depression interventions in these trials, which all involved patients with preexisting CVD, were delivered too late in the natural history of CVD. Accordingly, the objective of this single-center, parallel-group, assessor-blinded randomized controlled trial was to determine whether successful depression treatment before, versus after, the onset of clinical CVD reduces CVD risk in depression. Primary care patients with depression and elevated CVD risk from a safety net healthcare system (N = 216, Mage = 59 years, 78% female, 50% Black, 46% with income <$10,000/year) were randomized 1:1 to 12 months of the eIMPACT intervention (a modernized collaborative stepped care program involving internet cognitive-behavioral therapy [CBT], telephonic CBT, and/or select antidepressants) or usual primary care for depression (primary care providers supported by embedded behavioral health clinicians and psychiatrists). The primary outcome was endothelial dysfunction (brachial flow-mediated dilation) at 12 months, and the secondary outcomes were self-reported depressive symptoms (Hopkins Symptom Checklist-20), autonomic dysfunction (high-frequency heart rate variability), systemic inflammation (interleukin-6 and high-sensitivity C-reactive protein), and platelet activation (β-thromboglobulin and platelet factor 4) at 12 months. The central hypothesis was that the eIMPACT intervention would improve endothelial dysfunction in depressed adults by decreasing depressive symptoms, autonomic dysfunction, systemic inflammation, and platelet activation. Primary results are posted to ClinicalTrials.gov at NCT02458690. The de-identified limited dataset available on BDC consists of only the individual phenotypic data needed to confirm this trial’s primary results – i.e., randomization status, primary and secondary outcome variables, and participant characteristics utilized in the hypothesis-testing models (age, sex, race, education, income, and systolic blood pressure). We also provide the SAS code to replicate the results of the hypothesis-testing models reported in Table 4 and Supplemental Tables 1-3 in the main outcomes paper (#2 in Selected Publications). Of note, the user will need to specify the file path for the dataset to run the SAS code. Instructions for requesting individual-level data are available on BDC at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BDC. For questions about availability, you may contact the BDC team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs003283

• PE-CGS: Optimizing Engagement of Hispanic Colorectal Cancer Patients in Cancer Genomic Characterization Studies

  Colorectal Cancer (CRC) is the second leading cause of cancer death in the US. Hispanic/Latinos (H/L) are the largest and fasting growing ethnic group in the US, and cancer is the leading cause of death among H/L in the US. Therefore, we need to fully understand the full complexity of the molecular etiology of cancer in this ethnic group. For instance, although incidence rates of CRC are lower among Latinos as compared to Whites or African Americans, Hispanics with metastatic disease have shorter overall survival when adjusted for health care setting, demographics, disease characteristics and treatment factors. H/L also tend to be diagnosed at a younger age and with higher stage, and we have previously reported that Mexican H/L in California have the greatest proportion of young (The Cancer Genome Atlas has provided a deep overview of the molecular taxonomy of CRC in 594 cases, however, less than 1% of the cases (n=5) were H/L. Therefore, it is imperative for us to take more detailed assessment of the molecular genomic landscape of CRC in H/L. One of the major issues likely limiting our ability to perform these large genomic initiatives in minority patients is that Patient or Participant Engagement practices may not be investigated to identify best practices for accruing and consenting patients into clinical translational biomedical research studies. This concept of Participant Engagement is critically important for both the patients and the translational cancer research community. Optimizing and improving our approaches for directly engaging patients at initial contact, throughout the course of a translational genomic study, and during the time of return of results is likely to lead to stronger relationships between the medical community and patients, but could also lead to significant improvement in outcomes for patients and for the cancer care community as a whole. As such, we propose the creation of the USC Center for Optimization of Participant Engagement in Cancer Characterization (COPECC) with a focus on optimizing the engagement of Latinos in CRC Genomic Characterization research studies. USC COPECC would serve as a member of the NCI U2C Participant Engagement and Cancer Genome Sequencing (PE-CGS) Network. Our investigative team includes experts in all relevant areas of research for genomic characterization, participant engagement, and engagement optimization. We have an established platform for consenting patients into cancer genomics studies that will serve as a standard process. The overall goal of USC COPECC is to generate results on participant engagement optimization and CRC genomic research that will be shared with the broader community to distribute best practices for engaging Latinos in hopes of improving overall outcomes for CRC in this underserved population.

  Study phs003985

• Title: Divergent levels of CD112 and INKA1 define a distinct subset of human long-term hematopoietic stem cells

  The data provided here was critical in establishing that human long-term hematopoietic stem cells (LT-HSC), previously described as the most primitive HSC population, is actually composed of distinct subsets that can be prospectively isolated. Via mechanistic studies centering around the Rho-GTPase effector kinase PAK4 and its inhibitor INKA1, we identified the immune checkpoint ligand CD112 as a marker for hematopoietic stem and progenitor cells, that is highest expressed on LT-HSC. More importantly, CD112 can be used to stratify functionally distinct subsets within LT-HSC: In response to regeneration-mediated stress, the CD112low subset exhibits a transient restraint (termed latency) before contributing to hematopoietic reconstitution, while the CD112high subset is primed to respond rapidly. High resolution RNA-seq of the CD112 surface expression spectrum within rare LT-HSC subsets (human umbilical cord blood) demonstrated that more genes are differentially upregulated in the deeper quiescent and less metabolic active subset. Genes enriched in this subset centre around cell adhesion and Rho-GTPase signaling. This is in agreement with the scRNAseq data from human G-CSF mobilized peripheral blood (mPB) generated here that was used as an model of in vivo activation/priming revealing via RNA-velocity and pseudo-time analysis that INKA1high versus PAK4high, CDK6high and CD112high enrichment are either detected early or late in diffusion pseudotime indicative of quiescent versus primed cell status, respectively. RNAseq following INKA1 overexpression in LT-HSC and ST-HSC revealed by GSEA an overall stemness preserving phenotype and particularly in LT-HSC, but not in short-term HSC (ST-HSC), suppression of transcriptional programs linked to activation. Collectively, our data decipher the molecular intricacies underlying HSC heterogeneity and self-renewal regulation and point to latency as an orchestrated physiological response that integrates quiescence control with HSC fate choices to preserve a stem cell reservoir.

  Dataset EGAD00001006541

• Center for Common Disease Genomics [CCDG] - Inflammatory Bowel Disease (IBD) - Global Microbiome Conservancy Host Exomes

  The human body is a complex ecosystem, hosting tens of billions of bacteria, primarily in the gut. This community, known as the 'gut microbiome', is vital to human health, affecting functions ranging from metabolism, immunity, and development, to behavior. Conversely, reduced microbiome diversity and other imbalances of the gut community (dysbiosis) are associated with many diseases of the industrialized world, such as metabolic syndrome, asthma, and inflammatory bowel diseases among others. Microbiome-based interventions thus hold the potential to revolutionize our understanding of, and therapeutic approaches to, many aspects of human health and disease. Despite many advances, current understanding of the human microbiome is largely limited to majority ethnic groups in industrialized nations, and does not reflect the full diversity of human commensal microbiota. In addition to the scientific ramifications of minority underrepresentation, there are significant translational and ethical implications as well: First, failing to capture the full diversity of healthy human microbiota may limit our ability to understand and generate effective therapeutics for many microbiome-associated diseases. Second, underrepresented groups are less likely to benefit from microbiome-based medical advances tailored to well-studied populations, propagating healthcare inequities. The window of opportunity to characterize human microbiome diversity is closing rapidly. Human gut microbial diversity is diminishing around the globe, due to the spread of Westernized diets and lifestyles, which are associated with reduced microbiome biodiversity. The Global Microbiome Conservancy (GMbC) is a non-profit collaboration between scientists and communities around the world that aims to 1) preserve the full biodiversity of the human gut microbiome, 2) characterize its evolution across populations and host lifestyles and 3) investigate its interactions with the human host. We are collecting gut microbiome and human DNA samples from diverse populations around the world, from isolated groups to urbanized populations, to culture and study this essential biodiversity and to preserve it in a living "seed bank" as a long-term safeguard against future extinctions. The National Human Genome Research Institute (NHGRI) has funded a collaborative large-scale genome sequencing effort to comprehensively identify rare risk and protective variants contributing to multiple common disease phenotypes. Called the Centers for Common Disease Genomics (CCDG), this initiative will explore a range of diseases with the ultimate goal of: Undertaking variant discovery for enough different examples of disease architectures and study designs to better understand the general principles of the genomic architecture underlying common, complex inherited diseases. Understanding how best to design rare variant studies for common disease. Developing resources, informatics tools, and innovative approaches and technologies for multiple disease research communities and the wider biomedical research community. The initial focus of the CCDGs will be in cardiovascular disease (early-onset coronary artery disease, atrial fibrillation, hemorrhagic stroke), neuropsychiatric disease (epilepsy, autism), and autoimmune/inflammatory disease (type 1 diabetes, inflammatory bowel disease). The Broad Institute is one of four selected CCDG project centers. Both exome and genotyping information of GMbC participants will help understanding how recruited human populations are structured and genetically related. This human genetic structure will be analyzed in light of gut microbiome compositional and genomic differences to illuminate associations between specific microbiome traits and human groups and the evolutionary processes involved in the co-evolution of human hosts and their gut microbiome. It will also provide variant information for critical genes shaping the composition of microbiomes, such as genes involved in innate and adaptive immunity (e.g. antimicrobial peptides) or in the regulation of the immune response (e.g. Nod2). Association studies between specific variants in these genes and microbiome features will be performed, which will then be validated with in vitro and in vivo experiments. Human data from GMbC cohorts will also increase the genetic diversity of human populations, providing additional variant information for many susceptible loci that were found to be associated with Crohn's disease and ulcerative colitis. The whole genome sequencing data generated is comprised of samples from diverse and indigenous populations. Raw sequencing data, metadata, vcf and phenotype data at the individual level for a subset of the cohort's samples are available at https://anvilproject.org/data. For questions about availability, contact help@lists.anvilproject.org. Microbiome data for the samples sequenced in this study can be found in phs002235 Global Microbiome Conservancy Sequence Data.

  Study phs002205

• Epidemiological study comparing rates and risk factors for dementia in African Americans in Indianapolis and Yoruba living in Ibadan, Nigeria

  In 1991 collaboration between researchers at Indiana University School of Medicine and the University of Ibadan, Ibadan, Nigeria established the Indianapolis-Ibadan Dementia Project. It is a longitudinal, prospective population-based comparative epidemiological study of the prevalence and incidence rates and risk factors of Alzheimer's disease and other age associated dementias. The project compares samples of community-dwelling elderly (age > 70 years) African Americans living in Indianapolis to Yoruba living in Ibadan, Nigeria, employing the same research design, methods, and investigators. It initially reported significantly lower prevalence rates of disorders in the Yoruba compared to the African Americans. In subsequent waves of the study (1994-1995, 1997-1998) incidence rates, rates of newly diagnosed cases, were also found to be significantly lower in the Yoruba. In genetic studies, the frequency of the APOE 4 allele was about the same in the two groups. APOE 4 was a significant risk factor for Alzheimer's disease and dementia in the Americans, while no association was found for the Yoruba. The APOE 2 allele appears to be protective in the Americans, but not the Yoruba. A constellation of factors often associated with vascular risk including a history of hypertension, diabetes, and high cholesterol levels is less common in the Yoruba than in the American group. An interaction was observed between cholesterol, APOE genotype and Alzheimer's disease in both study groups. In 2001-2002 survivors of the original cohort were once again evaluated (N~800 in each site) and 2,000 additional individuals age 70 years and older were enrolled in each site. Blood samples were collected from approximately 1,500 study participants in each site for genetic studies and analysis of biochemical risk factors for vascular disease. Subsequent waves of field work were conducted in 2004, 2007, 2009, and 2011. This fieldwork followed the classic two-stage study design. The study design involves an in-home screening interview with the study participant, which includes a cognitive assessment, medical history and current medications, brief neurological examination, height and weight, blood pressure measurement and assessment of social involvement. There is also a screening interview with a close relative of the study participant to assess activities of daily living, personality change, and medical history of the study participant. On the basis of the screening interview a sample of study participants (N~500 in each site) is selected for a full clinical diagnostic dementia work up which includes a neurological test battery, extensive interview with a family member and examination by a clinician. Diagnoses are made in a consensus diagnosis conference using the criteria of the Diagnostic and Statistical Manual of Mental Disorders, Revised Third Edition (DSM-III R) and International Classification of Diseases 10th Revision (ICD-10) for dementia. The criteria of the National Institute for Neurological and Communicative Disease and Stroke-Alzheimer's Disease and Related Disorders Association were used to diagnose possible and probable Alzheimer's disease. The focus of the study is risk factors for dementia and Alzheimer's disease, but also of particular importance is the question of mild cognitive impairment. This refers to the condition of having some decline in cognition but the decline is not sufficient to meet the criteria for dementia. We have studied this over the course of this project. In follow up studies of individuals who have this diagnosis about one third of them are better at follow up, about a third are about the same, and about a third decline more to meet the criteria for dementia. This is a very important issue for researchers because the ultimate goal of the research is to figure out how to identify the individuals who will definitely progress to dementia. If there are clear identifiers, it would be possible to make interventions, while individuals still function well, and possibly prevent the development of dementia altogether or delay the onset significantly. This is crucial because at the moment individuals usually do not enter into the medical care system until the dementia symptoms are quite severe, and the pathological damage to the brain cannot be undone.

  Study phs000378

• National Cancer Institute Cancer Genome Characterization Initiative (CGCI)

  The Office of Cancer Genomics at the National Cancer Institute sponsored a series of studies as part of the Cancer Genome Characterization Initiative (CGCI) to assess novel emerging sequencing technologies in cancer. The CGCI program included comprehensive characterization of the genetic aberrations found in different pediatric and/or adult tumors. CGCI characterized a number of B-cell non-Hodgkin lymphomas (including diffuse large B-cell lymphoma (DLBCL) from patients with and without HIV+ infection, follicular lymphoma (FL), as well as adult and pediatric Burkitt lymphomas), and additional HIV-associated tumors (including DLBCL, lung, and cervical cancers). All data from these projects is available at the NCI Genomic Data Commons. Individual project descriptions are available by disease on the substudy pages (links are included at the top of this page). Brief summaries are as follows: Non-Hodgkin Lymphoma (NHL) - CGCI investigators probed genomic alterations more deeply than had previously been possible by using state-of-the-art RNA sequencing (mRNA-seq) and whole genome shotgun sequencing (WGS) coupled with leading edge bioinformatics, data management and analysis approaches. The project sequenced tumor DNA and/or RNA from 117 NHL tumor samples and 10 cell lines. This included the genomes or exomes of 1 Follicular Lymphoma (FL) and 13 diffuse large B-cell lymphoma (DLBCL) cases, all with matched constitutional DNA sequenced to comparable depths, RNA-sequencing (mRNA-seq) of 92 DLBCL, 12 FL and 8 B-cell NHL cases with other histologies and 10 DLBCL-derived cell lines. The DLBCL cases and cell-lines are from the two major subtypes of DLBCL: germinal center B-cell (GCB) and activated B-cell (ABC). HIV+ Tumor Molecular Characterization Project (HTMCP) - This project was a joint effort of the Office of Cancer Genomics (OCG) and the Office of HIV and AIDS Malignancy (OHAM). Its goals were to characterize HIV-associated cancers (obtained from HIV-infected patients) and compare them to the same types of cancers from patients without HIV infection. Investigators performed 30X genome sequencing of 100 cases of paired tumor and germline DNA, along with transcriptome sequencing in each of 3 types of HIV+ tumors (DLBCL, lung and cervical cancers). These platforms allow discovery of mutations both in coding and non-coding genomic regions, gene expression and genomic alterations (including translocations, insertions and deletions). Comparing tumors of cancer patients both with and without HIV-infection provides insight into the potential function of this virus in certain cancers. Burkitt Lymphoma Genome Sequencing Project (BLGSP) - This project was a collaborative effort between the National Cancer Institute and the Foundation for Burkitt Lymphoma Research to develop a databank of the many alterations found in Burkitt lymphoma (BL), an uncommon type of Non-Hodgkin lymphoma that occurs most often in children and young adults. The goal of the BLGSP was to explore potential genetic changes in patients with BL that could lead to better prevention, detection and treatment of the cancer. The project characterized the alterations of the tumors' genomes (with matched normal as control) and transcriptomes by sequencing the DNA and RNA of each case. Using the data generated, the ultimate goals of the project was to discover the molecular changes that are present in BL patients and then determine how those changes correlate with treatment regimen and outcome. CGCI data is accessible at the NCI's Genomic Data Commons (GDC) via the GDC's Data Portal and from each of the CGCI Publication Pages at the GDC (Please see the "Supplemental Links" section of any CGCI publication's "Publication Information and Associated Data Files page" at the GDC.). Available datasets include raw sequencing data, datasets generated by the original CGCI research teams (fully annotated clinical information and higher-level/analyzed molecular characterization data), as well as higher level data generated by the GDC. Please see the CGCI Use and Publication Guidelines for updated details on the sharing of any CGCI substudy data, including how to cite CGCI.To learn more about the CGCI studies, please visit the CGCI Program website.

  Study phs000235

• Heart Failure Network: Diuretic Optimization Strategies Evaluation in Acute Heart Failure (HFN DOSE-BioLINCC)

  ObjectivesThe DOSE study sought to evaluate the most effective dosing (high vs. low) and administration (continuous infusion vs. intermittent boluses) combination of the diuretic Furosemide in the treatment of patients with acute decompensated heart failure.BackgroundAcute decompensated heart failure is the most common cause of hospital admissions among patients older than 65 years of age and is responsible for more than 1 million hospitalizations annually in the United States. Intravenous loop diuretics are an essential component of current treatment and are administered to approximately 90% of patients who are hospitalized with heart failure. Despite decades of clinical experience with these agents, prospective data to guide the use of loop diuretics are sparse, and current guidelines are based primarily on expert opinion. As a result, clinical practice varies widely with regard to both the mode of administration and the dosing.SubjectsA total of 308 patients were enrolled between March 2008 and November 2009 at 26 clinical sites in the United States and Canada. DesignThe DOSE study was a prospective, randomized, double-blind, controlled trial with a 2-by-2 factorial design. Patients were randomly assigned to either a low-dose strategy (total intravenous furosemide dose equal to their total daily oral loop diuretic dose in furosemide equivalents) or a high-dose strategy (total daily intravenous furosemide dose 2.5 times their total daily oral loop diuretic dose in furosemide equivalents) and to administration of furosemide either by intravenous bolus every 12 hours or by continuous intravenous infusion.The study treatment, with group assignments concealed, was continued for up to 72 hours. At 48 hours, the treating physician had the option of adjusting the diuretic strategy on the basis of the clinical response. An assessment of biomarkers, including creatinine, cystatin C, and N-terminal pro-brain natriuretic peptide, was performed at a central core laboratory at baseline, 72 hours, and 60 days. Patients were followed for clinical events to day 60. The coprimary end points were patients' global assessment of symptoms, quantified as the area under the curve (AUC) of the score on a visual-analogue scale over the course of 72 hours, and the change in the serum creatinine level from baseline to 72 hours.ConclusionsAmong patients with acute decompensated heart failure, there were no significant differences in patients' global assessment of symptoms or in the change in renal function when diuretic therapy was administered by bolus as compared with continuous infusion or at a high dose as compared with a low dose. (Felker et. al., 2011, PMID: 21366472)

  Study phs003524

• Virginia PrIMeD Study

  The goal of this study was to determine whether screening children (2-16 yrs) in pediatric waiting rooms for genetic risk of type 1 diabetes (T1D) could be applied to diverse (by geography, genetic ancestry) communities, and for those at "high genetic risk," if barriers prevent subsequent screening for presence of islet autoantibodies. A total of 3,818 children were recruited from eight general pediatric and specialty clinics across Virginia. Clinical Research Coordinators were stationed at each clinic and obtained informed consent/assent, a brief medical history, and a saliva sample for DNA extraction and determination of their genetic risk using a T1D Genetic Risk Score (T1D GRS). Children were present in the clinic for a "healthy" visit, although children with and without a history of T1D were recruited into the study. Age, sex, self-reported ancestry/race, T1D history, and other medical history information was obtained. DNA was extracted from the saliva samples and genotyping with a T1D-focused array using 74 SNPs (including 26 SNPs in the HLA region) provided data to generate a T1D GRS for each individual. Of the 3,818 children recruited, there was a slight excess of males (1,959, 51.3%), a majority of white and Hispanic/Latino ancestry (82.8%), and 91 (2.4%) with prevalent T1D. A total of 542 (14.2%) had "high T1D genetic risk" (T1D GRS > 5). Although the T1D GRS included non-HLA genetic variants, 80% of those with "high genetic risk" would have been classified using only those SNPs in the HLA region alone. Of children with "high genetic risk" and without pre-existing T1D (n=494), 7.0% (34/494) consented for islet autoantibody screening. Among children with pre-existing T1D (n=91), 52% (n=48) also had a "high genetic risk." The HLA-focused T1D GRS was not significantly associated with age at onset of T1D. Of those at high genetic risk that consented for autoantibody testing (n=34) and completed the blood collection (n=28), two (2/28, 7.1%) tested positive for multiple autoantibodies and were at significant risk of developing T1D. Follow up of 55% of parents/guardians identified 2 (of 2,096, 0.095%) participants who developed T1D, one at "high genetic risk" and one with a first-degree relative with T1D. A major factor in obtaining islet autoantibody testing was concern over SARS-Cov-2 exposure and an independent non-scheduled blood collection.Individual-level data at each SNP (genotyped and imputed) for T1D genetic risk and affiliated data are provided in dbGaP.

  Study phs003609

• Rapid Acceleration of Diagnostics - Underserved Populations (RADx-UP): COVID-19 Testing and Vaccination Social Network Diffusion for Diverse Criminal Legal Involved Communities

  This RADx-UP Phase II proposal, "Social network diffusion of COVID-19 prevention for diverse Criminal Legal Involved Communities", will implement a situation appropriate COVID-19 testing and vaccination social network diffusion intervention - C3 - building upon RADx-UP Phase I lessons and successful social network prevention interventions developed previously by the research team. C3 Criminal Legal Involved (CLI) populations encompass those non-incarcerated who have experienced recent arrest, incarceration, probation, parole or diversion programs such as drug courts. While increases in COVID-19 testing have been observed among this group, there remain members with limited testing history as well as individuals who are vaccine hesitant. COVID-19 prevention messaging can no longer be simplified to "everyone test and/or everyone vaccinate" as testing and vaccination decisions among community members are sensitive to personal histories (i.e., prior infection), local infection rates (i.e., low rates) and testing/vaccination availability. As COVID-19 prevention efforts have become more complicated (i.e., test if exposed), people tend to focus on the messenger, and particularly those that are close to them. Personal connections and communications within existing personal network structures, such as families, friends and other trusted acquaintances represent the cornerstone to increase situation appropriate testing and overcoming COVID-19 vaccine hesitancy. C3 builds upon RADx-UP I, by using a network diffusion approach facilitated through motivational interviewing purposefully geared to mobilize one's own organic social network to increase context appropriate testing and vaccine uptake. Through this process we will maximize the primary benefit and impact of this type of intervention which also has the intended effect of increasing likelihood that the messenger themselves will undergo the same behavior change that they have been trained to promote. We will leverage infrastructure developed in RADx-UP Phase I, which includes 4 high-impact sites across the Central US from Phase I: Baton Rouge LA, Little Rock AR, Indianapolis IN, and Chicago IL. We will utilize established engagement efforts already in place and continue to fully integrate communities in the strategic application of the intervention. We will use the RE-AIM (Reach, Effectiveness, Adoption, Implementation, and Maintenance) framework to guide implementation. C3 aims to: Aim 1a. Test the efficacy (3-month situation appropriate testing or vaccination) of a network diffusion intervention (C3) versus an existing COVID-19 testing and vaccine linkage to care intervention among: 1) primary study participants (primary outcome); and 2) secondary study participants connected to primary participants (secondary outcome) using a RCT design. Aim 1b. Explore the mechanisms for differential intervention effects at the individual and network-level that may increase situation appropriate testing and/or vaccination uptake. Aim 2. Examine key RE-AIM components in real time tied to the implementation of the network diffusion intervention (C3).

  Study phs003234

• The Federated EGA network

  In the last 10 years, most human omics data has been generated in the context of research consortia while recently there has been an emergence of large cohorts of human data generated by healthcare initiatives. Many countries in Europe now have nascent personalised medicine programmes. Thus, human genomics is shifting from being predominantly research-driven to being funded through healthcare systems. Genetic data generated in a healthcare context is subject to more stringent information governance than research data and nonetheless all data must adhere to national data protections laws. In this context, EGA identified the need for the development of a federated network to enable secure sharing of data whilst enabling genetic data to remain within the jurisdiction in which it was generated. The Federated EGA is designed to support national data management requirements for genomic and clinical data collected from citizens as part of healthcare or biomedical research projects. It includes a secure authorised access mechanism to support research use of these data across Europe and worldwide. We have engaged with over 14 ELIXIR countries to develop the federation model. The EGA federated configuration is composed of Central EGA, Federated EGA nodes and Community EGA nodes: Central EGA offers international submissions and helpdesk support, currently EGA co-managed by EMBL-EBI and CRG, Federated EGA nodes offer EGA services to researchers within their national jurisdiction, Community EGA nodes are individual institutions or initiatives with human genetic data intended to be shared with the research community. Key services available in the Federated EGA structure are: Central EGA Federated EGA node Community EGA nodes Data submission Offers international submissions service Offers submission service in a particular jurisdiction Does not offer an external submissions service Helpdesk support Provides external international helpdesk Provides helpdesk support for submitters in its jurisdiction and for approved users of data managed at its facilities Provides helpdesk support only for approved users of data managed at its facilities Data distribution Manages worldwide distribution for data hosted at Central EGA Manages worldwide distribution for data hosted at Federated EGA node Distribution for data hosted at Community EGA node EMBL-EBI and CRG have prepared a series of documents describing the overall governance and coordination framework. These describe the Federated EGA structure, the rights and responsibilities of the different parties and governing committees, and node operation guidelines. The federation governance proposal is under review by the first countries invited to join as Federated nodes, with further interested countries likely to join in the coming years. The Central EGA team has been working closely with many ELIXIR partners, including ELIXIR Finland, Luxembourg, Germany, Norway, Spain and Sweden.

  Blog the-federated-ega-network

• Lung Tissue Research Consortium (LTRC-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from LTRC include DNA, Plasma, Serum, Tissue - FFPE Cassettes, Tissue – RNALater Frozen, and Tissue - Snap Frozen. Please note that use of biospecimens in genetic research is subject to a tiered consent. Objectives: The LTRC was a biobank resource established by the NHLBI to collect and distribute lung tissue, blood samples, clinical data, and radiographic studies from participants with chronic obstructive pulmonary disease (COPD), idiopathic pulmonary fibrosis (IPF), other related idiopathic interstitial pneumonias (IIP) and interstitial pneumonias associated with connective tissue diseases who undergo medically-indicated lung resection. All tissue and blood specimens and clinical data were banked centrally and stored for distribution to external investigators who have approved study proposals to investigate the pathogenesis or management of lung diseases. The ultimate goal of this program was to enable research that illuminates the pathobiology of lung diseases and leads to novel interventional treatments for these conditions. Background: Chronic lung diseases are a main cause of death and disability in the United States. COPD affects over 14 million individuals in the United States and represents the third leading cause of mortality. Cigarette smoking is a major risk factor. However, only one of six individuals who smoke develops COPD. This could imply either an individual susceptibility or an additional immunologic or infectious injury to lung cells. Current treatments offer symptomatic relief, but do not prevent disease progression. Better understanding of disease pathogenesis, including the potential roles of lung parenchymal cell apoptosis, immunologic injury, and inflammation may lead to therapies that improve survival and quality of life. Interstitial pneumonias, including IPF and those associated with connective tissue disease, are less common than COPD, but for many of these diseases there are poor outcomes. For example, IPF has a 50% survival rate 2-3 years following diagnosis, and currently no treatment exists which prolongs survival. The prevalence of IPF is approximately 28 cases per 100,000. The underlying histology of IPF is usual interstitial pneumonia (UIP), which can also occur in connective tissue diseases. The incidences of other interstitial pneumonias such as non-specific interstitial pneumonia (NSIP) or acute interstitial pneumonia (AIP) are less frequent but also occur as an expression of interstitial lung disease in the connective tissue diseases. Moreover, there is significant crossover of these three interstitial pneumonias so that cases of IPF/UIP may also reveal fibrotic NSIP and be complicated by episodes of AIP. This implies common injuries but dissimilar histological responses. All of these processes are characterized by epithelial injury, uncontrolled fibroproliferation and the deposition of collagen, irrespective of the histology. It is clear that a better understanding of the genesis of the interstitial pneumonias is required before effective interventions can be developed. Participants: A total of 4,486 participants were enrolled, and lung tissue was obtained from 3,333 of these participants.Design: Written informed consent of each participant was required before any LTRC procedure was performed. Phenotypic data were then obtained that included recording of relevant medical information, a limited exposure history, radiological evaluation, and pulmonary physiological and lung function testing. Questionnaires were administered to determine the extent of symptoms, associated medical illnesses, smoking, environmental and occupational exposures, and quality of life. Laboratory testing included pulmonary function testing, a six-minute walk test, and chest x-ray CT. Blood specimens were collected both for defining the clinical phenotype of donors and to obtain serum, plasma, and DNA for later investigative purposes. At the time of surgery, lung tissues were collected and processed for long-term storage. The LTRC collected only the 'non-tumorous' portions of lung tissue from surgical procedures performed for primary or metastatic lung tumors and received those specimens only after the local pathologist had procured all tissue required for clinical care. Samples of appropriate size were cut and placed in formalin, RNAlater, glutaraldehyde, or liquid nitrogen within 30 minutes of excision (approximately 5% of cases exceeded this target time). Blood and tissue specimens were subsequently shipped to a central Tissue Repository for further processing and long-term storage. A Radiology Center provided quality control and quality assessment of CT data. A Data Coordinating Center managed study operations and maintained a repository of study data. Conclusions: LTRC established a biospecimen collection that is unique in its size, diseases included, standardization of methods, and extent of phenotypic data, serving as a valuable resource to facilitate research on the pathobiology of lung diseases.

  Study phs003913

• Molecularly matched targeted therapies plus radiotherapy in patients with newly diagnosed glioblastoma without MGMT promoter hypermethylation (N2M2/NOA-20 phase I/IIa umbrella trial)

  Background: Patients with glioblastoma without MGMT promoter hypermethylation are unlikely to benefit from temozolomide (TMZ). Trials aiming at replacing TMZ with targeted agents in not molecularly selected patient populations have failed. Methods: This phase I/IIa umbrella trial aimed at showing safety, feasibility, and preliminary efficacy of targeted compounds in addition to standard radiotherapy initiated within 42 days postoperatively. Molecular diagnostics and bioinformatic evaluation are performed within 28 days after surgery. Stratification for treatment takes place in five subtrials, including alectinib, idasanutlin, palbociclib, vismogedib and temsirolimus, according to the best matching molecular alteration. Patients without matching alterations are randomized between subtrials without strong biomarkers using atezolizumab and asunercept and TMZ as standard of care. Primary objective of the phase I parts of the trial was dose finding or dose validation. In the phase IIa trials, centrally determined progression-free survival at six months (PFS-6) is used as endpoint for efficacy with interim analyses for futility (H0: p=0.231). Results: From May 2018 through July 2022, 301 patients were enrolled and 228 treated in 13 German NOA sites. The alectinib and vismodegib subtrials were closed since no molecularly matching patients were accrued; the idasanutlin subtrial was closed prior to the optimal dose at nine patients at discretion of the company providing the drug. The TMZ subtrial showed a PFS-6 of 18.52% (10/54 patients) (p=0.831) and a median overall survival (OS) of 12.1 months. Asunercept: PFS-6 of 15.4% (4/26) (p=0.8825) and OS of 12.8 months. Atezolizumab: PFS-6 of 21.4% (9/42) (p=0.660) and OS of 11.7 months. Palbociclib with patients demonstrating CDK4 amplification or CDKN2A/B codeletion: PFS-6 of 24.4% (10/41) (p=0.4823) and OS of 12.6 months. Temsirolimus with patients demonstrating mTOR activation: PFS-6 of 39.1% (18/46) (p=0.0109) and OS of 15.4 months. The regimen-limiting toxicity (RLT)-rate is 34.8%, which is insignificantly above the predefined unacceptable rate for RLTs of 30%. Most RLTs had severity grade 3, one RLT had severity grade 4. No RLTs resulted in death. Conclusions: N2M2 allows for elaborate molecular testing being integrated into the treatment decision and efficient determination of treatment activity for patients with newly diagnosed glioblastoma. There is clinical activity of temsirolimus in patients with tumors harboring an activated mTOR pathway although this is not positively prognostic without mTOR inhibition; there is no clinical activity for asunercept and atezolizumab in not molecularly selected patients and also palbociclib in molecularly selected patients.

  Study EGAS00001008033

• Environmental Influences on Child Health Outcomes (ECHO) - PATHWAYS - Conditions Affecting Neurocognitive Development and Learning in Early Childhood (CANDLE)

  Pregnant women are exposed daily to multiple chemical and non-chemical stressors, including air pollutants, phthalates, and psychosocial stress. The Developmental Origins of Health and Disease model (DOHaD) states that exposure to these stressors in pregnancy affects fetal development in a manner that impacts offspring health across the life course. Yet epidemiologic data in these areas is limited, particularly with U.S. samples. It is also poorly understood whether these exposures prenatally affect childhood neurodevelopment and airway health in an independent or combined manner, and likely moderators of effects, such as the sex of the child, are infrequently addressed. We propose to unify three diverse extant pregnancy cohorts: TIDES (N=717, 2010-12), GAPPS (N=1133, 2012-16), and CANDLE (N=1385, 2007-11), for a combined sample size of 3235 mother-child dyads in the PATHWAYS study. PATHWAYS will investigate how chemical (air pollutants and phthalates) and non-chemical (psychosocial stress) exposures during pregnancy are related to placental gene expression (transcriptome) and childhood neurodevelopment and airway health (at ages 4-6, 8-9, and 10-11 years). Each cohort has rich resources of prenatal data and banked specimens (urine, blood, and placenta) that will be harmonized for the PATHWAYS study and will contribute to the ECHO consortium. We will develop a national model with high spatiotemporal resolution of key air pollutants and assess urinary markers of maternal exposure. A composite measure will capture multilevel maternal psychosocial stress across pregnancy, and urinary phthalate and blood stress hormone [Corticotropin-releasing hormone (CRH)] levels in the second and third trimesters will provide individual assessment of those exposures in potential critical periods. We will characterize the placental transcriptome using RNA sequencing (RNA-Seq) and will assess neurodevelopment and airway health prospectively into middle childhood. PATHWAYS will examine how these prenatal exposures are related to the placental transcriptome and child health outcomes in main effect and interactive models, with emphasis on sex-specific associations. For both neurodevelopment and airway health, we propose to measure both phenotypic precursors of health outcomes (i.e. fluid cognition, lung function growth), which yield dimensional tests of proposed associations, as well as clinically meaningful and policy relevant outcomes (i.e. asthma, mental health). Our study is powered to assess interactive effects of chemical and non-chemical stressors and will be the first study to characterize how prenatal environmental exposures relate to placental transcriptome pathways in relation to childhood health outcomes. This represents a significant scientific advance in testing DOHaD hypotheses. Major contributions to the ECHO Consortium include: 1) the development of a state of the art national model of air pollution, 2) a large, diverse pregnancy cohort with extensive biorepositories and extant prenatal and postnatal biomarkers, placental transcriptome, psychosocial and environmental data, and 3) an experienced, interdisciplinary team that will contribute meaningfully to the ECHO program of work.The sequencing data in this submission pertains only to the 794 subjects from the CANDLE study for whom placental tissue transcriptomics was performed.

  Study phs003619

• Environmental Influences on Child Health Outcomes (ECHO) - PATHWAYS - Global Alliance to Prevent Prematurity and Stillbirth (GAPPS)

  Pregnant women are exposed daily to multiple chemical and non-chemical stressors, including air pollutants, phthalates, and psychosocial stress. The Developmental Origins of Health and Disease model (DOHaD) states that exposure to these stressors in pregnancy affects fetal development in a manner that impacts offspring health across the life course. Yet epidemiologic data in these areas is limited, particularly with U.S. samples. It is also poorly understood whether these exposures prenatally affect childhood neurodevelopment and airway health in an independent or combined manner, and likely moderators of effects, such as the sex of the child, are infrequently addressed. We propose to unify three diverse extant pregnancy cohorts: TIDES (N=717, 2010-12), GAPPS (N=1133, 2012-16), and CANDLE (N=1385, 2007-11), for a combined sample size of 3235 mother-child dyads in the PATHWAYS study. PATHWAYS will investigate how chemical (air pollutants and phthalates) and non-chemical (psychosocial stress) exposures during pregnancy are related to placental gene expression (transcriptome) and childhood neurodevelopment and airway health (at ages 4-6, 8-9, and 10-11 years). Each cohort has rich resources of prenatal data and banked specimens (urine, blood, and placenta) that will be harmonized for the PATHWAYS study and will contribute to the ECHO consortium. We will develop a national model with high spatiotemporal resolution of key air pollutants and assess urinary markers of maternal exposure. A composite measure will capture multilevel maternal psychosocial stress across pregnancy, and urinary phthalate and blood stress hormone [Corticotropin-Releasing Hormone (CRH)] levels in the second and third trimesters will provide individual assessment of those exposures in potential critical periods. We will characterize the placental transcriptome using RNA sequencing (RNA-Seq) and will assess neurodevelopment and airway health prospectively into middle childhood. PATHWAYS will examine how these prenatal exposures are related to the placental transcriptome and child health outcomes in main effect and interactive models, with emphasis on sex-specific associations. For both neurodevelopment and airway health, we propose to measure both phenotypic precursors of health outcomes (i.e., fluid cognition, lung function growth), which yield dimensional tests of proposed associations, as well as clinically meaningful and policy relevant outcomes (i.e., asthma, mental health). Our study is powered to assess interactive effects of chemical and non-chemical stressors and will be the first study to characterize how prenatal environmental exposures relate to placental transcriptome pathways in relation to childhood health outcomes. This represents a significant scientific advance in testing DOHaD hypotheses. Major contributions to the ECHO Consortium include: 1) the development of a state of the art national model of air pollution, 2) a large, diverse pregnancy cohort with extensive biorepositories and extant prenatal and postnatal biomarkers, placental transcriptome, psychosocial and environmental data, and 3) an experienced, interdisciplinary team that will contribute meaningfully to the ECHO program of work.The sequencing data in this submission pertain only to the 408 subjects from the GAPPS study for whom placental tissue transcriptomics was performed.

  Study phs003620

• Single cell RNAseq of stenotic, inflamed and non-inflamed transmural lesions from patients with Crohn's disease

  This dataset contains a gene-cell matrix derived from single-cell RNA sequencing (scRNA-seq) data of ileal tissue from Crohn's disease (CD) patients and colorectal cancer (CRC) patients. It includes: Crohn's Disease Patients: A trio of transmural lesions (stenotic, inflamed, and non-inflamed) from each patient. Colorectal Cancer Patients: Unaffected ileal tissue used as external non-inflamed control. Cell Level Metadata: The dataset includes relevant cell-level metadata such as cell type annotations used in the study. Experimental Details: Platform: 10x Genomics Chromium Single Cell 3' GEX Sequencing: Illumina NovaSeq Processing: Data processed with Cell Ranger software. Resulting count matrices were merged for downstream analysis, including integration and dimensionality reduction. Dataset Composition: Crohn's Disease Patients: 10 patients with 3 samples each (non-inflamed, inflamed, stenotic), totaling 30 samples. Colorectal Cancer Patients: 5 patients with 1 sample each of unaffected tissue, totaling 5 samples. Data Provided: Merged Raw Count Matrix: The final merged raw count matrix used for downstream analysis. Cell Metadata File: Contains details of sample, tissue, and patient for each cell in the count matrix. Barcodes File: Indicate each cell barcode which also encodes the sample, tissue, and patient details for each cell. CD.S_Inf: Stenotic Corhn's disease inflamed samples CD.S_Sten: Stenotic CD patient stenosis sample CD.S_Prox: Stenotic CD Patient - proximal non-inflamed sample CC.C_Prox: CRC Patient proximal unaffected sample eg: A barcode 'CC.C_1_Prox_AAGTCGTAGACCCTTA' indicates CRC Patient unaffected proximal sampe from CRC Patient no.1 and the nucleic acid sequence indicate a unique cell from this sample. Total Samples: Crohn's Disease (CD) Patients: 30 samples Colorectal Cancer (CRC) Patients: 5 samples Patient_no Sample Sample_type 1 CC.C_1 CC.C_1_Prox CC.C_Prox 2 CD.S_1 CD.S_1_Prox CD.S_Prox 3 CD.S_1 CD.S_1_Infl CD.S_Infl 4 CD.S_1 CD.S_1_Sten CD.S_Sten 5 CC.C_2 CC.C_2_Prox CC.C_Prox 6 CD.S_2 CD.S_2_Prox CD.S_Prox 7 CD.S_2 CD.S_2_Infl CD.S_Infl 8 CD.S_2 CD.S_2_Sten CD.S_Sten 9 CC.C_3 CC.C_3_Prox CC.C_Prox 10 CC.C_4 CC.C_4_Prox CC.C_Prox 11 CD.S_3 CD.S_3_Prox CD.S_Prox 12 CD.S_3 CD.S_3_Infl CD.S_Infl 13 CD.S_3 CD.S_3_Sten CD.S_Sten 14 CD.S_4 CD.S_4_Prox CD.S_Prox 15 CD.S_4 CD.S_4_Infl CD.S_Infl 16 CD.S_4 CD.S_4_Sten CD.S_Sten 17 CC.C_5 CC.C_5_Prox CC.C_Prox 18 CD.S_5 CD.S_5_Prox CD.S_Prox 19 CD.S_5 CD.S_5_Infl CD.S_Infl 20 CD.S_5 CD.S_5_Sten CD.S_Sten 21 CD.S_6 CD.S_6_Prox CD.S_Prox 22 CD.S_6 CD.S_6_Infl CD.S_Infl 23 CD.S_6 CD.S_6_Sten CD.S_Sten 24 CD.S_7 CD.S_7_Prox CD.S_Prox 25 CD.S_7 CD.S_7_Infl CD.S_Infl 26 CD.S_7 CD.S_7_Sten CD.S_Sten 27 CD.S_8 CD.S_8_Prox CD.S_Prox 28 CD.S_8 CD.S_8_Infl CD.S_Infl 29 CD.S_8 CD.S_8_Sten CD.S_Sten 30 CD.S_9 CD.S_9_Prox CD.S_Prox 31 CD.S_9 CD.S_9_Infl CD.S_Infl 32 CD.S_9 CD.S_9_Sten CD.S_Sten 33 CD.S_10 CD.S_10_Prox CD.S_Prox 34 CD.S_10 CD.S_10_Infl CD.S_Infl 35 CD.S_10 CD.S_10_Sten CD.S_Sten

  Dataset EGAD50000000559

• Treatment of Pulmonary Hypertension and Sickle Cell Disease with Sildenafil Therapy (Walk-PHaSST)

  Pulmonary arterial hypertension (PAH) is a progressive condition characterized by narrowing or stiffening pulmonary arterioles resulting in increased pulmonary blood pressure and reduced delivery of oxygenated blood to the body. It is a common complication of sickle cell disease and initially presents with the symptom of shortness of breath (dyspnea) on exertion. As the condition worsens, other symptoms such as dizziness, lower extremity edema, and chest pain can develop. The drug, sildenafil, works by relaxing blood vessels in the lungs which reduces pulmonary blood pressure and allows more oxygenated blood to circulate. Increased levels of oxygenated blood allows individuals with PAH to tolerate more activity, but guidelines for using sildenafil in patients with PAH and sickle cell disease were unavailable at the time of the Walk-PHaSST trial.Participants were screened for the existence of pulmonary hypertension with a six minute walk test and a Doppler echocardiogram that assessed TRV, diastolic function, and valvular and systolic function. Subjects with TRV ≥ 2.7 m/s received further clinical evaluation for possible causes of pulmonary hypertension. Other screening data included medical history, a physical exam, and standard laboratory testing. For individuals with moderate to severe pulmonary hypertension (TRV ≥ 3.0), a cardiac catheterization was done at the baseline and week 16 data collection periods.Subjects eligible for the main intervention trial based on screening results were randomized in a 1:1 double blind fashion to receive sildenafil or placebo for 16 weeks. Subjects received 20 mg of oral sildenafil or matching placebo 3 times daily for 6 weeks, followed by 40 mg 3 times daily for 4 weeks, followed by 80 mg 3 times daily for 6 weeks, as tolerated. Participants could also receive other therapies as needed to manage sickle cell and related complications. The primary outcome measure of the trial was change in the six minute walk test, a standard indicator of a person's heart and lung function and exercise capacity, from baseline to week 16. After completing the study treatment (or placebo), participants could choose to be part of the open-label follow-up phase of the study and continue to be assessed for up to one year.The study was intended to screen about 1000 subjects and randomize 132 subjects, however it was terminated early due to the unforeseen increase in adverse events in participants treated with sildenafil as compared to placebo. When the study was stopped, 33 participants had completed the trial. Subjects continued to be monitored, but were instructed to taper sildenafil treatment over three to seven days.There was no evidence that treatment with sildenafil impacted the six minute walk distance from baseline to week 16. In addition, treatment with sildenafil appeared to increase rates of hospitalization due to sickle cell disease pain.Due to in part to the early termination of the trial, the majority of subject data was collected from the screening phase of the study (n=720), as opposed to the main intervention trial (n=74).Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs002383

• ALCHEMIST Study

  The ALCHEMIST study will accrue patients that are potentially eligible for the Intergroup adjuvant studies and perform central EGFR and ALK genotyping using a central reference laboratory certified by the Clinical Laboratory Improvement Amendments of 1988 (CLIA). Patients may either present prior to surgery with resectable NSCLC, may present following complete resection (before or after adjuvant chemotherapy). Eligibility is limited to those with NSCLC of a non-squamous histological subtype and those with adequate performance status and organ function for future trial eligibility. All subjects must submit tissue for central EGFR and ALK genotyping, as well as additional tissue for advanced genomics at the CCG. Subjects may have had local genotyping done prior to registration, however if these results shows no targetable EGFR or ALK alterations (or if it shows a KRAS mutation) then the patient will not be eligible for this screening protocol given the primary aim is to facilitate accrual to the adjuvant studies. All subjects will provide peripheral blood for matched normal DNA. All subjects (including those known to have EGFR or ALK alterations with local genotyping) will have formalin-fixed tissue collected for central genotyping. The testing will be performed at Response Genetics (Los Angeles, CA), a commercial CLIA-certified laboratory. ALK FISH will be performed using the Vysis break-apart probe and EGFR sequencing will be performed of exons 18-21. It is preferred that a full tumor block be submitted, but if unavailable, 15 unstained slides can be submitted. Genotyping results are expected to be provided to the treating clinician within 14 business days of submission so they can be used to determine eligibility for the randomized adjuvant studies, or to confirm the local results. Results will also be reported at intervals to the study team for update into the Alliance database. In addition to the commercial genotyping at Response Genetics, tissue will be collected for research genomics by CCG. For those patients with a block available, this will be forwarded to the CCG after clinical testing at Response Genetics. For patients without a block available, 15 unstained slides should be submitted to the CCG BCR for exploratory analysis. A peripheral blood specimen will also be collected and sent to the CCG BCR to use as matched normal. Specimens will be coded. Over the course of the study, the CCG will perform advanced genomic analysis of the resected lung cancer specimens in a research, non-CLIA environment. Following completion of the genomic analysis, the results can be matched with the clinical follow-up results using a link between the samples codes and the patient identifiers for correlative analyses. Subjects participating in the follow-up portion of the ALCHEMIST study, as well as those participating in the adjuvant therapeutic studies, are expected to undergo a standard-of-care diagnostic biopsy to confirm recurrence. At least two core biopsies, minimum, should be obtained as part of this recurrence biopsy. Paraffin embedded tissue from this biopsy will be used for confirmation of recurrence, for CLIA genomics to plan subsequent clinical trials, and for additional research genomics by the CCG. Plasma will additionally be collected at recurrence and sent to CCG for study of circulating free DNA (cfDNA). Data for the ALCHEMIST study is not yet available to be accessed by the public at this time; when ready it will be made available at the GDC Data Portal.

  Study phs001140

• FIGHT-207: Anonymized Genomic Alterations and Clinical Responses

  Background: FIGHT-207 was a phase 2 study of the FGFR1-FGFR3 inhibitor pemigatinib in patients with previously treated, locally advanced/metastatic or unresectable solid tumor malignancies harboring activating fibroblast growth factor receptor (FGFR) gene alterations. Population information: 107 patients were divided into 3 cohorts: FGFR1–FGFR3 fusions/rearrangements; n=49 Activating FGFR1–FGFR3 non-kinase domain single nucleotide variants (SNVs); n=32 FGFR1–FGFR3 kinase domain mutations or variants of unknown significance (VUS) with potential pathogenicity; n=26 Participants on study had tumors that were grouped into the following histologies based on ≥ 5 patients: Cholangiocarcinoma, gynecologic cancers (cervical, endometrial, uterine), central nervous system (glioblastoma, low-grade pediatric glioma, astrocytoma), pancreatic cancer, breast cancer, urothelial tract/bladder cancer, non-small cell lung cancer, and other (adrenal cancer, anal cancer, cancer of unknown primary origin, colorectal cancer, gastric/gastroesophageal cancer, gallbladder cancer, giant cell bone tumor, head and neck cancer, lung neuroendocrine cancer, nasopharyngeal cancer, ovarian cancer, prostate cancer, renal cell cancer, sarcoma, solitary fibrous tumor). Among the efficacy-evaluable participants, 99 had both independent review committee (IRC) central best overall response (BOR) and tissue NGS- data; 2 additional patients had Not Evaluable (NE) as central BOR Baseline tissue targeted NGS data (F1CDx, Foundation Medicine Inc.) of genomic alterations are reported for N=101 participants Baseline plasma targeted NGS analysis (PredicineCare, Predicine Inc.) of genomic data are reported for N=83 participants; data at disease-progression are reported for N=78 participants. Principal Findings: The FIGHT-207 study provided evidence of clinical benefit of pemigatinib in multiple histologies, explored the clinical actionability of various FGFR1-FGFR3 gene alterations, and leveraged the depth of translational data from targeted NGS analysis of baseline samples and plasma samples obtained at baseline and end of treatment to provide key insights into the biology of FGFR inhibition and the clinical utility of FGFR inhibitors. The FIGHT-207 article (pending in Nat.Med. NMED-A128973B) reports evidence suggesting clinical acquired resistance to FGFR inhibition via secondary FGFR mutations as well as emerging co-mutations in other oncogenic and tumor suppressor pathways. This study also provides evidence of acquired resistance to FGFR inhibition in multiple histologies beyond cholangiocarcinoma and urothelial cancers in a systemic correlative analysis of post-progression ctDNA in a trial. Data available through dbGaP: Anonymized information for 101 participants with both IRC central BOR evaluation (including 2 patients with NE as BOR) and tissue NGS data, including tumor histology, enrollable FGFR alteration, and outcome. Genomic alterations determined by baseline tissue NGS (F1CDx, Foundation Medicine Inc.) Genomic alterations determined by plasma NGS analysis (PredicineCare, Predicine Inc.) of ctDNA analysis at baseline (n=83) and at end of treatment/ disease progression (n=78) including genomic alterations that were not assessed to be Germline SNPs.

  Study phs003590

• The NCAA-DoD Concussion Assessment, Research, and Education (CARE) Consortium

  Study Description: Established in 2014, the U.S. Department of Defense (DoD) and the National Collegiate Athletic Association (NCAA) funded the Concussion Assessment, Research and Education (CARE) Consortium to inform science, clinical care and public policy related to concussion and repetitive head impact exposure (HIE) in U.S. Military Service Academy (MSA) cadets and collegiate student-athletes. The primary aims of the initial study were to: (1) establish a multisite research consortium to characterize the effects of concussion and repetitive head impact exposure on brain health, (2) characterize the clinical sequelae and natural history of concussion, (3) characterize the effect of concussion and repetitive head impacts on brain structure and brain function. The 30 member institutions of the CARE Consortium (26 civilian universities/colleges and 4 military service academies) agreed to invite all varsity athletes to undergo multimodal clinical assessments at preseason baseline, and at 5 additional timepoints after concussion diagnosis. At the service academies, non-varsity athlete cadets/midshipmen were also studied. Assessment Categories At Each Time Point Baseline: • Demographics • Personal and Family History • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms ACUTE POST-INJURY FOLLOW-UP (CARE 1.0) (24 hrs; 48hrs; Asymptomatic; Unrestricted Return to Play (RTP); 6 mos) • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms CUMULATIVE & PERSISTENT EFFECTS. (CARE 2.0) In-Person Exit Visit; Post-grad Online • Demographics • Personal and Family History • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms • PROs • MROs (at academies only) LONG-TERM EFFECTS (CARE/SALTOS Integrated (CSI))Annual Online Assessment (at MSAs only); In-Person Research Visits • Demographics • Symptoms • Psychological health • PROs • MROs (at academies only)A subset of athletes at 6 of the CARE institutions underwent additional assessments including multimodal MRI, proteomic and genomic biomarker characterization, and head impact quantification (helmet-based sensors). Assessment time points for the ARC/pARC Neurocognitive and Behavioral Testing was done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), Unrestricted Return to Play, 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career.Blood biomarker collection was done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career. Multi-modal MRI studies were done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career. However, please note that only athletes from one study performance site completed a multi-modal MRI study at baseline.

  Study phs002175

• Heart Failure Network: Entresto(TM) in Advanced Heart Failure (HFN-LIFE-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To compare treatment with sacubitril/valsartan versus valsartan alone in patients with advanced heart failure with a reduced ejection fraction and recent New York Heart Association class IV symptoms.Background: Treatment with evidence-based medical therapies improves survival, reduces heart failure hospitalizations, and improves quality of life in patients with chronic heart failure with a reduced ejection fraction. However, evidence supporting the use of medical therapies among patients with advanced heart failure is limited. Patients with New York Heart Association (NYHA) class IV heart failure are not often enrolled in clinical trials.A previous trial reported that, compared with the angiotensin-converting enzyme inhibitor enalapril, sacubitril/valsartan, an angiotensin receptor-neprilysin inhibitor, reduced the relative risk of cardiovascular mortality and heart failure hospitalizations by 20% in ambulatory patients with heart failure with a reduced ejection fraction. Although patients with NYHA class IV heart failure were eligible to enroll, this population was underrepresented. The HFN-LIFE trial was initiated to provide additional information about the tolerability, safety, and potential efficacy of sacubitril/valsartan in patients with advanced heart failure.Participants: Of the eligible patients that enrolled, a total of 335 patients tolerated the run-in phase and were randomized to a treatment group. 167 patients were randomly assigned to receive sacubitril/valsartan and 168 patients were randomly assigned to receive valsartan alone.Design: The HFN-LIFE trial was a prospective, multicenter, randomized, double-blind phase 4 clinical trial. Trial enrollment was suspended early, due to the high risk for adverse outcomes associated with COVID-19 infection.Eligible patients were enrolled and began an unblinded run-in period of 3 to 7 days with sacubitril/valsartan, 24/26 mg (50-mg fixed dose), administered orally twice daily. Participants tolerating the run-in phase were randomized in a 1:1 fashion to receive sacubitril/valsartan (target dose, 200 mg twice daily) or valsartan (target dose, 160 mg twice daily). The initial doses were selected based on guidelines with dose adjustments being made every 2 weeks.The primary efficacy outcome was the area under the curve of NT-proBNP levels at 2, 4, 8, 12, and 24 weeks compared with the level of NT-proBNP at randomization. The secondary efficacy end point was the number of days the patient was alive, out of the hospital, and free from any of the following outcomes: listing for cardiac transplant, cardiac transplant, implantation of a left ventricular assist device, receipt of continuous inotropic therapy for 7 or more days, or hospitalization for heart failure on 2 or more occasions other than the index admission.Conclusions: In patients with chronic advanced heart failure with a reduced ejection fraction, there was no statistically significant difference between sacubitril/valsartan and valsartan alone with respect to reducing NT-proBNP levels.

  Study phs004171

• Cincinnati Children's Hospital Medical Center (CCHMC) - eMERGE Phase IIIA Data

  This submission includes genotyping or sequencing data from separate cohorts, each is described in separate paragraphs below. Extreme early onset obesity Obesity is a serious epidemic condition and on the rise in the United States. Today, nearly one out of three children is overweight or obese in this country. According to the Center for Disease Control, 35.7% of American adults and 17% of American children are obese. The medical costs associated with obesity are estimated to be in the billions. Without a doubt, interplay of additive genetic effects and common environmental effects influence this complex disease. However, despite being exposed to so-called "obesogenic environment", a large proportion of the population remains of normal weight. These observations suggest that innate, non-environmental, factors make some individuals more susceptible to obesity providing support for biological mechanisms, and thus genetic factors, to underlie the individual's response to the obesogenic environment. In young children with severe obesity the relative role of genetics and in utero programming are likely to outweigh the short duration of environmental and lifestyle exposures. This group is therefore an ideal one to study as they are likely enriched for variants that influence the risk of developing obesity. The purpose of this project is to further study and understand obesity in childhood and to develop a repository of samples for future studies into obesity. Eosinophilic Esophagitis (EoE) Eosinophilic Esophagitis (EoE) is one of the manifestations of eosinophilic gastrointestinal inflammation which have profound effects on a patient's health and development. Results of epidemiologic studies performed through our center demonstrate that eosinophil-associated gastrointestinal disease is not an uncommon entity. While the epidemiology of eosinophilic esophagitis has not been thoroughly studied until recently, there appears to be a significant increase in the diagnosis of EoE in the last decade. Based on our research, this mainly reflects increased disease recognition, but there is also a bona-fide increase in disease incidence which coincides with the increasing incidence of asthma and allergic diseases in the industrialized world. In addition, many patients with intractable symptoms thought in the past to represent atypical GERD or other disorders are now being recognized as having EoE. Diagnosis of EoE requires endoscopy and biopsies to document the characteristic histologic findings of esophageal eosinophilia. In general, this study proposed to elucidate the mechanisms underlying eosinophil growth, survival, migration, and function, and to investigate and further characterize the pathophysiology of, clinical manifestations of, and spectrum of disease severity of eosinophilic esophagitis in humans. The de-identified genotyping and genome wide association data generated as part of this research will be used for further genome research. Familial Sample Repository (FSR) and Directed Sample Repository (DSR) De novo mutations could cause many diseases, which has been demonstrated in mental retardation, autism and many rare genetic disorders. Family-based studies have a variety of advantages over case/control studies, including the elimination of analysis artifacts related to population stratification, the detection of genes that act through a recessive mechanism of inheritance and validation that the trait is not transmitted from a parent, something not possible using a case/control design. Additionally, DNA from families can be used to identify de novo mutations suggesting strong candidate causal polymorphisms. For this project, samples will be collected from families on an on-going basis. Families may be recruited because the patient either has a disease which is thought to be of genetic origin or from the general patient population to serve as controls or future identified diseases. Some phenotypes under study include fibroblastic rheumatism, diaphragmatic hernia, polymicrogyria, severe congenital neutropenia, primary sclerosing cholangitis and staph infection. CLRR-Cincinnati Lupus Registry and Repository Systemic lupus erythematosus (SLE) is a complex, partially understood autoimmune disorder. Genetic origins for SLE are supported by high heritability (> 66%), familial aggregation, increased monozygotic twin concordance, genetic linkages, and candidate gene genetic association, including HLA genes, Fc receptors, and complement components. Relevant environmental factors likely include infections (Epstein-Barr virus), therapeutics, personal habits (smoking), and diet. To continue a research resource facility for collection of well-characterized pedigrees containing a proband with systemic lupus erythematosus we develop this repository. Juvenile Idiopathic Arthritis (JIA) Juvenile Idiopathic Arthritis (JIA) is a debilitating complex genetic disorder characterized by inflammation of the joints and other tissues and shares histopathological features with other autoimmune diseases. It is considered complex genetic traits. There are more than 50,000 children with JIA in the USA, approximately 1 per 1000 births, which is about the same incidence as juvenile diabetes. It is believed that genes in the major histocompatibility complex (MHC) play a role in defining genetic risk, and it can be hypothesized that loci in other chromosomal regions are involved in conferring risk in JIA. These candidate chromosomal regions can be identified using genome-wide association analyses. The long-term goal is a comprehensive understanding of the genetic basis of these disabling arthropathies for which the molecular basis is not presently understood. These data will contribute to a national resource for the study of autoimmunity in children. Better Outcomes for Children-Cytogenetics Since 2007, more than 4000 samples, enriched with various rare or common genetic diseases as well as specific chromosomal abnormalities such as deletions and duplications have been genotyped for the purpose of subsequent GWAS and Phewas analyses and uncovering main genetic effects.

  Study phs001011

• The EGA at the International Congress of Human Genetics

  Today is the start of the International Congress of Human Genetics (ICHG). This event, hosted by the African Society of Human Genetics (AfSHG) and the Southern African Society for Human Genetics (SASHG), will reunite international experts to highlight how genomic technologies are being managed to address challenges generated by the current status of Human Health and Genomics. The European Genome-phenome Archive (EGA) will be at the Congress participating in workshops, meetings and talks where topics such as data access and discovery as well as the Federated EGA will be present. Data access and discovery In the context of the “Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. Data access and discovery In the context of the “ Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. During the last four years, CINECA has been identifying gaps in data sharing between Africa, Canada and Europe in order to build a federated solution for data access. Thomas Keane will present the project within the sessions happening the 24ᵗʰ. The Federated EGA at the ICHG A Federated EGA poster will be shown during the Poster Session 1 that will take place the 23ʳᵈ. The objective is to bring awareness of the European Genome-phenome Archive as a resource for permanent archive and secure data sharing. In this context, the network generated by the Federated EGA is key for cases where research data cannot be shared outside local jurisdictions. The Federated EGA was officially launched on 2022 with research institutes from five countries becoming the first nodes of this network. Nowadays, with more than 20 nodes preparing to join, it aims to become the largest human omics data sharing initiative towards understanding human health and disease. The H3Africa Initiative and the African research represented in the EGA 1.1% of the EGA studies include samples from African populations. Countries such as South Africa, Kenya, Uganda or Egypt, among others, are present in the 72.577 samples from African individuals archived at the EGA. 23 EGA datasets are managed by the Human Heredity and Health in Africa Initiative (H3Africa). This Initiative will celebrate its Consortium Meeting the 27ᵗʰ and 28ᵗʰ, back-to-back with the ICHG. H3ABioNet, the Pan African Bioinformatics Network for the H3Africa consortium, will also take this context to celebrate its 10-Year Symposium during the Congress. Members of the EGA team will attend both of them, as the H3ABioNet works in conjunction with H3Africa projects, to submit data to the European Genome-Phenome Archive.

  Blog the-ega-at-the-international-congress-of-human-genetics

• NHLBI TOPMed - NHGRI CCDG: The BioMe Biobank at Mount Sinai

  The IPM BioMe Biobank, founded in September 2007, is an ongoing, broadly-consented electronic health record (EHR)-linked clinical care biobank that enrolls participants non-selectively from the Mount Sinai Medical Center patient population. BioMe currently comprises >42,000 participants from diverse ancestries, characterized by a broad spectrum of longitudinal biomedical traits. Participants are enrolled through an opt-in process and consent to be followed throughout their clinical care (past, present, and future) in real-time, allowing us to integrate their genomic information with their EHRs for discovery research and clinical care implementation. BioMe participants consent for recall, based on their genotype and/or phenotype, permitting in-depth follow-up and functional studies for selected participants at any time. Phenotypic and genomic data are stored in a secure database and made available to investigators, contingent on approval by the BioMe Governing Board. BioMe uses a "data-broker" system to protect confidentiality. Ancestral diversity - BioMe participants represent a broad racial, ethnic and socioeconomic diversity with a distinct and population-specific disease burden. Specifically, BioMe participants are of African (AA), Hispanic/Latino (HL), European (EA) and other/mixed ancestry. BioMe participants are predominantly of African (AA, 24%), Hispanic/Latino (HL, 35%), European (EA, 32%), and other ancestry (OA, 10%). Participants who self-identify as Hispanic/Latino further report to be of Puerto Rican (39%), Dominican (23%), Central/South American (17%), Mexican (5%) or other Hispanic (16%) ancestry. More than 40% of European ancestry participants are genetically determined to be of Ashkenazi Jewish ancestry. With this broad ancestral diversity, BioMe is uniquely positioned to examine the impact of demographic and evolutionary forces that have shaped common disease risk. Phenotypes available in BioMe - BioMe has a high-quality and validated set of fully implemented clinical phenotype data that has been culled by a multi-disciplinary team of experienced investigators, clinicians, information technologists, data-managers, and programmers who apply advanced medical informatics and data mining tools to extract and harmonize EHRs. BioMe, as a cohort, offers a great versatility for designing nested case-control sample-sets, particularly for studying longitudinal traits and co-morbidity in disease burden. Biomedical and clinical outcomes: The BioMe Biobank is linked to Mount Sinai's system-wide Epic EHR, which captures a full spectrum of biomedical phenotypes, including clinical outcomes, covariate and exposure data from past, present and future health care encounters. As such, the BioMe Biobank has a longitudinal design as participants consent to make all of their EHR data from past (dating back as far as 2003), present and future inpatient or outpatient encounters available for research, without restriction. The median number of outpatient encounters is 21 per participant, reflecting predominant enrollment of participants with common chronic conditions from primary care facilities. Environmental data: The clinical and EHR information is complemented by detailed demographic and lifestyle information, including ancestry, residence history, country of origin, personal and familial medical history, education, socio-economic status, physical activity, smoking, dietary habits, alcohol intake, and body weight history, which is collected in a systematic manner by interview-based questionnaire at time of enrollment. The IPM BioMe Biobank contributed ~10,600 DNA samples for whole genome sequencing to the TOPMed program. Samples were selected for the Coronary Artery Disease (CAD) and the Chronic Obstructive Pulmonary Disease (COPD) working groups. Using a Case-Definition-Algorithm (CDA), we identified ~4,100 individuals with CAD (~50% women) and ~3,000 individuals as controls (65% women). In addition, we identified ~800 individuals with COPD (62% women) and 1800 individuals as controls (72% women). Another 600 BioMe participants with Atrial Fibrillation, all of African ancestry, were included.

  Study phs001644

• Center for Craniofacial and Dental Genetics (CCDG): Genetics of Orofacial Clefts and Related Phenotypes

  The purpose of this study is to investigate the genetics of orofacial clefts (OFCs) in a large study population, and importantly, to incorporate subclinical phenotypic features into these studies. Orofacial clefts (OFCs) comprise a significant fraction of human birth defects (about 1/700 live births (Rahimov et al. 2012) and represent a major public health challenge, as individuals with these anomalies require surgical, nutritional, dental, speech, medical and behavioral interventions, thus imposing a substantial economic and personal burden (Berk and Marazita 2002*). The most common forms include OFCs of the lip alone (CL, Figure 1A), CL plus cleft palate (CL+CP, Figure 1B) or of the palate only (CP, Figure 1C). Individuals born with OFC may have their first surgical repair at age 3 months, but this initial surgery is just the beginning of a lifetime of health burdens. An individual born with an OFC has a hospital use rate increased for most ages (up to 233% increase for children ages 0-10 years and 16% for middle aged adults (Wehby et al. 2012). Healthcare costs for children with OFCs are estimated to be 800% greater compared with their unaffected peers (Boulet et al. 2009). Data from Denmark show that people born with CL with or without CP (CL/P) have an increased mortality up to age 55, which may be attributed to an increased risk of suicide and/or certain cancers (Christensen et al. 2004). The focus of most OFC genetic research has been CL and/or CP. Furthermore, the majority of OFC, i.e. about 70% of CL/P and 50% of CP is considered "nonsyndromic" (Jones 1988), i.e. isolated anomalies with no other apparent cognitive or structural abnormalities. Figure 1 Sample OFC Types A: Bilateral Cleft Lip; B:Cleft Lip plus Cleft Palate; C:Cleft Palate Alone The factors leading to the majority of nonsyndromic OFCs are still unclear, particularly at an individual family level. As is true for many complex traits, substantial progress in gene identification has occurred in the OFC field in the last two years (Dixon et al. 2011; Marazita 2012). Genome Wide Association Studies (GWAS) and sequencing studies to date by our research team and others have focused on genetic risk factors for overt CL/P and CPO-and have been very successful. A major finding from this work is that OFCs exhibit significant genetic heterogeneity, i.e., multiple genetic regions have been implicated (Beaty et al. 2010; Ludwig et al. 2012). Thus, approaches are needed to understand this genetic heterogeneity. Are there GxG interactions at work? Are there subsets of families, each due to a different gene? Our research group has shown that a promising approach to dissect the etiology of OFC is to focus on subclinical phenotypic features within entire cleft families (not just in affected cases, but also in their non-cleft relatives). These subtle features are believed to represent mild manifestations of the same underlying genetic susceptibility responsible for OFCs; as such, their inclusion in case-control and family-based genetic studies can help to clarify and refine the relationship between genotype and phenotype. The study population comprises a large number of families and individuals (~12,000 individuals) from multiple populations worldwide (Caucasians from the US and Europe, Asians from China and the Philippines, Mixed Native American/Caucasians from South America, and Africans from Nigeria and Ethiopia). There are cases, case families (nuclear families and extended kindreds), as well as controls with no history of OFC nor other developmental defects. *Berk NW, Marazita ML (2002) Costs of Cleft lip and Palate: Personal and Societal Implications. In: Wyszynski DF (ed) Cleft Lip and Palate: From Origin to Treatment. Oxford University Press, Inc., New York, pp 458-467.

  Study phs000774

• Prognostic and therapeutic significance of leukemia subtypes and minimal residual disease measurements in pediatric acute lymphoblastic leukemia treated with contemporary risk-directed trial: a cohort study

  Background Genomic analyses to identify leukemia subtypes and refinement of minimal residual disease (MRD) determination are two recent advances that would have substantial impact on the management of children with acute lymphoblastic leukemia (ALL). However, the combined application of these two approaches to determine the prognostic and therapeutic significance of MRD measurement and full spectrum of leukemia subtypes in the context of contemporary risk-directed therapy has not been studied comprehensively.MethodsBetween October 29, 2007 and March 26, 2017, 598 consecutive children with newly diagnosed ALL were enrolled in a clinical trial at St. Jude Children’s Research Hospital. Patients were provisional classified according to the presenting clinical and laboratory features including immunophenotype and cytogenetics. Patients with ETV6-RUNX1 and high hyperdiploid B-progenitor ALL were provisionally included in the low-risk groups; those with TCF3-PBX1, hypodiploidy and T-cell ALL in the standard (intermediate)-risk group; and patients with BCR-ABL1, KMT2A and early T-cell precursor ALL in the high-risk group. Final risk assignment was based primarily on MRD levels measured by flow cytometry on Day 15 (≥1%) and Day 42 (<0.01% or ≥1%) of remission induction. Using genomic classification based on cytogenetics and genomic analysis (single nucleotide polymorphism array analysis and transcriptome, exome, and genome sequencing), patients were classified into 17 subtypes. The primary aim was to determine the event-free survival, overall survival and cumulative risk of relapse according to specific leukemia subtypes and MRD levels on Days 8, 15 and 42 of remission induction. This clinical trial was registered at ClinicalTrials.gov, number NCT00549848.FindingsPatients with ETV6-RUNX1, high hyperdiploidy and DUX4-rearranged B-ALL all received low- or standard-risk therapy, and had the highest 5-year event-free survival rates: 98.4% (95% CI, 95.9-100), 95.3% (91.2-99.4), and 95.0% (84.2-100), respectively. All 142 patients with Day 8 MRD<0.01%, except two with KMT2A-rearranged ALL and one with TCF3-PBX1, were in continuous complete remission. The TCF3-PBX1, PAX5alt, T-cell, early T-cell precursor, iAMP21 and hypodiploid ALL had intermediate outcome with 5-year event-free survival rates ranging from 80.0% (39.4-100) to 88.2% (71.7-100). Patients with KMT2A-rearranged, BCR-ABL1, BCR-ABL1-like and ETV6-RUNX1-like ALL had the worst outcomes, with 5-year event-free survival rates between 64.1% (43.9-84.3) and 76.2% (51.9-100), despite most patients receiving standard- or high-risk therapy. Treatment intensification based on MRD and genotype improved outcome. Relapse did not occur in any of the patients with ETV6-RUNX1, DUX4-rearranged, TCF3-PBX1, iAMP21, ZNF384-rearranged, hypodiploid, or BCR-ABL1-like B-ALL who had day 15 MRD≥1% and received standard-risk therapy. However, day 42 MRD<0.01% did not preclude relapse in patients with intermediate-risk or unfavorable subtypes including TCF3-PBX1, PAX5alt, T-cell, iAMP21, BCR-ABL1, BCR-ABL1-like, ETV6-RUNX1-like, KMT2A-rearranged, and MEF2D-rearranged ALL, despite intensified treatment in the standard- or high-risk arms. InterpretationContemporary risk-directed treatment based on genotypes and MRD can cure virtually all patients with ETV6-RUNX1, hyperdiploid>50 and DUX4-rearranged ALL. While intensified treatment improve outcome for patients with high MRD during induction, substantial proportions of patients with intermediate-risk or unfavorable subtypes would still relapse even achieving negative MRD status at the end of induction and require novel therapeutics to improve outcome.

  Study EGAS00001004739

• The British Autozygosity Populations BioResource (2022-04-26)

  This data set contains whole exome sequences of individuals from 8086 (mostly British Pakistani/British Bangladeshi, mostly self-reported parentally related) individuals from the following studies: 1. 5236 British Pakistani/British Bangladeshi adults from East London Genes & Health, now known as Genes & Health 2. 2624 British South Asian mothers from Born in Bradford (mostly Pakistani) 3. 1061 British South Asian adults from Birmingham (mostly Pakistani) This dataset contains all the exome sequence data available for this study on 2022-04-26

  Dataset EGAD00001008736

• After the completion of CINECA, EUCANCan, and euCanSHare. What's next?

  CINECA, EUCANCan, and euCanSHare were part of the EUCAN Cluster, made up of six projects that received funding under the same Horizon 2020 call. All EUCAN projects (CINECA, EUCANCan, EUCAN-Connect, euCanSHare, Receptor Plus, and ReCoDID) were aimed at facilitating data reuse and knowledge discovery by enhancing data exchange and long-term collaboration in the health field. Here are some highlights about EGA’s contribution to these projects. CINECA: advances in Federated discovery and infrastructure for cohorts CINECA (Common Infrastructure for National Cohorts in Europe, Canada, and Africa) developed a federated cloud-based infrastructure for making genomic and biomolecular data accessible. The project has assembled a virtual cohort of 1.4 million individuals from sources such as the EGA, CanDIG and H3Africa. The EGA–CRG co-leaded a work package Work Package 1 on Federated Data Discovery and Querying. Beacon v2, championed by Jordi Rambla and Lauren Fromont, has been one of the central elements for the discovery of human genetic and phenotypic data. The EGA-CRG contributed to the development of a model for cohort discovery inside the Beacon v2 model. The team also delivered a Discovery Portal was implemented to explore cohorts and individuals of synthetic data. It is a UI that gathers a network of Beacons, a service for query expansion, and a visualisation tool. Have a look at the Discovery Portal UI, gathering a network of Beacons. You will find entities such as the Barcelona Supercomputing Center (BSC), BioData.pt and the European Genomic Data Infrastructure (GDI), among others. euCanSHare: facilitation of data access management This joint EU-Canada project aimed to build a European and Canadian FAIR platform for cardiovascular data sharing and analysis. The EGA’s tasks contributed to the development of the data management plan and data flows, main web-portal and interoperability protocols. An important part of the EuCanShare platform is the data access manager, a tool for the data owners to control the access to their sensitive datasets. We built a user-friendly interface for data access committees (data owners) to easily manage their data requests and access credentials. The data access portal facilitates the creation and internal organization of the data access committees as well as the linkage of data usage conditions to specific datasets. The interface includes filters for browsing requests and page to visualize the request history helping with the handling of data access requests. EUCANCan: toward a federation of clinical institutions in oncology The EUropean-CAnadian CANcer Network worked towards building a federated network to advance personalized medicine in oncology, by promoting the standard analysis, management and sharing of harmonized genomic and phenotypic data. The EGA led tasks on defining data flows and preparing an adapted infrastructure for long-term data storage and sharing. One of the key contributions was the conception of the EGA communities, offering standard and interoperable solutions for data discovery, processing, and sharing to projects and institutions that would like to manage and share data in the context of the EGA ecosystem. What's Next? The participation in projects such as CINECA, EUCANCan, and euCanSHare provide us with experience for future projects. We are happy to enhance data sharing and reuse, vital for advancing clinical and genomic research. The Discovery Portal is a wonderful proof of concept for the Beacon network. Next, we will finalise both the network and the user interface, and make sure it can be applied to more clinically-centred settings like hospitals. Most data hosted at the EGA are about cancer research. Currently, we contribute to building tools and infrastructure to empower oncology research in several European projects such as EUCAIM, EUCANIMAGE and EOSC4Cancer. We also do not lose sight of initiatives in the field such as the International Cancer Genome Consortium (ICGC) with the project ARGO, whose data model was adopted in EUCanCan.

  Blog cineca-eucancan-and-eucanshare-were-concluded-in-june

• Best Practices for DACs

  Best Practices Data access committees (DACs) are institutional safeguards responsible for ensuring a balance between data protection and accessibility. However, there are no procedural standards that apply across DACs, which can lead to inconsistencies in their reviews and compromise their quality and effectiveness. Standardising DAC processes can foster trust and mutual recognition, paving the way for greater coordination, collaboration, and delegation between DACs and other oversight bodies to improve the efficiency of data access without sacrificing protection. To provide guidance, the following are suggestions for actions a DAC might take upon receiving a data access request: Aim to respond to all initial requests in less than 2 weeks. Failure to do so may result in follow-up emails from the EGA, journals, and ultimately dataset withdrawal. First, check that the data/EGAD number is consistent with your data submission. In other words, ensure that the requester has contacted the correct DAC. Verify that the user will be using the data within the terms of consent by asking them to sign up to the terms within the DAA. Ensure that data users who are granted access to the data comply with the terms of a Data Access Agreement (DAA) and to use the data only in approved ways. Look for an institutional email address for the requester. Search for evidence that the requester is "appropriately qualified/bona fide" for using the data, for example on PubMed, Research Gate, LinkedIn, etc. Confirm that the affiliated organisation is real and that the requester still works there. Inquire with the requester about who should have accounts created at the EGA under the terms of the agreement. If a negative decision is made, promptly communicate it to the requester and support it with the terms of the Data Access Policy that the requester has not met or cannot meet. Keep the information in the DAC up to date. If you leave your institution and are unable to manage data access requests on their behalf, you should add your replacement as a new contact in the DAC. Assist with data access requests for any further questions related to your data. The EGA can only check information that has been deposited in the repository. If the user has a specific question that the EGA cannot answer, we will redirect the user to the DAC. All the EGA studies and datasets referenced in a publication under your DAC must be publicly searchable on the EGA website before the paper is released. If possible, describe the permitted purposes for subsequent research projects, including associated limits and conditions, for all resources hosted in a repository using a common ontology, such as the GA4GH Data Use Ontology (DUO). It is considered best practice to try and release data only to those with an institutional email address. This gives reassurance to the EGA, research participants, and the general public that an appropriate individual is accessing and using the data. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security.

  Documentation access/data-access-committee/best-practices

• Clonal selection after gene therapy in sickle cell disease

  While gene therapy (GT) provides a potentially curative treatment option for patients with sickle cell disease (SCD), the occurrence of myeloid malignancies in clinical trials has prompted concern. To interrogate potential mechanisms underlying increased cancer risk, we used hematopoietic stem cell (HSC) clonal tracking by whole genome sequencing (WGS) to map the somatic mutation and clonal landscape of 2,592 gene modified as well as unmodified single stem and progenitor cells from six SCD patients undergoing gene therapy (7-26 years old, average 12.7× depth). Pre-GT phylogenetic trees in SCD were highly polyclonal and mutation burdens per cell were elevated in some, but not all, patients. Post-GT, no clonal expansions were identified. However, an increased frequency of driver mutations associated with myeloid neoplasms or clonal hematopoiesis (DNMT3A- and EZH2-mutated clones in particular) were seen in both genetically modified and unmodified cells suggested positive selection of mutant clones during gene therapy. This work sheds light on the mutation landscape and HSC clonal dynamics in gene therapy for SCD and highlights enhanced fitness of some HSCs harboring pre-existing driver mutations following gene therapy. Future studies should define the long-term fate of mutant clones including any contribution to expansions associated with myeloid neoplasms.

  Dataset EGAD00001010913

• Prevention and Early Treatment of Acute Lung Injury (PETAL) Crystalloid Liberal or Vasopressors Early Resuscitation in Sepsis (CLOVERS) (PETAL CLOVERS-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL CLOVERS include plasma, and whole blood. Please note that use of biospecimens in genetic research is subject to a tiered consent. Available Data: The data available for request now include Long Term Outcome data.Objectives: To compare the effects of a restrictive fluid strategy (with early use of vasopressors) to a liberal fluid strategy in participants with sepsis-induced hypotension.Background: Intravenous fluid resuscitation is a common therapy used in the initial treatment of participants with septic shock and sepsis-induced hypotension. The goal of initial fluid therapy is to increase depleted or functionally reduced intravascular volume that occurs in sepsis due to a vasodilated vascular network. However, intravenous fluid resuscitation can create dilutional coagulopathy, fluid overload, and pathogenic edema in the lungs and other organs. Vasopressor agents are also commonly used to treat hypoperfusion by inducing constriction of arterioles and venules and increasing cardiac contractility. Vasopressor therapy also comes with risks that include vasoconstriction resulting in tissue ischemia, increased cardiac workload, and arrhythmias. Clinicians have used these strategies, typically in combination, to provide supportive care for participants with sepsis-induced hypoperfusion. However, at the time of the CLOVERS study, there was limited data to guide specific use of these therapies, including fluid volumes, in the early care of participants with sepsis-induced hypotension. The CLOVERS study hypothesized that a restrictive fluid strategy used during the first 24-hours of resuscitation for sepsis-induced hypotension would lead to lower mortality before discharge home by day 90 than a liberal fluid strategy.Participants: A total of 1,563 participants, from 60 medical centers, of the planned 2,230 participants were enrolled, with 782 assigned to the restrictive fluid group and 781 to the liberal fluid group. Enrollment in the trial was ended after the second interim analysis due to a lack of significant difference observed between the two 24-hour strategies.Design: This study was a multi-center, prospective, phase 3 randomized non-blinded interventional trial of fluid treatment strategies in the first 24 hours for participants with sepsis-induced hypotension. Participants were randomly assigned in a 1:1 ratio to either a restrictive fluid strategy (with early vasopressor use) or a liberal fluid strategy. In each group, the assigned protocol was followed for a period of 24 hours. The restrictive fluid protocol prioritized vasopressors as the primary treatment for sepsis-induced hypotension, with 'rescue fluids' being permitted for prespecified indications that suggested severe intravascular volume depletion. The liberal fluid protocol consisted of a recommended initial 2000-ml intravenous infusion of isotonic crystalloid, followed by fluid boluses administered on the basis of clinical triggers (e.g., tachycardia) with 'rescue vasopressors' permitted for prespecified indications. A protocol amendment implemented in October, 2019, allowed for limiting the initial infusion to 1,000 ml if the participant's blood pressure and heart rate had stabilized and the clinical assessment was that the participant was unlikely to benefit from additional intravenous fluid administration. The clinical team could override the protocol-specified care instructions at any time if it was judged to be in the best interest of the participant.The primary outcome was death from any cause before discharge home by day 90. Secondary outcomes included 28-day measures of the number of days free from ventilator use, days free from renal-replacement therapy, days free from vasopressor use, days out of the ICU, and days out of the hospital. Conclusions: Among participants with sepsis-induced hypotension, the restrictive fluid strategy that was used in this trial did not result in significantly lower (or higher) mortality, or other measures of recovery such as length of hospital stay, before discharge home by day 90 than the liberal fluid strategy.

  Study phs004080

• Genes and Blood Clotting Study (GABC)

  Objectives: Use genome-wide approaches to identify genetic variants that influence common thrombosis and hemostasis factors, as well as selected common human traits. Design/Methods: The GABC study was a prospective sibling cohort design. Siblings were recruited by targeted email to the undergraduate and graduate student email lists at the University of Michigan. Healthy persons between 14 and 35 years old who had healthy siblings within the same age restriction were able to participate. Study participants agreed to an online informed consent and subsequently completed a 52-question online survey describing their specific bleeding traits as well as many common human traits. Fifty milliliters of blood was collected into a citrate-dextrose solution (ACD) from each participant. An aliquot of whole blood was used for an automated complete blood count analysis and the remainder was processed into platelet poor plasma and buffy coat portions. Plasma and buffy coat aliquots were snap frozen and stored in liquid nitrogen for future studies. 1189 individuals representing 507 sibships were collected between 06/26/2006 and 01/30/2009. Phenotyping Survey Details: To characterize individual bruising and bleeding history, the online survey recorded answers to questions based on a modified von Willebrand Disease (VWD) screening questionnaire. To characterize a collection of participant's common human traits, the survey recorded answers to questions about height, weight, presence of skin tags, history of acne, eye color, hair color, hair line characteristics, skin sunburn sensitivity, skin tanning ability, natural skin color, freckling, cheek dimpling, earlobe shape, shoe size, foot arch characteristics, hand fifth digit morphology, history of dyslexia, history of migraine headaches, history of seasonal allergies, history of apthous ulcers, tendency to sneeze while walking into a bright sunny place, history of dental caries, need for corrective eye lenses, handedness and like or dislike of strongly flavored foods. Biochemical phenotyping: Assays for plasma Von Willebrand Factor (VWF) antigen were performed using ELISA and "Alphalisa" techniques. Automated complete blood count analysis was performed on a Bayer Advia 120 on all participants (including WBC differential, RBC indices, and platelet count.) For the dbGaP v2 update, new biochemical phenotypes have been submitted and include von Willebrand Factor, von Willebrand Factor propeptide, plasminogen, gamma prime fibrinogen, ADAMTS 13, antithrombin III, protein C, and protein S. All new phenotypes were obtained using "Alphalisa" techniques. Genotyping Details: SNP genotyping was performed using genomic DNA extracted from peripheral blood at the Broad Institute, (MIT/Harvard). Genotyping was performed on the Illumina Omni-1 quad chip at the Broad Institute. For the dbGaP v2 update, genotyping data from the Illumina Human Exome was deposited. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to blood clotting through large-scale genome-wide association studies of siblings. Genotyping was performed at the Broad Institute of MIT and Harvard, a GENEVA genotyping center. Data cleaning and harmonization was performed by the primary investigators at the University of Michigan, Ann Arbor, and at the GEI-funded GENEVA Coordinating Center at the University of Washington. This study serves as a resource for investigators who are interested in the genetic determinants of specific plasma proteins in a healthy population. The sibling cohort design allows for linkage analysis in addition to association studies. Analysis of thrombosis and hemostasis related traits should help elucidate specific biochemical and genetic networks that maintain hemostasis. We hope to identify specific genetic determinants of VWF levels in order to better understand the factors that influence the development of VWD.

  Study phs000304

• Whole Genome Scan for Pancreatic Cancer Risk in the Pancreatic Cancer Cohort Consortium and Pancreatic Cancer Case-Control Consortium (PanScan)

  Within the framework of the NCI-sponsored Cohort Consortium, investigators from 12 prospective epidemiologic cohorts formed the Pancreatic Cancer Cohort Consortium in 2006. This study, also known as "PanScan", is funded by the National Cancer Institute (NCI) and involves conducting a genome-wide association study (GWAS) of common genetic variants to identify markers of susceptibility to pancreatic cancer. In 2007, the study was expanded to include 8 case-control studies. The study team includes scientists from the cohorts comprising the Consortium, the NCI and the Pancreatic Cancer Case Control Consortium (PanC4). PanScan I and II were conducted in 12 cohort studies and 8 case-control studies, leading to the discovery of four novel regions in the genome associated with risk for pancreatic adenocarcinoma. The third phase of PanScan (PanScan III) was conducted using recently identified incident pancreatic cancer cases drawn from fourteen cohorts from the cohort consortium, including nine prospective cohorts who participated in PanScan I, and five newly joined cohorts. The nine cohort studies that participated in PanScan I and had new genotyping of cases in PanScan III include ATBC, CPS-II, EPIC, HPFS, NHS, PHS, PLCO, SMWHS, and WHI; the five newly joined cohort studies include the Agricultural Health Study (AHS), the Multiethnic Cohort Study (MEC), the Melbourne Collaborative Cohort Study (MCCS), the Vitamins and Lifestyle Study (VITAL), and Selenium and Vitamin E Cancer Prevention Trial (SELECT). In addition to the cases from cohorts, we also included cases from the Gastrointestinal Cancer Clinic of Dana-Farber Cancer Institute Study (DFCI-GCC); from the University Hospital in Heidelberg, Germany, which is part of a larger European clinical case-control study (PANDoRA); and from clinic-based cases from eastern Spain (PANKRAS-II). The dbGaP datasets available include all subjects previously made available from PanScan I and II, plus 1,582 new incident pancreatic cancer cases of European descent from prospective cohorts, case-control studies or case series (genotyped as part of PanScan III). Also included are 61 pancreatic cancer cases and 67 control subjects from PanScan I as well as 173 pancreatic cancer cases from PanScan III of Asian ancestry from the Shanghai Men's and Women's Health Study (Supplemental Table 10, Wolpin et al. (Nat Genet, 2014)). The control population used in the analysis for the Wolpin et al. manuscript included cancer-free individuals from the prospective cohorts that contributed pancreatic cancer cases to PanScan III and controls from the Spanish Bladder Cancer SBC/EPICURO study that were previously genotyped using the OmniExpress, Omni 1M or Omni 2.5M SNP arrays. The data from these control subjects were posted to dbGaP under the GWAS in which they were initially genotyped and will not be made available in duplicate under this dbGaP study.The summary statistics for PanScan I-III were generated as detailed in Wolpin BM. et al., Genome-wide association study identifies multiple susceptibility loci for pancreatic cancer, Nature Genetics 2014; 46(9):994-1000 (https://www.nature.com/articles/ng.3052), and Klein, A. et al., Genome-wide meta-analysis identifies five new susceptibility loci for pancreatic cancer, Nature Communications, 2018;9(1):556 (https://www.nature.com/articles/s41467-018-02942-5). The dataset includes results from an association study of 5,117 individuals diagnosed with pancreatic ductal adenocarcinoma (PDAC) and 8,845 control individuals, or a total of 13,962 subjects of European ancestry (as compared to the genotype and phenotype information under this project that includes 9,437 individuals (PanScan I and II PDAC case and control individuals and PanScan III PDAC cases only). This is due to the fact that PanScan III “borrowed” GWAS data from control individuals genotyped separately from the PanScan GWAS project and are therefore not included as raw genotypes in phs000206.v5.p3. Association analysis was performed separately for PanScan I-II and PanScan III, followed by a meta-analysis of the two datasets. Results were filtered based on a minor allele frequency (MAF) < 0.01, an imputation INFO score < 0.3 and a heterogeneity P-value < 1x10-10 leaving a total of 9,758,390 variants. Columns in the summary statistics dataset are as follows: ID: variant rsIDChr: chromosome numberPosition: position in the chromosome, genome build GRCh37/hg19MarkerName: variant identifierAllele1: reference alleleAllele2: alternative alleleFreq1: allele frequency for allele2FreqSE: standard error of the allele frequencyMinFreq: the minimal allele frequency across studiesMaxFreq: the max allele frequency across studiesEffect: effect size for allele2StdErr: standard errorP-value: meta-analysis p-valueDirection: summary of effect direction for each studyHetISq: I^2 statistic which measures heterogeneity on scale of 0-100%HetChiSq: chi-squared statistic in simple test of heterogeneityHetDf: degrees of freedom for heterogeneity statisticHetPVal: P-value for heterogeneity statistic

  Study phs000206

• 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

• GEnomics and Transcriptomics of Human INsulinoma (GETHIN)

  The Genomics and Transcriptomics of Human Insulinoma (GETHIN) The common forms of diabetes - Types 1 and 2 - ultimately result from a deficiency of insulin-producing pancreatic beta cells. The Genomics and Transcriptomics of Human Insulinoma (GETHIN) study was performed in order to identify novel approaches to inducing human pancreatic beta cells to replicate and regenerate. As a corollary, developing drugs that are able to expand human beta cell mass in people with diabetes should reverse diabetes. Unfortunately, identifying druggable pathways that can enhance human beta cell replication has been a major challenge. In 2017, there is only one class of drugs - the harmine analogues - that can induce human beta cells to replicate, and in this case, higher replication rates are desirable. Thus, identifying additional drugs and druggable pathways is a priority in diabetes research. Insulinomas are rare, benign adenomas of the pancreatic beta cell that cause excess insulin production and hypoglycemia: exactly the opposite of Types 1 and 2 diabetes. Beta cell proliferation rates in insulinomas are abnormally high. Thus, the premise for The Genomics and Transcriptomics of Human Insulinoma study is that benign human insulinomas hold the genomic and transcriptomic "recipe", and the repertoire of druggable pathways, that can be exploited to induce regeneration or replication of human beta cells in diabetes. Because, insulinomas are so rare, are almost always benign (non-malignant), and are easily resected by laparoscopic surgery, little attention has been paid to understanding the genomics or transcriptomics of insulinoma. There are at present only three published studies employing next-gen sequencing in insulinoma (PMID:24326773; PMID:25787250; and PMID:25763608). These studies contained 10, 7 and 8 insulinomas, respectively, and highlighted likely mutations in YY1 and MEN1. Our goal was to markedly expand the database and to add RNAseq to these earlier studies. The GETHIN study reports next-gen sequencing on 38 insulinomas, by far the largest series of human insulinomas subjected to next-gen sequencing (see the Selected publications section for reference). This includes paired (genomic plus tumor) whole exome sequencing on 26 human insulinomas (22 sequenced at Mount Sinai, 4 downloaded from Cao et al, PMID:24326773), and 25 sets of RNAseq from insulinomas, some of which also had paired whole exome sequencing, and some of which did not. The insulinoma RNAseq was compared to RNAseq from 22 sets of FACS-sorted normal human beta cells. Since insulinomas are so rare, the 38 insulinomas were collected by several investigators at several institutions over several decades, but most (22 whole exome sets, and all RNAseq) were sequenced at the Icahn School of Medicine at Mount Sinai in New York. The current dataset contains whole exome sequencing and RNAseq on the 11 insulinomas harvested at Mount Sinai. The four from Cao et al can be retrieved from Cao et al PMID:24326773. Fastq files from the remaining 23 insulinomas will be added as the local IRBs and Institutional Certifications are acquired. Complete patient data are provided in our Nature Communications report. Going forward, our intention is to expand this series, with the goal of sequencing 100 human insulinomas. These will be added to dbGaP as they accrue. Paired-end whole exome sequencing (mean usable sequencing depth 79X and 105X for blood and insulinoma, respectively) was performed using an Illumina HiSeq 2500. Insulinoma and sorted normal beta cell RNAseq was performed on Ribozero and polyA paired end libraries using the Illumina HiSeq 2500. Complete sequencing and bioinformatic details are provided in our Nature Communications report. The principal findings from the study are that although each insulinoma has a different set of presumptive driver mutations, the majority converge on genes that are members of the Polycomb Complex, Trithorax Complex and other epigenetic modifying enzymes. In addition, 20% of insulinomas have copy number loss or loss of heterozygosity of all or most of chromosome 11, and the majority display abnormalities in CpG methylation and imprinting control on the imprinted Chr 11 p15.5-15.4 region that contains INS, IGF2, CDKN1C, KCNQ1, and other genes involved in beta cell specification and proliferation.

  Study phs001422

• TRanscriptomic ANalySis of left ventriCulaR gene Expression (TRANSCRibE)

  Myocardial ischemia occurs when there is a mismatch between coronary oxygen delivery and metabolic requirements of the myocardium, which may be clinically manifested during angina, coronary angioplasty or cardiopulmonary bypass (CPB). Myocardial ischemia may lead to a spectrum of myocardial stunning, hibernating myocardium, and ultimately cell death if the ischemic insult is severe. In the human heart, irreversible damage begins after approximately 20 to 40 minutes of oxygen deprivation. Observed molecular and cellular changes of myocardial ischemia are characteristic of an inflammatory response, but the exact mechanisms that underlie this pathological process are unclear and may not be full emulated by animal models of ischemia or infarction. Thus, we felt it valuable to investigate a human ischemia model. During cardiac surgery, CPB with aortic cross-clamping (AoXC) and cardioplegic arrest is associated with excellent clinical outcomes and suitable operative conditions. However, despite the use of cardioprotective strategies, AoXc during CPB is accompanied by a variable, yet obligate ischemic period lasting 1 to 3 hours, resulting in hypoxia, metabolic substrate depletion, reperfusion injury, apoptosis, and necrosis. Cardiac specific biomarkers of ischemia and infarction, including troponin, are elevated even after routine coronary artery bypass graft surgery and correlate with the duration of ischemia from AoXc.This process of CPB provides us with the ability to examine the transcriptional profile before and after an expected, consistent, and reproducible human ischemic event, albeit induced by cold cardioplegic arrest and not coronary occlusion. In addition, the absence of reperfusion in this time period allows us to examine the transcriptomic response to intermittent ischemia, without having to account for the perturbations of reperfusion injury. Although various animal models have been used to examine the effects of ischemia on cardiac function, no human data exist which examine the early transcriptomic response to a left ventricular (LV) ischemic insult. We therefore characterized the effect of cold cardioplegia induced acute ischemia on the transcriptional profile of the LV by performing whole transcriptome next-generation RNA-sequencing (RNA-seq) in patients undergoing cardiac surgery by sampling human LV tissue prior to, and after, the obligate ischemia during AoXC. We hypothesized that the cold cardioplegia induced ischemic injury will dramatically alter transcription in the human myocardium, and that we would identify genes and pathways, which will identify interventional targets for pharmacological therapy. Methods:We have collected left ventricle tissue samples and blood sample from patients undergoing heart surgery. We obtained punch biopsies (~3-5μg total RNA content) from the site of a routinely placed surgical vent in the anterolateral apical left ventricular wall of patients undergoing elective aortic valve replacement surgery with cardiopulmonary bypass. After an average of 79 minutes of aortic cross-clamping with intermittent cold blood cardioplegia for myocardial protection every 20 minutes, a second biopsy was obtained in the same manner. Tissue samples were immediately placed in RNAlater® (Ambion, ThermoFisher Scientific, Waltham, MA), and after 48 hours at +4°C were stored at -80°C until RNA extraction. Total RNA was isolated with Trizol and RNA quality was assessed using the Agilent Bioanalyzer 2100 (Agilent, Santa Clara, CA). Libraries were prepared by poly(A) mRNA isolation and reverse transcription Polymerase Chain Reaction (RT-PCR), then sequenced on the Illumina HiSeq2000 or HiSeq2500 (Illumina, San Diego, CA). As samples were analyzed at different times, different read lengths were employed, initially using single-end reads (n=20) and then transitioning to paired end reads (n=216), ranging from 36 - 100 base pairs. Raw sequencing files were processed using Sickle, Skewer, and STAR software, and aligned to GrCh37 or UCSC Hg19. DNA was isolated from whole blood using standard methods. SNP genotyping was performed using the Illumina Omni2.5Exome-8 BeadChip array with additional exome content (Illumina, San Diego, CA) chip, version 1.1. We first phased and imputed 93 subjects using a phasing tool called SHAPEIT and an imputation tool called MINIMAC, with 1000 Genomes phase 1 version 3 for the reference panel. We then phased and imputed 26 more subjects using SHAPEIT, an imputation tool called IMPUTE2, and 1000 Genomes phase 3 version 5.

  Study phs001679

• Genetic Basis of Early Onset Bicuspid Aortic Valve Disease

  The study protocol was approved by the Committee for the Protection of Human Subjects at the University of Texas Health Science Center at Houston (HSC-MS-11-0185). Study recruitment began on July 1, 2017, and concluded on March 30, 2022. After written informed consent, we enrolled probands with early onset BAV disease (EBAV), which we defined as individuals with BAV who were under the age of 30 at the time of first clinical event. Clinical events were defined as aortic replacement, aortic valve surgery, aortic dissection, moderate or severe aortic stenosis or aortic regurgitation, large aneurysm (Z > 4.5), or intervention for BAV-related conditions. Those with hypoplastic left heart, known genetic mutations, genetic syndromes, or complex congenital heart disease were excluded. Samples were collected and genotyped as previously reported. For comparison, we analyzed a cohort of older individuals of European ancestry with sporadic BAV disease selected from the International BAV Consortium (BAVGWAS). Phenotypes were derived from record review with confirmation of image data whenever possible [25-26]. The computational pipeline for CNV analysis of Illumina single nucleotide polymorphism (SNP) array data included three independent CNV detection algorithms.GenomeStudio was used to exclude samples with indeterminate sex or more than 5% missing genotypes, and single nucleotide polymorphisms (SNPs) with GenTrain = 0. Principal component analysis was used to remove outliers that did not cluster with European ancestry. Prior to CNV analysis, each dataset was trimmed by selecting a common set of 650,000 SNPs that were genotyped on each of the microarrays used in this study.Three independent algorithms (PennCNV, cnvPartition, and QuantiSNP) were used to generate CNV calls and sample-level quality statistics from SNP intensity data. PennCNV and QuantiSNP were run on Unix clusters and cnvPartition data were exported from GenomeStudio. The analysis was run using default configurations. PennCNV was used to generate QC data and remove CNV calls that intersect with polymorphic genomic regions. Samples that met any of the following criteria were excluded, standard deviation of the LogR ratio (obtained from PennCNV) > 0.35 or number of CNVs > 2 standard deviations above the mean for each data set. CNV calls less than 20 Kilobases in length and/or spanned by fewer than 6 probes were excluded. The overlap function for rare CNVs in PLINK was used to construct CNV regions (CNVRs) after adjacent regions were merged using PennCNV. LogR ratio (LRR) and B allele frequency (BAF) data at CNVRs and calls of interest were visualized in GenomeStudio for validation. For segregation analysis, GenomeStudio was used to determine the presence of CNVs in relatives.A total of 22,014 unselected control Illumina Genotypes obtained from the Database of Genotypes and Phenotypes were analyzed using identical methods (S1 Table). The Wisconsin Longitudinal Study (WLS) includes data on a cohort of 10,300 individuals who graduated from Wisconsin high schools in 1957. The Health and Retirement Study (HRS) includes data on 37,000 individuals aged 50 above from 23,000 households across the United States. Principal component analysis was used to select European ancestry genotypes from these datasets for analysis. Datasets were paired for case-control analysis based on the concordance of log-transformed sample-level quality control statistics (number of CNV calls and standard deviation of logR ratios). Chi-squared or Fisher exact tests were used to compare CNV frequencies in cases and controls.Rare CNV functions in PLINK (v1.7) were used to perform permutation-based burden tests or gene set-based enrichment tests. Case control burden tests were restricted to CNVs that were longer than 110 Kb and less than 0.1% in frequency. CNV overlap functions in PLINK were used to identify rare CNVs that intersect between datasets or involve specific BAV or CHD genes . The list of candidate genes included 190 CHD genes that have strong cumulative evidence to cause BAV or related congenital malformations from human or animal model data. Genome Reference Consortium Human Build 37 was used for CNV annotation [34].

  Study phs003705

• All you need to know about our new DAC Portal v2

  An updated version to boost the management of DACs (Data Access Committees), policies, and data access requests. In September of 2023, we launched new services for all EGA users, including a DAC Portal. Since then, our team has been working to refine it and improve the user experience. The version 2 of our DAC Portal is now ready, with a range of new features aimed at streamlining your workflow and boosting productivity. If you are interested in learning more about the latest version of our DAC Portal, then you are in the right place! In this post, you will find information about the implemented features and more. The full documentation is available on our website. Moreover, we highly recommend exploring the DAC Portal through the Take the Tour. This said, let's get cracking! Customise your data access requests table This table offers the possibility to tailor information about the data access requests by making visible or hiding different columns regarding the Dataset Persistent Identifier, the Organisation or the requestor's name s, among others. You can choose which columns to see, depending on your needs and interests. Additionally, we have implemented two new features columns with two new functionalities, DAC Comment and Expiration Date. You can find more details in the following sections! In this table, all data access requests are displayed by default. With the latest version of the Portal, you can now apply filters, combine them, and save them for future use. Leave internal comments on pending requests and visible to all the DAC Members We understand that many Data Access Committees (DACs) cannot instantly approve or deny data access requests. Often, there's an intermediary phase where discussions and the signing of legal documents are necessary. To facilitate this process, we've introduced the DAC comment feature! When you navigate to the DAC column, you'll find two tabs: "User" and "DAC". Under "User", you'll see the message provided by the requester at the time of requesting access to the data. As a DAC member/admin, you can then add an internal comment in the "DAC" tab. These comments are visible only to DAC members/admins, ensuring confidentiality. Requesters won't have access to DAC comments. By adding a DAC comment to a pending request, we'll know that you've begun reviewing it. This allows you to filter pending requests without DAC comments to focus on genuinely new requests, and it prevents you from receiving email notifications about ongoing data requests. Set expiration dates for permissions and revoke them automatically The latest update to the DAC Portal introduces a new feature allowing you to set expiration dates for new access requests. For instance, if you anticipate approving a data access request but only wish to grant access for a limited time, you can now specify an expiration date for the granted permissions. Once this date is reached, the permissions will automatically be revoked. By default, permissions are granted indefinitely without an expiration date. However, if you ever need to revoke permissions, you can easily do so from the History page. Audit your metadata objects Managing and auditing your metadata objects will be easier from now on as the new DAC Portal enhances and facilitates your role as a Data Controller. This is possible thanks to the tables available in each of the primary tabs visible on the homepage: DACs, Policies and Datasets. Starting with DACs, this section allows to check the policies linked to a specific DAC. In Policies, you can obtain a list of the datasets connected to a particular policy. In the Dataset tab, it is possible to group datasets by either DAC or Policy, as well as the release status. Now you have the option of deprecating metadata objects that you don’t want to use anymore, or that were created by mistake. You will find the deprecate button on the EDIT page of the DAC, as well as for registered policies. You can find more information here. What's neat about this feature is that once a DAC or policy is deprecated, it becomes hidden within the DAC Portal. This ensures that you only see information that is consistently up to date! Define your preferences regarding email notifications For pending requests, you will be able to decide how often you want to get the notifications: daily, weekly or fortnightly. Remember, you will not receive email notifications for pending requests with a DAC comment! Furthermore, you have the flexibility to decide which notifications you wish to receive, such as invitations to join a new DAC or notifications regarding DAC acceptance by the Helpdesk, among other options. Check the User preference to see the complete list of available notification settings! What’s next: incoming DAC Portal API 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 consult the DAC API specification. This post was written by Aina Jené and Ana T. Alonso.

  Blog new-dac-portal-v2

• 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

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? The 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

• 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

• Privacy Notice for Helpdesk service

  Privacy Notice for EGA Helpdesk service 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. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 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 dr. Thomas Keane, by: email at: tk2@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? We process your personal data on the grounds of important public interest. 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 users of the service: Name Email address Job title Date and time when the support request was sent We will use your personal data for the following purposes: To provide uninterrupted user access to the service To better understand the needs of the users and guide future improvements of the service To 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 organizations. 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. 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. Published at: February 6, 2019

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

• How to request data

  Request Data Access If you're looking to access data from the EGA for your research, you are in the right documentation page! In this page you will find a step by step guide on how to request data archived at the EGA, as well as some frequently asked questions you might find useful. When requesting data, you'll need to provide information about your research project and intended use of the data. Keep in mind that your data access request may require additional approvals or agreements depending on the datasets and data providers involved. Step by step guide Register yourself as an EGA user. Validate your account. A validation link will be sent to your email to activate your EGA user account. Log into the EGA page. Search the dataset of interest from the dataset catalogue or search bar. Click on “Request access” Add a comment requesting these files and send your request Your request is successfully registered, and the DAC will receive a notification about your request In addition to submitting your request, you should also contact the DAC directly via e-mail. You can access the DAC's contact information from the relevant dataset page. Frequently Asked Questions (FAQ) Which is the role of the EGA in the data access process? The European Genome-phenome Archive (EGA) facilitates the secure distribution under controlled access of personally identifiable genetic and phenotypic data. Data Access Committee (DAC) is a body of one or more individuals who are responsible for data release to external requestors, based on participant consent and/or National Research Ethics terms. How do I request access to multiple datasets? To request access for multiple datasets managed by the same Data Access Committee (DAC), please start by visiting the DAC catalogue to locate the DAC of your choice. Once you've found the relevant DAC, proceed to its dedicated page where you'll find a "Request access" button. After logging in to the EGA website, you'll be presented with a comprehensive list of datasets under the chosen DAC. Select the datasets you're interested in, and then compose a message indicating your access request. Click the "Send" button to submit your request, which will include the chosen datasets. Please be sure to review the data usage policies for the requested datasets, as policies can vary among datasets managed by the same DAC. I am a co-applicant. Will I be given a joint access account? Each applicant needs to create an EGA account themselves, with unique login details. User log-in details are for individual use only and should never be shared, under any circumstances. EGA services are only provided to EGA account holders. Therefore, the co-applicant will send a formal request to the DAC. What happens if a co-applicant leaves or a new member needs to be added to an existing DAC application? The appropriate Data Access Committee (DAC) should be contacted and informed about the required changes so that the application can be updated. I have changed my place of work since my EGA account was created. Can I still have access to data? You must contact the relevant Data Access Committee (DAC). The DAC did not reply to my data access request. How should I proceed? There is no estimated time for DAC response. Please allow up to four weeks for a response. In the meantime, please send them a weekly reminder of the status of your request by emailing them directly.If the DAC becomes unresponsive, meaning that they fail to communicate with a requestor within the specified time frame, please contact the EGA Helpdesk team. I have an account with the EGA and would like access to further datasets. How should I proceed? You need to reapply to the relevant Data Access Committee (DAC). Once the DAC has approved your application your account will be updated and an email will be sent to notify you of a change made to your account. How do I download files of the datasets I have been granted access to? The preferred method for data download and decryption is the EGA Secure Download Client. Please carefully review the provided documentation. How do I download metadata? Metadata is retrieved from the EGA webpage; you will not need to use any download client. Be informed that you will only be able to download metadata of your approved datasets. For such download, you should first log in the EGA webpage with your credentials. Then browse the metadata's dataset you have gained access and you will find a metadata download button. You may also want to have a look our metadata schema. I have forgotten or misplaced my user account password; how do I get a new one? Click on “Log in”, located in the top right corner of the EGA homepage. Then click “Forgot password”, type in your registered institutional email address, and instructions for resetting your password will be sent to you. Please check both regular and junk/spam folders. I was sent a link to set a password for my download account, but it seems like the link has expired. What should I do? The procedure is the same as the one for a forgotten password, explained in the previous question.

  Documentation access/request-data/how-to-request-data

• Transdisciplinary Research Into Cancer of the Lung (TRICL) - Exome Plus Targeted Sequencing

  The study was conducted under the auspices of the Transdisciplinary Research In Cancer of the Lung (TRICL) Research Team, which is a part of the Genetic Associations and MEchanisms in ONcology (GAME-ON) consortium, and associated with the International Lung Cancer Consortium (ILCCO). Ethics All participants provided written informed consent. All studies were reviewed and approved by institutional ethics review committees at the involved institutions. Sequencing data are derived from four sub-studies. The sub-studies that contributed include Harvard, Liverpool, Toronto, and IARC. The IARC and Toronto studies are described above. A description of the Harvard and Liverpool studies is provided below. Liverpool Lung Project: The Liverpool Lung Project (LLP)1 is a case control and cohort study, which has over 11,500 individuals, with detailed epidemiological, clinical and outcome data with associated specimens (i.e. tumour tissue, blood, plasma, sputum, bronchial lavage, EBUS and oral brushings). The participants have completed a detailed lifestyle questionnaire and updated data on clinical outcome and hospital events are collected through the Office of National Statistics, Cancer Registry and from Health Episode Statistics. The project is registered on the UK National Institute for Health Research (NIHR) lung cancer portfolio and has all the required ethical approvals and sponsorship arrangements in place. The LLP has detailed standard operating procedures (SOP) for all aspects of the recruitment, data, specimen collection as well as the data storage. The LLP Cohort study has 8,224 participants with blood and 7,761 with plasma samples. The LLP case-control samples have been incorporated into in a large number of international GWAS and molecular studies 2,3, methylation 4-7, microRNA 8and next generation studies 9-11, resulting in high ranking publications, as well as forming the basis for the LLP risk prediction model 12-14 which has been utilised in the UK lung cancer screening trial (UKLS) 15-17 Patient and control DNAs were derived from EDTA-venous blood samples. Harvard Samples. David Christiani at the Harvard University School of Public Health has been directing research studies to investigate etiological factors influencing lung cancer development since 1983 and has amassed a collection of 2000 controls and 5055 lung cancer cases. He has been actively collecting and storing snap frozen tumor samples since 1992. Around 1500 tumor samples have been collected and the average wet tumor yield is about 30 grams of tumor, of which 631 cases have completely annotated clinical and survival information. Pathology confirmation is provided by two pathologists. At the time of surgery, a minimum of 30 grams of wet lung tumor tissue and 30 grams of non-involved tissue from the same lobe is sectioned, flash frozen and sent to Dr. Christiani&#39;s lab for logging and storage. A blood sample for DNA and serum is collected. A structured interview by trained research staff is conducted on each case, and clinical outcomes and treatments is extracted and entered into the molecular epidemiology data base at Harvard. Fresh frozen samples have been collected from 1451 lung cancer and are available for study. Samples from this collaborative study have played key roles in major studies, including the initial finding describing EGFR mutations in lung cancer 22. Participants in this study are patients, &#62; 18 years of age, with newly diagnosed histologically confirmed lung cancer. Samples that are included in the analysis have the following histologies: Adenocarcinoma: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3 8560/3; LCC: 8012/3, 8031/3; squamous carcinoma: 8070/3, 8071/3, 8072/3, 8074/3; and other NSCLC: 8010/3, 8020/3, 8021/3, 8032/3, 8230/3. The Toronto Study: The Toronto study was conducted in the Great Toronto Area between 1997 and 2014. Cases were recruited at the hospitals in the network of University of Toronto and Lunenfeld- Tanenbaum Research Institute. At the time of recruitment in the clinical setting, provisional diagnoses of lung carcinoma were first assigned based on clinical criteria. Diagnoses for all cases included were histologically confirmed by the reference pathologist who is a specialist in pulmonary pathology, based on review of pathology reports from surgery, biopsy or cytology samples in 100% of cases. Diagnostic classification was done initially according to ICD-9, ICD-10, and ICD for oncology-2, and subsequently converted to ICD-O-3. Tumors were grouped into the major categories included in this analysis according to primary cancer type based on the ICD-3 definitions. Controls were randomly selected from individual visiting family medicine clinics and Ministry of Finance Municipal Tax Tapes. All subjects were interviewed using a standard questionnaire and information on lifestyle risk factors, occupational history, medical and family history was collected. Blood samples were collected from more than 85% of the subjects. IARC: The IARC data are derived from case-control studies conducted in Russia and include samples that have available tissue samples. Patient and control DNAs were derived from EDTA-venous blood samples. The lung cancer patients were classified according to ICD-O-3; SQ: 8070/3, 8071/3, 8072/3, 8074/3; AD: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3, 8560/3, 8251/3, 8490/3, 8570/3, 8574/3; with tumous with overlapping histologies classified as mixed. The Lung Cancer Transdisciplinary Research Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" section of this top-level study page phs000876 Lung Cancer Transdisciplinary Research Cohort. phs000877 Meta Analysis phs000878 CIDR Lung Cancer phs001681 Affy Axiom Array

  Study phs000876

• Submitting array based metadata

  Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. 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. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, 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 "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering 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 (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

  Documentation submission/metadata/submission/array

• Submitter Portal API

  Submitter Portal API 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. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have 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, 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 the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

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

• A Genome-Wide Association Study in Patients Experiencing Musculoskeletal Adverse Events on NCIC CTG Trial MA.27 Evaluating Aromatase Inhibitors as Adjuvant Therapy in Early Breast Cancer. A Collaboration Between the NIH Pharmacogenetics Research Network and the RIKEN Yokohama Institute Center for Genomic Medicine.

  Source of Patients The source of the patients for this genome-wide case control study was MA.27, which was conducted as a multi-cooperative group effort under the auspices of the NCI Breast Cancer Intergroup of North America. The NCIC Clinical Trials Group (CTG) serves as the coordinating group, with participation by the NCI-sponsored North Central Cancer Treatment Group, Eastern Cooperative Oncology Group (ECOG), Southwest Oncology Group, and Cancer and Leukemia Group B (CALGB). MA.27 involved postmenopausal women with histologically confirmed and completely resected invasive breast cancer with surgical margins clear of invasive carcinoma and DCIS in the following TMN categories (AJCC Version 6): pT1, pT2, pT3; pNx, pN0, pN1, pN2, pN3 (only when the sole basis is presence of 10 or more involved axillary nodes); MO. The primary tumor must have been ER and/or progesterone receptor positive. Patients were stratified by lymph node status at diagnosis, prior adjuvant chemotherapy, and trastuzumab use and were randomized to 5 years of adjuvant therapy with anastrozole or exemestane. The trial was activated on May 26, 2003, and reached its accrual objectives on July 31, 2008, after the randomization of 6827 North American patients, with the majority (79%) providing DNA and consent for genetic testing. Non-North American patients were also entered by the International Breast Cancer Study Group but they did not contribute DNA. From 2003 to December 21, 2004, patients also underwent a second randomization to celecoxib 400 mg twice daily or placebo but, after the entry of 1,622 patients, this treatment was discontinued because of reports of increased cardiovascular risk associated with celecoxib. Case Definition for Musculoskeletal Adverse Events Cases were defined to have had at least one of the following six MSAE): 1. pain - joint, 2. pain - muscle, 3. pain - bone, 4. arthritis, 5. joint - function, 6. musculoskeletal - other. Cases were required to have at least grade 3 toxicity, according to the NCI Common Terminology Criteria for Adverse Events v3.0, or go off treatment for any grade of the six MSAEs; and were required to have had an MSAE within the first two years (i.e., a MSAE occurring after 2 years was not be considered a case). Subjects were excluded from the case group who met the case definition while on celecoxib or in the three months after stopping celecoxib but subjects were allowed to be cases if they developed their first MSAE more than three months after stopping celecoxib. Study Design The design was a nested matched case-control study with two controls selected for each case. Random matching from the potential control group (i.e., risk-set sampling such that controls had at least the same length of followup as the timing of the case event) was done by matching the case on the following factors: 1. treatment arm (exemestane vs. anastrozole, blinded), 2. prior adjuvant chemotherapy (yes vs. no), 3. age at start of treatment (+/- 5 years), 4. Celecoxib allocation (yes vs. no). Attempts were made to exactly match each case with two controls according to the above criteria. If, however, controls could not be exactly matched, "close" matching was used to define a distance between each case and all potential controls in an optimal matching algorithm. Race is a potential confounding factor, and 94% of the MA.27 population is Caucasian, 3% are Black, 1% Asian, 1% American Indian, and 1% are of unknown race. Because there are so few non-Caucasian participants, was restricted to only Caucasians. Following identification of cases and controls, the list was sent to the CALGB Pathology Coordinating Office (PCO) at Ohio State University Medical Center for plating of the samples. Other patient factors that might influence the association of SNP genotypes with a MSAE, either as confounding factors or as effect modifiers, were included as investigational covariates. These include 1. body mass index (BMI), 2. bisphosphonate use, 3. fractures in past 10 years, 4. baseline ECOG performance status, 5. prior hormone replacement therapy, 6. prior adjuvant radiotherapy, and 7. prior taxane treatment. An Honest Broker Process was utilized to ensure patient confidentiality. Genotype Assays and Quality Control A GWAS was performed with the Illumina Human610-Quad at the RIKEN Center for Genomic Medicine. The DNA for all of the samples were adjusted to a concentration of 50 to 100 ng/&#181;L in a final volume of 50 &#181;L. The 96-well plates were designed to have a unique distribution pattern with x duplicates per plate to evaluate genotype concordance. Samples with &lt;98% call rate were removed from analyses. SNPs with ambiguous call will be excluded using the following criteria: 1. low signal intensity of each allele, 2. low cluster separation score, 3. SNP call rate &lt;0.98, 4. SNPs with Hardy Weinberg Equilibrium p-value &lt;0.001 were excluded. X-chromosome SNPs were used to validate female sex and quality control measures were examined across the different submitting centers. For all pairs of subjects, the percentage of matching genotypes were computed to screen for unexpected duplicate samples. All SNPs found to be associated with MSAE were subjected to visual inspection of the cluster plots to verify that the genotype clustering was adequate.

  Study phs000210

• 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

• Privacy Notice for Data Access Committee Account

  Privacy Notice for EGA Data Access Committee Account 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. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 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 , orpost at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: email at dpo@embl.org, orpost 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, orpost 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.eupost 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? We process your personal data on the grounds of important public interest. 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: NameEmail addressTitle/PositionOrganisationOrganisational affiliationBusiness addressTelephone numberIP addressesDate and time of a visit to the service websiteOperating systemAmount of data transmittedBrowserUsernamePassword The data controller will use your personal data for the following purposes: To provide DAC user account and authenticated access to the service,To publicly publish some information to facilitate scientific research,To better understand the needs of the data subjects and guide future improvements of the service,To create anonymous usage statistics (from number of DACs, datasets per DAC). 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 (for all user account data),The general public via Internet will get access to your name, email address, business address, telephone number and organisation you belong to. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Data categories ‘name`, `email address`, `telephone number`, `business address`; `organisation’ of the DAC user are published on the Internet. They thus become accessible to recipients in countries outside the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI), is necessary for important reasons of public interest embedded in the aims of EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union 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. 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. Published at: February 6, 2019

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

• FEGA and European GDI: working together to improve human health

  The Federated EGA is a global resource for discovery of and access to sensitive human omics and associated data consented for secondary use, through a network of human data repositories to accelerate biomedical research and improve human health. The Federated EGA network was launched in September 2022 with five inaugural nodes, and since 2023 seven operational nodes can share data across national borders in adherence to European and national laws. A few weeks after FEGA's official launch, in November 2022, the European Genomic Data Infrastructure (GDI) project was kicked-off . This European Commission co-funded project, coordinated by ELIXIR, is aimed to deliver federated, sustainable and secure data infrastructure to access genomic and related phenotypic and clinical data across Europe. This project supports the aim of the 1+MG initiative (25 EU countries, Norway and UK) to enable personalised medicine and health through a shared framework and infrastructure for securely accessing and integrating high quality genomic data and other health data across borders.1+MG will be an integral component of the European Health Data Space (EHDS) for secondary use (Healthdata@EU) as an authorised participant. How are Federated EGA and GDI similar? Given their shared visions, the Federated EGA and European GDI networks have a lot in common. To begin, they share the same overall goal of establishing networks of “nodes” that host sensitive human data within a jurisdiction and connecting these nodes in a global network to support data discovery and promote human genome data access for research and healthcare. FEGA and GDI are both initially focused on enabling access to human genomic data, while FEGA ambition is to expand the scope to clinical research data and other omics data in the future. FEGA and GDI are both built on open and interoperable software solutions, a subset of which are based on the LocalEGA components. FEGA and GDI implementation solutions are based on international community standards, for example those developed by the Global Alliance for Genomics and Health, which contributes to making them interoperable. Both FEGA and GDI allow for the nodes to make use of any solution that is fully compatible. As illustrated in Figure 1, a final key point is the significant overlap of institutions involved in envisioning and operating FEGA and GDI nodes, with the clear wish to keep them interoperable in the future. What distinguishes Federated EGA from GDI? Despite being largely similar, there are some differences between the FEGA and GDI networks, which we aim to clarify in this post. The first difference is the governance model that the nodes will operate to comply with national laws and GDPR. In the FEGA network, nodes have taken inspiration from the EGA data access model, where the infrastructure is a data processor of the hosted data and data controllership remains with the originating Data Access Committees (i.e. Data controllers) for each dataset. On the other hand, in the GDI network the controllership of datasets will be transferred to a 1+MG European Digital Infrastructure Consortium (EDIC) legal entity created by the Member States (MS), who will make data access decisions, with data holders having veto powers for their datasets. Importantly, FEGA nodes have the flexibility to choose another model to fit with their data protection framework, including becoming data controllers for their datasets. The second difference is the inclusion criteria for data. While FEGA nodes are designed to accept almost any type of omics data in need of control access (e.g. genomics, transcriptomics, genotyping, single cells sequencing, patient-tracked metagenomics), GDI nodes are initially, but not only, focused on accepting whole genome and exome sequencing data and affiliated data from sources such as (i) the Genome of Europe use case of the 1+MG initiative which specifically aims to fulfil the mission of building “a European network of national genomic reference cohorts of at least 500,000 citizens”) (ii) data collection of other types of genomic data identified by countries through the 1+MG dashboard and (iii) genomic data coming from data holders which would need to fulfil EHDS requirements. The third difference is the maturity of the software stacks. The FEGA network provides a set of software for data and metadata submission, storage, permissions management, and file distribution (the LocalEGA package). GDI is building a complete set of open source reference for the five functionalities covering the full data life cycle (a few more compared to the LocalEGA) including federated processing (analytics, AI/ML), which is still under active development. Notably, one of the GDI functionalities - storage and interfaces - can be satisfied by using the LocalEGA storage solution, highlighting the ability of FEGA and GDI to be interoperable. In both FEGA and GDI, nodes are allowed to use alternative solutions as long as they are fully interoperable with the networks. Figure 1 provides a simple overview of these described commonalities and differences. Figure1: schematic overview of the main commonalities and difference among a FEGA and a GDI node Can the same institute run a FEGA and a GDI node at the same time? The answer is Yes! We believe this is entirely possible and encouraged. As long as 1+MG requirements are continuously fulfilled in the implementation. The same trained personnel could operate the infrastructure and leverage the same national funding to run a FEGA and a GDI node. Several European nodes, especially GDI vanguard nodes like Norway, Sweden, Finland and Spain are following this model. The idea is that a lot of the work can be reused, given the overlapping scope and the interoperable technology. Thus, the hosted datasets can be discovered via the two catalogues, perhaps accessible under the same or different governance models. From a FEGA node perspective, the GDI datasets could simply be a subset of the datasets hosted in the FEGA node, which have their specific governance as any other. What's next? So, the amazing teams of people building the Federated EGA network and the European GDI network are working together to create infrastructures able to provide secure access to human genomic and associated data around Europe. Because we all know how much human genomics can improve healthcare and precision medicine. And we all want to collaborate to make it happen. This article has been reviewed collectively by members of the EGA and the GDI coordination team.

  Blog fega-and-gdi

• Privacy Notice for the Account User

  Privacy Notice for EGA User Account 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. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 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 dr. Thomas Keane, by: email at: tk2@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? We process your personal data on the grounds of important public interest. 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: Name Email address Title/Position Organisation Organisational affiliation Username and password (to authenticate access to the system) IP Address (for anonymous usage statistics) We process your personal data: to provide you with the authenticated access to the EGA service (opening and managing submission and distribution account), to publicly publish some aggregate data to facilitate scientific research (e.g. number of accounts, geographic distribution), to better understand the needs of the users and to guide future improvements of the service, to create anonymous usage statistics. If you do not provide us with your personal data we will not be able to open the user account and offer you our services or we will only provide you a subset of functionalities available within the service. 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 (for all user account data), Requested dataset Data access committee – DAC will have access to the name, email, organization, affiliation, title/position of the distribution user account, using it for their own purpose of granting access to their datasets. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Distribution user account data are in the process of granting access disclosed to dataset(s) DAC, which might be a recipient in countries outside of the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI) is necessary for important reasons of public interest embedded in the aims of the EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union. 6. How long do we keep your personal data? All data are stored for as long as you have the account open. Thereafter the storage is prolonged for as long as our service is live, even if you stop using our services. This prolongation is necessary for further scientific research, to ensure legal compliance and security and to facilitate internal and external audits it 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. 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. Published at: February 6, 2019

  Documentation data-protection/privacy-notice/ega-user-account

• 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

• eMERGE Network's Multi-Center Pilot of Pharmacogenetic Sequencing in Clinical Practice

  eMERGE-PGx is a multi-site test of the concept that sequence information can be coupled to electronic medical records (EMRs) for use in healthcare. The promise of personalized medicine - health care guided by each individual&apos;s biological characteristics - is being fostered by increasingly powerful and economical methods to acquire clinically relevant biomarkers from large numbers of people. One therapeutic area that seems especially ripe for an early test of the personalized medicine concept is pharmacogenomics (PGx) - the idea that individual variation in drug response includes a genomic component. Drug response variation is an accepted feature of virtually all drug treatments, and contemporary molecular biologic tools continue to identify key genes mediating drug metabolism, transport, and targets. Importantly, common variation in these genes is an increasingly well-recognized contributor, sometimes with large effects, to variation in drug responses. As a result, recommendations for genotype-guided therapy are increasing. These evidence-based recommendations, if implemented in health care practice, could reduce adverse drug events and improve time to therapeutic response. Through eMERGE-PGx, we are developing strategies for the optimal implementation of genetic sequence data into the clinical environment with the ultimate goal of improving patient care. Site 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. The PGx population selected for sequencing with the PGRNseq panel at CHOP is 1,650 children from CAG&#39;s biorepository with well-documented drug-related severe adverse events (SAEs) or EHR-based drug response profiles. SAEs were extracted from EPIC records and from CHOP&#39;s Adverse Event (AE) database, which documents every AE at CHOP. These AEs are classified by a medical review panel according to the causal relationship with the suspected drug into &#39;doubtful&#39;, &#39;possible&#39;, and &#39;probable&#39;. Individuals with events classified as probable, severe and objective, were selected for sequencing. The drugs more frequently associated with adverse events are antibiotics, antineoplastics, immunosuppressants and psychotropic drugs. This cohort constitutes 50% of the target population. The remaining subjects were selected using EHR-based algorithms that we have developed and validated at CAG for identifying patients not responding to ADHD medication (primarily atomoxetine) and patients refractory to antiepileptic treatment from responders. Cincinnati Children&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): 811 CCHMC samples were obtained from children, adolescents or young adults exposed to medication or at risk for needing medication of study interest. 55% of participants were exposed to one or more opioids and their DNA source was a CCHMC study-specific biobank; while 27% of participants were at risk for needing an opioid for surgical pain management and were newly recruited. The remainder of the cohort was exposed to methylphenidate and their DNA samples were obtained from a CCHMC study-specific biobank. The focus of Boston Children&#39;s Hospital eMERGE PGx project is on individuals with epilepsy. Samples were taken from a current pharmacogenomics study already in place through which DMET analysis was run and used as confirmation for PGRN-Seq results. A total of 109 samples were sent for PGRN-Seq analysis at University of Washington. The remaining 141 epilepsy samples were from Children&#39;s Hospital of Philadelphia and underwent testing with PGRN-Seq at CHOP. 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 data are from Geisinger patients who consent to participate in the MyCode project. MyCode participants agree to provide biological samples for broad research use, including genomic analysis, and for linking of sample data to information in the participant&#39;s Geisinger health record. The consent also permits sharing of de-identified data for research purposes. Group Health(GH)/University of Washington (UW): Potential 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 a participant 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): For this study, 750 subjects were selected and enrolled into PGx based on Vanderbilt&#39;s algorithm designed to enrich for patients who are most likely to receive one of three common drugs (Clopidogrel, Warfarin or Simvastatin) in the next 2-3 years. These patients were sent a letter of invitation and description of the PGx project. Follow-up phone calls were made, and interested subjects came in for a one time meeting to discuss the project and go through the informed consent with the research coordinator. If they were interested they signed the consent and HIPAA forms and gave blood. Subjects were chosen and enrolled into PGx independently of previous biobank participation. Mayo Clinic: The Right Drug, Right Dose, Right Time - Using Genomic Data to Individualize Treatment (The RIGHT Protocol) enrolled 1013 patients to test the hypothesis that prescribers could deliver genome-guided drug therapy at the point-of-care by using pharmacogenomic data preemptively integrated in the electronic medical record. Complete details regarding the study population have been previously described (Bielinski et al., 2014). Icahn School of Medicine at Mount Sinai School (Mt Sinai): Our study site is the Primary Care Associates (PCA) practice group of the Mount Sinai Faculty Practice Associates (FPA) of the Mount Sinai Medical Center in New York City. This practice has 12 physician providers. All patient encounters are documented and managed with EpicCare ambulatory electronic medical record. Active PCA Patients eligible for enrollment fulfilled the following criteria: a) age 50 or older receiving clinical care at Mount Sinai FPA PCA practice with at least one practice encounter within 18 months prior to commencement of enrollment; b) no history or current use of clopidogrel, warfarin, or simvastatin. Eligible patients were invited to participate through de novo recruitment by letter sent by their provider. Interested patients were screened for eligibility and enrolled to participate in the eMERGE PGX study on site by a dedicated research coordinator. In addition to de novo enrollment from clinical practice, patients of FPA PCA who had previously enrolled in Mount Sinai&#39;s BioMe Biobank program AND fulfilled eligibility criteria as stated under a) and b) were identified by chart review and samples sequenced at CIDR using PGRNseq platform (N=300). PGRNseq data from 291 samples passed stringent quality control and are included in the current data set. Furthermore, 56 of these patients carrying known and validated &#39;actionable&#39; variants affecting prescribing of clopidogrel, warfarin, and/or simvastatin were enrolled in the eMERGE PGX study following invitation through recontacting by the Principal Investigator of the BioMe Program. Northwestern University: Participants for this study were recruited from the General Internal Medicine (GIM) clinic at Northwestern Medical Group (NMG). Patients were selected for invitation to participate if they had been seen a minimum of two times over the last four years, having a high likelihood to receive a prescription for warfarin, Plavix, or a statin, and are seeing a physician who has agreed to allow their patients to be contacted for the study. We utilized an algorithm developed at Vanderbilt and tailored to our population which uses our EHR to estimate the probability that individuals will receive a prescription for warfarin, Plavix, or a statin in the next three years. Participants were sent a letter explaining the study prior to their GIM appointment and offered participation at the time of their visit. Participants were consented on-site and blood drawn after consent was obtained. The GIM clinic consists of 39 primary care physicians who provide approximately 80,000 patient encounters per year. As with any large primary care clinic, a significant proportion of patients in GIM clinic suffer from a variety of chronic health conditions, such as diabetes, hypertension, and coronary artery disease. Over 50,000 individuals have been seen by GIM doctors in the past 5 years; 11,562 of these patients have evidence of a statin prescription in the EHR, 3,436 have evidence of a warfarin prescription, and 1,872 have evidence of a Plavix prescription. Vanderbilt University: The more than 1000 participants enrolled into Vanderbilt&#39;s eMERGE PGx study were newly recruited from the Cardiology and Internal Medicine Clinics and the Hillsboro Medical Group within Vanderbilt University Medical Center (VUMC). Patients were selected based on a predictive algorithm estimating the patient&#39;s likelihood of receiving Clopidogrel, Warfarin, and/or Simvastatin. The algorithm identifies primarily older middle-aged patients, and the mean age of the study group is 74. The cohort is approximately 45% female with 75% of subjects self-identified as EA and 24% as AA. Subjects were consented in person by study personnel following a routine clinic visit and an introduction to the study staff by their doctor. VUMC is a comprehensive health care facility dedicated to patient care, research, and the education of health care professionals. Translational research into the causes and treatment of disease as well as studying fundamental biological properties is the primary focus of discovery at Vanderbilt. Clinical research is conducted in Vanderbilt University Hospital, the Nashville Veterans Administration Hospital, Meharry General Hospital and in their associated outpatient clinics. These hospitals and clinics, all associated with the Vanderbilt system, each have full time Vanderbilt faculty and medical housestaff and provide clinical care and participate in research programs. The Vanderbilt Clinic is comprised of more than 95 adult outpatient specialty practices and received over 1.5 million ambulatory visits in 2012-13. The Vanderbilt Heart and Vascular Institute offers a comprehensive heart program offering diagnosis, medical treatment, minimally invasive therapies, surgical intervention and disease management, tailored to each individual&#39;s unique needs. All programs within the Vanderbilt Clinic have survival figures that surpass the national average.

  Study phs000906

• Distribution of data using Live Distribution

  Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation access/download/files/live-outbox

• Projects

  Projects Jointly managed by the European Bioinformatics Institute (EMBL-EBI) in Cambridge (UK) and the Centre for Genomic Regulation (CRG) in Barcelona, the EGA provides an invaluable service to the worldwide biomedical research community. The teams leading the EGA are involved in several international partnerships and consortia in numerous scientific fields, where they contribute to ambitious projects. In addition to the project listed below, the EGA is in a long-standing partnership with the Global Alliance for Genomics and Health (GA4GH), as described on the dedicated page. On-going projects Project Duration Domain Funder Tags CANDLE | CANDLE project aims to conceptualise and advance the development of National Cancer Data Nodes (NCDNs) in European countries. These NCDNs will boost the reuse of cancer data for research, innovation and policy making, in order to improve diagnostics and treatment for cancer patients, as well as prevention and early detection. 2025-2028 Cancer Horizon Europe DOCUMENTATION EASIGEN-DS | The EASIGEN-DS project aims to conduct a design study to establish a new European Research Infrastructure on Advanced Genomics Technologies, EASIGEN. To develop an excellent scientific, technological and operational design, we will conduct landscape studies, stakeholder consultations, and community surveying. 2025-2028 Genomic and health data Horizon Europe DATA MANAGEMENT DOCUMENTATION INFRASTRUCTURE Go-IMPaCT | Go-IMPaCT will contribute sequenced genomes and provide infrastructure as part of IMPaCT-Cohort, one of the three fundamental pillars of the Precision Medicine Infrastructure associated with Science and Technology (IMPaCT) program in Spain. Along with the Genome of Europe (GoE) project, around 18.000 people will have their genomes sequenced, also contributing to Spain's commitments in 1+MG. Go-IMPaCT will fund the development of an EGA node to manage and share this genomic and phenoclinic data, laying the foundations for regional and ethnic genomic variability in Spain to be available for research purposes. The IMPaCT cohort is created with the spirit of being an open research tool, compatible with the rest of the health research ecosystem, and other international initiatives. 2025-2027 Large-scale genomics and health data; personalised medicine Instituto de Salud Carlos III ACCESS DISCOVERY INFRASTRUCTURE METADATA STANDARDS FAIR-FEGA | This project seeks to accelerate data depositions into FEGA, significantly increasing the data flow in and from FEGA nodes. It will build capacity within the FEGA nodes and increase awareness in a wide range of stakeholders, thus altogether achieving the ultimate goal of enhancing data reuse. The project will be carried out by a strategic consortium comprising seven ELIXIR nodes and two ELIXIR communities. 2025-2026 Not applicable ELIXIR ACCESS DISCOVERY DOCUMENTATION INFRASTRUCTURE METADATA STANDARDS FEGA-Connect | A consortium of six ELIXIR nodes plus the Polish FEGA node (in-kind contribution) joining forces to build a solid base to develop solutions for effective multi-omic sensitive data integration between FEGA nodes and other infrastructures and specialised Data repositories. We aim to promote a more coherent data deposition, discoverability and retrieval of multi-omics datasets, providing FAIRer data and consequently accelerating research. 2025-2026 Multi-omics data ELIXIR ACCESS DATA MANAGEMENT DISCOVERY INFRASTRUCTURE METADATA STANDARDS IMPaCT-Data 2 | IMPaCT-Data 2 will develop a digital platform for the integration and modelling of biomedical data associated with IMPaCT (Precision Medicine Infrastructure associated with Science and Technology) projects in Spain. It will deploy a sustainable infrastructure that facilitates the integration, standardisation, interoperability and analysis of clinical, genomic, molecular and medical imaging data. This platform will be aligned with European projects such as Genome of Europe (GoE), the first project to make use of the European Genomic Data Infrastructure (GDI), and EUCAIM. IMPaCT-Data 2 will benefit from advanced Artificial Intelligence and High Computing Capacity Systems capabilities, offering robust and accessible tools for researchers from the National Health System in Spain. 2025-2026 Large-scale genomics and health data; personalised medicine Instituto de Salud Carlos III ACCESS DISCOVERY INFRASTRUCTURE METADATA STANDARDS SenSec | This project aims to establish a mechanism for orchestrating secure access to sensitive data hosted by the EGA, whether in Central EGA or any Federated Node, from Galaxy, a popular open-source, community-driven VRE (Virtual Research Environment) for bioinformatics analysis. Building on a previous prototype that enabled Galaxy users within Trusted Research Environments (TREs) to decrypt sensitive data for workflow execution without sharing private encryption keys, SenSec will expand this prototype into a comprehensive solution for secure data analysis in Galaxy, facilitating encrypted data access and transfer from FEGA/EGA repositories to designated TREs. 2025-2026 Genomic and health data; trusted research environment ELIXIR ACCESS DATA ANALYSIS ERDERA | The European Rare Disease Research Alliance (ERDERA) takes over EJPRD to deliver concrete health benefits to rare disease patients in the next decade by advancing prevention, diagnosis and treatment research. To leave no one behind, over 170 organisations championed by the European Union and member states are working hand in hand to make Europe a world leader in rare diseases research and innovation. 2024-2034 Rare diseases Horizon Europe; "La Caixa" Foundation cofunds CRG's contribution ACCESS DATA ANALYSIS DISCOVERY INFRASTRUCTURE SYNTHIA | The aim of SYNTHIA is to deliver validated, reliable tools and methods for synthetic data generation (SDG). The tools will cover multiple data types including lab results, clinical notes, genomics, imaging and m-health data. SYNTHIA also hopes to make possible the generation of longitudinal data. 2024-2029 Genomic and health data; multi-omics; AI solutions Innovative Health Initiative (IHI) DATA ANALYSIS DATA MANAGEMENT INFRASTRUCTURE GoE | The Genome of Europe initiative aims to build a European network of national genomic reference cohorts of at least 500.000 citizens. These reference cohorts will be selected to be representative of the European population. 2024-2028 Large-scale genomic and health data Horizon Europe ACCESS DISCOVERY INFRASTRUCTURE METADATA STANDARDS HEREDITARY | HEREDITARY aims to transform the way we approach disease detection, prepare treatment response, and explore medical knowledge by building a robust, interoperable, trustworthy, and secure framework that integrates multimodal health data (including genetic data) while ensuring compliance with cross-national privacy-preserving policies. 2024-2027 Neurodegenerative disorders, gut-brain interplay Horizon Europe DATA MANAGEMENT DATA ANALYSIS EOSC-ENTRUST | The mission of EOSC-ENTRUST is to create a European network of trusted research environments for sensitive data and to drive European interoperability by joint development of a common blueprint for federated data access and analysis. 2024-2026 Trusted Research Environment Horizon Europe INFRASTRUCTURE EBV-MS | "Targeting Epstein-Barr Virus Infection for Treatment and Prevention of Multiple Sclerosis". The ambitious goals of the project are to answer the questions why only a few EBV infected persons develop MS, and define the underlying mechanism of this process, as well as clarify if targeting the EBV infection can prevent MS or improve the disease course. 2023-2028 Viral-host genetics; immune response; disease modelling; disease prevention; AI/ML solutions Horizon Europe DATA MANAGEMENT DATA ANALYSIS WISDOM | WELL-BEING IMPROVEMENT THROUGH THE INTEGRATION OF HEALTHCARE AND RESEARCH DATA AND MODELS WITHOUT BORDER FOR CHRONIC IMMUNE-MEDIATED DISEASES aims to deploy novel approaches for data processing, harmonisation, management, and secure data sharing and federated access for diseases like multiple sclerosis. Using an end-user guided approach, it will facilitate responsible and critical assessment of the use of AI in healthcare. 2023-2028 Chronic immune-mediated diseases Horizon Europe DATA MANAGEMENT INFRASTRUCTURE EUCAIM | EUropean Federation for CAncer IMages is a project that will build a highly secure, federated and large-scale European cancer imaging platform, with capabilities that will greatly enhance the potential of Artificial Intelligence in oncology. 2023-2027 Cancer Digital Europe Programme (DIGITAL) DISCOVERY CONTAGIO | CONTAGIO (COhorts Network To be Activated Globally In Outbreaks) aims to create coordination mechanisms to rapidly react to infectious disease (re-)emergence in low- and middle-income countries (LMICs). 2023-2026 Infectious Diseases European Commission - Horizon Europe ACCESS DATA MANAGEMENT DISCOVERY Youth-GEMs | Youth-GEMS (Gene Environment Interactions in Mental Health TrajectorieS of Youth) will conduct research into the genetic and environmental factors of mental health in young European people. 2022-2027 Mental health European Commission - Horizon Europe DATA MANAGEMENT DISCOVERY GDI | The European Genomics Data Infrastructure 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. 2022-2026 Genomic and health data European Commission - Horizon Europe; "La Caixa" Foundation cofunds CRG's contribution DISCOVERY DOCUMENTATION INFRASTRUCTURE IMPaCT-T2D | The IMPaCT-T2D project aims at studying the complete genomes of a large cohort of patients with Type 2 Diabetes mellitus (T2D), using modern sequencing technologies and artificial intelligence (AI) in order to improve the stratification and pharmacological treatment in the context of precision medicine. 2022-2025 Cardiovascular and Complex Diseases Spanish Ministry of Science and Innovation; Instituto de Salud Carlos III ACCESS DATA MANAGEMENT DISCOVERY INFRASTRUCTURE Completed projects Project Duration Domain Funder Tags EOSC4Cancer | EOSC4Cancer builds on existing projects, research outcomes and established community solutions to create the federated FAIR data, analysis and services infrastructure needed for European Cancer research programmes. 2022-2025 Cancer European Commission - Horizon Europe DISCOVERY EuCanImage | A European Cancer Image Platform Linked to Biological and Health Data for Next-Generation Artificial Intelligence and Precision Medicine in Oncology. 2020-2025 AI Solutions in Oncology European Commission - H2020 Programme; "La Caixa" Foundation cofunds CRG's contribution DATA MANAGEMENT METADATA STANDARDS GenoMed4ALL | A consortium built to empower personalised medicine in the field of haematological diseases through the use of AI and the pooling of genomic and clinical data. 2020-2025 Hematological diseases European Commission - H2020 Programme DISCOVERY METADATA STANDARDS BY-COVID | The BeYond-COVID project aims to make COVID-19 data accessible to scientists in laboratories but also to anyone who can use it, such as medical staff in hospitals or government officials. Going beyond SARS-CoV-2 data, the project will provide a framework for making data from other infectious diseases open and accessible to everyone. 2021-2024 Infectious diseases European Commission - H2020 Programme ACCESS DATA MANAGEMENT DISCOVERY INFRASTRUCTURE IMPaCT-Data | IMPaCT-Data aims to create the infrastructure for secondary use of data from Spanish healthcare systems - electronic health records, medical imaging and genomic repositories - and contribute with the knowledge and methodology produced to the healthcare system. 2021-2024 Large-scale genomics and health dataSpanish Ministry of Science and Innovation; Instituto de Salud Carlos III ACCESS DATA MANAGEMENT DISCOVERY INFRASTRUCTURE LaMarato | It is a project aimed at creating and developing a catalan interhospitalary network to interrogate genetic variants from thousands of genetic tests carried out in patients with rare diseases from the main catalan hospitals. 2021-2024 Genomic and health data Fundacio La Marato de TV3 (catalan foundation) DISCOVERY HealthyCloud | This consortium will contribute a Strategic Agenda towards the European Health Research and Innovation Cloud. The project will work in collaboration with a broad range of stakeholders to ensure that all voices are included and that the results are technically and ethically sound. 2021-2023 Not Applicable European Commission - H2020 Programme DOCUMENTATION B1MG | Beyond 1 Million Genomes aims to create a network of genetic and clinical data across Europe. The project provides coordination and support to the 1+ Million Genomes Initiative (1+MG). This initiative is a commitment of 24 EU countries, the UK and Norway to give cross-border access to one million sequenced genomes by 2022. 2020-2023 Not applicable European Commission - Horizon Europe DATA MANAGEMENT INFRASTRUCTURE METADATA STANDARDS ELIXIR-CONVERGE | An alliance with the goal of Connecting and aligning ELIXIR Nodes to deliver sustainable FAIR life-science data management services. 2020-2023 Data Management and Infectious Diseases European Commission - H2020 Programme DATA MANAGEMENT INFRASTRUCTURE METADATA STANDARDS IHCC | The International HundredK+ Cohorts Consortium aims to create a global platform for translational research ? informing the biological and genetic basis for disease and improving clinical care and population health. 2020-2022 Translational research NIH; The Wellcome Trust; CZI INFRASTRUCTURE METADATA STANDARDS PPCG | The Pan Prostate Cancer Group aims to harmonise and interrogate Whole Genome DNA Sequence data generated around the world from over 2000 men with prostate cancer, with associated transcriptome and methylome data to include men from different clinical categories, and ethnicities. This project is about providing breakthrough advances through analysis of a very large series of Whole Genome DNA data from prostate cancer contributed by many of the leading scientists and clinicians working in prostate cancer genomics. 2019-2024 Cancer Cancer Research UK DATA MANAGEMENT CINECA | Consortium providing a Federated solution enabling population-scale genomic and biomolecular data accessible across international borders accelerating research and improving the health of individuals resident across continents. 2019-2023 Large-scale Genomics and Health Data European Commission - H2020 Programme ACCESS DATA MANAGEMENT DISCOVERY INFRASTRUCTURE EASI-Genomics | A project designed to provide easy access to cutting-edge DNA sequencing technologies to researchers from academia and industry, within a framework that ensures compliance with ethical and legal requirements, as well as FAIR and secure data management. 2019-2023 Next Generation Sequencing European Commission - H2020 Programme ACCESS EJP-RD | An European consortium built to create a comprehensive, sustainable ecosystem allowing a virtuous circle between research, care, and medical innovation. 2019-2023 Rare diseases European Commission - H2020 Programme ACCESS DATA MANAGEMENT DOCUMENTATION METADATA STANDARDS EOSC-Life | EOSC-Life brings together the 13 Life Science research infrastructures (LS RIs) to create an open, digital and collaborative space for biological and medical research. The project will publish 'FAIR' data and a catalogue of services provided by participating RIs for the management, storage and reuse of data in the European Open Science Cloud (EOSC). 2019-2023 Not applicable European Commission - H2020 Programme DOCUMENTATION EUCANCan | A federated network aiming at implementing a cultural, technological and legal integrated framework across Europe and Canada, to enable and facilitate the efficient sharing of cancer genomic data. 2019-2023 Cancer European Commission - H2020 Programme DATA MANAGEMENT METADATA STANDARDS The Federated EGA framework: supporting sensitive data management across the ELIXIR Nodes | This project is a direct continuation of the FHD IS with the goal to position the FEGA framework as the core infrastructure driver to support human data sharing for research. 2019-2023 Human genomic data ELIXIR INFRASTRUCTURE UK Biobank | UK Biobank is a large-scale biomedical database and research resource, containing in-depth genetic and health information from half a million UK participants. This project is to archive whole genome sequencing and other genetic data for UK Biobank participants. 2019-2023 Large-scale Genomics and Health Data The Wellcome Trust; UKRI; Amgen; AstraZeneca; GSK; Johnson & Johnson DATA MANAGEMENT INFRASTRUCTURE VEIS | The core mission of VEIS is to create an open ecosystem of technologies that will address and adapt to the requirements of the systems used to analyse and interpret -omics and clinical data in research and application environments in biomedicine. The aim of the project is to leverage the value of the EGA for both industry and society. 2019-2022 Oncology and Rare diseases Generalitat de Catalunya and European Regional Development Fund (ERDF) ACCESS DISCOVERY ELIXIR BEACON IS | This study follows on from a number of earlier activities that have established the ELIXIR Beacon Project. The main aim is to extend the Beacon protocol, developed at EGA, to become the reference ELIXIR Data Discovery product 2019-2021 Not applicable ELIXIR DISCOVERY ELIXIR FHD IS | This project coordinates the delivery of FAIR compliant metadata standards, interfaces, and reference implementation to support the federated ELIXIR network of human data resources. 2019-2021 Human genomic data ELIXIR INFRASTRUCTURE ELIXIR Rare Disease | The Rare Disease Community extends and generalises the system of access authorisation and high volume secure data transfer developed within the EGA. The goal of the Community is to create a federated infrastructure that will enable researchers to discover, access and analyse different rare disease repositories across Europe. It is doing this in partnership with other European infrastructure projects, namely RD-CONNECT, BBMRI-ERIC and E-Rare.2019-2021 Rare diseases ELIXIR INFRASTRUCTURE Solve-RD | Solve-RD - solving the unsolved rare diseases - is a research project funded by the European Commission. It echoes the ambitious goals set out by the International Rare Diseases Research Consortium (IRDiRC) to deliver diagnostic tests for most rare diseases by 2020. The current diagnostic and subsequent therapeutic management of rare diseases is still highly unsatisfactory for a large proportion of rare disease patients - the unsolved RD cases. For these unsolved rare diseases, we are unable to explain the etiology responsible for the disease phenotype, predict the individual disease risk and/or rate of disease progression, and/or quantitate the risk of relatives to develop the same disorder. 2018-2024 Rare diseases European Commission - H2020 Programme ACCESS DATA MANAGEMENT METADATA STANDARDS EuCanShare | An EU-Canada joint infrastructure for next-generation multi-Study Heart research. 2018-2022 Cardiovascular Diseases European Commission - H2020 Programme ACCESS METADATA STANDARDS

  Documentation about/projects-and-funders/projects

• How to upload Crypt4GH files

  Uploading files Users who hold 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. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs)  for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username.  If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days.  Specific to using keys to authenticate Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation submission/data/uploading-files/inbox

• 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

• 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 Consortium - Lung Cancer Studies

  The study was conducted under the auspices of the Transdisciplinary Research In Cancer of the Lung (TRICL) Research Team, which is a part of the Genetic Associations and MEchanisms in ONcology (GAME-ON) consortium, and associated with the International Lung Cancer Consortium (ILCCO). Ethics: All participants provided written informed consent. All studies were reviewed and approved by institutional ethics review committees at the involved institutions. Sequencing data are derived from four substudies. The substudies that contributed include Harvard, Liverpool, Toronto, and IARC. The Alpha-Tocopherol, Beta-Carotene Cancer Prevention (ATBC) Study is a randomized primary prevention trial including 29,133 male smokers enrolled in Finland between 1985 and 1993. Participants ranged between ages of 50 to 69 at enrollment and were randomized in a factorial design to take either 50 milligrams of d-alpha tocopheryl acetate (Vitamin E), 20 mg of all-trans-beta-carotene, both or placebo. The study continued to monitor cancer incidence through 2012 and total mortality through December 2013. The CAncer de PUlmon en Asturias Study (CAPUA) is a hospital-based case-control study conducted in Asturias, Spain by the University of Oviedo. Lung cancer cases were recruited in three main hospitals of Asturias, following an identical protocol from 2002 to 2012. Eligible cases were incident cases of histologically confirmed lung cancer between 30 and 85 years of age and residents in the geographical area of each participating hospital. Controls were selected from patients admitted to those hospitals with diagnoses unrelated to the exposures of interest and individually matched by ethnicity, gender, age (&#177; 5 years) and hospital. Epidemiologic data were collected personally through computer-assisted questionnaires by trained interviewers during the first hospital admission. Structured questionnaires collected information on sociodemographic characteristics, recent and prior tobacco use, environmental exposure (air pollution and passive smoking), diet, personal and family history of cancer, and occupational history from each participant. Peripheral blood samples (or mouthwash samples when they refused to donate blood) were collected from all participants. Coding of histology was based on 2001 WHO/IASLC. Genomic DNA was extracted based on standard protocol. The Canadian Screening Study includes the nested case-control samples from 3 screening programs: IELCAP-Toronto: Ever smokers of more than 10 pack-years age 50 and above were eligible for the I-ELCAP screening program since 2003, and a total of 4782 individuals have been enrolled in the Greater Toronto Area. Participants were administered a LDCT scan along with a standard study questionnaire at baseline. Blood samples were systematically collected at baseline since 2006. Participants who had an abnormality in a CT scan were followed up every 1 to 2 years. The screening program was organized by the Princess Margaret Hospital. PanCan: Ever smokers between the ages of 50-75 with no previous history of invasive cancer are eligible to participate in the study. The study was carried out across Canada in Vancouver, Calgary, Hamilton, Toronto, Ottawa, Quebec, Halifax, and St. John's. A total of 2537 smokers have been screened from 2008 to 2011. All study participants completed a detailed questionnaire, spirometry, collection of blood specimens for biomarker measurement and LDCT at baseline. All participants are followed for a minimum of 3 years. On yearly follow up, an updated shorter questionnaire is administered, blood is collected and CT scans are performed. Blood samples are available from all 2537 individuals. BCCA Screening Program: From 1990 to 2007, 4274 smokers above 40 years old who had smoked 20 pack-years or more were enrolled at BCCA. Upon enrollment, subjects completed a questionnaire for their lifestyle and medical history. Baseline spirometry was conducted using a flow-sensitive spirometer in accordance with the American Thoracic Society recommendations. Since 2000, a LDCT was obtained in 2440 individuals. The participants were followed prospectively to determine whether they developed lung cancer. A total of 9759 individuals participated in the CT screening program in Canada from these 3 programs. The samples included in this project is based on a subset of nested lung cancer case-control pairs based on 1:2 ratio. The Carotene and Retinol Efficacy Trial (CARET) was a randomized, double-blind, placebo-controlled trial of the cancer prevention efficacy and safety of a daily combination of 30 mg of beta-carotene and 25,000 IU of retinyl palmitate in 18,314 persons at high risk for lung cancer. CARET began in 1985, and the intervention was halted in January 1996, 21 months ahead of schedule, with the twin conclusions for definitive evidence of no benefit and substantial evidence of a harmful effect of the intervention on both lung cancer incidence and total mortality. CARET continued to follow and collect endpoints on their participants through 2005. Pathology reports and medical records were reviewed to confirm cancer endpoints, and death certificates obtained to capture cause of death. During the active intervention phase of CARET, serum, plasma, whole blood, and lung tissue specimens were collected on participants. These biospecimens make up the CARET Biorepository. For the OncoArray Project, CARET provided DNA extracted from whole blood of lung cancer cases and controls matched on age at baseline (&#177; 4 years), sex, race, baseline smoking status, history of occupational asbestos exposure (asbestos vs heavy smoker), and year of enrollment (2-year intervals). The European Prospective Investigation into Cancer and Nutrition (EPIC) study is a multi-center cohort study involving 521,000 study participants from 10 European countries. The current study involved EPIC participants from 7 countries (Greece, Netherlands, UK, France, Germany, Spain, and Italy), including 1223 incident lung cancer cases and 1249 smoking matched controls. The Kentucky Lung Cancer Research Initiative is a study conducted by the Markey Cancer Center Cancer Center and the University of Kentucky using a population-based, case-control framework to study the extraordinarily high rates of lung cancer in Southeastern, Appalachian Kentucky. Cancer cases were recruited from the Kentucky Cancer Registry at the time of diagnosis and controls were recruited from a random digit dialing process from the same region. Study accrual began in January 5, 2012 and completed on September 5, 2014 and 520 subjects were recruited in a 4:1 ratio of controls: cases from Appalachian Kentucky. Of the 520 subjects recruited, 231 are included in the OncoArray analysis, including all 93 cancer cases, and 123 controls. Newly diagnosed lung cancer cases and controls underwent blood, toenail (for trace element analysis), urine, buffy coat, water, soil, and radon collection, residence GPS mapping, as well as an extensive epidemiologic, occupational, and health history questionnaire (Clinical Trials.gov Identifier: NCT01648166). The Harvard Lung Cancer Study (HLCS) is a case-control study based at Mass General Hospital (MGH) in Boston, Massachusetts from 1992 to 2004. Details of the study were described previously. Briefly, eligible cases included any person over the age of 18 years with a diagnosis of primary lung cancer that was further confirmed by an MGH lung pathologist. Controls were recruited from the friends or spouses of cancer patients or the friends or spouses of other surgery patients in the same hospital. Potential controls were excluded from participation if they had a diagnosis of any cancer (other than non-melanoma skin cancer). Interviewer-administered questionnaires, a modified version of the standardized American Thoracic Society respiratory questionnaire, collected information on demographics, medical history, family history of cancer, smoking history, and a detailed work history, including job titles and tasks. Genome-wide genotype data were first generated using Illumina Human 610-Quad BeadChips and then imputed by MACH against the 1000 Genome Project dataset (http://browser.1000genomes.org/index.html). The Institutional Review Board of MGH and the Human Subjects Committee of the Harvard School of Public Health approved the study. The Israel study (NICCC-LCA) is an ongoing case-control study of newly diagnosed lung cancer cases of any histology and population age/sex/ethnicity-matched "healthy" controls. All participants undergo face-to-face interviews, provide a venous blood sample (separated into DNA, Sera, lymphocytes) after signing an IRB-approved form. Histology reports, FFPE blocks and clinical follow-up are available for most cancer cases. The MD Anderson Cancer Center (MDACC) Study. Lung cancer cases and frequency-matched controls were ascertained from a large ongoing case-control study at the University of Texas MD Anderson Cancer Center (UTMDACC) since 1991. Detailed study description was provided previously (Spitz et al 2007). In brief, cases were newly-diagnosed and histologically confirmed lung cancer patients recruited from UTMDACC. Controls were healthy individuals without a history of cancer (except for nonmelanoma skin cancer) and recruited from the Kelsey-Seybold Clinics, the largest private multispecialty physician group in the Houston metropolitan area. Controls were frequency-matched to cases on age (&#177;5 years), sex, and race/ethnicity. After providing written informed consent, each study participants completed an in-person interview by staff interviewers to collect information on demographics, smoking status, etc. Blood samples were also drawn from all the study participants. This study was approved by institutional review boards of UTMDACC and Kelsey-Seybold Clinics. The Malm&#246; Diet and Cancer Study (MDCS) is a population-based prospective cohort study that recruited men and women aged at 44 to 74 years old of living in Malm&#246;, Sweden between 1991 and 1996. The main goal of the MDCS is to study the impact of diet on cancer incidence and mortality. It consists of a baseline examination including dietary assessment, a self-administered questionnaire, anthropometric measurements and collection of blood samples. A total of 165 incident lung cancer cases and 174 individually smoking-matched controls were available for this analysis. The Multiethnic Cohort (MEC) Study includes 215,251 men and women aged 45-74 years at recruitment, primarily from five ethnic/racial groups - African Americans and Latinos mostly recruited from CA (mainly from Los Angeles County) and Japanese Americans, Native Hawaiians and whites (mostly recruited from HI). The cohort was assembled in 1993-1996 by mailing a self-administered questionnaire to persons identified primarily through driver's license files. The baseline questionnaire obtained information on demographics, anthropometry, smoking history, medical and reproductive histories, family history of cancer, diet and physical activity. Incident cancer cases are identified by regular linkage with the State of California Cancer Registry and the Hawaii Tumor Registry, both members of the SEER Program of the NCI. In 2001-2006, a prospective biorepository was assembled by collecting a pre-diagnostic blood specimen from 67,594 surviving MEC members. At the time of blood collection a short questionnaire was administered that included information on smoking during the previous 15 days. For this study, cases were all lung cancer cases incident to blood draw and diagnosed before December 2012. For each case, a control was selected among unaffected MEC participants who were alive at time of the case's diagnosis and matched on study site, sex, race/ethnicity, age (age at diagnosis for cases; age at blood collection for controls), and date of blood collection. The Mount-Sinai Hospital-Princess Margaret Study (MSH-PMH) was conducted in the greater Toronto area from 2008 to 2013. Lung cancer cases were recruited at the hospitals in the network of the University of Toronto. Controls were selected randomly from individuals registered in the family medicine clinics databases and were frequency matched with cases on age and sex. All subjects were interviewed, and information on lifestyle risk factors, occupational history and medical and family history was collected using a standard questionnaire. Tumors were centrally reviewed by the reference pathologist, a member of the International Association for the Study of Lung Cancer (IASLC) committee, and a second pathologist in the University Health Network. If the reviews conflicted, a consensus was arrived at after discussion. Coding of histology was based on 2001 WHO/IASLC. Genomic DNA was extracted based on standard protocol. The New England Lung Cancer Study (NELCS) is a population-based case-control study of lung cancer among residents of Northern and Central New Hampshire counties and the bordering region of Vermont. Cases with histologically confirmed primary incident lung cancer were identified from 2005 to 2007 using the New Hampshire State Cancer Registry and the Dartmouth-Hitchcock Medical Center (DHMC) Tumor Registry. Control participants were identified using a commercial database and matched to lung cancer cases within 5-year age groups, sex and county. Genomic DNA was isolated from blood or buccal specimens provided by consenting participants. The study complied with requirements of the Dartmouth College's Committee for Protection of Human Subjects. The Nijmegen Lung Cancer Study. The Netherlands patients with lung cancer were identified through the population-based cancer registry of the Netherlands Comprehensive Cancer Organisation in Nijmegen, the Netherlands. Patients who were diagnosed in one of three hospitals (Radboud University Medical Center, Canisius Wilhelmina Hospital in Nijmegen, and Rijnstate Hospital in Arnhem) since 1989 and who were still alive at April 15th, 2008 were recruited for a study on gene-environment interactions in lung cancer. 458 patients gave informed consent and donated a blood sample. This case series was expanded with 94 patients to a total of 552 by linking three other studies to the population-based cancer registry in order to identify new occurrences of lung cancer among the participants of these other studies. All three other studies (i.e., POLYGENE, the Nijmegen Biomedical Study, and the Radboudumc Urology Outpatient Clinic Epidemiology Study) were initiated to study genetic risk factors for disease and participants to these studies gave general informed consent for DNA-related research and linkage with disease registries. Information on histology, stage of disease, and age at diagnoses was obtained through the cancer registry. Lifestyle information was collected through a structured questionnaire and whole blood for DNA isolation was collected by the regional thrombosis services. The cancer-free controls (46% males) were selected from participants of the "Nijmegen Biomedical Study" (NBS), an age- and sex-stratified random sample of the general population of the municipality of Nijmegen, The Netherlands. All participants provided extensive lifestyle information by structured questionnaires and blood samples for DNA isolation, serum and plasma. All controls are of self-reported European descent. The study protocols of the NBS were approved by the Institutional Review Board of the Radboudumc and all study subjects signed a written informed consent form. The Northern Sweden Health and Disease Study (NSHDS) encompasses several prospective cohorts. The current study involves participants from the V&#228;sterbotten Intervention Project (VIP), a sub-cohort within NSHDS. VIP is an ongoing prospective cohort and intervention study intended for health promotion of the general population of the V&#228;sterbotten County in northern Sweden. VIP was initiated in 1985 and all residents in the V&#228;sterbotten County were invited to participate by attending a health check-up at 40, 50 and 60 years of age. Participants were asked to complete a self-administered questionnaire including various demographic factors such as education, smoking habits, physical activity and diet. In addition, height and weight were measured and participants were asked to donate a fasting blood sample for future research. A total of 243 incident lung cancer cases and 266 individually smoking-matched controls were available for this analysis. Norway National Institute of Occupational Health Study. Early-stage NSCLC cases and healthy controls at the time of enrollment were Caucasians of Norwegian origin and were recruited from the same geographical region (Western Norway). The patients were enrolled in the study, whenever practically feasible among patients admitted for lung cancer at the Haukeland University Hospital in Bergen, Norway. The informed written consents covering analysis of molecular and genetic markers was signed by the patients prior to surgery. Only patients with histologically confirmed early-stage NSCLC were included in our study. The subjects included in this project are a subgroup recruited into the project "lung cancer genetics" at NIOH. The controls were recruited from the same geographical region of Western Norway and frequency-matched with cases on cumulative smoking dose (pack-years). Pack-years smoked [( 20 cigarettes per day) x years smoked] were calculated to indicate the cumulative smoking dose. The Cases and controls were interviewed using similar questionnaires and were categorized as never smokers, ex-smokers or current smokers. Never smokers are subjects indicating having smoked less than 100 cigarettes in their life time. Ex-smokers were defined as those having quitted at least 1 year before sampling, and current smokers were those indicating that they were smokers at the time of sampling. The project has been approved by the Regional Committee for Medical and Health Research Ethics in Southern Norway in accordance with the WMA Declaration of Helsinki. The ethical approval covered access to the NSCLC databank. The Prostate, Lung, Colorectal, and Ovarian Cancer Screening Trial (PLCO) Study, a randomized trial aimed at evaluating the efficacy of screening in reducing cancer mortality, recruited approximately 155,000 men and women age 55 to 74 years from 1992 to 20014. Screening for lung cancer among participants in the intervention arm included a chest x-ray at baseline followed by either three annual x-rays (for current or former smokers at enrollment) or two annual x-rays (for never smokers); participants in the control arm received routine health care. Screening-arm participants provided data on sociodemographic factors, smoking behavior, anthropometric characteristics, medical history, and family history of cancer, as well as blood samples annually for the first 6 years of the study (baseline T0 and T1 through T5). Lung cancers were ascertained through annual questionnaires mailed to the participants, and positive reports were followed up by abstracting medical records or death certificates. Follow-up in the trial as of July 2009 was 96.7%. Patients were excluded because of missing baseline questionnaire, previous history of any cancer, diagnosis of multiple cancers during follow-up, missing smoking information at baseline, missing consent for utilization of biologic specimens for etiologic studies, or unavailability/insufficient quantity of serum or DNA specimens. The Resource for the Study of Lung Cancer Epidemiology in North Trent (ReSoLuCENT) is an ongoing study conducted in Sheffield from 2006 and due to complete recruitment in 2016. The study recruited pathologically confirmed lung cancer cases diagnosed at age 60 years or younger and family matched controls. Lung cancer cases diagnosed at ages older than 60 years were recruited if they reported a family history of lung cancer. The cases and matched controls were recruited through several major cancer treatment centers, however, the majority were recruited in North Trent. All participants completed a detailed lifestyle questionnaire which included questions about occupational exposures, education, medical history and family history of cancer and lung disease. Participants also donated blood samples for DNA extraction. The ReSoLuCENT study has been funded by the Sheffield Hospitals Charity, Sheffield ECMC and Weston Park Hospital Cancer Charity. First degree relatives were removed from the sample deposited to dbGaP. The Roy Castle Lung Study of Liverpool Lung Project (LLP) is a case-control and cohort study which has recruited over 11,500 individuals since 1996 from the Liverpool region in the UK. Detailed epidemiological and clinical data is collected with associated specimens (i.e. tumor tissue, blood, plasma, sputum, bronchial lavage and oral brushings). The participants have completed a detailed lifestyle questionnaire at recruitment, with repeat questionnaires at intervals; updated data on clinical outcome and hospital events are collected through the Health and Social Care Information Center (including Office of National Statistics mortality data, Cancer Registry and Health Episode Statistics). The project is registered on the UK National Institute for Health Research (NIHR) lung cancer portfolio and has all the required ethical approvals and sponsorship arrangements in place. The lung tumors were reviewed by the reference pathologist. The Seoul Bundang Lung Cancer Study was conducted between 2005 and 2010 to discover genetic and environmental factors related with lung cancer development. Lung cancer cases were recruited at the Seoul National University Hospital in Bundang. Controls were selected randomly from individuals participated in health check-up program and were frequency matched with cases on age and sex. All subjects were interviewed, and information on lifestyle risk factors, occupational history and medical and family history was collected using a standard questionnaire. Tumors were reviewed by the pathologists in the hospital. If the reviews conflicted, a consensus was arrived at after discussion. Coding of histology was based on 2001 WHO/IASLC. Genomic DNA was extracted based on standard protocol. The Shanghai Cohort Study (SCS) consisted of 18,244 men in Shanghai, China, who were 45-64 years old at the time of enrollment during 1986-1989. Approximately 80% of eligible men participated in the study. At the time of recruitment, each cohort subject was interviewed in-person by a trained nurse interviewer using a structured questionnaire that included background information, history of tobacco and alcohol use, current diet, and medical history. At the completion of the interview, the nurse collected a 10 ml blood and a single void urine specimen from the study participant. The buccal cell samples were collected from all surviving cohort members (~15,000) in the 2001-2002 follow-up interviews. The cohort has been followed for the occurrence of cancer and death through routine ascertainment of new cases from the population-based Shanghai Cancer Registry and Shanghai Vital Statistics Units. To maximize the cancer findings and minimize the loss of follow-up, we contacted each surviving cohort member annually. Retired nurses visit the last known address of each living cohort member and record details of the interim health history of the cohort member. As of December 31, 2014, cumulatively 612 (3.4%) original subjects were lost to follow-up, and 574 (3.1%) refused to our continued follow-up interview. A nested case-control study of incident lung cancer cases within the Shanghai Cohort Study was used to examine the association between serum levels of vitamin B6 and other compounds in the one-carbon metabolism pathway and risk of lung cancer. Briefly, 516 lung cancer cases were identified among cohort participants with available serum samples as of 12/31/2006. For each case, we randomly selected one control subject from all cohort members who were free of cancer and alive at the time of cancer diagnosis of the index case. Controls were matched to the index case by age at enrollment (&#177;2 years), date of biospecimen collection (&#177;1 month) and neighborhood of residence at recruitment, and smoking status (current, former and never smokers) as established previously for other studies. For former smokers, cases and controls were further matched by years since quitting smoking (&lt;10 vs &#8805;10 years). One serum vial per subject was retrieved from biorepository and all serum samples were sent to the laboratory (B-vital) for measurements. DNA samples of 250 lung cancer cases and 250 matched controls were available for the present study. The Singapore Chinese Health Study (SCHS) cohort consisted of 63,257 Chinese men and women in Singapore when they were 45-74 years old at the time of enrollment between April 1993 and December 1998. At recruitment, each study subject was interviewed in person by a trained interviewer using a structured questionnaire that emphasized current diet assessed via a validated, 165-item food frequency questionnaire. The questionnaire also requested information on demographics, lifetime use of tobacco, incense use, current physical activity, usual sleep duration, reproductive history (women only), occupational exposure, medical history, and family history of cancer. Blood or buccal cell, and spot urine samples were collected first from a random 3% sample of cohort participants in April 1994, and extended to all surviving cohort participants starting in January 2000. Overall approximately 60% of eligible cohort participants donated biospecimens. The cohort has been passively followed for death and cancer occurrence through regular record linkage with the population-based Singapore Cancer Registry and the Singapore Registry of Births and Deaths. Migration out of Singapore, especially among housing estate residents, was negligible. As of latest update, only 55 individuals from this cohort were known to be lost to follow-up due to migration and other reason. A nested case-control study of incident lung cancer cases within the Singapore Chinese Health Study was used to examine the association between serum levels of vitamin B6 and other compounds in the one-carbon metabolism pathway and risk of lung cancer. As of 12/31/2011, 422 lung cancer cases were identified among cohort participants with available prediagnostic plasma samples. For each case, one control subject was randomly selected from all eligible cohort members who were alive and free of cancer on the date of cancer diagnosis of the index case. The control subject was individually matched to the index case by gender, dialect group (Hokkien, Cantonese), age at enrollment (&#177;3 years), date of baseline interview (&#177;2 year), date of biospecimen collection (&#177;6 months), and smoking status (current, former, and never smokers). For current smokers, cases and controls were further matched by number of cigarettes per day (&lt;15, &#8805;15 cigarettes/day). For former smokers, cases and controls were further matched by years since quitting smoking (&lt;10, &#8805;10 years). One plasma aliquot per subject was retrieved from the biorepository and all plasma samples were sent to the laboratory (B-vital) for measurements, and one aliquot of DNA per subject for the present study. The International Agency for Research on Cancer (IARC) L2 Study. Lung cancer cases and controls were recruited through a multicentric case-control study coordinated by the IARC in Russia, Poland, Serbia, Czech Republic, and Romania from 2005 to 2013. Cases were incident cancer patients collected from general hospitals. Controls were recruited from individuals visiting general hospitals and out-patient clinics for disorders unrelated to lung cancer and/or its associated risk factors, or from the general population. Information on lifestyle risk factors, medical and family history was collected from subjects by interview using a standard questionnaire. All study participants provided written informed consent. The current study included 1,133 lung cancer cases and 1,117 controls genotyped on the Oncoarray. The Washington State University Lung Cancer Study is a hospital case-control study of 511 subjects with newly-diagnosed (within 1 year of diagnosis) lung cancer and 820 race-, sex- and age-matched controls. Lung cancer cases were recruited from lung cancer clinics within the H. Lee Moffitt Cancer Center while controls were recruited from the Lifetime Cancer Screening Center, a H. Lee Moffitt Cancer Center affiliate. None of the controls were diagnosed with any form of cancer at the time of screening. Detailed questionnaire data and oral buccal cells were collected for all subjects. The Total Lung Cancer (TLC) Study is a hospital-based study that included 458 lung cancer patients recruited for Moffitt Cancer Center's Total Cancer Care&#8482; protocol between April 2006 and August 2010. Total Cancer Care&#8482; is a multi-institutional observational study of cancer patients that prospectively collects self-reported demographic and clinical data, medical record information and blood samples for research purposes. All patients used in this cohort were recruited from the Thoracic Oncology Clinic at the Moffitt Cancer Center. The Vanderbilt Lung Cancer Study (BioVU) is a case-control study nested within the Vanderbilt University Medical Center biobank, BioVU. BioVU is a biorepository of DNA extracted from blood drawn from patients seeking routine clinical care at Vanderbilt University Medical Center and linked to de-identified electronic health records for research purposes. Lung cancer cases and controls were identified from BioVU participants in February 2014. Lung cancer cases were identified from the Vanderbilt tumor registry. All specimens undergo pathologic review for determination of morphology. Coding of histology was based on SEER Program Coding Guidelines. Controls were randomly selected from BioVU participants, excluding cancer patients, and were matched to cases on age (&#177; 5 years), sex, and race. Relevant covariates were identified from electronic health records using natural language processing. Genomic DNA was extracted based on a standard protocol.

  Study phs001273