Search Results - EGA European Genome-Phenome Archive

National Epidemiologic Survey on Alcohol and Related Conditions-III (NESARC-III)

The National Epidemiologic Survey on Alcohol and Related Conditions-III (NESARC-III) is a nationally representative cross-sectional survey of the U.S. general population, which was sponsored by the National Institute on Alcohol Abuse and Alcoholism (NIAAA) and conducted in 2012-2013. The NESARC-III's target population was the U.S. noninstitutionalized civilian population, 18 years and older, including residents of selected group quarters (e.g., group homes, workers' dormitories). Multistage probability sampling was used to randomly select respondents. Primary sampling units (PSUs) were individual counties or groups of contiguous counties, secondary sampling units (SSU) comprised groups of Census-defined blocks, and tertiary sampling units were households within SSUs. Finally, eligible adults within sampled households were randomly selected. Hispanics, Blacks, and Asians were oversampled and resulted in a total of 36,309 respondents. All respondents provided informed consent for survey participation. Data were adjusted for oversampling and screener - and person-level nonresponse, then weighted through post-stratification to represent the US civilian population based on the 2012 American Community Survey. These weighting adjustments were found to compensate adequately for nonresponse. Interviewer field methods involved initial structured home study, in-person training, ongoing supervision, and random respondent callbacks to verify data. The NESARC-III collected information on alcohol and drug consumption, alcohol use disorder, other substance use disorders (e.g., nicotine, cannabis and opioid), and associated physical and psychiatric adverse consequences. In addition to a full array of sociodemographic characteristics such as race/ethnicity, gender, age, risk and environmental factors including adverse childhood experiences (e.g., sexual, physical abuse and neglect) and family history for alcohol, drug use disorders and other psychiatric disorders (e.g., mood, anxiety, personality disorders and PTSD) were included (phenotypic variables=4,320). As part of the NESARC-III, 22,848 informative samples were genotyped on Affymetrix Axiom Exome Array consisting of 319,283 SNPs and 103,404 custom-selected SNPs Array (refer to the SNP annotation file). The latter array was selected based on the addiction associated genes, the results of 5 GWAS of alcohol and other psychiatric disorders, and animal models with addiction phenotypes. After filtering out poor quality SNPs using the standard Affymetrix pipeline there are 295,218 SNPs in the NESARC-III genetic data. The 22,848 subjects in this study were all deeply and consistently phenotyped via structured diagnostic interview. Controls group can be selected for specific disorders from a pool of all samples. Here are numbers of cases for major DSM-5 mental disorders in NESARC-III genetic data: Alcohol use disorder (7,075); Nicotine use disorder (6,641); Drug use disorder (2,570); Major depressive disorder (5,214); Persistent depression(1,429); Bipolar I (543); Anxiety disorders (4,226); PTSD (1,674); Personality disorders (4,014); Eating Disorders (457).

Study phs001590

Molecularly matched targeted therapies plus radiotherapy in patients with newly diagnosed glioblastoma without MGMT promoter hypermethylation (N2M2/NOA-20 phase I/IIa umbrella trial)

