21178 results for "Buy fc 26 coins Buyfc26coins.com is EA Sports official for FC 26 coins The process was smooth and quick..ivNx"

in 61.71 milliseconds.

• Towards a Genomic Understanding of Myeloma

  This project was designed to describe genetic abnormalities in primary samples from patients with multiple myeloma by next generation sequencing. We generated sequence data from multiple myeloma (MM) patients analyzing DNA both from tumor cells (purified from bone marrow using CD138 selection as a marker of plasma cells) and from normal peripheral blood cells (either whole blood or Ficoll-purified mononuclear cells). Using massively parallel sequencing technology (Illumina GA-2 or HiSeq)), we performed whole-genome sequencing (WGS) and/or whole-exome sequencing (WES). The initial set currently deposited contains data from 38 MM patients (23 patients surveyed by WGS and 16 patients by WES, with one patient analyzed by both approaches). Genomes were sampled to high depth, obtaining an average of 33X coverage and 104X coverage for WGS and WES tumors, respectively. The normal samples had similar coverage. Our goal is to help researchers understand the complex genetic landscape of multiple myeloma and provide a resource for the generation of biological hypotheses.

  Study phs000348

• The genomic complexity of early T-cell progenitor acute lymphoblastic leukemia

  CREST The accurate identification of structural variations using whole-genome DNA sequencing data generated by next-generation sequencing technology is extremely difficult. To address this challenge, we have developed CREST, an algorithm that uses sequencing reads with partial alignments to the reference human genome (so-called soft-clipped reads) to directly map the breakpoints of somatic structural variations. We applied CREST to paired tumor/normal whole genome sequencing data from five cases of T-lineage acute lymphoblastic leukemia (T-ALL). A total of 110 somatic structural variants were identified, >80% of which were validated by genomic PCR and Sanger sequencing. The validated structural variants included 31 inter-chromosomal translocations, 19 intra-chromosomal translocations, one inversion, 22 deletions and 16 insertions. A comparison of the results generated with CREST to those obtained using the traditional paired-end discordant mapping methods demonstrate CREST to have a much higher sensitivity and specificity. In addition, application of CREST to publicly available whole-genome sequencing data from the human melanoma cancer cell line COLO-829 demonstrated the identification of 50 novel structural variations not detected using the standard methods, 20 of which were selected for validation with a 90% success rate. These data demonstrate that direct mapping of soft-clipped reads offers an improved method for detecting structural variants at the nucleotide level of resolution. T-ALL Early T-cell precursor acute lymphoblastic leukaemia (ETP ALL) is an aggressive malignancy of unknown genetic basis. We performed whole-genome sequencing of 12 ETP ALL cases and assessed the frequency of the identified somatic mutations in 94 T-cell acute lymphoblastic leukaemia cases. ETP ALL was characterized by activating mutations in genes regulating cytokine receptor and RAS signalling (67% of cases; NRAS, KRAS, FLT3, IL7R, JAK3, JAK1, SH2B3 and BRAF), inactivating lesions disrupting haematopoietic development (58%; GATA3, ETV6, RUNX1, IKZF1 and EP300) and histone-modifying genes (48%; EZH2, EED, SUZ12, SETD2 and EP300). We also identified new targets of recurrent mutation including DNM2, ECT2L and RELN. The mutational spectrum is similar to myeloid tumours, and moreover, the global transcriptional profile of ETP ALL was similar to that of normal and myeloid leukaemia haematopoietic stem cells. These findings suggest that addition of myeloid-directed therapies might improve the poor outcome of ETP ALL.

  Study phs000340

