17236 results for "free coins in fc 26 Visit Buyfc26coins.com for latest FC 26 coins news..xwWa"

in 29.49 milliseconds.

• Single-Cell Multiomics of the Immune Microenvironment in T-Cell Acute Lymphoblastic Leukemia

  We present single-cell transcriptome and surface protein expression (CITE-seq) data from four healthy donors and fifteen pediatric T cell acute lymphoblastic leukemia (T-ALL) patients at diagnosis and at different treatment timepoints (days 1 – 6 and at time of remission). Mononuclear cells from peripheral blood (PB; longitudinal) or bone marrow (BM; diagnosis only) were isolated and CD45high immune cells and CD45dimCD7+ malignant cells were sorted and subsequently pooled to enrich for immune cells. For comparison,CD45high immune cells from four healthy donors were also sorted. Single-cell sequencing of the transcriptome and surface protein expression (204 antibodies) was performed using the 10x Genomics platform.Multiomics analyses resulted in the identification of a T-ALL subgroup characterized by a remodeled immune microenvironment at initial diagnosis. This immune landscape is dominated by the presence of non-malignant CD4-CD8-TCRab T cells that interact with CXCL16 expressing non-classical monocytes. Leukemia cell intrinsic transcriptional rewiring in these patients is associated with activation of Rap1 signaling.

  Study phs004269

• Spatial predictors of response to immunotherapy in microsatellite stable metastatic colorectal cancer

  Microsatellite stable (MSS) colorectal cancers (CRC) are largely unresponsive to immune checkpoint inhibition (ICI), prompting investigation into strategies to enhance sensitivity. The MAYA trial, which utilized temozolomide (TMZ) in MGMT-silenced MSS mCRC, hypothesized that TMZ-induced hypermutation could sensitize tumors to ICI. This phase II trial met its primary endpoint, demonstrating durable clinical responses with TMZ combined with ipilimumab and nivolumab. To elucidate factors influencing response heterogeneity, we conducted multi-omic spatial profiling of samples from patients who participated in the MAYA trial, including baseline and on-treatment tissue and blood specimens. While increased neoantigen load following TMZ exposure did not consistently predict for deep responses, spatial profiling revealed key determinants. Lymphocyte proportions, particularly CD8+KI67+ cells, within stromal and tumor compartments, along with macrophage composition (CD68+CD163+ cells) at the tumor-stromal interface, were predictive of response. Treatment pressures dynamically altered the tumor microenvironment composition and activated peripheral immune cells. This study is the first to identify spatial predictors of response to this promising novel treatment approach for MSS CRC.

  Study EGAS50000001567

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• BLUEPRINT RNA-seq data for common cells in the haematopoietic lineages, from adult and cord blood samples.

  RNA-seq data for common cells in the haematopoietic lineages, from adult and cord blood samples.

  Study EGAS00001000327

• BLUEPRINT EpiVar ChIP-seq in lineage specifying transcription factors

  The BLUEPRINT project is a large-scale project investigating epigenetic mechanisms involved in blood formation, in health and disease. The human variation workpackage (WP10) of the project seeks to characterize the effect of common sequence variation on the epigenome status of a cell. To do this, the project will use highly purified blood cells to minimise "experimental noise" and therefore enhance the power to discover modest effects. Two peripheral blood cell types, the CD14+CD16- monocyte (an important central orchestrator of adaptive immunity and a bridge between innate and adaptive immunity) and the CD65+CD9- neutrophilic granulocyte (the frontline cell for innate immunity) have been selected for this purpose. The two types of cells will be obtained at high purity from adult blood (AB) of 200 healthy males and females, respectively. Cells will be purified by using already validated and fully operational protocols that are based on density gradient centrifugation of the buffy coat obtained from whole blood, followed by magnetic bead-based purification using monoclonal antibodies against Cluster of Differentiation (CD) lineage-specific cell surface markers. This data set contains functional genomics data for gene expression and chromatin state.

  Dataset EGAD00001004571

• 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&#243;n y de Estudios Avanzados del Instituto Polit&#233;cnico Nacional, Mexico City, Mexico). All participants provided signed informed consent. A total of 1,160 adults (&#8805; 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 &#8805; 25.0, &#8805; 30, and &lt; 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 &#181;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 &#8805; 126 mg/dL, 2HPG &#8805; 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 &#8805; 110 mg/ dL or 2HPG &#8805; 140 mg/dL. Elevated fasting levels of each lipid were defined as plasma TG &#8805; 150 mg/dL, TC &#8805; 200 mg/dL, and LDL &#8805; 130 mg/dL. Fasting HDL &lt; 40 mg/dL in men and &lt; 50 mg/dL in women were designated as low. Hypertension was defined by systolic blood pressure (SBP) &gt; 140 mm Hg, diastolic blood pressure (DBP) &gt; 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

