88 results for "华为昇腾+市场份额+2023"

in 11.76 milliseconds.

• Perceptions, Prevalence, and Patterns of Cannabis Use among Cancer Patients in NCI-Designated Cancer Centers

  This study aimed to better understand the evolving landscape of cannabis use among patients undergoing cancer treatment across diverse geographic regions. It sought to characterize patterns of use, patient perceptions, and contextual influences such as legal status and provider engagement that affect cannabis use. Given the shifting legal environment, this study addresses a critical gap in the literature by providing data on how cancer patients integrate cannabis into their care. The available delivery methods of cannabis have also undergone dramatic changes and now include edibles, oils, tinctures, topicals, and inhaled forms. State-based policy changes are rapidly changing. Yet research on cannabis use by cancer patients across a variety of geographic settings remains limited. The extent of cannabis use, the perceived and real benefits and risks of use, potential interactions with cancer treatment and other medications, and impact on comorbid conditions are uncertain. Clinicians should be aware of the extent of use in order to assess potential drug-drug interactions, side effects, and contraindications; hence, an understanding of how cancer patients and clinicians engage in discussions about cannabis use is essential. Twelve NCI-designated cancer centers were awarded supplemental funding to conduct surveys assessing cannabis use among recently diagnosed cancer patients. Selected sites were in 8 states with varied legal status for medical and recreational cannabis use at the time of the survey. The 12 cancer centers independently received approval from their institutional review boards (IRB) and collected data from September 2021 to August 2023. Eligible participants were cancer patients or survivors who resided in their respective cancer center's catchment area. Cancer centers were responsible for sampling patients within their catchment area with the goal of 1,000 completed surveys. Ten out of 12 cancer centers drew probability samples of patients from patient lists defining their catchment area with some stratifying the sample in various ways including by cancer type, by sex, by race/ethnicity or by a combination of demographic variables.

  Study phs004046

• A prospective study identifies MisMatch Repair genes as candidate predisposing genes for uveal melanoma.

  Objective: The aim of this study is to identify new predisposing genes for uveal melanoma (UM), the most common intraocular malignancy in adults. Design: Prospective cohort study from Institut Curie. Participants: 381 unselected patients diagnosed with UM between July 2021 and February 2023 at Institut Curie. Methods: All patients received genetic counseling and consented to extended genetic testing. A panel of 122 genes was analyzed by targeted sequencing on germline DNA from these patients. Main outcomes measures: UM was diagnosed by ophthalmologists at Institut Curie, and a senior pathologist confirmed the diagnosis when tumor or biopsy was available. Classification of the germline genetic variants was performed according to the ACMG guidelines. Results: We identified at least one pathogenic variant (PV) in 79 patients. Among those variants, 20 were found in clinically relevant genes for the patient’s follow-up and genetic counseling. We found a significant enrichment of germline pathogenic variants in Mismatch Repair (MMR) MLH1, MSH2 and MSH6 genes in this UM cohort, suggesting that MMR germline alterations could predispose to UM. From this cohort, one tumor was available from a patient carrying a MLH1 germline mutation. The tumor was characterized by a monosomy 3, in line with a loss of heterozygosity (LOH) of MLH1, located on chromosome 3. Loss of expression of MLH1 and PMS2 was observed by immunohistochemistry, and MMR mutational signatures SBS6, ID1 and ID2 were identified from the whole genome sequencing of the tumor. These data suggest that MLH1 is implicated in the oncogenesis of this UM. Conclusions: This study is the largest prospective constitutional study performed on UM patients, and the first demonstrating that MMR germline alterations are significantly enriched among these patients. Further analyses will be needed to estimate the risk of developing UM for patients with Lynch syndrome

  Study EGAS50000000914

