464 results for "GitHub+primate+acoustics+baboon+Zenodo+10.5281+Gui*"

in 235.34 milliseconds.

• Evaluation of Local Response of Prostate Cancer to Irradiation Using Multiparametric MRI and MR-Guided Biopsies

  The purpose of this study was to determine the rate of local recurrence in patients with intermediate and high risk prostate cancer treated with radiotherapy. In this study, multiparametric MRI was first performed, and biopsy tissue was acquired from cancerous regions detected on MRI. Blood samples were also taken. DNA and RNA were extracted from tissue taken at baseline. DNA was used for whole exome sequencing (WES). RNA was used for gene expression microarray. Each patient then received radiation therapy with androgen deprivation therapy.

  Study phs001821

• Kids First: The Genomic Architecture of Hirschsprung Disease (HSCR)

  Hirschsprung disease (HSCR) is a male biased developmental disorder associated with a lack of innervation of the gastrointestinal tract. Genetic studies have been instrumental in understanding its multifactorial inheritance, high heritability, syndromic associations, and genetic heterogeneity with variable penetrance and expressivity. At least 24 genes and 9 loci with pathogenic alleles (PAs) are known to underlie HSCR pathogenesis and explain 62% of its population attributable risk (PAR). Despite this heterogeneity, there is functional unity in HSCR: ~53% of HSCR PAs disrupt RET and EDNRB signaling in the developing enteric nervous system (ENS) in which 11 genes comprising a gene regulatory network control RET and EDNRB gene expression. We propose to identify the remaining 30% PAR by studying 857 unrelated HSCR cases, their 125 affected and 1,446 unaffected firstdegree relatives by whole genome sequencing to increase statistical power of gene discovery through improved detection of all types of coding and regulatory PAs. HSCR arises from cell autonomous defects in enteric neural crest cell precursors (ENCCs) affecting their proliferation, differentiation and migration in the ENS, functional studies that will guide our detection of novel genes.

  Study phs003662

• Convergent evolution towards CD38 biallelic loss is a recurrent mechanism of resistance to anti-CD38 antibodies in multiple myeloma.

  Monoclonal antibodies directed against CD38 are a therapeutic mainstay in multiple myeloma (MM). While they have contributed to improved outcomes, most patients will still experience disease relapse. Despite their ubiquity, little is known about tumor-intrinsic mechanisms of resistance to these drugs. Antigen escape, whereby tumor cells alter expression of cell surface immunotherapy targets, has been proposed as a potential avenue, and has been seen with other immunotherapies in MM. Yet, it is unknown whether MM cells can develop permanent resistance to anti-CD38 antibodies by acquiring genomic events leading to biallelic disruption of the CD38 gene locus. Here, by using whole genome and whole exome sequencing data from 701 newly diagnosed patients, 72 patients at relapse with naivety to anti-CD38 antibodies, and 52 patients collected at relapse following anti-CD38 antibodies, we report biallelic inactivation of CD38 as a recurrent mechanism of resistance in 6% of patients, often via convergent evolution where distinct subclones are advantaged towards the same selective endpoint within the same patient. Monoallelic loss of the CD38 locus was seen in another 14% post-CD38-directed therapy. Three of the cases with biallelic events on CD38 presented with missense mutations and retained CD38 expression. Functional work demonstrated that two of these mutations decreased binding affinity and antibody-dependent cellular cytotoxicity of commercial antibodies Daratumumab and Isatuximab. However, the third mutation (R140G) provided relative resistance only towards one commercial product. Given that patients are often rechallenged with CD38 antibodies following disease progression, these data support the need for next generation sequencing to guide treatment selection.

  Study EGAS50000000709

• Single-Cell TCR/BCR Sequencing for Korean COVID-19 Vaccinated and Patient Samples

  We conducted longitudinal single-cell TCR/BCR sequencing for COVID-19 vaccinated cases (297 samples from 112 cases) and COVID-19 infected cases classified as Asymptomatic (26 samples from 12 cases), Mild (82 samples from 37 cases), Moderate (123 samples from 50 cases), Severe (216 samples from 58 cases), and Critical (142 samples from 41 cases) according to the NIH guideline.

  Study phs003341

• Whole genome sequencing data of pediatric hypodiploid acute lymphoblastic leukemia

  Hypodiploid acute lymphoblastic leukemia (ALL) is a rare subtype of B-cell ALL characterized by chromosome number < 45 , encompassing near-haploid (24–29 chromosomes) and low-hypodiploid (30–39 chromosomes) subgroups. These subgroups display distinct genetic landscapes, including Ras and receptor tyrosine kinase pathway alterations in near-haploid ALL, and frequent IKZF2, RB1, and germline TP53 alterations in low-hypodiploid ALL. Clinically, hypodiploid ALL is associated with dismal prognosis, with 5-year overall survival rates often between 50-70% in children and markedly worse in adults. Despite advances in risk stratification and MRD-guided therapy, allogeneic stem cell transplantation remains the current standard recommendation for affected patients.

  Study EGAS50000001305

• Papua New Guinea Pangenome Project Data Access Policy

  This data policy applies to data access to the PNG15 and PNG16 sequencing data as well as derived genomic variant calls.

  Dac EGAC50000000674

