Search Results - EGA European Genome-Phenome Archive

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

The Lung Genomics Research Consortium (LGRC)

Chronic lung diseases represent a broad spectrum of chronic fibrosing/inflammatory lung conditions that are for the most part poorly responsive to treatment and often fatal. COPD/emphysema is the fourth leading cause of death in the United States and the incidence and rate of death from pulmonary fibrosis is increasing each year. Although progress has been made in interpretation of the clinical, radiological, and pathological features of chronic lung disorders, and progress in determining the pathobiology continues, the causes, biologic mechanisms, and therapeutic options remain obscure. Moreover, predicting individuals or populations at risk for developing any of these complex diseases, at present, is not possible. To address this challenge, we plan to create a genetic, molecular, and quantitative clinical phenotyping data warehouse with bioinformatic tools that will empower investigators to make fundamental discoveries in disease pathogenesis, refine diagnostic criteria, and lead to real gains in personalized medicine. The composite genetic, genomic, and epigenetic signature combined with quantitative clinical phenotypes has the potential to characterize the dynamic biological state of a complex disease and complement existing diagnostic approaches that are reliant on traditional clinical measures of disease. In the proposed project, we plan to extend the scope and impact of the NHLBI Lung Tissue Research Consortium (LTRC) biorepository by creating the Lung Genomics Research Consortium (LGRC), a comprehensive genetic, molecular, and quantitative clinical phenotyping warehouse. Our overall hypothesis is that a genetic, molecular, and quantitative clinical phenotyping warehouse combined with a rich clinical database will enable the lung research community to make fundamental discoveries in disease pathogenesis, refine diagnostic criteria, and lead to real gains in personalized medicine. We plan to pursue this hypothesis through the following aims. Specific Aim 1: Establish a genetic, genomic, and epigenetic molecular library to complement the existing clinical database in the LTRC. Specific Aim 2: Develop a quantitative clinical phenotyping platform using existing LTRC data, as well as an enhanced data set including novel quantitative CT and histology imaging analyses. Specific Aim 3: Establish a publicly-accessible database that would integrate the genetic, molecular, and quantitative phenotyping data with the existing clinical data in the LTRC and provide query and data exploration tools that are easily accessible to the lung research community. These discoveries will enable clinicians to Identify individuals at risk of developing chronic lung diseases; Diagnose these conditions earlier; Identify novel mechanisms that cause these diseases; Reclassify disease entities into categories more representative of molecular and cellular pathogenic mechanisms regardless of traditional disease categories; develop personalized approaches to treatment.

Study phs000624

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

NIH RECOVER-Pediatric: Understanding the Long-Term Impact of COVID on Children and Families

