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

in 22.42 milliseconds.

• Colorectal advanced adenomas NKI-AvL TGO COCOS series

  Colorectal cancer (CRC) develops from normal epithelium, through a benign precursor lesion called adenoma, by accumulation of genetic alterations affecting oncogenes and tumour suppressor genes. About 5% of colorectal adenomas are estimated to progress to CRC. However, it is important to identify which adenomas actually carry a high-risk of progression, because these serve as intermediate endpoints for e.g. screening programs. In clinical practice, adenomas with a size of ≥10 mm, villous component and/or high-grade dysplasia, called advanced adenomas, are considered high-risk, although solid evidence for this classification is lacking. Specific DNA copy number changes are associated with adenoma-to-carcinoma progression.For this tissue dataset, we applied low-pass whole genome sequencing to 96 advanced adenomas. Advanced adenomas were classified as lesions with low-risk or high-risk of progression, according to the presence of specific DNA copy number changes (Carvalho et al, CancerPrevRes, 2018).

  Study EGAS00001002952

• Exploring_the_heterogeneity_of_sarcoma_using_single_cell_sequencing_

  Multi region samples are collected from patients, with consent, immediately after resection of the tumour. Samples are digested and sorted using FACS as single cells into lysis buffer. Cells are then stored until further processing for G&T-seq. After sequencing, we will explore intra-tumour heterogeneity using computational approaches to integrate RNA and DNA data onto the tumour phylogeny This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Study EGAS00001002866

• Whole genome sequencing data of paediatric hyperdiploid acute lymphoblastic leukemia

  The hyperdiploid (HeH) subtype with 51–67 chromosomes is the most common subtype in childhood, presented in 25–30% of the cases, and is associated with excellent prognosis . The HeH subtype harbors relatively few additional genetic alterations, suggesting that extra chromosomes are the driving event for leukemia onset. Secondary hits usually affect the RAS signaling pathway and histone modifiers.

  Study EGAS50000001690

• RNA sequencing data of pediatric hyperdiploid acute lymphoblastic leukemia

  The hyperdiploid (HeH) subtype with 51–67 chromosomes is the most common subtype in childhood, presented in 25–30% of the cases, and is associated with excellent prognosis . The HeH subtype harbors relatively few additional genetic alterations, suggesting that extra chromosomes are the driving event for leukemia onset. Secondary hits usually affect the RAS signaling pathway and histone modifiers.

  Study EGAS50000001802

• 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

• NHLBI TOPMed - NHGRI CCDG: Massachusetts General Hospital (MGH) Atrial Fibrillation Study

  The Massachusetts General Hospital (MGH) Atrial Fibrillation Study was initiated in 2001. The study has enrolled serial probands, unaffected and affected family members with atrial fibrillation. At enrollment participants undergo a structured interview to systematically capture their past medical history, AF treatments, and family history. An electrocardiogram is performed; the results of an echocardiogram are obtained; and blood samples are obtained. For the TOPMed WGS project only early-onset atrial fibrillation cases were sequenced. Early-onset atrial fibrillation was defined as an age of onset prior to 66 years of age. Comprehensive phenotypic and pedigree data for study participants are available through dbGaP phs001001.

  Study phs001062

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! 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! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• Mutations in the RAS/MAPK pathway drive replication repair deficient hypermutated tumors and confer sensitivity to MEK inhibition

  The RAS/MAPK pathway is an emerging targeted pathway across a spectrum of both adult and pediatric cancers. Typically, this is associated with a single, well-characterized point mutation in an oncogene. Hypermutant tumors which harbor many somatic mutations may obscure the interpretation of such targetable genomic events. We find that replication repair deficient (RRD) cancers which are universally hypermutant and affect children born with RRD cancer predisposition, are enriched for RAS/MAPK mutations (p=10-8). These mutations are not random, exist in subclones, and increase in allelic frequency over time. The RAS/MAPK pathway is activated both transcriptionally and at the protein level in patient derived RRD tumors and these tumors responded to MEK inhibition in vitro and in vivo. Treatment of patients with RAS/MAPK hypermutant gliomas reveal durable responses to MEK inhibition. Our observations suggest that hypermutant tumors may be addicted to oncogenic pathways resulting in favorable response to targeted therapies.

  Study EGAS00001005008