• NHLBI TOPMed: TReating Children to Prevent EXacerbations of Asthma (TREXA)

  TREXA is a 44-week randomized, double-blind, double-masked, four-treatment, parallel trial that will evaluate the weaning strategy that provides the best protection against the development of exacerbations in children whose asthma is acceptably controlled on a low dose of ICS (per NAEPP guidelines). Following the 4 weeks of the run-in period on a 1x dose of ICS (100 &#181;g fluticasone b.i.d. or its equivalent), children who do not meet the definition of acceptable asthma control will be randomized to the parallel BADGER protocol; those who meet the definition of acceptable asthma control will be enrolled into the 44-week treatment phase of the study. The primary outcome measure will be time to first exacerbation requiring a prednisone course.

  Study phs001732

• Sequence data for "An allele-resolved nanopore-guided tour of the human placental methylome" (Kindlova et al 2025)

  Sequence data generated for the study "An allele-resolved nanopore-guided tour of the human placental methylome" includes Illumina WGS, Illumina RNA-seq, Illumina EM-seq, and Oxford Nanopore Technologies PromethION sequence data.

  Dataset EGAD50000001850

• Papua New Guinean Genome Altitude Project

  Study EGAS00001007085

• Single-Gene vs. Panel Sequencing in Advanced HR+/HER2− Breast Cancer

  Background: Hormone receptor-positive (HR+)/HER2-negative (HER2−) breast cancer is the most common subtype of breast cancer, with biomarker-driven therapies improving outcomes. Liquid biopsies, which analyze circulating tumor DNA (ctDNA), are increasingly essential in clinical management, offering a minimally invasive approach to assess somatic alterations and guide therapy decisions. However, the choice of assay directly affects clinical utility and global access to validated testing platforms remains inconsistent. To address these challenges, this study aimed to compare the performance of single-gene and panel-based sequencing for detecting PIK3CA mutations in HR+/HER2− breast cancer and evaluate the added value of broader genomic profiling in guiding treatment decisions. Patients and methods: We conducted a prospective, multicenter study comparing our previously established SiMSen-Seq (SSS) assay, a single-gene method targeting PIK3CA hotspot mutations, with the AVENIO ctDNA Expanded assay, enriching for 77 clinically relevant cancer genes. Additionally, tumor fractions were estimated with mFAST-SeqS by assessing chromosomal aneuploidy. We analyzed 161 plasma samples collected from 146 patients with HR+/HER2− advanced breast cancer before starting a new line of palliative therapy. Results: High concordance (92.6%) was observed between SSS and AVENIO for PIK3CA mutation detection, with accurate variant allele frequency (VAF) quantification confirmed by Bland-Altman analysis and linear mixed-effects modeling. AVENIO identified additional PIK3CA mutations in 19% of samples as well as other actionable alterations, including ESR1 mutations (17.5%) and PI3K pathway alterations (40.6%). Panel sequencing improved the interpretation of negative liquid biopsy results by integrating tumor fraction and VAF metrics. Conclusions: Panel sequencing assays such as AVENIO provide broader genomic coverage, enhance the detection of actionable mutations and refine the interpretation of negative liquid biopsy findings. These findings support the integration of comprehensive ctDNA profiling into routine clinical practice for HR+/HER2− advanced breast cancer while highlighting the need for improved assay accessibility and expanded genomic targets.

  Study EGAS00001008200

• Benchmark Dataset for Somatic Mutation Calling in Cell-Free DNA

  This study provides a comprehensive benchmarking resource for somatic variant detection in cell-free DNA (cfDNA) from cancer patients. Longitudinal plasma samples from colorectal and breast cancer cohorts were selected to create patient-matched dilution series spanning ultra-low to high circulating-tumour-DNA (ctDNA) fractions, while preserving each individual’s germline and clonal haematopoiesis background. Deep whole-genome sequencing (150×) and ultra-deep whole-exome sequencing (2,000×) generated a reference call set of ~37,000 single-nucleotide variants and ~58,000 insertions/deletions. These data enabled systematic evaluation of nine somatic variant callers across variable ctDNA levels and sequencing depths, and were further used to explore machine-learning–guided parameter tuning. The resulting dataset offers an openly accessible framework for developers and clinicians to assess and optimize somatic variant calling in liquid biopsy applications.

  Dataset EGAD50000001870

• Amplicon based re-sequencing of multi-region PDAC samples

  Multi-region tumor samples were cut from frozen sections or FFPEs and reviewed from microdissection and H&E staining in order to select ones with high cellularity. DNA extraction was done using DNeasy Blood & Tissue Kits for frozen samples following the manufacturer’s guideline. Extracted DNAs were processed on an Illumina HiSeq 2500 in a paired end mode (100x100) using a custom targeted panel based on the list of all unique somatic mutations from the original WES data by the Integrated Genomics Operation (IGO) at Memorial Sloan Kettering Cancer Center (New York, NY).

  Dataset EGAD50000000354

• Whole genome sequencing data from tumor and normal samples

  Whole genome sequencing FASTQ files from tumor and normal samples from 202 patients. All experiments reported in this article were performed in the Clinical Laboratory Improvement Amendments (CLIA)-certified and College of American Pathologists (CAP)-accredited laboratories at Personalis Inc., as guided by the Association for Molecular Pathology (AMP) and CAP’s joint recommendations52. Preferred input material consisting of FFPE slides (enabling H&E and macrodissection which is part of the standard NeXT Personal process) was not available for the majority (94%) of tumor samples. Most tumor samples (72%) were processed from FFPE curls, with the remaining processed from pre-extracted DNA and fresh frozen material. Where FFPE material on slide was available, tumor sections were macrodissected to increase tumor content, with a minimum allowable cellularity threshold of 20% determined by pathological review. The tumor cellularity threshold of 20% was chosen based on prior work demonstrating that no significant correlation is observed between tumor purity and assay limit of detection (LOD) at this threshold31. Genomic DNA was isolated from tumor and normal samples and WGS libraries prepared as previously described31. Genomic DNA was isolated from matched tumor and normal samples using the Qiagen AllPrep DNA/RNA FFPE Tissue Kit or the QIAamp DNA Mini Kit (QIAGEN, Germantown, MD, USA) using internally optimized workflows. WGS sequencing libraries were prepared with 120-500 ng of acoustically sheared genomic DNA (Covaris LLC, Woburn, MA, USA) using the KAPA HyperPrep Kit (Roche Sequencing Solutions, Pleasanton, CA, USA) and customized methods. Libraries were cleaned-up using AMPure XP beads and then quantified using the KAPA Library Quantification Kit (Roche Sequencing Solutions, Pleasanton, CA, USA), before being sequenced to 30X depth of coverage using a NovaSeq 6000 instrument (Illumina, San Diego, CA, USA).

  Dataset EGAD50000001909

• Pipeline Olympics: Continuous benchmarking of computational workflows for DNA methylation sequencing data

  DNA methylation is a widely studied epigenetic mark and a powerful biomarker of cell type, age, environmental exposure, and disease. Genome-wide DNA methylation profiling is usually performed using whole-genome sequencing following selective conversion of unmethylated cytosines into thymines via bisulfite treatment or enzymatic methods. Numerous software tools facilitate processing of raw sequencing data for DNA methylation profiling, but a comprehensive benchmarking has been lacking. In this study, we systematically compared methods and tools for processing DNA methylation sequencing data. We established a dedicated benchmarking dataset comprising genome-wide DNA methylation profiling data for four reference samples using five experimental protocols each. The results of data processing were compared to highly quantitative locus-specific DNA methylation measurements available for 46 genomic loci. Based on this gold-standard reference dataset, we identified workflows that consistently demonstrated high performance. We present our results in an interactive application that provides a “living benchmark” ready for continuous updating as new workflows are proposed and require benchmarking against existing methods. In summary, our study provides guidance for any laboratory studying DNA methylation on a genome-wide scale.

  Study EGAS50000000541

• Correction of the cytosine deamination artifacts in FFPE-based sequencing experiments

  Formalin-fixed paraffin-embedded (FFPE) samples are widely used in research and diagnostics, but cytosine deamination during fixation introduces sequencing artifacts, particularly C>T substitutions, which complicate reliable mutation detection. In this study, we systematically evaluated five computational methods and an enzymatic repair approach for FFPE artifact removal, as well as their combined application, using a custom dataset based on whole exome sequencing. Our results demonstrate that while computational strategies improve data quality, the enzymatic approach provides the most effective artifact correction. The study provides guidelines for both computational and enzymatic artifact correction strategies for reliable downstream analyses.

  Study EGAS50000001354

• Dataset for study Genome-wide gene expression analysis following CRISPRi of transposable elements

  Transposable elements (TEs), once regarded as parasitic genomic remnants, are now recognized as key regulators of gene expression and genome evolution, yet the functional specificity of individual TE subfamilies remains largely unexplored. This dataset investigates the transcriptional consequences of targeted repression of MER57E3 and LTR10B2 elements using CRISPR interference (CRISPRi) in human induced pluripotent stem cells (hiPSCs). hiPSCs expressing CRISPRi machinery (n = 2 biological replicates) were transduced with guide RNAs targeting individual or grouped copies of MER57E3 and LTR10B2, as well as the ZNF678 promoter or a lacZ non-targeting control. Transduced cells were subsequently differentiated into neural progenitor cells (NPCs), and total RNA was extracted for mRNA library preparation and sequencing. The dataset comprises 24 single-end mRNA-seq FASTQ files generated from these NPCs and wild-type controls.

  Dataset EGAD00001015689

• RNAseq: Acquired non-permissive bone marrow microenvironment impairs hematopoietic stem cell proliferation and maintenance and B-cell development post-HSCT

  Defects in B-cell reconstitution upon hematopoietic stem-cell (HSC) transplantation (HSCT) are a common observation, yet the mechanism remains unexplained. The bone marrow (BM) stroma, including mesenchymal stromal cells (MSCs), guides HSC maintenance and B-lymphopoiesis by secreting crucial cytokines. We report acquired, permanent, selective and complete B-cell deficiency in the context of full donor-chimerism in a patient with X-linked lymphoproliferative disease and aimed to identify the contribution of the BM-microenvironment in disrupted B-cell reconstitution post-HSCT. We studied longitudinal BM samples from the patient and his identical twin, both of whom underwent HSCT with the same donor with opposite outcomes in B-cell reconstitution. In the index patient BM, we observed progressive loss of proliferation of HSCs and a selective block at the pre-BI cell stage. In vitro modeling studies showed limited survival of patient-HSCs and a relative accumulation of pre-B cells. Patient-derived MSCs failed to support survival and proliferation of HSCs and B-cell development of healthy-HSCs which was correlated with reduced CXCL12 levels. Using bulk RNA-sequencing of MSCs and in vitro functional studies, we showed global changes in the patients’ MSCs and a progressive loss of CXCL12 expression. Indeed, survival of patients HSCs improved supplementing in vitro development culture with CXCL12, suggesting a contribution of defective CXCL12 signaling to the phenotype. In summary, our data show that an acquired defect in the BM-stromal microenvironment and exhaustion of HSCs and committed progenitors may cause a permanent non-permissive state for normal B-cell development.

  Study EGAS50000001437

• ATAC-seq: Acquired non-permissive bone marrow microenvironment impairs hematopoietic stem cell proliferation and maintenance and B-cell development post-HSCT

  Defects in B-cell reconstitution upon hematopoietic stem-cell (HSC) transplantation (HSCT) are a common observation, yet the mechanism remains unexplained. The bone marrow (BM) stroma, including mesenchymal stromal cells (MSCs), guides HSC maintenance and B-lymphopoiesis by secreting crucial cytokines. We report acquired, permanent, selective and complete B-cell deficiency in the context of full donor-chimerism in a patient with X-linked lymphoproliferative disease and aimed to identify the contribution of the BM-microenvironment in disrupted B-cell reconstitution post-HSCT. We studied longitudinal BM samples from the patient and his identical twin, both of whom underwent HSCT with the same donor with opposite outcomes in B-cell reconstitution. In the index patient BM, we observed progressive loss of proliferation of HSCs and a selective block at the pre-BI cell stage. In vitro modeling studies showed limited survival of patient-HSCs and a relative accumulation of pre-B cells. Patient-derived MSCs failed to support survival and proliferation of HSCs and B-cell development of healthy-HSCs which was correlated with reduced CXCL12 levels. Using bulk RNA-sequencing of MSCs and in vitro functional studies, we showed global changes in the patients’ MSCs and a progressive loss of CXCL12 expression. Indeed, survival of patients HSCs improved supplementing in vitro development culture with CXCL12, suggesting a contribution of defective CXCL12 signaling to the phenotype. In summary, our data show that an acquired defect in the BM-stromal microenvironment and exhaustion of HSCs and committed progenitors may cause a permanent non-permissive state for normal B-cell development.

  Study EGAS50000001438

• An allele-resolved nanopore-guided tour of the human placental methylome

  The placenta is a temporary organ present during pregnancy that is responsible for coordinating all aspects of pregnancy between the mother and fetus. It has a distinct epigenetic, transcriptomic, and mutational landscape with low levels of methylation, high numbers of transcribed loci, and a high mutational burden relative to somatic tissues. We present this landscape through the application of nanopore sequencing technology to provide a more comprehensive picture of female placental genomics and methylomics along with integrated haplotype-resolved transcriptomic analyses across eight trios. Whole genome sequencing of trios allows robust phasing, permitting comprehensive genome-wide investigation of parent-of-origin methylation and transcription. This enhanced view facilitates identifications of many new differentially methylated regions (DMRs), both conserved and differing between individuals, as well as novel imprinted genes.

  Study EGAS50000001301

• Oligodendroglia as functional effectors of Multiple Sclerosis risk variants (iPS derived hOPC scCRISPRi/a-seq)

  Study of the regulatory effect of a selection Multiple Sclerosis (MS) associated SNPs applying high-throughput functional genomics in human induced pluripotent stem cell-derived oligodendroglia (iPS-derived hOPCs). Selected cis-regulatory elements were assesed with lentiviral-based pooled single cell (sc)CRISPR-seq screens. CRISPRi/a (dCas9-KRAB and dCas9-p300 respectively) was performed, in combination with direct-capture Perturb-sequencing single-guide RNA (sgRNA) and droplet-based single-cell RNA-seq, allowing high sgRNA capture efficiency and identification of possible transcriptional regulatory mechanisms at a single cell/sgRNA level.

  Study EGAS50000001417

• scCRISPRi/a-seq Control and IFN treated iPS derived human GPC/OPCs

  Datasets consists of 2 batches of human glial progenitors (iPS), cells were sequenced as controls and IFN treated. Using the 10Genomics platform from the samples 2 libraries were built forgene expression libraries (scRNA-seq) and captured guides sequencing library (gRNA) on a set of Multiple Sclerosis associated SNPs. Batch one includes KRAB and P300 perturbed cells in 2 rounds sequenced RNA libraries for Ctrl and IFN and 1 round of capture guides for Ctrl and IFN. Batch 2 includes 1 round of both RNA expresison library and captures guides for KRAB and P300 perturbations in Ctrl and IFN treated cells.

  Dataset EGAD50000002053

• Target sequencing of 27 cancer-predisposing genes in Japanese colorectal cancer patients

  Background: National Comprehensive Cancer Network (NCCN) recently recommended germline genetic testing for all pancreatic cancer patients. However, the genes targeted by genetic testing and the feasibility of selecting patients likely to carry pathogenic variants have not been sufficiently verified. The purpose of this study was to genetically characterize Japanese patients and examine whether the current guideline is applicable in this population. Methods: Using targeted sequencing, we analyzed the coding regions of 27 cancer-predisposing genes in 1,005 pancreatic cancer patients and 23,705 controls in Japan. We compared the pathogenic variant frequency between cases and controls and documented the demographic and clinical characteristics of carrier patients. We then examined if it was possible to use machine learning to predict carrier status based on those characteristics. Findings: We identified 205 pathogenic variants across the 27 genes. Pathogenic variants in BRCA2, ATM, and BRCA1 were significantly associated with pancreatic cancer. Characteristics associated with carrier status were inconsistent with previous investigations. Machine learning classifiers had a low performance in determining the carrier status of pancreatic cancer patients, while the same classifiers, when applied to breast cancer data as a positive control, had a higher performance that was comparable to that of the NCCN guideline. Interpretation: Our findings support the clinical significance of multigene panel testing for pancreatic cancer and indicate that at least 3.4% of Japanese patients may respond to poly (ADP ribose) polymerase inhibitor treatments. The difficulty in predicting carrier status suggests that offering germline genetic testing for all pancreatic cancer patients is reasonable.

  Study JGAS000346

• GWAS for atrial fibrillation in the Japanese population

  We performed a genome-wide association study (GWAS) that utilized 8,180 atrial fibrillation cases and 28,612 controls and followed up in an additional 3,120 cases and 125,064 controls in the Japanese population. We replicated previously reported loci and identified six novel loci. Five of the six novel loci were specifically associated with atrial fibrillation in the Japanese population after comparing our data to individuals of European ancestry, suggesting there might be different susceptibility genetic factors across ancestries. Our study has discovered variants in genes HAND2, KCND3 and NEBL that are relevant to atrial fibrillation susceptibility. The involvement of PPFIA4 and SH3PXD2A in axon guidance also suggested its role in the disease pathogenesis. Our findings may contribute to a better understanding of atrial fibrillation susceptibility and pathogenesis.

  Study JGAS000101

• Target sequencing of 27 cancer-predisposing genes in Japanese pancreatic cancer patients

  Background: National Comprehensive Cancer Network (NCCN) recently recommended germline genetic testing for all pancreatic cancer patients. However, the genes targeted by genetic testing and the feasibility of selecting patients likely to carry pathogenic variants have not been sufficiently verified. The purpose of this study was to genetically characterize Japanese patients and examine whether the current guideline is applicable in this population. Methods: Using targeted sequencing, we analyzed the coding regions of 27 cancer-predisposing genes in 1,005 pancreatic cancer patients and 23,705 controls in Japan. We compared the pathogenic variant frequency between cases and controls and documented the demographic and clinical characteristics of carrier patients. We then examined if it was possible to use machine learning to predict carrier status based on those characteristics. Findings: We identified 205 pathogenic variants across the 27 genes. Pathogenic variants in BRCA2, ATM, and BRCA1 were significantly associated with pancreatic cancer. Characteristics associated with carrier status were inconsistent with previous investigations. Machine learning classifiers had a low performance in determining the carrier status of pancreatic cancer patients, while the same classifiers, when applied to breast cancer data as a positive control, had a higher performance that was comparable to that of the NCCN guideline. Interpretation: Our findings support the clinical significance of multigene panel testing for pancreatic cancer and indicate that at least 3.4% of Japanese patients may respond to poly (ADP ribose) polymerase inhibitor treatments. The difficulty in predicting carrier status suggests that offering germline genetic testing for all pancreatic cancer patients is reasonable.

  Study JGAS000327

• Geriatric Oncology Database of genotypes and methylation, gene expression, clinical data, and survey results on psychosocial and physical conditions in Japanese elderly cancer patients to establish truly effective treatment strategy

  Owing to the advent of super-aged society, cancer mortality in Japan is forecasted to become an all-time high. The management of elderly patients with cancer is a serious health issue and the need for specific care guidelines for this population is critical in Japan. The significant individual differences in comorbidity, physical and mental functioning, and social problems among aging individuals are obstacles to the progress. The response to cancer treatment varies significantly among patients, even in the same stage of the same type of cancer. Older aged patients are still less likely to be offered participation in clinical trials, thus the number of clinical evidences is limited. The molecular mechanisms regulating the physiological process of ageing and senescence, and cancer are far from understood. To establish a truly effective treatment algorithm, we attempted to develop a geriatric oncology database for genotypes and methylation, gene expression, clinical data, and survey results on psychosocial and physical conditions in Japanese elderly cancer patients in this retrospective study. The genomic analysis was performed in 62, 106, and 173 cases, respectively for gastric, colon and lung cancers. The clinical data and survey results on psychosocial and physical conditions were collected from 166, 313, and 344 patients respectively for gastric, colon and lung cancers, and also collected from 357, 49, and 300 benign cases respectively for cardiovascular disorder, respiratory dysfunction, diabetes and nephropathy as the analysis control.

  Study JGAS000061

• A prospective multicenter study of plasma ctDNA versus archival tumor tissue to guide FGFR-targeted therapy in metastatic urothelial cancer - Targeted

  Targeted sequencing data related to the publication titled "A prospective multicenter study of plasma ctDNA versus archival tumor tissue to guide FGFR-targeted therapy in metastatic urothelial cancer." FGFR alterations, seen in up to 25% of metastatic urothelial carcinoma, can be exploited with targeted therapy. Here, we perform targeted sequencing of cell-free DNA, archival FFPE, and white blood cell DNA to compare ctDNA versus tissue for FGFR biomarker status and monitor temporal changes to FGFR over the disease course, specifically after progressing on targeted therapy.

  Study EGAS50000001450

• Dynamics of Tumor Heterogeneity from Primary to Metastatic Dissemination in Prostate Cancer

  PRO-SPeCT: PROstate cancer heterogeneity deconvolution through Single cell Profiling of Chromatin accessibility and Transcriptomic output Identifying drivers of cancer progression to guide treatment selection is hindered by limited abilities to understand tumor heterogeneity’s impact on evolution. Here, we delineated the phenotypic variability across ~300,000 prostate tumor cells collected from multiple loci in primary and matched locoregional metastases. We found inter-patient heterogeneity to be confined to malignant populations. While malignant cell populations exhibit intra-locus heterogeneity, they maintain inter-loci phenotypic similarity within a patient’s prostate gland. In addition, the intra-locus heterogeneity between malignant cell populations is paired with a common clonal architecture. Lastly, we show that malignant cell populations disseminating to locoregional lymph nodes mirror the clonal architecture and phenotypic heterogeneity observed across primary tumor loci while showcasing cell state transition toward inflammatory phenotypes. These findings provide insights into distinct measures of tumor heterogeneity, revealing diverse evolutionary paths across patients converging to common phenotypic adaptations in early prostate cancer progression.

  Study EGAS50000000524

• Single cell transcriptomics to characterize the tumor microenvironment of prostate cancer fusion biopsies

  The primary objective of this study was to characterize the tumor microenvironment in fusion-guided transperineal biopsy samples from patients undergoing PC diagnosis. For each patient, one biopsy was taken from a suspected tumor region and another from a non-suspicious area, which were later classified as high- or low-tumorigenicity based on anatomopathological analysis. Using scRNA-seq data, we performed cancer-oriented cell annotation, differential expression analysis, and functional pathway enrichment studies across key cellular subpopulations. Additionally, differential abundance analysis was conducted to identify cell groups representative of different tumorigenicity levels. Finally, classification models were developed using gene expression data to differentiate high- vs. low-tumorigenicity samples, with the long-term goal of establishing a diagnostic classifier for PC stratification.

  Study EGAS50000000888

• CD4 auto-antigens

  The CD4 auto-antigen Access Committee (DAC) manages and oversees data access, ensuring compliance with ethical and regulatory guidelines while facilitating secure sharing with authorized researchers.

  Dac EGAC50000000864

• Assessing gene expression profiling from FFPE Patient Samples: A Comparison of Two Library Preparation Approaches and Recommendations

  Next-Generation Sequencing (NGS) has transformed cancer research and clinical practice, with Whole Exome Sequencing (WES) driving advances in mutational profiling and personalized oncology. Yet, transcriptomic signatures remain essential for understanding disease mechanisms, including therapy resistance pathways. RNA sequencing (RNA-seq), however, faces unique challenges when dealing with low-input or degraded RNA, as often found in archival formalin-fixed paraffin-embedded (FFPE) tissues. Although previous studies have compared library preparation protocols, rapidly evolving technologies call for updated evaluations. Here, we present a direct comparison of two FFPE-compatible stranded RNA-seq library preparation kits: TaKaRa™ SMARTer® Stranded Total RNA-Seq Kit v2 (Kit A) and Illumina Stranded Total RNA Prep Ligation with Ribo-Zero Plus (Kit B). Both kits generated high-quality RNA-seq data, yet important differences emerged. Notably, Kit A achieved comparable gene expression quantification to Kit B while requiring 20-fold less RNA input, a crucial advantage for limited samples, albeit with increased sequencing depth. We critically discuss these results in relation to RNA availability, technical performance, cost-effectiveness, processing time, and automation potential, offering practical guidance for selecting optimal RNA-seq strategies in clinical and translational research settings

  Study EGAS50000001066

• Comprehensive benchmarking of methods for mutation calling in circulating tumor DNA

  This study provides a comprehensive benchmarking resource for somatic variant detection in cell-free DNA (cfDNA) from cancer patients. Longitudinal plasma samples from colorectal and breast cancer cohorts were selected to create patient-matched dilution series spanning ultra-low to high circulating-tumour-DNA (ctDNA) fractions, while preserving each individual’s germline and clonal haematopoiesis background. Deep whole-genome sequencing (150×) and ultra-deep whole-exome sequencing (2,000×) generated a reference call set of ~37,000 single-nucleotide variants and ~58,000 insertions/deletions. These data enabled systematic evaluation of nine somatic variant callers across variable ctDNA levels and sequencing depths, and were further used to explore machine-learning–guided parameter tuning. The resulting dataset offers an openly accessible framework for developers and clinicians to assess and optimize somatic variant calling in liquid biopsy applications.

  Study EGAS50000001313

• Host factors dictate gut microbiome alterations in chronic kidney disease more strongly than to kidney function

  Despite recent progress, microbial markers in Chronic Kidney Disease (CKD) remain inconclusive. We combined quantitative faecal metagenomics (N=130 CKD cohort) and cross-study biomarker comparisons (Ntotal=4420) to study microbiome associations with glomerular filtration rate (eGFR; kidney function) and 4-year CKD progression. Transit time (TT) and medications primarily explained microbiome variation, trumping eGFR-related effects. Metagenome analysis showed increased p-cresol and indole synthesis potential and decreased plant-to-animal CAZyme ratios with lower eGFR, coupled to a Bact1 to Rum enterotype shift, suggesting saccharolytic-to-proteolytic microbiome transitions linked to dietary guidelines and slowed-down TT. Peritoneal dialysis patients showed increased (dysbiotic) Bact2 prevalence and linked intestinal inflammation. Only Escherichia coli, an unnamed Alistipes species and Bifidobacterium adolescentis were confounder-independent markers for eGFR, but these nor previous markers convincingly replicated across 11 studies. No predictors for CKD progression were found. Together, poor evidence for microbiome biomarkers but substantial eGFR-independent effects were found, suggesting potential for nutritional and TT interventions in CKD.

  Study EGAS50000000646

• 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

• 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

• 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

• Data Use Ontology (DUO)

  Data Use Ontology Data Use Ontology at EGA The EGA is committed to its involvement in the work of GA4GH. In an effort to enhance data discoverability and streamline data access, EGA have implemented the use of the Data Use Ontology (DUO), based on consent codes as described in Dyke et al. 2017. The Data Use Ontology codes will be displayed on the live dataset page of your submission to advise any would be requestor on how the data can be used and also to enhance data discoverability as users will be able to search on these codes to find applicable datasets. DUO can be browsed online via the Ontology Lookup Service Learn more reading the Data Use Ontology publication and the GA4GH Machine-Readable Consent Guidance! Check our DAC Portal Take The Tour and learn how to add DUO codes to your policy! Term Shorthand Label Description DUO:0000004 NRES no restriction This data use permission indicates there is no restriction on use. DUO:0000042 GRU general research use This data use permission indicates that use is allowed for general research use for any research purpose. DUO:0000006 HMB health or medical or biomedical research This data use permission indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry. DUO:0000007 DS disease specific research This data use permission indicates that use is allowed provided it is related to the specified disease. DUO:0000011 POA population origins or ancestry research only This data use permission indicates that use of the data is limited to the study of population origins or ancestry. DUO:0000012 RS research specific restrictions This data use modifier indicates that use is limited to studies of a certain research type. DUO:0000015 NMDS no general methods research This data use modifier indicates that use does not allow methods development research (e.g., development of software or algorithms). DUO:0000016 GSO genetic studies only This data use modifier indicates that use is limited to genetic studies only (i.e., studies that include genotype research alone or both genotype and phenotype research, but not phenotype research exclusively) DUO:0000018 NPUNCU not for profit, non commercial use only This data use modifier indicates that use of the data is limited to not-for-profit organizations and not-for-profit use, non-commercial use. DUO:0000019 PUB publication required This data use modifier indicates that requestor agrees to make results of studies using the data available to the larger scientific community. DUO:0000020 COL collaboration required This data use modifier indicates that the requestor must agree to collaboration with the primary study investigator(s). DUO:0000021 IRB ethics approval required This data use modifier indicates that the requestor must provide documentation of local IRB/ERB approval. DUO:0000022 GS geographical restriction This data use modifier indicates that use is limited to within a specific geographic region. DUO:0000024 MOR publication moratorium This data use modifier indicates that requestor agrees not to publish results of studies until a specific date. DUO:0000025 TS time limit on use This data use modifier indicates that use is approved for a specific number of months. DUO:0000026 US user specific restriction This data use modifier indicates that use is limited to use by approved users. DUO:0000027 PS project specific restriction This data use modifier indicates that use is limited to use within an approved project. DUO:0000028 IS institution specific restriction This data use modifier indicates that use is limited to use within an approved institution. DUO:0000029 RTN return to database or resource This data use modifier indicates that the requestor must return derived/enriched data to the database/resource. DUO:0000043 CC clinical care use This data use modifier indicates that use is allowed for clinical use and care. DUO:0000044 NPOA population origins or ancestry research prohibited This data use modifier indicates use for purposes of population, origin, or ancestry research is prohibited. DUO:0000045 NPU not for profit organisation use only This data use modifier indicates that use of the data is limited to not-for-profit organisations. DUO:0000046 NCU non-commercial use only This data use modifier indicates that use of the data is limited to not-for-profit use. Point to Notice: For the consent code DUO:0000007 where data is restricted to use on a specific disease, please accompany it with an appropriate ontology from MONDO e.g., If the data is restricted to the use of research into juvenile idiopathic arthritis the code should be displayed as DUO:0000007; MONDO:0011429.

  Documentation access/data-access-committee/data-use-ontology

• 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

• Policy Documentation

  Policy Documentation The following policy documentation is required to be prepared and submitted to the EGA, together with your data files and associated metadata. Data Access Agreement (DAA) The Data Access Agreement is a contract made between Data User and Data Access Committee. The agreement should be drafted by the DAC and includes, but is not limited to, details of data use, publication embargoes and storage. Completion of a DAA by the applicant/s should form part of the application process to the DAC. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA template Alternate (harmonised) DAA template

  Documentation access/data-access-committee/policy-documentation

• 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

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! 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. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. 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. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, 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! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• 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

• EGA account management

  How to manage your EGA account Welcome to the documentation page for creating an EGA user. The European Genome-Phenome Archive (EGA) is a platform for archiving, managing, and sharing human genomic and phenotypic data. To submit, access, and manage requests for the data hosted on the EGA platform, users are required to register for an account. This documentation page provides step-by-step instructions for creating an EGA user account, as well as information on the different types of EGA user accounts and their associated privileges. You can check the EGA data flow for a better understanding. Manage EGA account step-by-step guide Contact Information Public Keys Password Authenticator Federated Identity Sessions Request an EGA account step-by-step guide Fill in this form.You cannot use a generic email account (e.g., Gmail). Make sure you use your institutional email account.Your email is by default your username.The criteria for a strong password is: It should contain between 8 and 32 charactersIt should contain at least one uppercase letterIt should contain at least one numberIt should contain at least one special characterYou will need to wait for the Helpdesk team to check your identity. Please allow two business days for this step.After the Helpdesk validation step, you will receive an email with a link to validate your institutional email.Click the link to verify your email. It will redirect you to the EGA website.As soon as your account has been validated, you will be able to start adding more information to your EGA profile. For that, you first need to log in using your credentials from step 1. Manage EGA account step-by-step guide As a logged-in user, go to your profile by clicking on Welcome > My Profile. To modify it, click the Edit button.You will see the following options: Contact Information In this section, you can modify the personal information of your EGA account. Public Keys Adding a public key is necessary for downloading data via Live Outbox distribution. If you don’t know how to generate your key, you can follow the instructions available on How do I create a key? Password In the Password tab, you can change your password anytime to ensure the security of your account. However, if you receive an email notifying you that your password was modified and you did not initiate the change, it could be a sign that your account has been compromised. In this case, you should immediately contact our Helpdesk team to report the issue and receive assistance in restoring your account security. Authenticator You can set your two-factor authentication (2FA) system for your EGA account as an identity and access management security method that requires two forms of identification to access resources and data. To obtain your code, please follow the instructions below, also available in the Authenticator tab in your profile. Sessions The Sessions tab displays a list of all devices where you are currently logged in as an EGA user. This includes any open sessions you have on your computer, phone, or other devices. By reviewing the list of active sessions, you can monitor the devices that have access to your account and ensure that there are no unauthorised logins. If you notice any suspicious activity, you can close the sessions from this page to immediately terminate access to your account from the unauthorised device.

  Documentation how-to-manage-your-account

• 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

• 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

• EGA submission account terms

  Submission account terms Each EGA submission account has a dedicated submission box. To ensure continued service to all submitters EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. Those that are near to or exceeding this value will be monitored on a weekly basis by the helpdesk team and the submitter will be contacted and guidance provided accordingly on completing their metadata registration. You will be able to register your metadata associated with the files in your submission account via EGA Submitter Portal, Webin or the EGA REST API. EGA also requests that metadata is submitted within 60 days of upload data to a submission box. When we detect files that are over 60 days old in a submission box we will notify the submitter requesting that metadata be submitted or the files removed from the submission box. It is important to note that data is not archived at the EGA until the metadata describing the files has been associated and the archival process has completed. It is only when associated metadata has been submitted that the archival process into EGA is fully triggered. EGA removes files from the submission box once they have been successfully archived, so no action is required by a submitter to remove successfully archived files. Files over 90 days old will be deleted from the submission box unless EGA Helpdesk has been contacted and confirmed an exemption with the submitter.

  Documentation submission/terms

• 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

• How to encrypt files with EGACryptor

  File preparation Due to the processes used at the EGA for file archival the use of non-alphanumeric characters in a filename will cause issues in archival. By convention whitespaces in filenames are to be avoided and should be replaced with the underscore character (_). Before encrypting your files please make sure that any files that will be uploaded to EGA do not use special characters such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &  Crypt4gh EGACryptor Files encrypted with EGACryptor must be uploaded via FTP EGACryptor The EGACryptor v.2.0.0 is a JAVA-based application which enables submitters to produce EGA compliant encrypted files along with files for the encrypted and unencrypted md5sum for each file to be submitted. The application will generate an output folder that will by default mirror the directory structure containing the original files. This output folder can subsequently be uploaded to the EGA FTP staging area via an FTP or Aspera client. Download EgaCryptor Download EgaCryptor Using the EgaCryptor Using the EgaCryptor Encrypting single file Encrypting multiple files Encrypting all files in folder Points to note Troubleshooting Troubleshooting Download EGACryptor The required jar files can be obtained by downloading EgaCrytptor jar file After the file has been downloaded, extraction of the zipped archive is required. The EGACryptor has been built to work with Java Runtime Environments from version 6 and above and with the OpenJDK Environment. Please refer to the relevant resources for installation guidance. Installing the latest version of the OpenJDK will include the JCE files. If your installation of Java JRE is less than 1.8.0_151 will require the manual installation of the JCE Policy Files. You can verify the version of the Java SE Runtime Environment (JRE) installed by using the command: $ java -version If you need to install the JCE please follow the instructions below: Installing the JCE policy files (due to licensing terms and conditions the required policy files must be downloaded direct from the ORACLE website) : Download the unlimited strength JCE policy files (JRE 6 / JRE 7/ JRE 8) Uncompress and extract the downloaded file. This will create a subdirectory called JCE. This directory contains the following files: README.txt, COPYRIGHT.html, local_policy.jar and US_export_policy.jar Install the two policy JAR files by replacing the existing ones in your java home directory. Install the two policy JAR files by replacing the existing ones in your directory. The standard place for JCE jurisdiction policy JAR files is: /lib/security [Unix] or \lib\security [Win32] Notes: refers to the directory where the Java SE Runtime Environment (JRE) was installed. Additional performance enhancements that have been included in the EGACryptor V2.0.0: The ability to parallelise the processing of datasets through the use of the resources on a system. Multicore systems will allow the user to specify n-1 cores for an n-core system. The use of this feature on clusters may speed up the processing of datasets that have large file numbers but consult your local cluster guide to ensure that there are not monopolising resources that are needed by other system users. The default for this process remains single threaded. 3 levels of system usage can be specified. Full usage within the limits detailed above. A limited mode that will ensure that 50% of the system resources are available for other tasks. Maximum mode is limited to 75% of system resources, this allows encryption to be prioritised but allows for the system to be usable for light alternate tasks. Finally there is a throttling mode that allows you to specify the exact number of computational threads to be used. the EGACryptor is able to ingest a structured directory and will output a directory with the same structure containing the encrypted files along with the md5checksums for the plain and encrypted files. The entire output directory can then be uploaded to the EGA for archival. as with the input path, it is now possible to specify the output path. the options have been updated inline with the upgraded functionality. The tool can only be used via the command line. The EGACryptor is designed to perform a single task, encrypting your data, for upload of these files please refer to our uploading guide Using the EgaCryptor Below are the three ways on how the EGACryptor tool can be used: Encrypting a single file : java -jar ../EGA-Cryptor_2_0_0.jar -i example1.bam Encrypting multiple files : java -jar ../EGA-Cryptor_2_0_0.jar -i "example1.bam,example2.bam" Encrypting all the files within a folder java -jar ../EGA-Cryptor_2_0_0.jar -i path/to/target/directory By default the EGACryptor v2 will create a new output directory containing all encrypted files and the relevant checksums within the target directory. If a specific directory is desired this can be specified by using the -o flag. This can be achieved in a similar manner to the following example: java -jar ../EGA-Cryptor_2_0_0.jar -i /path/to/target/directory -o /path/to/output/directory The tool will output three files per input file: file.gpg ( encrypted file ) file.md5( file md5 sum value file ) file.gpg.md5 ( encrypted file md5 sum value file ) All output files must then be uploaded to your submission account using Aspera or FTP. Further documentation on how to upload files: FTP and Aspera. Points to note Remember to provide the path to EgaCryptor.jar and run the command from within the directory the file/s are located. ECryptor writes files to the source directory of your local file system, as a result you must have write-access permissions for the source directory. Troubleshooting If in doubt about the function of the EGACryptor it is recommended to first consult the built-in documentation. This can be accessessed by using the -h flag as stated in the following table. Built-in Commands Table: list of the command line options built into EGA-Cryptor v2.0.0. Command line Option Action --------------------- ----------- -f Set this option to allow application to create maximum threads to utilise full capacity of cores/processors available on machine -h Use this option to view the bult-in help menu * -i File(s) to encrypt. Provide file/folder path or comma separated file path if multiple files in double quotes -l Set this option to allow application to create maximum threads equals to 50% capacity of cores/processors available on machine -m Set this option to allow application to create maximum threads equals to 75% capacity of cores/processors available on machine -o Path of the output file. This is optional. If not provided then output files will be generated in the same path as that of source file (default: output- files) -t Set this option if user wants to control application to create maximum threads as specified. Application will calculate no. of cores/processors available on machine & will create threads accordingly Encryption Errors UnixFileSystem.createFileExclusively (Native Method) The error is thrown by UNIX ("UnixFileSystem.createFileExclusively(Native Method)"). It appears that the user does not have write-access to the file system where the file to be uploaded is located. EGACryptor always writes MD5 checksums into files before uploading them to the server, and these files are created in the same location where the uploaded file itself resides.Solution: address your directory permission issue and re-run the command. Install JCE Unlimited Strength Jurisdiction Policy files The JCE policy unlimited strength jurisdiction files should be installed according to your current java version If you are still facing difficulty with the EGACryptor v.2 after having consulted the documentation please contact the EGA Helpdesk.

  Documentation submission/data/file-preparation/egacryptor

• Quick Guide for data submission

  Quick Guide This is a quick guide to submit data to the EGA. Please select data type to display the right detailed instructions. Sequence data Array-based data Get your submission account You first need to create your EGA user. Then, once your account has been verified by the Help Desk team, request your submission account and provide details of the data type and platform(s) in your submission. Register Study/DAC Use Submitter Portal to register your study, samples, Data Access Committee (DAC) and Policy. Upload data Encrypt your data files using the and upload it to your inbox using SFTP. Register experiments and runs Associate each data file to a registered sample and study by Linking files to samples. Details of the experimental procedure you followed must be provided. Finalise your submission Group your runs/analysis into datasets and link them to your new or existing DAC and policy using DAC Portal. Data request are done at a dataset level, thus files within a datasets must share release conditions. Release and admin When finalising the submission, set a released date to instruct our Helpdesk to release your study. All registered studies are automatically placed on hold until the named submission or DAC contact instructs our Helpdesk for the study to be released. Get your submission account Fill the submission form and provide details of the data type and platform(s) in your submission. Register Study/DAC Use EGA Programmatic submission to register your study, samples, Data Access Committee (DAC) and Policy. Upload data Encrypt your data files using the EgaCryptor and upload it using default FTP clients or Aspera. Complete the Array-Format (AF) spreadsheet Download the AF spreadsheet and complete all four sections. Return the spreadsheet to the EGA helpdesk. Release and admin Instruct our Helpdesk to release your study. All registered studies are automatically placed on hold until the named submission or DAC contact instructs our Helpdesk for the study to be released.

  Documentation submission/quickguide

• Team

  The Team Mallory Freeberg Roderic Guigó Arcadi Navarro Helen Parkinson Jordi Rambla Ana T. Alonso Silvia Bahena Àlex Bedmar Kenneth Buckley Aldar Cabrelles Ángel Carreño Marcos Casado Giulia Cellerino Amy Curwin Teresa D'Altri Abeer Fadda Teresa Garcia Sara Gregorio Max Fischer Bela Juhasz Oriol Lopez-Doriga Mireia Marin Óscar Martínez Andrea Mero Akiris Moctezuma Aurora Moreno Liina Nagirnaja Francesc de Puig Santiago Rensonnet Gabriele Rinck Aravind Sankar Andres Silva Coline Thomas Sabela de la Torre Gemma Vicente The EGA Team at the CRG co-manages the European Genome and phenome Archive together with the EGA Team at the European Bioinformatics Institute. In addition to maintaining and distributing data, we enrich the contents of the EGA contributing with our knowledge about genomics and the relationship between genomes and phenomes. Previous Team Members Alexander Vikhorev Jeff Almeida-King Mario Alberich Sergi Aguilo Pablo Arce Minjie Ding Alfred Gil Leslie Glass Jag Kandasamy Vasudev Kumanduri llkka Lapalainen Audald Lloret i Villas Sira Martinez Anand Mohan Dietmar Orth Justin Paschall Saif Ur Rehman Gary Saunders Thomas Smith Ashutosh Shimpi Marc Sitges Dhvani Solanki Giselle Kerry Nino Spataro Dylan Spalding Matthieu Vizuete-Forster Cristina Yenyxe Gonzalez Garcia Paul Flicek Anna Foix Emilio Garcia Rios Jorge Izquierdo Roberto Ariosa Marta Ferri Peradalta Daniel Barrowdale Babita Singh Umuthan Uyan Aleix Canalda Dona Shaju Mauricio Moldes Carles Garcia Frédéric Haziza Alegria Aclan Lauren Fromont Alvis Brazma Marta Huertas Arnau Soler Gemma Milla Claudia Vasallo Aina Jené Csaba Halmagyi Raül Garcia Thomas Keane Mei Gascón

  Documentation about/team

• Federated EGA

  Federated EGA Federated EGA Index Overview Map of FEGA status across the world Current status of the FEGA Network Documentation Overview Federated EGA is a global network of repositories enabling secure discovery and access to sensitive human data. Our vision is to accelerate scientific discovery and healthcare breakthroughs by creating the go-to worldwide sensitive human data resource. Our values are: Privacy & Trust: Ensuring privacy of data subjects, security of services and acting with integrity to build community trust.FAIRness: Driving reuse of data through standardisation of metadata and clear access policies.Diversity: Expanding our network and representing global diversity in the data we host to bring benefits worldwide. Federated EGA - European by name, global by nature Federated EGA collaborates with European and global initiatives (GA4GH, ELIXIR, 1+ Million Genomes Framework, GDI), demonstrating that a network for transnational discovery of and access to human data is possible. By providing a solution to emerging challenges around secure and efficient management of human omics and associated data, the FEGA Network fosters data reuse, enables reproducibility, and accelerates biomedical research. For general enquiries or to request more information about Federated EGA, please send an email to fega-info [at] lists [dot] ega-archive [dot] org. Read more about the Federated EGA in our commentary in Nature Genetics! Learn more about setting up a Federated EGA Node in our onboarding documentation. Map of FEGA status across the world Current status of the FEGA Network Node Description Joined CEGA Central EGA is managed by the Centre for Genomic Regulation (CRG) and EMBL-EBI. The EGA has been a trusted repository for sensitive data since 2008. CEGA coordinates the FEGA network, hosts central services and the EGA catalogue. 2022 Finland FEGA Finland is hosted by CSC - IT Center for Science Ltd., which is the national ELIXIR Node in Finland. CSC is a state-owned company specialising in providing high-quality IT infrastructure and services for Finnish higher education and research. 2022 Germany The German Human Genome-Phenome archive (GHGA) is part of the German National Research Data Infrastructure (NFDI). It is coordinated by the German Cancer Research Center (DKFZ) and includes over 20 academic partners. 2022 Norway FEGA Norway is a service by ELIXIR Norway, the Norwegian node of the European organisation ELIXIR. University of Oslo as a partner institution in ELIXIR Norway is hosting the service relying on the TSD infrastructure for sensitive data. ELIXIR Norway is a consortium of 5 Norwegian universities and is coordinated by University of Bergen. 2022 Spain FEGA Spain is co-hosted by the Barcelona Supercomputer Center (BSC) and the Centre for Genomic Regulation (CRG), both part of ELIXIR Spain and the Spanish National Infrastructure for Personalised Medicine associated with Science and Technology (IMPaCT). 2022 Sweden FEGA Sweden is hosted by the National Bioinformatics Infrastructure Sweden (NBIS), which legally is part of Uppsala University. NBIS forms the bioinformatics platform at SciLifeLab and constitutes the Swedish node of the European organisation ELIXIR. 2022 Poland FEGA Poland is hosted by Biobank Lodz, which is part of University of Lodz. Biobank Lodz is an element of the infrastructure of the Regional Digital Medicine Centers established by the Medical Research Agency. 2022 Portugal FEGA Portugal is managed by BioData.pt, the distributed infrastructure for Life and Health data for Portugal. This entity is a non-profit association of 15 life sciences R&I organisations spread across the country, and the home of ELIXIR Node in Portugal. 2023 Canada Canadian Genome-phenome Archive is part of the Pan Canadian Genome Library, with the mandate to allow the secure and responsible sharing and analysis of Canadian genomic information. 2024 Switzerland Swiss FEGA is hosted by SIB Swiss Institute of Bioinformatics, which is the national ELIXIR Node in Switzerland, on behalf of the Swiss FEGA Partnership which includes 4 other key partners (ETH Zurich, Health 2030 Genome Center, Swiss Data Science Center and Switch). 2025 Documentation Title Version Description Mission, vision, values Federated EGA Mission, vision, values 1.0 The official Mission-Vision-Values statement for FEGA, produced and formally approved by the FEGA Strategic Committee in September 2025. Structure and Organisation Federated EGA Structure and Organisation 2.0 The structure of the FEGA network and service expectations, responsibilities and commitments. FEGA is organised into three tiers: Central EGA, FEGA Nodes and FEGA Affiliates. Strategic Committee Federated EGA Strategic Committee 1.1 Terms of reference for the FEGA Strategic Committee describe the purpose and objectives of the committee, which is to provide direction and strategic planning for the FEGA network. The committee receives input from, and provides feedback for the EGA Strategic Committee. Operations Committee Federated EGA Operations Committee 1.1 Terms of reference for the FEGA Operations Committee describe the purpose and objectives of the committee, which is to review operational performance and coordinate technical roadmaps of FEGA Nodes and Central EGA. The committee receives advice from, and provides operational reporting to the FEGA Strategic Committee. Guidelines Node Operations guidelines 2.1 An overview of the operational areas which require resources in order to create a FEGA Node. The document is based on more than 15 years' experience of EMBL-EBI and CRG operating the EGA and initial expericences of the inaugural FEGA Nodes. The operational areas of responsability are in line with the FEGA Maturity Model, which guides establishment and operation of FEGA Nodes. Collaboration Federated EGA Node Collaboration Agreement 1.3 Nodes are welcome to make a copy of this current version of the CA to start its review with their legal teams and understand the responsibilities of joining FEGA. Nevertheless, this version (the one with a watermark) shall not be signed: the official version needs to be obtained from FEGA prior signing through its official channels.

  Documentation about/projects-and-funders/federated-ega

• 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

• 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 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 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 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 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 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 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 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 Completed projects Project Duration Domain Funder Tags 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 LaMarató | 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 Fundació La Marató 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

• Security Overview

  Security Overview The European Genome-phenome Archive (EGA) houses consented human data under controlled access. Access decisions are handled by the relevant Data Access Committee (DAC), which autonomously manages requests through the DAC Portal. This document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. As security is a prime concern of the EGA, the EGA is a member of the Global Alliance for Genomics and Health (GA4GH) Data Security work stream. The EGA contributes and helps develop the recommendations outlined the GA4GH Security Technology Infrastructure document, which defines guidelines, best practices, and standards for building and operating an infrastructure that promotes responsible data sharing in accordance with the GA4GH Privacy and Security Policy. Explore the EGA dataflow to gain deeper insights! Accessing data in the EGA involves several steps. First, users need to create an EGA account. Once logged in, they can request access to data controlled by a DAC through the EGA website (see documentation). The DAC oversees these requests through the DAC Portal, and if approved, grants the necessary permissions to the user's EGA account, allowing them to access and download all relevant data and metadata for the requested dataset(s). The key points of EGA security strategy are: 1 Regular Risk Assessment The EGA regularly identifies and assesses risk related to the following: Breach of confidentiality,Breach of privacy or autonomy,Malicious or accidental corruption or destruction of data archived at EGA,Disruption of services provided by the EGA. 2 Risk mitigation The EGA implements and maintains safeguards to minimise the risks identified above in accordance with the 6 control objectives listed in Appendix 1 and outlined in the GA4GH Security and Infrastructure document.If a breach is discovered, the EGA applies a defined protocol to minimise damage. 3 Identity and authorisation management The EGA authenticates the identity of individuals or software accessing controlled access data held at the EGA.The EGA ensures an appropriate level of assurance (LoA) is applied to the identity consistent with the risk associated with that individual, such as multi-factor authentication for DACs.The EGA provides the minimum access rights and privileges consistent with the user’s identity, allowing access consistent with the GA4GH Privacy and Security Policy, as determined by the appropriate DAC. 4 Audit Logs The EGA maintains a set of logs recording: Changes to user access rights,Data access requests,Resource usage. 5 Cryptography, communication security, and data integrity The EGA ensures data transmission integrity using a hash function.All data transmitted to or from the EGA is end-to-end encrypted.All data at EGA is stored using strong encryption.Encryption keys are not stored in the same system as the encrypted data.All data archived at EGA must be accompanied by a signed submission statement ensuring appropriate consent or ethical approval has been obtained, and is in accordance with all applicable laws and regulations. The EGA has a defined protocol defining the response in the event of a security breach, and is continuing to work with the GA4GH Data Security Work Stream to help define best practice and associated standards for breach responses. Appendix 1 GA4GH Control Objectives Control Objective 1: Implement technology safeguards to minimise the risk of unauthorised access, use, or disclosure of confidential and private data.Control Objective 2: Implement technology safeguards to minimise the risk of discovery, access, and use of individuals’ clinical and genomic data, and individual identities, other than as authorised by applicable jurisdictional law, institutional policy, and individual consents.Control Objective 3: Implement technology safeguards to minimise the risk of accidental or malicious corruption or destruction of data.Control Objective 4: Implement technology safeguards to minimise the risk of disruption, degradation, and interruption of services enabling access to data.Control Objective 5: Implement technology safeguards to minimise the risk of potential security attacks and misuse of authorised accesses and privileges.Control Objective 6: Implement technology safeguards to promptly detect the failure to attain the above control objectives and to respond with proper countermeasures.Appendix 2Refer to the document below to learn more about EGA long-term data preservation policy and procedures at EMBL-EBI.Long-term data preservation

  Documentation about/security

• About

  About What's the EGA? The European Genome-phenome Archive (EGA) is a global network for permanent archiving and sharing of personally identifiable genetic, phenotypic, and clinical data generated for the purposes of biomedical research projects or in the context of research-focused healthcare systems. Jointly managed by the European Bioinformatics Institute (EMBL-EBI) in Cambridge (UK) and the Centre for Genomic Regulation (CRG) in Barcelona, we aim to advance biomedical research and promote personalised medicine worldwide by enabling discovery of and access to human genomic and health research data. The EGA contains data collected from individuals whose consent agreements authorise data release for specific research use to bona fide researchers. We ensure strict security measures to control access to the data and maintain patient confidentiality. With expertise in data management and technical infrastructure, we promote FAIR data reuse and enable researchers to share their data securely. By leveraging public funding and our strategic partnerships, the EGA provides a free service for permanent data storage, data discovery, and secure data access. In addition, we foster a federated network to provide transnational access to human research data in compliance with legal frameworks. For additional information about the EGA, please contact: Helen Parkinson and Mallory Freeberg EMBL European Bioinformatics Institute Arcadi Navarro, Roderic Guigó, and Jordi Rambla Center for Genomic Regulation History The European Genome-phenome Archive was launched in 2008 at the European Bioinformatics Institute (EMBL-EBI), an outstation of the European Molecular Biology Laboratory (EMBL), to address an identified need for archiving and sharing the results of genome-wide association studies from the Wellcome Trust Case Control Consortium. With the signing of a memorandum of understanding in 2013 and a formal agreement in 2016, the EGA became a joint project of EMBL-EBI and the Centre for Genomic Regulation (CRG). The two institutes work together to support the EGA services, including supporting submissions, website, strategic leadership, and data infrastructure developments. In 2022, the Federated EGA was officially launched with the signature of the first five countries: Finland, Germany, Norway, Spain, and Sweden. With more than 20 additional nodes worldwide preparing to join, the Federated EGA aims to become the largest human omics data sharing initiative towards understanding human health and disease. EGA overview If you're a researcher you may need to deposit, manage, or access genomic data in a secure and regulated way. The European Genome-phenome Archive (EGA) is a platform that facilitates these processes, ensuring that sensitive data is stored and shared in accordance with legal and ethical regulations. Submission process To start a submission, you need to become an EGA submitter. For that, you’ll need to sign a Data Processing Agreement (DPA) with us, that defines the terms and conditions under which your data will be processed and shared within the EGA system. The access to each study is controlled by its Data Access Committee (DAC). The DAC is responsible for managing data access requests and ensuring that the release of data is in accordance with the General Data Protection Regulation (GDPR). Please, note that once your data is released, all public metadata related to your study and dataset(s) will be searchable on the EGA website. However, the files are only accessible under controlled access, which means that a DAC has to agree to a previous data access request. Request process It is possible to submit an access request to data stored at the EGA. The DAC assigned to the study will assess the request and, if approved, grant access to the data. Requesters must provide sufficient justification for your request and comply with the intended data usage in order to get access to it. Each dataset is covered by a Data Access Agreement (DAA) that defines the terms and conditions of use for the specified dataset/s. The DAA is created and provided by the DAC, and must be signed by the individual requesting access to the given dataset/s. Download process Once the request for access is approved, the data and metadata can be downloaded. The EGA offers various download options to fit the needs: it is possible to preview files without downloading them, download specific files of interest, or even download terabytes of data. Overall, the EGA provides a secure and regulated environment for depositing, managing, and accessing human data. Regardless of the role - submitter, DAC member, or requester - the EGA provides assistance for each while ensuring that sensitive data is managed in an ethical and responsible manner. More information on how EGA handles data is available in the EGA dataflow.

  Documentation about/ega

• Jeju Genome Project DAC

  This Data Access Committee (DAC) evaluates and manages access requests for large-scale genomic and phenotypic datasets generated as part of the Jeju Genome Project (JGP). The committee's mission is to facilitate responsible data sharing to advance precision medicine and population genetics. The DAC ensures that data access is granted only to bona fide researchers who agree to the terms of the Data Access Agreement (DAA) and whose proposed research is strictly consistent with the informed consent provided by the participants and the ethical guidelines of the project.

  Dac EGAC50000000938

• Zimbabwe Mendelian Disorders Genomics DAC

  Data Access Committee responsible for reviewing and approving access requests to human genomic data generated from individuals with suspected Mendelian disorders. The DAC ensures ethical use of genomic data in accordance with institutional, national, and international guidelines, protecting participant privacy while enabling responsible data sharing for research purposes.

  Dac EGAC50000000963

• The Spatial Heterogeneity in Multiple Myeloma - from the Subclonal Architecture to the Immune Microenvironment (partly hipo_K08K)

  Multiple myeloma (MM) cells show pronounced heterogeneity not only within a given patient but also between spatially separated tumor loci in the bone marrow. Understanding this spatial heterogeneity is emerging as a critical challenge for the successful treatment of the disease. Yet, our understanding of spatial differences in the subclonal architecture, molecular signatures and interactions with the tumor microenvironment remains very limited. To address this shortcoming, we performed bulk and single-cell multi-region sequencing, including random bone marrow samples from the iliac crest and paired imaging-guided focal lesion specimens from 15 newly diagnosed MM patients. We found a median of 5 subclones per patient and unique subclones in focal lesions. Central features of spatial heterogeneity included a consistent down-regulation of the chemoattractant cytokines CXCL7 and CXCL12 in focal lesion tumor cells as well as a significant depletion of macrophages in the focal lesion microenvironment. In contrast, a site-specific expansion of T-cell clones was not detected in focal lesions. In conclusion, our results demonstrate the relevance of considering spatial heterogeneity with potential implications for immunotherapies and molecular studies analyzing the role of gene signatures and MM-microenvironment interactions in disease progression.

  Study EGAS00001006090

• The genomic landscape of Burkitt Lymphoma

  As part of the ICGC, the ICGC MMML-Seq project performed whole genome sequencing and RNA sequencing of Burkitt Lymphomas . Burkitt lymphomas are the most common B-cell lymphomas in childhood. Analyses were performed in concordance with the guidelines of the ICGC. The results define the genomic landscape of structural variants, somatic single nucleotide variants and mutational signatures in these lymphomas.

  Study EGAS00001002198

• Comparison of capture-based method for transcriptome profiling of formalin-fixed paraffin embedded tumor samples

  Background: The need for fresh frozen (FF) tissue limits implementing RNA sequencing (RNA-seq) in the clinic. The majority of clinical samples are stored as formalin-fixed, paraffin-embedded (FFPE) tissues. Exome capture platforms have been developed for RNA-seq from FFPE samples. However, these methods have not been systematically compared. Methods: Transcriptomic analysis of 32 FFPE tumor samples from 11 patients was performed using three exome capture-based methods: Agilent SureSelect V6, TWIST NGS Exome, and IDT XGen Exome Research Panel. We compared these methods to TruSeq RNA-seq of fresh frozen (FF-TruSeq) tumor samples from the same patients. We assessed the recovery of clinically relevant biological features. Results: The Spearman's correlation coefficients between the global expression profiles of the three capture-based methods from FFPE and matched FF-TruSeq were high (rho = 0.72-0.9, p &lt; 0.05). A significant correlation between the expression of key immune genes between individual capture-based methods and FF-TruSeq (rho = 0.76-0.88, p &lt; 0.05) was observed. All exome capture-based methods reliably detected outlier expression of actionable genes, including ERBB2, MET, NTRK1, and PPARG. In urothelial cancer samples, the Agilent assay was associated with the highest molecular subtype concordance with FF-TruSeq (Cohen's k = 0.7, p &lt; 0.01). Both Agilent and IDT detected all the clinically relevant fusions that were initially identified in FF-TruSeq. Conclusion: All exome capture-based methods had comparable performance and concordance with FF-TruSeq. By enabling the interrogation of FFPE tumor samples, our findings will enable the implementation of RNA-seq in the clinic to guide precision oncology approaches.

  Study EGAS00001005255