Background: Patients with glioblastoma without MGMT promoter hypermethylation are unlikely to benefit from temozolomide (TMZ). Trials aiming at replacing TMZ with targeted agents in not molecularly selected patient populations have failed. Methods: This phase I/IIa umbrella trial aimed at showing safety, feasibility, and preliminary efficacy of targeted compounds in addition to standard radiotherapy initiated within 42 days postoperatively. Molecular diagnostics and bioinformatic evaluation are performed within 28 days after surgery. Stratification for treatment takes place in five subtrials, including alectinib, idasanutlin, palbociclib, vismogedib and temsirolimus, according to the best matching molecular alteration. Patients without matching alterations are randomized between subtrials without strong biomarkers using atezolizumab and asunercept and TMZ as standard of care. Primary objective of the phase I parts of the trial was dose finding or dose validation. In the phase IIa trials, centrally determined progression-free survival at six months (PFS-6) is used as endpoint for efficacy with interim analyses for futility (H0: p=0.231). Results: From May 2018 through July 2022, 301 patients were enrolled and 228 treated in 13 German NOA sites. The alectinib and vismodegib subtrials were closed since no molecularly matching patients were accrued; the idasanutlin subtrial was closed prior to the optimal dose at nine patients at discretion of the company providing the drug. The TMZ subtrial showed a PFS-6 of 18.52% (10/54 patients) (p=0.831) and a median overall survival (OS) of 12.1 months. Asunercept: PFS-6 of 15.4% (4/26) (p=0.8825) and OS of 12.8 months. Atezolizumab: PFS-6 of 21.4% (9/42) (p=0.660) and OS of 11.7 months. Palbociclib with patients demonstrating CDK4 amplification or CDKN2A/B codeletion: PFS-6 of 24.4% (10/41) (p=0.4823) and OS of 12.6 months. Temsirolimus with patients demonstrating mTOR activation: PFS-6 of 39.1% (18/46) (p=0.0109) and OS of 15.4 months. The regimen-limiting toxicity (RLT)-rate is 34.8%, which is insignificantly above the predefined unacceptable rate for RLTs of 30%. Most RLTs had severity grade 3, one RLT had severity grade 4. No RLTs resulted in death. Conclusions: N2M2 allows for elaborate molecular testing being integrated into the treatment decision and efficient determination of treatment activity for patients with newly diagnosed glioblastoma. There is clinical activity of temsirolimus in patients with tumors harboring an activated mTOR pathway although this is not positively prognostic without mTOR inhibition; there is no clinical activity for asunercept and atezolizumab in not molecularly selected patients and also palbociclib in molecularly selected patients.

Study EGAS00001008033

Swarm Learning to identify COVID-19, tuberculosis and leukemia patients based on blood transcriptomes

Identification of patients with life-threatening diseases including leukemias or infections such as tuberculosis or COVID-19 is an important goal of modern precision medicine. However, there is an increasing divide between what is technically possible and what is allowed because of privacy legislation. We have recently illustrated that classical machine learning can identify leukemia patients based on their blood transcriptomes. To facilitate integration of any omics data from any data owner world-wide without violating privacy laws, we here introduce Swarm Learning (SL), a decentralized machine learning approach uniting edge computing, artificial intelligence (AI), blockchain and privacy protection without the need for a central coordinator thereby going beyond federated learning. To illustrate its feasibility, using more than 12,000 transcriptomes from peripheral blood mononuclear cells and more than 2,000 peripheral blood transcriptomes we demonstrate that SL of omics data distributed across different individual sites leads to disease classifiers that outperform those developed at individual sites. Yet, SL completely protects local privacy regulations by design. We propose this approach to noticeably accelerate the introduction of precision medicine.

Dataset EGAD00001006231

The Dutch Microbiome Project Batch 2

The Dutch Microbiome Project (DMP) data includes shotgun metagenomic sequencing of faecal samples 8,208 Dutch individuals. Paired-end sequencing was performed using Illumina HiSeq 2000 platform. Data is archived in two batches to facilitate easier data access and upload to EGA. Batch 2 of DMP includes ~400 samples.

Dataset EGAD00001007501

Targeted sequencing of diffuse large B-cell lymphoma tumour samples from the UK's Haematological Malignancy Research Network

Targeted sequencing was applied to an unselected population-based diffuse large B-cell lymphoma cohort (n=928) diagnosed in the UK's Haematological Malignancy Research Network catchment population of ~4 million (14 centres). DNA extracted from tumour samples was sequenced with a 293-gene panel using the Illumina HiSeq 2500. All data are provided in the CRAM format.

Dataset EGAD00001008616

Studies of Left Ventricular Dysfunction (SOLVD-BioLINCC)

