201 results for "fc coins kopen xbox Besuche die Website Buyfc26coins.com. Ohne Probleme, top..EgjF"

in 10.66 milliseconds.

• National Cancer Institute (NCI) Biospecimen Pre-analytical Variables (BPV) Analysis

  The Biospecimen Pre-analytical Variables (BPV) Program is a National Cancer Institute-sponsored study to systematically assess the effects of pre-analytical factors on the molecular profile of biospecimens. A robust biospecimen collection infrastructure was established to prospectively collect biospecimens using rigorous standard operating procedures to control for most variables while introducing experimental conditions to study specific biospecimen handling issues, including the cold ischemic time (delay to formalin fixation), time in formalin, freezing methods, and storage temperatures and durations. RNA and DNA from biospecimens collected under these conditions was analyzed on multiple molecular platforms. The potential effects of these pre-analytical conditions on protein integrity and detection of metabolites were also examined. Data from this study will be used to develop evidence-based biospecimen standard operating procedures and best practices for fit-for-purpose collection, processing, and storage of biospecimens. The BPV Cohort is utilized in the following dbGaP substudies. To view genotypes, analysis, expression data, other molecular data, and derived variables collected in these substudies, please click on the following sub-studies below or in the "Substudies" box located on the right hand side of this top-level study page phs001304 BPV Cohort. The substudy links will be active once they are released by dbGaP. Preanalytical Impacts on Global Metabolite Profiling - plasma (MassSpec by Metabolon) This study was to evaluate the impact of the storage temperature (s) (-80°C and LN2 vapor) and the length of storage on human plasma quality using LC-MS/MS (liquid-chromatography-mass spectrometry/mass spectrometry) based global metabolite profiling. The study includes 240 plasma samples collected from 40 donors. Investigate the effect of the delay to fixation on the proteome and phosphoproteome -FFPE (MassSpec by Caprion). The study is to do proteome and phosphoproteome analysis on Delay to fixation was carried out using FFPE tumor samples from colon and ovarian cancer patients comparing 2, 3, and 12hr delay to fixation to the 1hr time point. The study includes 100 samples 20 donors. Investigate the effect of storage conditions of tumor specimens on the proteome and phosphoproteome profiling- Frozen tissue and plasma (MassSpec by Caprion). The study was to evaluate the effects of storage conditions on tumor specimens. Plasma samples from 40 cancer patients stored at two different temperatures (-80°C and LN2) for a given period (0-2, 6-8, and 12-14 months) were evaluated. Frozen kidney tumor samples from 20 patients were compared for effects of different snap frozen (dry ice vs. LN2) and storage temperatures (-80°C and LN2). The study includes 100 tissue and 240 plasma samples from 60 donors. Preanalytical Impacts on Genomic Sequencing by Next Generation Sequencing (NGS) technology (mRNA/miRNA and WES by Expression Analysis). The goal of the study is to determine the effects of cold ischemic delay-to-fixation (4 time points) and formalin preservation (FFPE) on the nature and quality of genomic profiles using the matched freshly frozen sample as the gold standard, which including WES, RNAseq. The study includes 395 samples from 37 donors. Preanalytical Impacts on Copy Number Variation (CNV) Detection by aCGH technology (aCGH by Georgetown University). This study was to use aCGH to evaluate the effect of variation in cold ischemia time and time in formalin fixation on CNV in DNA extracted from kidney cancer specimens. The study includes 235 samples from 40 donors. Evaluation of frozen conditions on mRNA profiling by TaqMan assay (mRNA expression by Georgetown University). This study was to utilize gene expression profiling, using custom TaqMan arrays, to compare the molecular profiles of RNA from frozen tumor samples collected using two freezing methods (dry ice or LN2), two storage temperatures (-80°C or LN2 vapor), as well as Optimal Cutting Temperature (OCT) compound and non-OCT embedded. The study includes 100 samples from 20 donors. mRNA signature for stratification by cold ischemia time (mRNA expression by IBBL). The study was to determine the effects of cold ischemic time (delay-to-fixation) and formalin preservation (FFPE) on mRNA detection by Taqman assay using tumor tissue specimens from kidney, colon and ovarian cancer patients. There are160 samples from 40 donors. The Biospecimen PV cohort is utilized in the following dbGaP individual studies. To view molecular data, and derived variables collected in these individual studies, please click on the following individual studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs001304 Biospecimen PV cohort. phs001634 CIT mRNA phs001635 CNV aCGH phs001636 Fixation Delay phs001637 Global Metabolite Profiling phs001638 mRNA TaqMan phs001639 NGS phs001640 Tumor Storage

  Study phs001304

