10982 results for "monedas ultimate team FC 26 Visité Buyfc26coins.com. Servicio premium a un precio estándar. Increíble..XLis"

in 20.32 milliseconds.

• WGS datasets of pediatric glioblastoma

  WGS with linked reads of pediatric glioblastoma. For each patient, blood and tumor tissue were sequenced. For two patients, we also provide sequencing data for the blood of their parents.

  Dataset EGAD00001005212

• DIPG WES and RNA-Seq

  We characterised H3K27M-mutant diffuse intrinsic pontine glioma (DIPG, n=21) and RNA-Seq (n=26 DIPG, 12 normal brain)

  Dataset EGAD00001006450

• Genomic Basis of Phenotypic Variability of Complex Disorders

  The 520-kbp deletion on chromosome 16p12.1 is associated with multiple neurodevelopmental outcomes, including intellectual disability/developmental delay (ID/DD), schizophrenia, autism, and epilepsy. This variant is inherited in >95% of cases from carrier parents manifesting neuropsychiatric features, while affected children with the deletion were more likely to carry another large Copy Number Variation (CNV) or rare deleterious mutation elsewhere in the genome, or "second-hits", compared to carrier parents. Thus, while the 16p12.1 deletion confers significant risk for a range of disorders, the ultimate phenotypic trajectory is determined by "second-hit" variants in the genetic background. However, outstanding questions remain about the genetic background in these disorders, including the functional effects of "second-hit" variants towards gene expression or developmental phenotypes, the full spectrum of "second-hit" variants, and the mechanisms driving accumulation of these variants.In version 1, we performed deep clinical phenotyping, whole-genome sequencing (WGS), SNP microarray analysis, and RNA-sequencing of lymphoblastoid cell lines of 32 individuals in five large families with the 16p12.1 deletion. We found that specific classes of rare single-nucleotide and structural variants in coding and non-coding regions contributed towards expression changes in affected children based on their inheritance patterns, including a subset of variants that acted synergistically with the deletion to alter expression. We further found that rare variant-mediated expression changes contribute to specific developmental phenotypes in the carrier children, suggesting a potential genetic mechanism for variable expressivity of the deletion.In version 2, we additionally analyzed genetic and phenotypic data from individuals with 16p12.1 deletion and their spouses to assess the role of assortative mating modulating phenotypic outcomes of the 16p12.1 deletion. We identified significant within- and cross- disorder phenotypic correlations between spouses, but observed no significant genetic correlations between spouses, in line with expectations.

  Study phs002450

• RNA-seq and scRNA/TCR-seq data for publication: "Pharmacological inhibition of nonsense-mediated mRNA decay enhances anti-tumour immunity"

  PDFs RNA-seq and scRNA/TCR-seq data for Pharmacologic inhibition of nonsense-mediated mRNA decay enhances anti-tumour immunity

  Dataset EGAD50000001720

• 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

• Duplex sequencing of 26 genes

  Buccal samples and paired esophageal epithelium were obtained using the three sizes of swabs and endoscopic biopsy, respectively. Forty samples from 10 subjects were analyzed via duplex sequencing. This dataset contains bam files that were mapped to the GRCh37 reference genome.

  Dataset EGAD50000000998

• RNA-seq samples

  Raw FASTQ files obtained by RNA sequencing of tumor samples from patients (age 12-29) with newly diagnosed, recurrent intermediate or high-grade sarcoma.

  Dataset EGAD00001008393

• Somatic mutations in twin breast cancers (2019-04-03)

  The aim of this study is to investigate the somatic mutations in twins with BRCA1/2 negative breast cancer with no strong family history. . This dataset contains all the data available for this study on 2019-04-03.

  Dataset EGAD00001004890

• Next generation sequencing of diffuse intrinsic pontine glioma samples to identify recurrent mutations, variations, and expression patterns to define novel therapies

  Diffuse intrinsic pontine glioma (DIPG) is an extremely rare (~350 cases/year) and universally fatal childhood brain cancer. Standard clinical strategies such as chemotherapy and radiotherapy show only transient improvement in patient condition and result in negligible change in survival, DIPG remains at below 1% survival after 5 years. Prioritization of panobinostat through previous cooperative work resulted in a phase 1 clinical trial. Nonetheless, new therapies for DIPG must be identified to further dramatically change the statistics for DIPG. To identify novel therapy strategies for DIPG, we performed whole exome(16 new samples, 22 previously published samples, 38 in total with 26 matched normal) and RNA deep sequencing (17 new samples, 11 previously published samples) on a cohort of new patient samples. Sequencing results aid in the identification of recurrent mutations/variations and endotypic expression profiling to identify new therapeutic and treatment strategies for DIPG.

  Study phs001526

