3955 results for "*geneti*"

in 32.21 milliseconds.

• Phosphoproteomics adds value to treatment recommendations in molecular tumor boards

  Precision oncology approaches employing genomics-guided targeted therapies for individual patients have provided significant survival benefits in several cancer types. However, low response rates in most solid malignancies, many patients without actionable genomic lesions, and increasing evidence that non-genomic mechanisms may play an important role in tumors indicate that genomics alone is often insufficient to inform and guide the clinical care of patients. Here, we show for the first time that comprehensive (phospho)proteome profiling is feasible and informative in a real-world prospective precision oncology setting. We developed a novel tumor pathway activity (TUPAC) scoring methodology that provides a holistic perspective on dysregulated receptor tyrosine kinase (RTK) signaling in individual patients. Based on 919 tumor tissue profiles of patients enrolled in the national NCT/DKTK MASTER study and the INFORM registry trial, we illustrate how TUPAC scoring can be used to uncover individual tumor biology in rare cancers and demonstrate that TUPAC methodology identifies EGFR-driven sarcomas despite the absence of genetic EGFR alterations. Overall, our work demonstrates the utility of the additional phosphoproteome data layer to enhance therapeutic recommendations in molecular tumor boards.

  Study EGAS00001007891

• The University of Hong Kong Intestinal Metaplasia Organoids Study

  Background: Gastric intestinal metaplasia (IM) is a pre-cancerous stage spanning a morphological spectrum that is poorly represented by human cell line models. Objective: We aim to establish and characterize human IM cell models to better understand IM progression along the cancer spectrum. Design: A large human gastric IM organoid (IMO) cohort (n=28), their clonal derivatives and normal gastric organoids (n=42) for comparison were established. Comprehensive multi-omics profiling and functional characterization were performed. Results: Single-cell transcriptomes revealed IMO cells spanning a spectrum from hybrid gastric/intestinal to advanced intestinal differentiation. Their lineage trajectories connected different cycling and quiescent stem and progenitors, highlighting differences in gastric to IM transition and the potential origin of IM from STMN1 cycling isthmus stem cells. Hybrid IMOs showed impaired differentiation potential, high lineage plasticity beyond gastric or intestinal fates, and reactivation of a fetal gene program. Cell populations in gastric IM and cancer tissues were highly similar to those derived from IMOs and exhibited a fetal signature. Genomically, IMOs showed elevated mutation burden, frequent chromosome 20 gain, and epigenetic de-regulation of many intestinal and gastric genes. Functionally, IMOs were FGF10 independent and showed downregulated FGFR2. Several IMOs exhibited a cell-matrix adhesion independent (CMi) subpopulation that displayed chromosome 20 gain but lacked key cancer driver mutations, potentially representing the earliest neoplastic precursor of IM-induced gastric cancer. Conclusions: Overall, our IM organoid biobank captured the heterogeneous nature of IM, revealing mechanistic insights on IM pathogenesis and progression, offering an ideal platform for studying early gastric neoplastic transformation and chemoprevention.

  Study EGAS00001007899

• Transcriptomics-driven classification of ALAL

  Acute leukemia of ambiguous lineage (ALAL) is a rare, poor-prognosis subtype of acute leukemia that cannot be assigned to a single hematopoietic lineage. Although ALAL patients are typically treated with acute myeloid leukemia (AML) or acute lymphoblastic leukemia (ALL) regimens, optimal treatment choice is hindered by their lineage ambiguity. Therefore, we investigated the added value of transcriptomics for improving lineage assignment, currently based mainly on surface markers. First, we used an in-house pipeline to comprehensively detect genetic lesions in RNA-sequencing data (n=23) with a sensitivity >90%, as confirmed by targeted DNA sequencing. Second, we compared ALAL gene expression profiles (GEPs) with representative AML (n=145), B-ALL (n=223) and T-ALL (n=85) cases. In a principal component analysis, ALALs did not form a separate group, but clustered with AML, B-ALL or T-ALL. Accordingly, a machine learning classifier trained with GEPs of acute leukemias segregated 20/23 ALALs into myeloid-, B- or T-lymphoid leukemia. These 20 cases harbored genetic abnormalities consistent with the classifier-assigned leukemia. Furthermore, ALAL GEPs were deconvoluted with single-cell transcriptional profiles of normal hematopoietic cells using CIBERSORTx, revealing enrichment for signatures of lineages corresponding to the leukemic type predicted by our algorithm. The classifier was validated on an external ALAL cohort (n=24), assigning 75% of the patients to a lineage matching their immunophenotypic and methylation profiles. In conclusion, integrative analysis of RNA-sequencing data can accurately classify most ALAL cases. The pipeline and classifier developed in our study are valuable tools to improve ALAL diagnosis and guide therapeutic decisions.

  Study EGAS00001007967

