10916 results for "division 1 coins fc 26 Buyfc26coins.com is FC 26 coins official site..AwVj"

in 29.90 milliseconds.

• Diagnostic Genomic Analysis is Prognostic in AYA ALL Patients Treated on a MRD-Stratified Paediatric Protocol

  Background: Over the last decade, next generation sequencing has enabled classification of multiple new recurrent genomic drivers of acute lymphoblastic leukemia (ALL). We provide a comprehensive genomic survey of adolescent and young adult (AYA) patients treated on the Australasian Leukaemia and Lymphoma Group (ALLG) ALL06 study. ALL06 clinical trial described the efficacy and tolerability of AYA ALL patients aged 15-39 years treated on a single minimal residual disease (MRD)-stratified platform. In this study we have taken the ALL06 cohort and retrospectively performed comprehensive genomic analyses assessing response of AYA patients with various genomic subtypes treated with a paediatric approach. Methods: Genomic risk classification of B- and T-ALL patients (n=57) enrolled to the study was based on mRNA-Sequencing, MLPA, immunophenotyping and cytogenetics. Results: Using this approach, 36/40 (90%) B- and 13/17 (76.5%) T-ALL patients were classified according to genomic risk. We have linked outcome data with each patient’s genomic risk and found a strong correlation between adverse genomic risk and MRD at the end of consolidation, translating to inferior overall and relapse free survival. Patients with adverse risk genomics who achieved negative MRD status had improved responses compared to those with persistent MRD. Patients with standard risk genomics had excellent responses regardless of their MRD status. Conclusion: Our data argue strongly for incorporation of a genomic risk classification into future ALL treatment paradigms at the time of diagnosis.

  Study EGAS50000000752

• 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

• Environmental Arsenic and Diabetes Mellitus (Chihuahua Cohort)

  The Chihuahua Cohort was established as part of a larger NIEHS-funded project that used laboratory models (tissue culture and mice) and human subjects to examine the association between exposure to arsenic and diabetes, including identification of mechanisms underlying this association. All procedures involving human subjects were approved by institutional review boards at the University of North Carolina at Chapel Hill and Cinvestav-IPN (Centro de Investigación y de Estudios Avanzados del Instituto Politécnico Nacional, Mexico City, Mexico). All participants provided signed informed consent. A total of 1,160 adults (≥ 18 years old) with a minimum 5-year uninterrupted residency in the Chihuahua study area were recruited between 2008 and 2012. Samples of drinking water were obtained from the participants' households. Data on residency, occupation, drinking-water sources and use, smoking, alcohol consumption, and medical history were recorded by a study questionnaire. Spot urine and fasting venous blood were collected during medical examination that included an oral glucose tolerance test (OGTT) with blood drawn 2 hr after a 75-g glucose dose. Plasma from both fasting and 2-hr blood samples was collected. Body mass index (BMI) of each participant was calculated from body weight and height. BMI cutoffs of ≥ 25.0, ≥ 30, and < 18.5 kg/m2 were used to define overweight, obese, and underweight individuals, respectively. Participants' waist circumference was also measured. Blood pressure was assessed using a manual sphygmomanometer. Three measurements were taken at intervals of at least 1 min, with a 5-min rest before obtaining the first reading; the mean of the last two measurements was used. The concentrations of arsenic in drinking water and arsenic species in urine were measured by hydride generation-atomic absorption spectrometry. The limit of detection for As in water as well as for As species in urine was 0.01 µg As/L. Creatinine concentration in urine was determined using an established colorimetric assay. DNA was isolated from blood for genotyping analysis.The following measures were taken: glucose concentration in fasting blood (FBG) and in blood collected 2 hours into OGTT (2HBG); concentrations of triglycerides, HDL and total cholesterol (TC) in fasting plasma; and LDL was calculated using the Friedewald equation. Diabetes was classified by FPG ≥ 126 mg/dL, 2HPG ≥ 200 mg/dL, or self-reported diabetes diagnosis or medication use (WHO/International Diabetes Federation 2006). Prediabetes was defined as the absence of diabetes with FPG ≥ 110 mg/ dL or 2HPG ≥ 140 mg/dL. Elevated fasting levels of each lipid were defined as plasma TG ≥ 150 mg/dL, TC ≥ 200 mg/dL, and LDL ≥ 130 mg/dL. Fasting HDL < 40 mg/dL in men and < 50 mg/dL in women were designated as low. Hypertension was defined by systolic blood pressure (SBP) > 140 mm Hg, diastolic blood pressure (DBP) > 90 mmHg, or self-reported use of anti-hypertensive medication. Genotyping analysis, which will be available in version 2 of this study, was carried out in a subset of ~600 subjects with focus on enzymes involved in the metabolism of arsenic, including AS3MT, GSTs.All data collected during the medical exams or generated by the above-described chemical and biochemical analysis of water, urine and blood/plasma, as well as results of the genotyping analysis are included in dbGaP. Data generated by metabolomics and epigenetic analyses in small subsets of the Chihuahua cohort are not included, but are available in published articles.

  Study phs002139