• Egypt_Genome_Project___high_coverage_whole_genome_sequencing

  All humans outside Africa are descendants of the same single exit, usually dated at 50-70 thousand years ago. However, the route taken out of Africa is still debated. The two main candidates are a northern route via Egypt and the Levant, or a southern route via Ethiopia and the Arabian Peninsula. We are generating genetic data to evaluate these two possibilities. In this study we propose to generate high-coverage sequencing data for 3 Egyptian samples.

  Study EGAS00001000482

• Clonal expansion and epigenetic reprogramming following deletion or amplification of mutant IDH

  Initially IDH1 mutant gliomas are shown to have IDH1 is deletions or amplifications at recurrence yielding a higher-grade tumor with a reprogrammed epigenome. We also report systematic selection for cells with IDH1 CNA in vitro and in vivo.

  Study EGAS00001002618

• Tumor-associated neutrophil 1 precursors impair homologous DNA repair and promote sensitivity to PARP-inhibition

  Tumor evolution is one of the major mechanisms responsible for acquiring therapy resistant and more aggressive cancer clones. Whether the tumor microenvironment through immune-mediated mechanisms might promote the development of more aggressive cancer types is crucial for the identification of additional therapeutical opportunities. Here, we identify a subset of tumor-associated neutrophils, defined as tumor-associated neutrophil precursors (PreNeu). These PreNeu are enriched in highly proliferative hormone-dependent breast cancers and impair DNA repair capacity

  Study EGAS00001008154

• Kibbutzim Family study

  The Kibbutzim Family Study (KFS) was established in 1992 to investigate the environmental and genetic determinants of cardiometabolic risk factors and their change over time. The participants belong to large families living in close-knit communities, called “Kibbutzim”, in Northern Israel. The Kibbutz has been a communal settlement, which has created a relatively homogeneous environment for its members. Kibbutz members are mostly of Ashkenazi Jewish ancestry, with the remaining members belonging to other Jewish subgroups. Participants were recruited in two phases from six Kibbutzim. In the first recruitment phase of the study (1992–1993) 500 individuals from 80 extended families (range 2 to 43) were examined. During the second phase (1999–2000), all participants from the first phase were invited for repeat examinations (80% response rate) and additional new participants were recruited, giving a total of 922 individuals from 150 extended families (range 2 to 55). Families were invited to participate if they consisted of at least four individuals who (i) lived in the Kibbutz, (ii) spanned at least two generations, and (iii) were at least 15 years old. Families were retained if at least two family members consented to participate in the study. Overall, 1033 participants were recruited; 111 were examined only in the first phase, 533 only in the second phase, and 389 were included in both. 901 individuals were successfully genotyped using Illumina HumanCoreExome BeadChip.

  Study EGAS00001002782

