20305 results for "Fc coins Buyfc26coins.com is EA Sports official for FC 26 coins They are efficient and quick always..Z2Xg"

in 18.73 milliseconds.

• NHLBI TOPMed: MWCCS: Sex Differences in the Role of Multi-Omics in HIV-Associated Carotid Artery Atherosclerosis

  The MACS-WIHS Combined Cohort Study (MWCCS) is a multicenter prospective cohort study of men and women in the U.S. that aims to understand and reduce the impact of chronic health conditions, including heart, lung, blood, and sleep (HLBS) disorders that affect people living with HIV. MWCCS, which currently has over 5000 active study participants, is designed to investigate a spectrum of questions relating to the basic science, clinical science, and epidemiology of HIV infection in the U.S., with a focus on comorbidities among men and women living with HIV. The current substudy, nested within the MWCCS, integrates detailed metabolomics and proteomics data, among other "omics" measures, to improve the understanding of the etiology of atherosclerosis and cardiovascular disease in women and men with HIV, guide mechanistic studies, and provide insights to more efficient intervention strategies. Data on 374 men are included in the current substudy.

  Study phs003651

• Targeting the p53 pathway to treat Malignant Rhabdoid and High-Risk Atypical Teratoid Rhabdoid Tumors

  Rhabdoid tumors (RTs) predominantly affect young children and are among the deadliest pediatric solid tumors. Despite multimodal therapy consisting of surgery, radiation, and chemotherapy, children with these tumors have median survival of less than one year. RTs can arise throughout the body, including the central nervous system (CNS) where they are called atypical teratoid rhabdoid tumors (AT/RTs), and in extra-CNS locations such as the kidneys and other soft tissues where they are designated malignant RTs (MRTs). We previously identified MDM2 and MDM4 as therapeutic vulnerabilities in RTs and showed that treatment with the MDM2 inhibitor idasanutlin increased survival in mice bearing MRT xenografts. However, the therapeutic potential of idasanutlin in CNS RT tumors is unknown. Single agent therapies are prone to resistance and show limited clinical benefit on their own. Therefore, we sought to identify combination strategies incorporating idasanutlin that would be effective in both CNS and extra-CNS RTs. Here, we show that the XPO1 inhibitor selinexor increased nuclear retention of p53 and potentiated idasanutlin-induced p53 pathway activation and cytotoxicity in AT/RT and MRT cell lines in vitro. Importantly, combination therapy limited acquired resistance through TP53 mutation. In vivo, combination therapy was well-tolerated, reduced tumor burden, and increased survival in orthotopic models of both AT/RT and MRT. Our results demonstrate that combining idasanutlin with selinexor is a promising therapeutic strategy for children with rhabdoid tumors.

  Study EGAS00001007680

• Beacon v2

  Beacon v2: a tool for data discovery Motivation In the era of data-driven health research and personalised medicine, human genomic data has become extremely valuable. These are also identifiable data, as they carry information pointing to a specific individual as well as their own family; and as such, they must be protected. This makes data discovery particularly challenging: this is where "Beacon" comes in. A "Beacon" is an API aiming to enable the search of genomic variants and associated information without jeopardising the privacy of the dataset. Here, we refer to its current version, namely version 2 (v2). Definition Beacon v2 is a term that can refer to different aspects. The EGA is playing a central role in the following aspects: The Beacon v2 protocol is a Global Alliance for Health and Genomics standard. The Beacon v2 Reference Implementation (B2RI) is an "out-of-the-box" Beacon instance developed with ELIXIR, which facilitates Beacon deployment. The EGA Beacon(s) are Beacons following the v2 standard and using the B2RI, deployed on top of data hosted at the EGA and allowing for their discovery. Resources Depending on whether you are visiting us a stakeholder (you need more general information about Beacon), a deployer /implementer (you want to have your own Beacon instance), or an EGA user (you want to query Beacon and start browsing data), you will be interested in the following resources: Your role Beacon aspect Documentation type Stakeholder Beacon v2 protocol Beacon website Beacon page on the GA4GH website Deployer/Implementer Beacon v2 protocol Read the docs: Beacon v2 standard technical description GitHub repository Beacon v2 standard Beacon v2 Reference Implementation Read the docs: B2RI technical description GitHub repository B2RI Guide to deploy Beacon using B2RI EGA user EGA Beacon EGA AF Browser

  Documentation about/projects-and-funders/beacon