The NIH Researching COVID to Enhance Recovery (RECOVER) initiative comprises a set of three combined retrospective and prospective, longitudinal and observational meta-cohort studies with nested case-control studies designed to define and characterize the epidemiology, natural history, clinical spectrum, and underlying mechanisms of post-acute effects of SARS-CoV-2 infection (PASC or Post-COVID syndrome) in a diverse study population representative of the general COVID-19 population in the US. Enrolled patients, with and without known SARS-CoV-2 infection, will be observed for clinical signs and symptoms of PASC and will be assessed for risk and resiliency factors and potential mediating factors associated with the severity and progression of PASC. The objective of the RECOVER initiative is to enhance knowledge of recovery from SARS-CoV-2 infections in order to support development of novel diagnostic and therapeutic interventions. Overarching scientific objectives are as follows:Characterize the incidence and prevalence of sequelae of SARS-CoV-2 infection.Characterize the spectrum of clinical symptoms, subclinical organ dysfunction, natural history, and distinct phenotypes identified as sequelae of SARS-CoV-2 infection. Define the biological mechanisms underlying pathogenesis of the sequelae of SARS-CoV-2 infection. The RECOVER observational studies comprise three cohorts across the lifespan (adult, pediatric, and tissue pathology (autopsy)). The data collection and data analysis plans for each cohort have been harmonized to use common data elements where feasible. Brief descriptions of each cohort are provided in the following paragraphs: 1) NIH RECOVER: A Multi-site Observational Study of Post-Acute Sequelae of SARS-CoV-2 Infection in Adults (see phs003463)The RECOVER adult cohort study is a combined retrospective and prospective, longitudinal, observational meta-cohort of individuals who will enter the cohort with and without SARS-CoV-2 infection and at varying stages before and after infection. Individuals with and without SARS-CoV-2 infection, and with or without PASC symptoms, will be followed to identify risk factors and occurrence of PASC. This study will be conducted in the United States and subjects will be recruited through inpatient, outpatient, and community-based settings. Study data including age, demographics, social determinants of health, medical history, vaccination history, details of acute SARS-CoV-2 infection, overall health and physical function, and PASC symptom screen will be reported by subjects or collected from the electronic health record using a case report form at specified intervals. Biologic specimens will be collected at specified intervals, with some tests performed in local clinical laboratories and others performed by centralized research centers or banked in the Biospecimen Repository. Advanced clinical examinations and radiologic examinations will be performed at local study sites with cross-site standardization. 2) A Multi-Center Observational Study: The RECOVER Post Acute Sequelae of SARS-CoV-2 (PASC) Pediatric Cohort Study (this study)The RECOVER pediatric study is a combined retrospective and prospective, longitudinal, observational meta-cohort of individuals ages newborn-25 years who will enter the cohort with and without SARS-CoV-2 infection at varying stages before and after infection. Individuals with and without SARS-CoV-2 infection and with or without PASC symptoms will be followed to identify risk factors and occurrence of PASC. This study recruit participants inpatient, outpatient, and community-based settings in the United States. Study data including age, demographics, social determinants of health, medical history, vaccination history, details of acute SARS-CoV-2 infection, overall health and physical function, and PASC symptoms will be reported by participants or collected from the electronic health record using a case report form at specified intervals. Biologic specimens will be collected at specified intervals, with some tests performed in local clinical laboratories and others performed by centralized research centers or banked in the Biospecimen Repository. Advanced clinical and radiologic examinations will be performed at local study sites with cross-site standardization. 3) NIH RECOVER: A Multi-site Pathology Study of Post-Acute Sequelae of SARS-CoV-2 Infection The RECOVER tissue pathology study is a cross-sectional study designed to define and characterize the epidemiology, natural history, clinical spectrum, and underlying mechanisms of post-acute effects of SARS-CoV-2 infection in a diverse population representative of the general COVID-19 population in the US. The autopsy study will characterize the pathology of PASC in (i) non-hospitalized patients who die 30 days or later from symptom onset of COVID-19, and (ii) hospitalized patients who die 30 days or later after discharge from a hospitalization for COVID-19. The study will include decedents who had previously fully recovered from SARS-CoV-2 infection (i.e., >30 days from onset in non-hospitalized, or >30 days from discharge in hospitalized patients), and decedents who meet clinical criteria of PASC as defined by the recent World Health Organization publication (see Section 5.4 below). The autopsy study will also explore the pathology of acute SARS-CoV-2 infection in a smaller subset of patients who died 15-30 days from symptom onset. This protocol defines the common set of clinical data elements, autopsy procedures for tissue collection, core measures, pathology protocols, shared pathology tissues, data elements, and methodology. Each investigator site is expected to perform autopsies on the decedents to address the pathophysiology of the potential long-term effects of SARS-CoV-2 infection on human health. The Consortium analysis plan aims to address research questions by incorporating: 1) tissue obtained from autopsies performed at each Phase II participant's site; and 2) tissue available from other pathology investigators/autopsy sites within the Consortium.

Study phs003461

MDACC Lymphoma & Myeloma WGS of Tumor and Non-tumor Cells in Multiple Myeloma

FastQ files from paired tumor and non-tumor WGS data from patients diagnosed with newly diagnosed (n = 6), refractory/relapsed multiple myeloma (n = 3) or plasma cell leukemia (n = 1). These samples presented >95% tumor PCs in bone marrow aspirates. Plasma cells and T cells (non-tumor cells) were isolated from bone marrow aspirates using a magnetic approach.

Dac EGAC50000000282

Whole-genome sequencing data of metastatic salivary gland cancer

This dataset contains whole-genome sequencing data of three patients with metastatic salivary gland cancer who underwent autopsy to harvest tumor biopsies from spatially separated metastatic sites and biopsies from healthy skin as a control. Two patients had the subtype adenoid cystic carcinoma (patients 1 and 4) and one patient had the subtype myoepithelial carcinoma.

Dataset EGAD50000002056

WGS of Newly Diagnosed and Refractory/Relapsed Multiple Myeloma

This dataset includes paired tumor and non-tumor WGS data from patients diagnosed with newly diagnosed (n = 6), refractory/relapsed multiple myeloma (n = 3) or plasma cell leukemia (n = 1). These samples presented >95% tumor PCs in bone marrow aspirates. Plasma cells and T cells (non-tumor cells) were isolated from bone marrow aspirates using a magnetic approach.

Dataset EGAD50000001177

Shallow whole genome sequencing data from circulating tumour DNA (ctDNA) data of High Grade Serous Ovarian Cancer Patients (batch 1)

The dataset contains shallow whole genome sequencing data of 128 high-grade serous carcinoma (HGSC) patients sequenced with Novoseq 6000. The 128 samples are plasma samples that have been collected before treatment. The files provided are paired fastq files.

Dataset EGAD50000000949

Total RNA sequencing of fibroblasts from an control individual

Total RNA sequencing of fibroblasts from an individual with 30-55x GCC repeats in the FMR1 5'UTR. Libraries were prepared with total RNA with Ribo-Zero ribosomal RNA depletion (illumina), and sequenced paired-end, 75bp on a NextSeq 550 system. This dataset contains three RNA-sequencing replicates from the same cell line.

Dataset EGAD50000000922

Highly complex single-cell mixture of 5 individuals of high cell number

Mixture of 5 unrelated individuals sequenced by 10x as a scATAC-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile using the De-goulash pipeline. The separation file is submitted as the processed file. The bam are submitted as unprocessed files.

