10670 results for "800k fc coins Navštivte Buyfc26coins.com Speciální balíčky na prázdniny a dovolené..dQVy"

in 132.85 milliseconds.

• 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

• The Research Institute at Nationwide Children's Hospital Genetics of Congenital Heart Disease (CHD)

  Congenital heart disease (CHD) is the most common type of birth defect, but the cause for the majority of cardiac birth defects remains unknown. Numerous epidemiologic studies have demonstrated evidence that genetic factors likely play a contributory, if not causative, role in CHD. A few genes have been identified by us and other investigators using traditional genetic approaches, but these genes only account for a small portion of the non-syndromic CHDs. Therefore, we are now utilizing whole exome sequencing (WES) and whole genome sequencing (WGS), with the addition of more traditional genetic techniques such as chromosomal microarray or traditional linkage analysis, to identify genetic causes of familial and isolated CHD. With WES/WGS, we are able to sequence all of the genes of an individual and apply different data analysis techniques based on whether we are analyzing a multiplex family or a cohort of trios (mother, father and child with CHD) with a specific isolated CHD. Therefore, WES/WGS is a robust method for identification of novel genetic causes of CHD, which will have important diagnostic and therapeutic consequences for these children. Subjects provided blood samples, skin biopsy, or saliva samples for DNA extraction and creation of cell lines. Tissue remaining after surgical procedures was also collected. Medical records were searched for detailed phenotype data and subjects were followed longitudinally for outcome.

  Study phs002010

• ApoA-1 and Atherosclerosis in Psoriasis

  Apolipoprotein A-1 is a protein localized to high-density lipoprotein that functions to remove cholesterol from tissues for transport back to the liver. Psoriasis is a systemic inflammatory disease associated with poor high-density lipoprotein function and accelerated non-calcified burden by coronary computed tomographic angiography. In this study, 310 psoriasis patients from The Psoriasis, Atherosclerosis, and Cardiometabolic Disease Initiative (PACI) were studied at baseline to determine if levels of circulating apolipoprotein A-1 predict early onset coronary artery disease in inflammatory conditions. Of the 310 participants, 124 were followed for four years to determine if apolipoprotein A-1 predicts non-calcified coronary burden over time. The primary outcome of this study was non-calcified coronary burden by coronary computed tomography angiography. To assess non-calcified coronary burden, participants underwent coronary computed tomography angiography using the same scanner (320-detector row Aquilion ONE ViSION, Toshiba, Japan). For ApoA-1 quantification, fasting blood draw was performed the same day as the coronary computed tomography angiography. The 400MHz proton Vantera Clinical Analyzer was used to quantify Plasma apolipoprotein A-1. The study determined that low levels of apolipoprotein A-1 are associated with increased coronary artery burden and that this relationship persists over time. The data are available through dbGaP and the dataset includes all variables reported in the manuscript.

  Study phs003231

• NHLBI TOPMed: Pulmonary Hypertension and the Hypoxic Response in SCD (PUSH)

  During Visit One, the PUSH Study will perform echocardiography on 600 children and adolescent with patients with sickle cell disease (SCD) and 100 control children and adolescents at three Field Centers, namely Howard University, Children's National Medical Center and University of Michigan. Patients or their parents will be approached and asked to give informed consent. If they appear to have a difficult reading, reading of the consent will be offered. Patients or their parents not appearing to comprehend the consent will not be eligible. As a part of this visit, each participant or parent will sign informed consent, complete a Participant Contact Information Form, complete a Medical History Form, undergo physical examination with completion of a Physical Examination Form and have blood drawn. Each participant must have echocardiography performed with measurement of Tricuspid Regurgitant Jet Velocity (TRV). In addition, attempts will be made 1) to perform a six-minute walk test, 2) to collect information from a recent (within six months) Transcranial Doppler Study (TCD) or to perform TCD, and 3) to perform pulmonary function tests. Study personnel will review all forms for completeness and conduct phlebotomy. Blood will be shipped to the Central Lab. Results of all procedures and tests will be transmitted to the Data Manager at Howard University. Sequencing was only done on sickle cell participants.

  Study phs001682