• Papuan Y chromosome Diversity Panel

  Island Southeast Asia and Oceania host one of the world’s richest assemblages of human phenotypic, linguistic and cultural diversity. Despite this, the region’s male genetic lineages are globally among the last to remain unresolved. We compiled ~9.7 Mb of Y chromosome sequence from a diverse sample of over 380 men from this region, including 152 first reported here. The granularity of this dataset allows us to fully resolve and date the regional Y chromosome phylogeny. This new high-resolution tree confirms two main population bursts: multiple rapid diversifications following the region’s initial settlement ~50 kya, and extensive expansions &lt;6 kya. Notably, ~40-25 kya the deep rooting local lineages of C-M130, M-P256, and S-B254 show almost no further branching events in Island Southeast Asia, New Guinea and Australia, matching a similar pause in diversification seen in maternal mitochondrial DNA lineages. The main local lineages start diversifying ~25 kya, at the time of the Last Glacial Maximum. This improved Y chromosome topology highlights localized events with important historical implications, including pre-Holocene contact between Mainland and Island Southeast Asia, potential interactions between Australia and the Papuan world, and a sustained period of diversification following the flooding of the ancient Sunda and Sahul continents as the insular landscape observed today formed. The high-resolution phylogeny of the Y chromosome presented here thus enables a detailed exploration of

  Study EGAS00001006025

