Search Results - EGA European Genome-Phenome Archive

Resource for Genetic Epidemiology Research on Adult Health and Aging (GERA)

The Resource for Genetic Epidemiology Research on Aging (GERA) Cohort was created by a RC2 "Grand Opportunity" grant that was awarded to the Kaiser Permanente Research Program on Genes, Environment, and Health (RPGEH) and the UCSF Institute for Human Genetics (AG036607; Schaefer/Risch, PIs). The RC2 project enabled genome-wide SNP genotyping (GWAS) to be conducted on a cohort of over 100,000 adults who are members of the Kaiser Permanente Medical Care Plan, Northern California Region (KPNC), and participating in its RPGEH. The purpose of the RPGEH is to facilitate research on the genetic and environmental factors that affect health and disease by linking together clinical data from electronic health records, survey data on demographic and behavioral factors, and environmental data from various sources, with genetic data derived from biospecimens collected from participants. At the time of the award of the RC2 project in late 2009, the RPGEH had established a cohort of about 140,000 individuals who had answered a detailed survey, provided saliva samples for extraction of DNA, and given broad consent for the use of their data in studies of health and disease. To maximize the diversity of the resulting sample, the GERA cohort was formed by including all racial and ethnic minority participants with saliva samples (N = 20,925; 19%); the remaining participants were drawn sequentially and randomly from white non-Hispanic participants (89,341; 81%). A total of 110,266 participant samples were included to ensure that at least 100,000 were successfully assayed. The resulting GERA cohort is 42% male, 58% female, and ranges in age from 18 to over 100 years old with an average age of 63 years at the time of the RPGEH survey (2007). The sample is ethnically diverse, generally well-educated with above average income. Approximately 69% of the participants are married or living with a partner. Length of membership in KPNC averages 23.5 years. UCSF and RPGEH investigators worked with the genomics company Affymetrix to design four custom microarrays for genotyping each of the four major race-ethnicity groups included in the GERA Cohort, described in detail in Hoffmann et al., 2011a and 2011b. Following genotyping and quality control procedures, and after removal of invalid, discordant, or withdrawn samples, about 103,000 participants were successfully genotyped. The resulting genotypic data were linked to survey data and data abstracted from the electronic medical records. As described below, all RPGEH participants were mailed new consent forms with explicit discussion of the placement of data in the NIH-maintained dbGaP. About 77% of participants returned completed consent forms, resulting in a final sample size of 78,486 participants in the GERA Cohort with data for deposit into dbGaP. Origins of the RPGEH GERA Cohort The goal in creating the RPGEH GERA cohort was to create a large, multiethnic, and comprehensive population-based resource for research into the genetic and environmental basis of common age-related diseases and their treatment, and factors influencing healthy aging and longevity. The GERA Cohort consists of a diverse cohort of more than 100,000 adults who are members of the Kaiser Permanente Medical Care Plan, Northern California Region (KPNC), and participating in its Research Program on Genes, Environment and Health (RPGEH). KPNC is an integrated health care delivery system with a population of about 3.3 million people in northern California. The membership of KPNC is representative of the general population in the 14 county area in which facilities are located, although the membership is underrepresented for the extremes of income at both ends of the spectrum. The RPGEH utilizes the longitudinal electronic health records (EHR) of KPNC to obtain clinical, laboratory, imaging and pharmacy information on all cohort members, to which personal demographic, behavioral and health characteristics have been added through member surveys. The GERA Cohort comprises a subsample of the RPGEH participant cohort, and was created through the RC2 award from the NIA, NIMH, and NIH Common Fund as described above. GERA Study Design The GERA Cohort is a subsample, as described above, of the longitudinal cohort enrolled in the Kaiser Permanente RPGEH. The RPGEH cohort includes about 400,000 survey participants of whom about 200,000 have provided broad consent and a sample of saliva or blood for use in studies of genetic and environmental factors in health and disease. The GERA Cohort was developed from a mailed survey sent to all adult members of KPNC who had been members for two years or more in 2007. All survey respondents were contacted and asked to complete a consent form; those who completed consent forms were asked to provide a saliva sample. Additional male participants were added to the RPGEH through inclusion of the Northern California sample of the California Men's Health Study (CMHS) cohort of about 40,000 men from KPNC, ages 45-69 years old at the time of the CMHS survey in 2002-2003. The CMHS participants contributed about 15,400 saliva samples to the RPGEH and were eligible for inclusion in the GERA Cohort. CMHS participants were included according to the same sampling design as for the RPGEH cohort as a whole. Specifically, all minority participants were selected for inclusion in order to maximize representation of minorities in the GERA Cohort, and Non-Hispanic White participants were selected at random to complete the sample of 110,266 GERA Cohort participants. GERA Genotypic Data High-density genotyping was conducted at UCSF using custom designed Affymetrix Axiom arrays, as described in Hoffmann et al. (2011a; 2011b). To maximize genome-wide coverage of common and less common variants, four specific arrays were designed for individuals of Non-Hispanic White (EUR), East Asian (EAS), African-American (AFR), and Latino (LAT) race/ethnicity. There was broad overlap among the SNPs on the arrays, which were designed using a hybrid greedy imputation algorithm (Hoffmann et al., 2011b) applied to genotype information validated by Affymetrix from the 1000 Genomes Project. However, in order to capture low frequency variants specific to particular race-ethnicity groups, SNP content varies between arrays. A more detailed description of the process of genotyping and results is included in Genotyping of DNA Samples. Description of the analyses of population structure and development of principal components for adjustment of population structure is included in Population Structure Analysis. GERA Phenotypic Data RPGEH and CMHS Survey Data. The sources of data on demographic and behavioral factors deposited in dbGaP for the GERA Cohort are the RPGEH and CMHS surveys. Data on common demographic factors such as gender, race/ethnicity, marital status, and education and on behavioral factors such as smoking, alcohol consumption, and body mass index, have been cleaned, edited, reconciled between the two surveys, and compiled into summary indices, where appropriate, for deposition into dbGaP. A more complete description of the survey variables is included in Survey Variables Documentation. Please note that the terms of use of the GERA Cohort Data, as specified in the Data Use Certification (DUC), prohibit the use of survey variables as outcomes in analyses. For example, a genome-wide association study (GWAS) of education or smoking is not permitted as specified by the DUC. Only health conditions can be used as outcome variables in analyses. Health Conditions derived from Kaiser Permanente Electronic Medical Records. Data on the occurrence of health conditions in participants in the GERA Cohort have been derived from summarizing ICD-9 coded diagnoses in Kaiser Permanente's electronic medical records. An algorithm that aggregates specific ICD-9 codes into appropriate diagnostic groups for selected conditions is applied to outpatient and inpatient databases; see Disease and Conditions Definitions Documentation for details. The criterion for including a condition as "present" for a participant is the occurrence of two or more diagnoses within a diagnostic category occurring on separate days. Two or more is used as the criterion in order to reduce false positives due to mistakes or rule-out diagnoses. When compared with validated disease registries, the criterion of 2+ diagnoses yields high specificity and good sensitivity. ICD-9 codes in the electronic records are specified in several ways. For outpatient visits occurring during the period 1995 to 2006, diagnoses were assigned by the treating physician who endorsed specific diagnoses on an optically scanned list that varied by specialty. Beginning in 2006 with the advent of an integrated, fully electronic medical record, outpatient diagnoses are made by physicians/ providers using a pull down menu. Discharge diagnoses from inpatient stays are specified by physicians and coded by specially trained coders. Databases of ICD-9 codes for diagnoses assigned at outpatient visits, or as one of the discharge diagnoses following inpatient stays, are complete and available for all KPNC members dating back to 1995. Although the average length of KPNC membership among GERA cohort members is 23.5 years in 2007, not all have been members since 1995, so the history for some conditions, such as those that are not chronic or recurrent, may not be complete for all cohort members. The year of first membership in KPNC is included as a variable in the list of survey variables, enabling investigators to estimate the number of years of observation of each Cohort member. RPGEH Access and Collaborations Website and Procedures The RPGEH maintains a web portal for inquiries and applications for collaboration and access to data. The url is: https://rpgehportal.kaiser.org/. RPGEH has an application process and an Access Review Committee that reviews applications for collaboration and use. For more details, please contact RPGEH through the website.

Study phs000674

Security Overview

Security Overview The European Genome-phenome Archive (EGA) houses consented human data under controlled access. Access decisions are handled by the relevant Data Access Committee (DAC), which autonomously manages requests through the DAC Portal. This document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. As security is a prime concern of the EGA, the EGA is a member of the Global Alliance for Genomics and Health (GA4GH) Data Security work stream. The EGA contributes and helps develop the recommendations outlined the GA4GH Security Technology Infrastructure document, which defines guidelines, best practices, and standards for building and operating an infrastructure that promotes responsible data sharing in accordance with the GA4GH Privacy and Security Policy. Explore the EGA dataflow to gain deeper insights! Accessing data in the EGA involves several steps. First, users need to create an EGA account. Once logged in, they can request access to data controlled by a DAC through the EGA website (see documentation). The DAC oversees these requests through the DAC Portal, and if approved, grants the necessary permissions to the user's EGA account, allowing them to access and download all relevant data and metadata for the requested dataset(s). The key points of EGA security strategy are: 1 Regular Risk Assessment The EGA regularly identifies and assesses risk related to the following: Breach of confidentiality,Breach of privacy or autonomy,Malicious or accidental corruption or destruction of data archived at EGA,Disruption of services provided by the EGA. 2 Risk mitigation The EGA implements and maintains safeguards to minimise the risks identified above in accordance with the 6 control objectives listed in Appendix 1 and outlined in the GA4GH Security and Infrastructure document.If a breach is discovered, the EGA applies a defined protocol to minimise damage. 3 Identity and authorisation management The EGA authenticates the identity of individuals or software accessing controlled access data held at the EGA.The EGA ensures an appropriate level of assurance (LoA) is applied to the identity consistent with the risk associated with that individual, such as multi-factor authentication for DACs.The EGA provides the minimum access rights and privileges consistent with the user’s identity, allowing access consistent with the GA4GH Privacy and Security Policy, as determined by the appropriate DAC. 4 Audit Logs The EGA maintains a set of logs recording: Changes to user access rights,Data access requests,Resource usage. 5 Cryptography, communication security, and data integrity The EGA ensures data transmission integrity using a hash function.All data transmitted to or from the EGA is end-to-end encrypted.All data at EGA is stored using strong encryption.Encryption keys are not stored in the same system as the encrypted data.All data archived at EGA must be accompanied by a signed submission statement ensuring appropriate consent or ethical approval has been obtained, and is in accordance with all applicable laws and regulations. The EGA has a defined protocol defining the response in the event of a security breach, and is continuing to work with the GA4GH Data Security Work Stream to help define best practice and associated standards for breach responses. Appendix 1 GA4GH Control Objectives Control Objective 1: Implement technology safeguards to minimise the risk of unauthorised access, use, or disclosure of confidential and private data.Control Objective 2: Implement technology safeguards to minimise the risk of discovery, access, and use of individuals’ clinical and genomic data, and individual identities, other than as authorised by applicable jurisdictional law, institutional policy, and individual consents.Control Objective 3: Implement technology safeguards to minimise the risk of accidental or malicious corruption or destruction of data.Control Objective 4: Implement technology safeguards to minimise the risk of disruption, degradation, and interruption of services enabling access to data.Control Objective 5: Implement technology safeguards to minimise the risk of potential security attacks and misuse of authorised accesses and privileges.Control Objective 6: Implement technology safeguards to promptly detect the failure to attain the above control objectives and to respond with proper countermeasures.Appendix 2Refer to the document below to learn more about EGA long-term data preservation policy and procedures at EMBL-EBI.Long-term data preservation

