Search Results - EGA European Genome-Phenome Archive

High-depth whole genome sequencing of 26 premalignant breast lesions

Ductal carcinoma in situ (DCIS) is a non-obligate precursor lesion of breast cancer, representing 20-25% of newly diagnosed breast cancer lesions. It is currently not possible to predict which DCIS patients will progress to invasive breast cancer. The samples deposited here are part of a larger study using high-depth whole-genome sequencing (WGS) to investigate the somatic mutation genomic landscape of DCIS. Comprehensive evaluation of DCIS genomes aims to uncover biological insights into breast cancer progression and potential opportunities to stratify DCIS patients for personalised treatment options or active surveillance. Due to specific restrictions imposed by the ethical approval at sample collection, the use of the germline data is restricted to filtering of somatic mutation calls only and cannot be used outside this purpose.

Study EGAS50000001559

Discover Cancer Image Europe, the first release of the EUCAIM platform to fuel cancer research and data sharing

The EUCAIM consortium and the European Commission have announced the release of Cancer Image Europe, a platform to fuel collaborative innovation and data sharing across Europe. This constitutes a major milestone in EUCAIM's development and an exciting step towards achieving the project's vision and goals. The platform aims to accelerate the pace of AI development and other data-intensive cancer research activities, constituting the basis for a fully-fledged infrastructure for sharing, reusing, and exploiting cancer imaging data, especially using AI techniques. A platform paving the way for the future of cancer diagnosis and treatment Cancer Image Europe brings benefits to researchers, clinicians, and AI innovators across Europe as it addresses the fragmentation of existing cancer image repositories. The platform gathers a public catalogue of cancer imaging datasets from the repositories of the EU-funded AI for Health Imaging projects. A distributed Atlas of Cancer Imaging with over 60 million anonymised cancer image data from over 100,000 patients will be established as part of future updates. The first version of Cancer Image Europe also includes a public catalogue of cancer imaging datasets, a federated searching tool to understand the information available in the federated providers, and full integration with Life Science Login. Moreover, it reuses and adds value to key components of EU-funded research projects and infrastructure in the field of cancer. The Public Catalogue When we talk about data re-use, data discovery is key. The EUCAIM public catalogue is the result of a systematic and collaborative process to which the EGA-CRG has actively contributed. This browsing interface gathers the metadata of the available cancer imaging datasets. This descriptive information will help researchers in their data retrieval. Our contribution to the Public Catalogue comes from our experience gained in the deployment of our federated network, the Federated EGA (FEGA), and as partners in projects such as EuCanImage (AI4HI initiative), in which we worked on the definition of common data models, ontologies and data standards. The EUCAIM Project EUCAIM is a cornerstone of the European Commission-initiated European Cancer Imaging Initiative, a flagship of the Europe's Beating Cancer Plan, which aims to foster innovation and deployment of digital technologies in cancer treatment and care, to achieve more precise and faster clinical decision-making, diagnostics, treatments, and predictive medicine for cancer patients. For more information about the first release of the Cancer Image Europe platform and the EUCAIM project, please visit cancerimage.eu.

Blog discover-cancer-image-europe

Germline RUNX1 Variation and Predisposition to Childhood Acute Lymphoblastic

Somatic mutations of RUNX1, which encodes the myeloid and lymphoid transcriptional factor RUNX1, are common in both B- and T- acute lymphoid leukemia (ALL) and are associated with poor prognosis of T-ALL. However, there has been no comprehensive investigation of the pattern or prevalence of RUNX1 germline mutation in both B- and T-ALL. Here we report germline RUNX1 variants in 1.23% of B-ALL and 2.11% of T-ALL, identifying 31 unique variants in 62 B-ALL and 18 unique variants in 26 T-ALL children. The majority of frameshift and nonsense variants affected RUNX1 function in transcriptional regulation, hematopoiesis, and cellular proliferation. We identified JAK3 as the most frequent somatic mutation in T-ALL with RUNX1 variants. These results not only identify RUNX1 as a leukemia predisposition gene but also further underline the importance of germline genetic variants to the development of ALL

