465 results for "ultimate team coins fc 26 Besök Buyfc26coins.com Inga klagomål överhuvudtaget. Rekommenderar till alla..kIhF"

in 28.65 milliseconds.

• FIGHT-207: Anonymized Genomic Alterations and Clinical Responses

  Background: FIGHT-207 was a phase 2 study of the FGFR1-FGFR3 inhibitor pemigatinib in patients with previously treated, locally advanced/metastatic or unresectable solid tumor malignancies harboring activating fibroblast growth factor receptor (FGFR) gene alterations. Population information: 107 patients were divided into 3 cohorts: FGFR1–FGFR3 fusions/rearrangements; n=49 Activating FGFR1–FGFR3 non-kinase domain single nucleotide variants (SNVs); n=32 FGFR1–FGFR3 kinase domain mutations or variants of unknown significance (VUS) with potential pathogenicity; n=26 Participants on study had tumors that were grouped into the following histologies based on ≥ 5 patients: Cholangiocarcinoma, gynecologic cancers (cervical, endometrial, uterine), central nervous system (glioblastoma, low-grade pediatric glioma, astrocytoma), pancreatic cancer, breast cancer, urothelial tract/bladder cancer, non-small cell lung cancer, and other (adrenal cancer, anal cancer, cancer of unknown primary origin, colorectal cancer, gastric/gastroesophageal cancer, gallbladder cancer, giant cell bone tumor, head and neck cancer, lung neuroendocrine cancer, nasopharyngeal cancer, ovarian cancer, prostate cancer, renal cell cancer, sarcoma, solitary fibrous tumor). Among the efficacy-evaluable participants, 99 had both independent review committee (IRC) central best overall response (BOR) and tissue NGS- data; 2 additional patients had Not Evaluable (NE) as central BOR Baseline tissue targeted NGS data (F1CDx, Foundation Medicine Inc.) of genomic alterations are reported for N=101 participants Baseline plasma targeted NGS analysis (PredicineCare, Predicine Inc.) of genomic data are reported for N=83 participants; data at disease-progression are reported for N=78 participants. Principal Findings: The FIGHT-207 study provided evidence of clinical benefit of pemigatinib in multiple histologies, explored the clinical actionability of various FGFR1-FGFR3 gene alterations, and leveraged the depth of translational data from targeted NGS analysis of baseline samples and plasma samples obtained at baseline and end of treatment to provide key insights into the biology of FGFR inhibition and the clinical utility of FGFR inhibitors. The FIGHT-207 article (pending in Nat.Med. NMED-A128973B) reports evidence suggesting clinical acquired resistance to FGFR inhibition via secondary FGFR mutations as well as emerging co-mutations in other oncogenic and tumor suppressor pathways. This study also provides evidence of acquired resistance to FGFR inhibition in multiple histologies beyond cholangiocarcinoma and urothelial cancers in a systemic correlative analysis of post-progression ctDNA in a trial. Data available through dbGaP: Anonymized information for 101 participants with both IRC central BOR evaluation (including 2 patients with NE as BOR) and tissue NGS data, including tumor histology, enrollable FGFR alteration, and outcome. Genomic alterations determined by baseline tissue NGS (F1CDx, Foundation Medicine Inc.) Genomic alterations determined by plasma NGS analysis (PredicineCare, Predicine Inc.) of ctDNA analysis at baseline (n=83) and at end of treatment/ disease progression (n=78) including genomic alterations that were not assessed to be Germline SNPs.

  Study phs003590

• The NCAA-DoD Concussion Assessment, Research, and Education (CARE) Consortium

  Study Description: Established in 2014, the U.S. Department of Defense (DoD) and the National Collegiate Athletic Association (NCAA) funded the Concussion Assessment, Research and Education (CARE) Consortium to inform science, clinical care and public policy related to concussion and repetitive head impact exposure (HIE) in U.S. Military Service Academy (MSA) cadets and collegiate student-athletes. The primary aims of the initial study were to: (1) establish a multisite research consortium to characterize the effects of concussion and repetitive head impact exposure on brain health, (2) characterize the clinical sequelae and natural history of concussion, (3) characterize the effect of concussion and repetitive head impacts on brain structure and brain function. The 30 member institutions of the CARE Consortium (26 civilian universities/colleges and 4 military service academies) agreed to invite all varsity athletes to undergo multimodal clinical assessments at preseason baseline, and at 5 additional timepoints after concussion diagnosis. At the service academies, non-varsity athlete cadets/midshipmen were also studied. Assessment Categories At Each Time Point Baseline: • Demographics • Personal and Family History • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms ACUTE POST-INJURY FOLLOW-UP (CARE 1.0) (24 hrs; 48hrs; Asymptomatic; Unrestricted Return to Play (RTP); 6 mos) • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms CUMULATIVE & PERSISTENT EFFECTS. (CARE 2.0) In-Person Exit Visit; Post-grad Online • Demographics • Personal and Family History • Neurocognitive Assessment • Neurological Status • Postural Stability • Symptoms • PROs • MROs (at academies only) LONG-TERM EFFECTS (CARE/SALTOS Integrated (CSI))Annual Online Assessment (at MSAs only); In-Person Research Visits • Demographics • Symptoms • Psychological health • PROs • MROs (at academies only)A subset of athletes at 6 of the CARE institutions underwent additional assessments including multimodal MRI, proteomic and genomic biomarker characterization, and head impact quantification (helmet-based sensors). Assessment time points for the ARC/pARC Neurocognitive and Behavioral Testing was done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), Unrestricted Return to Play, 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career.Blood biomarker collection was done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career. Multi-modal MRI studies were done at Baseline, <48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at >60 days after final game of junior year until end of collegiate career. However, please note that only athletes from one study performance site completed a multi-modal MRI study at baseline.

  Study phs002175