• Coronary Artery Risk Development in Young Adults (CARDIA) Study - Cohort

  CARDIA is a study examining the etiology and natural history of cardiovascular disease beginning in young adulthood. In 1985-1986, a cohort of 5115 healthy black and white men and women aged 18-30 years were selected to have approximately the same number of people in subgroups of age (18-24 and 25-30), sex, race, and education (high school or less and more than high school) within each of four US Field Centers. These same participants were asked to participate in follow-up examinations during 1987-1988 (Year 2), 1990-1991 (Year 5), 1992-1993 (Year 7), 1995-1996 (Year 10), 2000-2001 (Year 15), 2005-2006 (Year 20), and 2010-2011 (Year 25); the proportions of the surviving cohort that have returned for the seven follow-up examinations were 90%, 86%, 81%, 79%, 74%, 72%, and 72%, respectively. In addition to the follow-up examinations, participants are contacted regularly for the ascertainment of information on out-patient procedures and hospitalizations experienced between contacts. Within the past five years, 95% of the original surviving cohort has been contacted. While the specifics of each examination has differed somewhat, data have been collected on a variety of factors believed to be related to heart disease. These include conditions with clear links to heart disease such as blood pressure, cholesterol and other lipids. Data have also been collected on physical measurements such as weight and skinfold fat as well as lifestyle factors such as substance use (tobacco and alcohol), dietary and exercise patterns, behavioral and psychological variables, medical and family history, and other chemistries (e.g., insulin and glucose). In addition, subclinical atherosclerosis was measured via echocardiography during Years 5, 10, and 25, computed tomography during Years 15 and 20, and carotid ultrasound during Year 20. The CARDIA Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs000285 CARDIA Cohort. phs000236 PAGE_CALiCo_CARDIA phs000309 GENEVA_CARDIA phs000399 GO-ESP HeartGO_CARDIA phs000613 CARDIA_CARe

  Study phs000285

• Genetic Modifiers of Huntington's Disease

  Huntington's disease (HD) is a neurodegenerative disorder typically diagnosed in mid-life that is caused by expansion of an otherwise polymorphic CAG trinucleotide repeat. The mutation causes a gain-of-function of the huntingtin protein to trigger a pathogenic process that produces detectable phenotypic differences many years before the traditional diagnosis, which is based upon characteristic motor symptoms. The prediagnosis phase of pathogenesis is now the subject of intense scrutiny by an NINDS-funded longitudinal study, PREDICT-HD, in which undiagnosed gene carriers are followed longitudinally and subjected to detailed phenotyping (PREDICT-HD Huntington Disease Study -- dbGaP Study Accession: phs000222). This powerful approach, which offers the potential for moving the focus of therapeutic development to the decades prior to neurological disease diagnosis, is enabled by the fact that all individuals with HD have the same type of mutation, which can be determined at any time in life by a single HD CAG repeat PCR amplification assay. The precise length of the HD CAG repeat differs between individuals. There is a strong negative correlation between the number of CAG repeats and the age at onset of diagnostic neurological abnormalities in HD, such that the CAG repeat accounts for ~50% of the variation in age at diagnosis. Analysis of the remaining variance not explained by the length of the CAG repeat has shown that it is highly heritable, being due to genetic variation, elsewhere in the genome. The intent of the Genetic Modifiers of Huntington's Disease study is to identify genetic modifiers of HD pathogenesis by using genomewide association techniques in diagnosed HD individuals to identify genetic factors associated with the residual variance in age at onset not explained by the CAG repeat, and to extend these analyses to pre-diagnosis phenotypes, for example, those defined in the PREDICT-HD study. Identification of modifier genes is a top priority for HD research (and an example of an approach that can be applied in other late-onset genetic disorders), as it could provide clues to developing rational treatments that delay or prevent the pathogenic process from causing the ravages of the disease that ensue in the ~15 years of inexorable decline to ultimate death that now follows clinical diagnosis. To further that goal, the release of study version 2 makes available whole exome sequencing data of n=221 study participants.

  Study phs000371