• Rapid Acceleration of Diagnostics - Underserved Populations (RADx-UP): COVID-19 Testing and Prevention in Correctional Settings

  This study will work with diverse correctional facilities across MN, RI, WA, and FL to characterize the incidence of COVID-19 disease progression and related outcomes. The goal is to identify barriers and facilitators to develop strategies to improve testing in these under-served populations by: Increasing the reach, access, uptake, and impact of COVID-19 testing among incarcerated people and staff in prison and jails. Individuals in congregate settings have been disproportionately affected by COVID-19, with correctional settings accounting for 39 of the 50 largest cluster outbreaks in the country to date. Schema of Correctional Facilities: Correctional facilities are amplifiers of infectious diseases for structural reasons: 1) Dormitory-style living and overcrowded conditions make social distancing nearly impossible 2) They have a focus primarily on security not health 3) Their medical departments are under-resourced and often disconnected from local public health agencies. Correctional facilities must be the focus of urgent intervention to understand the incidence of COVID-19, how it spreads in correctional facilities, and durable long-term strategies to reduce transmission, including testing and vaccines. However, our work from the COVID Prison Project shows that correctional systems have implemented a range of testing strategies, without coordination, such that synthesizing the information on COVID-19 incidence, outcomes and optimal testing strategies (including repeat testing and contact tracing) has been challenging. Incarcerated people decline testing due to concerns about confidentiality, implications for release, and fear of placement in solitary confinement. Through interviews we will identify ethical concerns and potential solutions for COVID-19 testing and vaccine strategies in correctional facilities using a community-engaged strategy. The project's work from the COVID Prison Project shows that correctional systems have implemented a range of testing strategies, without coordination, such that synthesizing the information on COVID-19 incidence, outcomes and optimal testing strategies (including repeat testing and contact tracing) has been challenging. Incarcerated people decline testing due to concerns about confidentiality, implications for release, and fear of placement in solitary confinement. Through interviews we will Identify ethical concerns and potential solutions for COVID-19 testing and vaccine strategies in correctional facilities using a community-engaged strategy. Goals: 1. Identify ethical concerns and potential solutions for COVID-19 testing and vaccine strategies in correctional facilities using a community-engaged strategy. 2. Characterize incidence of COVID-19, disease progression, and related-outcomes and effectiveness of testing and contact tracing in correctional facilities. Participant Selection: a. Potential subjects must be currently incarcerated at key facilities in Washington, Rhode Island, Minnesota, and Florida. These facilities are Everglades Correctional Institution and Homestead Correctional Institution in Florida, Shakopee and Stillwater correctional facilities in Minnesota, the Rhode Island Department of Corrections, and Yakima County Jail in Washington. b. Participating correctional facilities in Florida, Minnesota, Rhode Island, and Washington will provide de-identified data on approximately 16,859 incarcerated adults and correctional staff. Data sources include deidentified data from medical records, administrative data, and policy documents pertaining to COVID-19. c. 3 series of focus groups (6, 12, 18 months) x 3 distinct groups (incarcerated people, medical providers, and correctional leaders) x 4 sites=36 total focus groups over the study period. d. Will utilize 74,812 COVID-19 tests to test and re-test a total of 16,859 incarcerated people and correctional staff for active infection over a six-month period in the FL, MN, and RI state prison systems and the Yakima County Jail in WA.

  Study phs003361

• Whole-Genome sequencing of hepatocellular carcinomas

  The French ICGC project on liver tumors is coordinated by Pr Jessica Zucman-Rossi and funded by Inca (French Institute for Cancer). The aim of the present project is to identify the catalog of somatic and germline mutations in liver tumors using whole genome and whole exome sequencing together with CGH-SNP, methylome and transcriptomic profiling. For this purpose, a series of 500 liver tumors are collected through the French National Liver Collection and these samples will be analyzed using the different omics technologies. The data will be deposited in the ICGC and EGA database to be publically available for the scientific community. Hepatocellular carcinoma (HCC) accounts for more than 90% of liver cancers, and is a major health problem. It is the 3rd cause of cancer-related mortality. Advances in genomic analyses have formed a comprehensive understanding of different underlying pathobiological layers resulting in hepatocarcinogenesis. Thus, the development of next-generation sequencing technologies has made it possible to generate more comprehensive catalogues of somatic alteration events (single nucleotide substitutions, structural variations, and epigenetic changes) in liver cancer genome than ever before. The dataset will include 50 whole genome sequencing tumor/germline pairs, of which 6 are deposited in February 2014.

  Study EGAS00001000706

• HCA_Immune_PBMC_Teichmann_LK_RNA_managed_acces

  The aim of this study is to characterise CD8 T cell populations that are specific to prevalent viruses in the healthy blood donors. We obtained PBMC samples from a commercial supplier that have been HLA-typed and pre-tested for reactivity against EBV, CMV, and influenza using ELISPOT and peptide pool stimulation.

  Study EGAS00001007936