• Heart Failure Network: Entresto(TM) in Advanced Heart Failure (HFN-LIFE-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To compare treatment with sacubitril/valsartan versus valsartan alone in patients with advanced heart failure with a reduced ejection fraction and recent New York Heart Association class IV symptoms.Background: Treatment with evidence-based medical therapies improves survival, reduces heart failure hospitalizations, and improves quality of life in patients with chronic heart failure with a reduced ejection fraction. However, evidence supporting the use of medical therapies among patients with advanced heart failure is limited. Patients with New York Heart Association (NYHA) class IV heart failure are not often enrolled in clinical trials.A previous trial reported that, compared with the angiotensin-converting enzyme inhibitor enalapril, sacubitril/valsartan, an angiotensin receptor-neprilysin inhibitor, reduced the relative risk of cardiovascular mortality and heart failure hospitalizations by 20% in ambulatory patients with heart failure with a reduced ejection fraction. Although patients with NYHA class IV heart failure were eligible to enroll, this population was underrepresented. The HFN-LIFE trial was initiated to provide additional information about the tolerability, safety, and potential efficacy of sacubitril/valsartan in patients with advanced heart failure.Participants: Of the eligible patients that enrolled, a total of 335 patients tolerated the run-in phase and were randomized to a treatment group. 167 patients were randomly assigned to receive sacubitril/valsartan and 168 patients were randomly assigned to receive valsartan alone.Design: The HFN-LIFE trial was a prospective, multicenter, randomized, double-blind phase 4 clinical trial. Trial enrollment was suspended early, due to the high risk for adverse outcomes associated with COVID-19 infection.Eligible patients were enrolled and began an unblinded run-in period of 3 to 7 days with sacubitril/valsartan, 24/26 mg (50-mg fixed dose), administered orally twice daily. Participants tolerating the run-in phase were randomized in a 1:1 fashion to receive sacubitril/valsartan (target dose, 200 mg twice daily) or valsartan (target dose, 160 mg twice daily). The initial doses were selected based on guidelines with dose adjustments being made every 2 weeks.The primary efficacy outcome was the area under the curve of NT-proBNP levels at 2, 4, 8, 12, and 24 weeks compared with the level of NT-proBNP at randomization. The secondary efficacy end point was the number of days the patient was alive, out of the hospital, and free from any of the following outcomes: listing for cardiac transplant, cardiac transplant, implantation of a left ventricular assist device, receipt of continuous inotropic therapy for 7 or more days, or hospitalization for heart failure on 2 or more occasions other than the index admission.Conclusions: In patients with chronic advanced heart failure with a reduced ejection fraction, there was no statistically significant difference between sacubitril/valsartan and valsartan alone with respect to reducing NT-proBNP levels.

  Study phs004171

• Cincinnati Children's Hospital Medical Center (CCHMC) - eMERGE Phase IIIA Data

  This submission includes genotyping or sequencing data from separate cohorts, each is described in separate paragraphs below. Extreme early onset obesity Obesity is a serious epidemic condition and on the rise in the United States. Today, nearly one out of three children is overweight or obese in this country. According to the Center for Disease Control, 35.7% of American adults and 17% of American children are obese. The medical costs associated with obesity are estimated to be in the billions. Without a doubt, interplay of additive genetic effects and common environmental effects influence this complex disease. However, despite being exposed to so-called "obesogenic environment", a large proportion of the population remains of normal weight. These observations suggest that innate, non-environmental, factors make some individuals more susceptible to obesity providing support for biological mechanisms, and thus genetic factors, to underlie the individual's response to the obesogenic environment. In young children with severe obesity the relative role of genetics and in utero programming are likely to outweigh the short duration of environmental and lifestyle exposures. This group is therefore an ideal one to study as they are likely enriched for variants that influence the risk of developing obesity. The purpose of this project is to further study and understand obesity in childhood and to develop a repository of samples for future studies into obesity. Eosinophilic Esophagitis (EoE) Eosinophilic Esophagitis (EoE) 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 EoE 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 EoE. Diagnosis of EoE 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. The de-identified genotyping and genome wide association data generated as part of this research will be used for further genome research. Familial Sample Repository (FSR) and Directed Sample Repository (DSR) De novo mutations could cause many diseases, which has been demonstrated in mental retardation, autism and many rare genetic disorders. Family-based studies have a variety of advantages over case/control studies, including the elimination of analysis artifacts related to population stratification, the detection of genes that act through a recessive mechanism of inheritance and validation that the trait is not transmitted from a parent, something not possible using a case/control design. Additionally, DNA from families can be used to identify de novo mutations suggesting strong candidate causal polymorphisms. For this project, samples will be collected from families on an on-going basis. Families may be recruited because the patient either has a disease which is thought to be of genetic origin or from the general patient population to serve as controls or future identified diseases. Some phenotypes under study include fibroblastic rheumatism, diaphragmatic hernia, polymicrogyria, severe congenital neutropenia, primary sclerosing cholangitis and staph infection. CLRR-Cincinnati Lupus Registry and Repository Systemic lupus erythematosus (SLE) is a complex, partially understood autoimmune disorder. Genetic origins for SLE are supported by high heritability (> 66%), familial aggregation, increased monozygotic twin concordance, genetic linkages, and candidate gene genetic association, including HLA genes, Fc receptors, and complement components. Relevant environmental factors likely include infections (Epstein-Barr virus), therapeutics, personal habits (smoking), and diet. To continue a research resource facility for collection of well-characterized pedigrees containing a proband with systemic lupus erythematosus we develop this repository. Juvenile Idiopathic Arthritis (JIA) 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 complex genetic traits. 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. These data will contribute to a national resource for the study of autoimmunity in children. Better Outcomes for Children-Cytogenetics Since 2007, more than 4000 samples, enriched with various rare or common genetic diseases as well as specific chromosomal abnormalities such as deletions and duplications have been genotyped for the purpose of subsequent GWAS and Phewas analyses and uncovering main genetic effects.

  Study phs001011

• The EGA at the International Congress of Human Genetics

  Today is the start of the International Congress of Human Genetics (ICHG). This event, hosted by the African Society of Human Genetics (AfSHG) and the Southern African Society for Human Genetics (SASHG), will reunite international experts to highlight how genomic technologies are being managed to address challenges generated by the current status of Human Health and Genomics. The European Genome-phenome Archive (EGA) will be at the Congress participating in workshops, meetings and talks where topics such as data access and discovery as well as the Federated EGA will be present. Data access and discovery In the context of the “Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. Data access and discovery In the context of the “ Federated data analysis workshop“ that will be held the 26ᵗʰ, managed in the context of the CINECA project, a hands-on-session on Beacon v2 Discovery will be led by Mauricio Moldes. Another session on authorisation and data access will be presented by Mallory Freeberg and Coline Thomas, with and introduction by Thomas Keane. During the workshop, an end-to-end federated data analysis use case will be presented. During the last four years, CINECA has been identifying gaps in data sharing between Africa, Canada and Europe in order to build a federated solution for data access. Thomas Keane will present the project within the sessions happening the 24ᵗʰ. The Federated EGA at the ICHG A Federated EGA poster will be shown during the Poster Session 1 that will take place the 23ʳᵈ. The objective is to bring awareness of the European Genome-phenome Archive as a resource for permanent archive and secure data sharing. In this context, the network generated by the Federated EGA is key for cases where research data cannot be shared outside local jurisdictions. The Federated EGA was officially launched on 2022 with research institutes from five countries becoming the first nodes of this network. Nowadays, with more than 20 nodes preparing to join, it aims to become the largest human omics data sharing initiative towards understanding human health and disease. The H3Africa Initiative and the African research represented in the EGA 1.1% of the EGA studies include samples from African populations. Countries such as South Africa, Kenya, Uganda or Egypt, among others, are present in the 72.577 samples from African individuals archived at the EGA. 23 EGA datasets are managed by the Human Heredity and Health in Africa Initiative (H3Africa). This Initiative will celebrate its Consortium Meeting the 27ᵗʰ and 28ᵗʰ, back-to-back with the ICHG. H3ABioNet, the Pan African Bioinformatics Network for the H3Africa consortium, will also take this context to celebrate its 10-Year Symposium during the Congress. Members of the EGA team will attend both of them, as the H3ABioNet works in conjunction with H3Africa projects, to submit data to the European Genome-Phenome Archive.

  Blog the-ega-at-the-international-congress-of-human-genetics

• NHLBI TOPMed - NHGRI CCDG: The BioMe Biobank at Mount Sinai

  The IPM BioMe Biobank, founded in September 2007, is an ongoing, broadly-consented electronic health record (EHR)-linked clinical care biobank that enrolls participants non-selectively from the Mount Sinai Medical Center patient population. BioMe currently comprises >42,000 participants from diverse ancestries, characterized by a broad spectrum of longitudinal biomedical traits. Participants are enrolled through an opt-in process and consent to be followed throughout their clinical care (past, present, and future) in real-time, allowing us to integrate their genomic information with their EHRs for discovery research and clinical care implementation. BioMe participants consent for recall, based on their genotype and/or phenotype, permitting in-depth follow-up and functional studies for selected participants at any time. Phenotypic and genomic data are stored in a secure database and made available to investigators, contingent on approval by the BioMe Governing Board. BioMe uses a "data-broker" system to protect confidentiality. Ancestral diversity - BioMe participants represent a broad racial, ethnic and socioeconomic diversity with a distinct and population-specific disease burden. Specifically, BioMe participants are of African (AA), Hispanic/Latino (HL), European (EA) and other/mixed ancestry. BioMe participants are predominantly of African (AA, 24%), Hispanic/Latino (HL, 35%), European (EA, 32%), and other ancestry (OA, 10%). Participants who self-identify as Hispanic/Latino further report to be of Puerto Rican (39%), Dominican (23%), Central/South American (17%), Mexican (5%) or other Hispanic (16%) ancestry. More than 40% of European ancestry participants are genetically determined to be of Ashkenazi Jewish ancestry. With this broad ancestral diversity, BioMe is uniquely positioned to examine the impact of demographic and evolutionary forces that have shaped common disease risk. Phenotypes available in BioMe - BioMe has a high-quality and validated set of fully implemented clinical phenotype data that has been culled by a multi-disciplinary team of experienced investigators, clinicians, information technologists, data-managers, and programmers who apply advanced medical informatics and data mining tools to extract and harmonize EHRs. BioMe, as a cohort, offers a great versatility for designing nested case-control sample-sets, particularly for studying longitudinal traits and co-morbidity in disease burden. Biomedical and clinical outcomes: The BioMe Biobank is linked to Mount Sinai's system-wide Epic EHR, which captures a full spectrum of biomedical phenotypes, including clinical outcomes, covariate and exposure data from past, present and future health care encounters. As such, the BioMe Biobank has a longitudinal design as participants consent to make all of their EHR data from past (dating back as far as 2003), present and future inpatient or outpatient encounters available for research, without restriction. The median number of outpatient encounters is 21 per participant, reflecting predominant enrollment of participants with common chronic conditions from primary care facilities. Environmental data: The clinical and EHR information is complemented by detailed demographic and lifestyle information, including ancestry, residence history, country of origin, personal and familial medical history, education, socio-economic status, physical activity, smoking, dietary habits, alcohol intake, and body weight history, which is collected in a systematic manner by interview-based questionnaire at time of enrollment. The IPM BioMe Biobank contributed ~10,600 DNA samples for whole genome sequencing to the TOPMed program. Samples were selected for the Coronary Artery Disease (CAD) and the Chronic Obstructive Pulmonary Disease (COPD) working groups. Using a Case-Definition-Algorithm (CDA), we identified ~4,100 individuals with CAD (~50% women) and ~3,000 individuals as controls (65% women). In addition, we identified ~800 individuals with COPD (62% women) and 1800 individuals as controls (72% women). Another 600 BioMe participants with Atrial Fibrillation, all of African ancestry, were included.

  Study phs001644

• Center for Craniofacial and Dental Genetics (CCDG): Genetics of Orofacial Clefts and Related Phenotypes

  The purpose of this study is to investigate the genetics of orofacial clefts (OFCs) in a large study population, and importantly, to incorporate subclinical phenotypic features into these studies. Orofacial clefts (OFCs) comprise a significant fraction of human birth defects (about 1/700 live births (Rahimov et al. 2012) and represent a major public health challenge, as individuals with these anomalies require surgical, nutritional, dental, speech, medical and behavioral interventions, thus imposing a substantial economic and personal burden (Berk and Marazita 2002*). The most common forms include OFCs of the lip alone (CL, Figure 1A), CL plus cleft palate (CL+CP, Figure 1B) or of the palate only (CP, Figure 1C). Individuals born with OFC may have their first surgical repair at age 3 months, but this initial surgery is just the beginning of a lifetime of health burdens. An individual born with an OFC has a hospital use rate increased for most ages (up to 233% increase for children ages 0-10 years and 16% for middle aged adults (Wehby et al. 2012). Healthcare costs for children with OFCs are estimated to be 800% greater compared with their unaffected peers (Boulet et al. 2009). Data from Denmark show that people born with CL with or without CP (CL/P) have an increased mortality up to age 55, which may be attributed to an increased risk of suicide and/or certain cancers (Christensen et al. 2004). The focus of most OFC genetic research has been CL and/or CP. Furthermore, the majority of OFC, i.e. about 70% of CL/P and 50% of CP is considered "nonsyndromic" (Jones 1988), i.e. isolated anomalies with no other apparent cognitive or structural abnormalities. Figure 1 Sample OFC Types A: Bilateral Cleft Lip; B:Cleft Lip plus Cleft Palate; C:Cleft Palate Alone The factors leading to the majority of nonsyndromic OFCs are still unclear, particularly at an individual family level. As is true for many complex traits, substantial progress in gene identification has occurred in the OFC field in the last two years (Dixon et al. 2011; Marazita 2012). Genome Wide Association Studies (GWAS) and sequencing studies to date by our research team and others have focused on genetic risk factors for overt CL/P and CPO-and have been very successful. A major finding from this work is that OFCs exhibit significant genetic heterogeneity, i.e., multiple genetic regions have been implicated (Beaty et al. 2010; Ludwig et al. 2012). Thus, approaches are needed to understand this genetic heterogeneity. Are there GxG interactions at work? Are there subsets of families, each due to a different gene? Our research group has shown that a promising approach to dissect the etiology of OFC is to focus on subclinical phenotypic features within entire cleft families (not just in affected cases, but also in their non-cleft relatives). These subtle features are believed to represent mild manifestations of the same underlying genetic susceptibility responsible for OFCs; as such, their inclusion in case-control and family-based genetic studies can help to clarify and refine the relationship between genotype and phenotype. The study population comprises a large number of families and individuals (~12,000 individuals) from multiple populations worldwide (Caucasians from the US and Europe, Asians from China and the Philippines, Mixed Native American/Caucasians from South America, and Africans from Nigeria and Ethiopia). There are cases, case families (nuclear families and extended kindreds), as well as controls with no history of OFC nor other developmental defects. *Berk NW, Marazita ML (2002) Costs of Cleft lip and Palate: Personal and Societal Implications. In: Wyszynski DF (ed) Cleft Lip and Palate: From Origin to Treatment. Oxford University Press, Inc., New York, pp 458-467.

  Study phs000774

• Prognostic and therapeutic significance of leukemia subtypes and minimal residual disease measurements in pediatric acute lymphoblastic leukemia treated with contemporary risk-directed trial: a cohort study

  Background Genomic analyses to identify leukemia subtypes and refinement of minimal residual disease (MRD) determination are two recent advances that would have substantial impact on the management of children with acute lymphoblastic leukemia (ALL). However, the combined application of these two approaches to determine the prognostic and therapeutic significance of MRD measurement and full spectrum of leukemia subtypes in the context of contemporary risk-directed therapy has not been studied comprehensively.MethodsBetween October 29, 2007 and March 26, 2017, 598 consecutive children with newly diagnosed ALL were enrolled in a clinical trial at St. Jude Children’s Research Hospital. Patients were provisional classified according to the presenting clinical and laboratory features including immunophenotype and cytogenetics. Patients with ETV6-RUNX1 and high hyperdiploid B-progenitor ALL were provisionally included in the low-risk groups; those with TCF3-PBX1, hypodiploidy and T-cell ALL in the standard (intermediate)-risk group; and patients with BCR-ABL1, KMT2A and early T-cell precursor ALL in the high-risk group. Final risk assignment was based primarily on MRD levels measured by flow cytometry on Day 15 (≥1%) and Day 42 (<0.01% or ≥1%) of remission induction. Using genomic classification based on cytogenetics and genomic analysis (single nucleotide polymorphism array analysis and transcriptome, exome, and genome sequencing), patients were classified into 17 subtypes. The primary aim was to determine the event-free survival, overall survival and cumulative risk of relapse according to specific leukemia subtypes and MRD levels on Days 8, 15 and 42 of remission induction. This clinical trial was registered at ClinicalTrials.gov, number NCT00549848.FindingsPatients with ETV6-RUNX1, high hyperdiploidy and DUX4-rearranged B-ALL all received low- or standard-risk therapy, and had the highest 5-year event-free survival rates: 98.4% (95% CI, 95.9-100), 95.3% (91.2-99.4), and 95.0% (84.2-100), respectively. All 142 patients with Day 8 MRD<0.01%, except two with KMT2A-rearranged ALL and one with TCF3-PBX1, were in continuous complete remission. The TCF3-PBX1, PAX5alt, T-cell, early T-cell precursor, iAMP21 and hypodiploid ALL had intermediate outcome with 5-year event-free survival rates ranging from 80.0% (39.4-100) to 88.2% (71.7-100). Patients with KMT2A-rearranged, BCR-ABL1, BCR-ABL1-like and ETV6-RUNX1-like ALL had the worst outcomes, with 5-year event-free survival rates between 64.1% (43.9-84.3) and 76.2% (51.9-100), despite most patients receiving standard- or high-risk therapy. Treatment intensification based on MRD and genotype improved outcome. Relapse did not occur in any of the patients with ETV6-RUNX1, DUX4-rearranged, TCF3-PBX1, iAMP21, ZNF384-rearranged, hypodiploid, or BCR-ABL1-like B-ALL who had day 15 MRD≥1% and received standard-risk therapy. However, day 42 MRD<0.01% did not preclude relapse in patients with intermediate-risk or unfavorable subtypes including TCF3-PBX1, PAX5alt, T-cell, iAMP21, BCR-ABL1, BCR-ABL1-like, ETV6-RUNX1-like, KMT2A-rearranged, and MEF2D-rearranged ALL, despite intensified treatment in the standard- or high-risk arms. InterpretationContemporary risk-directed treatment based on genotypes and MRD can cure virtually all patients with ETV6-RUNX1, hyperdiploid>50 and DUX4-rearranged ALL. While intensified treatment improve outcome for patients with high MRD during induction, substantial proportions of patients with intermediate-risk or unfavorable subtypes would still relapse even achieving negative MRD status at the end of induction and require novel therapeutics to improve outcome.

  Study EGAS00001004739

• The British Autozygosity Populations BioResource (2022-04-26)

  This data set contains whole exome sequences of individuals from 8086 (mostly British Pakistani/British Bangladeshi, mostly self-reported parentally related) individuals from the following studies: 1. 5236 British Pakistani/British Bangladeshi adults from East London Genes & Health, now known as Genes & Health 2. 2624 British South Asian mothers from Born in Bradford (mostly Pakistani) 3. 1061 British South Asian adults from Birmingham (mostly Pakistani) This dataset contains all the exome sequence data available for this study on 2022-04-26

  Dataset EGAD00001008736

• After the completion of CINECA, EUCANCan, and euCanSHare. What's next?

  CINECA, EUCANCan, and euCanSHare were part of the EUCAN Cluster, made up of six projects that received funding under the same Horizon 2020 call. All EUCAN projects (CINECA, EUCANCan, EUCAN-Connect, euCanSHare, Receptor Plus, and ReCoDID) were aimed at facilitating data reuse and knowledge discovery by enhancing data exchange and long-term collaboration in the health field. Here are some highlights about EGA’s contribution to these projects. CINECA: advances in Federated discovery and infrastructure for cohorts CINECA (Common Infrastructure for National Cohorts in Europe, Canada, and Africa) developed a federated cloud-based infrastructure for making genomic and biomolecular data accessible. The project has assembled a virtual cohort of 1.4 million individuals from sources such as the EGA, CanDIG and H3Africa. The EGA–CRG co-leaded a work package Work Package 1 on Federated Data Discovery and Querying. Beacon v2, championed by Jordi Rambla and Lauren Fromont, has been one of the central elements for the discovery of human genetic and phenotypic data. The EGA-CRG contributed to the development of a model for cohort discovery inside the Beacon v2 model. The team also delivered a Discovery Portal was implemented to explore cohorts and individuals of synthetic data. It is a UI that gathers a network of Beacons, a service for query expansion, and a visualisation tool. Have a look at the Discovery Portal UI, gathering a network of Beacons. You will find entities such as the Barcelona Supercomputing Center (BSC), BioData.pt and the European Genomic Data Infrastructure (GDI), among others. euCanSHare: facilitation of data access management This joint EU-Canada project aimed to build a European and Canadian FAIR platform for cardiovascular data sharing and analysis. The EGA’s tasks contributed to the development of the data management plan and data flows, main web-portal and interoperability protocols. An important part of the EuCanShare platform is the data access manager, a tool for the data owners to control the access to their sensitive datasets. We built a user-friendly interface for data access committees (data owners) to easily manage their data requests and access credentials. The data access portal facilitates the creation and internal organization of the data access committees as well as the linkage of data usage conditions to specific datasets. The interface includes filters for browsing requests and page to visualize the request history helping with the handling of data access requests. EUCANCan: toward a federation of clinical institutions in oncology The EUropean-CAnadian CANcer Network worked towards building a federated network to advance personalized medicine in oncology, by promoting the standard analysis, management and sharing of harmonized genomic and phenotypic data. The EGA led tasks on defining data flows and preparing an adapted infrastructure for long-term data storage and sharing. One of the key contributions was the conception of the EGA communities, offering standard and interoperable solutions for data discovery, processing, and sharing to projects and institutions that would like to manage and share data in the context of the EGA ecosystem. What's Next? The participation in projects such as CINECA, EUCANCan, and euCanSHare provide us with experience for future projects. We are happy to enhance data sharing and reuse, vital for advancing clinical and genomic research. The Discovery Portal is a wonderful proof of concept for the Beacon network. Next, we will finalise both the network and the user interface, and make sure it can be applied to more clinically-centred settings like hospitals. Most data hosted at the EGA are about cancer research. Currently, we contribute to building tools and infrastructure to empower oncology research in several European projects such as EUCAIM, EUCANIMAGE and EOSC4Cancer. We also do not lose sight of initiatives in the field such as the International Cancer Genome Consortium (ICGC) with the project ARGO, whose data model was adopted in EUCanCan.

  Blog cineca-eucancan-and-eucanshare-were-concluded-in-june

• Best Practices for DACs

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

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

• Prevention and Early Treatment of Acute Lung Injury (PETAL) Crystalloid Liberal or Vasopressors Early Resuscitation in Sepsis (CLOVERS) (PETAL CLOVERS-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL CLOVERS include plasma, and whole blood. Please note that use of biospecimens in genetic research is subject to a tiered consent. Available Data: The data available for request now include Long Term Outcome data.Objectives: To compare the effects of a restrictive fluid strategy (with early use of vasopressors) to a liberal fluid strategy in participants with sepsis-induced hypotension.Background: Intravenous fluid resuscitation is a common therapy used in the initial treatment of participants with septic shock and sepsis-induced hypotension. The goal of initial fluid therapy is to increase depleted or functionally reduced intravascular volume that occurs in sepsis due to a vasodilated vascular network. However, intravenous fluid resuscitation can create dilutional coagulopathy, fluid overload, and pathogenic edema in the lungs and other organs. Vasopressor agents are also commonly used to treat hypoperfusion by inducing constriction of arterioles and venules and increasing cardiac contractility. Vasopressor therapy also comes with risks that include vasoconstriction resulting in tissue ischemia, increased cardiac workload, and arrhythmias. Clinicians have used these strategies, typically in combination, to provide supportive care for participants with sepsis-induced hypoperfusion. However, at the time of the CLOVERS study, there was limited data to guide specific use of these therapies, including fluid volumes, in the early care of participants with sepsis-induced hypotension. The CLOVERS study hypothesized that a restrictive fluid strategy used during the first 24-hours of resuscitation for sepsis-induced hypotension would lead to lower mortality before discharge home by day 90 than a liberal fluid strategy.Participants: A total of 1,563 participants, from 60 medical centers, of the planned 2,230 participants were enrolled, with 782 assigned to the restrictive fluid group and 781 to the liberal fluid group. Enrollment in the trial was ended after the second interim analysis due to a lack of significant difference observed between the two 24-hour strategies.Design: This study was a multi-center, prospective, phase 3 randomized non-blinded interventional trial of fluid treatment strategies in the first 24 hours for participants with sepsis-induced hypotension. Participants were randomly assigned in a 1:1 ratio to either a restrictive fluid strategy (with early vasopressor use) or a liberal fluid strategy. In each group, the assigned protocol was followed for a period of 24 hours. The restrictive fluid protocol prioritized vasopressors as the primary treatment for sepsis-induced hypotension, with 'rescue fluids' being permitted for prespecified indications that suggested severe intravascular volume depletion. The liberal fluid protocol consisted of a recommended initial 2000-ml intravenous infusion of isotonic crystalloid, followed by fluid boluses administered on the basis of clinical triggers (e.g., tachycardia) with 'rescue vasopressors' permitted for prespecified indications. A protocol amendment implemented in October, 2019, allowed for limiting the initial infusion to 1,000 ml if the participant's blood pressure and heart rate had stabilized and the clinical assessment was that the participant was unlikely to benefit from additional intravenous fluid administration. The clinical team could override the protocol-specified care instructions at any time if it was judged to be in the best interest of the participant.The primary outcome was death from any cause before discharge home by day 90. Secondary outcomes included 28-day measures of the number of days free from ventilator use, days free from renal-replacement therapy, days free from vasopressor use, days out of the ICU, and days out of the hospital. Conclusions: Among participants with sepsis-induced hypotension, the restrictive fluid strategy that was used in this trial did not result in significantly lower (or higher) mortality, or other measures of recovery such as length of hospital stay, before discharge home by day 90 than the liberal fluid strategy.

  Study phs004080

• Clonal selection after gene therapy in sickle cell disease

  While gene therapy (GT) provides a potentially curative treatment option for patients with sickle cell disease (SCD), the occurrence of myeloid malignancies in clinical trials has prompted concern. To interrogate potential mechanisms underlying increased cancer risk, we used hematopoietic stem cell (HSC) clonal tracking by whole genome sequencing (WGS) to map the somatic mutation and clonal landscape of 2,592 gene modified as well as unmodified single stem and progenitor cells from six SCD patients undergoing gene therapy (7-26 years old, average 12.7× depth). Pre-GT phylogenetic trees in SCD were highly polyclonal and mutation burdens per cell were elevated in some, but not all, patients. Post-GT, no clonal expansions were identified. However, an increased frequency of driver mutations associated with myeloid neoplasms or clonal hematopoiesis (DNMT3A- and EZH2-mutated clones in particular) were seen in both genetically modified and unmodified cells suggested positive selection of mutant clones during gene therapy. This work sheds light on the mutation landscape and HSC clonal dynamics in gene therapy for SCD and highlights enhanced fitness of some HSCs harboring pre-existing driver mutations following gene therapy. Future studies should define the long-term fate of mutant clones including any contribution to expansions associated with myeloid neoplasms.

  Dataset EGAD00001010913

• Genes and Blood Clotting Study (GABC)

  Objectives: Use genome-wide approaches to identify genetic variants that influence common thrombosis and hemostasis factors, as well as selected common human traits. Design/Methods: The GABC study was a prospective sibling cohort design. Siblings were recruited by targeted email to the undergraduate and graduate student email lists at the University of Michigan. Healthy persons between 14 and 35 years old who had healthy siblings within the same age restriction were able to participate. Study participants agreed to an online informed consent and subsequently completed a 52-question online survey describing their specific bleeding traits as well as many common human traits. Fifty milliliters of blood was collected into a citrate-dextrose solution (ACD) from each participant. An aliquot of whole blood was used for an automated complete blood count analysis and the remainder was processed into platelet poor plasma and buffy coat portions. Plasma and buffy coat aliquots were snap frozen and stored in liquid nitrogen for future studies. 1189 individuals representing 507 sibships were collected between 06/26/2006 and 01/30/2009. Phenotyping Survey Details: To characterize individual bruising and bleeding history, the online survey recorded answers to questions based on a modified von Willebrand Disease (VWD) screening questionnaire. To characterize a collection of participant's common human traits, the survey recorded answers to questions about height, weight, presence of skin tags, history of acne, eye color, hair color, hair line characteristics, skin sunburn sensitivity, skin tanning ability, natural skin color, freckling, cheek dimpling, earlobe shape, shoe size, foot arch characteristics, hand fifth digit morphology, history of dyslexia, history of migraine headaches, history of seasonal allergies, history of apthous ulcers, tendency to sneeze while walking into a bright sunny place, history of dental caries, need for corrective eye lenses, handedness and like or dislike of strongly flavored foods. Biochemical phenotyping: Assays for plasma Von Willebrand Factor (VWF) antigen were performed using ELISA and "Alphalisa" techniques. Automated complete blood count analysis was performed on a Bayer Advia 120 on all participants (including WBC differential, RBC indices, and platelet count.) For the dbGaP v2 update, new biochemical phenotypes have been submitted and include von Willebrand Factor, von Willebrand Factor propeptide, plasminogen, gamma prime fibrinogen, ADAMTS 13, antithrombin III, protein C, and protein S. All new phenotypes were obtained using "Alphalisa" techniques. Genotyping Details: SNP genotyping was performed using genomic DNA extracted from peripheral blood at the Broad Institute, (MIT/Harvard). Genotyping was performed on the Illumina Omni-1 quad chip at the Broad Institute. For the dbGaP v2 update, genotyping data from the Illumina Human Exome was deposited. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to blood clotting through large-scale genome-wide association studies of siblings. Genotyping was performed at the Broad Institute of MIT and Harvard, a GENEVA genotyping center. Data cleaning and harmonization was performed by the primary investigators at the University of Michigan, Ann Arbor, and at the GEI-funded GENEVA Coordinating Center at the University of Washington. This study serves as a resource for investigators who are interested in the genetic determinants of specific plasma proteins in a healthy population. The sibling cohort design allows for linkage analysis in addition to association studies. Analysis of thrombosis and hemostasis related traits should help elucidate specific biochemical and genetic networks that maintain hemostasis. We hope to identify specific genetic determinants of VWF levels in order to better understand the factors that influence the development of VWD.

  Study phs000304

• Whole Genome Scan for Pancreatic Cancer Risk in the Pancreatic Cancer Cohort Consortium and Pancreatic Cancer Case-Control Consortium (PanScan)

  Within the framework of the NCI-sponsored Cohort Consortium, investigators from 12 prospective epidemiologic cohorts formed the Pancreatic Cancer Cohort Consortium in 2006. This study, also known as "PanScan", is funded by the National Cancer Institute (NCI) and involves conducting a genome-wide association study (GWAS) of common genetic variants to identify markers of susceptibility to pancreatic cancer. In 2007, the study was expanded to include 8 case-control studies. The study team includes scientists from the cohorts comprising the Consortium, the NCI and the Pancreatic Cancer Case Control Consortium (PanC4). PanScan I and II were conducted in 12 cohort studies and 8 case-control studies, leading to the discovery of four novel regions in the genome associated with risk for pancreatic adenocarcinoma. The third phase of PanScan (PanScan III) was conducted using recently identified incident pancreatic cancer cases drawn from fourteen cohorts from the cohort consortium, including nine prospective cohorts who participated in PanScan I, and five newly joined cohorts. The nine cohort studies that participated in PanScan I and had new genotyping of cases in PanScan III include ATBC, CPS-II, EPIC, HPFS, NHS, PHS, PLCO, SMWHS, and WHI; the five newly joined cohort studies include the Agricultural Health Study (AHS), the Multiethnic Cohort Study (MEC), the Melbourne Collaborative Cohort Study (MCCS), the Vitamins and Lifestyle Study (VITAL), and Selenium and Vitamin E Cancer Prevention Trial (SELECT). In addition to the cases from cohorts, we also included cases from the Gastrointestinal Cancer Clinic of Dana-Farber Cancer Institute Study (DFCI-GCC); from the University Hospital in Heidelberg, Germany, which is part of a larger European clinical case-control study (PANDoRA); and from clinic-based cases from eastern Spain (PANKRAS-II). The dbGaP datasets available include all subjects previously made available from PanScan I and II, plus 1,582 new incident pancreatic cancer cases of European descent from prospective cohorts, case-control studies or case series (genotyped as part of PanScan III). Also included are 61 pancreatic cancer cases and 67 control subjects from PanScan I as well as 173 pancreatic cancer cases from PanScan III of Asian ancestry from the Shanghai Men's and Women's Health Study (Supplemental Table 10, Wolpin et al. (Nat Genet, 2014)). The control population used in the analysis for the Wolpin et al. manuscript included cancer-free individuals from the prospective cohorts that contributed pancreatic cancer cases to PanScan III and controls from the Spanish Bladder Cancer SBC/EPICURO study that were previously genotyped using the OmniExpress, Omni 1M or Omni 2.5M SNP arrays. The data from these control subjects were posted to dbGaP under the GWAS in which they were initially genotyped and will not be made available in duplicate under this dbGaP study.The summary statistics for PanScan I-III were generated as detailed in Wolpin BM. et al., Genome-wide association study identifies multiple susceptibility loci for pancreatic cancer, Nature Genetics 2014; 46(9):994-1000 (https://www.nature.com/articles/ng.3052), and Klein, A. et al., Genome-wide meta-analysis identifies five new susceptibility loci for pancreatic cancer, Nature Communications, 2018;9(1):556 (https://www.nature.com/articles/s41467-018-02942-5). The dataset includes results from an association study of 5,117 individuals diagnosed with pancreatic ductal adenocarcinoma (PDAC) and 8,845 control individuals, or a total of 13,962 subjects of European ancestry (as compared to the genotype and phenotype information under this project that includes 9,437 individuals (PanScan I and II PDAC case and control individuals and PanScan III PDAC cases only). This is due to the fact that PanScan III “borrowed” GWAS data from control individuals genotyped separately from the PanScan GWAS project and are therefore not included as raw genotypes in phs000206.v5.p3. Association analysis was performed separately for PanScan I-II and PanScan III, followed by a meta-analysis of the two datasets. Results were filtered based on a minor allele frequency (MAF) < 0.01, an imputation INFO score < 0.3 and a heterogeneity P-value < 1x10-10 leaving a total of 9,758,390 variants. Columns in the summary statistics dataset are as follows: ID: variant rsIDChr: chromosome numberPosition: position in the chromosome, genome build GRCh37/hg19MarkerName: variant identifierAllele1: reference alleleAllele2: alternative alleleFreq1: allele frequency for allele2FreqSE: standard error of the allele frequencyMinFreq: the minimal allele frequency across studiesMaxFreq: the max allele frequency across studiesEffect: effect size for allele2StdErr: standard errorP-value: meta-analysis p-valueDirection: summary of effect direction for each studyHetISq: I^2 statistic which measures heterogeneity on scale of 0-100%HetChiSq: chi-squared statistic in simple test of heterogeneityHetDf: degrees of freedom for heterogeneity statisticHetPVal: P-value for heterogeneity statistic

  Study phs000206

• GEnomics and Transcriptomics of Human INsulinoma (GETHIN)

  The Genomics and Transcriptomics of Human Insulinoma (GETHIN) The common forms of diabetes - Types 1 and 2 - ultimately result from a deficiency of insulin-producing pancreatic beta cells. The Genomics and Transcriptomics of Human Insulinoma (GETHIN) study was performed in order to identify novel approaches to inducing human pancreatic beta cells to replicate and regenerate. As a corollary, developing drugs that are able to expand human beta cell mass in people with diabetes should reverse diabetes. Unfortunately, identifying druggable pathways that can enhance human beta cell replication has been a major challenge. In 2017, there is only one class of drugs - the harmine analogues - that can induce human beta cells to replicate, and in this case, higher replication rates are desirable. Thus, identifying additional drugs and druggable pathways is a priority in diabetes research. Insulinomas are rare, benign adenomas of the pancreatic beta cell that cause excess insulin production and hypoglycemia: exactly the opposite of Types 1 and 2 diabetes. Beta cell proliferation rates in insulinomas are abnormally high. Thus, the premise for The Genomics and Transcriptomics of Human Insulinoma study is that benign human insulinomas hold the genomic and transcriptomic "recipe", and the repertoire of druggable pathways, that can be exploited to induce regeneration or replication of human beta cells in diabetes. Because, insulinomas are so rare, are almost always benign (non-malignant), and are easily resected by laparoscopic surgery, little attention has been paid to understanding the genomics or transcriptomics of insulinoma. There are at present only three published studies employing next-gen sequencing in insulinoma (PMID:24326773; PMID:25787250; and PMID:25763608). These studies contained 10, 7 and 8 insulinomas, respectively, and highlighted likely mutations in YY1 and MEN1. Our goal was to markedly expand the database and to add RNAseq to these earlier studies. The GETHIN study reports next-gen sequencing on 38 insulinomas, by far the largest series of human insulinomas subjected to next-gen sequencing (see the Selected publications section for reference). This includes paired (genomic plus tumor) whole exome sequencing on 26 human insulinomas (22 sequenced at Mount Sinai, 4 downloaded from Cao et al, PMID:24326773), and 25 sets of RNAseq from insulinomas, some of which also had paired whole exome sequencing, and some of which did not. The insulinoma RNAseq was compared to RNAseq from 22 sets of FACS-sorted normal human beta cells. Since insulinomas are so rare, the 38 insulinomas were collected by several investigators at several institutions over several decades, but most (22 whole exome sets, and all RNAseq) were sequenced at the Icahn School of Medicine at Mount Sinai in New York. The current dataset contains whole exome sequencing and RNAseq on the 11 insulinomas harvested at Mount Sinai. The four from Cao et al can be retrieved from Cao et al PMID:24326773. Fastq files from the remaining 23 insulinomas will be added as the local IRBs and Institutional Certifications are acquired. Complete patient data are provided in our Nature Communications report. Going forward, our intention is to expand this series, with the goal of sequencing 100 human insulinomas. These will be added to dbGaP as they accrue. Paired-end whole exome sequencing (mean usable sequencing depth 79X and 105X for blood and insulinoma, respectively) was performed using an Illumina HiSeq 2500. Insulinoma and sorted normal beta cell RNAseq was performed on Ribozero and polyA paired end libraries using the Illumina HiSeq 2500. Complete sequencing and bioinformatic details are provided in our Nature Communications report. The principal findings from the study are that although each insulinoma has a different set of presumptive driver mutations, the majority converge on genes that are members of the Polycomb Complex, Trithorax Complex and other epigenetic modifying enzymes. In addition, 20% of insulinomas have copy number loss or loss of heterozygosity of all or most of chromosome 11, and the majority display abnormalities in CpG methylation and imprinting control on the imprinted Chr 11 p15.5-15.4 region that contains INS, IGF2, CDKN1C, KCNQ1, and other genes involved in beta cell specification and proliferation.

  Study phs001422

• TRanscriptomic ANalySis of left ventriCulaR gene Expression (TRANSCRibE)

  Myocardial ischemia occurs when there is a mismatch between coronary oxygen delivery and metabolic requirements of the myocardium, which may be clinically manifested during angina, coronary angioplasty or cardiopulmonary bypass (CPB). Myocardial ischemia may lead to a spectrum of myocardial stunning, hibernating myocardium, and ultimately cell death if the ischemic insult is severe. In the human heart, irreversible damage begins after approximately 20 to 40 minutes of oxygen deprivation. Observed molecular and cellular changes of myocardial ischemia are characteristic of an inflammatory response, but the exact mechanisms that underlie this pathological process are unclear and may not be full emulated by animal models of ischemia or infarction. Thus, we felt it valuable to investigate a human ischemia model. During cardiac surgery, CPB with aortic cross-clamping (AoXC) and cardioplegic arrest is associated with excellent clinical outcomes and suitable operative conditions. However, despite the use of cardioprotective strategies, AoXc during CPB is accompanied by a variable, yet obligate ischemic period lasting 1 to 3 hours, resulting in hypoxia, metabolic substrate depletion, reperfusion injury, apoptosis, and necrosis. Cardiac specific biomarkers of ischemia and infarction, including troponin, are elevated even after routine coronary artery bypass graft surgery and correlate with the duration of ischemia from AoXc.This process of CPB provides us with the ability to examine the transcriptional profile before and after an expected, consistent, and reproducible human ischemic event, albeit induced by cold cardioplegic arrest and not coronary occlusion. In addition, the absence of reperfusion in this time period allows us to examine the transcriptomic response to intermittent ischemia, without having to account for the perturbations of reperfusion injury. Although various animal models have been used to examine the effects of ischemia on cardiac function, no human data exist which examine the early transcriptomic response to a left ventricular (LV) ischemic insult. We therefore characterized the effect of cold cardioplegia induced acute ischemia on the transcriptional profile of the LV by performing whole transcriptome next-generation RNA-sequencing (RNA-seq) in patients undergoing cardiac surgery by sampling human LV tissue prior to, and after, the obligate ischemia during AoXC. We hypothesized that the cold cardioplegia induced ischemic injury will dramatically alter transcription in the human myocardium, and that we would identify genes and pathways, which will identify interventional targets for pharmacological therapy. Methods:We have collected left ventricle tissue samples and blood sample from patients undergoing heart surgery. We obtained punch biopsies (~3-5μg total RNA content) from the site of a routinely placed surgical vent in the anterolateral apical left ventricular wall of patients undergoing elective aortic valve replacement surgery with cardiopulmonary bypass. After an average of 79 minutes of aortic cross-clamping with intermittent cold blood cardioplegia for myocardial protection every 20 minutes, a second biopsy was obtained in the same manner. Tissue samples were immediately placed in RNAlater® (Ambion, ThermoFisher Scientific, Waltham, MA), and after 48 hours at +4°C were stored at -80°C until RNA extraction. Total RNA was isolated with Trizol and RNA quality was assessed using the Agilent Bioanalyzer 2100 (Agilent, Santa Clara, CA). Libraries were prepared by poly(A) mRNA isolation and reverse transcription Polymerase Chain Reaction (RT-PCR), then sequenced on the Illumina HiSeq2000 or HiSeq2500 (Illumina, San Diego, CA). As samples were analyzed at different times, different read lengths were employed, initially using single-end reads (n=20) and then transitioning to paired end reads (n=216), ranging from 36 - 100 base pairs. Raw sequencing files were processed using Sickle, Skewer, and STAR software, and aligned to GrCh37 or UCSC Hg19. DNA was isolated from whole blood using standard methods. SNP genotyping was performed using the Illumina Omni2.5Exome-8 BeadChip array with additional exome content (Illumina, San Diego, CA) chip, version 1.1. We first phased and imputed 93 subjects using a phasing tool called SHAPEIT and an imputation tool called MINIMAC, with 1000 Genomes phase 1 version 3 for the reference panel. We then phased and imputed 26 more subjects using SHAPEIT, an imputation tool called IMPUTE2, and 1000 Genomes phase 3 version 5.

  Study phs001679

• Genetic Basis of Early Onset Bicuspid Aortic Valve Disease

  The study protocol was approved by the Committee for the Protection of Human Subjects at the University of Texas Health Science Center at Houston (HSC-MS-11-0185). Study recruitment began on July 1, 2017, and concluded on March 30, 2022. After written informed consent, we enrolled probands with early onset BAV disease (EBAV), which we defined as individuals with BAV who were under the age of 30 at the time of first clinical event. Clinical events were defined as aortic replacement, aortic valve surgery, aortic dissection, moderate or severe aortic stenosis or aortic regurgitation, large aneurysm (Z > 4.5), or intervention for BAV-related conditions. Those with hypoplastic left heart, known genetic mutations, genetic syndromes, or complex congenital heart disease were excluded. Samples were collected and genotyped as previously reported. For comparison, we analyzed a cohort of older individuals of European ancestry with sporadic BAV disease selected from the International BAV Consortium (BAVGWAS). Phenotypes were derived from record review with confirmation of image data whenever possible [25-26]. The computational pipeline for CNV analysis of Illumina single nucleotide polymorphism (SNP) array data included three independent CNV detection algorithms.GenomeStudio was used to exclude samples with indeterminate sex or more than 5% missing genotypes, and single nucleotide polymorphisms (SNPs) with GenTrain = 0. Principal component analysis was used to remove outliers that did not cluster with European ancestry. Prior to CNV analysis, each dataset was trimmed by selecting a common set of 650,000 SNPs that were genotyped on each of the microarrays used in this study.Three independent algorithms (PennCNV, cnvPartition, and QuantiSNP) were used to generate CNV calls and sample-level quality statistics from SNP intensity data. PennCNV and QuantiSNP were run on Unix clusters and cnvPartition data were exported from GenomeStudio. The analysis was run using default configurations. PennCNV was used to generate QC data and remove CNV calls that intersect with polymorphic genomic regions. Samples that met any of the following criteria were excluded, standard deviation of the LogR ratio (obtained from PennCNV) > 0.35 or number of CNVs > 2 standard deviations above the mean for each data set. CNV calls less than 20 Kilobases in length and/or spanned by fewer than 6 probes were excluded. The overlap function for rare CNVs in PLINK was used to construct CNV regions (CNVRs) after adjacent regions were merged using PennCNV. LogR ratio (LRR) and B allele frequency (BAF) data at CNVRs and calls of interest were visualized in GenomeStudio for validation. For segregation analysis, GenomeStudio was used to determine the presence of CNVs in relatives.A total of 22,014 unselected control Illumina Genotypes obtained from the Database of Genotypes and Phenotypes were analyzed using identical methods (S1 Table). The Wisconsin Longitudinal Study (WLS) includes data on a cohort of 10,300 individuals who graduated from Wisconsin high schools in 1957. The Health and Retirement Study (HRS) includes data on 37,000 individuals aged 50 above from 23,000 households across the United States. Principal component analysis was used to select European ancestry genotypes from these datasets for analysis. Datasets were paired for case-control analysis based on the concordance of log-transformed sample-level quality control statistics (number of CNV calls and standard deviation of logR ratios). Chi-squared or Fisher exact tests were used to compare CNV frequencies in cases and controls.Rare CNV functions in PLINK (v1.7) were used to perform permutation-based burden tests or gene set-based enrichment tests. Case control burden tests were restricted to CNVs that were longer than 110 Kb and less than 0.1% in frequency. CNV overlap functions in PLINK were used to identify rare CNVs that intersect between datasets or involve specific BAV or CHD genes . The list of candidate genes included 190 CHD genes that have strong cumulative evidence to cause BAV or related congenital malformations from human or animal model data. Genome Reference Consortium Human Build 37 was used for CNV annotation [34].

  Study phs003705

• Submitter Portal

  Submitter Portal The Submitter Portal does not support array submissions! Please refer to the array documentationAny new objects registered in the Submitter Portal will not be available for use in an array submission For further information please check our Submission FAQs, submission quickguide as well as submission terms! The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. Submitter Portal Index Previous steps Access to Submitter Portal Start a Submission Take The Tour Tutorial Previous steps Create your EGA account To submit data, you first need to create your EGA user. Then, once your account has been verified by the Help Desk team, you will be able to request a submitter role and send the EGA Data Processing Agreement (DPA). In the case you already have an EGA account, or an ega-box (submission account), you can skip this step. Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role and added your public key to your profile, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find relevant information in the DAC Portal Guide. Access to Submitter Portal 1. Request Submitter Role Once you have created your EGA user, request a Submitter Role and complete relevant information such as submission type and size. 2. Signature of the Data Processing Agreement The Data Processing Agreement (DPA) signed by CRG and EMBL-EBI (Joint Data Processors for the EGA) can be downloaded to the submitter for its signature. Further information related to the DPA can be in the Privacy Notice section. The DPA should be signed by a legal representative of the submitter with power of attorney/appointment duly authorised to sign contracts on behalf of the institution. The submitter will return a fully-executed copy of the DPA to us. Please note that due to the high volume of submissions to EGA the DPA is non-negotiable. Once you have completed all the information and attached the DPA signed, send your Submitter request and the EGA Helpdesk Team will validate it and send a confirmation to start submitting your metadata. Start a Submission The steps below will show you how to start a submission and are accompanied with a tutorial and the Take the tour of Submitter Portal. 1. Login Go to the Submitter Portal interface and log in using your EGA account credentials. 2. Create a submission The Submitter Portal interface will show you any already existing open submissions. To start a new submission, click on “Create a Submission”.In this phase, you have the option to add any collaborator(s) as well as their permissions (“Read only”, “Read & Write” or “Full Access”). Please note that to add a collaborator, they must also have a submitter role. When adding a collaborator, please enter the user’s full email address in the search field and select the user. For security reasons, the portal does not display partial matches, so the full email address must be entered.The collaborator option is available while the submission is open. In the event that the submission is closed, you will need to reopen it. To do this, you only need to make a small modification in any objects within the submission, for example, copy and paste a title or description of the submission. Once the submission is open, you can add a collaborator. Further information can be found in the Submission Tour 3. Create Study Click on Add Study and complete the form with the relevant information. The fields with an asterisk (*) are mandatory. Further information can be found in the Submission Tour4. Create Sample Sample registration can be done either individually or in batches by using a template. Batch upload: download the template and complete it with information about the sequencing samples. Upload the samples.csv, and the sample will be created.Add a single sample: complete the mandatory fields with the metadata information of your sample.  Further information can be found in the Submission Tour5. Create Experiment Register an experiment with ​information about the sequencing methods, protocols, and machines. Experiments generate the connection between the samples and the study. Further information can be found in the Submission Tour6. Create Run Samples, experiments, and files are linked through runs. To register a run, you will be asked to select the appropriate experiment and the file format. Run registration can be done either individually or in batches by using a template. Batch upload: download the template and complete it with the sample file linkage. Upload the run.csv, and the runs will register.As the INBOX is a directory, bear in mind to include the file path (/). Example: /filename.c4gh.Add single run: select the file format, sample, and experiment from the drop box. For re-using submitted samples, please use the EGA accession ID (EGANXXX). Please note that files must be uploaded to your inbox before linking your files and samples. Further information can be found in the Submission Tour7. Create Analysis Analysis should be only used for BAM/BAI or CRAM/CRAI pair, VCF, and phenotype linkage to samples. The analysis is an EGA-specific metadata object that links samples to files. This object also stores some metadata about your experiments, such as the experiment type, genome reference, or the platform used. **If only BAM or CRAM alignment files are submitted but not the original unaligned FASTQ files, then please make sure that the BAM or CRAM files also contain the unaligned reads. This is critical to enable primary re-analysis and re-alignment of the dataset using new tools or future genome assemblies.** Start by selecting the samples to be linked to the file, and then populate the required attribute fields. Please be aware of the existence of mandatory fields that must be populated.When populating the chromosome field (mandatory), please select the chromosomes from the checkbox. Please take in consideration that EGA allows for the re-use of any registered metadata. Therefore, a previously registered study or samples can be referenced for the analysis in the current data submission.Further information can be found in the Submission Tour 8. Create Dataset Dataset contains the collection of runs/analysis data files subjected to controlled access by being associated with a Policy. Complete the mandatory fields such as title, description, type and policy. Please, take in consideration that DAC and Policy must be registered in advance in the DAC Portal. Similar to other metadata objects, you can re-use previous runs or analyses, using their EGA accessions IDs (runs - EGAR, analyses - EGAZ). If you would like your dataset to be added to the cBioPortal instance, please review the cBioPortal documentation.Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested, please delete them from your SFTP INBOX after finalising your submission. This will prevent the files from reappearing in your Submitter Portal Inbox. Once you have completed your submission, click on the Finalise button and schedule an estimated release date. Afterwards, your submission will be sent to Helpdesk for approval. Please note that once the Helpdesk has approved your submission, you will receive the identifiers for your data. See the Frequently Asked Questions (FAQ) for more information. 10. Update closed submission If you want to append more files to a closed submission, you will need to reopen the submission where the dataset is registered.Please note that you can only modify datasets that begin with the ID EGAD5XXXXXXX.  Find the Submission: go to the Submitter Portal Menu -> Datasets section and find the submission ID (EGA0XXX). Reopen the submission where the dataset is located: to reopen a submission, simply register new metadata, such as runs or analyses, and the submission will automatically reopen and appear on the main page. You can also do a small edition, such as copying and pasting a title or description. Take The Tour The Submitter Portal Take The Tour is a visual guide of all the steps described previously about how to start a submission. Tutorial In this tutorial, we will show you how to use the Submitter Portal to register your metadata. Please note the video focuses on the run-based submission (for raw files - fastq - and aligned data - BAM/CRAM) and analysis-based submission (for your BAM/BAI pairs, variation -VCF - and phenotype files).

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal

• 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

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• 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

• Privacy Notice for Helpdesk service

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

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

• Transdisciplinary Research Into Cancer of the Lung (TRICL) - Exome Plus Targeted Sequencing

  The study was conducted under the auspices of the Transdisciplinary Research In Cancer of the Lung (TRICL) Research Team, which is a part of the Genetic Associations and MEchanisms in ONcology (GAME-ON) consortium, and associated with the International Lung Cancer Consortium (ILCCO). Ethics All participants provided written informed consent. All studies were reviewed and approved by institutional ethics review committees at the involved institutions. Sequencing data are derived from four sub-studies. The sub-studies that contributed include Harvard, Liverpool, Toronto, and IARC. The IARC and Toronto studies are described above. A description of the Harvard and Liverpool studies is provided below. Liverpool Lung Project: The Liverpool Lung Project (LLP)1 is a case control and cohort study, which has over 11,500 individuals, with detailed epidemiological, clinical and outcome data with associated specimens (i.e. tumour tissue, blood, plasma, sputum, bronchial lavage, EBUS and oral brushings). The participants have completed a detailed lifestyle questionnaire and updated data on clinical outcome and hospital events are collected through the Office of National Statistics, Cancer Registry and from Health Episode Statistics. The project is registered on the UK National Institute for Health Research (NIHR) lung cancer portfolio and has all the required ethical approvals and sponsorship arrangements in place. The LLP has detailed standard operating procedures (SOP) for all aspects of the recruitment, data, specimen collection as well as the data storage. The LLP Cohort study has 8,224 participants with blood and 7,761 with plasma samples. The LLP case-control samples have been incorporated into in a large number of international GWAS and molecular studies 2,3, methylation 4-7, microRNA 8and next generation studies 9-11, resulting in high ranking publications, as well as forming the basis for the LLP risk prediction model 12-14 which has been utilised in the UK lung cancer screening trial (UKLS) 15-17 Patient and control DNAs were derived from EDTA-venous blood samples. Harvard Samples. David Christiani at the Harvard University School of Public Health has been directing research studies to investigate etiological factors influencing lung cancer development since 1983 and has amassed a collection of 2000 controls and 5055 lung cancer cases. He has been actively collecting and storing snap frozen tumor samples since 1992. Around 1500 tumor samples have been collected and the average wet tumor yield is about 30 grams of tumor, of which 631 cases have completely annotated clinical and survival information. Pathology confirmation is provided by two pathologists. At the time of surgery, a minimum of 30 grams of wet lung tumor tissue and 30 grams of non-involved tissue from the same lobe is sectioned, flash frozen and sent to Dr. Christiani&#39;s lab for logging and storage. A blood sample for DNA and serum is collected. A structured interview by trained research staff is conducted on each case, and clinical outcomes and treatments is extracted and entered into the molecular epidemiology data base at Harvard. Fresh frozen samples have been collected from 1451 lung cancer and are available for study. Samples from this collaborative study have played key roles in major studies, including the initial finding describing EGFR mutations in lung cancer 22. Participants in this study are patients, &#62; 18 years of age, with newly diagnosed histologically confirmed lung cancer. Samples that are included in the analysis have the following histologies: Adenocarcinoma: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3 8560/3; LCC: 8012/3, 8031/3; squamous carcinoma: 8070/3, 8071/3, 8072/3, 8074/3; and other NSCLC: 8010/3, 8020/3, 8021/3, 8032/3, 8230/3. The Toronto Study: The Toronto study was conducted in the Great Toronto Area between 1997 and 2014. Cases were recruited at the hospitals in the network of University of Toronto and Lunenfeld- Tanenbaum Research Institute. At the time of recruitment in the clinical setting, provisional diagnoses of lung carcinoma were first assigned based on clinical criteria. Diagnoses for all cases included were histologically confirmed by the reference pathologist who is a specialist in pulmonary pathology, based on review of pathology reports from surgery, biopsy or cytology samples in 100% of cases. Diagnostic classification was done initially according to ICD-9, ICD-10, and ICD for oncology-2, and subsequently converted to ICD-O-3. Tumors were grouped into the major categories included in this analysis according to primary cancer type based on the ICD-3 definitions. Controls were randomly selected from individual visiting family medicine clinics and Ministry of Finance Municipal Tax Tapes. All subjects were interviewed using a standard questionnaire and information on lifestyle risk factors, occupational history, medical and family history was collected. Blood samples were collected from more than 85% of the subjects. IARC: The IARC data are derived from case-control studies conducted in Russia and include samples that have available tissue samples. Patient and control DNAs were derived from EDTA-venous blood samples. The lung cancer patients were classified according to ICD-O-3; SQ: 8070/3, 8071/3, 8072/3, 8074/3; AD: 8140/3, 8250/3, 8260/3, 8310/3, 8480/3, 8560/3, 8251/3, 8490/3, 8570/3, 8574/3; with tumous with overlapping histologies classified as mixed. The Lung Cancer Transdisciplinary Research Cohort is utilized in the following dbGaP sub-studies. To view genotypes, other molecular data, and derived variables collected in these sub-studies, please click on the following sub-studies below or in the "Sub-studies" section of this top-level study page phs000876 Lung Cancer Transdisciplinary Research Cohort. phs000877 Meta Analysis phs000878 CIDR Lung Cancer phs001681 Affy Axiom Array

  Study phs000876

• Submission FAQ

  Submission FAQ Before Submission Is the EGA the right archive for my data? The 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. How can I add my dataset to the cBioPortal instance? In order to link your data to the cBioPortal, you must register it as a normal dataset in the Submitter Portal. For more information, please refer to the cBioPortal documentation. 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