• Genetic Epidemiology of COPD (COPDGene) Funded by the National Heart, Lung, and Blood Institute

  Chronic obstructive pulmonary disease (COPD) is the fourth leading cause of death in the United States and the only leading cause of death that is steadily increasing in frequency. This project will establish a racially diverse cohort that is sufficiently large and appropriately designed for genome-wide association analysis of COPD. A total of 10,000 subjects will be recruited, including control smokers, definite COPD cases (GOLD Stage 2 to 4), and subjects not included in either group (GOLD 1 or GOLD-Unclassified). This cohort will be used for cross-sectional analysis, although long-term longitudinal follow-up will be a future goal. The primary focus of the study will be genome-wide association analysis to identify the genetic risk factors that determine susceptibility for COPD and COPD-related phenotypes. Detailed phenotyping of both cases and controls, including chest CT scan assessment of emphysema and airway disease, will allow identification of genetic determinants for the heterogeneous components of the COPD syndrome. The hypotheses to be studied are: 1) Precise phenotypic characterization of COPD subjects using computed tomography, as well as clinical and physiological measures, will provide data that will enable the broad COPD syndrome to be decomposed into clinically significant subtypes. 2) Genome-wide association studies will identify genetic determinants for COPD susceptibility that will provide insight into clinically relevant COPD subtypes. 3) Distinct genetic determinants influence the development of emphysema and airway disease. The initial phase of genome-wide association analysis included 500 COPD cases and 500 control subjects (all non-Hispanic White) genotyped with the Illumina Omni-1 chip. The second phase genotyped the entire study cohort using the Illumina Omni-Express chip. Unique aspects of the study include: 1) Inclusion of large numbers of African American subjects (approximately 1/3 of the cohort); 2) Obtaining chest CT scans (including inspiratory and expiratory images); and 3) Inclusion of the full range of disease severity. The COPDGene_v6 Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" box located on the right hand side of this top-level study page phs000179 COPDGene_v6 Cohort. phs000296 ESP LungGO COPDGene phs000765 COPDGene_Geno

  Study phs000179