Dataset EGAD00001007793

IMCISION RNAseq

RNA sequencing of 32 primary head and neck squamous cell carcinoma (HNSCC) samples prior to treatment with neoadjuvant anti-PD-1 (n=6) or anti-PD-1 + anti-CTLA-4 (n=26) immunotherapy, and 30 paired on-treatment HNSCC samples (i.e. after neoadjuvant immunotherapy). RNA quantity used: 10ng. Library Preparation Kit: SMART Stranded Total RNA Seq Kit (Takara). Sequencing parameters: NovaSeq 6000, 2x 100 bp. File type: fastQ

Dataset EGAD00001008127

PCGP Ph-like ALL

Background: BCR-ABL1-like, or Ph-like acute lymphoblastic leukemia is characterized by a gene expression profile similar to BCR-ABL1 positive ALL, genetic alterations of lymphoid transcription factor genes, and poor outcome. Sequencing of small numbers of Ph-like ALL cases has identified genetic alterations activating kinase signaling suggesting Ph-like ALL may be amenable to treatment with tyrosine kinase inhibitors. However, the spectrum of genetic alterations in childhood and adult Ph-like ALL is incompletely understood. Methods: We performed genomic profiling of 1736 B-ALL cases and next-generation sequencing for 160 Ph-like cases. We examined the functional effects of chimeric fusion proteins in mouse cell lines. Results: The frequency of Ph-like ALL rose from 11% in children to 26% in young adults, and was associated with very poor outcome. Kinase-activating alterations were identified in 90% of Ph-like cases, most commonly fusions involving 10 kinase or cytokine receptor genes (ABL1, ABL2, CRLF2, CSF1R, EPOR, JAK2, NTRK3, PDGFRB, PTK2B and TYK2), and mutations involving FLT3, IL7R and SH2B3. Expression of ABL1, ABL2, CSF1R and JAK2 fusions resulted in cytokine-independent proliferation of cell lines and activation of pSTAT5. Cells expressing ABL1, ABL2, CSF1R and PDGFRB fusions were sensitive to dasatinib, and JAK2 fusions to ruxolitinib. Conclusions: Ph-like ALL is characterized by a diverse range of genomic alterations that converge on a limited number of kinase signaling pathways amenable to inhibition with currently available tyrosine kinase inhibitors. Trials identifying Ph-like ALL and testing the efficacy of tyrosine kinase inhibitor therapy are warranted

Study EGAS00001000654

NHLBI TOPMed: The Cleveland Family Study (CFS)

The Cleveland Family Study (CFS) is one cohort involved in the WGS project. The CFS was designed to provide fundamental epidemiological data on genetic and non-genetic risk factors for sleep disordered breathing (SDB). In brief, the CFS is a family-based study that enrolled a total of 2284 individuals from 361 families between 1990 and 2006. The sample was selected by identifying affected probands who had laboratory diagnosed obstructive sleep apnea. All first degree relatives, spouses and available second degree relatives of affected probands were studied. In addition, during the first 5 study years, neighborhood control families were identified through a neighborhood proband, and his/her spouses and first degree relatives. Each exam, occurring at approximately 4 year intervals, included new enrollment as well as follow up exams for previously enrolled subjects. For the first three visits, data, including an overnight sleep study, were collected in the participants' homes while the last visit occurred in a general clinical research center (GCRC). Phenotypic characterization of the entire cohort included overnight sleep apnea studies, blood pressure, spirometry, anthropometry and questionnaires. The GCRC exam (n=735 selected individuals) included more comprehensive phenotype data on a focused subsample of the larger cohort, to permit linking SDB phenotypes with cardio-metabolic phenotypes, with an interest in identifying genetic loci that are associated with these related phenotypes. In this last round of data collection, a subset of 735 individuals was selected based on expected genetic informativity by choosing pedigrees where siblings had extremes of the apnea hypopnea index (AHI). Participants underwent detailed phenotyping including laboratory polysomnography (PSG), ECG, spirometry, nasal and oral acoustic reflectometry, vigilance testing, and blood and urine collection before and after sleep and after an oral glucose tolerance test. A wide range of biochemical measures of inflammation and metabolism were assayed by a Core Laboratory at the University of Vermont. 994 individuals were sequenced as part of TOPMed Phase 1, including 507 African-Americans and 487 European-Americans. Among the sequenced individuals, 156 were probands with diagnosed sleep apnea, an additional 706 were members of families with probands, and 132 were from neighborhood control families. 298 individuals were sequenced as part of TOPMed Phase 3.5, including 169 African-Americans and 129 European-Americans. Among the newly sequenced individuals, 33 were probands with diagnosed sleep apnea, an additional 214 were members of families with probands, and 51 were from neighborhood control families. Please note: Phenotype and pedigree data are available through "NHLBI Cleveland Family Study (CFS) Candidate Gene Association Resource (CARe)", phs000284.

