10675 results for "fc coins olx Navštivte Buyfc26coins.com Podpora pro profesionální hráče a týmy..zSiZ"

in 11.35 milliseconds.

• Robust methylation-based classification of brain tumours using nanopore sequencing

  Background: DNA methylation-based classification of cancer provides a comprehensive molecular approach to diagnose tumours. In fact, DNA methylation profiling of human brain tumours already profoundly impacts clinical neuro-oncology. However, current implementations using hybridization microarrays are time-consuming and costly. We recently reported on shallow nanopore whole-genome sequencing for rapid and cost-effective generation of genome-wide 5-methylcytosine profiles as input to supervised classification. Here, we demonstrate that this approach allows to discriminate a wide spectrum of primary brain tumours. Results: Using public reference data of 82 distinct tumour entities, we performed nanopore genome sequencing on N=382 tissue samples covering 46 brain tumour (sub)types. Using bootstrap sampling in a cohort of N = 56 cases, we find that a minimum set of 1,000 random CpG features is sufficient for high-confidence classification by ad hoc random forests. We implemented score recalibration as confidence measure for interpretation in a clinical context and empirically determined a platform-specific threshold in a randomly sampled discovery cohort (N = 185). Applying this cut-off to an independent validation series (N = 184) yielded 148 classifiable cases (sensitivity 80.4%) and demonstrated 100 % specificity. Cross-lab validation demonstrated robustness with concordant results across four laboratories in 10/11 (90.9%) cases. In a prospective benchmarking (N = 15), median time to results was 21.1 hours. Conclusions: In conclusion, nanopore sequencing allows robust and rapid methylation-based classification across the full spectrum of brain tumours. Platform-specific confidence scores facilitate clinical implementation for which prospective evaluation is warranted and ongoing.

  Study EGAS00001006540

• Chronic lymphocytic leukemia IGHV somatic hypermutation detection by targeted capture next-generation sequencing

  Somatic hypermutation (SHM) status of the immunoglobulin heavy variable (IGHV) gene locus plays a crucial role in determining the prognosis and treatment of patients with chronic lymphocytic leukemia (CLL). A common approach for determining SHM status is multiplex PCR of the IGH gene followed by Sanger sequencing; however, this technique is low throughput, vulnerable to failure, and does not allow multiplexing with other molecular diagnostic assays. Here we designed and validated a DNA targeted capture approach that allows the assessment of IGHV SHM status as a sub-module of a larger next-generation sequencing (NGS) assay. We developed an end-to-end assay that takes as input raw FASTQ files and outputs a report containing IGHV SHM status and V-allele usage following the guidelines of the European Research Initiative on CLL (ERIC). We validated the approach on 35 CLL patient samples, 34 of which were previously characterized using Sanger sequencing. The targeted capture NGS panel identified the SHM status of 34 of 35 CLL patients. We showed 100% sensitivity and specificity among the 33 CLL samples with both NGS and Sanger calls. Furthermore, we demonstrated that this panel can be combined with additional targeted capture panels to detect common and prognostically important CLL single nucleotide variants (SNV) and insertion/deletion (indel) variants as well as copy number variants (del17p). Thus, a targeted capture approach to IGHV SHM detection can be easily integrated into broader sequencing panels, allowing broad CLL prognostication in a single molecular assay.

  Study EGAS00001006887

• Whole Exome Sequencing data of six chRCC tumors corresponding to three patients

  Mammalian target of rapamycin (mTOR) is a central regulator of mammalian metabolism and physiology. Aberrant hyperactivation of the mTOR pathway promotes tumor growth and metastasis, and can also promote tumor resistance to chemotherapy and cancer drugs; this makes mTOR an attractive cancer therapeutic target. mTOR inhibitors have been approved to treat cancer; however, the mechanisms underlying drug sensitivity remain poorly understood. Here, whole exome sequencing of three chromophobe renal cell carcinoma (chRCC) patients with exceptional mTOR inhibitor sensitivity revealed that all three patients shared somatic mutations in the deubiquitinase USP9X. The clonal characteristics of the mutations, which were amassed by studying multiple patients’ primary and metastatic samples from various years, together with the low USP9X mutation rate in unselected chRCC series, reinforced a causal link between USP9X and mTOR inhibitor sensitivity. Rapamycin treatment of USP9X-depleted HeLa and renal cancer 786-O cells, along with the pharmacological inhibition of USP9X, confirmed that this protein plays a role in patients’ sensitivity to mTOR inhibition. USP9X was not found to exert a direct effect on mTORC1, but subsequent ubiquitylome analyses identified p62 as a direct USP9X target. Increased p62 ubiquitination and the augmented rapamycin effect upon bortezomib treatment, together with the results of p62 and LC3 immunofluorescence assays, suggested that dysregulated autophagy in USP9X-depleted cells can have a synergistic effect with mTOR inhibitors. In summary, we show that USP9X constitutes a potential novel marker of sensitivity to mTOR inhibitors in chRCC patients, and represents a clinical strategy for increasing the sensitivity to these drugs.

  Study EGAS00001007104

