546 results for "pc coins fc 26 Besøk Buyfc26coins.com Fungerte utmerket til mitt Ultimate Team. Kjøpte flere spillere nå..eqwj"

in 11.06 milliseconds.

• Gene Expression and Biomarker Utility in Post-Mortem Samples

  The FAA Functional Genomics Team examined the feasibility of analyzing gene expression profiles using post-mortem brain, lung, muscle, and blood samples collected from aviation accident fatalities, with the goal of validating post-mortem extracted RNA for use in RNA sequencing. We compared the RNA sequencing results obtained from THC-positive and THC-negative samples to determine whether RNA sequencing on samples collected from aviation accident fatalities was possible and if any differences in gene expression associated with THC consumption were detectable post-mortem. The study population included 57 males of indeterminant age who perished in general aviation accidents and for whom post-mortem toxicological testing identified delta-9-THC or its primary or secondary metabolites, as well as negative controls. We determined that RNA sequencing on post-mortem aviation accident fatality samples is possible, and further identified genes showing differential expression in lung and muscle between THC-positive and THC-negative samples. We conclude that post-mortem tissue samples collected from aviation accident fatalities are suitable for gene expression profiling, but caution researchers that such samples have low RNA integrity numbers and some degree of microbial contamination is both probable and to be expected. Raw sequencing files (.fastq) from this study are available in dbGaP.

  Study phs003546

• Stratifying and Targeting Pediatric Medulloblastoma through Genomics

  In this project, genomic analyses of pediatric medulloblastoma samples, obtained through the international medulloblastoma consortium, will be performed. RNA and miRNA expression profiles of 1000 samples, representing all four subgroups (Wnt, Shh, Group C, and D), will be studied to identify novel subtypes within each subgroup. The resulting subtype-specific expression profiles will support the development of reliable and robust biomarkers to more accurately and reliably classify medulloblastomas for treatment in clinical trials. For that purpose, two assays will be developed: an antibody-based immunohistochemical assay and an orthogonal nucleic acid-based hybridization assay. Additional genomic DNA analysis of the 300 high risk subgroup cases will support the discovery of subgroup specific somatic mutations in order to inform current clinical trials of targeted therapies, and to identify genes and pathways already targeted in other diseases. Such therapies could be rapidly transitioned to Phase II trials in medulloblastoma. Furthermore, the discovery of somatic mutations could be used for developing as well as validating specific biomarkers. The project team will also try to identify risk factors that predispose children to this type of cancer.

  Study EGAS00001000273

• The Mutational Landscape of CTCL and Sezary Syndrome

  Sezary syndrome is a leukemic and aggressive form of cutaneous T-cell lymphoma (CTCL) resulting from the malignant transformation of skin-homing central memory CD4+ T cells. To identify new genetic alterations involved in Sezary syndrome and CTCL transformation we performed whole-exome sequencing of tumor-normal sample pairs from 26 Sezary syndrome and 16 CTCL patients. These analyses revealed a distinctive pattern of somatic copy number alterations in Sezary syndrome including highly prevalent recurrent chromosomal deletions involving the TP53, RB1, PTEN, DNMT3A, and CDKN1B tumor suppressor genes. Mutation analysis identified a broad spectrum of somatic mutations involving key genes involved in epigenetic regulation (TET2, CREBBP, MLL3, BRD9, SMARCA4 and CHD3) and signaling, including mutations in MAPK1, BRAF, CARD11 and PRKG1 driving increased MAPK, NFKB and NFAT activity upon T-cell receptor stimulation. Collectively, our findings provide new insights into the genetics of Sezary syndrome and CTCL and support the development of personalized therapies targeting key oncogenically activated signaling pathways for the treatment of these diseases.

  Study phs000994

• Genetics of Glucose Regulation in Gestation and Growth (Gen3G) Cohort - Placenta Transcriptomics RNA Sequencing

  The overarching goals of Genetics of Glucose regulation in Gestation and Growth (Gen3G) are to increase our understanding of biological, environmental, and genetic determinants of glucose regulation during pregnancy and their impact on fetal/child development. Gen3G is a prospective cohort study: we initially recruited 1,024 pregnant women between 2010-2013 at Blood Sampling in Pregnancy Clinic during the first trimester of pregnancy (median 9 weeks of gestation) in Sherbrooke, Québec, Canada. We assessed 898 pregnant women at second trimester (median 26 weeks of gestation), when participants completed a 75g oral glucose tolerance test (OGTT) as clinically indicated for screening of gestational diabetes mellitus (GDM). We collected data for 854 mother-child dyads at delivery (from medical records), in addition to placenta and/or cord blood samples in majority of newborns.The overall goal of the grant that supported data that is included in this dbGaP submission was to discover novel placental factors that regulate glucose metabolism in pregnancy and predict GDM by conducting genome-wide transcriptomics (RNA and miRNA) in carefully collected placenta samples from Gen3G.

  Study phs003151