• Illumina HumanCoreExome genotyping data from the TEENAGE (TEENs of Attica: Genes and Environment) study.

  The TEENAGE study is a cross-sectional study comprising healthy Greek adolescents. The study was conducted according to the guidelines specified in the Declaration of Helsinki and all procedures involving human subjects were approved by the Institutional Review Board of Harokopio University and the Greek Ministry of Education, Lifelong Learning and Religious Affairs. The TEENAGE study target population comprised adolescent students aged 13 to 15 years attending the first three classes of public secondary schools located in the wider Athens area of Attica. The regions across Attica from which students were recruited were physically similar and all urban in nature. Sampling of regions and schools selected to participate was random. Students were enrolled from the wider urban region to ensure that they were coming from families with varying educational background and socio-economic status. Moreover, in order to exclude any vast economic disparities, all participating schools were exclusively public schools, which are free of charge. A total of twenty-four schools participated in the study out of 285 junior secondary public schools in Attica. Anthropometric, medical and dietary information was obtained. DNA samples were genotyped using Illumina HumanCoreExome BeadChips (Illumina, San Diego, CA, USA) at the Wellcome Trust Sanger Institute, Hinxton, UK. Genotypes were called using GenCall (Illumina Genome Studio) followed by zCall and quality control (QC) was performed in two stages (pre- and post-zCall).

  Study EGAS00001001001

