16802 results for "sec+and+unspecified+malignant+neoplasm"

in 52.41 milliseconds.

• Cell-Free, Methylated DNA in Blood Samples Reveals Tissue-Specific, Cellular Damage from Radiation Treatment

  Radiation therapy is an effective cancer treatment, although damage to surrounding healthy tissues can also occur. Cell-type specific DNA methylation patterns can be used to decode the cellular origins of cell-free DNA fragments, allowing for minimally-invasive monitoring of tissue damage. To evaluate whether changes in cell-free DNA methylation can indicate damages to tissues in patients treated with radiation, we collected serum samples from 15 breast cancer patients at three timepoints during their standard-of-care radiation therapy after surgery. A baseline sample was taken for each patient before onset of radiation therapy and a second End-Of-Treatment (EOT) sample was taken 30 minutes after the last treatment fraction. Finally, a recovery sample was taken one month after completion of radiation therapy. From serum samples, cell-free DNA was isolated and bisulfite capture-sequencing DNA methylation data were generated. Bisulfite capture-sequencing DNA methylation data were also generated from buffy coat and tissue-specific endothelial gDNA samples as well as from serum/plasma samples of healthy controls. The analysis of serum samples from breast cancer patients undergoing radiation treatment revealed distinct tissue-specific epithelial and endothelial responses to radiation across multiple organs. In conclusion, as a proof of concept we show that cell-type specific methylation signatures can be applied to detect cellular injury from radiation treatment using minimally invasive cell-free DNA in blood samples.

  Study phs003290

• Noninvasive prenatal molecular karyotyping from maternal plasma

  Fetal DNA is present in the plasma of pregnant women. Massively parallel sequencing of maternal plasma DNA has been used to detect fetal trisomies 21, 18, 13 and selected sex chromosomal aneuploidies noninvasively. Case reports describing the detection of fetal microdeletions from maternal plasma using massively parallel sequencing have been reported. However, these previous reports were either polymorphism-dependent or used statistical analyses which were confined to one or a small number of selected parts of the genome. In this report, we reported a procedure for performing noninvasive prenatal karyotyping at 3 Mb resolution across the whole genome through the massively parallel sequencing of maternal plasma DNA. This method has been used to analyze the plasma obtained from 6 cases. In 5 cases, fetal microduplications or microdeletions have been detected successfully from maternal plasma. The two cases with fetal microduplications represented the first noninvasive prenatal detection of such changes from maternal plasma. In the remaining case, the plasma DNA sequencing result was consistent with the pregnant mother being a carrier of a microduplication. Simulation analyses were performed for determining the number of plasma DNA molecules that would need to be sequenced and aligned for enhancing the diagnostic resolution of noninvasive prenatal karyotyping to 2 Mb and 1 Mb. In conclusion, noninvasive prenatal molecular karyotyping from maternal plasma by massively parallel sequencing is feasible and would enhance the diagnostic spectrum of noninvasive prenatal testing.

  Study EGAS00001000439