• Blood-based monitoring of relapsed/refractory cHL patients predict responses to PD-1 blockade treatment

  Hodgkin lymphoma (cHL) patients are uniquely susceptible to treatment with programmed cell death-1 (PD-1) treatment. However, monitoring with FDG-PET/CT, the current response detection standard, is challenging. Here, we address the potential applicability of tissue biomarkers and blood-based biomarkers in PD-1 treated cHL patients. We evaluated 9p24.1/PD-L1/PD-L2 alterations, and expression of PD-L1 and antigen presentation molecules (HLA class I/II) in 9 tissue biopsies of 4 patients. In addition, we assessed circulating tumor DNA (ctDNA), extracellular vesicle associated miRNAs (EV-miRNAs), soluble PD-L1 and serum TARC (sTARC) in 26 longitudinal blood samples of these patients during PD-1 treatment. We found that the predictive power of tissue biomarkers is dependent on the timing of the biopsy . The dynamics of blood-based biomarkers: sTARC, EV-miRNAs and ctDNA corresponded well immunotherapy treatment response. Therefore, blood-based biomarkers are promising monitoring strategies in PD-1 treated cHL patients and should be further explored in clinical trials or observational studies.

  Study EGAS00001005894

• Molecular stratification of endometrioid ovarian carcinoma predicts clinical outcome

  Endometrioid ovarian carcinoma (EnOC) is an under-investigated type of ovarian carcinoma. Here, we report the largest genomic study of EnOCs to date, performing whole exome sequencing of 112 cases following rigorous pathological assessment. High frequencies of mutation were detected in CTNNB1(43%), PIK3CA(43%), ARID1A(36%), PTEN(29%), TP53(26%) and SOX8(19%), a novel target of recurrent mutation in EnOC. POLE and mismatch repair protein-encoding genes were mutated at lower frequency (6%, 18%) with significant co-occurrence. A molecular taxonomy was constructed using a novel algorithm (PRISTINE), identifying clinically distinct EnOC subtypes: TP53m cases demonstrated greater genomic complexity, were frequently FIGO stage III/IV at diagnosis (48%) and incompletely debulked (44%), and demonstrated inferior survival; conversely, CTNNB1m cases demonstrated low complexity and excellent clinical outcome, were predominantly stage I/II at diagnosis (89%) and completely resected (87%). Tumour complexity provides further resolution within the TP53wt/CTNNB1wt group. Moreover, we identify the WNT, MAPK/RAS and PI3K pathways as good candidate targets for molecular therapeutics in EnOC.

  Study EGAS00001004366

• A plasma protein biomarker signature that differentiates acute rheumatic fever from related clinical presentations

  Acute Rheumatic Fever (ARF) is a systemic inflammatory condition triggered by Group A Streptococcus infection, with timely diagnosis critical to prevent Rheumatic Heart Disease. ARF pathogenesis is poorly understood and diagnosis is based on clinical criteria. Here, we compared ARF cases and well-defined controls from two Uganda cohorts. We identified a 5-protein signature that discriminates ARF patients from clinically-similar conditions (receiver operating characteristic-area under the curve (ROC-AUC)=1.0, n=18 definite ARF vs n=9 known alternate diagnosis; ROC-AUC=0.97, n=18 definite ARF vs n=13 unknown alternate diagnosis), which retained very good diagnostic value in a validation cohort (ROC-AUC=0.83 n=26 definite ARF vs n=13 unknown alternate diagnosis). Pathway analysis identified the epithelial-mesenchymal transition pathway as highly-associated with acute ARF, suggesting that tissue damage and repair is central to ARF pathogenesis. Our findings require further validation, yet highlight the potential for proteomics to identify clinically useful diagnostic biomarkers that would revolutionise ARF diagnosis and treatment.

  Study EGAS00001008381

• Paired Biopsy Project: West Coast Dream Team

  This project aims to analyze the paired metastatic biopsy samples from patients with metastatic castration-resistant prostate cancer (mCRPC), collected before the initiation of the first-line androgen receptor signaling inhibitor (ARSI) for mCRPC and after radiographic disease progression on that ARSI, to understand the resistance mechanisms. We generated both whole genome sequencing (WGS) and RNA-seq data on these samples. A majority of these samples have been deposited in the public domain along with prior publications, and this project contains the 16 WGS samples that have not yet been deposited.

  Study EGAS50000000327

• 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

• IMCISION DNAseq

  Whole-exome sequencing of 32 primary head and neck squamous cell carcinoma samples prior to treatment with neoadjuvant anti-PD-1 (n=6) or anti-PD-1 + anti-CTLA-4 (n=26) immunotherapy. DNA quantity used: 50ng. Library Preparation Kit: Twist Human Core Exome Plus (Twist Bioscience). Sequencing parameters: NovaSeq 6000, 2x 100 bp. File type: fastQ.

  Dataset EGAD00001008139