22928 results for "ega"

in 20.13 milliseconds.

• Security Overview

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

  Documentation about/security

• EGA submission account terms

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

  Documentation submission/terms

• Metadata Public API

  Metadata Rest Endpoints Common Aspects Functionality Identifiers Requests and Responses Request Response Querying Querying by Object Cross-Querying by Object Common Aspects Functionality The Metadata REST API allows EGA users to request metadata from the EGA. Using this api you will be able to obtain the publicly available information from EGA study, sample, experiment, run, analysis, policy, dac and dataset. The API also allows for objects to be cross-referenced in order to obtain for example all the datasets linked to a dac. Identifiers EGA objects can be identified by their unique accession. These are ID's displayed everywhere, shared among all EGA locations and specific for each data type (More information on the list below) EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID Server Request and Response Request All the endpoints implement these two HTTP methods, GET and HEAD. Moreover, there is an authentication layer that allows to disclose the private information about each object if the user runs the endpoint with their token and has permissions to the related dataset. HTTP Method Description GET Returns the objects and their public information (including private information if the user has permissions) HEAD Returns the count of objects to be returned Response API responses are diverse but they always return a status call. Below you have a summary on what these codes mean and some tips that can help you troubleshooting them: HTTP Status Code Description Resolution 200 OK No error handling necessary 206 Partial Content Expected status code when paginating the results. No error handling necessary 400 BAD REQUEST Request incorrectly formulated 401 UNAUTHORISED/FORBIDDEN You do not have permissions over the object you are trying to access. / The authorised user is not permitted to make the given request. 404 NOT FOUND The object/resource you are trying to access does not exist. 500 INTERNAL SERVER ERROR This is a server-side error, try later. If the issue persists, contact the Heldpesk. Querying Querying by Object In the below documentation, worked examples can be found on how to use the API, to query about each unique EGA object. https://metadata.ega-archive.org/analyses/{id} https://metadata.ega-archive.org/dacs/{id} https://metadata.ega-archive.org/datasets/{id} https://metadata.ega-archive.org/runs/{id} https://metadata.ega-archive.org/samples/{id} https://metadata.ega-archive.org/studies/{id} Worked example for the EGA data access committee(DAC) EGAC00001000514 https://metadata.ega-archive.org/dacs/EGAC00001000514 Points to notice Please, be advised that all EGA objects can be queried by using the same endpoint. For example: https://metadata.ega-archive.org/datasets Returns all the datasets registered at the EGA. https://metadata.ega-archive.org/datasets?limit=5&offset=15 Returns 5 results skipping the initial 15 results. Cross-Querying by Object The EGA REST API Metadata also allows for the crossquerying of public metadata. For example, should I want to query the datasets included in the ICGC DAC: https://metadata.ega-archive.org/dacs/EGAC00001000010/datasets Below, you can find worked examples on how to perform the call to the API. https://metadata.ega-archive.org/datasets/EGAD00001000645/analyses https://metadata.ega-archive.org/datasetsEGAD00001000645/files https://metadata.ega-archive.org/datasets/EGAD00001000620/runs https://metadata.ega-archive.org/datasets/EGAD00001000620/samples https://metadata.ega-archive.org/samples/EGAN00001092114/datasets https://metadata.ega-archive.org/files/EGAF00000056146/dacs https://metadata.ega-archive.org/files/EGAF00000056146/datasets https://metadata.ega-archive.org/files/EGAF00000056146/studies There are more endpoints included in this category. Please, find all the possibilities (green tick) in the table below. Table The table displays in a ordered fashion the objects that can be crossreferenced using the metadata API. BY Analysis Dac Dataset Experiment Policy Run Sample Study File Analysis ✔ ✔ Dac ✔ ✔ Dataset ✔ ✔ ✔ ✔ Experiment ✔ ✔ ✔ ✔ Policy ✔ Run ✔ ✔ ✔ Sample ✔ ✔* ✔ Study ✔ ✔ ✔ ✔ ✔ ✔* File ✔ *: These cross queries do not include data from Array-File submissions. Check out the SPEC

  Documentation discovery/metadata/public-metadata-api

• Woodcock et al TenMenDeep Study EGA Dataset B

  Woodcock et al TenMenDeep EGA Dataset B. These are Illumina based deep sequencing data based on bait capture sequencing. See Woodcock et al methods for more detail. Note: the Amplicon sequencing data type is selected because the EGA Website currently has no option to select Bait Capture Sequencing or similar.

  Dataset EGAD00001005382

• Woodcock et al TenMenDeep Study EGA Dataset A

  Woodcock et al TenMenDeep EGA Dataset A. These are Illumina based deep sequencing data based on bait capture sequencing. See Woodcock et al methods for more detail. Note: the Amplicon sequencing data type is selected because the EGA Website currently has no option to select Bait Capture Sequencing or similar.

  Dataset EGAD00001005381

• PGDx EGA Data Access Committee

  Dac EGAC00001002922

• Implementation of the GDPR

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

  Documentation about/privacy-notice

• Tools

  EGA Tools This page provides details of the applications available at the EGA. Submission Tool Description EgaCryptor Encrypt and create md5sum values. Crypt4gh Encrypt, decrypt or re-encrypt files. INBOX Upload your files once encrypted. FTP Upload your files once encrypted. Submitter Portal Submit and manage your submission metadata online (SEQUENCING AND PHENOTYPE ONLY) Submitter Portal API Submit and manage your submission metadata programmatically. Webin Submit and manage your submission metadata online (array data) Webin API Submit metadata using XML files. Aimed to array-based submissions. Star2xml Format conversion tool to transform tabular formats (e.g. spreadsheets) into EGA's XMLs. Used for large programmatic submissions. Data Access Tool Description DAC Portal Manage and control data access request. Download Tool Description PyEGA3 Download and decrypt datasets requested through your EGA web account. Live Outbox Download and decrypt datasets requested through your EGA web account. Fuse Client A quick and convenient way to browse through EGA files without the need for complete downloads. EGA QuickView A quick and convenient way to browse through EGA files without the need for complete downloads.

  Documentation tools

• Catalogue Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue What is in the EGA? The European Genome-phenome Archive (EGA) overview The EGA archives and distributes the results of several types of studies. Such studies include genome-wide association studies (GWAS), different purpose sequencing and molecular diagnosis assays among others. Moreover, these studies target many different kind of diseases from cancer to neurodegenerative alterations. We summarised all this data in the charts below. The statistics are computed daily based on an updated list of studies. Each pie chart depicts a different aspect of the studies: which disease type was studied, which type of sampling method was used and what was the scope of the genomic analysis. Number of studies per disease type Studies in the EGA by disease barHorizontalChart('disease-graph', 'https://stats.ega-archive.org/catalog/by_disease') Number of studies per technology type Studies in the EGA by technology barHorizontalChart('technology-graph', '/stats/studies/technology', 'Include dbGaP') Number of studies per sample type Studies in the EGA by samples barChart('samples-graph', '/stats/studies/sample-types', 'Include dbGaP')

  Documentation about/statistics/catalogue

• DAC-for-UniExome-EGA-upload-2021

  Dac EGAC00001002168