• Transcriptomic Analysis of Human Hematopoietic Progenitors from Healthy Donors and Bone Marrow Failure Patients

  The purpose of this study was to define transcriptional changes that occur in the rare and heterogeneous bone marrow progenitors that are affected in Shwachman-Diamond Syndrome. Data are reported for four genetically confirmed SDS patients ranging from 11-26 years old, 3 male and 1 female, and four healthy donors ranging from 25-29 years old, 2 male and 2 female. Subjects provided written, informed consent in accordance with the Declaration of Helsinki's Ethical Principles of Medical Research Involving Human Subjects. Single CD34+ cells were purified from fresh bone marrow and cDNA libraries were prepared using the SMARTer Ultra Low RNA Kit (Clontech; pre-2015) or SMART-Seq v4 Ultra Low RNA Kit (Clontech; post-2015). Libraries were sequenced on a HiSeq 2500 Instrument (Illumina, San Diego, CA) to a read depth of ~3 M paired-end, 25 bp reads per single cell. Paired-end reads were mapped to the hg38 human transcriptome (Gencode v24) using STAR v2.4.2a.

  Study phs001845

• PATL2 is a key actor of oocyte maturation whose invalidation causes infertility in women and mice

  The genetic causes of oocyte meiotic deficiency (OMD), a form of primary infertility characterised by the production of immature oocytes, remain largely unexplored. Using whole exome sequencing, we found that 26% of a cohort of 23 subjects with OMD harboured the same homozygous nonsense pathogenic mutation in PATL2, a gene encoding a putative RNA-binding protein. Using Patl2 knockout mice, we confirmed that PATL2 deficiency disturbs oocyte maturation, since oocytes and zygotes exhibit morphological and developmental defects respectively. PATL2's amphibian orthologue is involved in the regulation of oocyte mRNA as a partner of CPEB. However, Patl2's expression profile throughout oocyte development in mice, alongside colocalisation experiments with Cpeb1, Msy2 and Ddx6 (three oocyte RNA-regulators) suggest an original role for Patl2 in Mammals. Accordingly, transcriptomic analysis of oocytes from WT and Patl2-/- animals demonstrated that in the absence of Patl2, expression levels of a select number of highly relevant genes involved in oocyte maturation and early embryonic development are deregulated. In conclusion, PATL2 is a novel actor of mammalian oocyte maturation whose invalidation causes OMD in humans.

  Study EGAS00001002903

• Small‑scale mutations are infrequent as mechanisms of resistance in post‑PARP inhibitor tumour samples in high grade serous ovarian cancer

  Targeted DNA sequencing of high-grade serous ovarian cancer (HGSC) tumour and normal samples from 26 patients. Following target hybrid capture of 63 genes involved in DNA repair and response to treatment with an Agilent SureSelect XT panel, sequencing libraries were generated using the SureSelect XT Low Input Target Enrichment System (Agilent) as per the manufacturer's protocol. Libraries were sequenced on an Illumina NextSeq 500 at the Peter MacCallum Cancer Centre (Melbourne, Australia).

  Study EGAS50000000146

• Long-read whole-genome sequencing of post-mortem sporadic PD cases and non-PD controls using gut tissue

  This study aims to enable in-depth genomic characterization of Parkinson’s disease (PD) by examining single nucleotide polymorphisms, structural variants, and quantitative trait loci. Long-read whole-genome sequencing was performed using the Oxford Nanopore PromethION platform on colon tissue collected post‑mortem from PD patients and non-PD controls. These data contribute high-resolution insights into genomic variation that may affect PD biology. The project is part of Team Voet’s efforts within the ASAP Collaborative Research Network, which promotes resource sharing and accelerates discovery in Parkinson’s disease research.

  Study EGAS50000001689

• Chromatin accessibility in human monocyte differentiation

  This dataset consists of ATAC-seq data from human monocytes, monocyte-derived dendritic cells or monocyte-derived macrophages as well as monocyte-derived cells that were subjected to siRNA treatment targeting TET2, IRF4 and EGR2. In total, it includes 26 samples.

  Dataset EGAD00001006601

• ICGC PCAWG Dataset: ORCA-IN_PCAWG_WGS_BWA

  ICGC PCAWG Dataset for WGS BAM aligned using BWA MEM. Project: ORCA-IN.

  Dataset EGAD00001002120