• Genome-wide association study for Bladder Cancer Risk

  This study funded by the National Cancer Institute (NCI) involves conducting a genome-wide association study of common genetic variants to identify markers of susceptibility to bladder cancer. This bladder GWAS has led to the discovery of three novel regions in the genome associated with bladder cancer risk. Cases were defined as individuals having histologically confirmed primary carcinoma of the urinary bladder, including carcinoma in situ (ICD-0-2 topography codes C67.0-C67.9 or ICD9 codes 188.1-188.9). Scan data were obtained from two case-control studies carried out in Spain and the United States (specifically, those in the Maine and Vermont components of the New England Bladder Cancer Study) and three prospective cohort studies in Finland and the United States (specifically Alpha-Tocopherol, Beta-Carotene Cancer Prevention Study, Prostate, Lung, Colorectal and Ovarian Cancer Screening Trial, and The American Cancer Society Cancer Prevention Study II Nutrition Cohort). We used data from 591,637 single nucleotide polymorphisms 3,532 affected individuals (cases) and 5,119 controls of European descent and replication including 8382 cases and 48275 controls from 16 studies. In a combined analysis, we identified three new regions associated with bladder cancer on chromosomes 22q13.1, 19q12 and 2q37.1: rs1014971, (P ≈ 8 x 10-12) maps to a non-genic region of chromosome 22q13.1, rs8102137 (P = 2 x 10-11) on maps to CCNE1 and rs11892031 (P = 1 x 10-7) maps to the UGT1A cluster on 2q37.1. We confirmed four previously identified genome-wide associations on chromosomes 3q28, 4p16.3, 8q24.21 and 8q24.3 (Rothman N et al., Nature Genetics, 2010, PMID: 20972438). Through meta-analysis with the MD Anderson Texas Bladder Cancer Study (TXBCS), we also identified a novel susceptibility locus that mapped to a region of 18q12.3, marked by rs7238033 (P = 8.7 x 10(-9); allelic odds ratio 1.20 with 95% CI: 1.13-1.28) and two highly correlated SNPs, rs10775480/rs10853535 (r(2)= 1.00; P = 8.9 x 10(-9); allelic odds ratio 1.16 with 95% CI: 1.10-1.22) (Garcia-Closas M et al, Human Molecular Genetics, 2011) For NCI-GWAS2, we performed genotyping on cases and controls for the New Hampshire component of the New England Bladder Cancer Study (NEBCS-NH). For the majority of new bladder cancer cases, we genotyped only cases from four case-control studies, the Los Angeles Bladder Cancer Study (LABCS), the French Center for Research on Prostate Diseases (CeRePP), the French Bladder Study (FBCS) and the Brescia Bladder Cancer Study (BBCS). We used existing control data from four cohort studies already genotyped and subjected to rigorous quality control metrics: the European Prospective Investigation Into Cancer and Nutrition Study (EPIC), Womens Health Initiative (WHI), Health Professionals Follow-up Study (HPFS), Nurses Health Study (NHS), which have been a part of Cancer Genetic Markers of Susceptibility (CGEMS). Meta-analysis of NCI-GWAS1, NCI-GWAS2 and a previously reported GWAS TXBCS-GWAS along with taqman replication, identified two new loci: rs10936599 on 3q26.2 (P = 4.53 x 10(-9)) and rs907611 on 11p15.5 (P = 4.11 x 10(-8)). Two notable loci were also identified that approached genome-wide statistical significance: rs6104690 on 20p12.2 (P = 7.13 x 10(-7)) and rs4510656 on 6p22.3 (P = 6.98 X 10(-7)); these require further studies for confirmation (Figueroa J et al, Human Molecular Genetics, 2013).

  Study phs000346