• Sudden Cardiac Death in Heart Failure Trial (SCD-HeFT-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives The Sudden Cardiac Death in Heart Failure Trial (SCD-HeFT) was designed to evaluate the hypothesis that amiodarone or a conservatively programmed shock-only, single-lead implantable cardioverter defibrillator (ICD) would decrease the risk of death from any cause in a broad population of patients with mild-to-moderate heart failure. Background Patients with congestive heart failure (CHF) can die suddenly and unpredictably from arrhythmia despite the use of proven medical therapies, such as beta-blockade. Two approaches have been developed to prevent sudden death among patients with CHF: therapy with amiodarone and therapy with an ICD. However, most of the mortality data on amiodarone and ICD therapy at the time of the study had been obtained in clinical trials performed after myocardial infarction in patients without CHF or those with ventricular arrhythmias. Thus, more data was needed to guide these therapies in patients who did not meet these criteria. Participants There were a total of 2521 participants. 847 were randomly assigned to placebo, 845 to amiodarone, and 829 to ICD therapy. Design Before randomization, participants underwent electrocardiography, a 6-minute walk test, 24-hour ambulatory electrocardiography, liver and thyroid function studies, and chest radiography. Participants were required, if clinically reasonable, to receive treatment with a beta-blocker and an angiotensin-converting-enzyme inhibitor, as well as an aldosterone antagonist, aspirin, and statins, when appropriate. Participants were randomly assigned in equal proportions to receive placebo, amiodarone, or a single-chamber ICD programmed to shock-only mode. Participants assigned to amiodarone or matching placebo began therapy as outpatients immediately after randomization. Placebo and amiodarone were administered as a loading dose of 800 mg/day for one week, 400 mg/day for three weeks, and then as a daily maintenance dosage according to weight and bradycardia status. Participants assigned to ICD therapy received their device a median of three days after randomization. The goal of ICD therapy was to treat only rapid, sustained ventricular tachycardia or ventricular fibrillation. Dual-chamber or biventricular devices, or antitachycardia or rate-response pacing therapies were not permitted. The ICD was uniformly programmed to have a detection rate of 187 beats per minute or more. Antibradycardia pacing was initiated only if the intrinsic rate decreased to less than 34 beats per minute. Median follow-up was 45.5 months. The primary end point was death from any cause. Secondary outcome measures included cardiac mortality, arrhythmic mortality, morbidity, quality of life, and incremental cost-effectiveness of the interventions. Each active treatment arm was compared to the placebo drug arm. Conclusions In participants with NYHA class II or III CHF and LVEF of 35% or less, amiodarone had no favorable effect on survival, whereas single-lead, shock-only ICD therapy reduced overall mortality by 23%.

  Study phs003654

• Resuscitation Outcomes Consortium (ROC) Trauma Epidemiologic Registry (Trauma Epistry) (ROC-Trauma Epistry-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Available Data: This dataset only includes traumatic injury participants. For ROC cardiac arrest Epistry data please see: ROC-Cardiac Epistry 1 and 2 and ROC-Cardiac Epistry 3.Objectives: To build a prospective population-based registry of participants with out-of-hospital traumatic injury responded to by Emergency Medical Services (EMS). Specific aims included: to establish whether the results of Resuscitation Outcomes Consortium (ROC) trials can be generalized to the larger population of people that experience traumatic injury; to more fully establish the burden of traumatic injury; and to examine the relationships between variation in EMS structure and process, regional and periodic factors, and participant outcomes.Background: Traumatic injury is a major public health problem generating substantial morbidity, mortality, and economic burden on society. The majority of seriously injured persons are initially evaluated and cared for by prehospital providers, however the effect of EMS systems, EMS clinical care, and EMS interventions on trauma patient outcomes is largely unknown. EMS factors such as service level, number of responding providers, use of procedures or drugs in the field, training, quality assurance/feedback, and response time intervals also vary significantly by region.The Resuscitation Outcomes Consortium (ROC) was established in 2004 to conduct clinical research in the areas of cardiopulmonary arrest and life-threatening traumatic injury with the overall goal of improving resuscitation outcomes. Previous trauma registries have generally focused primarily on hospitalized patients with limited prehospital information. Registries may also exclude trauma cases at far ends of the spectrum, such as those who die in the field or in a non-trauma center and/or patients that are treated and released. These limitations do not allow for detailed, outcome-based assessments of EMS system factors necessary to define prehospital resuscitation best practices. Therefore there was a need for standardized data collection of out-of-hospital traumatic injuries matched to hospital-based outcomes in diverse geographic locations in order to identify the independent effects of prognostic or treatment factors accounting for variations in survival. Participants: The registry included 13,830 traumatic events from 264 EMS agencies transporting to 287 acute care hospitals from the following regional centers: Birmingham, Alabama; Dallas, Texas; Iowa City, Iowa; Milwaukee, Wisconsin; Pittsburgh, Pennsylvania; Portland, Oregon; San Diego, California; Seattle/King County, Washington; Ottawa, Ontario; Toronto, Ontario; and Vancouver, British Columbia.Design: ROC Epistry collected standardized data regarding episode-specific factors, participant demographics, clinical information, pre-hospital interventions and disposition, hospital information, and participant outcome for all out-of-hospital traumatic injuries in the ROC regions. Cases were identified through review of emergency response system records including dispatch centers, EMS ground agencies, and air medical services. Out-of-hospital data were extracted from existing databases whenever possible and augmented with targeted review of EMS reports. Hospital data were abstracted directly from the hospital file in most cases. Sites submitted data using a web-based interface or batch uploads (Newgard, et al., 2008, PMID: 18482792).

  Study phs003809

• Privacy Notice for Helpdesk service

  Privacy Notice for EGA Helpdesk service This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by dr. Thomas Keane, by: email at: tk2@ebi.ac.uk or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org , or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? We process your personal data on the grounds of important public interest. For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from users of the service: Name Email address Job title Date and time when the support request was sent We will use your personal data for the following purposes: To provide uninterrupted user access to the service To better understand the needs of the users and guide future improvements of the service To create anonymous usage statistics 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? There are no personal data transfers to third countries or international organizations. 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration. Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period. Request information to understand data processing activities when the results of these activities are applied to you. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. Published at: February 6, 2019

  Documentation data-protection/privacy-notice/ega-helpdesk

• 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

• Genome-Wide Association Studies of Prematurity and Its Complications

  Preterm labor resulting in the delivery of a premature child is a complex problem with an enormous impact on individuals, families and society. An estimated 500,000 children are born prematurely in the U.S. each year, and 5 million worldwide die annually of prematurity and its complications. Prematurity is also the single largest contributor to disability-adjusted life years, a measure of the lifetime impact of a disease. Despite the importance of the problem and its disproportionate occurrence in poor and minority populations, its underlying etiology (or etiologies) remains unknown; the single best predictor for preterm delivery is a previous preterm birth. The largest single cause of prematurity is spontaneous preterm labor, and suspected triggers for this include infection, stress, poor nutrition and genetic factors. Family and twin studies provide strong evidence that genetic factors underlie about 40% of the risk for prematurity. A major challenge in studying genetic factors in prematurity is maternal/uterine factors, fetal/placental factors, or both may influence risk. Thus, any approach to studying preterm birth should account for both infant and maternal risk, environmental covariates and interactions. The Danish National Birth Cohort (DNBC) is a well-established, prospective cohort that enrolled women early in pregnancy, prior to any adverse pregnancy outcomes, to minimize bias in data collection and sampling. See details at: http://www.ssi.dk/English. The DNBC followed over 100,000 pregnancies beginning in the first trimester and has extensive biological material and epidemiologic data on health outcomes in both mother and child. The current study posted on dbGaP contains data from a genome-wide case/control study using approximately 1,000 preterm mother-child pairs from the DNBC most with spontaneous onset of labor or preterm premature rupture of membranes (PPROM), along with 1,000 control pairs where the child was born at ~40 weeks' gestation. After data cleaning some small changes in case/control status and other variables resulted in minor changes in numbers of cases or controls in certain categories. Environmental variables are being used as covariates in the analysis. To replicate positive findings, we are using additional mother-child pairs from the DNBC and from the general Danish population, as well as 2200 samples coming primarily from an African-American population known to have high rates of preterm labor and delivery. This group includes over 1000 mostly very low birthweight infants, over 500 infant term controls, 326 term mother/baby pairs and 180 preterm mother/baby pairs. The data from these additional cohorts will be available in separate dbGaP postings. The study is expected to yield a better understanding of the biology of parturition, identify common genetic factors that play a role in preterm birth and its complications and suggest environmental modifications that can prolong gestation, with the goal of improving both neonatal and adult outcomes. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to prematurity and its complications through large-scale genome-wide association studies of a well-characterized cohort of Danish mothers and babies. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were done at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000103

• Data Quality Control

  Data Quality Control High-throughput sequencing techniques have become the leading method to study, decode and discover the genomic origins of biological phenomenons. EGA provides a secure archival of such identifiable genomics data with the purpose of data-upcycling, i.e. to re-use these data for research. High-quality data standards are essential to ensure the quality and credibility of the research. Moreover, a quality check report can assure a researcher beforehand about the data that they will request access, therefore saving time and effort. The EGA has developed a File Quality Control Report (QC Report) to provide generic quality control reports for Fastq, SAM/BAM/CRAM, and VCF files deposited at EGA. This QC Report will allow users to get information regarding the files submitted within a specific dataset. The data requesters will obtain information such as the quality of reads, mapped reads, number of variants, and other features before starting the requesting process, which will save the efforts and time.Accessing file quality control reportsIn each dataset page, the user can explore the files that it contains by clicking the "files" tab. The Quality Control report of a file has two sections. The first one, contains general information about the file, such as the inferred assembly, total reads, the dataset or study where it comes from, etc. The second section contains plots that summarise interesting information about the file, for example, the base coverage distribution, base quality or mapped reads. The description of each plot is accessible by clicking the "i" button at the top-right corner of each plot box. Technical Description For analysing the fastq, SAM/BAM/CRAM and VCF files, the EGA applies a set of tools widely used in the bioinformatics community. FASTQ: FastQC, recognised as the gold standard tool by the community.Per base sequence quality, per sequence quality scores, per base sequence content, per sequence GC content, sequence duplication levels, etc.SAM/BAM/CRAM: samtools, also the gold standard, generates results plots useful to get an overall idea of the quality of the file.base coverage distribution, base quality, % of mapped reads, % of both mates mapped, singletons, duplicates, etc.VCF: vcftools and bcftools, combined with a custom script to infer the genome assembly.site frequency distribution, Ts/Tv, base changes, indel distribution, etc.

  Documentation access/request-data/quality-control-reports