• Mutant KIT as imatinib-sensitive target in metastatic sinonasal carcinoma (H021)

  Sinonasal carcinomas (SNCs) comprise various rare tumor types that are characterized by marked histologic diversity and largely unknown molecular profiles, yet share an overall poor prognosis owing to an aggressive clinical course and frequent late-stage diagnosis. The lack of effective systemic therapies for locally advanced or metastatic SNC poses a major challenge to therapeutic decision making for individual patients. Here, we used whole-exome and transcriptome sequencing to identify a KIT exon 11 mutation (c.1733_1735del, p.578_579del) as actionable target in a patient with metastatic SNC whose tumor, despite all diagnostic efforts, could not be assigned to any known SNC category and was refractory to multimodal therapy. Molecularly guided treatment with imatinib resulted in a dramatic and durable response with remission of nearly all tumor manifestations, indicating a dominant driver function of mutant KIT in this tumor. This observation highlights the potential of unbiased genomic profiling for uncovering the vulnerabilities of individual malignancies, particularly in rare and unclassifiable tumors, and underscores that KIT exon 11 mutations represent tractable therapeutic targets across different histologies.H021

  Study EGAS00001001845

• IDENTIFICATION AND TARGETED MANAGEMENT OF A PATIENT WITH A NEURODEGENERATIVE DISORDER CAUSED BY BIALLELIC MUTATIONS IN SLC5A6

  We describe a sibling pair displaying an early infantile-onset, progressive neurodegenerative phenotype, with symptoms of developmental delay and epileptic encephalopathy developing from 12 to 14 months of age. Using whole exome sequencing, compound heterozygous variants were identified in SLC5A6, which encodes the sodium-dependent multivitamin transporter (SMVT) protein. SMVT is an important transporter of the B-group vitamins biotin, pantothenate and lipoate. The protein is ubiquitously expressed and has major roles in vitamin uptake in the digestive system, as well as transport of these vitamins across the blood-brain barrier. Pathogenicity of the identified variants was demonstrated by impaired biotin uptake of mutant SMVT. Identification of this vitamin transporter as the genetic basis of this disorder guided targeted therapeutic intervention, resulting clinically in improvement of the patient’s neurocognitive and neuromotor function. This is the second report of biallelic mutations in SLC5A6 leading to a neurodegenerative disorder due to impaired biotin, pantothenate and lipoate uptake. The genetic and phenotypic overlap of these cases confirms mutations in SLC5A6 as the genetic cause of this disease phenotype. Recognition of the genetic disorder caused by SLC5A6 mutations is essential for early diagnosis and to facilitate timely intervention by triple vitamin (biotin, pantothenate and lipoate) replacement therapy.

  Study EGAS00001003861

• The Simons Genome Diversity Project: 300 genomes from 142 diverse populations

  Here we report the Simons Genome Diversity Project data set: high quality genomes from 300 individuals from 142 diverse populations. These genomes include at least 5.8 million base pairs that are not present in the human reference genome. Our analysis reveals key features of the landscape of human genome variation, including that the rate of accumulation of mutations has accelerated by about 5% in non-Africans compared to Africans since divergence. We show that the ancestors of some pairs of present-day human populations were substantially separated by 100,000 years ago, well before the archaeologically attested onset of behavioural modernity. We also demonstrate that indigenous Australians, New Guineans and Andamanese do not derive substantial ancestry from an early dispersal of modern humans; instead, their modern human ancestry is consistent with coming from the same source as that in other non- Africans.

  Study EGAS00001001959