• Single-cell atlas of > 1.5 million PBMC with multi-layer omics data in Japanese

  Osaka Atlas of Immune Cells (OASIS) is multi-omics immune cell atlas from 235 Japanese including COVID-19 patients and healthy subjects. The 5’ single-cell transcriptomics data profiled over 1,500,000 peripheral blood mononuclear cells (PBMCs). OASIS links these single-cell transcriptomics data with host genetics, plasma proteomics, and metagenomics data.

  Study EGAS00001008016

• Patient-derived tumoroids from CIC::DUX4 rearranged sarcoma identify MCL1 as a therapeutic target

  High-risk sarcomas, such as metastasized and relapsed Ewing and CIC-rearranged sarcomas, currently lack effective curative systemic treatment options. Precision medicine approaches offer hope and among them ex vivo drug response profiling of patient-derived tumor cells emerges as a promising novel tool to identify effective drugs for individual patients. Here, we established ex vivo culture conditions to propagate Ewing and CIC::DUX4-sarcomas as tumoroids in a co-clinical manner. These models retained their original molecular and functional characteristics, including recurrent ARID1A mutations, and serve as tumor avatars suitable for large-scale drug testing. Indeed, screening a large drug library on a small living biobank of such tumors not only revealed distinct response differences between the two entities, but also identified an exceptional dependency of CIC::DUX4-sarcoma cells on MCL1. Mechanistically. MCL1 was identified as a direct target gene of the CIC::DUX4 fusion protein. Genetic and pharmacological inhibition of MCL1 induced rapid apoptosis in CIC::DUX4-sarcoma cells and inhibited tumor growth in a xenograft model. Thus, MCL1 represents a potential novel therapeutic target for CIC::DUX4-sarcoma. Overall, our study highlights the feasibility of co-clinical drug response profiling for individual sarcoma cases and suggests that prospective tests, to evaluate its clinical benefit are highly warranted.

  Study EGAS00001008039

• Genetic origins of the Kiritimati population from central-eastern Micronesia

  The migration of Austronesian-speaking populations through Oceania has intrigued researchers for decades. The Kiribati islands, situated along the boundaries of Micronesia and Polynesia, provide a crucial link in this migration. We analyzed the genome-wide data of the Kiritimati population of Kiribati to uncover their genetic origins and connections with other Oceanian groups. Our study reveals that the Kiritimati population primarily exhibits Remote Oceanian-related ancestry associated with ancient Lapita and present-day Polynesian populations. In addition, our identity-by-descent analysis identifies populations from Philippines as their closest relatives in Island Southeast Asia. The genetic links between Kiritimati, ancient Lapita, and modern Polynesians underscore the shared ancestry and continuous gene flow across these regions. This genetic continuity and ongoing links are supported by linguistic and cultural evidence, illustrating a complex history of migration and admixture in Oceania.

  Study EGAS00001008060

• Epi2Diag

  Genomic DNA was extracted from whole blood and bisulfite converted using the EZ DNA Methylation Lightning Kit (Zymo research). DNA methylation profile was then derived using Illumina’s Infinium EPIC array v2.0. in accordance with the manufacturer’s protocol at the ASGARD-Rouen genomic platform (Inserm U1245, University of Rouen and Rouen University Hospital, Rouen France) on an Illumina NextSeq550 scanner.

  Study EGAS00001008070

• Single cell TCRseq data fromTIL and non-TIL expanded TRACERx samples in the manuscript Bulk TCRseq from TRACERx samples from 'Subclonal immune evasion in non-small cell lung cancer'

  Immune checkpoint blockade in non-small cell lung cancer (NSCLC) rarely leads to complete tumour remission, suggesting that tumours harbour subpopulations of cancer cells that can escape immune predation. However, while tumours consist of multiple genetically distinct clones, the extent to which separate tumour subclones differ intrinsically in their functional capacity for immune evasion remains largely unexplored. This has been challenging to address due to an inability to isolate and propagate individual tumour subclones from human cancers. Here, we leverage the multi-region TRACERx lung cancer evolution study to generate a patient-derived platform that allows the functional analysis of immune escape at single clone resolution. We generated libraries of >20 separate NSCLC organoid lines per patient by isolating individual (clonal) organoids established from multiple spatially separated tumour regions. Each organoid subline was co-cultured with autologous tumour infiltrating lymphocytes (TIL) to evaluate their capacity to elicit a T cell response. Organoid lines derived from separate tumour regions, or from single clones within individual regions, differ vastly in their capacity to elicit a T cell response, showing the coexistence of intrinsically immune evading (‘cold) and non-evading (‘hot) clones in the same primary tumour. Organoid lines escaping T cell recognition represent genetically and transcriptionally unique subclones with a distinct evolutionary history, showing that evolutionary sculpting of subclonal diversity can have functional consequences for anti-tumour immunity. Notably, the identification of immune-evasive subclones would not have been possible using computational approaches alone, highlighting the unique value of functional co-culture platforms. This patient-derived functional co-culture platform reveals that tumour evolution can give rise to distinct cancer clones with intrinsic differences in immune evasion capacity and provides an approach to prospectively identify, isolate and characterise immune evading subclones from patients with cancer.

  Study EGAS00001008161

