12403 results for "cancer studies using rna-seq"

in 60.44 milliseconds.

• Privacy Notice for EGA Web user

  Privacy Notice for EGA Public Website This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by dr. Thomas Keane, by: email at: tk2@ebi.ac.uk or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org , or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? For providing you access to the website and for offering support whilst using the website, we need your consent under Article 5 (2) of the IP 68 (equivalent to Article 6 (1)(a) of the GDPR). For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: IP addresses Date and time of a visit to the service website Operating system Amount of data transmitted Browser Email address (only when support is requested by the user) The data controller will use your personal data for the following purposes: To provide the user access to the service To better understand the needs of the users and guide future improvements of the service To monitor website activities according to and in compliance with the Terms of Use To better understand the needs of the website visitors and guide future improvements of the service To conduct and monitor website security activities To create anonymous usage statistics 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? There are no personal data transfers to third countries or international organisations. 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration. Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period. Request information to understand data processing activities when the results of these activities are applied to you. Object at any time to the processing of your personal data unless we can demonstrate that we have legitimate reasons to process your personal data. Request free of charge and without excessive delay rectification or erasure of your personal data if we have not been processing it respecting the data protection policies of the respective controllers. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. Published at: February 6, 2019

  Documentation data-protection/privacy-notice/ega-website

• 33 patients with Monoclonal Gammopathy of Undetermined Significance (MGUS) had whole exome sequencing performed. Cells were sorted by FACSAria using CD138, CD19 and CD56 to obtain a pure abnormal plasma cell population. Generated somatic variants were compared to a previous study of 463 multiple myeloma patients.

  Monoclonal gammopathy of undetermined significance (MGUS) is a premalignant precursor of multiple myeloma (MM) with a 1% risk of progression per year. Although targeted analyses have shown the presence of specific genetic abnormalities such as IGH translocations, RB1 deletion, 1q gain, hyperdiploidy or RAS genes mutations, little is known about molecular mechanism of malignant transformation. We have performed whole exome sequencing together with SNP array analysis in 33 flow-cytometry separated abnormal PC samples of MGUS patients to describe somatic gene mutations and chromosome changes at the genome-wide level. Non-synonymous mutations (NS-SNVs) and copy number alterations (CNAs) were present in 97.0% and in 63.6% of cases, respectively. Importantly, the number of somatic mutations was significantly lower in MGUS compared to MM (p<10-4) and we have identified 6 myeloma significantly mutated genes which are KRAS, NRAS, DIS3, HIST1H1E, EGR1 and LTB in the MGUS dataset. We also found a positive correlation with increasing chromosome changes and somatic mutations. IGH translocations were present in 27.3% of cases comprising t(4;14), t(11;14), t(14;16) or t(14;20) and were in a similar frequency to MM, which corresponded with primary lesion hypothesis. Data from this study showed MGUS is a genetically comprehensive disease, however overall genetic instability is significantly lower compared to MM.

  Study EGAS00001001658