Documentation about/security

Better Outcomes for Children: GWAS from Cincinnati Children's Hospital Medical Center (CCHMC) - eMERGE Phase II data - (dbGaP Deposit 1)

This submission includes genotyping data from 6 separate cohorts (named A-E here), each is described in separate paragraphs below. Cohort A) Autism is a neurodevelopmental disorder that affects 1.5 million people in the United States, at an estimated lifetime cost of $4 million. It is part of Pervasive Developmental Disorder characterized by impairments in communication, language and reciprocal social interaction, and by unusual patterns of restricted and repetitive interests or behaviors. Autism, or autistic disorder, is the most severe form of the disease which has a wide range of symptom severity encompassed by the more inclusive term, Autism Spectrum Disorder (ASD). The prevalence of Autistic Disorder is currently estimated to be 4 per 1000, affecting 4 times more boys than girls. Susceptibility to autism is clearly attributable to genetic factors but the extensive clinical and genetic heterogeneity within the disorder have hindered efforts at genetic dissection. Identifying the genetic variants that contribute to this highly heritable disease is crucial to advancing research on autism. Reported concordance rates among monozygotic twins range from 60% − 90% and heritability of autism has been estimated to be 90% or greater. Identifying genetic variants that contribute to this highly heritable disease is crucial to advancing research on autism. Cohort B) The long-term objective of this research is to determine the molecular genetic basis of Cardiovascular (CV) disease in the young; this study seeks to identify gene mutations that cause "structural heart defects". Every year in the USA, 32,000 individuals are born with CV malformations; approximately 20% die during the first year of life. Another 30,000 young people develop a disturbance of cardiac rhythm or conduction. In addition, the life expectancy of another 40,000 young people is shortened by other forms of CV disease. It is becoming more apparent that in spite of the success in diagnosis and treatment, very little is known about the causes of CV disease in the young; understanding the causes will permit insight into the pathophysiologic basis of disease and allow definition of disease risk - two critical elements for disease prevention. Disease prevention and/or risk modification promises to be the new frontier in the management of CV disease in the young. Cohort C) Eosinophilic Esophagitis (EE) is one of the manifestations of eosinophilic gastrointestinal inflammation which have profound effects on a patient's health and development. Results of epidemiologic studies performed through our center demonstrate that eosinophil-associated gastrointestinal disease is not an uncommon entity. While the epidemiology of eosinophilic esophagitis has not been thoroughly studied until recently, there appears to be a significant increase in the diagnosis of EE in the last decade. Based on our research, this mainly reflects increased disease recognition, but there is also a bona-fide increase in disease incidence which coincides with the increasing incidence of asthma and allergic diseases in the industrialized world. In addition, many patients with intractable symptoms thought in the past to represent atypical GERD or other disorders are now being recognized as having EE. Diagnosis of EE requires endoscopy and biopsies to document the characteristic histologic findings of esophageal eosinophilia. In general, this study proposed to elucidate the mechanisms underlying eosinophil growth, survival, migration, and function, and to investigate and further characterize the pathophysiology of, clinical manifestations of, and spectrum of disease severity of eosinophilic esophagitis in humans. Cohort D) Juvenile idiopathic arthritis (JIA) is a debilitating complex genetic disorder characterized by inflammation of the joints and other tissues and shares histopathological features with other autoimmune diseases. It is considered a complex genetic disorder. There are more than 50,000 children with JIA in the USA, approximately 1 per 1000 births, which is about the same incidence as juvenile diabetes. It is believed that genes in the major histocompatibility complex (MHC) play a role in defining genetic risk, and it can be hypothesized that loci in other chromosomal regions are involved in conferring risk in JIA. These candidate chromosomal regions can be identified using genome wide association analyses. The long-term goal is a comprehensive understanding of the genetic basis of these disabling arthropathies for which the molecular basis is not presently understood. The results of recent GWAS for Caucasian JIA were recently published in Arthritis Rheum. 2012 Feb 21 (Published online, PMID=22354554). Cohort E) Childhood Absence Epilepsy (CAE) is characterized by very frequent (several to many per day) absence seizures in an otherwise normal child with an EEG usually demonstrating 3 Hz bilateral, synchronous, symmetrical spikewaves pattern with normal background activity. CAE occurs in 10% to 15% of all children with epilepsy with an annual incidence of 6.3 to 8/100,000 in children <15 years of age. Females are more affected than males. Epilepsy onset is typically between the ages of 4 to 8 years with a peak incidence of 6 to 7 years. CAE does not start after age 13 years. The primary objective of this study is: To identify the optimal anticonvulsant (i.e. the antiepileptic drug (AED) with highest rate of seizure control and lowest incidence of treatment limiting toxicity) used for the initial treatment of children with Childhood Absence Epilepsy (CAE). The secondary objectives are: To determine the pharmacogenetic and other non-heritable factors underlying the interindividual variation in anticonvulsant response efficacy and toxicity. To define and contrast the effects of ethosuximide, lamotrigine, and valproic acid monotherapy on cognition (attention), behavior and quality of life in children with Childhood Absence Epilepsy. Cohort F) Cincinnati Controls. These are local healthy children selected to be representative of the population of Cincinnati with respect to gender and ancestry. Cohort G) Cytogenetics cases are ascertained by the clinical request to obtain cytogenetic analysis. The platform used included genotyping data which are then available for genome wide association analysis

Study phs000494

Health and Retirement Study (HRS)

Introduction to V2: This data release comprises data from the V1 release combined with approximately 3,000 additional samples, collected during the HRS 2010 field period. The 2010 data include samples from a random half of the new cohort enrolled in 2010 along with a significant expansion of the minority sample. Description: The University of Michigan Health and Retirement Study (HRS) is a longitudinal panel study that surveys a representative sample of approximately 20,000 people in America over the age of 50 every two years. Supported by the National Institute on Aging (NIA U01AG009740) and the Social Security Administration, the HRS explores the changes in labor force participation and the health transitions that individuals undergo toward the end of their work lives and in the years that follow. The study collects information about income, work, assets, pension plans, health insurance, disability, physical health and functioning, cognitive functioning, and health care expenditures. Through its unique and in-depth interviews, the HRS provides an invaluable and growing body of multidisciplinary data that researchers can use to address important questions about the challenges and opportunities of aging. Because of its innovation and importance, the HRS has become the model and hub for a growing network of harmonized longitudinal aging studies around the world. Origins of the HRS. As the population ages it is increasingly important to obtain reliable data about aging and topics that are relevant to a range of policy issues in aging. To address this need, the National Institutes on Aging (NIA) established a cooperative agreement with the University of Michigan Institute for Social Research to collect such data. The HRS launched data collection in 1992 and has re-interviewed the original sample of respondents every two years since then. By adding new cohorts and refreshing the sample, the HRS has grown to become the largest, most representative longitudinal panel study of Americans 50 years and older. HRS Study Design. The target population for the original HRS cohort includes all adults in the contiguous United States born during the years 1931-1941 who reside in households, with a 2:1 oversample of African-American and Hispanic populations. The original sample is refreshed with new birth cohorts (51-56 years of age) every six years. The sample has been expanded over the years to include a broader range of birth cohorts as well. The target population for the AHEAD survey consists of United States household residents who were born in 1923 or earlier. Children of the Depression (CODA) recruits households born 1924-1930, War Babies 1942-47, Early Boomers 1948-53, and Mid-Boomers 1954-59. Data collection includes a mixed mode design combining in-person, telephone, mail, and Internet. For consenting respondents, HRS data are linked at the individual level to administrative records from Social Security and Medicare claims. Genetic Research in the HRS. The HRS has genotyped 2.5 million single nucleotide polymorphisms (SNPs) on respondents using Illumina's Human Omni2.5-Quad (Omni2.5) BeadChip. The genotyping was performed by the NIH Center for Inherited Disease Research (CIDR). Saliva was collected on half of the HRS sample each wave starting in 2006. In 2006, saliva was collected using a mouthwash collection method. From 2008 onward, the data collection method switched to the Oragene kit. Saliva completion rates were 83% in 2006, 84% in 2008, and 80% in 2010 among new cohort enrollees. HRS Phenotypic data. Phenotypic data are available on a variety of dimensions. Health measures include physical/psychological self-report, various health conditions, disabilities, cognitive performance, health behaviors (smoking, drinking, exercise), physical performance and anthropomorphic measures, and biomarkers (HbA1c, Total Cholesterol, HDL, CRP, Cystatin-C). Data are also available on health services including utilization, insurance and out-of-pocket spending with linkage to Medicare records. Economic measures include employment status/history, earnings, disability, retirement, type of work, income by source, wealth by asset type, capital gains/debt, consumption, linkage to pensions, Social Security earnings/benefit histories. There is also extensive information on family structure, proximity, transfers to/from of money, time, social and psychological characteristics, as well as a wide range of demographics. Performance on a cognitive test combining immediate and delayed word recall was selected as an example trait for the dbGaP data release. In the immediate word recall task the interviewer reads a list of 10 nouns to the respondent and asks the respondent to recall as many words as possible from the list in any order. After approximately five minutes of asking other survey questions, the respondent is asked to recall the nouns previously presented as part of the immediate recall task. The total recall score is the sum of the correct answers to these two tasks, with a range of 0 to 20. Researchers who wish to link to other HRS measures not in dbGaP will be able to apply for access from HRS. A separate Data Use Agreement (DUA) will be required for linkage to the HRS data. See the HRS website (http://hrsonline.isr.umich.edu/gwas) for details.