• Asthma in the Lives of Families Today (ALOFT)

  Social interactions and the overall psychosocial environment have a demonstrated impact on health, particularly for people living in disadvantaged urban areas. Here we investigated the effect of psychosocial experiences on gene expression in peripheral blood immune cells of 251 children with asthma in Metro Detroit. Participants were included from an ongoing longitudinal study Asthma in the Lives of Families Today (ALOFT; recruited from November 2010-July 2018. The ALOFT project was established to identify the behavioral and biological pathways through which family social environments impact youth with asthma.In version 1 we used RNA-sequencing and a new machine learning approach to identify transcriptional signatures of 19 variables including psychosocial factors, blood cell composition and asthma symptoms. Using longitudinal data collected from a subset of the participants we showed that transcriptional signatures track the longitudinal changes in measured phenotypes. Importantly, we found 169 genes associated with asthma that are regulated by psychosocial factors, and 344 significant gene-environment interactions for gene expression levels. These results demonstrate that immune gene expression mediates the link between negative psychosocial experiences and asthma risk.In version 2, we focused on pubertal development. We identified substantial gene expression changes associated with age and pubertal development. We showed that genetic effects on gene expression change dynamically during pubertal development. Gene expression changes during puberty are correlated with gene expression changes associated with asthma and may explain sex differences in prevalence. Our results show that molecular data used to study the genetics of early onset diseases should consider pubertal development as an important factor that modifies the transcriptome.Version 3 uses single cell RNA-seq to study the dynamics of the transcriptional response to glucocorticoids in activated Peripheral Blood Mononuclear Cells from 96 African American children. We employed novel statistical approaches to calculate a mean-independent measure of gene expression variability and a measure of transcriptional response pseudotime. Using these approaches, we demonstrated that glucocorticoids reverse the effects of immune stimulation on both gene expression mean and variability. Our novel measure of gene expression response dynamics, based on the diagonal linear discriminant analysis, separated individual cells by response status on the basis of their transcriptional profiles and allowed us to identify different dynamic patterns of gene expression along the response pseudotime. We identified genetic variants regulating gene expression mean and variability, including treatment-specific effects, and demonstrated widespread genetic regulation of the transcriptional dynamics of the gene expression response.Version 4 adds scATAC-seq in activated peripheral blood mononuclear cells (PBMC) from 16 children with asthma with phytohemagglutinin (PHA) or lipopolysaccharide (LPS), and treated with dexamethasone (DEX), an anti-inflammatory glucocorticoid. We analyzed changes in chromatin accessibility, measured transcription factor motif activity, and identified treatment and cell-type specific transcription factors that drive changes in both gene expression mean and variability. We observed strong positive linear dependence between motif response and their target gene expression changes, but negative in variability changes. This result suggests that an increase of transcription factor binding tightens the variability of gene expression around the mean. We then annotated genetic variants in chromatin accessibility peaks and response motifs followed by computational fine-mapping of eQTL signals from a pediatric asthma cohort. We found that eQTLs were 5-fold enriched in peaks with response motifs and refined the credible set for 410 asthma risk genes, with 191 having the causal variant in response motifs. These results enhance the understanding of molecular mechanisms for asthma risk variants mediated by gene expression.

  Study phs002182

• Small molecule inhibitors of LOXL synergize with 5-AZA to restore erythropoiesis in myeloid neoplasms

  Objectives: Bone marrow (BM) stroma and microenvironmental factors in the BM milieu of myeloid neoplasms are increasingly being recognized as novel perspective therapeutic targets. Lysyl oxidases (LOX/LOXL) are crucial enzymes that cross-link collagen and contribute to the deposition of aberrant stiff extracellular matrix (ECM) in the BM of patients with myelodysplastic syndromes (MDS) and myeloproliferative neoplasms (MPN). Here, we studied whether inhibition of LOX/LOXL enzymes produced by BM-derived MSCs favors the differentiation of MDS/MPN hematopoietic stem cell and progenitor cells (HPSCs) and enhances the effects of 5-azacytidine (5-AZA). Methods: Primary co-cultures of MSCs and HPSCs were established from n=31 MDS/MPN patients and treated with the pan-LOX/LOXL inhibitor PXS-5505, 5-AZA or the combination of both for 4 days. At the end of co-culture, HSPC differentiation was assessed by CFU assays and flow cytometry. In some of the experiments, MSCs monolayers were pre-treated or not with PXS-5505 for 6 days and decellularized using 20 mM ammonia. Subsequently, autologous HSPCs were cultured on ECM matrices in the presence of 5-AZA or PXS-5505 + 5-AZA combination with or without inhibitors of integrin signaling such as blebbistatin, Y-27632 and αvβ3-integrin blocking antibodies. Patient-derived xenografts (PDX) were established in NSG mice based on intrafemoral co-injection of HSPCs and autologous MSCs. PDX were treated with 3 cycles of 5-AZA (75 mg/m2), PXS-5505 (30 mg/kg on alternate days for the duration of 5-AZA treatment) or combination of both. Results: MSCs of MDS and MPN patients displayed significant overexpression of LOX/LOXL transcripts as compared to healthy age-matched controls. Remarkably, LOX/LOXL inhibition in MSCs/HSPCs co-cultures increased erythroid differentiation of patient HSPCs that had suboptimal or no response to 5-AZA alone. From a total of n=31 advanced stage MDS/MPN patients, n=11 (35.5%) responded to the combination treatment, which was evidenced by a significant increase of CD235a+CD45- erythroid cell production compared to 5-AZA/PXS/untreated arms (p<0.05). Of note, combination treatment with 5-AZA + PXS-5505 facilitated differentiation of CD235+ erythroid progenitors from HSPCs sub-clones with low mutational VAFs. The presence of MSCs was necessary for the effects of the combination treatment and required direct cell contacts between MSCs and HSPCs. Moreover, PXS-5505-mediated alterations of the ECM composition alone were sufficient to induce erythroid differentiation. Inhibition of integrin-mediated signaling using blebbistatin, Y-27632 and αvβ3-integrin antibodies completely abrogated the effects of PXS-5505 induced erythroid differentiation. In vivo, the combination of PXS-5505 + 5-AZA favored erythroid differentiation of HSPCs and confirmed the in-vitro results. The combination treatment of 5-AZA + PXS-5505 induced the greatest reduction of disease burden as assessed by decrease of spleen indexes, total engraftment rates, BM fibrosis and mutational VAF profiles. Conclusions: The combination of 5-AZA + LOX/LOXL inhibitor PXS-5505 in MDS and MPN synergistically restores erythropoietic differentiation of primary HSPCs. The effect is dependent of contact interaction between HSPCs and niche components, such as MSCs and MSCs-derived ECM. Our data propose a strong rationale for a BM niche targeted combination treatment with 5-AZA + PXS-5505 in transfusion dependent MDS and MPN, which will be assessed in forthcoming clinical trials.

  Study EGAS00001006174

• Recurrent DNMT3B gene rearrangements are associated with unfavorable outcome in dicentric (9;20)-positive pediatric BCP-ALL

  The dicentric chromosome dic(9;20)(p11∼13;q11), occurs in 2% of pediatric acute lymphoblastic leukemia (ALL) cases. However, the prognostic significance of the dic(9;20) alterations and the mechanism in which these alterations drive leukemogenesis remains elusive. Our study describes the demographic, clinical, prognostic, and molecular characteristics of the dic(9;20)-positive ALL in a cohort of 57 pediatric BCP-ALL patients. Targeted RNA-seq and Array CGH analysis unraveled heterogeneous breakpoints on chromosomes 9 and 20 and frequent deletions of the IKZF1 gene. Together with the intrinsic susceptibility for deletions in CDKN2A, CDKN2B, and PAX5 genes in the dic(9;20)-positive ALL, these patients are eligible for treatment escalation in the AIEOP-BFM ALL 2017 clinical study. Survival analysis revealed poor 5-year event-free survival (pEFS) of 69% in dic(9;20)-positive ALL cases, compared to BCP-ALL patients enrolled in modern treatment studies. Strikingly, we identified six dic(9;20)-positive cases with rearrangements involving the DNMT3B gene, and poor 5-year pEFS of 25% (SE = 20%), compared to 79% (SE = 9%) for the remaining cohort (P = 0.011). Despite the loss of the methyltransferase domain of the DNMT3B gene in most cases with DNMT3B rearrangements, we did not observe major changes in the global methylation patterns. Differential gene expression analysis of DNMT3B-rearranged ALL unraveled a dysregulation of genes involved in hematopoiesis, lymphocyte maturation, and the PI3K/AKT signaling pathway. After confirmation in an independent cohort, DNMT3B-rearranged ALL cases should be considered high-risk for relapse and treated accordingly. We provide clinical data sets of Array CGH, targeted RNA-seq, total RNA-seq, whole genome bisulfite (WGBS) and whole genome DNA sequencing (WGS) obtained from bone marrow (BM) or peripheral blood (PB) mononuclear cells of 57 pediatric patients with dicentric chromosome dic(9;20) positive Acute lymphocytic leukemia (ALL), from which in 6 cases DNMT3B gene rearrangement was identified. This data is complemented by total RNA-seq and WGBS of samples from 4 additional ALL patients with a t(12;21) translocation and ETV6-RUNX1 gene fusion. DNA was isolated from BM or PB lymphocytes using Qiagen QIAamp DNA Blood Midi Kit to perform i) Array CGH of 58 dic(9;20) positive samples by hybridizing 500ng DNA using a Agilent 400K SurePrint G3 Custom CGH Human Genome Microarray (e-Array design 84704) ii) WGBS of 6 DNMT3B rearrangement positive samples and 4 ETV6-RUNX1 positive samples using Tecan TrueMethyl oxBS-Seq module for library preparation and Illumina NovaSeq 6000 platform to run 2x151 cycles iii) WGS of DNMT3B rearrangement positive samples using Illumina Lotus DNA Library Prep Kit followed by sequencing running 2x160 cycles on an Illumina NovaSeq 6000 platform. RNA was isolated from PB lymphocytes using the PerkinElmer Chemagic 360 instrument, followed by i) targeted RNA-seq of 56 dic(9;20) positive samples prepared using Illumina TruSight RNA Pan-Cancer Panel and sequenced on an Illumina MiSeq platform running 2x75 cycles ii) total RNA-seq of 6 DNMT3B rearrangement positive samples and 4 ETV6-RUNX1 positive samples utilizing TruSeq Stranded Total RNA Library Prep Gold kit and running 2x100 cycles on an Illumina NovaSeq 6000 platform.

  Study EGAS00001007383