Dataset EGAD50000000480

EGAD00000000049

RNA-SEQ data from oestrogen-receptor-alpha-positive metastatic lobular breast cancer sample

Dataset EGAD00000000049

EGAD00000000045

Genomic sequencing and transcriptome shotgun sequencing of a metastatic tumour and its recurrence after drug therapy in a single patient

Dataset EGAD00000000045

RNA sequencing data of pediatric ETV6::RUNX1 acute lymphoblastic leukemia (set 4)

The dataset includes RNA sequencing FASTQ files from a diagnostic tumor sample of one ETV6::RUNX1 ALL patient (ALLK-132). Novogene's internal method was used in directional library preparation including rRNA removal. The diagnostic tumor sample was sequenced using Illumina Novaseq X Plus, and the target sequencing depth was 21 Gb.

Dataset EGAD50000002590

Hospitalised COVID-19 patients: transcriptomic data (longitudinal design- 3 timepoints)

Hospitalised COVID-19 patients (n=81), cohort from Latvia, 224 transcriptome samples. Longitudinal sampling: A- acute phase, B- 1-month post-hospitalisation, C- 3-4 months post-hospitalization All patients(n=81) were unvaccinated during the study period, Male (n=35), Female (n=46), average age ~57

Dataset EGAD50000002067

DDD DATAFREEZE 2016-10-03: 7832 trios - VCF files

DDD DATAFREEZE 2016-10-03: 7831 trios - VCF files

Dataset EGAD00001003340

WES of probands in KLB project

These are the vcf files of exome sequencing of the two probands who were found to harbor mutations in KLB. Sample: EGAN00001564799 is the proband 1; Sample: EGAN00001564800 is the proband 11 in the KLB paper. Exome capture was performed using the SureSelect All Exon capture (Agilent Technologies, Santa Clara, CA USA) and sequenced on the HiSeq2500 (Illumina, San Diego CA USA).

Dataset EGAD00001003463

RRBS sequencing data of ovarian cancer, breast cancer, control tissues, and white blood cell DNA.

The dataset comprises 8 breast cancer, 11 ovarian cancer, 1 benign tumour, 18 normal tissue, 2 endometrium, and 23 white blood cell samples. Genome wide methylation analysis was performed by Reduced Representation Bisulfite Sequencing (RRBS) on Illumina HiSeq 2500. Data is provided as FASTQ files

Dataset EGAD00001003822

Whole genome sequencing of HSPC and SI clones of disomy- and trisomy 21 fetuses samples (HiSeq X Ten samples)

Whole genome sequencing of HSPC and SI clones of 2 disomy- and 1 trisomy 21 fetuses samples (HiSeq X Ten samples). 5 disomy clones and 5 trisomy clones were included in this experiment. Three bulk samples were also included.

Dataset EGAD00001005459

Whole genome sequencing of glioblastoma reveals enrichment of non-coding constraint mutations in known and novel genes

The dataset comprises of an aggregate level VCF (version 4.1), containing the somatic point and indel mutations found across the glioblastoma cohort (SweGBM-1, n=38 samples). The VCF file is in accordance with the HTS format specifications (https://samtools.github.io/hts-specs/).

Dataset EGAD00001006084

The natural history of clonal haematopoiesis: phase 6 targeted

Deep targeted sequencing of 56 genes associated with clonal haematopoiesis and haematological malignancy in peripheral blood-derived DNA from 11 older adults, each previously sampled 2-5 times over the preceding ~13 years.

Dataset EGAD00001007683

Mixture of 2 (closer mtDNA)

Mixture of 2 unrelated individuals (of close mtDNA haplogroup) sequenced by 10x as a scRNA-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile. The clustering of SNPs is submitted as the processed file. The Sequencing fastqs are submitted as unprocessed files.

Dataset EGAD00001008727

RNA sequencing of Human Organoid Lines

The study will use RNA sequencing to aid in benchmarking different culture conditions in a set of genetically annotated human organoid lines. The data will be used to assess whether there are any clonal differences introduced when culturing these lines in different conditions.

Dataset EGAD00001007971

Post Mortem brain data used in paper "Significant and pervasive effects of RNA degradation on Nanopore direct RNA sequencing"

This dataset contains data used in the paper titled "Significant and pervasive effects of RNA degradation on Nanopore direct RNA sequencing. The data consists of one post mortem sample that was sequenced with direct RNA sequencing form Oxford Nanopore Technologies on a promethION flow cell.

Dataset EGAD00001009308

DDD resource files

DDD resource files (e.g. link between sample and individual ids)

Dataset EGAD00001010136

RNAseq data from NEN patient derived tumor organoids (PDTOs) and matched parental tumors - MUMC

The dataset includes fastq files from 4 NEN tumors or metastases and matched PDTOs. The sequencing was done with either a Nextseq 2000 or a NovaSeq 6000 instrument.

Dataset EGAD00001009991

15407 results for "1 mil coins fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..buoc"

in 22.84 milliseconds.