• Longitudinal Study of Immune Mediated Disorders After Allogenic Hematopoietic Cell Transplantation (HCT)

  Allogeneic hematopoietic cell transplantation (HCT) is the only known curative option for many hematologic disorders. After transplantation, many patients develop immune mediated disorders that may be life-threatening. Post-HCT immune mediated disorders are rare relative to other diseases but the prototype of graft versus host disease (GVHD) develops in 30-70% of patients. The morbidity and mortality associated with these HCT-associated immune mediated disorders are major barriers to successful use of transplantation to cure rare hematologic malignancies such as leukemia, lymphoma, multiple myeloma, myelodysplastic/myeloproliferative syndromes amongst other diseases. The purpose of this study is to characterize and more completely define the onset and course of immune mediated disorders after allogeneic HCT, focusing on participants who develop cutaneous sclerosis, bronchiolitis obliterans syndrome (BOS), late acute graft-vs.-host disease (GVHD), and chronic GVHD. Of the participants undergoing allogeneic hematopoietic cell transplantation (HCT), can we, the researchers better identify who will develop immune-mediated disorders, what types of disorders participants will have, and whether these disorders will be severe or respond to currently available therapies? This is a longitudinal study of 1118 individuals (1081 adults and 100 children). Those participating in this study will be evaluated over a 3 year period at 9 study sites. Participants will be enrolled pre-transplant, or up to day 121 post transplantation. This wide enrollment window will allow sites to use recruitment methods that are most efficient at their institutions. At least 2 years of follow-up will ensure an adequate sample size, and sufficient time for observation of the full spectrum of immune mediated disorders. The data of 1023 individuals have been submitted to dbGaP.

  Study phs001331

• Clonal somatic copy number altered driver events inform drug sensitivity in high-grade serous ovarian cancer.

  This dataset consists of shallow whole genome sequencing data and amplicon sequencing data for 26 ovarian cancer patients (21 high-grade serous ovarian cancer, 4 low-grade serous ovarian cancer and 1 clear cell ovarian cancer). The data are provided as single end FASTQ files for the shallow whole genome sequencing data (31 libraries) and paired end FASTQ files for the amplicon sequencing data (98 libraries).

  Dataset EGAD00001008716

• Transcriptome analysis of endometrial organoids derived from patients with Mayer-Rokitansky-Küster-Hauser syndrome

  The Mayer-Rokitansky-Küster-Hauser (MRKH) syndrome is characterized by agenesis of the uterus and upper part of the vagina in females with normal ovarian function. The cause of the disease is still enigmatic. Here, we developed organoid cultures from endometrium found in uterine rudiment horns of MRKH patients. Phenotypically they share great similarity between healthy control organoids and are fully hormone responsive. Transcriptome analysis using RNA-seq identified possible disease-causing pathways altered in MRKH patients during development of the female reproductive tract. Thus, the organoid cultures provide a powerful research model for further insight into disease-causing alterations.

  Study EGAS00001005908

• Study the differences at the trascriptome level between iNKT and T cells

  Chimeric antigen receptor anti-CD19 (CAR19)-T cell immunotherapy-induced clinical remissions in CD19+ B cell lymphomas are often short-lived. We tested whether CAR19-engineering of the CD1d-restricted invariant NKT (iNKT) cells would result in enhanced anti-lymphoma activity. CAR19-iNKT cells co-operatively activated by CD1d- and CAR19-CD19-dependent interactions are more effective than CAR19-T cells against CD1d-expressing lymphomas in vitro and in vivo. The swifter in vivo anti-lymphoma activity of CAR19-iNKT cells and their enhanced ability to eradicate brain lymphomas underpinned an improved tumor-free and overall survival. CD1d transcriptional de-repression by all-trans retinoic acid results in further enhanced cytotoxicity of CAR19-iNKT cells against CD19+ chronic lymphocytic leukemia cells. Thus, iNKT cells are a highly efficient platform for CAR-based immunotherapy of lymphomas and possibly other CD1d-expressing cancers.

  Study EGAS00001003176

• Multi-Modal Single-Cell and Whole-Genome Sequencing of Small, Frozen Clinical Specimens

  Clinical application of single-cell sequencing technologies has been hampered by their need for quick processing of relatively large, fresh specimens. Here, we benchmarked the performance of a new technique for single-cell sequencing from snap-frozen clinical samples, vs. sequencing from fresh samples, on 5 samples from cutaneous melanoma brain metastasis, 6 samples from NSCLC brain metastasis, and 3 from uveal melanoma primary tumor. Additionally, we performed frozen sample sequencing of 20 uveal melanoma liver metastasis samples, and 3 cutaneous melanoma extracranial metastasis samples. Finally, for selected groups of the above-mentioned samples, we also performed TCR sequencing, SlideSeqV2 spatial transcriptomics, ultra-shallow whole-genome sequencing, and whole-exome sequencing, to present a comprehensive multi-modal profiling of all datasets.

  Study phs003097

• Cookies

  Cookies https://ega-archive.org does not identify users on this site. It does use cookies, though. What is a cookie? Cookies are text files containing small amounts of information which are downloaded to your device when you visit a website. They allow a website to remember your preferences and are therefore useful to improve your online experience. Find out more information about cookies. Types of cookies we use Functional These cookies record the columns you wish to display or hide in the results page.Performance These cookies are used to analyse trends, administer the website, track visitor movements and gather broad demographic information for aggregate use. We use the information to compile reports and to help us improve our websites. These cookies are not linked to personally identifiable information. Session cookie A session cookie for a website only exists whilst the user is reading or navigating the website. When the user closes their web browser these cookies are usually removed.

  Documentation cookies

• 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