• Persistence of circulating tumor DNA in breast cancer patients during neoadjuvant treatment is a significant predictor of poor tumor response

  Purpose:Accurate assessment of response during neoadjuvant systemic treatment (NST) poses a major clinical challenge. Therefore, a minimally-invasive assessment of tumor response based on cell-free circulating tumor DNA (ctDNA) may be beneficial to guide treatment decisions.Experimental Design: We profiled 93 genes in tissue from 193 early breast cancer patients. Patient-specific assays were designed to track ctDNA during NST from 145 patients with available plasma. ctDNA presence and levels were correlated with complete pathological response (pCR) and residual cancer burden (RCB) as well as with clinicopathologic characteristics of the tumor to identify potential proxies for ctDNA release. Moreover, we tested the predictive value of driver events identified in the tumor.Results:At baseline, ctDNA could be detected in 63/145 (43.4%) patients and persisted in 25/63 (39.7%) patients at mid-therapy (MT) and 15/63 (23.8%) patients at the end of treatment. ctDNA detection at MT was significantly associated with higher RCB (OR 0.062, 95% CI 0.01-0.48, P=0.0077). Out of 31 patients with detectable ctDNA at MT, 30 patients (96.8%) were non-responders (RCB II, n=8; RCB III, n=22) and only one patient responded to the treatment (RCB I). Considering all 145 patients with baseline (BL) plasma, none of the patients with RCB 0 and only 6.7% of patients with RCB I had ctDNA detectable at MT, while 30.6% and 29.6% of patients with RCB II/III, respectively, had a positive ctDNA result. Conclusion:Overall, our results demonstrate that the detection and persistence of ctDNA at mid-therapy may have the potential to negatively predict response to neoadjuvant treatment and identify patients who will not achieve pCR or be classified with RCB II/III.

  Study EGAS00001005798