• OMKar

  The whole genome karyotype refers to the sequence of large chromosomal segments that make up an individuals genotype. karyotype analysis, which includes descriptions of aneuploidies and other rearrangements is crucial for understanding genetic risk factors, for diagnosis, treatment decisions, and genetic counseling linked to constitutional disorders. The current karyotyping standard is based on microscopic examination of chromosomes, a complex process that requires high expertise and offers Mb scale resolution. Optical Genome Mapping (OGM) technology can identify large DNA lesions in a cost-effective manner. In this paper, we developed OMKar, a method that uses OGM data to create a virtual karyotype. OMKar processes Structural (SV) and Copy Number (CN) Variants as inputs and encodes them into a compact breakpoint graph. It recomputes copy numbers using Integer Linear Programming to maintain CN balance and then identifies constrained Eulerian paths representing entire donor chromosomes. In tests using 38 whole genome simulations of constitutional disorders, OMKar reconstructed the karyotype with 88% precision and 95% recall on SV concordance and 95% Jaccard score on CN concordance. We applied OMKar to 50 prenatal, 41 postnatal, and 63 parental samples from ten different sites. OMKar reconstructed the correct karyotype in 144 out of 154 samples, covering 25 of 25 aneuploidies, 32 of 32 balanced translocations, and 72 of 82 unbalanced variations. Detected constitutional disorders included Cri-du-chat, Wolf-Hirschhorn, Prader-Willi deletions, Down, and Turner syndromes. Importantly, it identified a plausible genetic mechanism for five cases of constitutional disorder that were not detected by other technologies. Together, these results demonstrate the robustness of OMKar for OGM-based karyotyping.

  Study EGAS00001008245

• Peruvian Population Genomics: Unraveling the Genetic Landscape and Admixture Dynamics of Urban Populations

  Genome-wide study of human populations living in Peruvian urban areas

  Study EGAS00001008264

• Genome-wide methylation detection and episignature analysis using PacBio long-read sequencing

  Study EGAS00001008250

• Ultra-long sequencing for contiguous haplotype resolution of the human immunoglobulin heavy chain locus

  Genetic diversity within the human immunoglobulin heavy chain (IGH) locus influences the expressed antibody repertoire and susceptibility to infectious and autoimmune diseases. However, repetitive sequences and complex structural variation pose significant challenges for large-scale characterization. Here, we introduce a method that combines Oxford Nanopore ultra-long sequencing and adaptive sampling with a bioinformatic pipeline to produce haplotype-resolved, annotated IGH assemblies. Notably, our strategy overcomes prior limitations in phasing resolution, enabling single-contig haplotype assemblies that span the entire IGH locus. We applied this method to four individuals and validated the accuracy of the IGH assemblies using Pacific Biosciences HiFi reads, demonstrating near-complete sequence congruence, detecting only indels with a high degree of confidence. Moreover, when applied to the reference material HG002, our pipeline revealed no base differences and a limited number of indels compared with the Telomere-to-Telomere genome benchmark across the IGH region. Importantly, in the four individuals, our approach uncovered 30 novel alleles and previously uncharacterized large structural variants, including a 120 kb duplication spanning IGHE to IGHA1 and an expanded seven-copy IGHV3-23 gene haplotype. These findings underscore the power of our method to resolve the full complexity of the IGH locus and uncover previously unrecognized variants that may affect immune function and disease susceptibility. Thus, our method provides a strong basis for future immunological research and translational applications.

  Study EGAS50000001042