Study phs000428

Women's Health Initiative Clinical Trial and Observational Study

The Women's Health Initiative (WHI) is a long-term national health study that has focused on strategies for preventing heart disease, breast and colorectal cancer, and osteoporotic fractures in postmenopausal women. The original WHI study included 161,808 postmenopausal women enrolled between 1993 and 1998. The Fred Hutchinson Cancer Research Center in Seattle, WA serves as the WHI Clinical Coordinating Center for data collection, management, and analysis of the WHI. The WHI has two major parts: a partial factorial randomized Clinical Trial (CT) and an Observational Study (OS); both were conducted at 40 Clinical Centers nationwide. The CT enrolled 68,132 postmenopausal women between the ages of 50-79 into trials testing three prevention strategies. If eligible, women could choose to enroll in one, two, or all three of the trial components. The components are: Hormone Therapy Trials (HT): This double-blind component examined the effects of combined hormones or estrogen alone on the prevention of coronary heart disease and osteoporotic fractures, and associated risk for breast cancer. Women participating in this component with an intact uterus were randomized to estrogen plus progestin (conjugated equine estrogens [CEE], 0.625 mg/d plus medroxyprogesterone acetate [MPA] 2.5 mg/d] or a matching placebo. Women with prior hysterectomy were randomized to CEE or placebo. Both trials were stopped early, in July 2002 and March 2004, respectively, based on adverse effects. All HT participants continued to be followed without intervention until close-out. Dietary Modification Trial (DM): The Dietary Modification component evaluated the effect of a low-fat and high fruit, vegetable and grain diet on the prevention of breast and colorectal cancers and coronary heart disease. Study participants were randomized to either their usual eating pattern or a low-fat dietary pattern. Calcium/Vitamin D Trial (CaD): This double-blind component began 1 to 2 years after a woman joined one or both of the other clinical trial components. It evaluated the effect of calcium and vitamin D supplementation on the prevention of osteoporotic fractures and colorectal cancer. Women in this component were randomized to calcium (1000 mg/d) and vitamin D (400 IU/d) supplements or a matching placebo. The Observational Study (OS) examines the relationship between lifestyle, environmental, medical and molecular risk factors and specific measures of health or disease outcomes. This component involves tracking the medical history and health habits of 93,676 women not participating in the CT. Recruitment for the observational study was completed in 1998 and participants were followed annually for 8 to 12 years. Extension Studies: The original protocol allowed for follow-up until March 2005, after which participants were invited to enroll in the first WHI Extension Study for follow-up through 2010. Participants were invited again to participate in the second WHI Extension Study with continued follow up from 2010 to at least 2015. As of March 31, 2011 there were 93,122 women enrolled in the second extension. In Extension Study 2, the overall WHI study population was divided into two new subsamples, the Medical Records Cohort (MRC) and the Self-Report Cohort (SRC). The MRC consists of all former hormone trial participants and all African American and Hispanic participants from all study components. The SRC consists of the remaining participants. The extent of outcome information collected differs between the two cohorts, with more extensive outcomes information collection on the MRC. As part of Extension Study 2, selected older WHI participants were invited to participate in an In Person Visit (a.k.a., Long Life Study) at their homes during which additional blood samples were collected and various measurements were taken (such as blood pressure, height, weight, waist circumference, grip strength, etc.). In October 2015, Extension Study 2 was renewed with continued follow-up planned through October 2020, pending annual contract review and renewal. Additional Information: The WHI website, https://www.whi.org/about/SitePages/About%20WHI.aspx has much more information about the study. For WHI data collection forms used over the years, please see https://www.whi.org/researchers/studydoc/SitePages/Forms.aspx. For additional dataset documentation, see https://www.whi.org/researchers/data/Pages/Available%20Data.aspx. For data preparation and use, please refer to 'WHI dbGaP Cohort Data Release Data Preparation Guide May 2018' for additional details about the WHI data. The WHI 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 substudies below or in the "Substudies" box located on the right hand side of this top-level study page phs000200 WHI Cohort. phs000386 WHI SHARe phs000281 GO-ESP WHISP phs000315 WHI GARNET phs000503 WHISE phs000227 PAGE WHI phs000675 WHIMS+ phs000746 WHI Harmonized and Imputed GWAS phs001334 WHI Metabolomics of CHD phs001335 WHI BA23 phs001614 WHI LLS Phase III GWAS

Study phs000200

All you need to know about our new DAC Portal v2

An updated version to boost the management of DACs (Data Access Committees), policies, and data access requests. In September of 2023, we launched new services for all EGA users, including a DAC Portal. Since then, our team has been working to refine it and improve the user experience. The version 2 of our DAC Portal is now ready, with a range of new features aimed at streamlining your workflow and boosting productivity. If you are interested in learning more about the latest version of our DAC Portal, then you are in the right place! In this post, you will find information about the implemented features and more. The full documentation is available on our website. Moreover, we highly recommend exploring the DAC Portal through the Take the Tour. This said, let's get cracking! Customise your data access requests table This table offers the possibility to tailor information about the data access requests by making visible or hiding different columns regarding the Dataset Persistent Identifier, the Organisation or the requestor's name s, among others. You can choose which columns to see, depending on your needs and interests. Additionally, we have implemented two new features columns with two new functionalities, DAC Comment and Expiration Date. You can find more details in the following sections! In this table, all data access requests are displayed by default. With the latest version of the Portal, you can now apply filters, combine them, and save them for future use. Leave internal comments on pending requests and visible to all the DAC Members We understand that many Data Access Committees (DACs) cannot instantly approve or deny data access requests. Often, there's an intermediary phase where discussions and the signing of legal documents are necessary. To facilitate this process, we've introduced the DAC comment feature! When you navigate to the DAC column, you'll find two tabs: "User" and "DAC". Under "User", you'll see the message provided by the requester at the time of requesting access to the data. As a DAC member/admin, you can then add an internal comment in the "DAC" tab. These comments are visible only to DAC members/admins, ensuring confidentiality. Requesters won't have access to DAC comments. By adding a DAC comment to a pending request, we'll know that you've begun reviewing it. This allows you to filter pending requests without DAC comments to focus on genuinely new requests, and it prevents you from receiving email notifications about ongoing data requests. Set expiration dates for permissions and revoke them automatically The latest update to the DAC Portal introduces a new feature allowing you to set expiration dates for new access requests. For instance, if you anticipate approving a data access request but only wish to grant access for a limited time, you can now specify an expiration date for the granted permissions. Once this date is reached, the permissions will automatically be revoked. By default, permissions are granted indefinitely without an expiration date. However, if you ever need to revoke permissions, you can easily do so from the History page. Audit your metadata objects Managing and auditing your metadata objects will be easier from now on as the new DAC Portal enhances and facilitates your role as a Data Controller. This is possible thanks to the tables available in each of the primary tabs visible on the homepage: DACs, Policies and Datasets. Starting with DACs, this section allows to check the policies linked to a specific DAC. In Policies, you can obtain a list of the datasets connected to a particular policy. In the Dataset tab, it is possible to group datasets by either DAC or Policy, as well as the release status. Now you have the option of deprecating metadata objects that you don’t want to use anymore, or that were created by mistake. You will find the deprecate button on the EDIT page of the DAC, as well as for registered policies. You can find more information here. What's neat about this feature is that once a DAC or policy is deprecated, it becomes hidden within the DAC Portal. This ensures that you only see information that is consistently up to date! Define your preferences regarding email notifications For pending requests, you will be able to decide how often you want to get the notifications: daily, weekly or fortnightly. Remember, you will not receive email notifications for pending requests with a DAC comment! Furthermore, you have the flexibility to decide which notifications you wish to receive, such as invitations to join a new DAC or notifications regarding DAC acceptance by the Helpdesk, among other options. Check the User preference to see the complete list of available notification settings! What’s next: incoming DAC Portal API 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 consult the DAC API specification. This post was written by Aina Jené and Ana T. Alonso.

Blog new-dac-portal-v2

Submission FAQ