• Chronic Renal Insufficiency Cohort (CRIC) Study Metabolomics and Proteomics

  The Chronic Renal Insufficiency Cohort (CRIC study) was established in 2001 by the National Institute of Diabetes, Digestive, and Kidney Diseases (NIDDK) to improve the understanding of the relationship between chronic kidney disease and cardiovascular disease. The goals of the CRIC Study are to examine risk factors for progression of chronic kidney disease and cardiovascular disease among patients with chronic kidney disease and to develop predictive models to identify high-risk subgroups, informing future treatment trials and increasing application of available preventive therapies. This record includes plasma metabolomics and plasma proteomics data. Genotype data for 3527 CRIC Study partcipants is available at dbGaP in phs000524, "Chronic Renal Insufficiency Cohort (CRIC)-GWAS". Additional phenotypic, clinical, and outcomes data are available at the NIDDK Central Repository and can be linked to data available at dbGaP.More than 330 manuscripts have been published, reporting on the effects of a broad range of risk factors (from molecular biomarkers of disease pathways to clinical, demographic, and behavioral characteristics) on the progression of CKD and other health consequences. The full CRIC bibliography can be found at the BIBLIOGRAPHY for the Chronic Renal Insufficiency Cohort (CRIC) Study.

  Study phs003709

• Molecular profiling of longitudinally observed small colorectal polyps: a cohort study

  Knowledge of the natural history of colorectal adenomas is limited because these lesions are removed upon detection. The few studies in which small adenomas have been left in situ for a limited period of time have shown that most lesions remain stable or even completely vanish. Lesions that have grown in size more often turn out to be advanced adenomas when resected. Specific DNA copy number changes (cancer associated events or CAEs) are associated with progression of adenomas to cancer. The aim of the study was to evaluate whether growth of small colorectal polyps left in situ is associated with specific molecular features.

  Study EGAS00001003284

• Somatic Copy Number Analysis of Endometrial Carcinomas

  Endometrial cancer (EC) is the most commonly diagnosed gynecologic malignancy in the United States and is the sixth leading cause of cancer death amongst American women. The purpose of this study was to identify somatic (tumor-specific) copy number alterations in 7 clear cell ECs, 31 serous ECs, 17 endometrioid ECs, and the clear cell components of 2 endometrioid/clear cell ECs. To this end, DNAs from de-identified primary endometrial tumors and matched non-tumor tissues or blood were hybridized to high-density Illumina Infinium HumanHap650Y Beadchips or to high-density Human660W-Quad Beadchips and the data analyzed to annotate somatic copy number alterations throughout the genome.

  Study phs001690

• 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

• University of Washington Cerebrospinal Fluid Biomarker Study for Parkinson disease

  There is a clear need to develop biomarkers for Parkinson disease (PD) diagnosis and monitoring disease progression. In this study we evaluated cerebrospinal fluid (CSF) proteins, which are known to be critically involved in PD or identified in our preliminary profiling studies, aptamers, and RNAs as potential PD biomarkers. Access to subjects for this study was via the Pacific Northwest Udall Center (PANUC) and the Alzheimer&#39;s Disease Research Center (ADRC) at the University of Washington and Oregon Health and Sciences University (OHSU). Using CSF samples from 30 well-characterized patients with PD and 30 age-, sex-matched healthy controls, we prepared RNA seq libraries and performed deep sequencing of all RNA species, including small and long RNA, mRNAs, noncoding RNAs and differentially spliced transcripts. We then tried several methods for RNAseq data analysis to optimize our analysis pipeline. We identified a total of 3381 transcripts corresponding to 182 long intergenic RNAs (LincRNAs), 11 microRNAs (miRNAs), 2861 protein-coding transcripts, 200 pseudogenes and 127 antisense RNAs; some of them were differentially expressed between PD and control groups. Selected differentially expressed RNAs have been validated in the same set of CSF samples using real-time PCR (RT-PCR). Further validations in independent, larger cohorts of samples are still ongoing. Our results obtained so far suggested that CSF proteins and RNAs could be used as good indexes for PD diagnosis and disease severity/progression. This study is a part of the NIDDS-funded Parkinson&#39;s Disease Biomarkers Program (PDBP).

  Study phs000901

• Vitamin-D-Kids Asthma

  The Vitamin D Kids Asthma Study (VDKA) was a 48-week multicenter randomized, double-blinded, placebo-controlled trial of vitamin D3 for severe asthma exacerbations in children 6-16 years old, recruited from February 28, 2016 to September 20, 2019. An ancillary study for nasal sampling was conducted at the Pittsburgh site. Prior to randomization, participants completed questionnaires and underwent collection of nasal samples for gene expression studies. VDKA was approved by the IRBs of all participating institutions, and the ancillary study was approved by the IRB of the University of Pittsburgh. Written parental consent was obtained for participating children, from whom written assent was also obtained.

  Study phs004051