• Best Practices for DACs

  Best Practices Data access committees (DACs) are institutional safeguards responsible for ensuring a balance between data protection and accessibility. However, there are no procedural standards that apply across DACs, which can lead to inconsistencies in their reviews and compromise their quality and effectiveness. Standardising DAC processes can foster trust and mutual recognition, paving the way for greater coordination, collaboration, and delegation between DACs and other oversight bodies to improve the efficiency of data access without sacrificing protection. To provide guidance, the following are suggestions for actions a DAC might take upon receiving a data access request: Aim to respond to all initial requests in less than 2 weeks. Failure to do so may result in follow-up emails from the EGA, journals, and ultimately dataset withdrawal. First, check that the data/EGAD number is consistent with your data submission. In other words, ensure that the requester has contacted the correct DAC. Verify that the user will be using the data within the terms of consent by asking them to sign up to the terms within the DAA. Ensure that data users who are granted access to the data comply with the terms of a Data Access Agreement (DAA) and to use the data only in approved ways. Look for an institutional email address for the requester. Search for evidence that the requester is "appropriately qualified/bona fide" for using the data, for example on PubMed, Research Gate, LinkedIn, etc. Confirm that the affiliated organisation is real and that the requester still works there. Inquire with the requester about who should have accounts created at the EGA under the terms of the agreement. If a negative decision is made, promptly communicate it to the requester and support it with the terms of the Data Access Policy that the requester has not met or cannot meet. Keep the information in the DAC up to date. If you leave your institution and are unable to manage data access requests on their behalf, you should add your replacement as a new contact in the DAC. Assist with data access requests for any further questions related to your data. The EGA can only check information that has been deposited in the repository. If the user has a specific question that the EGA cannot answer, we will redirect the user to the DAC. All the EGA studies and datasets referenced in a publication under your DAC must be publicly searchable on the EGA website before the paper is released. If possible, describe the permitted purposes for subsequent research projects, including associated limits and conditions, for all resources hosted in a repository using a common ontology, such as the GA4GH Data Use Ontology (DUO). It is considered best practice to try and release data only to those with an institutional email address. This gives reassurance to the EGA, research participants, and the general public that an appropriate individual is accessing and using the data. 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.

  Documentation access/data-access-committee/best-practices

• Global Microbiome Conservancy Sequence Data

  The human body is a complex ecosystem, hosting tens of billions of bacteria, primarily in the gut. This community, known as the 'gut microbiome', is vital to human health, affecting functions ranging from metabolism, immunity, and development, to behavior. Conversely, reduced microbiome diversity and other imbalances of the gut community (dysbiosis) are associated with many diseases of the industrialized world, such as metabolic syndrome, asthma, and inflammatory bowel diseases among others. Microbiome-based interventions thus hold the potential to revolutionize our understanding of, and therapeutic approaches to, many aspects of human health and disease. Despite many advances, current understanding of the human microbiome is largely limited to majority ethnic groups in industrialized nations, and does not reflect the full diversity of human commensal microbiota. In addition to the scientific ramifications of minority underrepresentation, there are significant translational and ethical implications as well: first, failing to capture the full diversity of healthy human microbiota may limit our ability to understand and generate effective therapeutics for many microbiome-associated diseases. Second, underrepresented groups are less likely to benefit from microbiome-based medical advances tailored to well-studied populations, propagating healthcare inequities.  Human gut microbial diversity is diminishing around the globe, due to the spread of industrialized diets and lifestyles, which are associated with reduced microbiome biodiversity. The Global Microbiome Conservancy (GMbC) is a non-profit collaboration between scientists and communities around the world that aims to 1) preserve the full biodiversity of the human gut microbiome, 2) characterize its evolution across populations and host lifestyles and 3) investigate its interactions with the human host. We are collecting gut microbiome and human DNA samples from diverse populations around the world, from isolated groups to urbanized populations, to culture and study this essential biodiversity and to preserve it in a living "seed bank" of bacterial isolates as a long-term safeguard against future extinctions. Human genetic data for the samples sequenced in this study can be found in phs002205.

  Study phs002235

• MEC/SEF RNA-seq

  RNA transcript expression sequencing of 27 MEC/SEF tumor samples. Samples were sequenced at Beijing Genomics Institute. Prior to sequencing, rRNA removal library preparation was done for any samples that had degraded. Samples were sequenced on a DNBseq platform sequencer with a read length of 100PE, producing approximately ~40M raw reads (~8GB) raw data per sample.

  Dataset EGAD50000000761