• Ultra-Fast Patient-Derived Xenografts Identify Functional and Spatial Tumour Heterogeneities that Drive Therapeutic Resistance

  Treatment of patients with advanced cancers increasingly relies on agents targeting specific molecular or cellular aberrations. These expensive therapies often fail because of pre-existing drug resistance. Intra-tumoural molecular and micro-environmental heterogeneity resistance can create resistance in one or more subclones of a tumour, leading to spatio-functional heterogeneity. We created a rapid approach for quantifying tumour functional phenotypes based on tumour-implantation into the chorioallantoic membrane of chick embryos. We apply this technique to 43 separate biopsies from 6 patients with renal cell carcinoma (RCC) with 36 replicates per biopsy, achieving a 93.6% engraftment rate (1449/1548). Challenging these models with sunitinib, an anti-angiogenic therapy frequently used in RCC allowed us to quantify spatio-functional heterogeneity in individual patients. Prediction of de novo drug resistance in advanced cancer patients would facilitate precision medicine by tailoring systemic therapies and improve clinical trial design outcome measures. We describe a patient-derived xenograft platform where fresh patient tumour samples are implanted into the chorioallantoic membrane (CAM) of chick embryos at high engraftment efficiencies, permitting large scale “tumour avatar” studies to guide the selection of drugs and to predict clinical drug resistance outcomes in renal cell carcinoma (RCC) patients. Applying this “tumour avatar” model in a co-clinical trial on RCC patients, we observe intra-tumoural functional heterogeneity with sunitinib treatment, revealing the presence of drug-resistant clones prior to the initiation of therapy. Multi-regional exome Matched DNA sequencing of the primary tumour and metastases revealed DNA mutational signatures associated with sunitinib resistance at baseline and after treatment. These These studies demonstrate a rapid and affordable method of findings confirm the existence of genetic and surveying functional tumour heterogeneities heterogeneity.

  Study EGAS00001002627

• Genetic_screening__of_GPI_anchor_protein_synthesis__

  This study will analyse the guide sequence which were used for making mutations in the Cas9-expressing cells. We used GeCKO v2 library which were released by Feng Zhang, 2014. This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Study EGAS00001001256

• RNA-sequencing of six Pilocytic astrocytoma tumors

  Pilocytic astrocytoma (PA) is the most common pediatric brain tumor. A recurrent feature of PA is deregulation of the mitogen activated protein kinase (MAPK) pathway most often through KIAA1549-BRAF fusion, but also by other BRAF- or RAF1-gene fusions and point mutations (e.g. BRAFV600E). These features may serve as diagnostic and prognostic markers, and also facilitate development of targeted therapy. The aim of this study was to characterize the genetic alterations underlying the development of PA tumor in six cases, and evaluate methods for fusion oncogene detection. Using a combined analysis of RNA sequencing and copy number variation data we identified a new BRAF fusion involving the 5’ gene fusion partner GTF2I (7q11.23), not previously described in PA. The novel GTF2I-BRAF 19-10 fusion was found in one case, while the other five cases harbored the frequent KIAA1549-BRAF 16-9 fusion gene. Comparing fusion detection methods, Fluorescence in situ hybridization with BRAF break apart probe was the most sensitive method for detection of the two different BRAF rearrangements (GTF2I-BRAF and KIAA1549-BRAF). Our finding of a novel BRAF fusion in PA further emphasis the important role of B-Raf in tumorigenesis of these tumor types. Also, the growing list of BRAF/RAF gene fusions suggests these to be informative tumor markers in molecular diagnostics, which could guide future treatment strategies.

  Study EGAS00001002149

• Illumina HumanOmniExpress genotyping data from the TEENAGE (TEENs of Attica: Genes and Environment) study.

  The TEENAGE study is a cross-sectional study comprising healthy Greek adolescents. The study was conducted according to the guidelines specified in the Declaration of Helsinki and all procedures involving human subjects were approved by the Institutional Review Board of Harokopio University and the Greek Ministry of Education, Lifelong Learning and Religious Affairs. The TEENAGE study target population comprised adolescent students aged 13 to 15 years attending the first three classes of public secondary schools located in the wider Athens area of Attica. The regions across Attica from which students were recruited were physically similar and all urban in nature. Sampling of regions and schools selected to participate was random. Students were enrolled from the wider urban region to ensure that they were coming from families with varying educational background and socio-economic status. Moreover, in order to exclude any vast economic disparities, all participating schools were exclusively public schools, which are free of charge. A total of twenty-four schools participated in the study out of 285 junior secondary public schools in Attica. Anthropometric, medical and dietary information was obtained. DNA samples were genotyped using Illumina HumanOmniExpress BeadChips (Illumina, San Diego, CA, USA) at the Wellcome Trust Sanger Institute, Hinxton, UK. Genotype calling algorithm used was Illuminus (Teo et al., 2007).

  Study EGAS00001000996

• Systems biology of Colorectal Cancer

  Colorectal cancer (CRC) is one of the most common cancers in both males and females, and it is perhaps the best understood of all epithelial tumors in terms of its molecular origin. Yet, despite large amount of work that has concentrated on understanding of colon tumorigenesis, we still do not know the full complement of molecular lesions that are individually necessary – and together sufficient – to cause colorectal cancer. Neither do we understand why some specific mutations that are relatively rare in other tumors (e.g. loss of the APC tumor suppressor) are extremely common in colorectal cancer. We propose here to use the tools of systems biology to develop a quantitative and comprehensive model of colorectal tumorigenesis. The model will include identification of cell-type specific and oncogenic pathways that contribute to colon tumorigenesis, and explain in molecular detail how a genotype of an individual CRC leads to activation of downstream genes that drive uncontrolled cell growth. This model will subsequently be used to find novel therapeutic targets, to guide genetic screening to identify individuals with elevated risk for developing CRC, and to classify patients into molecular subgroups to select the treatment combination that is optimal for each patient (personalized medicine). The specific objectives of the SYSCOL project are: 1. Identify genetic markers for individual risk using genotyping and sequencing of constitutional DNA from sporadic and familial CRC cases and controls 2. Identify genes and regulatory elements that contribute to colorectal cancer cell growth 3. Use data from Aims 1-2 to develop a quantitative model for colorectal tumorigenesis 4. Apply the model for identification of high-risk individuals, for molecular classification of the disease, and for identification of novel molecular treatment targets

  Study EGAS00001000854

• Genome-wide expression profiles to compare array-based, RNAseq and NanoString technologies in patients with resected pancreatic ductal carcinoma.

  Using formalin-fixed paraffin embedded (FFPE) tissues collected prospectively in patients with resected pancreatic ductal carcinoma (PDC) we generated genome-wide expression profiles to compare array-based, RNAseq and NanoString technologies. Samples included in the study were collected 17 patients. After careful selection by the pathologist of 17 malignant cells-enriched, 7 stroma-enriched, and 6 normal (normal pancreas in 4 cases and normal duodenum in 2 cases) regions, sections were macrodissected, and total RNA extracted. Two additional FFPE-frozen matched-paired PDAC from our local Biobank were included. Our study represents the most extensive work comparing three technologies to generate gene expression profiles from FFPE samples, and provides technical guidance for future biomarker studies in samples collected prospectively in the context of clinical trials.

  Study EGAS00001002501

• Papuan Genomes: whole genome sequencing

  The genomes of 25 individuals from Papua New Guinea was sequenced to high depth (30x) to address population genetic questions relating to the spread of humans outside of Africa and the peopling of Sahul (the continent of Greater Australia). The study design of this project was to sequence small numbers of genomes from several geographically distinct Papuan groups, focusing on the highland regions that are thought to have been more isolated, to enable comparisons between populations within Papua New Guinea and with Australian Aboriginal populations. Data from this project feed directly into on-going projects on the genetic history of Australia and also serve as a first look at the population genomics of the Papuan highlands.

  Study EGAS00001001247

• A Genomic History of Aboriginal Australia

  The population history of Aboriginal Australians remains largely uncharacterised. We generated high-coverage genomes for 83 Aboriginal Australians (speakers of Pama-Nyungan languages) and 25 Papuans from the New Guinea Highlands. We find that Papuan and Aboriginal Australian ancestors diversified 25-40 thousand years ago (kya), suggesting early population structure in the ancient continent of Sahul (Australia, New Guinea and Tasmania). However, all studied Aboriginal Australians descend from a single founding population that differentiated ~10-32 kya. We infer a population expansion in northeast Australia during the Holocene (past c.10 kya) associated with limited gene flow from this region to the rest of Australia consistent with the spread of the Pama-Nyungan languages. We estimate that Aboriginal Australians and Papuans diverged from Eurasians 51-72 kya, following a single out of Africa dispersal, and subsequently admixed with different archaic populations. Finally, we report evidence of selection in Aboriginal Australians potentially associated with living in the desert.

  Study EGAS00001001766

• Sequencing data of multiple sarcoma samples for personalized medicine and endotype identification

  Sequencing data derived from multiple patient samples was used to guide multiple patient-specific experiments and identify potential therapeutic options. These diseases are rare and high-risk (undifferentiated pleomorphic sarcoma, rhabdomyosarcoma) and thus have few available validated clinical options. This leaves the population of patients with few options if, and when, standard therapy fails to cure or control disease. An aspect of the personalize therapy design included the identification of broader disease endotypes (a combination of genetic and clinical data describing patient status) to identify subgroups of the individual disease that could better define treatments and could segment patient populations for deeper preclinical research.

  Study EGAS00001003981

• Reference Exome Data for a Northern Brazilian population

  Whole exome sequencing (WES) is a popular technology widely used in the diagnosis of rare genetic diseases and provides useful variant data for analysis of complex diseases. However, there is not always adequate population-specific reference data available to assist clinical geneticists in assigning a diagnostic variant to a specific clinical condition. Here we provide a catalogue of variants called after sequencing the exomes of 45 babies from the State of Rio Grande do Nord in Brazil. Sequence data were processed using an ‘intersect-then-combine’ (ITC) approach, using GATK and SAMtools to call variants. A total of 612,761 variants were identified in at least one individual in this Brazilian Cohort, including 559,448 single nucleotide variants (SNVs) and 53,313 insertion/deletions. Of these, 58,111 overlapped with nonsynonymous (nsSNVs) or splice site (ssSNVs) SNVs in dbNSFP. As an aid to clinical diagnosis of rare diseases, we used the American College of Medicine Genetics and Genomics (ACMG) guidelines to assign pathogenic/likely pathogenic status to 439 (0.755%) of the 58,111 nsSNVs and ssSNVs. Our data set provides a useful reference point for diagnosis of rare diseases in Brazil.

  Study EGAS00001004112

• Integration of genomics and histology reveals diagnosis and effective therapy of refractory cancer of unknown primary with PDL1 amplification (H021)

  Identification of the tissue of origin in cancer of unknown primary (CUP) poses a diagnostic challenge and is critical for directing site-specific therapy. Currently, clinical decision making in patients with CUP primarily relies on histopathology and clinical features. Comprehensive molecular profiling has the potential to contribute to diagnostic categorization and, most importantly, guide CUP therapy through identification of actionable lesions. We here report the case of an advanced-stage malignancy initially mimicking poorly differentiated soft-tissue sarcoma that did not respond to multi-agent chemotherapy. Molecular profiling within a clinical whole-exome and transcriptome sequencing program revealed a heterozygous, highly amplified KRAS G12S mutation, compound-heterozygous TP53 mutation/deletion, high mutational load, and focal amplification of chromosomes 9p (including PDL1 [CD274] and JAK2) and 10p (including GATA3). Integrated analysis of molecular data and conventional histopathology suggested a diagnosis of triple-negative breast cancer (TNBC) and provided a rationale for immune checkpoint inhibitor therapy with pembrolizumab, which resulted in rapid clinical improvement and a lasting partial remission. Analysis of 157 TNBC samples from The Cancer Genome Atlas revealed focal, high-level PDL1 amplification coinciding with excessive PDL1 mRNA expression in 24% of cases. Collectively, these results illustrate the diagnostic utility of multidimensional tumor profiling in cases with non-descript histology and immune phenotype, demonstrate the predictive power of genomic PDL1 amplification for immune checkpoint inhibition, and suggest a targeted therapeutic strategy in chromosome 9p24.1/PDL1-amplified cancers.H021

  Study EGAS00001001846

• Evolutionary dynamics of residual disease in human glioblastoma

  Glioblastoma is the most common and aggressive adult brain malignancy against which conventional surgery and chemoradiation provide limited benefit. Even when a good treatment response is obtained, recurrence inevitably occurs either locally (c.80%) or distally (c.20%), driven by cancer clones that are often genomically distinct from those in the primary tumour. Glioblastoma cells display a characteristic infiltrative phenotype, invading the surrounding tissue and often spreading across the whole brain. We hypothesised that cancer cells responsible for relapse reside in two compartments of residual disease that are left behind after treatment: the infiltrated normal brain parenchyma, and the sub-ventricular zone (SVZ). In this model, residual disease subclones diverge early during glioblastoma evolution, may remain dormant in the normal parenchyma and are responsible for recurrence. To test our hypothesis, we performed whole-exome sequencing of 69 multi- region samples collected using fluorescence-guided resection from 11 patients, including the infiltrating tumour margin (M) and the SVZ for each patient, as well as matched blood. We used a phylogenomic approach to dissect the spatio-temporal evolution of each tumour and unveil the relation between residual disease and the main tumour mass. We also analysed two patients with paired primary-recurrence samples with matched residual disease. Our results suggest that the infiltrative phenotype is an early evolutionary trait of glioblastoma, giving rise to the tumour mass detected at surgery. After treatment, the same infiltrative clone may seed the growth of a recurrent tumour, thus representing the ‘missing link’ between the primary tumour and recurrent disease. These results are consistent with recognised clinical phenotypic behaviour and suggest that more specific therapeutic targeting of cells in the infiltrated brain parenchyma may improve patient’s outcome.

  Study EGAS00001003043

• Spatial genomic heterogeneity in multiple myeloma revealed by multi- region sequencing

  The bone-marrow (BM) containing skeletal system is the reservoir of Multiple Myeloma (MM), the malignant counterpart of antibody-secreting plasma cells. To gain insight into its spatial clonal architecture, we performed multi-region whole-exome sequencing of radiology-guided fine-needle aspirates from 51 MM patients. We found spatial genomic heterogeneity in a substantial proportion of cases including bi-allelic inactivation of tumor suppressors and mutations affecting cancer genes. The amount of heterogeneous mutations associated with the size of focal tumor lesions in whole body imaging consistent with focal outgrowth of highly advanced clones. In conclusion, our results support the regional initiation of transformation processes leading to high-risk disease as well as the pre-existence of key driver events in restricted areas. As such, our study does not only provide new insights in the underlying biology of MM progression but also has considerable implications for standard diagnostic approaches in the clinic.

  Study EGAS00001002111