• Spatio-temporal Profiling of a Rhabdoid Tumor Case Study

  Background Immune checkpoint inhibition (ICI) has revolutionized oncology, offering extended survival and long-term remission in previously incurable cancers. While highly effective in tumors with high mutational burden, lowly mutated cancers, including pediatric malignancies, present low response rate and limited predictive biomarkers. Patients and methods We present a framework for the identification and validation of tumor-reactive T cells as a biomarker to quantify ICI efficacy and as candidates for a personalized TCR-T cell therapy. Therefore, we profiled a pediatric malignant rhabdoid tumor patient with complete remission after ICI therapy using deep single-cell T cell receptor (TCR) repertoire sequencing of the tumor microenvironment (TME) and the peripheral blood. Results Tracking T cell dynamics longitudinally from the tumor to cells in circulation over a time course of 12 months revealed a systemic response and durable clonal expansion of tumor-resident and ICI-induced TCR clonotypes. We functionally validated tumor reactivity of TCRs identified from the TME and the blood by co-culturing patient-derived tumor cells with TCR-engineered autologous T cells. Here, we observed unexpectedly high frequencies of tumor-reactive TCR clonotypes in the TME and confirmed T cell dynamics in the blood post-ICI to predict tumor-reactivity. Conclusion These findings strongly support spatio-temporal tracking of T cell activity in response to ICI to inform therapy efficacy and to serve as a source of tumor-reactive TCRs for personalized TCR-T designs.

  Study EGAS00001008174

• A no-stop mutation in MAGEB4 is a possible cause of rare X-linked azoospermia and oligozoospermia in a consanguineous Turkish family

  Purpose: The purpose of this study was to identify mutations that cause non-syndromic male infertility using whole exome sequencing of family cases.Methods: We recruited a consanguineous Turkish family comprising nine siblings with male triplets; two of the triplets were infertile as well as one younger infertile brother. Whole exome sequencing (WES) performed on two azoospermic brothers, identified a mutation in the MAGEB4 gene which was confirmed via Sanger sequencing and then screened for on control groups and unrelated infertile subjects. The effect of the mutation on mRNA and protein levels were tested after in vitro cell transfection. Structural features of MAGEB4 were predicted throughout the conserved MAGE domain.Results: The novel single base substitution (c.1041A>T) in the X-linked MAGEB4 gene was identified as a no-stop mutation. The mutation is predicted to add 24 amino acids to the C-terminus of MAGEB4. Our functional studies were unable to detect any effect either on mRNA stability, intracellular localization of the protein or the ability to homo / heterodimerize with other MAGE proteins. We thus hypothesize that these additional amino acids may affect the proper protein interactions with MAGEB4 partners. Conclusion: The whole exome analysis of a consanguineous Turkish family revealed MAGEB4 as a possible new X-linked cause of inherited male infertility. This study provides the first clue to the physiological function of a MAGE protein.

  Study EGAS00001002272