Study phs000954

Everything you need to know about Federated EGA Affiliates: Q&A

Addressing common questions about Federated EGA (FEGA) Affiliates and providing answers. FEGA Affiliates have recently been defined as the third tier within the newly approved “Federated EGA Structure and Organisation” document, alongside Central EGA (CEGA) and the FEGA Nodes. In this blog post, we aim to answer the questions that may arise on this topic. For more general information about FEGA Affiliates, you can refer to this blog post. Let's now start with the questions and answers! What is the difference between a FEGA Affiliate and a FEGA Node? FEGA Nodes A FEGA Node is a national-level service that accepts submissions and provides archiving and access services within a single country's jurisdiction. Nodes provide end-to-end services for submitters in that jurisdiction, including submission support, processing, permissions management, and distribution. FEGA Affiliates A FEGA Affiliate is not a national submission service. Instead, it archives data from its own legal entity and/or selected partner institutions (for example, consortium partners). Affiliates are designed for organisations and consortia that need to keep data stewardship and access decisions within their own governance model, while still enabling discovery through the broader FEGA ecosystem. What do Affiliates commit to? Here is a practical checklist of the core expectations for a FEGA Affiliate. FEGA Affiliate checklist Discovery and metadata Submit non-personal metadata to CEGA to obtain EGA accessions and enable discovery (with metadata validation handled by the CEGA Helpdesk). Operations and resilience Maintain a data storage system and a defined backup/recovery approach. Ensure operational capacity (personnel and infrastructure) to deliver Affiliate services. Maintain systems and practices that support local data security and align with EGA best-practices. Access and user support Provide data distribution or access (e.g in a trusted research environment) to authorised users to datasets hosted at the Affiliate. Provide permissions management for datasets archived by the Affiliate (the CEGA DAC (Data Access Committee) Portal is always at your disposal to use). Provide a minimal helpdesk with sufficient capacity to support relevant DACs and approved users. Membership term Commit to a minimum membership term of four years. Governance and participation (lightweight by design) Affiliates integrate into the FEGA network operationally, but without the committee obligations associated with Nodes. When is becoming an Affiliate the right fit? Consider the Affiliate tier if: You host (or plan to host) controlled-access datasets that must be managed under your organisation’s or consortium’s governance, you want studies to be discoverable through EGA, but need access control and/or distribution to remain local, and you are not aiming to operate a national submission service tier.. What if a FEGA Node already exists in my jurisdiction? We encourage any potential Affiliate to reach out to their national FEGA Node to explore collaboration at the national level. Why? Federated models within a country already exist in FEGA, where a national Node operates like a Central EGA for their country. FEGA Nodes can also represent the interests of any Affiliates within their jurisdiction at the FEGA Committees. FEGA Nodes have experience and can support you on your FEGA journey. Ready to join as a FEGA Affiliate? We’re excited to open this formally defined pathway for organisations and consortia to participate in the federation. If you think the FEGA Affiliate tier fits your needs, start by assessing: Your scope (organisation/consortium-held data rather than public external submissions), Your ability to provide the core services (permissions, distribution/access, helpdesk, monitoring), and Your readiness to submit non-personal metadata to CEGA for accessioning and discovery. To express interest, please contact us here, and we'll help you understand the onboarding steps and how Affiliates integrate into the FEGA network.