Data Access NOTE:Please refer to the "Authorized Access" section below for information about how access to the data from this accession. Access differs from many other dbGaP accessions. ObjectivesThis study was initiated in 1986, primarily to evaluate the effects of enalapril, an ACE inhibitor, on long-term mortality and major morbidity in a group of participants with left ventricular dysfunction. Two large separate trials were run concurrently as part of SOLVD: 1) a prevention trial of participants with low ejection fraction but no overt symptoms of CHF and, 2) a treatment trial of participants with low ejection fraction and symptoms of CHF. In addition, participants at selected sites were entered into substudies to evaluate the effect of enalapril on a number of intermediate outcomes such as right and left ventricular function and hemodynamics, LV mass and wall stress, hormones, arrhythmias, exercise capacity, and quality of life in subsets of participants. Lastly, a registry of 6,336 participants with congestive heart failure of LV dysfunction was designed to describe the clinical course of an unselected group of participants. Background Congestive Heart Failure (CHF) is a major and increasingly recognized public health problem. The recognition that participants with CHF often have elevated peripheral vascular resistance has led to the introduction of vasodilator therapy, which has emerged as an important component of its treatment. Of the vasodilators, the angiotensin-converting enzyme (ACE) inhibitors appeared to be the most promising. In 1985, little was known about the impact of any long-term drug treatment on survival. SOLVD Registry: The SOLVD Registry is a hospital-based observational study, conducted at selected SOLVD hospitals, of participants with at least moderate left-ventricular dysfunction (EF ≤ 45%) and/or radiologically confirmed heart failure. It consists of a main study (n=6,273) and a substudy (n=898). Although there is overlap between the Registry and the SOLVD trials, the Registry sample is not a subset of SOLVD nor is it the pool of participants eligible for both trials. Participants A total of 2,569 participants were enrolled into the treatment study and 4,228 participants were enrolled in the prevention study. The dataset available through the NHLBI contains the prevention and treatment study data as well as the registry data. Conclusions In the prevention trial, a significant reduction in the incidence of heart failure and the rate of related hospitalizations was observed for participants in the enalapril arm. A statistically significant reduction in mortality was not observed in the enalapril treatment arm; however, there was a trend toward fewer total deaths and deaths due to cardiovascular causes among the enalapril participants (SOLVD Investigators, et al., 1992, PMID: 1463530).

Study phs003668

APOBEC mutagenesis is a common process in normal human small intestine

The single base substitution mutational signatures SBS2 and SBS13, likely caused by APOBEC cytosine deaminases, are common in many human cancer types. However, the stimulus activating APOBEC mutagenesis is unknown and understanding of when it occurs in the progression from normal to cancer cell is limited. Here, as part of a wider survey of human tissues, we whole genome sequenced 342 microdissected normal epithelial crypts from the small intestines of 39 individuals. SBS2/13 mutations were present in 17% normal small intestine crypts and were likely due to APOBEC3A activity. Localised clusters of SBS2/13 mutations (kataegis) were also commonly found. APOBEC mutation burdens were variable between individuals and between crypts from the same individual. Crypts with SBS2/13 often had immediate crypt neighbours without SBS2/13, suggesting that the underlying cause of SBS2/13 is cell-intrinsic rather than a widely distributed microenvironmental exposure, or needs to be permitted by cell-intrinsic conditions. APOBEC mutagenesis occurred throughout the human lifespan, including in young children, and was episodic with a small number of episodes occurring during the life history of a single cell. The results indicate that APOBEC mutagenesis is more common in the small intestine epithelium than in many other cell types, and is an episodic process in vivo initiated or permitted by cell intrinsic factors.

Dataset EGAD00001008764

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

Genetic Determinants of EGFR-Driven Lung Cancer Growth and Therapeutic Response In Vivo

Oncogenic alterations in EGFR frequently co-occur with additional genetic alterations in EGFR-driven lung adenocarcinoma (LUAD), but how specific combinations of mutations affect tumor phenotypes and responses to targeted therapy is yet unknown. We leveraged a genetically engineered mouse model of EGFR mutant/Trp53-deficient LUAD to study the consequences of inactivating 10 different tumor suppressor genes on the fitness and tyorosine kinase inhibitor (TKI) sensitivity of these tumors. We found that loss of Keap1 is associated with a reduced response to therapy. In patients, we found that mutations in the KEAP1/NFE2L2/CUL3 pathway are associated with a significantly shorter time to treatment failure for EGFR TKI therapy compared to matched patients with wild-type KEAP1/NFE2L2/CUL3 tumors. We also analyzed whole exome sequencing data from tumor specimens before TKI treatment and at the time of treatment resistance for mutations in the KEAP1 pathway and these data are being submitted here.  

Study phs002334

Neoadjuvant nivolumab or nivolumab plus ipilimumab in early-stage triple negative breast cancer: phase 2 adaptive BELLINI trial. WES