• CSER: South-Seq: DNA Sequencing for Newborn Nurseries in the South

  SouthSeq, part of the Clinical Sequencing Evidence-Generating Research (CSER2) effort, aims to perform genome sequencing for infants in nurseries at hospitals in Alabama, Mississippi, Louisiana, and Kentucky. SouthSeq aims to sequence 600 newborn babies presenting with congenital anomalies, or other signs of a rare genetic disorder. The primary goals of SouthSeq are to provide early diagnoses to children with rare genetic conditions, to demonstrate the utility of genome sequencing as a frontline test with potential to improve intermediate and long-term clinical outcomes, and to equip non-genetics providers to deliver test results in order to facilitate the conduction of genome sequencing outside of major medical centers where patients may not have access to a genetics provider. SouthSeq also aims to ensure that genomic testing is applied across diverse communities; recruitment efforts focus on patients from rural and minority populations that have been historically under-represented in both medicine and genomics research. Sequencing and analysis for SouthSeq are being conducted at the HudsonAlpha Institute for Biotechnology in Huntsville, Alabama (https://www.hudsonalpha.org/). Enrollment of infants with signs of genetic disease is approved at five clinical sites, including nurseries at the University of Alabama at Birmingham, the University of Mississippi Medical Center, Woman's Hospital in Baton Rouge, Children's Hospital in New Orleans, and the University of Louisville. Both biological parents are enrolled when available so that follow-up testing can be performed to determine inheritance. Further, participant families may choose to opt-into return of secondary findings identified in the proband, which focus on pathogenic and likely pathogenic variation identified within ACMG SFv3.0 genes.

  Study phs002307

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! 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! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• Defective Homologous Recombination DNA Repair as Therapeutic Target in Advanced-Stage Chordoma (HIPO_021)

  HIPO project: HIPO_021 Importance: Chordomas are rare tumors of the axial skeleton and skull base with few therapeutic options and no clinically validated molecular drug targets. The value of comprehensive genomic analyses for guiding medical therapy of patients with advanced-stage chordoma is unknown.Objective: To identify therapeutically tractable genetic lesions in a cohort of chordoma patients within a genomics-guided precision oncology program and to document the outcome of individualized, molecularly targeted chordoma therapy.Design, Setting, and Participants: We performed whole-exome sequencing of tumor and matched germline control samples from seven patients with locally advanced or metastatic chordoma who were enrolled in a cross-institutional molecular stratification registry trial for younger adults with advanced-stage cancer across all histologies and patients with rare tumors. All patients were heavily pretreated and had progressive disease prior to molecular analysis.Interventions: Individualized medical therapy was administered according to the patients’ molecular profiles.Main Outcomes and Measures: Candidate therapeutic targets identified by whole-exome sequencing and response to genotype-directed therapy.Results: All patients harbored alterations of two or more genes known to be involved in DNA repair via homologous recombination (HR), including heterozygous deletions of ERCC6, FANC family members, RAD51L (n = 6), BRCA2 (n = 5), ATR, CHEK2, RAD18, RAD51B, and XRCC3 (n = 4); inactivating PTEN mutations coupled with loss of heterozygosity (n = 2); and pathogenic germline variants in BRCA2 (n = 1), NBN (n = 1), and CHEK2 (n = 1) that were accompanied by somatic deletion of the corresponding wild-type alleles. Consistently, a mutational signature associated with defective HR was enriched in all samples and co-occurred with extensive genomic instability, as evidenced by HR deficiency scores and high numbers of large-scale state transitions. These results prompted off-label treatment with the poly(ADP-ribose) polymerase (PARP) inhibitor olaparib in a patient whose tumor was refractory to irradiation and systemic treatment with imatinib, which led to a prolonged response and substantial clinical improvement.Conclusions and Relevance: Advanced-stage chordomas are frequently characterized by genomic imprints of defective HR DNA repair. HR deficiency represents a new therapeutic opportunity in this intractable disease through repositioning of PARP inhibitors that warrants further exploration in clinical trials.

  Study EGAS00001002720

• Clinical outcomes in ctDNA-positive urothelial carcinoma patients treated with adjuvant immunotherapy

  Minimally invasive approaches to detect residual disease after surgery are urgently needed to select patients at highest risk for metastatic relapse for additional therapies. Circulating tumour DNA (ctDNA) holds promise as a biomarker for molecular residual disease (MRD) and relapse,1-3 but its clinical value has yet to be demonstrated in a randomised clinical trial. We evaluated outcomes in post-surgical ctDNA-positive (+) patients in a randomised phase III trial of adjuvant atezolizumab versus observation. IMvigor010 enrolled 809 patients with muscle-invasive urothelial carcinoma and did not meet its primary endpoint of disease-free survival (DFS) in the intent-to-treat population. Within the study, an exploratory planned analysis of prospectively collected plasma was performed, which tested the utility of ctDNA to identify patients who may benefit from adjuvant atezolizumab treatment. ctDNA was measured at the start of therapy (cycle 1 day 1; C1D1) and at week 6 (cycle 3 day 1; C3D1), and 581 patients were evaluable for ctDNA. The prevalence of ctDNA positivity at C1D1 was 37% (n=214), and ctDNA positivity identified patients with poor prognosis (observation arm DFS HR= 6.19 (4.29, 8.91), p<0.0001). Here we show that ctDNA(+) patients had improved DFS and overall survival (OS) with atezolizumab versus observation (DFS HR= 0.56 (0.41-0.77); p=0.0003 and OS HR= 0.58 (0.4-0.86); p=0.0063). No difference in DFS or OS between arms was noted for ctDNA-negative patients. The rate of ctDNA clearance was higher with atezolizumab (18%) versus observation (4%) (p=0.0041). Transcriptomic analysis revealed that tumours from ctDNA(+) patients had higher expression of cell cycle and keratin genes. Within the ctDNA(+) patient population in the atezolizumab arm, non-relapsing patients were further enriched in prominent immune response signatures including PD-L1, IFNG, CXCL9, and high tumour mutational burden, whereas relapse was associated with angiogenesis and fibroblast-transforming growth factor-beta signatures (F-TBRS). TCGA molecular subset analysis revealed increased efficacy of atezolizumab in patients with basal-squamous tumours, consistent with underlying tumour-immune contexture. Together these findings suggest that adjuvant atezolizumab may be associated with improved outcomes compared with observation in this high-risk ctDNA(+) population. These findings, if validated in other settings, would shift approaches to post-operative cancer care.

  Study EGAS00001004997

• Tumor transcriptome profiling from the OAK and POPLAR randomized clinical trials of atezolizumab in 2L NSCLC

  This dataset includes full tumor transcriptomes from 891 advanced NSCLC tumors. These data originate from pre-treatment samples from two large randomized clinical trials for second-line non-small cell lung cancer (POPLAR and OAK). The patients in these trials were treated with either the PD-L1 inhibitor atezolizumab or chemotherapy.

  Dataset EGAD00001007703

• Integrated genomic analysis identifies driver genes and cisplatin-resistant progenitor phenotype in pediatric liver cancer

  Dataset EGAD00001007858

• The Precision Medicine in Liver Cancer across an Asia-pacific NETwork (PLANET) - Intratumoural immune heterogeneity

  The clinical relevance of immune landscape intratumoural heterogeneity (immune-ITH) and its role in tumour evolution remain largely unexplored. Here, we uncover significant spatial and phenotypic immune–ITH from multiple tumour sectors and decipher its relationship with tumour evolution and disease progression in hepatocellular carcinomas (HCC). Immune–ITH is associated with tumour transcriptomic-ITH, mutational burden, and distinct immune microenvironments. Tumours with low immune–ITH experience higher immunoselective pressure and escape via loss of heterozygosity in human leukocyte antigens and immunoediting. Instead, the tumours with high immune-ITH evolve to a more immunosuppressive/exhausted microenvironment. This gradient of immune pressure along with immune-ITH represents a hallmark of tumour evolution, which is closely linked to the transcriptome-immune networks that contributes to disease progression and immune inactivation. Remarkably, high immune-ITH and its transcriptomic signature are predictive for worse clinical outcome in HCC patients. This in-depth investigation of ITH provides evidence on tumour-immune co-evolution along HCC progression.

  Study EGAS00001003814

• Altered enhancer-promoter interaction leads to MNX1 expression in pediatric acute myeloid leukemia with t(7;12)(q36;p13)

  Acute myeloid leukemia (AML) with the t(7;12)(q36;p13) translocation occurs only in very young children and has a poor clinical outcome. The expected oncofusion between breakpoint partners (MNX1 and ETV6) has only been reported in a subset of cases. However, a universal feature is the strong transcript and protein expression of MNX1, a homeobox transcription factor that is normally not expressed in hematopoietic cells. Here, we map the translocation breakpoints on chromosomes 7 and 12 in affected patients to a region proximal to MNX1 and either introns 1 or 2 of ETV6. The frequency of MNX1 overexpression in pediatric AML (n=1556, own and published data) is 2.4% and occurs predominantly in t(7;12)(q36;p13) AML. Chromatin interaction assays in a t(7;12)(q36;p13) iPSC cell line model unravel an enhancer-hijacking event that explains MNX1 overexpression in hematopoietic cells. Our data suggest that enhancer-hijacking is a more common and overlooked mechanism for structural rearrangement-mediated gene activation in AML.

  Study EGAS50000000130