Blog fega-affiliates-q&a

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

Clonal selection after gene therapy in sickle cell disease

While gene therapy (GT) provides a potentially curative treatment option for patients with sickle cell disease (SCD), the occurrence of myeloid malignancies in clinical trials has prompted concern. To interrogate potential mechanisms underlying increased cancer risk, we used hematopoietic stem cell (HSC) clonal tracking by whole genome sequencing (WGS) to map the somatic mutation and clonal landscape of 2,592 gene modified as well as unmodified single stem and progenitor cells from six SCD patients undergoing gene therapy (7-26 years old, average 12.7× depth). Pre-GT phylogenetic trees in SCD were highly polyclonal and mutation burdens per cell were elevated in some, but not all, patients. Post-GT, no clonal expansions were identified. However, an increased frequency of driver mutations associated with myeloid neoplasms or clonal hematopoiesis (DNMT3A- and EZH2-mutated clones in particular) were seen in both genetically modified and unmodified cells suggested positive selection of mutant clones during gene therapy. This work sheds light on the mutation landscape and HSC clonal dynamics in gene therapy for SCD and highlights enhanced fitness of some HSCs harboring pre-existing driver mutations following gene therapy. Future studies should define the long-term fate of mutant clones including any contribution to expansions associated with myeloid neoplasms.

Dataset EGAD00001010914

OpACIN-neo – A Multicenter Phase 2 Study to identify the Optimal neo-Adjuvant Combination scheme of Ipilimumab and Nivolumab – Whole exome sequencing

The outcome of patients with macroscopic stage III melanoma is poor. Neoadjuvant treatment with ipilimumab plus nivolumab at the standard dosing schedule induced pathological responses in a high proportion of patients in two small independent early-phase trials. However, toxicity of the standard ipilimumab plus nivolumab dosing schedule was high, preventing its broader clinical use. The aim of the OpACIN-neo study (NCT02977052) to identify a dosing schedule of ipilimumab plus nivolumab that is less toxic but equally effective. 86 patients with macroscopic stage III melanoma were randomised to one of three dosing schedules: arm A, two cycles of ipilimumab 3 mg/kg plus nivolumab 1 mg/kg once every 3 weeks; arm B, two cycles of ipilimumab 1 mg/kg plus nivolumab 3 mg/kg once every 3 weeks; or arm C, two cycles of ipilimumab 3 mg/kg once every 3 weeks directly followed by two cycles of nivolumab 3mg/kg once every 2 weeks. Within the first 12 weeks, grade 3–4 immune-related adverse events were observed in 12 (40%) of 30 patients in group A, six (20%) of 30 in group B, and 13 (50%) of 26 in group C. Pathological responses occurred in 24 (80%) patients in group A, 23 (77%) in group B, and 17 (65%) in group C. The 2-year estimated relapse-free survival was 84% for all patients, 97% for patients achieving a pathologic response and 36% for nonresponders (p<0.001). High tumor mutational burden (TMB) and high interferon-gamma-related gene expression signature score (IFN-γ score) were associated with pathologic response and low risk of relapse; pathologic response rate (pRR) was 100% in patients with high IFN-γ score/high TMB, patients with high IFN-γ score/low TMB or low IFN-γ score/high TMB had pRRs of 91% and 88%; while patients with low IFN-γ score/low TMB had a pRR of only 39%. These data demonstrate long-term benefit in patients with a pathologic response and show the predictive potential of TMB and IFN-γ score.

Study EGAS00001004832

12208 results for "selling my fc coins Visit Buyfc26coins.com for latest FC 26 coins news..XVJT"

in 15.58 milliseconds.