Submission FAQ Before Submission Is the EGA the right archive for my data? TThe most suitable archive for your data is dependent on the type of data you are wishing to submit and whether the data require public or controlled access. Public access is defined as complete and open access to all submitted data. On the contrary, controlled access, exerted by the EGA, requires formal applications to be made to access the submitted data files and metadata. EGA only accepts human-derived data subject to controlled access. If your submission contains other types of data, please choose the appropriate repository for it (see image below): ENA, EVA, ArrayExpress, BioSD and GWAS catalog. Should your submission be subjected to controlled access? Data access conditions are normally defined in the original informed consent agreements signed by the participants involved in your study. All data submitted to the EGA is subject to controlled access. These consents prevent the derived data files, potentially identifiable, from being dispersed by open and public access. Controlled access data often refers to human data derived from medical research and consortium projects. If in doubt, consult the informed consent agreements that apply to your study The EGA enables you to hold a submission before publication. What data types can be submitted to the EGA? Data types accepted by the EGA can be split into three categories: Sequences: both in generic and platform-specific formats. Array-based: from raw signal files to processed matrices. Phenotypes: all possible phenotype formats are accepted. All manufacturer-specific raw data formats derived from major next generation sequencing platforms are accepted. Also generic sequence formats: flat reads in a FASTQ file, aligned sequences (BAM or CRAM files) as well as sequence variation files in VCF format. All array-based technologies are accepted, including raw data, intensity and analysis files, without any restriction on data formats accepted. We also accept and distribute phenotype data (associated to the samples) in almost any format: from an image to a README file. How long does a submission take? Submissions to EGA come in a variety of formats and sizes, thus it is difficult for us to exactly predict how long a submission will take. We, therefore, advise all of our submitters to allow as much time as possible to make a submission. Based on previous records, we anticipate that the submission process may take at least one month. The submitter’s familiarity with the procedures, possible technical issues that may arise during submission and the amount of data that is being submitted are the main factors that will affect the length of the submission process. However, each step of a regular submission should be considered when estimating the time it would take: Encryption of the files Upload of the files Metadata submission Archival of the files Release of the study and datasets to EGA webpage For example, the upload of the files depends on the submission size, while metadata submission mainly relies on each submitter’s expertise. Further, some steps (e.g. answering to inquiries) depend on the EGA Helpdesk team, which may take some days to be processed during busy times Is data deposited in the EGA secure? The EGA set-up consists of a secure computing facility for data processing, a shared EBI set-up for data submissions and distribution of data via data requests made through the EGA website. Data is also copied in the Barcelona Supercomputing Center (BSC) infrastructure, where all stored and distributed data is encrypted Data is encrypted along the submission process and stored securely, granting its access to authorised users exclusively. During the download process, through our Python Client or Aspera, all requested data is downloaded over secure https connections. All data at the EGA is encrypted, and only accessible (for log-in and download) through secure protocols. For further information please, visit our security overview. What documentation do I need to provide? All submissions require policy’s documentation: 'Data Access Agreement (DAA)', 'Data Processing Agreement (DPA)' and 'Authorized Submitters Formulary'. The data processors (EGA) and the data owners will also sign the DPA. Will all metadata be public? Among the submitted metadata we need to make the distinction between identifiable and unidentifiable metadata: (1) the former may allow the identification of the human the sample derived from (e.g. detailed geographical providence, personal name, family ancestry…); (2) while the latter can be used to interpret the data without compromising the anonymity of the patients. The majority of the metadata submitted to the EGA corresponds to the unidentifiable category (e.g. sequencer's model). This type of metadata is publicly available on the EGA website and other EBI resources/partners’ websites. On the other hand, some parts samples’ metadata are subject to being identifiable, and thus only accessible by authorized data requesters, with the exception of: 5 submitter-defined attributes of the sample: alias, title, subject_id, gender and phenotype. It is the submitter’s responsibility not to submit sensitive metadata in these public fields. 3 anonymised fields that pinpoint the sample record in archivals: sample’s EGA stable ID (EGAN…), BioSample ID (SAMEA…) and submitter’s center name. During Submission Are there any sample specific requirements for EGA? All samples submitted to the EGA must include the attributes of biological sex, subject ID (anonymised individual identifier) and phenotype information. These are critical for data findability and its analysis, and we highly recommend using controlled ontology terms where applicable. For example: defining tumour and non-tumour samples and/or defining disease state. The EGA recommends using the Experimental Factor Ontology Database to find ontologized terms that describe your sample phenotypes. How do I get an accession number to use in my publication? You will receive your study accession number (EGAS…) upon complete your submission, either: Programmatically. As soon as the metadata is submitted and validated your study will be assigned an accession number that will be given in the submission’s response. Manually registering your study and relevant metadata using the online metadata submission tool: the EGA submitter Portal. How are files uploaded to the EGA? Data files are uploaded into private submission drop boxes (i.e. environments to which you are granted access and where you can transfer your files) using INBOX or FTP. These spaces are provided as part of the submission procedure. Before uploading any file, you must encrypt your files, . Only encrypted files shall be uploaded to the drop boxes. Why does data need to to encrypted for my submitted files? It is one of the security steps the EGA has implemented. In case of a security breach, people without the proper encryption key will not be able to read or use the information that could have been leaked. This measure is essential when working with sensitive data, such as controlled access human data. All submitters must use crypt4gh to create EGA compliant files prior to uploading them. This encryption is GPG-based, using EGA’s public key. Why are my files not available if I see them in the INBOX? There exists a time window between the data upload and the availability of such files via the Submitter Portal. For this reason, some metadata (run and analysis objects) cannot be registered until at least 24 hours after the files have been uploaded to your box. Why are MD5 sum values generated for my submitted files? We require pre- and post- encryption MD5 (message-digest) checksum values to be provided for all submitted files. These 128-bit values are computed using the content of each file, creating unique sequences that allow us to ensure that file integrity has been maintained during the transfer process. In other words, if the MD5 checksums we generate and those you generated match, we infer that the content of the transferred files is correct (i.e. files are not corrupted or truncated). MD5 checksums are computed automatically using the crypt4gh tool provided. Your submission will not be accepted and may be significantly delayed if you do not provide MD5 checksum values for all data files in the required format. How can I check if my files are correctly uploaded to the inbox? It is important to check the status pf your file so you know whether your files are in the inbox, being processed, or if there is any issue with one of them. In order to check this, you should: Look for the file locally. Drag and drop it to the file table. Then bars will appear on the table, which means that we are processing it. Green: The files checksum are correct and your file will move to “ingested files”. No further actions are needed from your end.. Red: The files checksum does not match and your file needs to be re-uploaded. Please re-upload relevant files to your inbox using the same path. After Submission How do I use my accession number in my publication? We suggest the use of the below template, using your study accession ID (EGAS…) : Data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found at https://ega-archive.org and "The European Genome-phenome Archive of human data consented for biomedical research" Your study ID will be the one that groups your whole submission, and thus its usage is recommended as such. Nevertheless, all metadata submitted to EGA hold a unique and persistent identifier (starting with EGA…) that can be used to identify specific records. For example, you could reference a specific dataset (EGAD…) or sample (EGAN…) in your publications (see full list of identifiers). How do I make my data searchable? Once you have finalized your submission, you can schedule the data release. Please take into account that the release process needs time for the files to be archived in our system, and for the Helpdesk team to validate your submission. Can I withdraw (meta)data from the EGA? We have methods in place for the secure removal of deposited (meta)data. Contact EGA-helpdesk for further details. EGA complies with FAIRness of (meta)data, and thus, even when the data is removed we keep an entry for their identifiers in our system. In other words, we execute a soft delete on canceled objects (e.g. a study): metadata is still stored in our systems, but it loses all links, cannot be queried and data files cannot be retrieved anymore. The reason behind this behaviour is so that queries using withdrawn data properly respond back (see example of a canceled study). What happens to the data once it has been submitted to the EGA? When the data is submitted, the submitter can choose either keep their data private or schedule the release of their data.

Documentation submission/metadata/submission/FAQ

How to request data

Request Data Access If you're looking to access data from the EGA for your research, you are in the right documentation page! In this page you will find a step by step guide on how to request data archived at the EGA, as well as some frequently asked questions you might find useful. When requesting data, you'll need to provide information about your research project and intended use of the data. Keep in mind that your data access request may require additional approvals or agreements depending on the datasets and data providers involved. Step by step guide Register yourself as an EGA user. Validate your account. A validation link will be sent to your email to activate your EGA user account. Log into the EGA page. Search the dataset of interest from the dataset catalogue or search bar. Click on “Request access” Add a comment requesting these files and send your request Your request is successfully registered, and the DAC will receive a notification about your request In addition to submitting your request, you should also contact the DAC directly via e-mail. You can access the DAC's contact information from the relevant dataset page. Frequently Asked Questions (FAQ) Which is the role of the EGA in the data access process? The European Genome-phenome Archive (EGA) facilitates the secure distribution under controlled access of personally identifiable genetic and phenotypic data. Data Access Committee (DAC) is a body of one or more individuals who are responsible for data release to external requestors, based on participant consent and/or National Research Ethics terms. How do I request access to multiple datasets? To request access for multiple datasets managed by the same Data Access Committee (DAC), please start by visiting the DAC catalogue to locate the DAC of your choice. Once you've found the relevant DAC, proceed to its dedicated page where you'll find a "Request access" button. After logging in to the EGA website, you'll be presented with a comprehensive list of datasets under the chosen DAC. Select the datasets you're interested in, and then compose a message indicating your access request. Click the "Send" button to submit your request, which will include the chosen datasets. Please be sure to review the data usage policies for the requested datasets, as policies can vary among datasets managed by the same DAC. I am a co-applicant. Will I be given a joint access account? Each applicant needs to create an EGA account themselves, with unique login details. User log-in details are for individual use only and should never be shared, under any circumstances. EGA services are only provided to EGA account holders. Therefore, the co-applicant will send a formal request to the DAC. What happens if a co-applicant leaves or a new member needs to be added to an existing DAC application? The appropriate Data Access Committee (DAC) should be contacted and informed about the required changes so that the application can be updated. I have changed my place of work since my EGA account was created. Can I still have access to data? You must contact the relevant Data Access Committee (DAC). The DAC did not reply to my data access request. How should I proceed? There is no estimated time for DAC response. Please allow up to four weeks for a response. In the meantime, please send them a weekly reminder of the status of your request by emailing them directly.If the DAC becomes unresponsive, meaning that they fail to communicate with a requestor within the specified time frame, please contact the EGA Helpdesk team. I have an account with the EGA and would like access to further datasets. How should I proceed? You need to reapply to the relevant Data Access Committee (DAC). Once the DAC has approved your application your account will be updated and an email will be sent to notify you of a change made to your account. How do I download files of the datasets I have been granted access to? The preferred method for data download and decryption is the EGA Secure Download Client. Please carefully review the provided documentation. How do I download metadata? Metadata is retrieved from the EGA webpage; you will not need to use any download client. Be informed that you will only be able to download metadata of your approved datasets. For such download, you should first log in the EGA webpage with your credentials. Then browse the metadata's dataset you have gained access and you will find a metadata download button. You may also want to have a look our metadata schema. I have forgotten or misplaced my user account password; how do I get a new one? Click on “Log in”, located in the top right corner of the EGA homepage. Then click “Forgot password”, type in your registered institutional email address, and instructions for resetting your password will be sent to you. Please check both regular and junk/spam folders. I was sent a link to set a password for my download account, but it seems like the link has expired. What should I do? The procedure is the same as the one for a forgotten password, explained in the previous question.

Documentation access/request-data/how-to-request-data

Demographically Diverse Substance Use Disorder Cohorts of Dr. Stanley H. Weiss

The Demographically Diverse Substance Use Disorder Cohorts of Dr. Stanley H. Weiss, which constitute the Epidemiology of the Weiss Cohort Projects, consist of a series of inter-connected projects, building upon a set of cohort projects of various groups, mainly drug users from medication-assisted treatment programs, that Dr. Stanley H. Weiss first developed in the 1980’s plus several newer initiatives, each with an array of collaborators. Beginning in the 1980’s, Dr. Stanley H. Weiss started several long-term studies of persons who inject drugs (PWID) across the United States, ultimately enrolling over 10,000 participants through the early 1990’s with an average age then in their 30’s. About a quarter were enrolled from sites in New Jersey (NJ). These studies included the first testing of PWID for the human immunodeficiency virus (HIV) and the human T-cell lymphotropic viruses (HTLV I and HTLV II). Cumulative past support (initiation thru ~ 1999) for these cohort studies included ~ $20 million from intramural resources from the National Cancer Institute (NCI) and the National Institute on Drug Abuse (NIDA), plus multiple grants and in-kind support from the New Jersey Department of Health (NJDOH) totaling ~ $1 million. The Weiss Cohort Projects include the first large AIDS-era cohorts to include women at high risk for HIV. A high percentage of subjects in these studies are black or Latino. Thus, this is an ethnically diverse US cohort, with a high proportion of women included. These subjects are at high risk of parenteral and sexual infection from both drug use and sexual practices. Samples from other studies conducted by Dr. Weiss, in which detailed interviews were conducted, are included as controls (persons documented by us not to have a history of opioid drug use). As one of our groups of subjects have many persons of Haitian ancestry, we specifically included some Haitians who had never used opioids as controls. Our documentation includes such ancestry. These cohorts demonstrated high rates of HIV and HTLV-II infection in PWIDs, including one study initiated in 1981 with confirmation in the later cohorts. In the first two decades of these studies, among numerous publications was the first study showing a very high rate of hepatitis C infection among PWIDs. An example of how the studies’ long-time horizon proved essential was that it first became possible to test whether a person had ever been infected with hepatitis C virus (HCV), as well as how much HCV was in each person’s blood, many years after the specimens were collected. This allowed HCV amounts in blood to be compared for subjects who had died of liver disease early in the study versus those who survived. Then a sequence of published papers culminated in demonstrating, using a nested case-control design, that a high baseline HCV titer was predictive of early progression to death from end-stage liver failure. Outcomes related to HCV (end stage liver disease and hepatocellular carcinoma) remain under study. In the original cohort studies, the mean age at enrollment was ~ 33 years old, so that those still alive in 2022 are mainly now ~ 60 - 75 years old. Many participants have already died. The tincture of time has led to subjects reaching ages when many more are dying from a wide array of outcomes, including from many chronic diseases (including cancer) as well as from infectious agents (especially HIV, HCV) or drug overdose. Renewed collaboration with local drug treatment programs has led to new field-based studies, including examination of some currently evolving problems among drug users. Dr. Weiss joined the National Institute on Drug Abuse (NIDA) Genetics Consortium (NGC) in 2017, and through the NIDA project officer has had access to NGC contract resources (see below). NIH Certificate of Confidentiality, CC-DA-16-214 (attached) protects these studies. Past arrangements related to data on our subjects leads to restrictions on the use of data emanating from our study, such as potential commercialization and restrictions on whom may access and use these data. NIDA Genetics Consortium (NGC) resources further support these endeavors and will be used as part of the NGC analyses studying the genetics of substance use. Study participants signed informed consent for the information collected from them to be used with no time limit and for biologic specimens collected from them to be used without restriction in future research. Serum samples were collected from participants, and from many also plasma, white blood cells and/or urine samples. About 100,000 vials were stored. All specimens have been continuously preserved at sufficiently cold temperatures to prevent deterioration, and many subjects separated white blood cells were processed and frozen in such a way as to maintain viability. Detailed data from the participants has been accumulated over time, and in general, linkage has been retained in each sub-study in accordance with the consent forms and protocols. For some participants, specimens were collected at multiple times (that is, sequential specimens). Multiple specimens from a single person exist in this database, and efforts at de-duplication remain ongoing. Dr. Weiss should be contacted if an investigator requires unique individuals since: • Multiple phases of enrollment occurred, and as our prospective follow-up continues; Dr. Weiss may identify new instances of multiple enrollment. • Some persons are related to each other. • In general, in this dataset for dbGaP, only a single specimen/record form a given person is included. Advances in laboratory testing techniques now permit innovative new uses for our linked research biospecimen repository. The ongoing focus of an interdisciplinary research program based on these cohorts relates subjects’ diseases, behaviors, medical history, and outcomes with biological and exposure markers. Participants’ use of various substances was ascertained on study enrollments, many serially over time. Quantitative frequency of use data, also sometimes sequential over time, were ascertained. Active ascertainment of outcomes is being conducted, including matching to mortality and cancer databases. Investigators interested in collaborations on specific outcomes (which is not part of this dbGaP dataset) or in the use of our stored specimens are encouraged to contact the principal investigator, Dr. Weiss. The processing of the genomic data was done in conjunction with NIDA, and in accordance with some longstanding data cleaning steps used by NIDA in the NIDA Genetics Consortium (NGC), a group to which we shall be contributing these data for collaborative analyses. Since there is the potential for these steps to introduce certain types of potential biases, we summarize these here. Under contract from NIDA, cryopreserved sera or plasma (-80 C) or cells (in liquid nitrogen) were used, with most stored having been stored for 30 to 40 years in our biorepository. In the case of serum or plasma, in which only (largely) cell-free DNA fragments were available, DNA was extracted and restored prior to amplification. Industry standard DNA amplification techniques were done on all samples prior to genotyping in accord with established protocols of the NIDA Genetics Consortium. Our genotype data were run and processed on the Illumina Infinium OmniExpress_v_1.3 array. This array has 714,238 SNPs, and was designed many years ago. There were 628 SNPs on the array that do not correspond to any chromosome position, and these were removed. Genotype data were submitted by NIDA’s contracted genotyping laboratory in six batches over time to NIDA’s contracted dbGaP data management group, which conducted quality control (QC) analyses. QC analysis included an assessment of batch effects on for five of the six batches. (One of the batches, with only 12 samples, was too small for QC analysis of batch effects.) Standard NIDA Genetic Consortium cleaning was performed. Samples with a call rate <.85 were removed. Only one sample per person was retained. When more than one specimen was genotyped from one subject, only the sample with the higher call rate was retained (provided, of course, that that call rate was ≥ 0.85). We have retained some people we know are related, including some found to have been related through genotyping; the pedigree file describes those relationships. In summary, key cleaning steps include: 1. Using PLINK to check gender discrepancy. 2. Using PREST-PLUS and KING (Kinship-based Inference for GWAS) to check relatedness. 3. Using PEDCHECK and PLINK to check/zero-out Mendelian error. 4. Using PLINK to perform sample QC, SNP QC, along with KING to perform chromosome X and chromosome Y QC. 5. SNP-QC: Batch-effect: 5 Batches were compared (one batch, with few samples, was not). These five batches were compared to each other in all ten possible pairs, one batch vs. another batch, examining SNP allele frequency discrepancies by population (from GRAF), Fisher Exact Allelic test, with the criterion of p<5e-8 for removal. 6. SNP-QC: discordant SNPs in QC duplicates. Compared 25 QC duplicated samples with call rate > 0.95, removed SNPs with 3+ discordance. 7. There were 1,056 SNPs that were monomorphic; these have been retained so they can be included in analyses in which our dbGaP data are combined with those from other cohorts (in the latter of which those SNPs may not be monomorphic). The final cleaned dataset submitted has 8,898 samples and 606,793 SNPs.

Study phs002140

Action to Control Cardiovascular Risk in Diabetes (ACCORD - Imaging)

Available DataAction to Control Cardiovascular Risk in Diabetes (ACCORD-Imaging), provides access to ECG signals data from the ACCORD clinical trial. The clinical phenotyping and outcomes data from the trial are associated with ACCORD-BioLINCC, phs003551.ObjectivesThe purpose of this study was to determine if intensive glycemic control, multiple lipid management and intensive blood pressure control could prevent major cardiovascular events (myocardial infarction, stroke or cardiovascular death) in adults with type 2 diabetes mellitus. Secondary hypotheses included treatment differences in other cardiovascular outcomes, total mortality, microvascular outcomes, health-related quality of life and cost-effectiveness.BackgroundGlycemia Trial:Patients with type 2 diabetes mellitus die of cardiovascular disease (CVD) at rates two to four times higher than non-diabetic populations of similar demographic characteristics. They also experience increased rates of nonfatal myocardial infarction and stroke. With the growing prevalence of obesity in the United States, CVD associated with type 2 diabetes is expected to become an even greater public health challenge in the coming decades than it is now. Expected increases in event rates will be associated with a concomitant rise in suffering and resource utilization.The ACCORD study investigated whether intensive therapy to target normal glycated hemoglobin (HbA1c) levels would reduce cardiovascular events in patients with type 2 diabetes who had either established cardiovascular disease or additional cardiovascular risk factors when compared to standard therapy (HbA1c between 7.0% and 7.9%). A separate analysis investigated whether reduction of blood glucose concentration decreases the rate of microvascular complications in these patients.Lipid Therapy Trial:Patients with type 2 diabetes mellitus have an increased incidence of atherosclerotic cardiovascular disease attributable, in part, to associated risk factors such as dyslipidemia. This is characterized by elevated plasma triglyceride levels, low levels of high-density lipoprotein (HDL) cholesterol and small, dense low-density lipoprotein (LDL) particles. The ACCORD Lipid Therapy trial was designed to test the effect of a therapeutic strategy that uses a fibrate to raise HDL-C and lower triglyceride levels and uses a statin for treatment of LDL-C reduce the rate of CVD events compared to a strategy that only uses a statin for treatment of LDL-C on cardiovascular outcomes in patients with type 2 diabetes that were at high risk for cardiovascular disease.Blood Pressure Trial:Diabetes mellitus increases the risk of cardiovascular disease at every level of systolic blood pressure. Because cardiovascular risk in patients with diabetes is graded and continuous across the entire range of levels of systolic blood pressure, even at prehypertensive levels, the Seventh Report of the Joint National Committee on Prevention, Detection, Evaluation, and Treatment of High Blood Pressure (JNC 7) recommended beginning drug treatment in patients with diabetes who have systolic blood pressures of 130 mm Hg or higher, with a treatment goal of reducing systolic blood pressure to below 130 mm Hg. There is, however, a paucity of evidence from randomized clinical trials to support these recommendations. The ACCORD Blood Pressure trial tested the effect of a target systolic blood pressure below 120 mm Hg on major cardiovascular events among high-risk persons with type 2 diabetes compared to a strategy that targeted a SBP of EYE Substudy:Diabetic retinopathy, an important microvascular complication of diabetes, is a leading cause of blindness in the United States. Randomized, controlled clinical trials in cohorts of patients with type 1 diabetes and those with type 2 diabetes have shown the beneficial effects of intensive glycemic control and intensive treatment of elevated blood pressure on the progression of diabetic retinopathy. Elevated serum cholesterol and triglyceride levels have been implicated, in observational studies and small trials, as additional risk factors for the development of diabetic retinopathy and visual loss. The ACCORD EYE Substudy evaluated the effects of the ACCORD medical strategies on the progression of diabetic retinopathy in a subgroup of trial patients.MIND Substudy:Studies suggest that older persons with type 2 diabetes have at least twice the likelihood of developing late-life cognitive impairment or dementia compared to those without. The mechanisms underlying these cognitive disorders are increasingly thought to reflect a mixed pathology pattern with contributions from vascular, neurodegenerative and neurovascular processes. Pathophysiological mechanisms that have been described include inflammation, oxidative stress, energy imbalance, protein misfolding, glucocorticoid-mediated effects and differences in genetic susceptibilities. The ACCORD MIND substudy took as a premise that early intervention with the ACCORD therapeutic strategies to improve glycemic control could mitigate the adverse effects of type 2 diabetes on the brain.Subjects10,251 patients with type 2 diabetes and HbA1c concentrations of 7.5% or more participated in the trial. Of these patients, 5518 were assigned to the lipid therapy arm and 4733 to the blood pressure arm. EYE Substudy:A subgroup of 2856 patients was evaluated for the effects of the ACCORD interventions at 4 years on the progression of diabetic retinopathy. Patients who, at baseline, had a history of proliferative diabetic retinopathy that had been treated with laser photocoagulation or vitrectomy were excluded.MIND Substudy:A subgroup of 2977 patients was evaluated for cognitive function and brain volume. The ACCORD MIND substudy excluded patients aged DesignPatients were randomly assigned to undergo either intensive glycemic control (targeting a glycated hemoglobin level EYE Substudy:EYE Substudy patients were evaluated at two standardized and comprehensive eye examinations for the effects of the ACCORD interventions at 4 years on the progression of diabetic retinopathy by 3 or more steps on the Early Treatment Diabetic Retinopathy Study Severity Scale (as assessed from seven-field stereoscopic fundus photographs, with 17 possible steps and a higher number of steps indicating greater severity) or the development of diabetic retinopathy necessitating laser photocoagulation or vitrectomy.MIND Substudy:The cognitive primary outcome, the Digit Symbol Substitution Test (DSST) score, was assessed at baseline, 20 and 40 months. Total brain volume (TBV), the primary brain structure outcome, was assessed with MRI at baseline and 40 months in a sub-set of 632 patients. All patients with follow-up data were included in the primary analyses.ConclusionsGlycemia Trial:As compared with standard therapy, the use of intensive therapy to target normal glycated hemoglobin levels for 3.5 years increased mortality and did not significantly reduce major cardiovascular events. (NEJM. 2008; 358(24): 2545-59).Microvascular Outcomes of the Glycemia Trial:Intensive therapy did not reduce the risk of advanced measures of microvascular outcomes, but delayed the onset of albuminuria and some measures of eye complications and neuropathy. Microvascular benefits of intensive therapy should be weighed against the risk of increased total and cardiovascular disease-related mortality, increased weight gain, and higher risk for severe hypoglycemia. (Lancet. 2010; 376(9739): 419-30)Lipid Therapy Trial:The combination of fenofibrate and simvastatin did not reduce the rate of fatal cardiovascular events, nonfatal myocardial infarction or nonfatal stroke, as compared with simvastatin alone. These results do not support the routine use of combination therapy with fenofibrate and simvastatin to reduce cardiovascular risk in the majority of high-risk patients with type 2 diabetes (NEJM. 2010; 362(17): 1563–1574).Blood Pressure Trial:In patients with type 2 diabetes at high risk for cardiovascular events, targeting a systolic blood pressure of less than 120 mm Hg, as compared with less than 140 mm Hg, did not reduce the rate of a composite outcome of fatal and nonfatal major cardiovascular events (NEJM. 2010; 362: 1575-1585).EYE Substudy:Intensive glycemic control and intensive combination treatment of dyslipidemia, but not intensive blood-pressure control, reduced the rate of progression of diabetic retinopathy (NEJM. 2010; 363: 233-244).MIND Substudy:Although significant differences in TBV favored the intensive therapy, cognitive outcomes were not different. Combined with the unfavorable effects on other ACCORD outcomes, MIND findings do not support using intensive therapy to reduce the adverse effects of diabetes on the brain in patients similar to MIND patients (Lancet Neurol. 2011; 10(11): 969–977).

Study phs003562

Childhood Cancer Survivor Study (CCSS)

Background and Rationale for the Childhood Cancer Survivor Study (CCSS) Over the last several decades, advances in treatments for childhood and adolescent cancer have substantially improved survival following diagnosis. These improvements gave rise to the responsibility for investigating long-term treatment-associated morbidity and mortality. Early efforts to describe late effects were largely conducted through single-institution and limited consortia studies. However, by the mid-1980s, it became increasingly clear that these approaches had inherent limitations, including small sample size, convenience sampling, incompletely characterized populations, and limited length of follow-up. To overcome these limitations, the CCSS was proposed and funded by the National Cancer Institute (NCI) as a U01 grant in 1994. Subsequently, the strengths of the CCSS, including an efficient and extensive infrastructure, plus expanding database and biorepository, were recognized and appreciated. Thus, in consultation with the NCI, the CCSS was converted to a U24 (resource grant) funding mechanism to serve the scientific community in 2000. The overarching goal of the CCSS resource is to increase the conduct of innovative and high impact research related to pediatric cancer survivorship. CCSS has been used extensively by researchers from a wide range of disciplines to address a broad spectrum of topics. Strengths of the resource include its large size, comprehensive annotation of treatment exposures, ongoing longitudinal follow-up with characterization of a wide array of participant characteristics and outcomes, and an established biorepository. Design of the Childhood Cancer Survivor Study The Childhood Cancer Survivor Study (CCSS) is a multi-institutional, multi-disciplinary collaborative research resource comprised of a retrospective hospital-based cohort of survivors of childhood cancer and a comparison sibling cohort. Eligible survivors from 31 participating institutions were diagnosed between 1970 and 1999, prior to age 21 years, with selected common pediatric cancers (leukemia, central nervous system tumors, Hodgkin lymphoma, non-Hodgkin lymphoma, kidney tumors, neuroblastoma, soft tissue sarcoma, or bone tumors). All patients who survived five years from the date of diagnosis were eligible, regardless of disease or treatment status. The baseline questionnaire was completed by 24,368 survivors and 5,039 siblings recruited to serve as a comparison group. To date, participants have completed three general follow-up surveys, as well as a number of specialized surveys on specific topics (e.g. health care, insurance, screening practices, men's and women's health issues, adolescent health, sleep and fatigue). In addition, biological samples (buccal cells, saliva and/or blood) have been collected for over 11,000 participants. Full descriptions of the design and characteristics of the CCSS have been previously published (Robison et al; Leisenring et al.), and available data and samples are described at https://ccss.stjude.org/develop-a-study/gwas-data-resource.html. Treatment Data in the Childhood Cancer Survivor Study A key feature of CCSS is the availability of detailed treatment data, which were collected by abstraction of medical records for each individual member of the cohort. Detailed abstraction included dates of therapy, protocol information, and specific details regarding surgery, chemotherapy and radiation. Quantitative dose details were collected for 22 specific chemotherapeutic agents, including alkylating agents, anthracyclines, platinum compounds and epipodophyllotoxins. In addition to individual agent doses, algorithms have been created to calculate cumulative doses of all drugs in a specific class, such as anthracyclines (doxorubicin, daunomycin and idarubicin) or platinum agents (cisplatinum and carboplatinum). Data abstracted for surgeries included dates and both the names and corresponding International Classification of Diseases (9th revision) code. For radiation treatment data, all relevant records were sent to the Radiation Physics Center at M.D. Anderson Cancer Center for detailed abstraction and dosimetry. Initial body region dosimetry was performed for all participants, followed by more detailed dosimetry as needed for specific studies. Genomics Data in the Childhood Cancer Survivor StudyThe NCI's Division of Cancer Epidemiology and Genetics and CCSS investigators collaborated to conduct genomics studies (SNP array genotyping and whole exome sequencing) using samples from the CCSS Biorepository. Studies included all cohort participants with available DNA regardless of sex or ancestry when the genomics studies were initiated. Phenotype Data in the Childhood Cancer Survivor Study Vital status and cause of death for both participants and non-participants is determined via linkage with the National Death Index (NDI). Identification of subsequent neoplasms is based on self-report, followed by validation using medical records, or via NDI. A wide array of additional health outcomes have been ascertained via a comprehensive set of questions on the CCSS questionnaires, covering potential adverse events across a range of organ systems (hearing/vision/speech, urinary, hormonal, heart and circulatory, respiratory, digestive, brain and nervous systems). In addition to health outcomes, longitudinal data have been collected on demographics, health behaviors, family history, screening practices, insurance status, and a range of psychosocial and neurocognitive factors. A full listing of available variables and copies of the CCSS questionnaires are available at http://ccss.stjude.org. Research Areas in the Childhood Cancer Survivor Study Extensive use by the research community has resulted in over 265 published manuscripts on a wide range of topics, including associations between treatment factors and mortality, subsequent neoplasms, chronic health conditions, cardiac events, neurocognitive sequelae, psychosocial factors, fertility, and health status. Additional topics have included health behaviors, screening practices, health care access and utilization, statistical and exposure assessment methodology, and development of risk prediction models. A full listing of published manuscripts using CCSS data is available on the CCSS website at https://ccss.stjude.org/published-research/publications.html. The Childhood Cancer Survivor Study as a Resource for Investigators The CCSS is an NCI-funded resource (U24 CA55727) to promote and facilitate research among long-term survivors of cancer diagnosed during childhood and adolescence. Interested investigators are encouraged to develop research ideas and propose projects within CCSS, whether or not they are from a participating CCSS institution. The CCSS is now accepting proposals to collaborate with CCSS and NCI investigators in the use of genomics data and corresponding outcomes-related data to address innovative research questions relating to potential genetic contributions to risk for treatment-related outcomes. Any researcher, or group of researchers, qualified to conduct genetic research can submit a proposal. There are no restrictions relative to country, institution, or prior involvement in CCSS. A full description of the process for developing a proposal for genetic research in CCSS can be found at https://ccss.stjude.org/develop-a-study/gwas-data-resource.html, along with listings of approved proposals.

Study phs001327

Action to Control Cardiovascular Risk in Diabetes (ACCORD-BioLINCC)

Related StudiesWhole genome and whole exome data is available on a subset of participants with phs001411. ECG signal data is available with phs003562.ObjectivesThe purpose of this study was to determine if intensive glycemic control, multiple lipid management and intensive blood pressure control could prevent major cardiovascular events (myocardial infarction, stroke or cardiovascular death) in adults with type 2 diabetes mellitus. Secondary hypotheses included treatment differences in other cardiovascular outcomes, total mortality, microvascular outcomes, health-related quality of life and cost-effectiveness. BackgroundGlycemia Trial:Patients with type 2 diabetes mellitus die of cardiovascular disease (CVD) at rates two to four times higher than non-diabetic populations of similar demographic characteristics. They also experience increased rates of nonfatal myocardial infarction and stroke. With the growing prevalence of obesity in the United States, CVD associated with type 2 diabetes is expected to become an even greater public health challenge in the coming decades than it is now. Expected increases in event rates will be associated with a concomitant rise in suffering and resource utilization.The ACCORD study investigated whether intensive therapy to target normal glycated hemoglobin (HbA1c) levels would reduce cardiovascular events in patients with type 2 diabetes who had either established cardiovascular disease or additional cardiovascular risk factors when compared to standard therapy (HbA1c between 7.0% and 7.9%). A separate analysis investigated whether reduction of blood glucose concentration decreases the rate of microvascular complications in these patients. Lipid Therapy Trial: Patients with type 2 diabetes mellitus have an increased incidence of atherosclerotic cardiovascular disease attributable, in part, to associated risk factors such as dyslipidemia. This is characterized by elevated plasma triglyceride levels, low levels of high-density lipoprotein (HDL) cholesterol and small, dense low-density lipoprotein (LDL) particles. The ACCORD Lipid Therapy trial was designed to test the effect of a therapeutic strategy that uses a fibrate to raise HDL-C and lower triglyceride levels and uses a statin for treatment of LDL-C reduce the rate of CVD events compared to a strategy that only uses a statin for treatment of LDL-C on cardiovascular outcomes in patients with type 2 diabetes that were at high risk for cardiovascular disease. Blood Pressure Trial: Diabetes mellitus increases the risk of cardiovascular disease at every level of systolic blood pressure. Because cardiovascular risk in patients with diabetes is graded and continuous across the entire range of levels of systolic blood pressure, even at prehypertensive levels, the Seventh Report of the Joint National Committee on Prevention, Detection, Evaluation, and Treatment of High Blood Pressure (JNC 7) recommended beginning drug treatment in patients with diabetes who have systolic blood pressures of 130 mm Hg or higher, with a treatment goal of reducing systolic blood pressure to below 130 mm Hg. There is, however, a paucity of evidence from randomized clinical trials to support these recommendations. The ACCORD Blood Pressure trial tested the effect of a target systolic blood pressure below 120 mm Hg on major cardiovascular events among high-risk persons with type 2 diabetes compared to a strategy that targeted a SBP of EYE Substudy: Diabetic retinopathy, an important microvascular complication of diabetes, is a leading cause of blindness in the United States. Randomized, controlled clinical trials in cohorts of patients with type 1 diabetes and those with type 2 diabetes have shown the beneficial effects of intensive glycemic control and intensive treatment of elevated blood pressure on the progression of diabetic retinopathy. Elevated serum cholesterol and triglyceride levels have been implicated, in observational studies and small trials, as additional risk factors for the development of diabetic retinopathy and visual loss. The ACCORD EYE Substudy evaluated the effects of the ACCORD medical strategies on the progression of diabetic retinopathy in a subgroup of trial patients. MIND Substudy: Studies suggest that older persons with type 2 diabetes have at least twice the likelihood of developing late-life cognitive impairment or dementia compared to those without. The mechanisms underlying these cognitive disorders are increasingly thought to reflect a mixed pathology pattern with contributions from vascular, neurodegenerative and neurovascular processes. Pathophysiological mechanisms that have been described include inflammation, oxidative stress, energy imbalance, protein misfolding, glucocorticoid-mediated effects and differences in genetic susceptibilities. The ACCORD MIND substudy took as a premise that early intervention with the ACCORD therapeutic strategies to improve glycemic control could mitigate the adverse effects of type 2 diabetes on the brain. Participants10,251 participants with type 2 diabetes and HbA1c concentrations of 7.5% or more participated in the trial. Of these patients, 5518 were assigned to the lipid therapy arm and 4733 to the blood pressure arm. EYE Substudy: A subgroup of 2856 participants was evaluated for the effects of the ACCORD interventions at 4 years on the progression of diabetic retinopathy. Participants who, at baseline, had a history of proliferative diabetic retinopathy that had been treated with laser photocoagulation or vitrectomy were excluded. MIND Substudy: A subgroup of 2977 participants was evaluated for cognitive function and brain volume. The ACCORD MIND substudy excluded participants aged Design Participants were randomly assigned to undergo either intensive glycemic control (targeting a glycated hemoglobin level EYE Substudy: EYE Substudy participants were evaluated at two standardized and comprehensive eye examinations for the effects of the ACCORD interventions at 4 years on the progression of diabetic retinopathy by 3 or more steps on the Early Treatment Diabetic Retinopathy Study Severity Scale (as assessed from seven-field stereoscopic fundus photographs, with 17 possible steps and a higher number of steps indicating greater severity) or the development of diabetic retinopathy necessitating laser photocoagulation or vitrectomy. MIND Substudy: The cognitive primary outcome, the Digit Symbol Substitution Test (DSST) score, was assessed at baseline, 20 and 40 months. Total brain volume (TBV), the primary brain structure outcome, was assessed with MRI at baseline and 40 months in a sub-set of 632 patients. All patients with follow-up data were included in the primary analyses. Conclusions Glycemia Trial: As compared with standard therapy, the use of intensive therapy to target normal glycated hemoglobin levels for 3.5 years increased mortality and did not significantly reduce major cardiovascular events. (Action to Control Cardiovascular Risk in Diabetes Study Group, et al.,2008, PMID:18539917). Microvascular Outcomes of the Glycemia Trial: Intensive therapy did not reduce the risk of advanced measures of microvascular outcomes, but delayed the onset of albuminuria and some measures of eye complications and neuropathy. Microvascular benefits of intensive therapy should be weighed against the risk of increased total and cardiovascular disease-related mortality, increased weight gain, and higher risk for severe hypoglycemia. (Ismail-Beigi et al., 2010, PMID: 20594588) Lipid Therapy Trial: The combination of fenofibrate and simvastatin did not reduce the rate of fatal cardiovascular events, nonfatal myocardial infarction or nonfatal stroke, as compared with simvastatin alone. These results do not support the routine use of combination therapy with fenofibrate and simvastatin to reduce cardiovascular risk in the majority of high-risk patients with type 2 diabetes (ACCORD Study Group, et al., 2010, PMID: 20228404). Blood Pressure Trial: In patients with type 2 diabetes at high risk for cardiovascular events, targeting a systolic blood pressure of less than 120 mm Hg, as compared with less than 140 mm Hg, did not reduce the rate of a composite outcome of fatal and nonfatal major cardiovascular events (ACCORD Study Group, et al., 2010, PMID: 20228401). EYE Substudy: Intensive glycemic control and intensive combination treatment of dyslipidemia, but not intensive blood-pressure control, reduced the rate of progression of diabetic retinopathy (ACCORD Study Group, et al., 2010, PMID: 20587587). MIND Substudy: Although significant differences in TBV favored the intensive therapy, cognitive outcomes were not different. Combined with the unfavorable effects on other ACCORD outcomes, MIND findings do not support using intensive therapy to reduce the adverse effects of diabetes on the brain in patients similar to MIND patients (Launer et al., 2011, PMID: 21958949).

Study phs003551

How to encrypt files with EGACryptor

File preparation Due to the processes used at the EGA for file archival the use of non-alphanumeric characters in a filename will cause issues in archival. By convention whitespaces in filenames are to be avoided and should be replaced with the underscore character (_). Before encrypting your files please make sure that any files that will be uploaded to EGA do not use special characters such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | & Crypt4gh EGACryptor Files encrypted with EGACryptor must be uploaded via FTP EGACryptor The EGACryptor v.2.0.0 is a JAVA-based application which enables submitters to produce EGA compliant encrypted files along with files for the encrypted and unencrypted md5sum for each file to be submitted. The application will generate an output folder that will by default mirror the directory structure containing the original files. This output folder can subsequently be uploaded to the EGA FTP staging area via an FTP or Aspera client. Download EgaCryptor Download EgaCryptor Using the EgaCryptor Using the EgaCryptor Encrypting single file Encrypting multiple files Encrypting all files in folder Points to note Troubleshooting Troubleshooting Download EGACryptor The required jar files can be obtained by downloading EgaCrytptor jar file After the file has been downloaded, extraction of the zipped archive is required. The EGACryptor has been built to work with Java Runtime Environments from version 6 and above and with the OpenJDK Environment. Please refer to the relevant resources for installation guidance. Installing the latest version of the OpenJDK will include the JCE files. If your installation of Java JRE is less than 1.8.0_151 will require the manual installation of the JCE Policy Files. You can verify the version of the Java SE Runtime Environment (JRE) installed by using the command: $ java -version If you need to install the JCE please follow the instructions below: Installing the JCE policy files (due to licensing terms and conditions the required policy files must be downloaded direct from the ORACLE website) : Download the unlimited strength JCE policy files (JRE 6 / JRE 7/ JRE 8) Uncompress and extract the downloaded file. This will create a subdirectory called JCE. This directory contains the following files: README.txt, COPYRIGHT.html, local_policy.jar and US_export_policy.jar Install the two policy JAR files by replacing the existing ones in your java home directory. Install the two policy JAR files by replacing the existing ones in your directory. The standard place for JCE jurisdiction policy JAR files is: /lib/security [Unix] or \lib\security [Win32] Notes: refers to the directory where the Java SE Runtime Environment (JRE) was installed. Additional performance enhancements that have been included in the EGACryptor V2.0.0: The ability to parallelise the processing of datasets through the use of the resources on a system. Multicore systems will allow the user to specify n-1 cores for an n-core system. The use of this feature on clusters may speed up the processing of datasets that have large file numbers but consult your local cluster guide to ensure that there are not monopolising resources that are needed by other system users. The default for this process remains single threaded. 3 levels of system usage can be specified. Full usage within the limits detailed above. A limited mode that will ensure that 50% of the system resources are available for other tasks. Maximum mode is limited to 75% of system resources, this allows encryption to be prioritised but allows for the system to be usable for light alternate tasks. Finally there is a throttling mode that allows you to specify the exact number of computational threads to be used. the EGACryptor is able to ingest a structured directory and will output a directory with the same structure containing the encrypted files along with the md5checksums for the plain and encrypted files. The entire output directory can then be uploaded to the EGA for archival. as with the input path, it is now possible to specify the output path. the options have been updated inline with the upgraded functionality. The tool can only be used via the command line. The EGACryptor is designed to perform a single task, encrypting your data, for upload of these files please refer to our uploading guide Using the EgaCryptor Below are the three ways on how the EGACryptor tool can be used: Encrypting a single file : java -jar ../EGA-Cryptor_2_0_0.jar -i example1.bam Encrypting multiple files : java -jar ../EGA-Cryptor_2_0_0.jar -i "example1.bam,example2.bam" Encrypting all the files within a folder java -jar ../EGA-Cryptor_2_0_0.jar -i path/to/target/directory By default the EGACryptor v2 will create a new output directory containing all encrypted files and the relevant checksums within the target directory. If a specific directory is desired this can be specified by using the -o flag. This can be achieved in a similar manner to the following example: java -jar ../EGA-Cryptor_2_0_0.jar -i /path/to/target/directory -o /path/to/output/directory The tool will output three files per input file: file.gpg ( encrypted file ) file.md5( file md5 sum value file ) file.gpg.md5 ( encrypted file md5 sum value file ) All output files must then be uploaded to your submission account using Aspera or FTP. Further documentation on how to upload files: FTP and Aspera. Points to note Remember to provide the path to EgaCryptor.jar and run the command from within the directory the file/s are located. ECryptor writes files to the source directory of your local file system, as a result you must have write-access permissions for the source directory. Troubleshooting If in doubt about the function of the EGACryptor it is recommended to first consult the built-in documentation. This can be accessessed by using the -h flag as stated in the following table. Built-in Commands Table: list of the command line options built into EGA-Cryptor v2.0.0. Command line Option Action --------------------- ----------- -f Set this option to allow application to create maximum threads to utilise full capacity of cores/processors available on machine -h Use this option to view the bult-in help menu * -i File(s) to encrypt. Provide file/folder path or comma separated file path if multiple files in double quotes -l Set this option to allow application to create maximum threads equals to 50% capacity of cores/processors available on machine -m Set this option to allow application to create maximum threads equals to 75% capacity of cores/processors available on machine -o Path of the output file. This is optional. If not provided then output files will be generated in the same path as that of source file (default: output- files) -t Set this option if user wants to control application to create maximum threads as specified. Application will calculate no. of cores/processors available on machine & will create threads accordingly Encryption Errors UnixFileSystem.createFileExclusively (Native Method) The error is thrown by UNIX ("UnixFileSystem.createFileExclusively(Native Method)"). It appears that the user does not have write-access to the file system where the file to be uploaded is located. EGACryptor always writes MD5 checksums into files before uploading them to the server, and these files are created in the same location where the uploaded file itself resides.Solution: address your directory permission issue and re-run the command. Install JCE Unlimited Strength Jurisdiction Policy files The JCE policy unlimited strength jurisdiction files should be installed according to your current java version If you are still facing difficulty with the EGACryptor v.2 after having consulted the documentation please contact the EGA Helpdesk.

Documentation submission/data/file-preparation/egacryptor

All you need to know about our new DAC Portal

With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

Blog new-dac-portal

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

Distribution of data using Live Distribution

Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

Documentation access/download/files/live-outbox

How to upload Crypt4GH files

Uploading files Users who hold an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files, please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention, such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs) for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username. If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days. Specific to using keys to authenticate Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

Documentation submission/data/uploading-files/inbox

What is a DAC?

What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant. For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source. Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions. You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks. Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, the EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

Documentation access/data-access-committee/what-is-dac

Identification of Genes Involved in Familial Coronary Artery Disease

Studying families with multiple cases of coronary artery disease (CAD) or with early onset CAD in order to identify new genes involved in CAD in an autosomal dominant manner. After identifying these genes in families that pass on CAD in Mendelian inheritance, we want to pursue their role in the pathogenesis of CAD and their contribution in the general population.

Study phs000514

Exome Sequencing Reveals Frequent Inactivating Mutations in BAP1, ARID1A, and PBRM1 in Intrahepatic Cholangiocarcinomas

Through exomic sequencing of 32 intrahepatic cholangiocarcinomas, we discovered frequent inactivating mutations in multiple chromatin remodeling genes (including BAP1, ARID1A, and PBRM1) – mutation in one of these genes occurred in almost half of the carcinomas sequenced. We also identified frequent mutations at previously reported hotspots in genes encoding the metabolic enzymes IDH1 and IDH2 in intrahepatic cholangiocarcinomas. In contrast, TP53 was the most frequently altered gene in a series of nine gallbladder carcinomas. These studies highlight the importance of dysregulation of chromatin remodeling in intrahepatic cholangiocarcinomas.

Study EGAS00001001108

Characterization of Sex Differences in Human Placentas

Whole exome and whole transcriptome sequencing data from human (Homo sapiens) placenta and maternal decidua tissues. This study characterizes sex differences in gene expression in the placenta. Differences in gene expression in maternal decidua from pregnancy with a male or female placenta. Patterns of X chromosome inactivation in the placenta. Genome-wide allele-specific expression in human placentas. 

Study phs002240

Establishment of xenogfafts and cultured cell lines from clinical samples

The purpose of the present study was to clarify the presence or absence of alterations in the molecular properties of patient-derived xenografts (PDXs) with up to eight passages in endometrial carcinomas. Alterations in the proportion of immunohistochemically positive/negative cells for PAX8, estrogen receptor, PAX2, and PTEN were observed in established PDXs of endometrioid carcinomas and carcinosarcomas, whereas proportions of cells with AE1/AE3, TP53, ARID1A PMS2, and MSH6 were maintained. Variants of cancer-associated genes in PDX compared to those in the parental tumors were examined in two cases, a frameshift deletion in BRCA1 was observed in the parental tumor tissue, and additional genomic alterations were found in the PDXs of this case. Genomic and phenotypic alterations in endometrial carcinoma PDXs relative to the parental tumors were observed and were partly associated with endometrial cancer-specific characteristics in cellular differentiation and gene mutations.

Study JGAS000585

Screening Cases of Isolated Dystonia for Variants in CIZ1

Recently, we have identified that variants in CIZ1 gene is associated with dystonia. To identify the prevalence of CIZ1 mutations in dystonia population, we use High resolution melting (HRM) to examine all the coding sequence in 3976 subjects with primary dystonia as well as 1819 subjects of normal controls. Indels in Q rich region of exon 2 in CIZ1 were identified in 21 subjects with dystonia but only 3 controls (P<0.05). Other single nucleotide change variants were also found in some of the patients which include a novel missense mutation (c.787A>G, p.R263G) found in a female patient with apparently familial dystonia. We confirmed that mutations in CIZ1 could be associated with dystonia but in rare cases.

Study phs001455

RNA-Seq studies of Gene Expression in Cells and Networks in FI and ACC in Autism

RNA-Seq studies of Gene Expression in Cells and Networks in FI (fronto-insular) and AC (anterior cingulate) cortex in Autism. We seek to understand the cellular bases of autism by using a new technology, RNA-Seq, to determine differences in gene expression in autopsy brains of subjects with well described autism versus age and sex matched neurotypical individuals. We have investigated two specific cortical areas involved in self-awareness and social reciprocity which are abnormal in autism and have found increased expression in a network of genes related to inflammation in autism group A, whereas the remaining cases, autism group B, have increased expression in a network of genes related to synapses. The current dbGaP study release includes RNA sequencing and phenotype data of n=27 subjects of African - American, Caucasian, or Hispanic origin.

Study phs000609

Nuclease deficiencies alter plasma cell-free DNA methylationprofiles (mouse)

The effects of DNASE1L3 or DNASE1 deficiency on cfDNA methylation was explored in plasma of mice deficient in these nucleases and in DNASE1L3-deficient humans. Compared to wildtype cfDNA, cfDNA in Dnase1l3-deficient mice was significantly hypomethylated, while cfDNA in Dnase1-deficient mice was hypermethylated. The cfDNA hypomethylation in Dnase1l3-deficient mice was due to increased fragmentation and representation from open chromatin regions (OCRs) and CpG islands (CGIs). These findings were absent in Dnase1-deficient mice.

Study EGAS00001004696

12254 results for "fc coins kopen ps4 Besuche die Website Buyfc26coins.com. Coins in Minuten da..Gidj"

in 39.41 milliseconds.