The adaptive BELLINI trial explored whether short combination ICI induces immune activation (primary endpoint: two-fold increase in CD8+ T cells or IFNG), providing rationale for neoadjuvant ICI without chemotherapy. In window of opportunity cohorts A (4 weeks anti-PD1) and B (4 weeks anti-PD1 + anti-CTLA4), we observed immune activation in 53% (8/15) and 60% (9/15) of patients, respectively. High tumor-infiltrating lymphocytes (TILs) correlated with response. Based on these data, we opened cohort C for patients with high TILs (≥50%) who received 6 weeks neoadjuvant anti-PD1 + anti-CTLA4 followed by surgery (primary endpoint: pathological complete response, pCR). 53% (8/15) of patients had major pathological response (< 10% viable tumor) at resection, with 33% (5/15) having pCR. All cohorts met Simon’s two-stage threshold for expansion to stage II. In conclusion, neoadjuvant immunotherapy without chemotherapy demonstrates potential efficacy and warrants further investigation in patients with early TNBC.

Study EGAS50000000568

Oncogenic FOXL2C134W has gain-of-function chromatin remodeling activity that reprograms glucocorticoid receptor occupancy to promote ovarian granulosa cell tumor growth

Adult type ovarian granulosa cell tumors (AGCTs) are rare malignancies with near universal somatic mutation c.C402G (p.Cys134Trp) in FOXL2, a forkhead box-family transcription factor important for ovarian function. Relapsed AGCT is incurable and the mechanism of the unique FOXL2 mutation remains incompletely understood. To identify FOXL2C134W-dependent pharmacologic synergies, we created and characterized endogenous FOXL2 isogenic AGCT cells and an AGCT tumoroid biobank. A drug screen identified that glucocorticoids promote FOXL2C134W-dependent AGCT growth. Epigenetic investigation revealed that the Cys134Trp mutation exposes latent DNA sequence-specific pioneering activity in FOXL2, a unique oncogenic mechanism. FOXL2C134W pioneering activity redirects glucocorticoid receptor chromatin occupancy to drive hyaluronan synthase 2 gene expression and increase extracellular hyaluronan secretion. Treatment of AGCT models with hyaluronidase reduces viability and this effect can be rescued by dexamethasone. Thus, gain-of-function pioneering activity contributes to the oncogenic mechanism of FOXL2C134W and creates a potentially targetable synergy with glucocorticoid signaling.

Study EGAS50000000622

Genomic determinants of response and resistance to inotuzumab in B-ALL

Inotuzumab Ozogamicin (InO) is an antibody-drug conjugate which delivers calicheamicin to CD22-expressing cells. In a retrospective cohort of InO treated B-cell acute lymphoblastic leukemia (B-ALL) patients, we sought to understand the genomic determinants of response to InO. Acquired CD22 mutations were observed in 11% (3/27) of post-InO relapsed samples. CD22 mutation types were diverse (frameshift, nonsense, missense and stoploss) and we identified multiple mechanisms of mutation induced CD22 escape, including protein truncation, protein destabilization, and epitope alteration. Accelerated acquisition of mutations by error-prone DNA damage repair could drive CD22 mutation and escape. Acquired loss-of-function mutations in TP53, ATM and CDKN2A were observed, suggesting compromise of the G1/S DNA damage checkpoint as a mechanism of evading InO-induced apoptosis. In conclusion, genetic alterations modulating CD22 expression and DNA damage response influence InO efficacy. The diverse mechanisms of CD22 escape advocates for a refined approach for monitoring CD22-targeted therapy.

Study EGAS50000000067

Pyjacker identifies enhancer hijacking events in acute myeloid leukemia including MNX1 activation via deletion 7q

Acute myeloid leukemia with complex karyotype (ckAML) is characterized by high genomic complexity, including frequent TP53 mutations and chromothripsis. We hypothesized that the numerous genomic rearrangements could reposition active enhancers near proto-oncogenes, leading to their aberrant expression. We developed pyjacker, a computational tool for the detection of enhancer hijacking events, and applied it to a cohort of 39 ckAML samples. Pyjacker identified motor neuron and pancreas homeobox 1 (MNX1), a gene aberrantly expressed in 1.4% of AML patients, often as a result of del(7)(q22q36) associated with hijacking of a CDK6 enhancer. MNX1-activated cases show significant co-occurrence with BCOR mutations and a gene signature shared with t(7;12)(q36;p13) pediatric AML. We demonstrated that MNX1 is a dependency gene, as its knockdown in a xenograft model reduces leukemia cell fitness. In conclusion, enhancer hijacking is a frequent mechanism for oncogene activation in AML.