• Bibliography Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue Here we expose in a yearly and cumulative manner, the publications, citations, publishers journals and impact factor of EGA related studies. Publications citing data stored at the EGA The studies that use EGA datasets are requested to cite the EGA into their bibliography. This fact allows for a faster spreading of the role and purpose of the EGA, being the availability of their studies for testability and reusability purposes. In order to track the studies we use the unique study accession, provided by the EGA when submitting a new study, and comprised of the keyword EGAS followed by 11 digits such as EGAS00000000001. We use the Europe PMC RESTful Web Service in order to query, and index studies where the EGAS accession was used. Below, you can find a chart showing the journal publishers of the studies citing data stored in the EGA being cited: Publications Citing Data Stored in the EGA pieChart('publishers-citations', 'https://stats.ega-archive.org/publishers/citations', 'Publishers') Number of publications citing data stored in the EGA by year Here, you can find a chart showing the number of publications citing data stored in the EGA by year. These publications could have deposit, or re-used the data. The study acession can be found in the publication. The default values are non-cumulative. You can see cumulative values by clicking "Cumulative". Number of Publications Citing Data Stored in the EGA by Year barChart('publications-by-year', 'https://stats.ega-archive.org/publications/year', ['Number of Publications by Year', 'Publications by Year']) Journal Impact Factor of Publications Citing Data Stored in the EGA Here, you can find a chart showing the journal impact factor of publications citing data stored in the EGA. We have used Scimago Journal Rank for this purpose. Low impact treshold was defined between 0.0 and 5.0 excluding; Medium impact treshold was defined between 5.0 and 10.0 excluding; High impact range was established from values equal to or higher than 10.0; Journal Impact Factor of Publications Citing Data Stored in the EGA pieChart('citations-publication-impact-factor', 'https://stats.ega-archive.org/citations/publication/impact/factor', 'Publication Impact Factor') Publications citing a publication containing a EGA study accession The publications, stating a EGA study accession in the bibliography, can be cited for testibility or reusability purposes. Below, you can find a chart showing the publishers of the publications being cited: Publications Citing a Publication Containing a EGA Study Accession pieChart('publications-citations', 'https://stats.ega-archive.org/publications/citations', 'Publishers') Number of publications citing a publication containing a EGA study accession by year Here, you can find a chart showing the number of publications citing a publication containing a EGA study accession by year by year. The values are non-cumulative: Number of published citations by year barChart('citations-year', 'https://stats.ega-archive.org/citations/year', ['Number of Publications', 'Citations by Year'])

  Documentation about/statistics/bibliography

• Neoadjuvant combination PD-L1 plus CTLA-4 blockade in patients with cisplatin-ineligible operable urothelial carcinoma

  Immune checkpoint therapy (ICT) is being tested in the neoadjuvant setting for patients with localized urothelial carcinoma (UC), with one study reporting data in cisplatin-ineligible patients who received anti PD-L1 monotherapy. The study reported that patients with bulky tumors, a known high-risk feature defined as greater than clinical T2 disease, had fewer responses, with pathologic complete response (pCR) rate of 17%. Here, we report on the first pilot combination neoadjuvant trial (NCT02812420) with anti-PD-L1 (durvalumab) plus anti-CTLA-4 (tremelimumab) in cisplatin-ineligible patients, with all tumors identified as having high risk features (N=28). Primary endpoint was safety and we observed 6 of 28 patients (21%) with grade ≥3 immune-related adverse events, consisting of asymptomatic laboratory abnormalities (N=4), hepatitis and colitis (N=2). We also observed pCR of 37.5% and downstaging to pT1 or less in 58% of patients who completed surgery (N=24). In summary, we provide initial safety, efficacy and biomarker data with neoadjuvant combination anti-PD-L1 plus anti-CTLA-4, which warrants further development for patients with localized UC, especially cisplatin-ineligible patients with high-risk features who do not currently have an established standard-of-care neoadjuvant treatment. Publication: Gao et al. Neoadjuvant PD-L1 plus CTLA-4 blockade in patients with cisplatin-ineligible operable high-risk urothelial carcinoma. Nature Medicine volume 26, pages1845–1851(2020)

  Study EGAS00001004074

• Efficacy of JAK/STAT pathway inhibition in murine xenograft models of early T-cell precursor (ETP) acute lymphoblastic leukemia

  Early T-cell precursor (ETP) acute lymphoblastic leukemia (ALL) is a recently described subtype of T-ALL characterized by a unique immunophenotype and genomic profile as well as a high rate of induction failure. Frequent mutations in cytokine receptor and JAK/STAT signaling pathways led us to hypothesize that ETP-ALL is dependent on JAK/STAT signaling. Here we demonstrate aberrant activation of the JAK/STAT pathway in ETP-ALL blasts relative to non-ETP T-ALL. Moreover, ETP-ALL showed hyperactivation of STAT5 in response to IL7, an effect that was abrogated by the JAK1/2 inhibitor ruxolitinib. In vivo, ruxolitinib displayed activity in 6/6 patient-derived murine xenograft models of ETP-ALL, with profound single-agent efficacy in 5 models. Ruxolitinib treatment decreased peripheral blast counts relative to pre-treatment levels and compared to control (P<0.01) in 5/6 ETP-ALL xenografts, with marked reduction in mean splenic blast counts (P<0.01) in 6/6 samples. Surprisingly, both JAK/STAT pathway activation and ruxolitinib efficacy were independent of the presence of JAK/STAT pathway mutations, raising the possibility that the therapeutic potential of ruxolitinib in ETP-ALL extends beyond those cases with JAK mutations. These findings establish the preclinical in vivo efficacy of ruxolitinib in ETP-ALL, a biologically distinct subtype for which novel therapies are needed.

  Study EGAS00001001146