• CDK4/6 inhibition in advanced chordoma: final results of the NCT PMO-1601

  Background. Chordoma is a rare bone tumor with no approved systemic therapy. Inactivation of the tumor suppressor p16 (encoded by CDKN2A) leads to aberrant cyclin D-CDK4/6-RB pathway activity, which can be inhibited by palbociclib in chordoma cell lines. Patients and Methods. We conducted a phase II single-arm, open-labeled trial on palbociclib in adult patients with advanced chordomas with p16 loss (by immunohistochemistry) or CDKN2A loss (by genomic analysis) and CDK4/6 and RB1 presence (by immunohistochemistry or RNA-Sequencing). Patients received 125mg palbociclib once daily for 21 days in a 28-day cycle. The study used a Simon optimal 2-stage design. The primary endpoint was disease control rate after six cycles. Response was evaluated according to Response Evaluation Criteria in Solid Tumors (RECIST) version 1.1. Secondary endpoints included progression-free survival, overall survival, and biomarker analysis. The study was considered positive if 25% of patients reached the primary endpoint. Results. Between December 2017 and April 2023, 28 patients (median age 60 years, range 31-84) were enrolled. After a median follow-up of 28 months, the disease control rate was 39%, with 11 out of 28 patients achieving stable disease. No objective responses were observed. The median progression-free survival was 5.6 months, and the median overall survival was 24.6 months. Treatment was well tolerated without new safety signals. CDKN2A deletions were the most common genomic alterations underlying p16 loss and were accompanied by MTAP co-deletion. There was no correlation between responder phenotypes by immunohistochemistry and outcome. RNA-based analysis showed heterogeneous pathways deregulation at study entry suggesting underlying primary resistance mechanisms Conclusion. This trial met its primary endpoint with a 39% disease control rate, though antitumor activity was modest. Molecularly tailored combination therapies should be considered to improve efficacy. (ClinicalTrials.gov number, NCT03110744).

  Study EGAS00001007985

• Synthetic - FEGA Sweden Heilsa synthetic dataset December 2023

  Synthetic - This submission contains a subset of a synthetic dataset derived from the project Heilsa Tryggvedottir - a Nordic collaboration on sharing sensitive human data. Heilsa Tryggvedottir is funded by the Nordic e-Infrastructure Collaboration (NeIC), the ELIXIR nodes of Finland, Norway, and Sweden, Computerome in Denmark, and the Estonian Scientific Computing Infrastructure (ETAIS). In the synthetic data creation process, it was attempted to strike a fine balance between the usability of the datasets (e.g. technical FEGA development, testing, user training, and basic bioinformatics) and compliance with GDPR. File names and file content (e.g. headers in fastq) are anonymized. Moreover, the X, Y, and mitochondrial sequences have been discarded from the original data since these data can be used for maternal, paternal, or ethnic origin tracing. The dataset does not follow natural haplotype distribution (inherent to imputation panels). The only inputs derived from real sequence data are variant distribution density per chromosome and learning sequencing error models. The synthetic dataset consists of two fastq files, a cram file, a vcf file, and two index files.

  Study EGAS50000000086

• MutWP5: CRUK Mutographs of Cancer: Cancer Mastectomy (WG)(Novaseq)

  Sequencing of LCM-derived microbiopsies from 40 women who underwent mastecomies due to breast cancer. LCM and sequencing will be conducted on both normal, unaffected breast, and, where possible, tumour tissue. Goal to assess the mutational burden, spectrum, and clonal dynamics within the tissue, and compare findings between the normal and associated cancer tissues. Whole-genome sequencing will be conducted on samples identified as promising from the initial targeted data. Results from this poriton of the study will be compared to women who had cosmetic breast reduction surgeries and those who are BRCA carriers. . This dataset contains all the data available for this study on 2023-03-08.

  Dataset EGAD00001010114