• PanCuRx Translational Research Initiative

  The goal of the PanCuRx TRI is to seek solutions to the high fatality rate of pancreatic adenocarcinoma (PDAC), the most common type of pancreatic cancer, by generating new knowledge about the genetics and biology of the disease, mechanisms of how tumours grow and tailored treatment options. PDAC is the fourth leading cause of cancer death in Canada and is expected to become the second-leading cause of cancer death within the next decade. The current five-year survival rate of eight per cent is the lowest of all epithelial cancers. There are major clinical challenges to treating the disease, including the fact that PDAC spreads to other parts of the body early so surgical removal of the tumour benefits few patients, that PDAC has proven relatively resistant to systemic therapies such as chemotherapy and that there has been limited benefit from the use of newer molecular targeted agents. The PanCuRx team has created the world’s first resource of tumour-purified PDAC whole genomes; more than 500 PDAC samples, with combined clinical annotation, have been successfully sequenced and analyzed at the Ontario Institute for Cancer research in Toronto. The resulting clinical genomic resource created from this data has led to multiple new findings that have established a framework to better understand PDAC biology and lays the foundation for new genomic approaches to better understanding the disease. The team also launched a clinical trial called COMPASS (Comprehensive Molecular Characterization of Advanced Ductal Pancreas Adenocarcinoma for Better Treatment Selection: A Prospective Study), which is recruiting patients with advanced PDAC (both locally advanced and metastatic) at The Princess Margaret Cancer Centre (PM) in Toronto. The study uses the molecular results from individual patient tumours to guide selection of better second line treatment on a case-by-case basis. The primary objective of the initial study was to assess the feasibility of collecting tumour materials from patients with advanced PDAC and delivering results within 56 days of biopsy. Having achieved this objective, the trial has expanded to other cancer centres across Canada. Pancreatic cancer is one of the most deadly forms of cancer and outcomes have not improved in four decades. The PanCuRx initiative is providing a better understanding of the disease and actively applying new knowledge to cancer patients through clinical trials. This knowledge will help to improve quality of life and prolong survival for pancreatic cancer patients worldwide.

  Study EGAS00001002543

• Drug screening and whole genome sequencing of primary cells and cell lines from ovarian cancer patients to associate genomic aberrations with in vitro drug sensitivities

  Identifying drugs for cancers with poor prognosis like ovarian cancer (OC) is hindered by inappropriate cell models and the limitations of current viability assays. We developed an automated confocal microscopy-based live cell assay (DeathPro) that robustly de-convolves cell death and proliferation over time by employing a specific image processing strategy. Using DeathPro, we screened nine OC patient-derived cell lines and one normal cell line (HOSEpiC) with 22 drugs or combinations. Whole genome was performed to analyze if the cell lines harbor OC-typical genomic aberrations and to relate genomic features to drug sensitivities. Commonly observed alterations in OC patients like TP53 mutations and MYC or PI3KCA amplifications were absent in the normal cell line but frequently detected in the OC cell lines. Moreover, genome-derived homologous recombination deficiency (HRD) scores of the OC cell lines correlated with their responses to carboplatin, olaparib and DNA demethylation drugs. Overall, we propose an imaging-based platform to guide drug development and genome-drug sensitivity analysis.

  Study EGAS00001002239

• Prostate Cancer and Normal Adjacent Prostate RNA-seq samples, NGS-ProToCol

  The dataset "Prostate Cancer and Normal Adjacent Prostate RNA-seq samples, NGS-ProToCol" includes 41 Normal Adjacent Prostate and 51 ribo-depleted Prostate Cancer RNA-seq samples. ---- Detection of fusion transcripts and their genomic breakpoints from RNA sequencing data Youri Hoogstrate, Malgorzata A. Komor, René Böttcher, Job van Riet, Harmen J. G. van de Werken, Stef van Lieshout, Ralf Hoffmann, Evert van den Broek, Anne S. Bolijn, Natasja Dits, Daoud Sie, David van der Meer, Floor Pepers, Chris H. Bangma, Geert J. L. H. van Leenders, Marcel Smid, Pim French, John W.M. Martens, Wilbert van Workum, Peter J. van der Spek, Bart Janssen, Eric Caldenhoven, Christian Rausch, Mark de Jong, Andrew P. Stubbs, Gerrit A. Meijer, Remond J.A. Fijneman, Guido Jenster

  Study EGAS00001002816

• Identification_of_synthetic_lethal_genes_by_CRISPR_Cas9_library

  Sequencing is performed on PCR products from the amplification of gRNA segments introduced into cell lines (some are commercial, some are derived by collaborators, as described in HMDMC 13/076). Cellular DNA or RNA are not sequenced. This data is defined as "Other Biological/Biochemical Assay Data" under the WTSI datasharing guidelines and consequently will be released at the time of publication and/or through faculty websites. SEQUENCING DETAILS: in October 2016 3 DNA samples will be submitted for PCR amplification and purification through CGP pipeline using Thompson's custom primer set and PCR settings and sequencing with Hiseq using a custom protocol (with 3 forward reads to read sgRNA1, sgRNA2 and the index, optimized with Illumina Bespoke Sanger team); read length 50bp. The following set of samples will be submitted in later 2016 and ealry 2017 as cell pellet to be processed through CGP Cas9 pipeline (Thompson's oligos and protocols) and sequences on Hiseq (same custom sequencing protocol described above) We are utilizing a custom CRISPR/Cas9 library to identify synthetic lethal gene pairs. Cells will be transduced with LV expressing Cas9, then infected with LV expressign the library of 42'000 sgRNA pairs. Cell pellet will be collected from the cell population at different timepoints. The samples will be processed by CGP pipeline customized for the specific protocol and then sequenced to identify the 19bp of the sgRNA and quantify their representation.

  Study EGAS00001002117

• Dynamics of multiple resistance mechanisms in plasma DNA and their clinical implications for NSCLC patients receiving EGFR-targeted therapies

  Background:The development of resistance mechanisms to targeted therapies is complicated by underlying tumour heterogeneity. When multiple resistance mechanisms co-exist, identifying the dominant driver(s) is critical for selection of treatment. Patients and methods:We studied the relative dynamics of multiple oncogenic drivers and resistance mechanisms in 50 patients with EGFR-mutant non-small cell lung cancer (NSCLC), during treatment with gefitinib and hydroxychloroquine (NCT00809237). We performed digital PCR and targeted deep sequencing of cell-free DNA from longitudinal plasma samples from all patients, and shallow whole genome sequencing of serial samples from three patients who underwent histological transformation to small-cell lung cancer (SCLC). ResultsEGFR activating mutations were assessed in tumour samples and accurately identified in plasma samples of 95% of patients (41/43). We identified additional mutations including EGFR T790M (31/50, 62%), TP53 (23/50, 46%), PIK3CA (7/50, 14%), and PTEN (4/50, 8%), and tracked their relative levels in plasma. Patients with both TP53 and EGFR mutations detected in plasma pre-treatment tended to have worse overall survival than those where only EGFR was detected. The resistance-conferring EGFR T790M mutation was identified in 62% of the patients who progressed. Changes in relative levels of T790M and activating mutations in EGFR corresponded to clinical responses in two patients who were given sequential treatments. Patients who progressed without T790M detected in plasma had worse PFS during TKI continuation, and developed alternative resistance mechanisms, that could be identified in plasma DNA, including SCLC-associated copy number changes and TP53 mutations, that tracked with progression and response to subsequent therapies. Conclusion:Longitudinal analysis of multiple oncogenic drivers in ctDNA may help identifying dominant mechanisms of resistance to EGFR-targeted therapies, and highlight the importance of monitoring genetic events that are not direct drug targets but provide non-invasive molecular information that may guide clinical management.

  Study EGAS00001002908

• Enhanced detection of circulating tumor DNA by fragment size analysis

  Existing methods to improve detection of circulating tumor DNA (ctDNA) have focused on sensitivity for detecting genomic alterations but have rarely considered the biological properties of plasma cell-free DNA (cfDNA). We hypothesized that differences in fragment lengths of circulating DNA could be exploited to enhance sensitivity for detecting the presence of ctDNA and for non-invasive genomic analysis of cancer. We surveyed ctDNA fragment sizes in 344 plasma samples from 200 cancer patients using low-pass whole-genome sequencing (0.4×). To establish the size distribution of mutant ctDNA, tumor-guided personalized deep sequencing was performed in 19 patients. We detected enrichment of ctDNA in fragment sizes between 90–150 bp, and developed methods for in vitro and in silico size selection of these fragments. Selecting fragments between 90–150 bp improved detection of tumor DNA, with more than 2-fold median enrichment in &amp;gt;95% of cases, and more than 4-fold enrichment in &amp;gt; 10% of cases. Analysis of size-selected cfDNA identified clinically actionable mutations and copy number alterations that were otherwise not detected. Identification of plasma samples from patients with advanced cancer was improved by predictive models integrating fragment length and copy number analysis of cfDNA, with AUC&amp;gt; 0.99 compared to AUC &amp;lt; 0.80 without fragmentation features. Increased identification of cfDNA from patients with glioma, renal, and pancreatic cancer was achieved with AUC &amp;gt; 0.91, compared to AUC &amp;lt; 0.5 without fragmentation features. Fragment size analysis and selective sequencing of specific fragment sizes can boost ctDNA detection. This could reduce the required depth of cfDNA sequencing for clinical applications, earlier diagnosis and study of tumor biology.

  Study EGAS00001003258

• The genomic landscape of follicular and diffuse large B-cell lymphoma

  As part of the ICGC, the ICGC MMML-Seq project performed whole genome sequencing and RNA sequencing of follicular and diffuse large B-cell lymphoma. Follicular and diffuse large B-cell lymphomas are the most common B-cell lymphomas in adulthood. Analyses were performed in concordance with the guidelines of the ICGC. The results define the genomic landscape of structural variants, somatic single nucleotide variants and mutational signatures in these lymphomas

  Study EGAS00001002199

• This study explored and validated the clinical application of targeted NGS of circulating tumor DNA in identifying tumor-specific mutations and uncovering clinical actionable targets in a variety of solid tumors in large patient cohorts.

  Cancer is a disease of genetic alterations. Comprehensive genetic diagnosis is needed to match each patient to appropriate cancer therapy. However, acquisition of representative tumor samples is invasive and often infeasible. Circulating tumor DNA (ctDNA) is a promising non-invasive biomarker for cancer mutational profiling. Here we implemented targeted next generation sequencing (NGS) with a customized pan-cancer gene panel on 605 clinical ctDNA samples in multiple cancer types. Overall, tumor-specific mutations were identified in 87% of ctDNA samples, with mutation spectra highly concordant with their matched tumor tissues. 71% of patients have at least one clinical actionable mutation with 76% of which have suggested drugs approved or in clinical trials. In particular, our study reveals a unique mutation spectrum in Chinese lung cancer patients, which could be used to guide treatment decision and monitor the appearance of drug-resistant mutations. Taken together, our study demonstrated the clinical utility of target NGS-based ctDNA mutational profiling to guide cancer treatment decision.

  Study EGAS00001002251

• Bioinformatic Methods and Bridging of Assay Results for Reliable Tumor Mutational Burden Assessment in Non-Small Cell Lung Cancer

  Tumor mutational burden (TMB) has emerged as a predictive biomarker of response to immune checkpoint inhibitors. Standardization of TMB measurement is essential for implementing diagnostic tools to guide treatment. Here we evaluate bioinformatic TMB analysis by whole exome sequencing (WES) in formalin-fixed, paraffin-embedded samples. In CheckMate 026, TMB was retrospectively assessed in 312 patients with non-small cell lung cancer (58% of the intent-to-treat population) who received first-line nivolumab treatment or chemotherapy. We examined the sensitivity of TMB assessment to bioinformatic filtering methods and assessed concordance between TMB data derived by WES and the FoundationOne CDx™ assay. TMB scores comprising synonymous, indel, frameshift, and nonsense mutations (all mutations) were 3.1-fold higher than data including missense mutations only, but values were highly correlated (Spearman’s r = 0.99). Scores from CheckMate 026 samples including missense mutations only were similar to those generated from data in The Cancer Genome Atlas, but those including all mutations were generally higher. Using databases for germline subtraction (instead of matched controls) showed a trend for race-dependent increases in TMB scores. Parameter variation can therefore impact TMB calculations, highlighting the need for standardization. Encouragingly, WES and FoundationOne CDx outputs were highly correlated (Spearman’s r = 0.90) and differences could be accounted for by empirical calibration, suggesting that reliable TMB assessment across assays, platforms and centers is achievable.

  Study EGAS00001003661

• Reference epigenomes generated as part of the International Human Epigenomics Consortium (IHEC)

  The Centre for Epigenome Mapping Technologies (CEMT) is an epigenome sequencing platform funded by the Canadian Institutes of Health Research (CIHR) and Genome BC as part of the Canadian Epigenetics, Environment and Health Research Consortium (CEEHRC). CEMT aims to produce 100 human reference epigenomes, each comprising the following datasets: whole genome; whole genome bisulfite and oxidative bisulfite; transcriptome; microRNA; and chromatin immunoprecipitation (ChIP)-seq for the core chromatin marks (H3K4me1, H3K4me3, H3K9me3, H3K27me3, H3K36me3, and H3K27ac).CEEHRC is a full member of the International Human Epigenomics Consortium (IHEC), which aims to coordinate the production of 1,000 reference maps of human epigenomes for key cellular states relevant to health and diseases. As such, all datasets submitted by the CEMT platform conform to IHEC assay standards and metadata guidelines.

  Study EGAS00001000552

• Successful BRAF/MEK-inhibition in a young patient with BRAF V600E-mutated extrapancreatic acinar cell carcinoma (HIPO-021)

  Pancreatic acinar cell carcinoma (PAC) is a rare disease with a poor prognosis. Treatment options for metastatic PAC are limited and often follow chemotherapeutic regimens for pancreatic ductal adenocarcinoma. Although recurrent genomic alterations, such as BRAF fusions and defects in genes involved in homologous recombination DNA repair, have been described in PAC, data on the clinical efficacy of molecularly guided, targeted treatment are scarce. Here we describe the case of a 27-yr-old patient with BRAF V600E-mutated PAC who was successfully treated with a combination of BRAF and MEK inhibitors. The patient presented to our clinic with abdominal pain and weight loss. Imaging showed extensive retroperitoneal disease as well as mediastinal lymphadenopathy. Because of elevated alpha-fetoprotein (AFP) levels and inconclusive histologic findings, a germ cell tumor was suspected; however, PEI chemotherapy was unsuccessful. A repeat biopsy yielded the diagnosis of PAC and treatment with FOLFIRINOX was initiated. Comprehensive molecular profiling within the MASTER (Molecularly Aided Stratification for Tumor Eradication Research) precision oncology program revealed a somatic BRAF V600E mutation and a germline PALB2 stop-gain mutation. Therapy was therefore switched to BRAF/MEK inhibition, resulting in almost complete remission and disease control for 12 mo and a remarkable improvement in the patient's general condition. These results indicate that BRAF alterations are a valid therapeutic target in PAC that should be routinely assessed in this patient population.

  Study EGAS00001004282