• Memory-like HCV-specific CD8+ T cells retain a chronic scar after cure of chronic HCV infection

  Chronic hepatitis C virus (HCV) infection is associated with CD8+ T-cell exhaustion characterized by limited effector functions and thus compromised anti-viral activity. Exhausted HCV-specific CD8+ T cells are comprised of memory-like and terminally exhausted CD8+ T-cell subsets. So far, little is not known about the molecular profile and fate of these cells after elimination of chronic antigen stimulation by direct acting antiviral therapy (DAA). Here, we report an antigen-driven molecular core signature underlying exhausted CD8+ T-cell subset heterogeneity in chronic viral infection with a progenitor/progeny relationship of memory-like and terminally exhausted HCV-specific CD8+ T cells via an intermediate stage. Furthermore, transcriptional profiling reveals that the memory-like cells remain after DAA-mediated cure while terminally exhausted HCV-specific CD8+ T-cell subsets are lost. Thus, the memory polarization of the overall HCV-specific CD8+ T-cell response after cure does not result from re-differentiation of exhausted T cells. Consequently, antigen elimination has little impact on the exhausted core signature of memory-like CD8+ T cells that remains clearly different from bona fide T-cell memory. These results identify a molecular signature of T-cell exhaustion that is imprinted like a chronic scar in HCV-specific CD8+ T cells even after HCV cure, highlighting the requirement of re-programming to elicit full effector potential of exhausted T cells.

  Study EGAS00001004538

• Assessing mitochondrial bioenergetics in coronary artery disease: A translational left ventricular tissue study in humans (The AMBITION study).

  Severe or recurrent myocardial ischemia can lead to long-term left ventricular (LV) dysfunction and heart failure in patients with coronary artery disease (CAD). In this study, we assessed for chronic metabolomic and transcriptomic adaptations within LV myocardium of patients with evidence of preoperative inducible ischemia undergoing coronary artery bypass grafting (CABG). During surgery, paired transmural LV biopsies were acquired on the beating heart from a region of inducible ischemia (determined by stress perfusion cardiovascular magnetic resonance), and a remote LV segment. From 33 patients, 63 LV biopsies were acquired on the beating heart during CABG, comparing to analysis of LV samples from 11 donor hearts. The global myocardial ATP/ADP ratio was reduced in CAD patients as compared to donor LV tissue with increased expression of oxidative phosphorylation (OXPHOS) genes encoding the electron transport chain complexes across multiple cell types. Paired analyses of biopsies obtained during CABG from LV segments with or without inducible ischemia revealed no significant difference in the ATP/ADP ratio, broader metabolic profile or expression of ventricular cardiomyocyte genes implicated in OXPHOS. Finally, differential metabolite analysis suggested dysregulation of several intermediates in patients with impaired LVEF; this notably included the tricyclic acid cycle metabolite, succinate. Overall, our results suggest that viable human myocardium in patients with stable CAD has global alterations in bioenergetic and transcriptional profile without large regional differences between areas with or without inducible ischemia.

  Study EGAS00001007351