• WGS of cell-free DNA derived from plasma of patients with pediatric sarcoma and healthy controls, and lcWGS/RRBS of matched tumor tissue

  This dataset contains: i) 241 deep (median 12x) whole-genome sequencing profiles of 95 patients with Ewing sarcoma, 31 patients with other pediatric sarcomas, and 22 additional profiles from healthy controls. Sequencing was performed on a NovaSeq 6000 instrument using the NovaSeq S4 2x100 bp configuration. In addition, pilot experiments for 18 cfDNA samples were performed using Illumina HiSeq 2000/2500 machines (2x75 bp configuration). Data is provided as .fastq.gz files (2 files, .R1 and .R2, per sample). i) Low coverage whole-genome-sequencing on 43 tumor biopsy samples from patients with Ewing sarcoma with matched cfDNA samples. The samples were sequenced using a NovaSeq 6000 instrument with the NovaSeq S4 1x100 bp configuration. Data are provided as unmapped (raw) .bam files. iii) Reduced-representation bisulfite sequencing data for 38 tumor biopsy samples from patients with Ewing sarcoma with matched cfDNA samples, and 2 control samples. RRBS libraries were sequenced on Illumina HiSeq 2000/2500 machines. Data are provided as unmapped (raw) .bam files.

  Dataset EGAD00001007080