• Data files for PCGP SJACT RNASEQ

  This dataset contains RNA-Seq files for the SJACT cohort associated with the paper "Genetic landscape of pediatric Adrenocortical Tumor". In this paper, we analyse 37 adrenocortical tumours (ACTs) by whole-genome, whole-exome and/or transcriptome sequencing.

  Dataset EGAD00001002680

• Sequencing of pancreatic cancer primary tumors and metastases

  The extent of heterogeneity of driver gene mutations present in naturally occurring metastases is largely unknown, i.e. treatment-naïve metastatic disease. To address this issue, 60x whole genome sequencing of 26 metastases from 4 patients was carried out. We found that the identical driver gene mutations were present in every metastatic lesion of each patient studied. Passenger gene mutations not known or predicted to have functional consequences accounted for all intratumoral heterogeneity. Even with respect to these passenger gene mutations, the genetic similarity among the founding cells of metastases was markedly higher than that expected for any two cells randomly taken from a normal tissue. The uniformity of driver gene mutations among metastases in the same patient has critical, encouraging implications for the success of future targeted therapies in advanced stage disease.

  Study EGAS00001002186

• Germline RUNX1 Variation and Predisposition to Childhood Acute Lymphoblastic

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

  Study EGAS00001005403

• Multicenter Study of Hydroxyurea (MSH)

  This study aimed to determine whether or not treatment with hydroxyurea titrated to maximum tolerated doses would reduce the frequency of vaso-occlusive (painful) crises by at least 50% in 299 men and women between 18 and 50 years old with a diagnosis of sickle cell anemia by gel electrophoresis conducted by a Core Laboratory. A secondary objective investigated correlations of fetal hemoglobin (HbF) levels and other patient or treatment characteristics with the occurrence of vaso-occlusive (painful) crises, and the effect of treatment on the quality of life.This controlled trial made hydroxyurea the first drug of proven benefit in preventing vaso-occlusive pain crisis and acute chest syndrome caused by sickle cell disease, with additional findings including reduced mortality in adult patients taking hydroxyurea for frequent painful sickle cell episodes after 9 of years follow-up. No significant side-effects of hydroxyurea therapy were noted.Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

  Study phs002348

• Defining Cutaneous Gene Expression Signatures in Juvenile Dermatomyositis

  Skin inflammation in juvenile dermatomyositis (JDM) can signal disease onset or flare up and prevent complete disease remission. Our objective was to evaluate JDM cutaneous expression signatures through tape stripping in both lesional and non-lesional skin and as compared to paired blood. A total of 28 JDM and 20 control (CTL) patients participated in the study. All patients had tape strip sampling of non-lesional (NL) skin at enrollment visit. Within our JDM cohort, paired lesional (L) skin was additionally sampled if rash was present. 16/28 of JDM patients had at least one additional skin sample associated with a follow-up (FU) visit (total number of follow-up samples included = 26 NL and 4 L). We identified a common innate immune signature in both lesional and non-lesional JDM skin. Using unsupervised hierarchical clustering of skin expression data, we distinguished a JDM molecular subgroup characterized by a mitochondrial dysfunction signature. In comparison to blood expression data, we determined that skin may more effectively highlight the JDM subgroup characterized by a mitochondrial dysfunction expression signature. Data available include bulk RNA-sequencing data from tape strips and blood of the JDM and control patients from this study.

  Study phs003884

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• 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

• 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

• 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

• Integrated Personal omics Processing (iPoP) Longitudinal multi-omics profiling of prediabetes

  Type 2 diabetes mellitus (T2D) is a significant health problem. Close to 20 million individuals in the United States have T2D, and 79 million aged 20 years or older are clinically pre-diabetic, with a 5-year conversion rate of 10% to 23% from prediabetes to T2D. In a collaborative effort to systematically understand diabetes and its etiology, the team is comprised of leading experts in research on both the human host as well as the microbiome, as properties of both are likely relevant in T2D development. For a better elucidation of mechanisms of onset and progression of T2D disease, the group is performing a detailed analysis of the biological processes that occur in the microbiome and human host by longitudinal profiling of patients at risk for T2D. Both microbiome and host profiles are being analyzed by state-of-the-art omics platforms, and these large-scale and diverse data sets will be integrated to determine the dynamic pathways that change during the onset and progression of T2D, especially during viral infections and other stresses. This longitudinal study is expected to reveal changes in the microbiome and host at an unprecedented level of detail, and identify molecules and pathways that play important roles in diabetes onset and progression.

  Study phs001719