• Non-coding mutations reveal cancer driver cistromes in luminal breast cancer

  Whole-genome sequencing of primary breast tumors enabled the identification of cancer driver genes and non-coding cancer driver plexuses from somatic mutations. However, differentiating between driver and passenger events among non-coding genetic variants remains a challenge to understand the etiology of cancer and inform the delivery of personalized cancer medicine. Herein, we reveal enrichment of non-coding mutations in cis-regulatory elements that cover a subset of transcription factors linked to tumor progression in luminal breast cancers. Using a cohort of 26 primary luminal ER+PR+ breast tumors, we compiled a catalogue of ~100,000 unique cis-regulatory elements from ATAC-seq data. Integrating this catalogue with somatic mutations from 350 publicly available breast tumor whole genomes, we identified four recurrently mutated individual cis-regulatory elements. By then partitioning the non-coding genome into cistromes, defined as the sum of binding sites for a transcription factor, we uncovered cancer driver cistromes for ten transcription factors, namely CTCF, ELF1, ESR1, FOSL2, FOXA1, FOXM1 GATA3, JUND, TFAP2A, and TFAP2C in luminal breast cancer. Nine of these ten transcription factors were shown to be essential for growth in breast cancer, with four exclusive to the luminal subtype. Collectively, we present a strategy to find cancer driver cistromes relying on quantifying the enrichment of non-coding mutations over cis-regulatory elements concatenated into a functional unit drawn from an accessible chromatin catalogue derived from primary cancer tissues.

  Study EGAS00001005235

• 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

• Germline Mutations and Developmental Mosaicism Underlying EGFR-Mutant Lung Cancer

  We designed this study to examine the etiology of multiple lung tumors in EGFR-mutant non-small cell lung cancer patients who undergo surgical resection. Participants were 52-85 years old never or former smokers, who had at least 2 surgical lung tumor pathology specimens available in the Massachusetts General Hospital biobank, at least one of which had an EGFR mutation by routine clinical genotyping. 10 patients were selected, along with two patients from a family with an inherited EGFR-T790M mutation leading to multiple lung tumors. These patient tumor samples and matched normal lung samples were microdissected to collect DNA.In addition to obtaining clinical histories, we performed whole exome sequencing to evaluate the genetic profile of matched tumor and normal samples. The WES data are available on dbGaP. Our data showed increasing mutational burden and copy number alteration with increasing invasiveness, as compared to normal tissues, for the subset of samples that were assessed for tumor invasiveness. We also observed a range of numbers of shared mutations between tumors in a single patient, indicating different degrees of relatedness between lung tumors. We hope that this resource will help researchers understand non-small cell lung cancer presentations with multiple lung tumors. These data may aid in clinical decision making for such patients.

  Study phs003379