• Fecal microbiota transplantation - Effect of engraftment on plasma metabolomics and cllinical outcomes

  Fecal Microbiota Transplantation (FMT) has emerged as a potential modality for mitigating microbiome-associated diseases. Despite this potential, the precise causal pathways by which specific gut microbiota strains induce remission remain inadequately elucidated. In this study, we aimed to discern the impact of engraftment of donor-infused strains on alterations in plasma metabolites, subsequently contributing to the amelioration of clinical parameters involved in subjects with metabolic syndrome (MetSyn) receiving an FMT. We observed that a higher fraction of donor strains engrafted in the recipient is correlated to a reduction in diastolic blood pressure and found specific strains associations through Canonical correlation analysis. Integrating the metabolomics profile show that engraftment of Collinsella aerofaciens and Fusocatenibacter saccharovorans was related to a reduction in 2 oxoarginine in plasma, which was subsequently correlated to a reduction in diastolic blood pressure. In conclusion, we applied a novel framework to elucidate on the complex and heterogenous FMT intervention, establishing a connection between engrafted microbiota and clinical outcome parameters. Our findings underscore the potential therapeutic efficacy of FMT in ameliorating MetSyn, demonstrating a potential contribution of microbial strain engraftment to the improvement of MetSyn via modulation of circulating metabolites.

  Study EGAS50000000409

• Women's Environmental Cancer and Radiation Epidemiology (WECARE) Study

  Study population The WECARE Study is an international multicenter population-based case-control study of cases with asynchronous contralateral breast cancer (CBC) and individually matched controls with unilateral breast cancer (UBC). Recruitment and data collection for the WECARE Study were conducted in two phases, herein referred to as WECARE I (2001&#8211;2004) and WECARE II (2009&#8211;2012). The study design of the first phase (WECARE I) has been described in detail elsewhere [Bernstein JL, et al 2004, PMID: 15084244]; the second phase (WECARE II) employed a nearly identical approach [Langballe R, et al 2016, PMID: 27400983]. Participants in each phase were identified through eight population-based cancer registries, including six in the United States that contribute to the National Cancer Institute's Surveillance, Epidemiology, and End Results (SEER) program: Los Angeles County Cancer Surveillance Program; Cancer Surveillance System of the Fred Hutchinson Cancer Center (Seattle region, WA); State Health Registry of Iowa; Cancer Surveillance Program of Orange County/San Diego-Imperial Organization for Cancer Control (Orange County/San Diego, CA); the Greater Bay Area Cancer Registry (San Francisco Bay Area region and Santa Clara region, CA); and the Sacramento and Sierra Center Registry (Sacramento region, CA). Participants were additionally identified using the Ontario Cancer Registry (Canada) and the Danish Breast Cancer Cooperative Group Registry, supplemented by data from the Danish Cancer Registry. The study protocol was approved by the institutional review or regulatory ethics boards at each study site. Data collection Study participants were interviewed by telephone using a structured questionnaire aimed at evaluating known or suspected breast cancer risk factors, including personal demographics, medical history, menstrual and reproductive history, family history of cancer, use of hormones, smoking, and alcohol intake. Risk factor status was assessed during the period prior to first diagnosis, as well as between first diagnosis and reference date (i.e., the at-risk period for CBC). Detailed data on treatment and tumor characteristics were obtained directly from cancer registry records or by abstracting medical records, including pathology and surgical reports, radiation oncology clinic notes, and systemic adjuvant treatment data. Complete medical treatment history information was collected, and for all women who received radiotherapy, the radiation dose to the contralateral breast was reconstructed using radiotherapy records and radiation measurements. Biospecimens were collected from study participants for genotyping: blood collected from WECARE I women; and saliva collected from WECARE II women.

  Study phs003945