• H3Africa - Genomic and Environmental Risk Factors for Cardiometabolic Disease in Africans

  The long-term vision of the AWI-Gen Collaborative Centre (CC) is to build sustainable capacity in Africa for research that leads to an understanding of the interplay between genetic, epigenetic and environmental risk factors for obesity and related cardiometabolic diseases (CMD) in sub-Saharan Africa. The CC will be consolidated under the auspices of the University of the Witwatersrand (Wits) and the International Network for the Demographic Evaluation of Populations and Their Health in Developing Countries (INDEPTH). It will capitalize on the unique strengths of existing longitudinal cohorts, including the urban Soweto and rural Agincourt studies in South Africa (Wits based), and the well established INDEPTH demographic health and surveillance centers in Kenya, Ghana, Burkina Faso and South Africa. The centers offer established infrastructure, trained fieldworkers, long-standing community engagement, and detailed longitudinal phenotypic data, focusing on obesity and cardiometabolic health. Key strengths are harmonized phenotyping across sites, building on strong existing cohorts, and representation of the geographic and social variability of African populations. We aim to: 1. Build sustainable infrastructure (biobanks and laboratories) and capabilities (well characterized population cohorts, genotyping and bioinformatics) for genomic research on the African continent; 2. Understand the genomic architecture of sub-Saharan populations from west, east and south Africa to guide genomic studies (genome sequencing and high throughput SNP and CNV arrays using unrelated individuals and family trios to improve the accuracy of haplotype analyses) and; 3. Investigate the independent and synergistic genomic contributions to body fat distribution (BMI, hip/waist circumference, subcutaneous and visceral fat) in these populations considering the relevant environmental and social contexts (rural/urban communities, quickly transitioning obesity prevalence, differential HIV, TB, and malaria infection histories). We will investigate the effect of obesity and fat distribution on the risk for CMD in the longitudinal cohorts.

  Study EGAS00001002482

• Characterization of genetic intratumor heterogeneity in colorectal cancer and matching patient-derived spheroid cultures.

  Patient-derived in vitro cultures of colorectal cancer (CRC) may help guide treatment strategies prior to patient treatment. However, most previous studies have been performed on a single biopsy per tumor. The purpose of this study was to analyze multiple spatially distinct biopsies from CRCs and see how well intratumor heterogeneity (ITH) was recapitulated in matching patient-derived spheroids. Three to five biopsies were collected from six CRC tumors. Each biopsy was split in two; one half was used for spheroid culturing, the other half was used for direct DNA and RNA purification. For two of the patients, lymph node metastases were analyzed. Somatic mutations were called from whole exome sequencing data. Each tumor contained multiple mutations shared across all biopsies and spheroids, including major CRC drivers such as APC, KRAS, and TP53. At the same time, all tumors exhibited ITH on both mutation and copy number level. The concordance between biopsies and spheroids ranged between 40-70% for coding mutations. For three of the patients the biopsy and spheroid from matching areas clustered together, meaning that the spheroid resembled the area of origin more than the other areas. However, all biopsies and spheroids contained private mutations. Thereby, multiple cultures from spatially distinct sites of the tumor increase the insight into the genetic profile of the entire tumor. RNA sequencing based molecular subtyping was stable and seemed independent of genetic ITH. In conclusion, all examined CRC tumors contained genetic ITH on mutation and copy number level. Spheroid cultures partly reflected this ITH, meaning that multiple cultures from distinct sites of the tumor improved the representation of the different genetic subclones in the primary tumor. This should be taken in to account when establishing patient-derived models for drug screening.

  Study EGAS00001002684

• Genetic characterization patients affected by Cancer of Unknown Primary

  The genetic changes sustaining the development of human Cancers of Unknown Primary (CUP) remain elusive. Here we report the genomic profiling of 14 rigorously selected CUP samples. Although no specific recurring mutation in known driver genes was found, a comparison of the mutational landscape of CUPs with that of most other human tumor types revealed a consistent change in diverse genes belonging to the axon guidance KEGG pathway.

  Study EGAS00001006621

• Genomic landscape of IG-MYC positive Burkitt lymphoma with precursor B-cell immunophenotype.

  As part of the ICGC, the ICGC MMML-Seq project performed whole genome sequencing of a rare Burkitt lymphoma subtype with precursor B-cell immunophenotype. Analysis were performed in concordance with the guidelines of the ICGC.

  Study EGAS00001002968

• Characterization_of_individual_foci_of_multicentric_multifocal_breast_cancer_using_targeted_next_generation_sequencing

  Multifocality or multicentricity in breast cancer may be defined as the presence of two or more tumor foci within a single quadrant of the breast or within different quadrants of the same breast, respectively. This original classification of the breast cancer as multicentric or multifocal was based on the assumption that cancers arising in the same quadrant were more likely to arise from the same ductal structures than those occurring in separate areas of the breast. The problem with these definitions is that the “quadrants” of the breast are arbitrary external designations, as no internal boundaries do exist. This project will therefore focus both on synchronous multifocal and multicentric tumors. The incidence of multifocal and multicentric breast cancers was reported to be between 13 and 75% depending on the definition used, the extent of the pathologic sampling of the breast and whether in situ disease is considered evidence of multicentricity (1). Although this incidence is variable, those figures show that it is a frequent phenomenon. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic management of the cancer. Multifocality or multicentricity has been associated with a number of more aggressive features including an increased rate of regional lymph node metastases and adverse patient outcome when compared with unifocal tumors (2-3), and a possible increased risk of local recurrence following breast conserving surgery (4). For the moment, the literature is divided on whether there is a corresponding impact on survival outcomes. Today, the current convention to stage and to treat multifocal and multicentric tumors is the classical tumor-node-metastasis (TNM) staging guidelines with which tumor size is assessed by the largest tumor focus without taking other foci of disease into consideration. If some papers, as the recent one from Lynch and colleagues, support the current staging convention (3), others, however, as Boyages et al. suggested that aggregate size and not the size of the largest lesion should be considered in order to refine the prognostic assessment of those tumors (5). On the top of that, the question whether multifocal/multicentric carcinomas are due to the spread of a single carcinoma throughout the breast or is due to multiple carcinomas arising simultaneously has been a matter of debate. Some studies suggested that multifocal breast cancer may result from either intramammary spread from a single primary tumor or multiple synchronous primary tumors; whereas others suggest that multiple breast carcinomas always arise from the same clone (6-8). Recently, Pietri and colleagues analyzed the biological characterization of a series of 113 multifocal/multicentric breast cancers (8) which were diagnosed over a 5-year period. The expression of estrogen (ER) and progesterone (PgR) receptors, Ki-67 proliferative index, expression of HER2 and tumor grading were prospectively determined in each tumor focus, and mismatches among foci were recorded. Mismatches in ER status were present in 5 (4.4%) cases and PgR in 18 (15.9%) cases. Mismatches in tumor grading were present in 21 cases (18.6%), proliferative index (Ki-67) in 17 (15%) cases and HER2 status in 11 (9.7%) cases. Interestingly, this heterogeneity among foci has led to 14 (12.4%) patients receiving different adjuvant treatments compared with what would have been indicated if we had only taken into account the biologic status of the primary tumor. This study therefore showed that differences in biological characteristics of multifocal/multicentric lesions play a crucial role in the adjuvant treatment decision making process. In this study, we will concentrate on a larger series of patients with multifocal invasive ductal breast cancer lesions. We aim at: 1. Evaluating the incidence of multifocality according to the different breast cancer molecular subtypes (ER-/HER2-, HER2+, ER+/HER2-). 2. Evaluating the incidence of multifocality in patients with hereditary breast cancer disease (presence of germline BRCA1 or BRCA2 mutations). Moreover, we would like to investigate if multifocal lesions with BRCA1 or BRCA2 mutations exhibit a characteristic combination of substitution mutation signatures and a distinctive profile of deletions as demonstrated recently by Nik-Zainal and colleagues (9). 3. Correlating multifocality with clinical information in order to define its influence on patients’ survival (DFS and OS). 4. Carrying high coverage targeted gene sequencing of driver cancer genes and genes whose mutation is of therapeutic importance in order to compare clinically-relevant genetic differences between several multifocal breast cancer lesions. 5. Evaluating the impact of the distance between the different lesions on the clinical outcome but also on the genetic differences. 6. Comparing gene expression patterns between several multifocal breast cancer lesions and correlate them with the results of the targeted genes screen. 7. Characterizing the genomic and transcriptomic status of cancer related genes in metastatic lesions (local recurrence, positive lymph node or distant metastatic sites) from the same multifocal invasive ductal breast cancer patients in order to evaluate the consequence of genomic and transcriptomic heterogeneity of multifocal lesions on metastatic lesions. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic choice. This project has the potential to identify genetic/transcriptomic differences existing between several lesions constituting multifocal breast cancers, which in the routine clinical practice are usually considered to be homogeneous among them. We foresee validating significant results in a larger series of patients and this, in turn, could have a remarkable impact on the treatment and clinical management of multifocal breast cancers. Indeed, we hope to provide some evidence whether or not each focus matters in multifocal and multicentric breast cancer to define the adequate therapeutic approach, especially in the context of targeted therapies. The work to be done at Sanger will be target gene screen pooling of 1400 samples.

  Study EGAS00001000407

• RNA-seq of Glioblastoma stem cells

  Chromatin accessibility discriminates stem from mature cell populations, enabling the identification of primitive stem-like cells in primary tumors, such as Glioblastoma (GBM) where self-renewing cells driving cancer progression and recurrence are prime targets for therapeutic intervention. We show, using single-cell chromatin accessibility, that primary GBMs harbor a heterogeneous self-renewing population whose diversity is captured in patient-derived glioblastoma stem cells (GSCs). In depth characterization of chromatin accessibility in GSCs identifies three GSC states: Reactive, Constructive, and Invasive, each governed by uniquely essential transcription factors and present within GBMs in varying proportions. Orthotopic xenografts reveal that GSC states associate with survival, and identify an invasive GSC signature predictive of low patient survival. Our chromatin-driven characterization of GSC states improves prognostic precision and identifies dependencies to guide combination therapies.

  Study EGAS00001003070

• Molecular Signature of Saudi Thyroid Cancer Using whole exome sequencing

  In Saudi Arabia, thyroid cancer ranked second only to breast cancer among females, eleventh among males and this increased incidence is prevalent in other Gulf Council Countries also. Differentiated thyroid cancer, which includes papillary thyroid cancer (PTC) and follicular subtypes, accounts for 90% of all thyroid malignancies. Currently, there are no clinical or molecular diagnostic tools to predict recurrence and aggressiveness of a subset of PTC. With the goal of better understanding the pathobiology of thyroid carcinogenesis we will use Whole Exome Sequencing to decipher the molecular and genetic signature of Saudi PTC based on International Cancer Genome Consortium (ICGC) Guidelines. The study will provide a better understanding of PTC and should have important clinical implications in the development of new and better strategies for targeted therapeutic intervention for the treatment of Saudi Arabian PTC

  Study EGAS00001000680

• Anaplastic_Meningioma_WGS_X10

  Anaplastic meningiomas are a rare, malignant variant of meningioma. At present there is no effective treatment for this cancer. The aim of the study is to identify somatic mutations in anaplastic meningiomas. We plan to sequence a set of 500 known cancer genes in 50 anaplastic meningioma and corresponding peripheral blood DNA samples. Bioinformatics will be used to analyse the results to assess the probability of these mutations being causal and so likely of critical importance for the tumour growth. Identification of these mutations will guide selection of appropriate compounds to effectively treat the disease.

  Study EGAS00001000859

• Study on the consequences of prenatal famine exposure on DNA methylation.

  The potential of the epigenome to undergo environmentally-induced changes during early development is central to its postulated role in human disease. Here, we report a genome-scale view of DNA methylation differences after early gestational malnutrition that was caused by the Dutch Hunger Winter, a severe famine at the end of World War II. We adopted an annotation guided analysis of reduced-representation bisulfite sequencing data generated in 24 middle-aged individuals who had been exposed to famine in utero and 24 unexposed sibling controls. We observed differential DNA methylation primarily at genomic regions with regulatory potential, including enhancers active during early development. In-depth annotation of 181 prenatally-induced differentially methylated regions (P-DMRs) showed that they were predominantly located in gene bodies and co-occurred with histone marks denoting an active state. In line with the early gestational timing of the exposure, the P-DMRs mapped to genes that were enriched for differential expression patterns during blastocyst development and early organogenesis. Validation and further explorative analyses of 6 P-DMRs mapping to SMAD7, CDH23, INSR, RFTN1, CPT1A and KLF13 highlighted the critical role of gestational timing, indicated that differential methylation extended along pathways involved in growth, development and metabolism, and suggested associations with birth weight and serum LDL cholesterol in adulthood and confirmed an enhancer function for the INSR and CPT1A P-DMRs. Our results point toward a link between prenatal malnutrition and epigenetic modulation of growth and lipid metabolism that may underlie the adverse metabolic phenotype of exposed individuals in later life.

  Study EGAS00001000668

• 65 prostate cancer cases WGS and transcriptome sequencing project

  We obtained whole-genome and transcriptome sequencing of tumor-benign pairs from 65 Asian prostate cancer (PCa) patients. Taken together with the TCGA PCa cohort, our integration analysis provides the first comprehensive mutational landscape of PCas across major ethnics worldwide and reveals potential novel role of frequent altered chromatin remodeler genes in PCas without androgen receptor (AR) alteration and complex rearrangements derived from Chromoplexy. In addition, we identified 5 putative tumor suppressor genes (TSGs) chains including one on chromosome 13q with novel findings of PCDH9 (deletions in 15/65 tumors) which was implicated in aggressive progression of prostate cancer. Finally, the integrative pathway and co-expression network analysis followed by the functional study indicated the frequent altered genes, particularly focal amplifications of PLXNA1 (11/65), in semaphoring signaling of axon guidance pathway may interact with PI3K/AKT and AR signaling and also contribute to the aggressiveness and progression of prostate cancer.

  Study EGAS00001000888