• Duplex sequencing of 26 genes

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

  Dataset EGAD50000000998

• NHLBI TOPMed: Defining the Time-Dependent Genetic and Transcriptomic Responses to Cardiac Injury Among Patients with Arrhythmias

  The UMMS miRhythm Study is an ongoing study of adult patients undergoing an elective electrophysiology study or arrhythmia ablation procedure for a supraventricular or ventricular arrhythmia, including atrial fibrillation (AF). Atrial fibrillation is a major clinical and public health problem that is related to atrial pathologic remodeling. Few tools are available to quantify the activity or extent of this remodeling, rendering it difficult to identify individuals at risk for AF. Previous studies have suggested an important role for miRNA in cardiovascular disease through gene expression regulation, making this a promising avenue for studying AF mechanisms. The aim of the study is to determine the time-dependent changes to key circulating miRNAs in a model of planned atrial injury and remodeling via ablation. Such knowledge might provide additional insight into the biology and activity of the acute atrial injury response, and furthermore, inform new targets for development of preventative interventions or allow for better AF risk stratification. To assess pathways regulating atrial pathological remodeling, patient blood samples are collected prior to their ablation procedures and also at a regularly scheduled 1-month follow-up appointment. Plasma expression of miRNA is measured using high-throughput quantitative reverse transcriptase polymerase chain reaction (RT-qPCR), providing novel insights into the regulatory processes underlying AF, as well as acute atrial injury in vivo. Additionally, data collected from whole-genome sequencing (WGS) is used to supplement miRNA analyses and further explore new relations between genes and abnormal heart rhythm.

  Study phs001434

• Gabriella Miller Kids First Pediatric Research Program: An Integrated Clinical and Genomic Analysis of Treatment Failure in Pediatric Osteosarcoma

  The Gabriella Miller Kids First Pediatric Research Program (Kids First) is a trans-NIH effort initiated in response to the 2014 Gabriella Miller Kids First Research Act and supported by the NIH Common Fund. This program focuses on gene discovery in childhood cancers and structural birth defects and the development of the Gabriella Miller Kids First Pediatric Data Resource (Kids First Data Resource). Both childhood cancers and structural birth defects are critical and costly conditions associated with substantial morbidity and mortality. Elucidating the underlying genetic etiology of these diseases has the potential to profoundly improve preventative measures, diagnostics, and therapeutic interventions. All of the WGS and phenotypic data from this study are accessible through dbGaP and kidsfirstdrc.org, where other Kids First datasets can also be accessed. Although the survival of children with relapsed osteosarcoma is very poor, little is known about the etiology of treatment failure in this disease. The purpose of this project is to perform whole genome sequencing on serial samples from patients with osteosarcoma obtained before treatment, after treatment, and at relapse/metastasis in order to identify the mutations and pathways that are drivers of drug resistance. If successful, our results may help identify patients at high risk for treatment failure and may yield new treatments for children who cannot currently be cured.

  Study phs001714

• Efficacy of Ustekinumab Followed by Abatacept for the Treatment of Psoriasis Vulgaris (PAUSE)

  Psoriasis is a chronic immune disease of the skin and joints that affects about 2% of the population. The most common form of psoriasis is plaque psoriasis, also called psoriasis vulgaris. A variety of drugs, including biologics, are available for treatment of moderate to severe psoriasis. When biologic agents are stopped, psoriasis can return (relapse) and often requires the biologic to be restarted and continued. No treatment program has been identified to prevent relapse of psoriasis. The study design has a lead-in period of weight-based ustekinumab treatment, with all participants receiving either 45 mg ustekinumab ( 100 kg) administered subcutaneously at weeks 0 and 4. At week 12, participants will be assessed for a Psoriasis Area and Severity Index (PASI) 75 response to ustekinumab. Participants who do not achieve a PASI 75 score will be discontinued from the investigation and permitted to seek standard therapy.

  Study phs003395