• Single cell RNAseq of stenotic, inflamed and non-inflamed transmural lesions from patients with Crohn's disease

  This dataset contains a gene-cell matrix derived from single-cell RNA sequencing (scRNA-seq) data of ileal tissue from Crohn's disease (CD) patients and colorectal cancer (CRC) patients. It includes: Crohn's Disease Patients: A trio of transmural lesions (stenotic, inflamed, and non-inflamed) from each patient. Colorectal Cancer Patients: Unaffected ileal tissue used as external non-inflamed control. Cell Level Metadata: The dataset includes relevant cell-level metadata such as cell type annotations used in the study. Experimental Details: Platform: 10x Genomics Chromium Single Cell 3' GEX Sequencing: Illumina NovaSeq Processing: Data processed with Cell Ranger software. Resulting count matrices were merged for downstream analysis, including integration and dimensionality reduction. Dataset Composition: Crohn's Disease Patients: 10 patients with 3 samples each (non-inflamed, inflamed, stenotic), totaling 30 samples. Colorectal Cancer Patients: 5 patients with 1 sample each of unaffected tissue, totaling 5 samples. Data Provided: Merged Raw Count Matrix: The final merged raw count matrix used for downstream analysis. Cell Metadata File: Contains details of sample, tissue, and patient for each cell in the count matrix. Barcodes File: Indicate each cell barcode which also encodes the sample, tissue, and patient details for each cell. CD.S_Inf: Stenotic Corhn's disease inflamed samples CD.S_Sten: Stenotic CD patient stenosis sample CD.S_Prox: Stenotic CD Patient - proximal non-inflamed sample CC.C_Prox: CRC Patient proximal unaffected sample eg: A barcode 'CC.C_1_Prox_AAGTCGTAGACCCTTA' indicates CRC Patient unaffected proximal sampe from CRC Patient no.1 and the nucleic acid sequence indicate a unique cell from this sample. Total Samples: Crohn's Disease (CD) Patients: 30 samples Colorectal Cancer (CRC) Patients: 5 samples Patient_no Sample Sample_type 1 CC.C_1 CC.C_1_Prox CC.C_Prox 2 CD.S_1 CD.S_1_Prox CD.S_Prox 3 CD.S_1 CD.S_1_Infl CD.S_Infl 4 CD.S_1 CD.S_1_Sten CD.S_Sten 5 CC.C_2 CC.C_2_Prox CC.C_Prox 6 CD.S_2 CD.S_2_Prox CD.S_Prox 7 CD.S_2 CD.S_2_Infl CD.S_Infl 8 CD.S_2 CD.S_2_Sten CD.S_Sten 9 CC.C_3 CC.C_3_Prox CC.C_Prox 10 CC.C_4 CC.C_4_Prox CC.C_Prox 11 CD.S_3 CD.S_3_Prox CD.S_Prox 12 CD.S_3 CD.S_3_Infl CD.S_Infl 13 CD.S_3 CD.S_3_Sten CD.S_Sten 14 CD.S_4 CD.S_4_Prox CD.S_Prox 15 CD.S_4 CD.S_4_Infl CD.S_Infl 16 CD.S_4 CD.S_4_Sten CD.S_Sten 17 CC.C_5 CC.C_5_Prox CC.C_Prox 18 CD.S_5 CD.S_5_Prox CD.S_Prox 19 CD.S_5 CD.S_5_Infl CD.S_Infl 20 CD.S_5 CD.S_5_Sten CD.S_Sten 21 CD.S_6 CD.S_6_Prox CD.S_Prox 22 CD.S_6 CD.S_6_Infl CD.S_Infl 23 CD.S_6 CD.S_6_Sten CD.S_Sten 24 CD.S_7 CD.S_7_Prox CD.S_Prox 25 CD.S_7 CD.S_7_Infl CD.S_Infl 26 CD.S_7 CD.S_7_Sten CD.S_Sten 27 CD.S_8 CD.S_8_Prox CD.S_Prox 28 CD.S_8 CD.S_8_Infl CD.S_Infl 29 CD.S_8 CD.S_8_Sten CD.S_Sten 30 CD.S_9 CD.S_9_Prox CD.S_Prox 31 CD.S_9 CD.S_9_Infl CD.S_Infl 32 CD.S_9 CD.S_9_Sten CD.S_Sten 33 CD.S_10 CD.S_10_Prox CD.S_Prox 34 CD.S_10 CD.S_10_Infl CD.S_Infl 35 CD.S_10 CD.S_10_Sten CD.S_Sten

  Dataset EGAD50000000559

• Allele Balance Bias Identifies Systematic Genotyping Errors and False Disease Associations

  In recent years, Next Generation Sequencing (NGS) has become a cornerstone of clinical genetics and diagnostics. Many clinical applications require high precision, especially if rare events such as somatic mutations in cancer or genetic variants causing rare diseases need to be identified. Although random sequencing errors can be modeled statistically and deep sequencing minimizes their impact, systematic errors remain a problem even at high depth of coverage. Understanding their source is crucial to increase precision of clinical NGS applications. In this work, we studied the relation between recurrent biases in allele balance (AB), systematic errors and false positive variant calls across a large cohort of human samples analyzed by whole exome sequencing (WES). We have modeled the allele balance distribution for biallelic genotypes in 987 WES samples in order to identify positions recurrently deviating significantly from the expectation, a phenomenon we termed allele balance bias (ABB). Furthermore, we have developed a genotype callability score based on ABB for all positions of the human exome, which detects false positive variant calls that passed state-of-the-art filters. Finally, we demonstrate the use of ABB for detection of false associations proposed by rare variant association studies (RVAS).

  Study EGAS00001003027