• SweGen: a whole-genome data resource of genetic variability in a cross-section of the Swedish population

  The SweGen project represents a comprehensive map of genetic variation in the Swedish population. This Study contains four datasets where the first one contains whole-genome sequencing data in CRAM-format for 942 individuals from the Swedish Twin Registry, the second one contains genetic variant frequencies in VCF-format for the same individuals, the third one contains whole-genome sequencing data in CRAM-format for 58 individuals from the Northern Sweden Population Health Study and the fourth one contains genetic variant frequencies in VCF-format for the same individuals. The data, serving as a reference dataset, is a valuable and national resource for genetics research and clinical diagnostics and can be used, for instance, to increase understanding of both rare and complex disorders. It also serves as an international resource for larger studies of human population genetics.

  Study EGAS50000000906

• The cellular state space of AML unveils novel NPM1 subtypes with distinct clinical outcomes and immune evasion properties

  Acute myeloid leukemia (AML) is a genetically and cellularly heterogeneous disease. We characterized 120 AMLs using bulk genomic and transcriptomic analyses (WES, MP-WGS, RNA-seq), and single-cell RNA sequencing (scRNA-seq). Our results reveal an extensive cellular heterogeneity that distorts the bulk transcriptomic profiles. Notably, NPM1 mutated AML could be stratified into two novel, clinically relevant classes (NPM1class I and NPM1class II).

  Study EGAS50000001084

• Epigenetic characterization 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 human 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, in line with the higher invasive properties of Invasive state GSCs compared to Reactive and Constructive GSCs as shown by in vitro and in vivo assays. Our chromatin-driven characterization of GSC states improves prognostic precision and identifies dependencies to guide combination therapies.

  Study EGAS50000001804

• MPIMG DAC

  DAC of the Max Planck Institute for Molecular Genetics

  Dac EGAC50000000149

• Long-read Nanopore and Ion Torrent sequencing data for BRCA1/2 variant detection

  This dataset contains long-read sequencing (LRS) data generated using Oxford Nanopore Technologies (ONT) for the analysis of BRCA1 and BRCA2 variants in individuals referred for hereditary breast genetic testing. The study includes samples previously analyzed using Ion Torrent sequencing, enabling comparison between short-read and long-read sequencing approaches.

  Dac EGAC50000000946

• How to use the EGA search box

  Tips on how to search Tip 1: Use simple and clear keywords No matter what you are searching: a study, a dataset or a committee; the search will look recursively in all the fields of all the entities in the database. Thus, there is no need to specify which type of data you are looking for. Try to use single and specific words and avoid long and complex expressions. Try it out: cancer rna-seq instead of cancer studies using RNA-seq. Tip 2: Narrow your results using search operators Search operators give you more control over the results. They manage the way keywords are used to restrict the search. By default, the search engine applies an OR operator when a space is inserted between two words. Include AND (capitalised) between the keywords in your search in order to show only pages containing both terms. Try it out: Search all the studies based on transcriptomic data, including those ones that use RNA sequencing to obtain this data. Tip 3: Do not worry about details The search engine automatically checks for the most common spelling mistakes of given words and suggests the use of the correct version. It also ignores capital letters and most punctuation so none of these mistakes will hamper the accuracy of your search. Besides, when using a combination of words, the search engine will suggest similar combinations with a higher number of results. Tip 4: Use words that are likely to appear within the text Unfortunately, our search engine is not able to interpret words yet. Therefore, words which do not appear in the body text will not return any result despite them denoting a group of present terms. For instance, if we are looking for studies focused on neurological diseases, using neurological as a keyword would not be the best option. Instead, you should use the name of each neurological disease such as bipolar disorder, schizophrenia or depression. In the same fashion, incomplete words do not return any result. Please include an asterisk (*) before and/or after the incomplete word in order to allow for partial matching. Try it out: canc* instead of canc(without wildcard). Also you can try out *oma, or even *geneti* Tip 5: Narrow down your search by filtering the results You can filter the results by the following options: general, study, and dataset. Under these categories, you will find more sub-filters to refine your search. Make sure that you click on Apply in order to filter the results. You can clear the filtering anytime. Advanced Searches Additional example queries: Search for DUO:0000005 and word lung example query Or write: DUO:0000005 AND lung Search for an exome sequencing study in dbGaP example query Or write: study_type: "exome sequencing" AND repository:dbGaP Search for an exome sequencing study in EGA example query Or write: study_type: "exome sequencing" AND repository:ega Search for a dataset that is at the EGA beacon and with type "Whole genome sequencing" and with number of samples between 100 and 2000 and with technology "Illumina HiSeq 2000" example query Or write: is_in_beacon:true AND dataset_types:"Whole genome sequencing" AND samples:[100 TO 2000] AND dataset_technologies:"Illumina HiSeq 2000" Search for PMIDS example query Or write: pmids:32025007

  Documentation discovery/metadata/search-box

• 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

• 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