• Anaplastic oligodendroglioma exome and RNA sequencing data

  Anaplastic oligodendrogliomas (AOs) are rare primary brain tumors which are generally incurable, with heterogeneous prognosis and few treatment targets identified. Most oligodendrogliomas have chromosome 1p/19q co-deletion and IDH mutation. We analyzed 51 AOs by whole-exome sequencing, identifying previously reported frequent somatic mutations in CIC and FUBP1. We also identified recurrent mutations in TCF12 and in an additional series of 83 AO. Overall 7.5% of AO are mutated for TCF12, which encodes an oligodendrocyte-related transcription factor. 80% of TCF12 mutations identified were in either the bHLH domain, which is important for TCF12 function as a transcription factor, or were frame shift mutations leading to TCF12 truncated for this domain. We show that these mutations compromise TCF12 transcriptional activity and are associated with a more aggressive tumor type. Our analysis provides further insights into the unique and shared pathways driving AO.

  Study EGAS00001001209

• Long-Term Outcome in Offspring and Mothers of Dexamethasone-Treated Pregnancies at Risk for Classical Congenital Adrenal Hyperplasia Owing to 21-Hydroxylase Deficiency

  Summary The purpose of this study is to perform the first long-term follow up study both of adolescents and young adults with a history of prenatal treatment with dexamethasone and of their mothers and to test for adverse medical or behavioral side effects. The emphasis will be on the outcome of this prenatal treatment in those fetuses who are not affected with steroid 21-hydroxylase deficiency (21OHD) form of congenital adrenal hyperplasia (CAH) and are either heterozygotes or homozygote-unaffected. Prenatal treatment of 46,XX fetuses with 21OHD (via administration of dexamethasone to the pregnant mother) has been shown to reduce the masculinization of the genitalia and, thereby, the later need for 'corrective' feminizing genital surgery and potential impairment of sexual functioning. Along with the suppression of excess prenatal androgen production and reduction of prenatal masculinization of the genitalia in 46,XX fetuses with 21OHD, prenatal dexamethasone treatment may reduce the behavioral masculinization that is well documented in untreated 46, XX patients with 21OHD. Those fetuses who are partially treated until diagnosis of an unaffected status (heterozygous or homozygous-unaffected) will be studied as well. This latter group is of importance because these fetuses are being unnecessarily treated, but we have no way of diagnosing the unaffected status before the 8th week of gestation when treatment must begin for the female fetus who is affected. As treatment is necessary only until term in the female fetus affected with classical CAH, male fetuses and unaffected or heterozygous female fetuses do not require treatment. Thus, only one out of eight fetuses will require prenatal treatment until term. Findings of adverse effects of glucocorticoid treatment in non-human mammals [1, 2] have raised concerns among other clinicians and investigators about potential adverse side effects of such treatment on the developing human. Thus, this study will address this concern and investigate the potential adverse side effects of prenatal treatment. Detailed Description Females with classical CAH owing to 21-hydroxylase deficiency are born with ambiguous genitalia due to the production of excess androgens in utero. Prenatal treatment with dexamethasone was inaugurated in 1978 by Maguelone Forest and has been the standard of practice in the United States since 1986. Dexamethasone, which crosses the placental barrier, suppresses the fetal adrenal gland production of androgens, thus preventing ambiguous genitalia in the affected female. Children of both sexes are prenatally treated as soon as pregnancies at risk are confirmed. Treatment in females with 21OHD continues to term, but is discontinued in males and unaffected females. To date, 685 pregnancies have been diagnosed, of which 366 fetuses were treated. These investigators will study prenatally treated adolescents and adults 12 years and older with respect to medical and behavioral outcomes (see Table 5). In addition, mothers of children prenatally treated for varying periods of time for suspected 21OHD will be studied for long-term side effects of dexamethasone treatment administered during pregnancy. The long-term outcome in these children and their mothers has never before been studied.

  Study phs001317

• Ataxia Gene Identification by Integrated Genomic Analysis

  Ataxias are a group of diseases that result in a lack of coordinated muscle movement. Hereditary ataxias are genetically heterogeneous and it is reported that 40% of suspected genetic ataxias currently have an unknown cause. We used exome sequencing to detect mutations responsible for ataxia. We sequenced, when available, multiple individuals per family to identify family specific mutations and further confirmed segregation of variants using samples from available affected and unaffected family members.

  Study phs000757