• Genome-wide DNA-methylation assessment by MethylCap-seq and Infinium HumanMethylation450 BeadChips: an independent large-scale comparison

  DNA-methylation is an important epigenetic feature in health and disease. Two cost-efficient genome-scale methodologies to assess DNA-methylation are MethylCap-seq and Illumina's Infinium HumanMethylation450 BeadChips (HM450). However, objective information regarding the best-suited methodology for a specific research question is scant. Therefore, we performed a large-scale evaluation on a set of 70 brain tissue samples obtained from 65 glioblastoma and 5 non-tumoral brain tissues, using a gold standard free Bayesian modeling procedure. While conditional specificity was adequate for both approaches, conditional sensitivity was systematically higher for HM450. Also the genome-wide characteristics were compared, revealing that the HM450 probes assess less than 10% of the regions identified as methylated by MethylCap-seq. Hence the latter method may detect more potentially relevant DNA-methylation, defined by either functional location or previously reported differentially methylated candidate regions. Our results therefore indicate that – at least for the tissue under study - both methodologies are complementary, with a higher sensitivity for HM450, but a far larger genome-wide coverage for MethylCap-seq. Note that here only the relevant MethylCap-seq data is deposited, for the HM450 data we refer to GEO (GSE60274).

  Study EGAS00001001191

• Bisulfite-converted duplexes for the strand-specific detection and quantification of rare mutations

  The identification of mutations that are present at low frequencies in clinical samples is an essential component of precision medicine. The development of molecular barcoding for next generation sequencing has greatly enhanced the sensitivity of detecting such mutations by massively parallel sequencing. However, further improvements in specificity would be useful for a variety of applications. We herein describe a technology (BiSeqS) that can increase the specificity of sequencing by at least two orders of magnitude over and above that achieved with molecular barcoding and can be applied to any massively parallel sequencing instrument. BiSeqS employs bisulfite treatment to distinguish the two strands of molecularly barcoded DNA; its specificity arises from the requirement for the same mutation to be identified in both strands. Because no library preparation is required, the technology permits very efficient use of the template DNA as well as sequence reads, which are nearly all confined to the amplicons of interest. Such efficiency is critical for clinical samples, such as plasma, in which only tiny amounts of DNA are often available. We show here that BiSeqS can be applied to evaluate transversions, as well as small insertions or deletions, and can reliably detect one mutation among >10,000 wild type molecules.

  Study EGAS00001002406

• MutWP1: CRUK Grand Challenge Mutographs of Cancer: Oesophageal adenocarcinoma

  The Mutographs project aims to advance our understanding of the causes of cancer through studies of mutational signatures. Led by Mike Stratton, together with Paul Brennan, Ludmil Alexandrov, Allan Balmain, David Phillips and Peter Campbell, this large-scale international research endeavour was awarded a Cancer Research UK Grand Challenge. Different patterns of somatic mutation are generated by the different environmental, lifestyle and genetic factors that cause cancer, many of them are still unknown. Within Mutographs, the International Agency for Research on Cancer is coordinating the recruitment of 5000 individuals with cancer (colorectal, renal, pancreatic, oesophageal adenocarcinoma or oesophageal squamous cancers) across 5 continents to explore whether different mutational signatures explain marked variation in incidence. In brief, through an international network of collaborators around the world, biological materials are collected, along with demographic, histological, clinical and questionnaire data. Whole genome sequences of tumour-germline DNA pairs are generated at the Wellcome Trust Sanger Institute (40X and 20X depth respectively). Somatic mutational signatures are subsequently extracted by non-negative matrix factorisation methods and correlated with risk factors data. Through an enhanced understanding of cancer aetiology, Mutographs unprecedented effort is anticipated to outline modifiable risk factors, lead to new approaches to prevent cancer, and provide opportunities to empower early detection, refine high-risk groups and contribute to further therapeutic development. This dataset contains all the data available for this study on 2021-09-27.

  Dataset EGAD00001006083