• Smith-Lemli-Opitz Syndrome: A Longitudinal Clinical Study of Patients Receiving Cholesterol Supplementation

  Smith-Lemli-Opitz syndrome (SLOS) is a disorder of cholesterol production by the body. It is caused by changes in the DHCR7 gene, which is the blueprint for an enzyme called 7-dehydrocholesterol- delta7-reductase. This enzyme is necessary for the production of cholesterol by all cells in the body. People with SLOS often have malformations of major organs, slow growth, feeding difficulties and intellectual disability or learning problems. Because patients with SLOS cannot make enough cholesterol, it has been proposed that cholesterol supplementation (either with egg yolk or liquid suspensions of cholesterol) could help improve the symptoms of the disease. However, despite the widespread use of cholesterol supplementation, it is still not known whether it works or not. The study will try to provide an answer to this question by studying the disease and its progression while patients are receiving cholesterol. The clinical features of SLOS are thought to be related to low cholesterol and buildup of toxic cholesterol precursors (substances from which cholesterol is formed). But how exactly low cholesterol and toxic precursors contribute to the disease is poorly understood. This knowledge is critically important because it should help discover new therapeutic targets and develop treatments of the disease in the long run. The study will try to fill this gap with a comprehensive clinical and biochemical testing of the study participants over the course of several years. Last, a limitation of previous SLOS research studies has been their low number of participants. This is understandable because SLOS is a rare diseases and few research groups are working on it. However, in order to fully understand the disease, researchers need to study as many patients as possible. This study is unique in that it is run by a network of several highly specialized clinical research sites across the country. Having several sites involved increases the researcher&#39;s ability to recruit and study large number of patients, and centralize patients&#39; information in a comprehensive SLOS clinical registry. This registry will be key to identify markers for diagnostic testing, screening and measuring outcomes in future studies of treatment. The purpose of this study is to learn as much as possible about Smith-Lemli-Opitz Syndrome (SLOS) by following a large group of affected children and adults over time. In this study, we will measure cholesterol and other similar chemicals in blood and urine, evaluate development and behavior, do limited medical evaluation, and carry out brain imaging studies.This study will help researchers: learn more about what causes SLOS and how SLOS changes with age, note differences in features of SLOS among those affected, evaluate the effect of giving extra cholesterol in this condition, and develop ways to evaluate whether treatments developed in the future will be helpful.

  Study phs001430

• Rare Diseases Clinical Research Network (RDCRN) Vasculitis Clinical Research Consortium (VCRC) Longitudinal Protocol for Polyarteritis Nodosa

  The development and validation of accurate biological markers and predictors of disease activity and outcome in Polyarteritis Nodosa (PAN), a form a idiopathic vasculitis, would have a major positive impact on the clinical care of patients with this rare disease, be an important advance in the design of clinical trials and feasibility of new drug development, and provide important insight into the pathogenesis of this condition. Current measures of disease activity, including erythrocyte sedimentation rate (ESR) and C-reactive protein (CRP), while helpful in selected settings, are mostly considered highly flawed and markers whose poor correlation with disease flares makes them inadequate to help guide therapy. Similarly, ESR and CRP are clearly unhelpful as diagnostic tests for vasculitis. The current state of clinical investigation for vasculitis relies heavily upon determination of disease status solely by clinical presentation and investigator opinion. Thus, discovery and validation of more precise markers that quantifiably measure activity, predict disease course, and correlate with an important biological process, would be of great importance. Knowledge to be gained from this study could potentially be highly important. Discovery of effective biomarkers of vasculitis and assessment of long term disease course and complications by the collection of clinical and diagnostic imaging studies proposed could lead to better care and less toxic treatment regimens. Furthermore, insight into the pathophysiology of vasculitis could be gained and this might lead to better treatments and improved outcomes in terms of reduction of vascular and treatment related complications. Ideally, excellent biomarkers reflect a sophisticated understanding of the pathophysiology of a disease.

  Study phs000590

• Parent-of-origin dependent DNA methylation and gene expression in the human placenta

  DNA methylation is globally reprogrammed after fertilization and the parental genomes have similar DNA methylation profiles after implantation except at the germline differentially methylated regions (gDMRs). We, and others, have previously shown that there are a large number of transient gDMRs in human blastocysts, whose differential methylation is lost in embryonic tissues after implantation. In this study we employed genome-wide allelic DNA methylation analyses of highly purified trophoblast cells from human placentas. ~40% of the transient-in-embryo gDMRs maintained their parent-of-origin-dependent biased allelic methylation. RNA sequencing-based allelic expression analyses revealed that some of the placental-specific gDMRs were associated with novel imprinted genes. This approach identified the first examples of X-linked gDMRs specific to the placenta. These findings highlight the unique regulation of allelic DNA methylation in the human placenta, which is important for understanding normal placental development and the pathogenesis of pregnancy complications.

  Study JGAS000038

• Divergence between high metastatic tumor burden and low circulating tumor DNA concentration in metastasized breast cancer

  Circulating tumor DNA (ctDNA) was reported to represent a highly sensitive biomarker of metastatic cancer disease directly reflecting tumor burden and dynamics. Here we investigated the role of ctDNA in patients with metastatic breast cancer. In an index patient with more than 100,000 circulating tumor cells (CTCs) in serial blood analyses, whole genome, exome, or targeted deep sequencing of the primary tumor, metastases, and 551 CTCs were consistent with a genetically homogeneous cancer. However, the allele fractions (AFs) of ctDNA were only 2-3% in each analysis, which did neither reflect the tumor burden nor the dynamics of this progressive disease by far. Indeed, plasma analyses of 71 further patients demonstrated highly variable AFs of mutant fragments, which frequently did not correspond to the tumor burden. These results provide insights into mechanisms involved in CTC and ctDNA release into the circulation and have important implications for diagnostic tests based on liquid biopsies.

  Study EGAS00001000625