• ProHealth: Kaiser Permanente Genome-wide Association Study of Prostate Cancer

  A genome-wide association study (GWAS) of prostate cancer (PCa) was conducted in Kaiser Permanente (KP) Northern California health plan members (7,783 cases, 38,595 controls; 80.3% non-Hispanic white, 4.9% African-American, 7.0% East Asian, and 7.8% Latino) [PMID: 26034056]. The data for these members were drawn from three KP cohort studies: Research Program in Genes, Environment and Health (RPGEH) ProHealth, and California Men's Health Study (CMHS) (described further under Study History). Four custom arrays were designed for genotyping, one for each of the four major race-ethnicity groups in the RPGEH cohort: African Americans, East Asians, Latinos, and Non-Hispanic Whites. The number of SNPs and SNP content varied by array, with SNP content designed to maximize the genome-wide coverage of low frequency and more common variants specific to the different race-ethnicity groups, including newly identified SNPs from sequencing projects, and SNPs with established associations with disease phenotypes and risk factors [PMIDs: 21565264, 21903159]. Within the total study cohort, n=34,736 completed a consent which permitted deposition of data to NIH. Genotyping followed the same general procedure described in [PMIDs: 26092718, plus additional quality control (QC) steps for the additional men, in order to control for potential batch and kit effects, described in [PMID: 26034056. Briefly, we first repeated the filters described in [PMID: 26092718] for all four arrays (EUR, LAT, EAS, AFR). Then, on an array-wise basis, we removed SNPs with MAF<0.01, with a call rate<95%, or with Hardy-Weinberg Equilibrium (HWE) p-value in homogeneous groups<1x10ˆ-5. Furthermore, on the EUR array, to adjust for potential kit effect, we conducted a GWAS of kit, and removed those kit associated SNPs with p<1x10ˆ-6; we also re-genotyped each of the new samples (those not genotyped with the original GERA data) with some of the original GERA data, and removed SNPs with >13/1,268 (1%) mismatches. For the AFR array, to adjust potential plate batch issues, we conducted a GWAS of whether an individual was in the original GERA data vs. in the newly genotyped data and removed those batch-associated SNPs with p<0.05 (we used a stronger threshold than that used for the EUR array because there were fewer individuals on the AFR array); we also re-genotyped each of the new samples with the original GERA data and removed SNPs with >2/78 (2.6%). After the QC described above, imputation was performed as described in [PMID: 26034056]. Imputation was performed on an array-wise basis, pre-phasing with SHAPE-IT v2.5 [PMID: 22138821], and imputing from the 1000 Genomes Project October 2014 release as a cosmopolitan reference panel with IMPUTE2 [PMID: 22384356]. In addition to the GWAS described above, a nested exome-wide association study (EWAS) of PCa was also conducted (7,489 cases, 7,323 controls; 78% non-Hispanic white, 9% African-American, 3% East Asian, 6% Latino, 4% Other). A custom EWAS array primarily focused on rare variants was designed for genotyping that complemented the GWAS arrays [PMID: 26034056]. The EWAS array content included missense and loss-of-function mutations, and rare exonic mutations from The Cancer Genome Atlas (TCGA) and dbGaP prostate cancer tumor exomes [PMID: 26544944; PMID: 26544944]. Much of the EWAS array design content overlapped with the probesets on the UK Biobank Affymetrix Axiom array [PMID: 30305743]. Genotyping and QC steps taken to filter out samples exhibiting low quality and variants with low call rates are described in Emami et al., 2020 [biorXiv]. The resulting EWAS array genotypes are provided here.

  Study phs001221