• Polyclonal selection of immune checkpoint mutations in thyroid autoimmunity - ExomeNanoSeq

  Our immune system contains multiple tolerance checkpoints to prevent the activation of self-reactive lymphocytes. How some lymphocytes escape these constraints to cause autoimmune disease remains poorly understood. A long-standing hypothesis in autoimmunity posits that somatic mutations in immune regulatory genes may enable self-reactive lymphocytes to bypass tolerance checkpoints. However, testing this hypothesis has proved challenging due to technical limitations in detecting somatic mutations in polyclonal cell populations. Here, we use deep whole-exome and targeted NanoSeq, a highly accurate single-molecule DNA sequencing protocol, to comprehensively search for driver mutations in autoimmune thyroid disease. This revealed a remarkably high number of B cell clones convergently acquiring loss-of-function somatic mutations in key immune checkpoint genes TNFRSF14 (also known as HVEM) and CD274 (encoding PD-L1), as well as less frequent driver mutations in a diversity of other immune genes. In highly inflamed biopsies, we detected tens to hundreds of independent immune-checkpoint mutant clones. Laser capture microdissection, methylation sequencing, spatial transcriptomics, immunohistochemistry and single-nucleus DNA sequencing localised these mutations to non-naive B cells and revealed frequent co-occurrence of drivers in single cells. We found widespread TNFRSF14 biallelic loss in mutant B cells, and several clones with as many as 4-6 driver mutations. Whilst each clone accounts for a small proportion of cells (typically <1%), the myriad mutant clones in each donor collectively amounted to a substantial fraction of B cells harbouring one or more driver mutations. Our results support the hypothesis that somatic mutations in autoimmune lymphocytes may allow them to escape tolerance constraints through a polyclonal cascade of somatic evolution. These findings provide new insights into the molecular basis of autoimmune disease and suggest novel diagnostic and therapeutic avenues.

  Dataset EGAD00001016058

• Polyclonal selection of immune checkpoint mutations in thyroid autoimmunity - TargetedNanoSeq

  Our immune system contains multiple tolerance checkpoints to prevent the activation of self-reactive lymphocytes. How some lymphocytes escape these constraints to cause autoimmune disease remains poorly understood. A long-standing hypothesis in autoimmunity posits that somatic mutations in immune regulatory genes may enable self-reactive lymphocytes to bypass tolerance checkpoints. However, testing this hypothesis has proved challenging due to technical limitations in detecting somatic mutations in polyclonal cell populations. Here, we use deep whole-exome and targeted NanoSeq, a highly accurate single-molecule DNA sequencing protocol, to comprehensively search for driver mutations in autoimmune thyroid disease. This revealed a remarkably high number of B cell clones convergently acquiring loss-of-function somatic mutations in key immune checkpoint genes TNFRSF14 (also known as HVEM) and CD274 (encoding PD-L1), as well as less frequent driver mutations in a diversity of other immune genes. In highly inflamed biopsies, we detected tens to hundreds of independent immune-checkpoint mutant clones. Laser capture microdissection, methylation sequencing, spatial transcriptomics, immunohistochemistry and single-nucleus DNA sequencing localised these mutations to non-naive B cells and revealed frequent co-occurrence of drivers in single cells. We found widespread TNFRSF14 biallelic loss in mutant B cells, and several clones with as many as 4-6 driver mutations. Whilst each clone accounts for a small proportion of cells (typically <1%), the myriad mutant clones in each donor collectively amounted to a substantial fraction of B cells harbouring one or more driver mutations. Our results support the hypothesis that somatic mutations in autoimmune lymphocytes may allow them to escape tolerance constraints through a polyclonal cascade of somatic evolution. These findings provide new insights into the molecular basis of autoimmune disease and suggest novel diagnostic and therapeutic avenues.

  Dataset EGAD00001016059

• Pathology and tumor biology DAC

  Dac EGAC00001003221

• CDH Asian Head and Neck Angiosarcoma

  Dac EGAC00001003145

• Relapsed and Primary Neuroblastoma DAC

  Dac EGAC00001000373

• Illumina - Population and Medical Genomics Group

  Dac EGAC00001000686

• ICR_Evolutionary Genomics and Modelling

  Dac EGAC00001001050

• RNAseq intra- and extracranial ECs DAC

  Dac EGAC00001001622

• Gene expression and Cancer

  Dac EGAC00001001772

• Neuroblastoma and cell migration DAC

  Dac EGAC00001001965