• Multiomic Landscape of Multiple Myeloma Precursor and Relapsed Disease

  Multiple myeloma (MM) is a treatable, though incurable, plasma cell malignancy. The molecular mechanisms driving disease onset and the emergence of drug resistance remain elusive. To better characterize the mutational, transcriptional, and epigenetic alterations that accompany MM disease evolution, we accessed molecular data from MM patients treated at Moffitt Cancer Center, with bone marrow biopsies collected between 2011 and 2023.We performed scMultiome (single-cell, paired RNA/ATAC-Seq, 10x Genomics) on 18 CD138+-selected bone marrow aspirate samples, including: 2 healthy donors, 3 patients with monoclonal gammopathy of undetermined significance (MGUS), 4 with smoldering myeloma (SMM), 3 with newly diagnosed MM (NDMM), 1 with early relapse MM (ERMM, 1 to 3 lines of therapy), and 5 with late relapse MM (LRMM, 4 or more lines of therapy). Our dataset includes a sequential sample: a patient with a premalignant condition ("scMultiome_SMM_4") that progressed to active myeloma ("scMultiome_NDMM_3"). These data allow for the assessment of transcriptional and epigenetic dysregulation at the cellular level. Our findings illustrate the dynamic epigenetic and transcriptional landscapes that accompany MM disease progression.We also conducted CUT&Tag analysis on 4 NDMM and 4 LRMM samples to map histone modifications, specifically H3K27ac, to investigate their role in transcriptional reprogramming observed in advanced stages of MM. This analysis revealed sample heterogeneity in terms of super-enhancer-regulated genes associated with active transcription.This cohort also includes samples from the clinical trial NCT04151667, “Daratumumab-Based Response-Adaptive Therapy for Older Adults With Newly Diagnosed Multiple Myeloma.” We performed scRNAseq (single-cell RNA sequencing, 10x Genomics) on 30 CD138+-selected bone marrow aspirate samples and 31 pre-sort samples featuring bone marrow mononuclear cells of various cell types from 5 healthy donors and 11 patients with newly diagnosed MM (NDMM). Our dataset includes sequential samples for all 11 NDMM patients, both prior to induction therapy (denoted by ‘a') with Daratumumab and Dexamethasone, and at cycle 2 day 22 (C2D22, i.e., 60 days after induction therapy start, denoted by ‘b'). For three NDMM patients, we also have samples at relapse (denoted by ‘c'). These data allow for the assessment of transcriptional dysregulation at the single-cell level in both the tumor and immune-tumor microenvironment, associated with Daratumumab treatment in NDMM patients.In addition to the molecular data, demographic, and phenotypic information for all samples is provided.

  Study phs003892

• Pathogenesis and Immunity in Endemic Burkitt Lymphoma

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

  Study phs001282

• Sickle Cell Disease Natural History Data Resource (SCD NHDR)

  Data Access NOTE Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. BackgroundThe NHLBI initiated the Sickle Cell Disease Natural History Data Resource (SCD NHDR) to leverage existing SCD studies to build a data resource to provide phenotypic data on contemporaneous control cohorts for gene therapy trials and other studies. The potential uses of the NHDR are broad, including providing matched controls for clinical trials, observing a cohort of untreated patients as part of a natural history study, or conducting comparative effectiveness research on a subpopulation with selected co-morbidities or drug treatment profiles. The SCD NHDR includes two multi-center SCD longitudinal cohort studies with extensive annual clinical data and patient surveys, the Sickle Cell Disease Implementation Consortium (SCDIC-I and SCDIC-II) and the Globin Research Network for Data and Discovery (GRNDaD). The SCDIC-I, initiated in 2017 and concluded in June 2022, enrolled over 2400 patients with SCD from 8 US treatment centers. The SCDIC-II reconsented 1220 of the SCDIC-I patients as well as enrolling an additional 450 new patients from the same 8 centers between September 2022 and October 2023, for a total of 1670 in SCDIC-II. Only two of the many GRNDaD centers are submitting data to the SCD NHDR for deposit into BDC (approximately 122 patients). Data submissions from the SCD NHDR to BDC will be annually starting in early 2024. Description of the Study Data All data obtained for the SCD NHDR are considered common data elements (CDEs) important for studies of SCD. These CDEs were identified from several workgroups of SCD experts convened under the NHLBI's Cure-SC Initiative (https://curesickle.org/cde-catalog). The following types of data elements were abstracted from the medical record – variables that describe the SCD diagnosis, SCD co-morbidities and other clinical complications, elements from the physical examination, medications and transfusions, insurance type, laboratory measurements, healthcare utilization, history of SCD-related procedures, and measurements from cardiac procedures. The following types of data were self-reported on the patient survey – demographics, diagnosis information, pain experience, social and mental health information, other patient reported outcome domains (e.g., sleep, fatigue), and alcohol and smoking history. Standard PRO measures were used from ASCQ-Me, PROMIS and Neuro-QoL. Patient surveys were completed approximately annually. Under SCDIC-I, two medical record abstractions and labs were reported at enrollment and approximately 3 years later. Under SCDIC-II and GRNDaD, all data are collected annually. Patients may refuse to complete the survey.

  Study phs003529

• Programmatic submission based on XML

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

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

• Drug development for pediatric cancers: the importance of patient' s genomic data re-use

  Cancer in children is uncommon and the overall prognosis for most pediatric cancers is good. However, while the combined survival rates have improved over the last decades, certain childhood malignancies, such as high-grade gliomas or metastatic sarcomas, still remain incurable in most patients. New strategies for targeting those devastating diseases are imperative, and patient genomic data can become a key asset in the process [1]. The Pediatric Cancer Genome Project’s datasets At EGA, we store over 500 datasets with sequencing data from pediatric cancer patients. A remarkable case is the datasets belonging to the Pediatric Cancer Genome Project (PCGP) from St. Jude Children’s Research Hospital–Washington University (Table 1 - EGAS list). PCGP is an ambitious effort to identify the mutations that drive childhood cancer and find new cures. Those datasets include 600 patients with complete tumor and normal genomes from 15 different tumor types. PCGP datasets have been an important resource for various studies that pooled genomic data from different public and in-house datasets to perform extensive genomic characterizations and publish comprehensive pan-cancer pediatric studies [2],[3]. Other interesting pediatric cancer datasets are from the Pediatric Brain Tumor Consortium, Sickkids or ICGC PedBrain project. How data reuse impacts drug development for pediatric cancers Recently, in October 2024, Nature Communications published a work led by the University of Michigan where authors used data from EGA (PCGP) check the table below as part of their strategy to pursue the identification of new tumor vulnerabilities susceptible to becoming novel therapeutic targets in diffuse midline glioma. Diffuse midline gliomas (DMG) are treatment-resistant and uniformly fatal pediatric brain tumors. The prognosis of this brainstem tumor is dismal with a median overall survival of 9–12 months from diagnosis. In this study, the authors first developed a lab model of the disease and reanalyzed data from the EGA to identify genes potentially linked to tumor severity. This approach revealed involvement of specific metabolic pathways, suggesting new possibilities for therapeutic intervention. In mice, the study shows that the use of statins can improve survival. For a brief overview of the underlying science, diffuse midline gliomas present intratumor heterogeneity with subpopulations of less-differentiated oligodendrocyte precursors and more differentiated astrocytes. Authors established in vitro models to recapitulate both phenotypes and identify metabolic programs in both subpopulations. To determine the clinical relevance, the authors re-used gene expression data from 76 DMG patients identifying a gene signature predicting decreased overall survival. After extensive metabolic characterization of subpopulations, authors defined strategies to target specific metabolic vulnerabilities. Pre-clinical experiments in mice using OXPHOS inhibitors and statins showed a reduction in tumor burden and increased overall survival [4]. In this scenario, the re-use of high-quality patient’s sequencing data appeared as an advantageous strategy to support the clinical relevance of in-vitro and pre-clinical findings. On the other hand, in rare conditions such as childhood cancer, the availability of public datasets and the possibility of pooling data from different sources can be the only way to obtain impactful results that lead to improvements for patients. References Davidoff, A. M. Pediatric Oncology. Seminars in pediatric surgery 19, 225–233 (2010). Gröbner, S. N. et al. The landscape of genomic alterations across childhood cancers. Nature 555, 321–327 (2018). Venu Thatikonda et al. Comprehensive analysis of mutational signatures reveals distinct patterns and molecular processes across 27 pediatric cancers. Nature Cancer 4, 276–289 (2023). Mbah, N. E. et al. Therapeutic targeting of differentiation-state dependent metabolic vulnerabilities in diffuse midline glioma. Nature Communications 15, (2024). Datasets and Studies ID Title Access Policy Year EGAD00001000134 Driver mutations in histone H3.3 and chromatin remodelling genes in paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAS0000100192 Somatic Histone H3 Mutations in Diffuse Intrinsic Pontine Gliomas and Non-Brainstem Paediatric Glioblastomas St. Jude Children's Research Hospital - Washington University Pediatric Cancer Genome Project 2017 EGAS00001000575 Whole genome sequencing and whole exome sequencing of DIPG tumors and matched normal tissue The hospital for sick children ("SickKids") 2016 EGAD00001000792 Exome sequencing reads of paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAD00001002006 Whole genome sequencing of paediatric glioblastoma in the ICGC PedBrain project ICGC PedBrain project 2016

  Blog drug-development-for-pediatric-cancers

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

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

  Blog new-dac-portal-v2

• 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 reach out to us here. 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

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

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

  Blog fega-and-gdi