• The Bangladesh Environmental Enteric Dysfunction (BEED) Study

  Environmental enteric dysfunction (EED), a sub-acute inflammatory condition of the small intestinal mucosa of unclear etiology, has been associated with a variety of environmental exposures and host factors and is implicated in growth faltering. Linear growth faltering usually occurs within the first two years of life and in most of the cases is irreversible demanding early diagnosis for treatment to be successful. The objectives of 'The Bangladesh Environmental Enteric Dysfunction Study (BEED)' are to investigate role of EED in malnutrition, examine the biology of EED to identify common biological pathways for potential interventions, to validate a system for histological scoring for EED and test the effectiveness of nutritional interventions in improving the growth parameters in children with stunting and or EED. In Bangladesh, participants are recruited from two age groups; a child cohort and a malnourished an adult cohort. In addition, two control groups are recruited for comparison consisting of a) children that are undergoing endoscopy as a part of their clinical care at the University of Virginia Health system (UVAHS) and b) an adult well-nourished control group recruited from the Gastroenterology Outpatient Department of Dhaka Medical College and Hospital in Bangladesh. The description of the study design and procedures of the study can be obtained from Mahfuz M, Das S, Mazumder RN, et al., 2017, PMID: 28801442.

  Study phs001891

• Single cell sequencing reveals the origin and the order of mutation acquisition in T-cell acute lymphoblastic leukemia.

  Next-generation sequencing has provided a detailed overview of the various genomic lesions implicated in the pathogenesis of T-cell acute lymphoblastic leukemia (T-ALL). Typically, 10 to 20 genomic lesions are found in T-ALL cells at diagnosis. However, it is currently unclear in which order these mutations are acquired and in which progenitor cells this is initiated. To address these questions, we used targeted single-cell sequencing of total bone marrow cells and CD34+CD38- multipotent progenitor cells for 4 T-ALL cases. Hierarchical clustering detected a dominant leukemia clone at diagnosis, accompanied by a few subclones harboring only a fraction of the mutations. We developed a graph-based algorithm to determine the order of mutation acquisition. Two of the four patients had an early event in a known oncogene (MED12, STAT5B) amongst various pre-leukemic events. Intermediate events included loss of 9p21 (CDKN2A/B) and acquisition of fusion genes, while NOTCH1 mutations were typically late events. Analysis of CD34+CD38- cells and myeloid progenitors revealed that in half of the cases somatic mutations were detectable in multipotent progenitor cells. We demonstrate that targeted single cell sequencing can elucidate the order of mutation acquisition in T-ALL and that T-ALL development can start in a multipotent progenitor cell.

  Study EGAS00001002830

• Hyperhaploid Multiple Myeloma

  Hyperhaploid multiple myeloma is a rare numerical aberration group defined by a range of 24-34 chromosomes which is associated with a poor prognosis. Hyperhaploid samples were sequenced by either exome or targeted panel sequencing. Samples had a median of 13 monosomies (range 12-14), which in general were those not associated with trisomies in hyperdiploid samples. The chromosomes traditionally trisomic in hyperdiploid myeloma were disomic in hyperhaploid myeloma with retention of heterodisomy. We examined the hyperhaploid samples for frequently mutated genes and found that 9/9 (100%) hyperhaploid samples had a mutation in TP53, exceeding the overall rate of mutation in newly diagnosed patients (5.5%), indicating an oncogenic dependency in this group. All samples with TP53 mutation also had monosomy of chromosome 17, indicating bi-allelic inactivation of TP53. As such, this high risk group is part of Double-Hit myeloma. DNA was obtained from either CD138+ cells from the bone marrow of multiple myeloma patients (tumor) or from stem cell harvests from the same patient (control). 100 ng of DNA was fragmented, end-repaired, and adapters ligated using the HyperPlus kit (KAPA Biosystems). After PCR amplification the libraries were hybridized with probes against either the entire exome (MedExome, Nimblegen) or a targeted panel of 140 genes using SeqCap reagents (Nimblegen). Hybridized libraries underwent further amplification before being sequenced on a NextSeq500 (Illumina) using 75 bp paired end reads.

  Study EGAS00001003203