Study EGAS50000000743

pancreatic ductal adenocarcinoma exomes in study: Pro-immunogenic Impact of MEK inhibition combined with an anti-CD40 immunostimulatory antibody

This dataset contains 3 pairs of exomes, germline (from whole blood) and patient-derived xenograft (PDX), from human pancreatic durctal adenocarcinoma patients. The data is referred to in the publication: "Pro-immunogenic impact of MEK inhibition synergizes with agonist anti-CD40 immunostimulatory antibodies in tumor therapy" (Nature Communications, 2020) Abstract: Cancer types with lower mutational load and a non-permissive tumor microenvironment are intrinsically resistant to immune checkpoint blockade. While the combination of cytostatic drugs and immunostimulatory antibodies constitutes an attractive concept for overcoming this refractoriness, suppression of immune cell function by cytostatic drugs may limit therapeutic efficacy. Here we show that targeted inhibition of mitogen-activated protein kinase (MAPK) kinase (MEK) does not impair dendritic cell-mediated T-cell priming and activation. Accordingly, combining MEK inhibitors (MEKi) with agonist antibodies (Abs) targeting the immunostimulatory CD40 receptor resulted in potent synergistic anti-tumor efficacy. Detailed analysis of the mechanism of action of MEKi GDC-0623 by means of flow cytometric analysis of the tumor immune infiltrate and whole tumor transcriptomics showed that, in addition to its cytostatic impact on tumor cells, this drug exerts multiple pro-immunogenic effects, including the suppression of M2-type macrophages, myeloid derived suppressor cells and CD4+ T-regulatory cells. In addition, MEKi was found to induce tumor-cell intrinsic interferon signaling, which contributed to antigen presentation by tumor cells. Finally, the tumoridical impact of MEKi involves the activation of multiple pro-inflammatory pathways involved in immune cell effector function in the tumor microenvironment. Our data therefore indicate that the combination of MEK inhibition with agonist anti-CD40 Ab is a promising therapeutic concept, especially for the treatment of mutant Kras-driven tumors such as pancreatic ductal adenocarcinoma.

Dataset EGAD00001005938

Natural history of clonal haematopoiesis (2017-09-04)

The incidence of acute myeloid leukemia (AML) increases with age and mortality exceeds 90% when diagnosed after age 60. Only 10-15% of cases evolve from a pre-existing myeloproliferative or myelodysplastic disorder; the remaining cases arise de novo without a detectable prodrome and are diagnosed upon development of bone marrow failure. Analysis of diagnostic blood samples has demonstrated that de novo AML is preceded by the accumulation of somatic mutations in pre-leukemic hematopoietic stem and progenitor cells (preL-HSPCs) that subsequently undergo clonal expansion. If individuals in this pre-leukemic phase could be identified, methods for determination of risk and monitoring for progression to overt AML could be developed. However recurrent AML mutations also accumulate during aging in healthy individuals who never develop AML, referred to as age related clonal hematopoiesis (ARCH). To distinguish individuals with preL-HSPCs at high risk of developing AML from those with ARCH, we undertook deep targeted sequencing of genes recurrently mutated in AML in blood samples from 133 individuals in the European Prospective Investigation into Cancer and Nutrition (EPIC) study taken on average 6 years before they developed AML (pre-AML group), together with 683 matched healthy individuals (Control group). Pre-AML cases displayed accelerated age-correlated accumulation of somatic mutations.The identity, number and variant allele frequency (VAF) of mutations differed between the two groups, and were incorporated into a computational model of AML risk prediction that accurately distinguished pre-AML cases from controls on average 7 years prior to AML development. Our findings provide proof of concept that early prediction of AML development is feasible in high-risk populations, paving the way for early disease detection, monitoring, and potentially prevention.

Dataset EGAD00001003703

14970 results for "cancer studies using rna-seq"

in 23.59 milliseconds.