• The Medical Genome Reference Bank: a whole genome data resource of 4,000 healthy elderly individuals.

  Allele frequency data from human reference populations is of increasing value for filtering and assignment of pathogenicity to genetic variants. Aged and healthy populations are more likely to be selectively depleted of pathogenic alleles, and therefore particularly suitable as a reference populations for the major diseases of clinical and public health importance. However, reference studies of the healthy elderly have remained under represented in human genetics. We have developed the Medical Genome Reference Bank (MGRB), a large scale comprehensive whole genome dataset of confirmed healthy elderly individuals, to provide a publicly accessible resource for health related research, and for clinical genetics. It also represents a useful resource for studying the genetics of healthy aging. The MGRB comprises 4,000 healthy, older individuals with no reported history of cancer, cardiovascular disease or dementia, recruited from two Australian community based cohorts. DNA derived from blood samples will be subject to whole genome sequencing. The MGRB will measure genome wide genetic variation in 4,000 individuals, mostly of European decent, aged 60 to 95 years (mean age 75 years). The MGRB has committed to a policy of data sharing, employing a hierarchical data management system to maintain participant privacy and confidentiality, whilst maximizing research and clinical usage of the database. The MGRB will represent a dataset of international significance, broadly accessible to the clinical and genetic research community.

  Study EGAS00001003511

• A novel orthotopic patient-derived xenograft model of radiation-induced glioma following medulloblastoma

  Radiation-induced glioma (RIG) is a highly aggressive brain cancer arising as a consequence of radiation therapy. We report a case of RIG that arose in the brain stem following treatment for paediatric medulloblastoma, and the development and characterisation of a matched orthotopic patient-derived xenograft (PDX) model (TK-RIG915). Patient and PDX tumours were analysed using DNA methylation profiling, whole genome sequencing (WGS) and RNA sequencing. While initially thought to be a diffuse intrinsic pontine glioma (DIPG) based on disease location, results from methylation profiling and WGS were not consistent with this diagnosis. Furthermore, clustering analyses based on RNA expression suggested the tumours were distinct from primary DIPG. Additional gene expression analysis demonstrated concordance with a published RIG expression profile. Multiple genetic alterations that enhance PI3K/AKT and Ras/Raf/MEK/ERK signalling were discovered in TK-RIG915 including an activating mutation in PIK3CA, upregulation of PDGFRA and AKT2, inactivating mutations in NF1, and a gain-of-function mutation in PTPN11. Additionally, deletion of CDKN2A/B, increased IDH1 expression, and decreased ARID1A expression were observed. Detection of phospho-S6, -4EBP1 and -ERK via immunohistochemistry confirmed PI3K pathway and ERK activation. Here, we report one of the first PDX models for RIG, which recapitulates the patient disease and is molecularly distinct from primary brain stem glioma. Genetic interrogation of this model has enabled the identification of potential therapeutic vulnerabilities in this currently incurable disease.

  Study EGAS00001004709

• 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

• Clonal heterogeneity leads to secondary resistance in a melanoma patient after adoptive cell therapy with tumor-infiltrating lymphocytes

  Adoptive cell therapy (ACT) with tumor-infiltrating lymphocytes (TIL) is effective in melanoma patients, although long-term responses seem restricted to patients with complete remissions. Many patients develop secondary resistance to TIL-ACT but involved mechanisms are unclear. Here, we describe a case of secondary resistance to TIL-ACT likely due to intratumoral heterogeneity and selection of a resistant tumor cell clone via transferred T cells. This is the first case of clonal selection of a pre-existing non-dominant tumor cell clone and demonstrates a new mechanism involved in secondary resistance to TIL-ACT and could potentially change current clinical practice, because it advocates for T cell collection from different tumor sites and analysis of tumor heterogeneity before the treatment with TIL-ACT.

  Study EGAS50000000279

• A benchmarking resource for NGS testing of cancer predisposition genes

  A benchmarking resource of 639 individuals, to assess the analytical sensitivity of cancer predisposition gene (CPG) testing.The dataset includes sequencing data generated using the TruSight Cancer Panel (TSCP) a targeted NGS assay for analysis of CPGs and orthogonally generated data supporting at least one pathogenic variant in a CPG for a total of 645 pathogenic CPG variants.The set of pathogenic CPG variants includes strong representation of some of the most challenging types of pathogenic variants, with 339 indels, including 16 complex indels and 24 insertions or deletions with length greater than 5bp, and 74 exon CNVs, including 23 single exon CNVs. There are 502 pathogenic variants in BRCA1 or BRCA2, making this an important first-line validation dataset for laboratories performing NGS testing of BRCA1 and BRCA2.

  Study EGAS00001002993