17274 results for "the best way to get coins in fc 26 Navštivte Buyfc26coins.com Společnost známá transparentními transakcemi..CQ2q"

in 66.25 milliseconds.

• Anaplastic meingioma methylation

  Methylation of anaplastic meningiona samples

  Dataset EGAD00010001629

• Region-specific Transcriptome Analysis of the Human Retina and Retinal Pigment Epithelium (RPE)/Choroid

  Proper spatial differentiation of retinal cell types is necessary for normal human vision. Many retinal diseases, such as Best disease and male germ cell associated kinase (MAK)-associated retinitis pigmentosa, preferentially affect distinct topographic regions of the retina. While much is known about the distribution of cell types in the retina, the distribution of molecular components across the posterior pole of the eye has not been well-studied. To investigate regional difference in molecular composition of ocular tissues, we assessed differential gene expression across the temporal, macular, and nasal retina and retinal pigment epithelium (RPE)/choroid of human eyes using RNA-Seq. RNA from temporal, macular, and nasal retina and RPE/choroid from four human donor eyes was extracted, poly-A selected, fragmented, and sequenced as 100 bp read pairs. Digital read files were mapped to the human genome and analyzed for differential expression using the Tuxedo software suite. Retina and RPE/choroid samples were clearly distinguishable at the transcriptome level. Numerous transcription factors were differentially expressed between regions of the retina and RPE/choroid. Photoreceptor-specific genes were enriched in the peripheral samples, while ganglion cell and amacrine cell genes were enriched in the macula. Within the RPE/choroid, RPE-specific genes were upregulated at the periphery while endothelium associated genes were upregulated in the macula. Consistent with previous studies, BEST1 expression was lower in macular than extramacular regions. The MAK gene was expressed at lower levels in macula than in extramacular regions, but did not exhibit a significant difference between nasal and temporal retina. The regional molecular distinction is greatest between macula and periphery and decreases between different peripheral regions within a tissue. Datasets such as these can be used to prioritize candidate genes for possible involvement in retinal diseases with regional phenotypes. Reprinted from Whitmore, S.S., Wagner, A.H., DeLuca, A.P., Drack, A.V., Stone, E.M., Tucker, B.A., Zeng, S., Braun, T.A., Mullins, R.F., Scheetz, T.E., 2014. Transcriptomic analysis across nasal, temporal, and macular regions of human neural retina and RPE/choroid by RNA-Seq. Experimental Eye Research. Used under Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported license. Additional RNA sequencing was performed on temporal, macular, nasal, inferior, and superior retina from a fifth subject and is included in this dataset. See original publication for details.

  Study phs001151

• PD-L1 blockade in combination with carboplatin as immune induction in metastatic lobular breast cancer: the GELATO-trial

  Invasive lobular breast cancer (ILC) is the second most common histological breast cancer subtype but published data on trials specific for ILC are so far lacking. Translational research revealed that a subset of ILCs may be immune-related and more sensitive to DNA-damaging agents such as platinum. In murine ILC models, synergy between immune checkpoint blockade and platinum has been observed. Here, we tested this concept in the phase II, GELATO-trial (NCT03147040), in which patients with metastatic ILC were treated with weekly carboplatin (AUC 1.5) as immune induction treatment for 12 weeks and atezolizumab (PD-L1 blockade; every three weeks) from the third week onwards until disease progression. Four out of 23 evaluable patients had a partial response (17%, 95%CI 5-39%) and two patients had stable disease for at least 24 weeks, resulting in a clinical benefit rate of 26% (95%CI 10-48%). Out of these six patients, four patients had triple-negative ILC (TN-ILC). In serial biopsies of metastatic lesions, we observed higher CD8 T-cell infiltration, expression of immune checkpoints, and exhausted T cells upon carboplatin/PD-L1 blockade. This is the first report of a clinical trial specifically for ILC and we demonstrate promising anti-tumor activity of atezolizumab with carboplatin as immune induction, in particular for TN-ILC. While activity of carboplatin/PD-L1 blockade in classical ER+ ILC was limited, our translational data yield important insights for the design of highly needed clinical trials in ILC.

  Study EGAS00001006902

• PATL2 is a key actor of oocyte maturation whose invalidation causes infertility in women and mice

  The genetic causes of oocyte meiotic deficiency (OMD), a form of primary infertility characterised by the production of immature oocytes, remain largely unexplored. Using whole exome sequencing, we found that 26% of a cohort of 23 subjects with OMD harboured the same homozygous nonsense pathogenic mutation in PATL2, a gene encoding a putative RNA-binding protein. Using Patl2 knockout mice, we confirmed that PATL2 deficiency disturbs oocyte maturation, since oocytes and zygotes exhibit morphological and developmental defects respectively. PATL2's amphibian orthologue is involved in the regulation of oocyte mRNA as a partner of CPEB. However, Patl2's expression profile throughout oocyte development in mice, alongside colocalisation experiments with Cpeb1, Msy2 and Ddx6 (three oocyte RNA-regulators) suggest an original role for Patl2 in Mammals. Accordingly, transcriptomic analysis of oocytes from WT and Patl2-/- animals demonstrated that in the absence of Patl2, expression levels of a select number of highly relevant genes involved in oocyte maturation and early embryonic development are deregulated. In conclusion, PATL2 is a novel actor of mammalian oocyte maturation whose invalidation causes OMD in humans.

  Study EGAS00001002903

• Single cell sequencing of a post-PD-1 inhibitor metastatic melanoma mass

  Three technical replicates of FACS-sorted T cells (CD45+CD3+) and one replicate of FACS-sorted tumor cells (MCSP+) were loaded to a targeted 10,000 cells per lane on the 10X Genomics Chromium Controler with the single cell 5’ Immune Repertoire and Gene Expression profiling kit. In total, we loaded ~30,000 individual tumor infiltrating lymphocytes (TILs) and ~10,000 melanoma cells on the 10X platform (10X Genomics, CA, USA). Reverse transcription, TCR enrichment, and library preparations were performed according to the 10X Genomics 5’ V(D)J protocol revision C. Transcriptome libraries were pooled and sequenced on the Illumina NovaSeq 6000 S2 flow cell with 26 R1, 8 i7, and 91 R2 cycles respectively. The TCR libraries were pooled and sequenced on the Illumina MiSeq V2 150 cycles paired-end. Single cell transcriptomic and TCR data was processed with the 10X Genomics Cell Ranger Pipeline version 2.2.0 with the software-provided GRCh38 reference transcriptomes. After quality control, there was RNAseq profile data available from 6267 immune and 4303 melanoma cells. Downstream processing and visualization was encompassed through Seurat and tSNE plots.

  Dataset EGAD00001006013

• NEI CIDR Methylation Profiling of Primary Open Angle Glaucoma in NEIGHBOR Samples

  This is a case-control study of Primary Open Angle Glaucoma (POAG). POAG is a progressive optic neuropathy that eventually leads to blindness. More than 30 million people worldwide have Primary Open Angle Glaucoma (POAG), of which greater than 3 million are blind. Gene expression changes in the retina have been observed for POAG. Several recent studies, including the NEIGHBOR consortium (NEI Glaucoma Human genetic collaboration) have used GWAS to identify correlative regions of the genome. Despite this, the genetic basis of Glaucoma is not well understood. Epigenetic variation may account for low heritability and environmental effects on human disease. Despite the significant advances being made in understanding the role of epigenetics in gene regulation in other fields, little is known about the relationship between DNA methylation patterns, retinal gene expression, and retinal disease. The goal of this study is to identify differentially methylated regions in the peripheral blood of patients with POAG. The case identification is as per the NEIGHBOR description: Cases and controls were recruited from ophthalmology clinics and were examined by ophthalmologists. For cases the clinical exam included intraocular pressure measurements, optic nerve assessment and visual field evaluation. Controls had no family history of glaucoma, normal intraocular pressure and normal optic nerves. POAG and control samples come from two sources: Duke University and Massachusetts Eye and Ear Infirmary (MEEI). These samples were collected and genotyped as part of the NEIGHBOR study. From the 219 POAG cases contributed to NEIGHBOR by Duke, 75 samples were selected for exome sequencing by Dr. Terry Gaasterland (UCSD) as part of an ARRA grant. These samples were selected to mirror the distribution of the entire set of Duke patients for variables such as age, cup-to-disc ratio, CCT, and IOP. From these 75 patients, 43 were selected for our study and an additional seven patients chosen at random, for a total 50 patients from Duke. From the 219 Duke controls, 50 were selected to match the age (at the time of blood draw) and sex of the 50 Duke POAG patients. From the NEIGHBOR control samples from MEEI, 27 were selected who best matched the age (at blood draw), time since sample collection and sex of the POAG probands from GLAUGEN. Additional individual-level phenotype and genotype data may be obtained through the authorized access portal of phs000238 (Neighbor - Glaucoma GWAS Study).

  Study phs000458

• Exome sequencing of uterine leiomyosarcomas

  Uterine leiomyosarcomas (ULMSs) are aggressive smooth muscle tumors associated with poor clinical outcome. Despite previous cytogenetic and molecular studies, their molecular background has remained elusive. To examine somatic variation in ULMS, we performed exome sequencing on 19 tumors. Altogether 43 genes were mutated in at least two ULMSs. Most frequently mutated genes included tumor protein P53 (TP53; 6/19; 33%), alpha thalassemia/mental retardation syndrome X-linked (ATRX; 5/19; 26%), and mediator complex subunit 12 (MED12; 4/19; 21%). Unlike ATRX mutations, both TP53 and MED12 alterations have repeatedly been associated with ULMSs. All the observed ATRX alterations were either nonsense or frameshift mutations. ATRX protein levels were reliably analyzed by immunohistochemistry in altogether 44 ULMSs, and the majority of tumors (23/44; 52%) showed clearly reduced expression. Loss of ATRX expression has been associated with alternative lengthening of telomeres (ALT), and thus the telomere length was analyzed with telomere-specific fluorescence in situ hybridization. The ALT phenotype was confirmed in all ULMSs showing diminished ATRX expression. Exome data also revealed one nonsense mutation in death-domain associated protein (DAXX), another gene previously associated with ALT, and the tumor showed ALT positivity. Aberrant expression of both TP53 and ATRX were associated with poor overall survival. In conclusion, exome sequencing revealed that TP53, ATRX, and MED12 are frequently mutated in ULMSs. ALT phenotype was commonly seen in tumors, indicating that ATR inhibitors, which were recently suggested as possible new drugs for ATRX-deficient tumors, could provide a potential novel therapeutic option for ULMS.

  Study EGAS00001001612

• Neoadjuvant combination PD-L1 plus CTLA-4 blockade in patients with cisplatin-ineligible operable urothelial carcinoma

  Immune checkpoint therapy (ICT) is being tested in the neoadjuvant setting for patients with localized urothelial carcinoma (UC), with one study reporting data in cisplatin-ineligible patients who received anti PD-L1 monotherapy. The study reported that patients with bulky tumors, a known high-risk feature defined as greater than clinical T2 disease, had fewer responses, with pathologic complete response (pCR) rate of 17%. Here, we report on the first pilot combination neoadjuvant trial (NCT02812420) with anti-PD-L1 (durvalumab) plus anti-CTLA-4 (tremelimumab) in cisplatin-ineligible patients, with all tumors identified as having high risk features (N=28). Primary endpoint was safety and we observed 6 of 28 patients (21%) with grade ≥3 immune-related adverse events, consisting of asymptomatic laboratory abnormalities (N=4), hepatitis and colitis (N=2). We also observed pCR of 37.5% and downstaging to pT1 or less in 58% of patients who completed surgery (N=24). In summary, we provide initial safety, efficacy and biomarker data with neoadjuvant combination anti-PD-L1 plus anti-CTLA-4, which warrants further development for patients with localized UC, especially cisplatin-ineligible patients with high-risk features who do not currently have an established standard-of-care neoadjuvant treatment. Publication: Gao et al. Neoadjuvant PD-L1 plus CTLA-4 blockade in patients with cisplatin-ineligible operable high-risk urothelial carcinoma. Nature Medicine volume 26, pages1845–1851(2020)

  Study EGAS00001004074

• Pancreatic adenocarcinoma QCMG 20110901

  Pancreatic adenocarcinoma QCMG 20110901

  Dataset EGAD00001000049

• Heart Failure Network: Diuretic Optimization Strategies Evaluation in Acute Heart Failure (HFN DOSE-BioLINCC)

  ObjectivesThe DOSE study sought to evaluate the most effective dosing (high vs. low) and administration (continuous infusion vs. intermittent boluses) combination of the diuretic Furosemide in the treatment of patients with acute decompensated heart failure.BackgroundAcute decompensated heart failure is the most common cause of hospital admissions among patients older than 65 years of age and is responsible for more than 1 million hospitalizations annually in the United States. Intravenous loop diuretics are an essential component of current treatment and are administered to approximately 90% of patients who are hospitalized with heart failure. Despite decades of clinical experience with these agents, prospective data to guide the use of loop diuretics are sparse, and current guidelines are based primarily on expert opinion. As a result, clinical practice varies widely with regard to both the mode of administration and the dosing.SubjectsA total of 308 patients were enrolled between March 2008 and November 2009 at 26 clinical sites in the United States and Canada. DesignThe DOSE study was a prospective, randomized, double-blind, controlled trial with a 2-by-2 factorial design. Patients were randomly assigned to either a low-dose strategy (total intravenous furosemide dose equal to their total daily oral loop diuretic dose in furosemide equivalents) or a high-dose strategy (total daily intravenous furosemide dose 2.5 times their total daily oral loop diuretic dose in furosemide equivalents) and to administration of furosemide either by intravenous bolus every 12 hours or by continuous intravenous infusion.The study treatment, with group assignments concealed, was continued for up to 72 hours. At 48 hours, the treating physician had the option of adjusting the diuretic strategy on the basis of the clinical response. An assessment of biomarkers, including creatinine, cystatin C, and N-terminal pro-brain natriuretic peptide, was performed at a central core laboratory at baseline, 72 hours, and 60 days. Patients were followed for clinical events to day 60. The coprimary end points were patients' global assessment of symptoms, quantified as the area under the curve (AUC) of the score on a visual-analogue scale over the course of 72 hours, and the change in the serum creatinine level from baseline to 72 hours.ConclusionsAmong patients with acute decompensated heart failure, there were no significant differences in patients' global assessment of symptoms or in the change in renal function when diuretic therapy was administered by bolus as compared with continuous infusion or at a high dose as compared with a low dose. (Felker et. al., 2011, PMID: 21366472)

  Study phs003524

• Cryptococcosis in Previously Healthy Adults

  Cryptococcus is a fungus that causes infections most commonly in immunocompromised patients, such as those with AIDS and solid organ transplant recipients and is currently responsible for an estimated 15% of all AIDS-related deaths globally. However, in developed countries, approximately one-third of cases fall outside these groups such that cryptococcal meningoencephalitis (CM) has become the most common cause of non-viral meningitis in the U.S. Within the U.S., approximately 15-20% have no readily identifiable immune defect and cryptococcal infection in these hosts has a mortality rate of 30-50% despite optimal antifungal therapy. NIH Clinical Study Protocol 93-I-0106 (NCT00001352). The objectives of this protocol can be broadly categorized as: 1) Characterize the immunologic and genetic mechanisms predisposing to disease acquisition; 2) Understand the post-infectious inflammatory response and distinguish its consequences from those directly due to fungal growth; and 3) Management of post-infectious neuro-inflammatory syndromes associated with cryptococcal meningitis (CM). This protocol recruits patients who have microbiological evidence of cryptococcal neurologic or non-CNS disease (typically pulmonary or bone). Cerebrospinal fluid (CSF) and blood samples collected during clinical care are used to measure serum and CNS cellular and soluble cytokines as well as to perform in-situ immunohistochemistry. CSF and blood samples are also collected to measure transcriptional (gene expression), proteomic (protein), and lipidomic (lipids) changes that occur throughout disease and treatment. Observational data detailing audiological, ophthalmological and neurocognitive deficits in these patients is also recorded. We have recently described a post-infectious inflammatory syndrome (PIIRS) associated with cryptococcal meningoencephalitis (CM) which can be best described as a neuro-inflammatory state during which CM patients present with altered mental status (Montreal Cognitive Assessment Score As part of the protocol, we treat patients for either microbiological failure or neuroinflammatory sequelae by conventional therapies utilizing FDA-approved pharmaceuticals at FDA-approved doses. To understand and identify the predominant biological pathways responsible for PIIRS neuroinflammation, we examined patient CSF at baseline (at time of PIIRS diagnosis) and post-treatment with different FDA-approved pharmaceuticals at FDA-approved doses compared to CSF from non-PIIRS donors. Upstream pathway analysis of differentially expressed genes in the CSF of PIIRS patients revealed a prominent role for the JAK/STAT pathway in the pathogenesis of PIIRS and support the use of the JAK inhibitor, ruxolinib, as a pathway-instructed therapy to treat PIIRS patients. Data available through dbGaP: single cell RNA sequencing (scRNA-seq) data from CSF cells of a patient with PIIRS at the time of diagnosis and following treatment with steroids (1g solumedrol/day) and NanoString transcriptional data from CSF cells of patients with PIIRS at the time of diagnosis compared to CSF cells from non-PIIRS donors.

  Study phs003871

• RNAseq dataset

  RNAseq experiment after DIS3 ASO or Control ASO treatment on human cells under plasmablast differentiation.

  Dataset EGAD50000001243

• Title: Divergent levels of CD112 and INKA1 define a distinct subset of human long-term hematopoietic stem cells

  The data provided here was critical in establishing that human long-term hematopoietic stem cells (LT-HSC), previously described as the most primitive HSC population, is actually composed of distinct subsets that can be prospectively isolated. Via mechanistic studies centering around the Rho-GTPase effector kinase PAK4 and its inhibitor INKA1, we identified the immune checkpoint ligand CD112 as a marker for hematopoietic stem and progenitor cells, that is highest expressed on LT-HSC. More importantly, CD112 can be used to stratify functionally distinct subsets within LT-HSC: In response to regeneration-mediated stress, the CD112low subset exhibits a transient restraint (termed latency) before contributing to hematopoietic reconstitution, while the CD112high subset is primed to respond rapidly. High resolution RNA-seq of the CD112 surface expression spectrum within rare LT-HSC subsets (human umbilical cord blood) demonstrated that more genes are differentially upregulated in the deeper quiescent and less metabolic active subset. Genes enriched in this subset centre around cell adhesion and Rho-GTPase signaling. This is in agreement with the scRNAseq data from human G-CSF mobilized peripheral blood (mPB) generated here that was used as an model of in vivo activation/priming revealing via RNA-velocity and pseudo-time analysis that INKA1high versus PAK4high, CDK6high and CD112high enrichment are either detected early or late in diffusion pseudotime indicative of quiescent versus primed cell status, respectively. RNAseq following INKA1 overexpression in LT-HSC and ST-HSC revealed by GSEA an overall stemness preserving phenotype and particularly in LT-HSC, but not in short-term HSC (ST-HSC), suppression of transcriptional programs linked to activation. Collectively, our data decipher the molecular intricacies underlying HSC heterogeneity and self-renewal regulation and point to latency as an orchestrated physiological response that integrates quiescence control with HSC fate choices to preserve a stem cell reservoir.

  Dataset EGAD00001006541

• CIDR: Collaborative Study on the Genetics of Alcoholism Case Control Study

  This is a case-control study of alcoholism, in which the subjects have been drawn from the Collaborative Study on the Genetics of Alcoholism (COGA), a large, ongoing family-based study that includes subjects from seven sites around the US. COGA has gathered detailed, standardized data on study participants, including diagnostic and neurophysiological assessments. This sample has already proved successful in identifying several genes that influence the risk for alcoholism and neurophysiological endophenotypes, which have been independently replicated. COGA data were included as part of two Genetic Analysis Workshops, and the phenotypes are familiar to the genetics community. Alcoholic probands were recruited from treatment facilities, assessed by personal interview, and after securing permission, other family members were also assessed. A set of comparison families was drawn from the same communities as the families recruited through an alcoholic proband. Assessment involved a detailed personal interview developed for this project, the Semi-Structured Assessment for the Genetics of Alcoholism (SSAGA), which gathers detailed information on alcoholism related symptoms along with other drugs and psychiatric symptoms. Many participants also came to the laboratories for electroencephalographic studies. Neurophysiological features that have been shown to be useful endophenotypes for which we have linkage and in some cases association results are included on a subset of the case-control sample: the beta power of the resting electroencephalogram (EEG), the P3(00) amplitude of the visual event-related potential (ERP), and the theta and delta event-related oscillations (EROs) underlying the P3 (See Porjesz et al., 2005; Porjesz and Rangaswamy, 2007 for reviews). A brief description of COGA is in Edenberg, H. J. (2002) The Collaborative Study on the Genetics of Alcoholism: an update. Alcohol Res Health 26, 214-218., Bierut, LJ, NL Saccone, JP Rice, A Goate, T Foroud, HJ Edenberg, L Almasy, PM Conneally, R Crowe, V Hesselbrock, T-K Li, JI Nurnberger, Jr, B Porjesz, MA Schuckit, J Tischfield, H Begleiter, and T Reich (2002) Defining alcohol-related phenotypes in humans: The Collaborative Study on the Genetics of Alcoholism. Alcohol Res Health 26, 208-213. Edenberg HJ and Foroud T (2006) The genetics of alcoholism: identifying specific genes through family studies. Addiction Biology 11, 386-396. This case-control sample of biologically unrelated individuals was drawn from COGA subjects. All cases meet DSM-IV criteria for alcohol dependence. Controls are individuals who have consumed alcohol, but did not meet any definition of alcohol dependence or alcohol abuse, nor did they meet any DSM-IIIR or DSM-IV definition of abuse or dependence for other drugs (except nicotine). All cases and controls have undergone identical clinical assessments. Many individuals in this case-control sample have not previously been genotyped. The Collaborative Study on the Genetics of Alcoholism (COGA) has four Co-Principal Investigators: B. Porjesz, V. Hesselbrock, H. Edenberg, L. Bierut. COGA includes nine different centers where data collection, analysis, and storage take place. The nine sites and Principal Investigators and Co-Investigators are: University of Connecticut (V. Hesselbrock); Indiana University (H.J. Edenberg, J. Nurnberger Jr., T. Foroud); University of Iowa (S. Kuperman); SUNY Downstate (B. Porjesz); Washington University in St. Louis (L. Bierut, A. Goate, J. Rice); University of California at San Diego (M. Schuckit); Howard University (R. Taylor); Rutgers University (J. Tischfield); Southwest Foundation (L. Almasy). Q. Max Guo serves as the NIAAA Staff Collaborator. This national collaborative study is supported by the NIH Grant U10AA008401 from the National Institute on Alcohol Abuse and Alcoholism (NIAAA) and the National Institute on Drug Abuse (NIDA). Funding support for genotyping, which was performed at the Johns Hopkins University Center for Inherited Disease Research, was provided by the National Institute on Alcohol Abuse and Alcoholism, the NIH GEI (U01HG004438),and the NIH contract "High throughput genotyping for studying the genetic contributions to human disease" (HHSN268200782096C). COGA has over 250 publications listed at www.niaaagenetics.org

  Study phs000125

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

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

  Study phs001317

• Regulatory T cell transcriptomic reprogramming characterizes adverse events by checkpoint inhibitors in solid tumors

  Tregs were sorted as CD4+CD25+CD127- cells from peripheral blood of patients with advanced metastatic melanoma, stage III(B-D)-IV, who were receiving treatment with anti-PD1 (n =26); and patients with kidney, non-small cell lung, liver and bladder cancer who were receiving treatment with anti-PD1. RNA was extracted and polyA libraries were prepared using the Illumina Truseq sample preparation kit v.2. Single-end sequencing was performed on NextSeq500.

  Dataset EGAD00001006415

• Characterization_of_individual_foci_of_multicentric_multifocal_breast_cancer_using_targeted_next_generation_sequencing

  Multifocality or multicentricity in breast cancer may be defined as the presence of two or more tumor foci within a single quadrant of the breast or within different quadrants of the same breast, respectively. This original classification of the breast cancer as multicentric or multifocal was based on the assumption that cancers arising in the same quadrant were more likely to arise from the same ductal structures than those occurring in separate areas of the breast. The problem with these definitions is that the “quadrants” of the breast are arbitrary external designations, as no internal boundaries do exist. This project will therefore focus both on synchronous multifocal and multicentric tumors. The incidence of multifocal and multicentric breast cancers was reported to be between 13 and 75% depending on the definition used, the extent of the pathologic sampling of the breast and whether in situ disease is considered evidence of multicentricity (1). Although this incidence is variable, those figures show that it is a frequent phenomenon. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic management of the cancer. Multifocality or multicentricity has been associated with a number of more aggressive features including an increased rate of regional lymph node metastases and adverse patient outcome when compared with unifocal tumors (2-3), and a possible increased risk of local recurrence following breast conserving surgery (4). For the moment, the literature is divided on whether there is a corresponding impact on survival outcomes. Today, the current convention to stage and to treat multifocal and multicentric tumors is the classical tumor-node-metastasis (TNM) staging guidelines with which tumor size is assessed by the largest tumor focus without taking other foci of disease into consideration. If some papers, as the recent one from Lynch and colleagues, support the current staging convention (3), others, however, as Boyages et al. suggested that aggregate size and not the size of the largest lesion should be considered in order to refine the prognostic assessment of those tumors (5). On the top of that, the question whether multifocal/multicentric carcinomas are due to the spread of a single carcinoma throughout the breast or is due to multiple carcinomas arising simultaneously has been a matter of debate. Some studies suggested that multifocal breast cancer may result from either intramammary spread from a single primary tumor or multiple synchronous primary tumors; whereas others suggest that multiple breast carcinomas always arise from the same clone (6-8). Recently, Pietri and colleagues analyzed the biological characterization of a series of 113 multifocal/multicentric breast cancers (8) which were diagnosed over a 5-year period. The expression of estrogen (ER) and progesterone (PgR) receptors, Ki-67 proliferative index, expression of HER2 and tumor grading were prospectively determined in each tumor focus, and mismatches among foci were recorded. Mismatches in ER status were present in 5 (4.4%) cases and PgR in 18 (15.9%) cases. Mismatches in tumor grading were present in 21 cases (18.6%), proliferative index (Ki-67) in 17 (15%) cases and HER2 status in 11 (9.7%) cases. Interestingly, this heterogeneity among foci has led to 14 (12.4%) patients receiving different adjuvant treatments compared with what would have been indicated if we had only taken into account the biologic status of the primary tumor. This study therefore showed that differences in biological characteristics of multifocal/multicentric lesions play a crucial role in the adjuvant treatment decision making process. In this study, we will concentrate on a larger series of patients with multifocal invasive ductal breast cancer lesions. We aim at: 1. Evaluating the incidence of multifocality according to the different breast cancer molecular subtypes (ER-/HER2-, HER2+, ER+/HER2-). 2. Evaluating the incidence of multifocality in patients with hereditary breast cancer disease (presence of germline BRCA1 or BRCA2 mutations). Moreover, we would like to investigate if multifocal lesions with BRCA1 or BRCA2 mutations exhibit a characteristic combination of substitution mutation signatures and a distinctive profile of deletions as demonstrated recently by Nik-Zainal and colleagues (9). 3. Correlating multifocality with clinical information in order to define its influence on patients’ survival (DFS and OS). 4. Carrying high coverage targeted gene sequencing of driver cancer genes and genes whose mutation is of therapeutic importance in order to compare clinically-relevant genetic differences between several multifocal breast cancer lesions. 5. Evaluating the impact of the distance between the different lesions on the clinical outcome but also on the genetic differences. 6. Comparing gene expression patterns between several multifocal breast cancer lesions and correlate them with the results of the targeted genes screen. 7. Characterizing the genomic and transcriptomic status of cancer related genes in metastatic lesions (local recurrence, positive lymph node or distant metastatic sites) from the same multifocal invasive ductal breast cancer patients in order to evaluate the consequence of genomic and transcriptomic heterogeneity of multifocal lesions on metastatic lesions. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic choice. This project has the potential to identify genetic/transcriptomic differences existing between several lesions constituting multifocal breast cancers, which in the routine clinical practice are usually considered to be homogeneous among them. We foresee validating significant results in a larger series of patients and this, in turn, could have a remarkable impact on the treatment and clinical management of multifocal breast cancers. Indeed, we hope to provide some evidence whether or not each focus matters in multifocal and multicentric breast cancer to define the adequate therapeutic approach, especially in the context of targeted therapies. The work to be done at Sanger will be target gene screen pooling of 1400 samples.

  Study EGAS00001000407

• ACTIV-6: COVID-19 Outpatient Randomized Trial to Evaluate Efficacy of Repurposed Medications

  This study is a platform protocol designed to be flexible so that it is suitable for a wide range of settings within healthcare systems and in community settings where it can be integrated into routine COVID-19 testing programs and subsequent treatment plans. This platform protocol will enroll participants in an outpatient setting with a confirmed polymerase chain reaction (PCR) or antigen test for SARS-CoV-2. Each appendix will describe a repurposed medication (study drug) to meet the protocol objectives. When only one study drug/appendix is under study, allocation between study drug and placebo will be 1:1. If multiple study drugs/appendices are under study, participants will also be randomized among the study drugs for which eligibility is confirmed. Since the route of administration of each study drug may differ, the placebos may also differ. To achieve blinding and an equitable randomization probability, a two-step randomization process will be used.In the first step, the participant will be randomized m:1 active study drug to placebo, where m is the number of active study drugs for which the participant is eligible. Then, participants will be randomized among the m study drugs for which they are eligible. Participants will carry their ‘study drug' versus ‘placebo' randomization with them into the study drug appendix. In this way, a participant allocated to placebo who is randomized to study drug A will be given the placebo that matches study drug A. This achieves equal probability of exposure to a placebo or an active study drug, and equitable distribution among all study arms for which a participant is eligible. Sites will be informed to which study drug appendix the participant is randomized, but not whether they are allocated to the study drug arm or placebo arm within that appendix. For analysis, concurrent placebo participants who were eligible for the study drug appendix will be pooled. This will result in approximately a 1:1 allocation ratio for any study drug to placebo. If a study drug appendix is stopped for efficacy and becomes standard of care, the active study drug arm may serve as a concurrent placebo for other study drugs.Participants will receive complete supply of repurposed medication (study drug) or placebo with length of treatment and amount of study drug/placebo depending on the study drug appendix and arm to which they are randomized.This study is designed so that it can be done completely remotely. However, screening and enrollment may occur in person at sites and unplanned study visits may occur in person or remotely, as deemed appropriate by an investigator for safety purposes. Participants will be on-study for up to 180 days, during which they will complete various questionnaires.

  Study phs003941

• NAR-GAB 2025 deposit data

  Paired-end whole-exome sequencing data derived from Illumina hybrid-capture experiments (Agilent SureSelect Human All Exon kits). Six human probands with rare diseases; one sample per subject. Sequencing reads from each individual were processed into analysis-ready gVCF files following standard best-practice pipelines, including alignment, duplicate marking, base quality calibration, and variant calling. All gVCF files are encrypted using Crypt4GH and are available under controlled access through our DAC in accordance with a strict DUO-based policy.

  Dataset EGAD50000002100

• Federated discovery and sharing of genomic data using Beacons

  The Beacon Project is a Global Alliance for Genomics & Health (GA4GH) initiative that enables genomic and clinical data sharing across federated networks. The project is working toward developing regulatory, ethics and security guidance to ensure proportionate safeguards for distribution of data according to the GA4GH-developed “Framework for Responsible Sharing of Genomic and Health-Related Data”. Within this Nature Biotechnology Correspondence a description of the Beacon protocol and how it can be used as a model for the federated discovery and sharing of genomic data is offered to the community. A Beacon is defined as a web-accessible service that can be queried for information about a specific allele. A user of a Beacon can pose queries of the form “Have you observed this nucleotide (e.g., C) at this genomic location (e.g., position 32,936,732 on chromosome 13)?” to which the Beacon responds with either “yes” or “no.” In this way, a Beacon allows allelic information of interest to be discovered by a remote searcher with no reference to a specific sample or patient, thereby mitigating privacy risks. The Beacon API (represented as a RESTful web application) provides a technical specification that a Beacon server must implement. The specification is open source and available online here. To simplify the process of lighting a Beacon, a free, open-source reference implementation of the latest specification has been developed. GA4GH is promoting different levels of data access (open, registered, and controlled) for convenience and for compatibility across its projects. Each so-called access tier has distinct visibility and requirements for authorization. For example, ‘open access’ Beacons are accessible to anonymous users of the internet, whereas ‘registered access’ Beacons are accessible to registered users (for example, bona fide researchers and clinicians) who have agreed to a set of conditions of data use. Many of the largest genomic archives, such as dbGaP, the European Genome-phenome Archive and the European Variation Archive, have provided access to variation data through Beacons for some or all of their datasets. Beacons can be interconnected through the Beacon Network, a directory and search engine for Beacons. Although individual Beacons answer the question “Have you observed this allele?”, the Beacon Network answers the question “Who has observed this allele?”. Beacons can be freely registered to the Beacon Network and can be searched independently or in aggregate with other connected Beacons.

  Blog federated-discovery-using-beacons

• NHLBI TOPMed: The Genetic Epidemiology of Asthma in Costa Rica

  This administrative supplement to the project, "The Genetic Epidemiology of Asthma in Costa Rica" (R37 HL066289) is in response to NOT-HL-14-029 to perform whole genome sequencing (WGS) on existing NHLBI populations. We focus on asthma because of its public health significance. Asthma affects 26 million U.S. children and adults, remains a major cause of morbidity (one-half million hospitalizations a year) and is the most common cause of school and work days lost. Asthma-related costs are estimated to be over $12.7 billion annually. The Asthma Probands for both the extended pedigrees and the trios utilized in this study were selected on the basis of a physician diagnosis of asthma; a history of recurrent asthma attacks or at least 2 respiratory symptoms; and either airway hyperresponsiveness to methacholine or significant response to bronchodilator (Albuterol) administration. These criteria are identical to the criteria used in the Childhood Asthma Management Program (CAMP). The three primary goals of this project are to: (1) identify common and rare genetic variants that determine asthma and its associated phenotypes (height, weight, IgE level, lung function, bronchodilator response, steroid treatment response) through whole genome sequencing (WGS); (2) perform novel family based association analysis of our WGS data to identify novel genes for asthma; and (3) integrate epigenomic and transcriptomic data with our WGS data and determine the epistatic interactions present using systems genomics approaches. Identification of the molecular determinants of asthma remains an important priority in translational science. Genome-wide association studies (GWAS) have been successful in this regard, identifying at least 10 novel susceptibility genes for asthma. However, as with most complex traits, the variants identified by GWAS explain only a fraction of the estimated heritability of this disorder. Herein, we propose a novel family-based study design and state-of-the-art genome sequencing techniques to map a set of sequence variants for asthma and its associated phenotypes and assess the interrelationships of the identified genes and variants using systems genomics methods. We have assembled a team of investigators highly-skilled and expert in whole genome sequencing (Drs. Michael Cho and Benjamin Raby), genetic association analysis (Drs. Scott T. Weiss, Jessica Lasky-Su and Christoph Lange), integrative genomics (Drs. Raby, Kelan Tantisira, Augusto Litonjua and Dawn DeMeo), and systems genomics (Drs. Weiss, Amitabh Sharma, Lange and Raby) to address this important problem with both a novel study design and data set.

  Study phs000988

• A panel of reference haplotypes for imputing complement component 4 (C4) gene structural variation

  Neuropsychiatric and autoimmune disorders have substantial epidemiological correlations (Benros et al., JAMA Psychiatry 2013, PMID: 23760347) and broad, genome-wide patterns of shared genetic risk (Pouget et al., Hum Mol Genet, PMID: 31211845; Tylee et al., Am J Med Genet B Neuropsychiatr Genet 2018, PMID: 30325587). Some cases of psychosis involve autoantibodies against the NMDA receptor, AMPA receptor, or other synaptic proteins (reviewed in Dalmau et al, Lancet Neurol 2011, PMID: 21163445). The related autoimmune conditions lupus and Sjogren's Syndrome also involve the development of autoantibodies. The possibility that neuropsychiatric disorders can have molecular mechanisms in common with autoimmune disorders - for example, that psychosis involves an inflammatory or autoimmune component in some patients, or that immune molecules are re-used in the brain to underlie other important biological activities (Stevens et al., Cell 2007, PMID: 18083105) - could open novel therapeutic possibilities for neuropsychiatric disorders. At a genetic level, the strongest genetic associations of schizophrenia, lupus, and Sjogren's Syndrome to common genetic variation involve associations to genetic markers in the Major Histocompatibility Complex (MHC) locus. Bipolar disorder in some studies also associates with variation in or near the MHC locus, though less strongly than schizophrenia does. Intriguingly, the same specific SNPs appear to associate strongly with schizophrenia, lupus, and Sjogren's; these strongly associating SNPs span a genomic segment that includes the HLA class II genes (which have an important role in antibody production) and the complement component 4 (C4) genes. The specific genes and alleles responsible for these associations need to be completely defined, and the extent to which they represent shared or distinct genetic influences in neuropsychiatric and autoimmune illnesses needs to be clarified. The complement component 4 (C4A and C4B) genes are present in the MHC locus, between the class I and class II HLA genes. C4A and C4B commonly vary in genomic copy number and encode complement proteins with distinct affinities for molecular targets. The complex genetic variation at C4 - arising from many alleles with different numbers of C4A and C4B genes - has been challenging to analyze in large cohorts. We recently developed an approach to this problem based on imputation: people share long haplotypes with the same combinations of SNP and C4 alleles, such that C4A and C4B gene copy numbers can be imputed from SNP data (Sekar et al., Nature 2016, PMID: 26814963). In the current work, to analyze C4 in large cohorts, we developed a way to identify C4 alleles from whole-genome sequence (WGS) data, then analyzed WGS data from 1,234 individuals to create a large multi-ancestry panel of 2,530 reference haplotypes of MHC SNPs and C4 alleles that can then be imputed into still-larger cohorts for which SNP data are available. With this dbGaP submission, we make this reference panel available for other studies. Protocols and software for imputing C4 alleles into genome-wide SNP data, and for performing molecular analyses on the C4 genes (such as direct measurement of copy number from genomic DNA), can be found on the McCarroll Lab web site (http://mccarrolllab.org/resources). We are also working to create additional reference panels for imputation of C4 alleles that will be based on still-larger and more diverse population samples; links to these will also be available on the McCarroll Lab web site as we create and validate them.

  Study phs001992

• Sequencing data for oesophageal and related samples - OACs release 2 (RNA)

  Dataset EGAD00001003839

• Prostate cancer datasets WES

  WES: 48 samples (5 blood samples from 6 patient data): 22 Tumour cores and 26 normal/benign cores (HiSeq)

  Dataset EGAD00001004467

• Exome reads and RNA-seq

  Exome sequencing for 26 patients with matched blood RNA-seq for 41 patients

  Dataset EGAD00001002722

• RNAseq

  RNAseq was performed on CDX, CDX-derived cell line and LNCaP cell line, with triplicates.

  Dataset EGAD00001006008

• alopecia areata

  exome sequencing files from 25 alopecia areata samples from spain.

  Dataset EGAD00001006370

• Sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC)

  In 2016 we established the Sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC) funded by the Ice Bucket Challenge Grant administered by the Motor Neurone Disease Research Institute of Australia. The goals of the SALSA-SGC are to collect biological samples from clinics across Australia with matched in depth clinical and self-report phenotypes and to generate multiple levels of genetic and genomic data. In this first data generation exercise of the SALSA-SGC the majority of the samples were collected prior to the formal establishment of SALSA-SGC from clinics across Australia.Briefly, the cohort includes the University of Sydney’s Australian Motor Neuron Disease DNA Bank (MND Bank) cohort recruited April 2000 to June 2011), with study protocol approved by the Sydney South West Area Health Service Human Research Ethics Committee (HREC). Cases were recruited from around Australia via state-based MND associations with diagnosis verified by a neurologist. The remainder of the cases were recruited from clinics across Australia between 2015 and 2017 under HREC approvals from Royal Brisbane and Women’s Hospital, Macquarie University Multidisciplinary Motor Neurone Disease Clinic,  Calvary Health Care Bethlehem in Melbourne , Fiona Stanley Hospital in Perth, and from 2016 under HREC approvals at each site for the sporadic ALS Australia Systems Genomics Consortium (SALSA-SGC). The ALS cases were diagnosed with definite or probable ALS according to the revised El Escorial criteria. Some controls were recruited as either partners or friends of patients, healthy individuals free of neuromuscular diseases. We are providing GWAS and MWAS data in this dataset. Individual level GWAS data were generated using Illumina Infinium CoreExome-24 version 1.1 chips for N= 846 cases and N=665 controls. Individual MWAS data was generated using the Illumina Human methylation 450K array for N=782 cases and N=613 controls. There 1315 individuals where GWAS and MWAS data has been generated and is available. Further information on these data sets can be found: Paper 1: Restuadi, R, Garton, FC, Benyamin, B, Lin, T, et al. Amyotrophic Lateral Sclerosis Genetic Correlation with Cognitive Performance, educational attainment and schizophrenia: evidence from polygenic risk score analysis. (submitted) Paper 2: Nabais, MF, Lin, T, Benyamin, B et al. Significant out-of-sample classification from methylation profile scoring for amyotrophic lateral sclerosis. 2020. NPJ genomic medicine. 5(10). Files provided in this submission include: GWAS: This folder contains QCed genotype for the Australian ALS case-control cohort. Contains PLINK files for genotyping data (not imputed yet). The individuals selected here have: good consistency on phenotype data ethics approval registered as part of sporadic ALS studies unrelated by GRM cut-off 0.05 No ancestry QC yet MWAS: This folder contains the IDAT and post-QC normalized DNAm (beta) for the Australian ALS case-control cohort. 2019_AUS_ALS_PCTG_DNAm.tar.gz - IDATS for 1315 individuals analyzed in the MWAS study normalized_beta_values - Binary files (created with the OSCA software) containing information on the individuals, probes and the DNAm (beta) values obtained after QC phenotype_file - contains all the covariates analysed in the MWAS including: case-control status, coded 0 = Control and 1 = ALS, predicted age, predicted cell-type proportions, predicted smoking scores, slide and chip position and sex Important Notes: The DNAm data were normalized together with samples that were not part of this ALS case/control study and thus, the normalization procedure may not be 100% reproducible using only the IDAT files uploaded here. Summary data has been made publicly available and can be accessed directly: Data collection and sample processing were performed at several clinics across Australia. Genotyping and DNA methylation arrays were performed by the Human Studies Unit, at the Institute for Molecular Bioscience (University of Queensland). Quality control of the genotypic, phenotypic and DNA methylation data was done by the Program of Complex Traits Genomics, at the Institute for Molecular Bioscience (University of Queensland).

  Study phs002068

• Characterization of individual foci of multicentric/multifocal breast cancer using targeted next generation sequencing

  Multifocality or multicentricity in breast cancer may be defined as the presence of two or more tumor foci within a single quadrant of the breast or within different quadrants of the same breast, respectively. This original classification of the breast cancer as multicentric or multifocal was based on the assumption that cancers arising in the same quadrant were more likely to arise from the same ductal structures than those occurring in separate areas of the breast. The problem with these definitions is that the ?quadrants? of the breast are arbitrary external designations, as no internal boundaries do exist. This project will therefore focus both on synchronous multifocal and multicentric tumors. The incidence of multifocal and multicentric breast cancers was reported to be between 13 and 75% depending on the definition used, the extent of the pathologic sampling of the breast and whether in situ disease is considered evidence of multicentricity (1). Although this incidence is variable, those figures show that it is a frequent phenomenon. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic management of the cancer. Multifocality or multicentricity has been associated with a number of more aggressive features including an increased rate of regional lymph node metastases and adverse patient outcome when compared with unifocal tumors (2-3), and a possible increased risk of local recurrence following breast conserving surgery (4). For the moment, the literature is divided on whether there is a corresponding impact on survival outcomes. Today, the current convention to stage and to treat multifocal and multicentric tumors is the classical tumor-node-metastasis (TNM) staging guidelines with which tumor size is assessed by the largest tumor focus without taking other foci of disease into consideration. If some papers, as the recent one from Lynch and colleagues, support the current staging convention (3), others, however, as Boyages et al. suggested that aggregate size and not the size of the largest lesion should be considered in order to refine the prognostic assessment of those tumors (5). On the top of that, the question whether multifocal/multicentric carcinomas are due to the spread of a single carcinoma throughout the breast or is due to multiple carcinomas arising simultaneously has been a matter of debate. Some studies suggested that multifocal breast cancer may result from either intramammary spread from a single primary tumor or multiple synchronous primary tumors; whereas others suggest that multiple breast carcinomas always arise from the same clone (6-8). Recently, Pietri and colleagues analyzed the biological characterization of a series of 113 multifocal/multicentric breast cancers (8) which were diagnosed over a 5-year period. The expression of estrogen (ER) and progesterone (PgR) receptors, Ki-67 proliferative index, expression of HER2 and tumor grading were prospectively determined in each tumor focus, and mismatches among foci were recorded. Mismatches in ER status were present in 5 (4.4%) cases and PgR in 18 (15.9%) cases. Mismatches in tumor grading were present in 21 cases (18.6%), proliferative index (Ki-67) in 17 (15%) cases and HER2 status in 11 (9.7%) cases. Interestingly, this heterogeneity among foci has led to 14 (12.4%) patients receiving different adjuvant treatments compared with what would have been indicated if we had only taken into account the biologic status of the primary tumor. This study therefore showed that differences in biological characteristics of multifocal/multicentric lesions play a crucial role in the adjuvant treatment decision making process. In this study, we will concentrate on a larger series of patients with multifocal invasive ductal breast cancer lesions. We aim at: 1. Evaluating the incidence of multifocality according to the different breast cancer molecular subtypes (ER-/HER2-, HER2+, ER+/HER2-). 2. Evaluating the incidence of multifocality in patients with hereditary breast cancer disease (presence of germline BRCA1 or BRCA2 mutations). Moreover, we would like to investigate if multifocal lesions with BRCA1 or BRCA2 mutations exhibit a characteristic combination of substitution mutation signatures and a distinctive profile of deletions as demonstrated recently by Nik-Zainal and colleagues (9). 3. Correlating multifocality with clinical information in order to define its influence on patients? survival (DFS and OS). 4. Carrying high coverage targeted gene sequencing of driver cancer genes and genes whose mutation is of therapeutic importance in order to compare clinically-relevant genetic differences between several multifocal breast cancer lesions. 5. Evaluating the impact of the distance between the different lesions on the clinical outcome but also on the genetic differences. 6. Comparing gene expression patterns between several multifocal breast cancer lesions and correlate them with the results of the targeted genes screen. 7. Characterizing the genomic and transcriptomic status of cancer related genes in metastatic lesions (local recurrence, positive lymph node or distant metastatic sites) from the same multifocal invasive ductal breast cancer patients in order to evaluate the consequence of genomic and transcriptomic heterogeneity of multifocal lesions on metastatic lesions. Multiple (multifocal/multicentric) breast carcinomas, especially when occurring in the same breast, represent a real challenge for both pathologists and clinicians in terms of identifying the cellular origin and the best therapeutic choice. This project has the potential to identify genetic/transcriptomic differences existing between several lesions constituting multifocal breast cancers, which in the routine clinical practice are usually considered to be homogeneous among them. We foresee validating significant results in a larger series of patients and this, in turn, could have a remarkable impact on the treatment and clinical management of multifocal breast cancers. Indeed, we hope to provide some evidence whether or not each focus matters in multifocal and multicentric breast cancer to define the adequate therapeutic approach, especially in the context of targeted therapies. The work to be done at Sanger will be target gene screen pooling of 1400 samples.

  Dataset EGAD00001000624

• 10x Genomics raw data of intestinal plasma cells

  The dataset contains raw fastq files (fastq.gz) for Chromium Single Cell 5’ gene expression (GEX), human B cell VDJ and feature barcode (CSP) sequencing from transglutaminase 2-specific and other small intestinal plasma cells isolated from four untreated celiac disease patients. Single cell 5’ gene expression, V(D)J-enriched and cell surface protein libraries were generated using Chromium single cell kits, and barcoded cDNA from a total of 5,000-10,000 cells per sample was generated using the 10x Genomics Chromium Controller. The libraries were pooled prior to sequencing on a NovaSeq 6000 instrument (Illumina) using the following configuration: read 1: 26 cycles, read 2: 89 cycles, index read 1: 8 cycles.

  Dataset EGAD50000000342

• OpACIN-neo – A Multicenter Phase 2 Study to identify the Optimal neo-Adjuvant Combination scheme of Ipilimumab and Nivolumab – Whole exome sequencing

  The outcome of patients with macroscopic stage III melanoma is poor. Neoadjuvant treatment with ipilimumab plus nivolumab at the standard dosing schedule induced pathological responses in a high proportion of patients in two small independent early-phase trials. However, toxicity of the standard ipilimumab plus nivolumab dosing schedule was high, preventing its broader clinical use. The aim of the OpACIN-neo study (NCT02977052) to identify a dosing schedule of ipilimumab plus nivolumab that is less toxic but equally effective. 86 patients with macroscopic stage III melanoma were randomised to one of three dosing schedules: arm A, two cycles of ipilimumab 3 mg/kg plus nivolumab 1 mg/kg once every 3 weeks; arm B, two cycles of ipilimumab 1 mg/kg plus nivolumab 3 mg/kg once every 3 weeks; or arm C, two cycles of ipilimumab 3 mg/kg once every 3 weeks directly followed by two cycles of nivolumab 3mg/kg once every 2 weeks. Within the first 12 weeks, grade 3–4 immune-related adverse events were observed in 12 (40%) of 30 patients in group A, six (20%) of 30 in group B, and 13 (50%) of 26 in group C. Pathological responses occurred in 24 (80%) patients in group A, 23 (77%) in group B, and 17 (65%) in group C. The 2-year estimated relapse-free survival was 84% for all patients, 97% for patients achieving a pathologic response and 36% for nonresponders (p<0.001). High tumor mutational burden (TMB) and high interferon-gamma-related gene expression signature score (IFN-γ score) were associated with pathologic response and low risk of relapse; pathologic response rate (pRR) was 100% in patients with high IFN-γ score/high TMB, patients with high IFN-γ score/low TMB or low IFN-γ score/high TMB had pRRs of 91% and 88%; while patients with low IFN-γ score/low TMB had a pRR of only 39%. These data demonstrate long-term benefit in patients with a pathologic response and show the predictive potential of TMB and IFN-γ score.

  Study EGAS00001004832

• OpACIN-neo – A Multicenter Phase 2 Study to identify the Optimal neo-Adjuvant Combination scheme of Ipilimumab and Nivolumab – RNA sequencing

  The outcome of patients with macroscopic stage III melanoma is poor. Neoadjuvant treatment with ipilimumab plus nivolumab at the standard dosing schedule induced pathological responses in a high proportion of patients in two small independent early-phase trials. However, toxicity of the standard ipilimumab plus nivolumab dosing schedule was high, preventing its broader clinical use. The aim of the OpACIN-neo study (NCT02977052) to identify a dosing schedule of ipilimumab plus nivolumab that is less toxic but equally effective. 86 patients with macroscopic stage III melanoma were randomised to one of three dosing schedules: arm A, two cycles of ipilimumab 3 mg/kg plus nivolumab 1 mg/kg once every 3 weeks; arm B, two cycles of ipilimumab 1 mg/kg plus nivolumab 3 mg/kg once every 3 weeks; or arm C, two cycles of ipilimumab 3 mg/kg once every 3 weeks directly followed by two cycles of nivolumab 3mg/kg once every 2 weeks. Within the first 12 weeks, grade 3–4 immune-related adverse events were observed in 12 (40%) of 30 patients in group A, six (20%) of 30 in group B, and 13 (50%) of 26 in group C. Pathological responses occurred in 24 (80%) patients in group A, 23 (77%) in group B, and 17 (65%) in group C. The 2-year estimated relapse-free survival was 84% for all patients, 97% for patients achieving a pathologic response and 36% for nonresponders (p<0.001). High tumor mutational burden (TMB) and high interferon-gamma-related gene expression signature score (IFN-γ score) were associated with pathologic response and low risk of relapse; pathologic response rate (pRR) was 100% in patients with high IFN-γ score/high TMB, patients with high IFN-γ score/low TMB or low IFN-γ score/high TMB had pRRs of 91% and 88%; while patients with low IFN-γ score/low TMB had a pRR of only 39%. These data demonstrate long-term benefit in patients with a pathologic response and show the predictive potential of TMB and IFN-γ score.

  Study EGAS00001004833

• Prostate cancer datasets WGS

  Low pass WGS: 48 samples (5 blood samples from 6 patient data): 22 Tumour cores and 26 normal/benign cores (Next Seq )

  Dataset EGAD00001004466

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

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

  Study phs003809

• What is metadata?

  What is metadata? Data represents units of information and metadata can be seen, simply put, as data about other data. For example, in a simple experiment in which a patient genome was sequenced, there are multiple and diverse fields of metadata: from the biological sex of the patient to the sequencing platform used. Another way to understand metadata, following our genomic experiment example, is going through the different layers of (meta)data: One of the basic units of information (data) would be the sequence of nucleotides (e.g. GCTGG and GCCGG). This DNA sequence can be contextualised within a chromosome by providing its locus (e.g. β-globin gene). This data, the locus, is about other data, the sequence of nucleotides, which would render it metadata. We can go one step further, and provide more context, by giving the associated phenotype of each of these sequences: GCTGG corresponds to a healthy individual, while GCCGG corresponds to a person with β-thalassaemia. Once again, this data is contextualising the data we have provided up to this point, which makes it metadata. With this simple example, what we are doing is adding layers of data that describe the ones below. Had we given the sequences alone, little would be possible from the researchers' point of view. But, now that the data has its accompanying metadata, a researcher could compare both sequences and their phenotypes to infer a possible cause of the disorder. Each layer of information broadens the possible applications of the data. Now that we know what metadata is, it is time to emphasise the importance of submitting good quality metadata. The quality of the metadata will determine whether the data is usable, discoverable, and interpretable by researchers and clinicians. One example that highlights the importance of good quality metadata is the description of biological sex of a patient: while the terms "female," "girl," or "woman" all represent the same concept, they are not harmonised. These different representations of a concept can create confusion and errors in data analysis. By applying standard definitions and terminologies to biological sex metadata, we can avoid misunderstandings and facilitate the integration of different datasets.  In order to comply with the FAIR principles and, more specifically, to allow for the (meta)data to be interoperable (i.e. used universally and unambiguously), we need to place some standards onto the (meta)data EGA  archives. These can be as simple as asserting that the given patient's biological sex is one of the correct terms (e.g. female or male); or as complex as multiple layers and combinations of validation steps with existing records. You can find further details on how EGA manages these standards on our metadata model page.

  Documentation submission/metadata/what-is-metadata

• BLUEPRINT: RNA-seq of progenitor cells

  Data supporting the paper Transcriptional diversity during lineage commitment of human blood progenitors

  Dataset EGAD00001000745

• NHLBI TOPMed: Best ADd-on Therapy Giving Effective Response (BADGER)

  BADGER is a 56-week randomized, double-blind, three-treatment, three-period cross-over trial that will evaluate the differential improvement in control that is achieved following three separate treatment interventions in children whose asthma is not acceptably controlled on a low dose of ICS (per NAEPP guidelines). All participants will enter an 8-week run-in period during which time they will receive a dose of 1x ICS (fluticasone 200 μg/day). During this 8-week time period, running 2-week averages to establish the lack of acceptable asthma control will be calculated. Thus, a child could qualify for randomization at any time during this 8-week run-in period. This approach should maximize both patient safety and successful enrollment. Children will continue to receive 1x ICS during the entire treatment phase. During each period of the treatment phase, they also will receive one add-on therapy in the form of LABA, LTRA or additional 1x ICS. The order of the add-on therapy assignment will be determined by randomization into one of six treatment sequences (order determined randomly). Each treatment period will be 16 weeks in length; the initial 4 weeks of each period will be considered to be the washout period for the previous treatment. The primary outcome measures will be frequency of asthma exacerbations, asthma control days, and FEV1.

  Study phs001728

• RNA-seq of atypical 3q26 samples

  RNA was isolated using phenol-chloroform extraction followed by DNase digestion or using the Qiagen Allprep DNA/RNA kit and protocol (Qiagen, #80204). cDNA synthesis was done using the SuperScript II Reverse Transcriptase kit (Invitrogen). Quantitative real-time PCR was performed by using primers as described previously13,21 on the 7500 Fast Real-time PCR System (Applied Biosystems). Relative levels of gene expression were calculated using the ΔΔCt method

  Dataset EGAD00001006106

• 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

• PYDP Papuan Y chromosome Diversity Panel

  The PYDP dataset includes 26 bam files of Y chromosome sequences for Papua New Guinean individuals from different locations, extracted from whole genome sequences. DNA was extrated from saliva samples (Oragen kit). Sequencing libraries were prepared using the TruSeq DNA PCR-Free HT kit. 150 bp paired-end sequencing was performed on the Illumina HiSeq X5 sequencer.

  Dataset EGAD00001008572

• Genome-Wide Association Studies of Prematurity and Its Complications

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

  Study phs000103

• H3Africa H3AChipDesign Phenotype

  Basic phenotypic data (country, ethnicity and sex) for 348 samples of the H3Africa Chip Design Study. Divided into 8 datasets of 41 samples from Zambia, 24 samples from Cameroon, 50 samples from Mali, 26 samples from Cameroon, 49 samples from Nigeria, 48 samples from Botswana, 50 samples from Benin, 60 samples from Burkina Faso and Ghana.

  Dataset EGAD00001005310

• Genomic consequences of aberrant DNA repair mechanisms stratify ovarian cancer histotypes

  Aberrant DNA repair processes are a hallmark of human tumours. How these deficiencies variously impact the genomes of ovarian cancer between and within histotypes remains unknown. We studied the whole genome pointmutation and structural variation patterns of 133 tumours (59 high grade serous (HGSC), 35 clear cell (CCOC), 29 endometrioid (ENOC), and 10 adult granulosa cell tumours (GCT)) as a substrate for class discovery in ovarian cancer. Ab-initio clustering of integrated point mutation and structural variation signatures revealed seven novel subgroups, comprising between and within histotype stratification. Prevalence of fold-back inversions (FBI) co-localised with high level amplification events divided HGSC into two prognostically significant subgroups. This finding was recapitulated in two additional independent cohorts (total n=576 cases), and transcended gene based mutation status and gene expression as prognostically relevant features of HGSC. CCOC were divided into one group harbouring a signature reflective of active genome editing via APOBEC enzymes (26%) and a complementary group with an age-relatedmutational signature. ENOC were divided intomicrosatellite instable (MSI) cases (28%) with a distinctmismatch repairmutation signature and an outlying mutation rate, with the remainder of cases distributed amongst the remaining six groups. We suggest the FBI, MSI, and APOBEC groups represent biologic strata that could direct treatment strategies. Taken together, our work establishes the efficacy of the somatic genome as a biomarker to stratify ovarian cancers, simultaneously identifying patients that may benefit from emerging therapeutics and distinct subgroups within classic ovarian cancer histotypes.

  Study EGAS00001002390

• 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

• NHLBI Family Heart Study (FamHS-Visit1 and FamHS-Visit2)

  The Family Heart Study (FamHS) was funded by the National Heart, Lung, and Blood Institute (NHLBI). It was begun in 1992 with the ascertainment of 1,200 families, half randomly sampled, and half selected because of an excess of coronary heart disease (CHD) or risk factor abnormalities as compared with age- and sex-specific population rates (Higgins et al. 1996). The families, with approximately 6,000 individuals, were sampled on the basis of information on probands from four population-based parent studies: the Framingham Heart Study, the Utah Family Tree Study, and two Atherosclerosis Risk in Communities (ARIC) centers (Minneapolis, and Forsyth County, NC). A broad range of phenotypes were assessed at a clinic examination in broad domains of CHD, atherosclerosis, cardiac and vascular function, inflammation and hemostasis, lipids and lipoproteins, blood pressure, diabetes and insulin resistance, pulmonary function, and anthropometry (FamHS Visit 1). Approximately 8 years later, study participants belonging to the largest pedigrees were invited for a second clinical exam (FamHS Visit 2). A total of 2,756 Caucasian subjects in 508 extended families were examined. A two-phase design was adopted for the genome wide association (GWA) study. In phase-1, 1007 subjects were chosen, equally distributed between the upper and lower quartile of age- and sex-adjusted values for coronary artery calcification, assessed by CT scan in Visit 2. These subjects were chosen to be largely unrelated; 34% of the subjects were from unique families, while 200 other subjects had 1 or more siblings selected into the sample, yielding a sample of 465 unrelated subjects. The remaining family members (N=1749) were genotyped in the phase-2 for replication of the top hits from the phase-1. The results presented here represent those for the analysis of the phase-1 case-control sample for variables assessed in FamHS Visit 1 (from 1992 to 1995) and for the variables assessed in FamHS Visit 2 (from 2002 to 2003). All subjects were typed on the Illumina HumMap 550 chip (Phase 1 genotype). Of these, 33 (3.3%) were excluded due to technical errors, call rates below 98%, and discrepancies between reported sex and sex-diagnostic markers. The final sample of 974 subjects have Visit 2 phenotypes, approximately 100 of these do not have Visit 1 phenotypes. There was no significant plate-to-plate variation in allele frequencies. The covariate adjustments were performed separately by sex using cubic polynomial age and clinical centers, and retaining the terms in the stepwise regression analysis that were significant at the 5% level. Extreme outliers (>4 SD from the mean) were set aside, temporarily, for the adjustments. The final phenotypes were computed for all individuals using the best mean regression models and standardizing to 0 mean and unit variance. The FamHS has contributed GWA results in many phenotype domains (antropometric and adiposity, atherosclerosis and coronary heart disease, lipid profile, diabetes and glicemic traits, metabolic syndrome etc) to meta-analyses and various consortia, including Heard-Costa et al. 2009, Köttgen et al. 2010, Teslovich et al. 2010, Nettleton et al. 2010, Lango et al. 2010, Heid et al. 2010, Speliotes et al. 2010, Dupuis et al. 2010, Kraja et al. 2011.

  Study phs000221

• Sickle Cell Disease Implementation Consortium Registry (SCDIC Registry-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 understand the barriers to care and other factors related to reduced healthcare utilization after the transition from pediatric to adult SCD care which may contribute to increased morbidity and mortality.Background: Fifty years ago, it was rare for individuals with SCD to live beyond childhood. Advances in care delivery and treatment have more than doubled the life expectancy of individuals with sickle cell disease (SCD) since 1972. Beginning in the 1970s, measures such as newborn screening, prophylactic administration of penicillin, and immunization against bacterial infections decreased complications and morbidity, increasing the length and quality of life of children with SCD. Blood transfusions are currently the only proven way to prevent some of the major complications of SCD, especially recurrent stroke. They are also used frequently to help manage some of the acute complications of SCD. More recently, the use of hydroxyurea (HU) as a therapeutic agent to increase fetal hemoglobin has been shown to further reduce the debilitating symptoms of and improve survival in SCD. L-glutamine and crizanlizumab are additional treatments to reduce pain crises and voxelotor is approved to lower the risk of anemia and improve blood flow. In the absence of a widely accessible cure, treatment for SCD is usually aimed at avoiding crises, relieving symptoms, and preventing complications. Many of the advances in treatment have not translated into an increase in longevity or quality of life for adolescents and adults because of disparities in access to routine primary health care.Individuals with SCD experience a markedly increased mortality beginning in the second decade of life. The third and later decades of life are frequently associated with severe chronic pain progressive organ damage and frequent hospitalizations. The provision of evidence-based and expert opinion-based care in SCD is complicated by the difficulties that many patients experience in obtaining access to the health care system and in receiving long-term care from knowledgeable providers. A registry of 2,400 people with SCD was established to provide a rich resource to study the natural history of SCD and to understand barriers to care during the transition from pediatric to adult care. Participants: 2,438 participants with a confirmed diagnosis of SCD were enrolled into the registry over an 18-month period. At the time of enrollment, all participants were 15-45 years of age, English speaking, and without a bone marrow transplant.Design: The SCDIC Registry is a longitudinal observational cohort study. At enrollment, data collection included a medical record abstraction of clinical history, the most recent lab results, and a participant survey which included several patient reported outcomes from PROMIS, ASCQ-Me and NeuroQoL. Similar surveys were administered at annual follow-up. Four to five years after enrollment, a second record abstraction was completed with all clinical events that occurred since enrollment and another set of recent labs. There were many research questions proposed to be answered with the study data thus there was no primary outcome.Conclusions: As noted previously, there were no primary outcomes determined at the start of the study. Research questions included examination of co-morbidities, healthcare utilization, and patient reported outcomes. Key findings from the Registry include:Executive dysfunction, learning difficulties, and poor comprehension significantly associated with poor activities of daily living skills. Executive dysfunction also associated with HU non-adherence. Continuing HU after conception increased odds of miscarriage or stillbirth compared to women who were not using HU. Continuing HU after conception increased odds of low birth weight in infants. Compared to adolescents, young adults had significantly more severe pain, organ dysfunction, mental health disorders, sleep problems, and barriers to medical care. Young adults were significantly less likely to see a sickle cell specialist in the past 2 years. Females had higher pain frequency and severity, more pain episodes, anxiety, depression, hospitalizations, and higher fetal hemoglobin levels. Males had more respiratory, musculoskeletal, genitourinary, and cardiovascular complications, more skin ulcers, and more use of HU. Among 128 subjects that died during the study period, iron overload, pulmonary hypertension, and depression, were significant predictors of the risk of death in multivariate analyses.

  Study phs004203

• Single-Cell Mitochondrial Mutation Lineage Tracing of Non-Dysplastic and Dysplastic Barrett's Esophagus

  This study addresses a critical knowledge gap in understanding Barrett's esophagus (BE), a common metaplastic condition and precursor to esophageal adenocarcinoma, by identifying lineage connections and cell states underlying its development and malignant transformation. We collected biopsies from 13 Barrett's esophagus patients undergoing routine surveillance endoscopy, sampling metaplastic tissue alongside normal squamous esophagus and gastric cardia tissues when clinically appropriate. Our novel approach integrated single-cell RNA sequencing of nearly 180,000 cells with mitochondrial DNA mutation analysis for lineage tracing, coupled with spatial transcriptomics and comprehensive whole-exome sequencing. For one patient with high-grade dysplasia, we performed detailed whole-exome sequencing analysis at 100x coverage on dissociated Barrett's esophagus cells alongside matched normal esophagus and gastric cardia tissues. This genomic profiling revealed critical genetic drivers of malignant transformation, including a truncating mutation in the mutation cluster region of APC (a negative WNT regulator), mutations in the tumor suppressor genes CDKN2A and TP53, and significant copy number alterations including loss of CDKN2A on chromosome 9. These genetic alterations corresponded with the transcriptional changes observed in our single-cell data, particularly WNT pathway dysregulation and the expansion of LGR5-expressing stem cells, providing molecular evidence for how single clones can initiate the dysplastic transformation. Data deposited in dbGaP consist specifically of the whole-exome sequencing raw files, processed variant calls, and copy number analyses from the single patient with high-grade dysplasia and matched normal esophagus and stomach control tissue. Whole exome sequencing was performed on an Illumina NovaSeq 6000. Sequencing data was preprocessed following the Genome Analysis Toolkit's (GATK) Best Practices. Sequencing data was analyzed with Mutect2 (GATK, v4.2.5.0) to identify short somatic mutations including single-nucleotide polymorphisms and insertions and deletions. The Barrett's esophagus sample was run with the two matched normals, as well as the publicly available germline resource somatic-hg38_af-only-gnomad.hg38.vcf.gz (GATK). Somatic variant calls were filtered using FilterMutectCalls (GATK) and loaded into the Integrative Genomics Viewer (v2.12.3) for identification of high-quality variants in known esophageal adenocarcinoma regulators. Copy number alterations in the Barrett's esophagus sample were estimated using CNVkit (v0.9.9). CNV, Mutect2, and SVC analyses will be made available through dbGAP. Copy number alterations in the Barrett's esophagus sample were estimated using CNVkit (v0.9.9) with the default run settings; a pooled reference was generated from the normal esophagus and stomach samples. Copy number results were plotted directly within CNVkit using the function scatter.

  Study phs003949

• Cerebrospinal fluid cfDNA sequencing for classification of central nervous system glioma

  Primary central nervous system (CNS) gliomas can be classified by characteristic genetic alterations. In addition to solid tissue obtained by surgery or biopsy, cell-free DNA (cfDNA) derived from cerebrospinal fluid (CSF) is an alternative source of material for genomic analyses. Experimental design: We performed targeted next-generation sequencing (NGS) of CSF cfDNA in a representative cohort of 85 patients presenting with with suspicion of primary or recurrent glioma at two neurooncological centers. Copy-number variation (CNV) profiles, single nucleotide variants (SNVs), and small insertions/ deletions (indels) were combined into a molecular-guided tumor classification. Comparison with the solid tumor was performed for 38 cases with matching solid tissue available. Results: Cases were stratified into four groups: glioblastoma (n = 32), other glioma (n = 19), non-malignant (n = 17) and no confirmed diagnosis available (n = 17). We introduce a molecular-guided tumor classification, enabling identification of tumor entities and/ or cancer specific alterations in 75.0 % (n = 24) of glioblastoma and 52.6 % (n = 10) of other glioma cases. The overlap between CSF and matching solid tissue was highest for CNVs (26-48 %) and SNVs at pre-defined gene loci (44 %), followed by SNVs/indels identified via uninformed variant calling (8-14 %). A molecular-guided tumor classification was made 23.5 % (n = 4) of cases with no confirmed diagnosis available. Conclusions: We developed a workflow for targeted sequencing of CSF cfDNA as well as a strategy for interpretation and reporting of sequencing results based on a molecular-guided tumor classification in glioma.

  Study EGAS50000000060

• A Genome-Wide Association Study in Patients Experiencing Breast Events While Receiving Adjuvant Aromatase Inhibitors for Early Breast Cancer on NCIC CTG Trial MA.27

  Source of patients:The source of the patients for this genome-wide case-control study was MA.27, which was conducted as a multi-cooperative group effort under the auspices of the NCI Breast Cancer Intergroup of North America. The NCIC Clinical Trials Group (CTG) serves as the coordinating group, with participation by the NCI-sponsored North Central Cancer Treatment Group, Eastern Cooperative Oncology Group (ECOG), Southwest Oncology Group, and Cancer and Leukemia Group B (CALGB). MA.27 involved postmenopausal women with histologically confirmed and completely resected invasive breast cancer with surgical margins clear of invasive carcinoma in the following TMN categories (AJCC Version 6): pT1, pT2, pT3; pNx, pN0, pN1, pN2, pN3 (only when the sole basis is presence of 10 or more involved axillary nodes); MO. The primary tumor must have been estrogen receptor (ER) and/or progesterone receptor positive. Patients were stratified by lymph node status at diagnosis, prior adjuvant chemotherapy, and trastuzumab use and were randomized to 5 years of adjuvant therapy with anastrozole or exemestane. The trial was activated on May 26, 2003, and reached its accrual objectives on July 31, 2008, after the randomization of 6827 North American patients, with the majority (79%) providing DNA and consent for genetic testing. Non-North American patients were also entered by the International Breast Cancer Study Group but they did not contribute DNA. From 2003 to December 21, 2004, patients also underwent a second randomization to celecoxib 400 mg twice daily or placebo but, after the entry of 1,622 patients, this treatment was discontinued because of reports of increased cardiovascular risk associated with celecoxib. The final results of this study have been published, see Goss et al., 2013 (23358971). The patients in this analysis came from three cohorts: Cohort 1 consisted of 870 patients genotyped on the Illumina Human610-Quad BeadChip studied in a GWAS with the phenotype of musculoskeletal adverse event, see Ingle et al., 2010 (20876420), Cohort 2 consisted of 882 patients genotyped on the Illumina OmniExpress platform studied in a GWAS with the phenotype of fragility fractures, see Liu et al., 2014 (25148458), and the remaining 2913 patients were genotyped with the Illumina OmniExpressExome platform.

  Study phs001043

• Impact of Respiratory Virus Infections and Bacterial Microbiome Shifts on Lymphocyte and Respiratory Function in Infants Born Prematurely or Full Term

  Public health importance: Babies born preterm, approximately 1 out of every 9 live births in the United States, have significant respiratory morbidity over the first two years of life, exacerbated by respiratory viral infections. Many (<50%) return to pediatricians, emergency rooms and pulmonologists with symptoms of respiratory dysfunction (SRD): intermittent or chronic wheezing, poor growth and an excess of upper and lower respiratory tract infections (LRTI). SRD correlate inversely with gestational age and weight at birth and is more common in those with chronic lung disease of prematurity, yet its incidence and severity varies widely among both the prematurely born and those born at term. There is evidence from clinical studies and animal models that risks of LRTI and recurrent wheezing is influenced by gut and respiratory flora and by T cell responses to infection. Information gained from this study will be used to identify characteristics, risk factors and potential mechanisms for early and persistent lung disease in children born at term and born preterm. This Clinical Research Study will investigate the relationships between sequential respiratory viral infections, patterns of intestinal and respiratory bacterial colonization, and adaptive cellular immune phenotypes which are associated with increased susceptibility to respiratory infections and long term respiratory morbidity in preterm and full term infants. We hypothesize that the timing and acquisition of specific viral infections and bacterial species are directly related to respiratory morbidity in the first year of life as defined by SRD and by measures of pulmonary function. We hypothesize that cellular and molecular immuno-maturity are altered due to factors presented by premature birth in such a way as to promote chronic inflammatory and cytotoxic damage to the lung, with subsequent enhanced, damaging responses to infectious agents and environmental irritants. Our preliminary studies demonstrate both feasibility and expertise in mutiparameter immunophenotyping of small volume peripheral blood samples obtained from premature infants including gene expression arrays of flow cytometry sorted cells. We will use new technologies for known viral identification, as well as high-throughput metagenome sequencing of RNA and DNA virus like particles (VLP) to be used for viral discovery in infant respiratory sample and use of high-throughput pyrosequencing (454T) of bacterial 16S rRNA to determine shifts in bacterial community structure, occurring in pre-term (PT) as compared to full term (FT) infants, over the first year of life. Finally, we present statistical approaches to stratify disease risk predictors using multivariate logistic regression modeling approaches. We propose to evaluate T cell phenotypic and functional profiles relative to viral and predominant bacterial exposures according to highly complementary, but independent, Specific Objectives. Objective 1: To determine if viral respiratory infections and patterns of respiratory and gut bacterial community structure (microbiome) in prematurely born babies predict the rate and degree of immunologic maturation, and pulmonary dysfunction, measured from birth to 36 weeks corrected gestational age (CGA). Objective 2: To determine the relationship between respiratory viral infections and disease severity up to one year CGA, and the lymphocyte (Lc) phenotypes documented at term gestation (birth for term infants and 36 wks/NICU discharge in preterm infants) and at one year CGA. Three secondary outcomes of this objective will be to a) relate the quantity, type and severity of viral infections with pulmonary function at one and three years of life, b) relate the viral community structure to severity of viral infections and c) to seek evidence of modulation of viral susceptibility by bacterial respiratory and gut community structure (microbiome). The relationship of colonization with known and non-identified bacterial species in both the respiratory tract and the gut will be evaluated. Flow cytometry data corresponding to this study can be found within Immport study SDY1302. Positive and negative controls for microbiome samples are uploaded under SRA bioproject PRJNA474485. Microbiome samples corresponding to PRISM2 are distinguished from PRISM1 via "_PRISM2" appended to the sample name. Within the positive and negative controls, PRISM1 controls are uploaded as bam files and PRISM2 controls are uploaded as paired fastq. Samples ending in -08 correspond to TLDA qPCR results for a given sample. There is a column for each pathogen tested and a column to indicate where that pathogen was bacteria or virus.

  Study phs001347

• Whole Exome Sequencing of paired gDNAs and PPGL tumor DNA from patients with cyanotic congenital heart disease

  Fastq files from Whole Exome Sequencing of 12 paired germline DNA (from blood/saliva) and 14 PPGL tumor DNA (from formalin-fixed paraffin-embedded (FFPE) blocks from surgery) from patients with cyanotic congenital heart disease (CCHD) and pheochromocytoma and paraganglioma (PPGL). Sequencing was performed using the Illumina HiSeq4000.

  Dataset EGAD50000001201

• DIPG WES and RNA-Seq

  We characterised H3K27M-mutant diffuse intrinsic pontine glioma (DIPG, n=21) and RNA-Seq (n=26 DIPG, 12 normal brain)

  Dataset EGAD00001006450

• Acute Respiratory Distress Network Early Versus Delayed Enteral Feeding to Treat People with Acute Lung Injury or Acute Respiratory Distress Syndrome (ARDSNet EDEN-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. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from ARDSNet-EDEN include bronchial lavage, plasma, DNA, and urine. Please note that use of biospecimens in genetic and non-genetic research is subject to a tiered consent. Objectives: To determine if initial lower-volume trophic enteral feeding would increase ventilator-free days (VFDs) and decrease gastrointestinal intolerances compared with initial full enteral feeding. Background: Mechanically ventilated patients cannot eat normally and if not fed for long periods become malnourished. Because malnutrition is associated with poor outcomes in critically ill patients, artificial nutrition is often provided, especially in those with acute lung injury (ALI) and with expected longer duration of mechanical ventilation. When feasible, enteral nutrition targeting full caloric needs has been advocated over parenteral nutrition. However, feeding intolerance and common care practices often serve as practical barriers to reaching recommended goals. Although confounded by indication and severity of illness, several observational studies have shown improved clinical outcomes, including fewer infections, shorter duration of mechanical ventilation, and lower mortality for patients receiving a higher percentage of calculated caloric needs. Nonetheless, the best timing, formulation, and amount of enteral nutrition remain unknown. Participants: A total of 1,000 participants were enrolled. Design: Participants were randomized, stratified by site and presence of shock at enrollment, to receive either trophic or full enteral feeding for the first 6 days of mechanical ventilation. The initial 272 patients were also simultaneously randomized to a separate trial (the OMEGA study) comparing a nutritional supplement containing omega-3 fatty acids and antioxidants with an isocaloric, isovolemic control in a 2 × 2 factorial design.The designated feeding strategy was initiated within 6 hours of randomization and continued until death, extubation, or day 6. The care of mechanically ventilated patients still receiving enteral feedings after day 6 was managed according to the full feeding strategy in both groups. In extubated patients who then required reintubation, enteral nutrition was restarted and managed according to the study protocol.In the full-feeding group, enteral nutrition was initiated at 25 mL/h and advanced to goal rates as quickly as possible. Gastric residual volumes were checked every 6 hours while enteral feeding was increased. Patients randomized to the initial trophic-feeding group had enteral nutrition initiated at 10 mL/h (10-20 kcal/h) for the first 272 patients who also received the omega-3 or control supplement (240 mL volume per day). After the data and safety monitoring board stopped the OMEGA portion of the factorial design, the initial trophic feeding rate was changed to 20 kcal/h to approximate the calories that had been delivered in the OMEGA study. Gastric Residual Volumes (GRVs) were checked every 12 hours during trophic feeding. In patients randomized to trophic feeding, enteral nutrition was advanced to full-energy feeding rates following the same protocol used for the full-feeding group if they were still receiving mechanical ventilation at 144 hours. Conclusions: There was no difference between groups with regard to the primary end point, VFDs to day 28. There also were no differences in 60-day mortality, organ failure−free days, ICU-free days, or the incidence of infection between groups. Similarly, there were no differences between groups in VFDs or survival when analyzed by body mass index category or when subsets of patients with shock or more severe lung injury (acute respiratory distress syndrome) were examined.JAMA. 2012 Feb 22;307(8):795-803

  Study phs004168

• Single Cell Analysis Program - Transcriptome (SCAP-T)

  This initiative is part of the Single Cell Analysis Program (SCAP) and is funded through the NIH Common Fund (See http://nihroadmap.nih.gov/), which supports cross-cutting programs that are expected to have exceptionally high impact. Common Fund initiatives address key roadblocks in biomedical research that impede basic scientific discovery and its translation into improved human health. In addition, these programs capitalize on emerging opportunities to catalyze progress across multiple biomedical fields. Single cell analysis has recently emerged as an important field of research because technologies have improved in sensitivity and throughput sufficiently to begin measuring and understanding heterogeneity in complex biological systems and correlating it with changes in biological function and disease processes. By profiling individual cells it is possible to resolve rare cells, transient cell states, and the influence of organization and environment on such cells and states, which cannot be described by ensemble measurements. The long-term goal of the SCAP is to accelerate this move towards personalizing health to the cellular level by understanding the link between cell heterogeneity, tissue function and emergence of disease through the discovery, development and translation of innovative approaches which will dramatically change the way cells are characterized. The SCAP will focus on research, which will systematically measure, analyze and model cell-to-cell variation, and identify crucial differences and rare biological states, which may have important functional consequences. Under SCAP, there are three studies to evaluate the cellular heterogeneity using transcriptional profiling of single cells (U01): University of Pennsylvania: Role of single cell mRNA variation in systems associated electrically excitable cells University of Southern California: Evaluation of cellular heterogeneity using patchclamp and RNA-seq of single cells University of California at San Diego: Single cell sequencing and in situ mapping of RNA transcripts in human brains The SCAP has been designed as a five-year program with several components: (1) the collection, analysis and sharing of comprehensive expression datasets to understand the role of heterogeneity in tissues and systemically and identify critical parameters and states; (2) the discovery of new, innovative tools for spatiotemporal imaging, manipulation, analysis and modeling of a biologically relevant population of cells with minimal perturbation; (3) milestone-driven validation and translation of technologies for characterizing single cells in situ meeting the needs of end-users; and (4) development and coordination of a multidisciplinary research community through workshops and other collective endeavors. Further details about the NIH SCAP-T program can be found here http://commonfund.nih.gov/singlecell/. The SCAP-T data sets include the detailed phenotype information, experimental protocols, QC information, RNA-sequencing data and NGS results from human heart and human brain cells. The first data release includes 697 single cells from human brain and heart. The second data release includes an additional 978 single cells from human brain and heart. The third data release includes an additional 1631 single cells from human brain and heart. The fourth data release is a correction to this study, but adds no new cells. The fifth data release includes an additional 2984 single cells from human brain and heart. The sixth data release includes an additional 944 single cells from human brain and heart. The seventh data release includes an additional 1977 single cells from human brain and heart. The SCAP-T data portal provides a customized interface for users to quickly identify and retrieve files by phenotypes, and data properties such as sequencing facility or coverage for all of these 9231 single cells. For more information about the SCAP-T study and the data portal, please visit http://www.scap-t.org.

  Study phs000833

• single cell RNA-seq of peripheral blood from analysis in infants with MLL-rearranged Acute Lymphoblastic Leukemia

  This dataset contains two experiments. 1) Single cell RNA-seq of peripheral blood diagnostic samples from patients with MLL-rearranged infant ALL that underwent relapse or not (samples ending in R relapsed, samples ending in N did not), sequenced with SORT-seq (see cell systems, 2016, doi:10.1016/j.cels.2016.09.002). For some of the patients, multiple indipendent plates were produced (each plate is a sample). Barcode-well correspondence can be found here: https://bitbucket.org/princessmaximacenter/sharq/src/master/data/celseq2_bc384-v4.csv . 2) Single cell RNA-seq of peripheral blood diagnostic samples from patients with MLL-rearranged infant ALL that underwent relapse or not (samples ending in R relapsed, samples ending in N did not), sequenced with10x Genomics Version 2.

  Dataset EGAD00001007752

• 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

• CNS Embryonal tumors

  The dataset represents a total of 58 DNA samples from 16 male and 12 female pediatric patients affected with embryonal central nervous system tumors. The samples were subject to whole genome sequencing, WGS, [48 samples, (representing 12 male and 11 female individuals)] and whole exome sequencing, WES, [10 samples, (representing 4 male and 1 female individuals)]. One tumor tissue sample and one peripheral blood sample were analyzed from each of 26 patients, whereas two tumor tissue samples and one peripheral blood sample were analyzed from two patients. The WGS samples were sequenced 2x150 bp paired-end on an Illumina HiSeqX v2.5 instrument, and the WES samples were sequenced 2x100 bp paired-end on an Illumina HiSeq 2500 instrument. The FASTQ files generated were aligned to the human reference genome sequence GRCh38/hg38 using bwa-mem, with the ALT-aware option turned on. Sorting of reads and marking of PCR duplicates was performed with GATK. Base quality score recalibration and joint realignment of reads around insertions and deletions (indels) were conducted using GATK tools. The dataset consists of 58 files in the CRAM format (lossless compression) with a total file size of ~8,8 TB. All CRAM files but one, are derived from one sequence run and one sample. P4551_227N_P4552_112N is a CRAM file where 2 sequence runs (P4551_227N and P4552_112N) from peripheral blood samples from the same individual, P019, were aligned into one single CRAM file. Additional genomic and molecular data (FASTQ, BAM, IDAT, and VCF files) and limited clinical data can be requested by ethically approved projects conducting research in the field of pediatric cancer.

  Dataset EGAD50000000298

• Center for Common Disease Genomics [CCDG] - Inflammatory Bowel Disease (IBD) - Global Microbiome Conservancy Host Exomes

  The human body is a complex ecosystem, hosting tens of billions of bacteria, primarily in the gut. This community, known as the 'gut microbiome', is vital to human health, affecting functions ranging from metabolism, immunity, and development, to behavior. Conversely, reduced microbiome diversity and other imbalances of the gut community (dysbiosis) are associated with many diseases of the industrialized world, such as metabolic syndrome, asthma, and inflammatory bowel diseases among others. Microbiome-based interventions thus hold the potential to revolutionize our understanding of, and therapeutic approaches to, many aspects of human health and disease. Despite many advances, current understanding of the human microbiome is largely limited to majority ethnic groups in industrialized nations, and does not reflect the full diversity of human commensal microbiota. In addition to the scientific ramifications of minority underrepresentation, there are significant translational and ethical implications as well: First, failing to capture the full diversity of healthy human microbiota may limit our ability to understand and generate effective therapeutics for many microbiome-associated diseases. Second, underrepresented groups are less likely to benefit from microbiome-based medical advances tailored to well-studied populations, propagating healthcare inequities. The window of opportunity to characterize human microbiome diversity is closing rapidly. Human gut microbial diversity is diminishing around the globe, due to the spread of Westernized diets and lifestyles, which are associated with reduced microbiome biodiversity. The Global Microbiome Conservancy (GMbC) is a non-profit collaboration between scientists and communities around the world that aims to 1) preserve the full biodiversity of the human gut microbiome, 2) characterize its evolution across populations and host lifestyles and 3) investigate its interactions with the human host. We are collecting gut microbiome and human DNA samples from diverse populations around the world, from isolated groups to urbanized populations, to culture and study this essential biodiversity and to preserve it in a living "seed bank" as a long-term safeguard against future extinctions. The National Human Genome Research Institute (NHGRI) has funded a collaborative large-scale genome sequencing effort to comprehensively identify rare risk and protective variants contributing to multiple common disease phenotypes. Called the Centers for Common Disease Genomics (CCDG), this initiative will explore a range of diseases with the ultimate goal of: Undertaking variant discovery for enough different examples of disease architectures and study designs to better understand the general principles of the genomic architecture underlying common, complex inherited diseases. Understanding how best to design rare variant studies for common disease. Developing resources, informatics tools, and innovative approaches and technologies for multiple disease research communities and the wider biomedical research community. The initial focus of the CCDGs will be in cardiovascular disease (early-onset coronary artery disease, atrial fibrillation, hemorrhagic stroke), neuropsychiatric disease (epilepsy, autism), and autoimmune/inflammatory disease (type 1 diabetes, inflammatory bowel disease). The Broad Institute is one of four selected CCDG project centers. Both exome and genotyping information of GMbC participants will help understanding how recruited human populations are structured and genetically related. This human genetic structure will be analyzed in light of gut microbiome compositional and genomic differences to illuminate associations between specific microbiome traits and human groups and the evolutionary processes involved in the co-evolution of human hosts and their gut microbiome. It will also provide variant information for critical genes shaping the composition of microbiomes, such as genes involved in innate and adaptive immunity (e.g. antimicrobial peptides) or in the regulation of the immune response (e.g. Nod2). Association studies between specific variants in these genes and microbiome features will be performed, which will then be validated with in vitro and in vivo experiments. Human data from GMbC cohorts will also increase the genetic diversity of human populations, providing additional variant information for many susceptible loci that were found to be associated with Crohn's disease and ulcerative colitis. The whole genome sequencing data generated is comprised of samples from diverse and indigenous populations. Raw sequencing data, metadata, vcf and phenotype data at the individual level for a subset of the cohort's samples are available at https://anvilproject.org/data. For questions about availability, contact help@lists.anvilproject.org. Microbiome data for the samples sequenced in this study can be found in phs002235 Global Microbiome Conservancy Sequence Data.

  Study phs002205

• Whole Genome Sequencing of Therapy-Related Myeloid Neoplasms

  The dataset consists of: 51 paired tumor/normal WGS samples (26 tumors and 25 normals), and 13 normal targeted samples.

  Dataset EGAD00001010026

• RNA-seq samples

  Raw FASTQ files obtained by RNA sequencing of tumor samples from patients (age 12-29) with newly diagnosed, recurrent intermediate or high-grade sarcoma.

  Dataset EGAD00001008393

• Cardiovascular Cell Therapy Research Network (CCTRN): A Phase II, RCT of Mesenchymal Stem Cells & Cardiac Stem Cells in Subjects With Ischemic HF (CONCERT HF-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. ObjectivesTo assess the feasibility, safety, and efficacy of autologous mesenchymal stromal cells (MSCs) and c-kit positive cardiac cells (CPCs), alone or in combination, in participants with ischemic heart failure.Background The prognosis of heart failure (HF) caused by chronic ischemic cardiomyopathy (coronary artery disease and prior myocardial infarction), hereby referred to as “ischemic HF”, remains poor. Many studies have explored the use of various types of stem or progenitor cells in participants with chronic ischemic HF, with encouraging results. Several clinical trials have suggested that MSCs and CPCs are both safe and beneficial in participants with ischemic HF. At the time of this study, no information was available on the efficacy of MSCs and CPCs in humans, however, both cell types have been shown to attenuate left ventricle (LV) dysfunction in animal models. Preclinical models indicate that combining MSCs and CPCs increases the therapeutic effects, but this had not yet been tested in humans. The CONCERT-HF study was initiated to assess whether autologous MSCs and CPCs, alone or in combination, can be manufactured and delivered to participants with ischemic HF; are well-tolerated; and improve LV function, quality of life, and functional capacity, and/or reduce scar size. Participants A total of 125 participants were randomized with 33 participants randomized to the MSCs and CPCs group, 29 participants to the MSCs alone group, 31 participants to the CPCs alone group, and 32 participants to the placebo group. Design The CONCERT-HF study was a multi-center Phase II, double-blind, randomized, placebo-controlled trial designed to evaluate the feasibility, safety, and efficacy of MSCs alone, CPCs alone, and their combination compared with placebo as well as each other in patients with ischemic HF. In Stage 1 (open label, lead-in study) participants were randomized 1:1 to either a standard-of-care control group (i.e., they did not undergo harvest, mapping, or injection procedures) or combination therapy (MSCs + CPCs, as described for Stage 2) to complete safety assessments. Once approval was granted for Stage 2, participants were randomized (1:1:1:1) to one of four treatments: placebo, autologous MSCs (target dose, 150 × 106 cells), autologous CPCs (target dose, 5 × 106 cells), or a combination of autologous MSCs and CPCs. At the harvest visit, right ventricular endocardial biopsy (EMB) was performed in participants randomized to receive CPCs alone or a combination of MSCs and CPCs. Participants randomized to receive MSCs alone or placebo had a sham procedure (right heart catheterization without EMB). All participants underwent a bone marrow aspiration and approximately 14 weeks later had transendocardial, electromechanically-guided injections of study product. Visits occurred at 1 day, 1 week, and 1, 3, 6, and 12 months after study product injection. A telephone contact took place at 24 months to assess the participant's current medications, as well as morbidity and mortality. Study endpoints included measures of safety, feasibility, and efficacy. Safety outcomes included all adverse events grade 2 and higher, including major adverse cardiac events (MACE) related to HF (death, hospitalization for worsening HF, and HF exacerbation not requiring hospitalization). Efficacy endpoints included quality of life, MRI measures of LV function and structure, functional capacity, and N-terminal pro-brain natriuretic peptide (NT-proBNP) levels. Conclusions In patients with ischemic HF, autologous MSCs and CPCs, alone or in combination, are safe and feasible; CPCs were associated with a reduction in the incidence of MACE related to HF compared to placebo; MSCs, either alone or in combination with CPCs, were associated with improved quality of life; these seemingly beneficial effects of CPCs and MSCs on clinical outcome were not associated with changes in LV function or structure; and combination therapy with MSCs and CPCs was associated with the best clinical outcomes with respect to both MACE related to HF and quality of life.

  Study phs004055

• 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

• 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: &#8226; Demographics &#8226; Personal and Family History &#8226; Neurocognitive Assessment &#8226; Neurological Status &#8226; Postural Stability &#8226; Symptoms ACUTE POST-INJURY FOLLOW-UP (CARE 1.0) (24 hrs; 48hrs; Asymptomatic; Unrestricted Return to Play (RTP); 6 mos) &#8226; Neurocognitive Assessment &#8226; Neurological Status &#8226; Postural Stability &#8226; Symptoms CUMULATIVE &amp; PERSISTENT EFFECTS. (CARE 2.0) In-Person Exit Visit; Post-grad Online &#8226; Demographics &#8226; Personal and Family History &#8226; Neurocognitive Assessment &#8226; Neurological Status &#8226; Postural Stability &#8226; Symptoms &#8226; PROs &#8226; MROs (at academies only) LONG-TERM EFFECTS (CARE/SALTOS Integrated (CSI))Annual Online Assessment (at MSAs only); In-Person Research Visits &#8226; Demographics &#8226; Symptoms &#8226; Psychological health &#8226; PROs &#8226; 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, &lt;48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), Unrestricted Return to Play, 7 days following Return to Play, and at &gt;60 days after final game of junior year until end of collegiate career.Blood biomarker collection was done at Baseline, &lt;48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at &gt;60 days after final game of junior year until end of collegiate career. Multi-modal MRI studies were done at Baseline, &lt;48hrs Post-Injury, Cleared for Return to Play Progression (Asymptomatic), 7 days following Return to Play, and at &gt;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

• DNA methylation database for gynecological cancer detection, classification and assay development

  MeD-seq data (fastq files) from gynecological cancers and associated healthy tissues. In total 292 fastq files generated by MeD-seq are deposited consisting of: healthy tissues (vulva n=11, cervix n=15, endometrium n=13, fallopian tube n=18 and ovary n=13), precursor lesions of cancer (vulva n=23 and cervix n=46) and cancer (vulva n=21, cervix n=45, endometrium n=26, fallopian tube n=8 and ovary n=33)

  Dataset EGAD50000000611

• Drug development for pediatric cancers: the importance of patient' s genomic data re-use

  Cancer in children is uncommon and the overall prognosis for most pediatric cancers is good. However, while the combined survival rates have improved over the last decades, certain childhood malignancies, such as high-grade gliomas or metastatic sarcomas, still remain incurable in most patients. New strategies for targeting those devastating diseases are imperative, and patient genomic data can become a key asset in the process [1]. The Pediatric Cancer Genome Project’s datasets At EGA, we store over 500 datasets with sequencing data from pediatric cancer patients. A remarkable case is the datasets belonging to the Pediatric Cancer Genome Project (PCGP) from St. Jude Children’s Research Hospital–Washington University (Table 1 - EGAS list). PCGP is an ambitious effort to identify the mutations that drive childhood cancer and find new cures. Those datasets include 600 patients with complete tumor and normal genomes from 15 different tumor types. PCGP datasets have been an important resource for various studies that pooled genomic data from different public and in-house datasets to perform extensive genomic characterizations and publish comprehensive pan-cancer pediatric studies [2],[3]. Other interesting pediatric cancer datasets are from the Pediatric Brain Tumor Consortium, Sickkids or ICGC PedBrain project. How data reuse impacts drug development for pediatric cancers Recently, in October 2024, Nature Communications published a work led by the University of Michigan where authors used data from EGA (PCGP) check the table below as part of their strategy to pursue the identification of new tumor vulnerabilities susceptible to becoming novel therapeutic targets in diffuse midline glioma. Diffuse midline gliomas (DMG) are treatment-resistant and uniformly fatal pediatric brain tumors. The prognosis of this brainstem tumor is dismal with a median overall survival of 9–12 months from diagnosis. In this study, the authors first developed a lab model of the disease and reanalyzed data from the EGA to identify genes potentially linked to tumor severity. This approach revealed involvement of specific metabolic pathways, suggesting new possibilities for therapeutic intervention. In mice, the study shows that the use of statins can improve survival. For a brief overview of the underlying science, diffuse midline gliomas present intratumor heterogeneity with subpopulations of less-differentiated oligodendrocyte precursors and more differentiated astrocytes. Authors established in vitro models to recapitulate both phenotypes and identify metabolic programs in both subpopulations. To determine the clinical relevance, the authors re-used gene expression data from 76 DMG patients identifying a gene signature predicting decreased overall survival. After extensive metabolic characterization of subpopulations, authors defined strategies to target specific metabolic vulnerabilities. Pre-clinical experiments in mice using OXPHOS inhibitors and statins showed a reduction in tumor burden and increased overall survival [4]. In this scenario, the re-use of high-quality patient’s sequencing data appeared as an advantageous strategy to support the clinical relevance of in-vitro and pre-clinical findings. On the other hand, in rare conditions such as childhood cancer, the availability of public datasets and the possibility of pooling data from different sources can be the only way to obtain impactful results that lead to improvements for patients. References Davidoff, A. M. Pediatric Oncology. Seminars in pediatric surgery 19, 225–233 (2010). Gröbner, S. N. et al. The landscape of genomic alterations across childhood cancers. Nature 555, 321–327 (2018). Venu Thatikonda et al. Comprehensive analysis of mutational signatures reveals distinct patterns and molecular processes across 27 pediatric cancers. Nature Cancer 4, 276–289 (2023). Mbah, N. E. et al. Therapeutic targeting of differentiation-state dependent metabolic vulnerabilities in diffuse midline glioma. Nature Communications 15, (2024). Datasets and Studies ID Title Access Policy Year EGAD00001000134 Driver mutations in histone H3.3 and chromatin remodelling genes in paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAS0000100192 Somatic Histone H3 Mutations in Diffuse Intrinsic Pontine Gliomas and Non-Brainstem Paediatric Glioblastomas St. Jude Children's Research Hospital - Washington University Pediatric Cancer Genome Project 2017 EGAS00001000575 Whole genome sequencing and whole exome sequencing of DIPG tumors and matched normal tissue The hospital for sick children ("SickKids") 2016 EGAD00001000792 Exome sequencing reads of paediatric glioblastoma McGill-DKFZ Pediatric Brain Tumour Consortium 2016 EGAD00001002006 Whole genome sequencing of paediatric glioblastoma in the ICGC PedBrain project ICGC PedBrain project 2016

  Blog drug-development-for-pediatric-cancers

• How to request data

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

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

• Download Metadata

  Metadata Distribution Welcome to the realm of Metadata Distribution within the EGA ecosystem! Our Metadata REST API empowers you to effortlessly retrieve metadata from the expansive landscape of EGA. By utilising this API, you gain access to publicly available insights across various EGA domains, including studies, samples, experiments, runs, analyses, policies, DACs, and datasets. Furthermore, this API facilitates cross-referencing of objects, enabling you to gather, for example, all the datasets associated with a specific DAC, seamlessly. In addition, we have added the ability to query private data using the metadata API. If you possess the necessary permissions, you can access behind-the-login private data for a specified list of datasets. Metadata Distribution Index Identifiers Dataset Mappings Website Download Metadata API - Private Identifiers At the core of EGA's organisational structure are unique accessions that serve as essential tags for our diverse objects. Here's a quick overview of the accessions and their corresponding object types: EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID For further information check our metadata schema documentation. Dataset Mappings For authorised datasets, comprehensive mappings reveal meaningful connections: Sample_file: This file presents information about the linkage between samples and files available in the dataset. Study_experiment_run_sample: This file presents information about the linkage between studies, experiments, runs, and samples within the dataset. Study_analysis_sample: This file presents information about the linkage between studies, analyses, and samples contained within the dataset. Run_sample: This file presents information about the linkage between runs and samples within the dataset. Analysis_sample: This file presents information about the linkage between analyses and samples within the dataset. An empty file indicates the absence of corresponding information. Website Download Our website serves as your gateway to downloading metadata. Simply navigate to the dataset page, and you'll find a blue Metadata button. Once authenticated, you can click this button for authorised datasets. If you lack permissions for a particular dataset, request access by clicking the 'Request Access' button. For authorised datasets, choose your preferred metadata format: CSV, TSV, or JSON. Metadata API - Private Leverage the power of programmatic metadata downloads! Start by authenticating yourself with your credentials to obtain an access token. With this token, programmatically query private information. Queries mirror the structure of the Public Metadata API. However, behind the login, you can delve into specific mapping information (as mentioned above in dataset mappings) alongside object-level exploration. Authentication An active session is required to work with the API. Each time you log in with your credentials a new session is started, which is identified by an access_token. Below an example on how to obtain one using curl: curl https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token \ -d 'client_id=metadata-api' \ -d 'username=...' \ --data-urlencode 'password=...' \ -d 'grant_type=password' All responses from the API are in JSON format. A successful response should include a new token to be used for the session: {"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiA...TNw", "expires_in":300, "refresh_expires_in":1800, "refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiA...pTX10", "token_type":"Bearer", ... } Save the access_token value and include it in the API call headers. Example query usage Below you can find some example of queries available behing authentication and authorisation. Querying study-experiment-run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_experiment_run_sample \ -H 'Authorization: Bearer access_token' Querying run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/run_sample \ -H 'Authorization: Bearer access_token' Querying study-analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_analysis_sample \ -H 'Authorization: Bearer access_token' Querying analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/analysis_sample \ -H 'Authorization: Bearer access_token' Querying sample-file mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/sample_file \ -H 'Authorization: Bearer access_token' You can get a different output format by adding one of these options to the curl command: -H 'Accept: text/tsv' -H 'Accept: application/json' -H 'Accept: text/csv' For more detailed information, refer to the Metadata API Specification.

  Documentation access/download/metadata

• 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

• What is a DAC?

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

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

• Virginia PrIMeD Study

  The goal of this study was to determine whether screening children (2-16 yrs) in pediatric waiting rooms for genetic risk of type 1 diabetes (T1D) could be applied to diverse (by geography, genetic ancestry) communities, and for those at "high genetic risk," if barriers prevent subsequent screening for presence of islet autoantibodies. A total of 3,818 children were recruited from eight general pediatric and specialty clinics across Virginia. Clinical Research Coordinators were stationed at each clinic and obtained informed consent/assent, a brief medical history, and a saliva sample for DNA extraction and determination of their genetic risk using a T1D Genetic Risk Score (T1D GRS). Children were present in the clinic for a "healthy" visit, although children with and without a history of T1D were recruited into the study. Age, sex, self-reported ancestry/race, T1D history, and other medical history information was obtained. DNA was extracted from the saliva samples and genotyping with a T1D-focused array using 74 SNPs (including 26 SNPs in the HLA region) provided data to generate a T1D GRS for each individual. Of the 3,818 children recruited, there was a slight excess of males (1,959, 51.3%), a majority of white and Hispanic/Latino ancestry (82.8%), and 91 (2.4%) with prevalent T1D. A total of 542 (14.2%) had "high T1D genetic risk" (T1D GRS > 5). Although the T1D GRS included non-HLA genetic variants, 80% of those with "high genetic risk" would have been classified using only those SNPs in the HLA region alone. Of children with "high genetic risk" and without pre-existing T1D (n=494), 7.0% (34/494) consented for islet autoantibody screening. Among children with pre-existing T1D (n=91), 52% (n=48) also had a "high genetic risk." The HLA-focused T1D GRS was not significantly associated with age at onset of T1D. Of those at high genetic risk that consented for autoantibody testing (n=34) and completed the blood collection (n=28), two (2/28, 7.1%) tested positive for multiple autoantibodies and were at significant risk of developing T1D. Follow up of 55% of parents/guardians identified 2 (of 2,096, 0.095%) participants who developed T1D, one at "high genetic risk" and one with a first-degree relative with T1D. A major factor in obtaining islet autoantibody testing was concern over SARS-Cov-2 exposure and an independent non-scheduled blood collection.Individual-level data at each SNP (genotyped and imputed) for T1D genetic risk and affiliated data are provided in dbGaP.

  Study phs003609

• Everything you need to know about Federated EGA Affiliates: Q&A

  Addressing common questions about Federated EGA (FEGA) Affiliates and providing answers. FEGA Affiliates have recently been defined as the third tier within the newly approved “Federated EGA Structure and Organisation” document, alongside Central EGA (CEGA) and the FEGA Nodes. In this blog post, we aim to answer the questions that may arise on this topic. For more general information about FEGA Affiliates, you can refer to this blog post. Let's now start with the questions and answers! What is the difference between a FEGA Affiliate and a FEGA Node? FEGA Nodes A FEGA Node is a national-level service that accepts submissions and provides archiving and access services within a single country's jurisdiction. Nodes provide end-to-end services for submitters in that jurisdiction, including submission support, processing, permissions management, and distribution. FEGA Affiliates A FEGA Affiliate is not a national submission service. Instead, it archives data from its own legal entity and/or selected partner institutions (for example, consortium partners). Affiliates are designed for organisations and consortia that need to keep data stewardship and access decisions within their own governance model, while still enabling discovery through the broader FEGA ecosystem. What do Affiliates commit to? Here is a practical checklist of the core expectations for a FEGA Affiliate. FEGA Affiliate checklist Discovery and metadata Submit non-personal metadata to CEGA to obtain EGA accessions and enable discovery (with metadata validation handled by the CEGA Helpdesk). Operations and resilience Maintain a data storage system and a defined backup/recovery approach. Ensure operational capacity (personnel and infrastructure) to deliver Affiliate services. Maintain systems and practices that support local data security and align with EGA best-practices. Access and user support Provide data distribution or access (e.g in a trusted research environment) to authorised users to datasets hosted at the Affiliate. Provide permissions management for datasets archived by the Affiliate (the CEGA DAC (Data Access Committee) Portal is always at your disposal to use). Provide a minimal helpdesk with sufficient capacity to support relevant DACs and approved users. Membership term Commit to a minimum membership term of four years. Governance and participation (lightweight by design) Affiliates integrate into the FEGA network operationally, but without the committee obligations associated with Nodes. When is becoming an Affiliate the right fit? Consider the Affiliate tier if: You host (or plan to host) controlled-access datasets that must be managed under your organisation’s or consortium’s governance, you want studies to be discoverable through EGA, but need access control and/or distribution to remain local, and you are not aiming to operate a national submission service tier.. What if a FEGA Node already exists in my jurisdiction? We encourage any potential Affiliate to reach out to their national FEGA Node to explore collaboration at the national level. Why? Federated models within a country already exist in FEGA, where a national Node operates like a Central EGA for their country. FEGA Nodes can also represent the interests of any Affiliates within their jurisdiction at the FEGA Committees. FEGA Nodes have experience and can support you on your FEGA journey. Ready to join as a FEGA Affiliate? We’re excited to open this formally defined pathway for organisations and consortia to participate in the federation. If you think the FEGA Affiliate tier fits your needs, start by assessing: Your scope (organisation/consortium-held data rather than public external submissions), Your ability to provide the core services (permissions, distribution/access, helpdesk, monitoring), and Your readiness to submit non-personal metadata to CEGA for accessioning and discovery. To express interest, please contact us here, and we'll help you understand the onboarding steps and how Affiliates integrate into the FEGA network.

  Blog fega-affiliates-q&a

• Whole genome sequencing data of high-grade serous ovarian cancer samples (set 8a)

  Whole genome sequencing data of 26 high-grade serous carcinoma (HGSC) patients (87 samples) sequenced with MGISEQ-2000 and HiSeq X Ten.

  Dataset EGAD00001011304

• Upcycling and merging data to challenge the dogma and identify new therapeutic targets for Glioblastoma

  Glioblastoma is the most common brain tumour. Characterised by a poor prognosis and its recurrence after multimodal treatments, the search for preventable risk factors has been mainly inconclusive up to date. Recently, the data merge from datasetsdeposited at the EGA allowed Aaron Diaz’s team to discover that the glioblastoma cells shift toward a mesenchymal phenotype when the tumour is recurring. Challenges in glioblastoma research As for virtually all cancer types, many efforts have been made to unveil the molecular features responsible of the disease, and several cellular pathways have indeed been identified as being frequently mutated in glioblastoma. Nonetheless, targeted therapies based on identified genes have so far failed to improve outcome, thus survival mostly relies on a standard treatment unchanged since 2005. This is a frustrating situation for both the scientific and medical communities, and above all for the patients, still facing a dreadful path. Some researchers hypothesised that this may be due to the inability to efficiently target cancer stem cells, the originators of the other cell types, thus inducing cancer relapse. In 2019 Charles P. Couturier and colleagues sequenced RNA from single cells of freshly excised glioblastomas of 16 patients, and demonstrated that glioblastoma cells replicate normal brain cell development with a conserved neural cancer cell hierarchy centered around glial progenitor-like cells. In this way, they helped identify the possible target cells to improve efficacy and durability of treatment. Data upcycling at the EGA: the glioblastoma case study Single cell RNA sequencing is generated with a laborious and expensive protocol. The quality of the starting material is crucial (cells sample freshly extracted from the patients) and often several attempts are needed before producing reliable quality sequencing results. Collecting big numbers of patients is also challenging. The sequencing data produced by Kevin Petrecca’s group in Montreal, Canada and deposited at the EGA (EGAS00001004422) was recently upcycled by Lin Wang in San Francisco, California and pooled with their freshly produced ones, and then deposited at the EGA as Dataset EGAS00001004909 The data merge allowed Aaron Diaz’s team to discover that the glioblastoma cells shift toward a mesenchymal phenotype when the tumour is recurring. They profiled 86 primary-recurrent patient-matched paired glioblastoma samples with single-nucleus RNA, among other techniques. These very comprehensive results lead the team to challenge the findings from several other cancer fields where chemotherapy standard chemo-radiation therapy selection pressure at the level of genomic alterations; this is indeed not the case for glioblastoma, where the pressure results in phenotypic transition between cellular states. Several technical controls were made to ensure that the merge of the data was not introducing a bias in the results, and an Inter-table analysis demonstrated nearly equal contribution to overall variance from each of the studies included, indicating that the findings were not due to inter-laboratory technical effect. A novel principal-component analysis showed that the largest contribution to variation in primary glioblastoma neoplastic cells was an axis between MES (mesenchymal) and proneural expression programs. In summary, treating glioblastoma often makes a MES, as commented by Lucy Stead about this remarkable work. Check Aaron Diaz’s team Nature Cancer paper, with strong technical tools, state of the art analysis and data from different sources converging to the same outcomes that made possible a significant step toward a better handling of a frightful cancer. References Couturier, C.P., Ayyadhury, S., Le, P.U. et al. Single-cell RNA-seq reveals that glioblastoma recapitulates a normal neurodevelopmental hierarchy. Nat Commun 11, 3406 (2020). Stead, L.F. Treating glioblastoma often makes a MES. Nat Cancer 3, 1446–1448 (2022). Wang, L., Jung, J., Babikir, H. et al. A single-cell atlas of glioblastoma evolution under therapy reveals cell-intrinsic and cell-extrinsic therapeutic targets. Nat Cancer 3, 1534–1552 (2022). Related links: Kevin Petrecca’s group dataset deposited at the EGA: EGAS00001004422 Lin Wang dataset deposited at the EGA: EGAS00001004909

  Blog upcycling-and-merging-data-to-challenge-glioblastoma

• 86 paired-end MiSeq 16S rRNA sequencing samples

  We compared bacterial communities in breast milk from teen (≤19 yr, n = 26) vs. adult (&gt;19 yr, n = 56) mothers, normal weight (BMI 18.5-24.9, n = 63) vs. overweight (BMI ≥ 25, n = 19) mothers, primiparous (parity = 1, n = 41) vs. multiparous (parity &gt; 1, n = 44), early (5-46d postpartum, n = 39) vs. established lactation (4-6 mo postpartum, n = 45), breastfeeding (EBF: PBF, n = 72) vs. mixed feeding (n = 11) and mothers with (Na/K ratio &lt; 0.6, n = 75) and without SCM (Na/K ration ≥ 0.6, n = 10).

  Dataset EGAD00001004160

• Wilm's tumor sequencing data

  No. of samples: 80 (28 ULP-WGS, 26 WES, 26 RNA-SEQ) File types: FASTQ (28 ULP-WGS, 19 WES, 18 RNA) and BAM (7 WES, 8 RNA) Technology used: Sequencing - Illumina Novoseq 6000; Map/Align - Illumina DRAGEN v3.7.5; Genome assembly - GrCh38p13 Filename nomenclature: - SampleName_Passage_SampleType_TissueType_SequencingType - Passage of: PX = unknown; PZ = from patient; P0 = first passage from patient on plastic; P1 = first passage from plastic/PDX/organoid - SampleType: STN = normal; STT = tumor - SampleType STN: 00 = tissue unknown; 01 = adjacent normal; 02 = fibroblast; 03 = germline blood; 21 = cell line from patient tissue; 22 = cell line from PDX; 23 = cell line from patient fibroblast - SampleType STT: 00 = tissue unknown; 01 = primary tumor; 21 = cell line from patient; 22 = cell line from PDX - TissueType: WT = Wilm's tumor; 00 = kidney unknown; 01 = kidney left; 02 = kidney right - SequencingType: 00 = unknown; 02 = ultra-low pass whole-genome sequencing; 20 = whole-exome; 61 = bulk RNA-sequencing

  Dataset EGAD00001011111

• Submitter Portal API

  Submitter Portal API 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. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have 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, 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 the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

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

• Single cell RNA sequencing of colorectal cancer patients (KUL5)

  All libraries were sequenced on Illumina NextSeq or NovaSeq6000 until sufficient saturation was reached.

  Dataset EGAD00001008585

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

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

  Study phs001304

• Genetic characterization of B-cell prolymphocytic leukemia: a hierarchical prognostic model involving MYC and TP53 abnormalities - RNA-seq

  B-cell prolymphocytic leukemia (B-PLL) is a rare disease, whose molecular pathology is largely unknown. We report here the cytogenetic and molecular findings in a large series of 34 B-PLL. Karyotype (K) was complex (≥3 abnormalities) in 73%, and highly complex (HCK≥5) in 45%. The most frequent chromosomal aberrations were: translocation targeting the MYC gene [t(MYC)] (62%), 17p deletion including TP53 gene (38%), trisomy 18/18q (30%), 13q14 deletion (29%), trisomy 3 (24%), trisomy 12 (24%) and 8p deletion (23%). Whole-Exome Sequencing performed in 16 patients revealed recurrent mutations in TP53 (6/16, 38%), MYD88 (n=4), BCOR (n=4), MYC (n=3), SF3B1 (n=3), FAT1 (n=3), SETD2 (n=2), CHD2 (n=2), CXCR4 (n=2) and BCLAF1 (n=2). The main group of patients (21/34, 62%) had a t(MYC) associated with a higher percentage of prolymphocytes (p=0.03), CD38 expression (p&lt;0.001), lower K complexity (p=0.0004), mutations in MYC and in genes involved in RNA metabolism and chromatin remodeling. Principal component analysis of gene expression data showed that patients with t(MYC) clustered together. A second group with MYC gain (5/34, 15%), was associated with HCK≥5 (p=0,01) and trisomy 3 (p=0,008). Altogether, 26/34 patients (76%) had a MYC activation, translocation or gain, that were mutually exclusive. We identified 3 distinct cytogenetic prognostic groups (p=0.0006): lower risk: absence of MYC activation (median not reached); intermediate risk: MYC activation without del17p (125 months); high risk: MYC activation + del17p (11 months). Our results show that cytogenetic analysis is a useful diagnostic tool in B-PLL that improves prognostic stratification.

  Study EGAS00001003274

• Genetic characterization of B-cell prolymphocytic leukemia: a hierarchical prognostic model involving MYC and TP53 abnormalities - WXS

  B-PLL is a rare disease, whose molecular pathology is largely unknown. We report here the cytogenetic and molecular findings in a large series of 34 B-PLL. Karyotype (K) was complex (≥3 abnormalities) in 73%, and highly complex (HCK≥5) in 45%. The most frequent chromosomal aberrations were: translocation targeting the MYC gene [t(MYC)] (62%), 17p deletion including TP53 gene (38%), trisomy 18/18q (30%), 13q14 deletion (29%), trisomy 3 (24%), trisomy 12 (24%) and 8p deletion (23%). Whole-Exome Sequencing performed in 16 patients revealed recurrent mutations in TP53 (6/16, 38%), MYD88 (n=4), BCOR (n=4), MYC (n=3), SF3B1 (n=3), FAT1 (n=3), SETD2 (n=2), CHD2 (n=2), CXCR4 (n=2) and BCLAF1 (n=2). The main group of patients (21/34, 62%) had a t(MYC) associated with a higher percentage of prolymphocytes (p=0.03), CD38 expression (p&lt;0.001), lower K complexity (p=0.0004), mutations in MYC and in genes involved in RNA metabolism and chromatin remodeling. Principal component analysis of gene expression data showed that patients with t(MYC) clustered together. A second group with MYC gain (5/34, 15%), was associated with HCK≥5 (p=0,01) and trisomy 3 (p=0,008). Altogether, 26/34 patients (76%) had a MYC activation, translocation or gain, that were mutually exclusive. We identified 3 distinct cytogenetic prognostic groups (p=0.0006): lower risk: absence of MYC activation (median not reached); intermediate risk: MYC activation without del17p (125 months); high risk: MYC activation + del17p (11 months). Our results show that cytogenetic analysis is a useful diagnostic tool in B-PLL that improves prognostic stratification.

  Study EGAS00001003275

• 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 (&lt;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&lt;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&lt;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&gt;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

• 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

• Detection of Colorectal Cancer Susceptibility Loci Using Genome-Wide Sequencing

  The Genetics and Epidemiology of Colorectal Cancer Consortium (GECCO) is a collaborative effort comprised of a coordinating center and scientific researchers from well-characterized cohort and case-control studies. This international consortium aims to accelerate the discovery of common and rare genetic risk variants for colorectal cancer by conducting large-scale meta-analyses of existing and newly generated genome-wide association study (GWAS) data, whole genome sequencing, replicating and fine-mapping of genetic discoveries, and investigating how genetic risk variants are modified by environmental risk factors. To expand these efforts, we assembled case-control sets or nested case-control sets from 6 different North American or European studies. Summary descriptions and study participant inclusions/exclusion criteria for each of these studies are detailed below. Cancer Prevention Study II (CPS II): The CPS II Nutrition cohort is a prospective study of cancer incidence and mortality in the United States, established in 1992 and described in detail elsewhere (Calle et al., 2002 PMID:12015775; Campbell et al., 2014 PMID:25472679). At enrollment, participants completed a mailed self-administered questionnaire including information on demographic, medical, diet, and lifestyle factors. Follow-up questionnaires to update exposure information and to ascertain newly diagnosed cancers were sent biennially starting in 1997. Reported cancers were verified through medical records, state cancer registry linkage, or death certificates. The Emory University Institutional Review Board approves all aspects of the CPS II Nutrition Cohort. We restricted to samples that had blood DNA source. Controls were matched to cases in a case/control ratio of 2:1 on reference year and sex. Darmkrebs: Chancen der Verh&#252;tung durch Screening (DACHS): This German study was initiated as a large population-based case-control study in 2003 in the Rhine-Neckar-Odenwald region (southwest region of Germany) to assess the potential of endoscopic screening for reduction of colorectal cancer risk and to investigate etiologic determinants of disease, particularly lifestyle/environmental factors and genetic factors. Cases with a first diagnosis of invasive colorectal cancer (International Classification of Diseases 10 codes C18-C20) who were at least 30 years of age (no upper age limit), German speaking, a resident in the study region, and mentally and physically able to participate in a one-hour interview, were recruited by their treating physicians either in the hospital a few days after surgery, or by mail after discharge from the hospital. Cases were confirmed based on histologic reports and hospital discharge letters following diagnosis of colorectal cancer. All hospitals treating colorectal cancer patients in the study region participated. Based on estimates from population-based cancer registries, more than 50% of all potentially eligible patients with incident colorectal cancer in the study region were included. Community-based controls were randomly selected from population registries, employing frequency matching with respect to age (5-year groups), sex, and county of residence. Controls with a history of colorectal cancer were excluded. Controls were contacted by mail and follow-up calls. The participation rate was 51%. During an in-person interview, data were collected on demographics, medical history, family history of CRC, and various life-style factors, as were blood and mouthwash samples. Routine formalin-fixed, paraffin-embedded (FFPE) tumor samples from the patients enrolled were requested from the pathology institutes and used for tumor tissue analyses. This analysis includes participants with blood source DNA that were recruited up to 2010 in this ongoing study. Controls were matched to cases on reference age and sex in a case/control ratio of 2:1. Health Professionals Follow-up Study (HPFS): A parallel prospective study to the NHS (Nurses' Health Study). The HPFS cohort comprised 51,529 men aged 40-75 who, in 1986, responded to a mailed questionnaire (Rimm et al., 1990 PMID:2090285). Participants provided information on health related exposures, including current and past smoking history, age, weight, height, diet, physical activity, aspirin use, and family history of colorectal cancer. Colorectal cancer and other outcomes were reported by participants or next-of-kin and were followed up through review of the medical and pathology record by physicians. Overall, more than 97% of self-reported colorectal cancers were confirmed by medical record review. Information was abstracted on histology and primary location. Incident cases were defined as those occurring after the subject provided the blood sample. Prevalent cases were defined as those occurring after enrollment in the study but before the subject provided the blood sample. Follow-up evaluation has been excellent, with 94% of the men responding to date. Colorectal cancer cases were ascertained through January 1, 2008. In 1993-1995, 18,825 men in the HPFS mailed blood samples by overnight courier, which were aliquoted into buffy coat and stored in liquid nitrogen. In 2001-2004, 13,956 men in the HPFS who had not provided a blood sample previously mailed in a swish-and-spit sample of buccal cells. Incident cases were defined as those occurring after the subject provided a blood or buccal sample. Prevalent cases were defined as those occurring after enrollment in the study in 1986, but before the subject provided either a blood or buccal sample. Participants with histories of cancer (except nonmelanoma skin cancer), ulcerative colitis, or familial polyposis, case-control sets were excluded. Control participants were required to be free of invasive colorectal cancer and non-invasive (stage 0 in situ) colorectal cancer. For this study, only European ancestry participants with blood source DNA and incident colorectal cancer cases were eligible for selection. Since enrollment year and sex matched exactly, controls were randomly selected in a case/control ratio of 2:1. Nurses Health Study (NHS): The NHS cohort began in 1976 when 121,700 married female registered nurses age 30-55 years returned the initial questionnaire that ascertained a variety of important health-related exposures (Belanger et al., 1978 PMID:248266). Since 1976, follow-up questionnaires have been mailed every 2 years. Colorectal cancer and other outcomes were reported by participants or next-of-kin and followed up through review of the medical and pathology record by physicians. Overall, more than 97% of self-reported colorectal cancers were confirmed by medical-record review. Information was abstracted on histology and primary location. The rate of follow-up evaluation has been high: as a proportion of the total possible follow-up time, follow-up evaluation has been more than 92%. Colorectal cancer cases were ascertained through June 1, 2008. In 1989-1990, 32,826 women in NHS I mailed blood samples by overnight courier, which were aliquoted into buffy coat and stored in liquid nitrogen. In 2001-2004, 29,684 women in NHS I who did not previously provide a blood sample mailed a swish-and-spit sample of buccal cells. Incident cases were defined as those occurring after the subject provided a blood or buccal sample. Prevalent cases were defined as those occurring after enrollment in the study in 1976 but before the subject provided either a blood or buccal sample. Participants with histories of cancer (except nonmelanoma skin cancer), ulcerative colitis, or familial polyposis, case-control sets were excluded. For this study, only European ancestry participants with blood source DNA and incident colorectal cancer cases were eligible for selection. Since enrollment year and sex matched exactly, controls were randomly selected in a case/control ratio of 2:1. Prostate, Lung, Colorectal and Ovarian Cancer Screening Trail (PLCO): PLCO enrolled 154,934 participants (men and women, aged between 55 and 74 years) at ten centers into a large, randomized, two-arm trial to determine the effectiveness of screening to reduce cancer mortality. Sequential blood samples were collected from participants assigned to the screening arm. Participation was 93% at the baseline blood draw. White colorectal cancer cases with a family history of colorectal cancer (no history of ulcerative colitis, Crohn's Disease, diverticulitis, Gardner's syndrome, Familial Polyposis) and successful genotyping from previous Peters GWAS were selected for this project. Controls were matched to cases on reference age and sex in a case/control ratio of 2:1. Women's Health Initiative (WHI): WHI is a long-term national health study that has focused on strategies for preventing heart disease, breast and colorectal cancer, and osteoporotic fractures in postmenopausal women. The original WHI study included 161,808 postmenopausal women enrolled between 1993 and 1998. The Fred Hutchinson Cancer Research Center in Seattle, WA serves as the WHI Clinical Coordinating Center for data collection, management, and analysis of the WHI. The WHI has two major parts: a partial factorial randomized Clinical Trial (CT) and an Observational Study (OS); both were conducted at 40 Clinical Centers nationwide. The CT enrolled 68,132 postmenopausal women between the ages of 50-79 into trials testing three prevention strategies. If eligible, women could choose to enroll in one, two, or all three of the trial components. The components are: Hormone Therapy Trials (HT): This double-blind component examined the effects of combined hormones or estrogen alone on the prevention of coronary heart disease and osteoporotic fractures, and associated risk for breast cancer. Women participating in this component with an intact uterus were randomized to estrogen plus progestin (conjugated equine estrogens [CEE], 0.625 mg/d plus medroxyprogesterone acetate [MPA] 2.5 mg/d) or a matching placebo. Women with prior hysterectomy were randomized to CEE or placebo. Both trials were stopped early, in July 2002 and March 2004, respectively, based on adverse effects. All HT participants continued to be followed without intervention until close-out. Dietary Modification Trial (DM): The Dietary Modification component evaluated the effect of a low-fat and high fruit, vegetable and grain diet on the prevention of breast and colorectal cancers and coronary heart disease. Study participants were randomized to either their usual eating pattern or a low-fat dietary pattern. Calcium/Vitamin D Trial (CaD): This double-blind component began 1 to 2 years after a woman joined one or both of the other clinical trial components. It evaluated the effect of calcium and vitamin D supplementation on the prevention of osteoporotic fractures and colorectal cancer. Women in this component were randomized to calcium (1000 mg/d) and vitamin D (400 IU/d) supplements or a matching placebo. The Observational Study (OS) examines the relationship between lifestyle, environmental, medical and molecular risk factors and specific measures of health or disease outcomes. This component involves tracking the medical history and health habits of 93,676 women not participating in the CT. Recruitment for the observational study was completed in 1998 and participants were followed annually for 8 to 12 years. All centrally confirmed White cases of invasive colorectal cancer, or death from colorectal cancer were selected as potential cases from the March, 2011 database. Case priory lists are: 1) have positive family history of colorectal cancer; 2) randomly select cases until we get a total of n=800 cases. Control participants were required to be White, free of invasive colorectal cancer and non-invasive (stage 0 in situ) colorectal cancer. Centrally denied cases of colorectal cancer were not allowed into the control pool. Case and control participants were subject to the following exclusion criteria: (1) had prior history of colorectal cancer at baseline; (2) had no available DNA (DNA searching as Nov 15, 2012); (3) cannot be deposited to dbGaP; (4) lost to follow-up after enrollment; (5) selected for WHI study M26 Phase II. Controls were matched to cases in a case/control ratio of 2:1. In order to get 2 cases with 1 control, cases were grouped by enrollment year (a total of 5 groups). For each year group, around 50% cases were selected to match controls. In total, 401 cases were selected to match controls. Matching was done on enrollment year, which was matched exactly. For additional information, see dbGaP: phs000200 and ClinicalTrials: NCT00000611.

  Study phs001554

• From research to data sharing: exploring EGA user's experiences

  The Cell Plasticity and Regeneration Group at the Bellvitge Biomedical Research Institute-IDIBELL focuses on the process of recruitment of macrophages that takes place in the small intestine during injury and healing. They recently published a paper titled “Mucosal Macrophages Govern Intestinal Regeneration in Response to Injury" in Gastroenterology Journal. As part of the research, some experiments were conducted using human intestinal organoid lines. These cells were processed for RNA sequencing, and the sequencing data were deposited at the EGA to be made available to the scientific community. When dealing with human genomic information, repositories must ensure the availability of the datasets while ensuring data protection. In this context, the European Genome-phenome Archive stands as a service for secure archiving and sharing of genetic, phenotypic and clinical data resulting from biomedical research. Following the recent publication of their paper, we took the opportunity to talk to Ilias Moraitis, first author, and Jordi Guiu, group leader, to find out about their experience with data sharing. Could you explain the focus of your research? In the lab, we study intestinal regeneration and how immune cells participate in this process. We use several techniques: engineered mouse models, image tracing, as well as mouse and human cells intestinal organoids. What challenges do you face regarding data management? We didn’t have a lot of problems. Always the informatic part, the data analysis, can give problems. But everything was smooth and working. We think it’s very important to deposit the data in repositories. For the mouse data it is very straightforward, but for us it was the first time depositing human data, which is sensitive because it comes from patients, and this is legally regulated. That’s why we thought about the EGA, and it was our first time. Why do you think it is important to submit data to repositories such as EGA? Because we think data is important for the science. Nowadays, we are sequencing a lot everywhere worldwide and having these resources shared with the scientific community it’s not only good for science, but it is also saving money and reducing costs. And there is so much data in there that can be used for other projects and for other questions. And it saves time! How was the process of submitting the data to the EGA? The communication worked very well but it was slower than we would like. But I think this is something we learn on the way. People usually wait until the last minute to do this before publication but if you know it in advance, you can start the process earlier. If you had to repeat the process, would you do anything differently? It’s like everything, isn’t it? For the first time you don’t know, you aren’t sure, but for the second time you know the steps, you know what to do and it’s faster. Of course, we would to do it earlier. Also, there were some things related to the control access that we didn’t know how to manage, but it was something more internal to us. Who is going to receive the communications and when, is our ethical committee going to evaluate this? All these technicalities that we didn’t know before starting this process, so we had to think about all these things. Next time it will be faster on our side. Do you have any suggestions for us to improve the submission process? Maybe we’ll need to ask our bioinformatician who did it! He was in charge of this part. Besides that, we think if the process were faster, it would be better for everyone. Also, in science a lot of times you have to do a lot of things at the very last minute, because of the nature of the experiments, or the need to accomplish for submitting a paper. Being faster in the process would be a plus. On your side, we went through the process and were able to find some information, but there were aspects we weren't aware of and weren't sure how to handle. I'm not sure if other institutes have different protocols for managing data requests or how they handle these internally. We believe the main issue lies in how the forms are filled out. Do you have any recommendations for other submitters? The main advice is to do this with enough time. Submit the data when you have the sequences, and don’t wait until the last minute. And then it can be under embargo, so you don’t need to make it public at that moment. As soon as you sequence, upload it and then it will be there for whenever you need to publish. How do you think we could encourage other researchers to submit their data? There are different layers here. One is that it is mandatory. You have to do this. The other is that we belong to a research community, to the same community and sharing this is making our research community stronger and more efficient. And then, also because this gives you visibility. The data is there, other people can analyse your data, and this also will bring citations to your papers. It has many advantages.

  Blog from-research-to-data-sharing

• National Eye Institute (NEI) Age-Related Eye Disease Study (AREDS)

  The Age-Related Eye Disease Study (AREDS) was initially designed as a long-term multi-center, prospective study of the clinical course of age-related macular degeneration (AMD) and age-related cataract. In addition to collecting natural history data, AREDS included a clinical trial of high-dose vitamin and mineral supplements for AMD and a clinical trial of high-dose vitamin supplements for cataract. AREDS participants were 55 to 80 years of age at enrollment and had to be free of any illness or condition that would make long-term follow-up or compliance with study medications unlikely or difficult. On the basis of fundus photographs graded by a central reading center, best-corrected visual acuity and ophthalmologic evaluations, 4,757 participants were enrolled in one of several AMD categories, including persons with no AMD. The clinical trials for AMD and cataract were conducted concurrently. AREDS participants were followed on the clinical trials for a median time of 6.5 years. Subsequent to the conclusion of the clinical trials, participants were followed for an additional 5 years and natural history data were collected. The AREDS research design is detailed in AREDS Report 1. AREDS Report 8 contains the mainline results from the AMD trial; AREDS Report 9 contains the results of the cataract trial. Blood samples were also collected from 3,700+ AREDS participants for genetic research. Genetic samples from 600 AREDS participants (200 controls, 200 Neovascular AMD cases, and 200 Geographic Atrophy cases) were selected using data available in March 2005 and then were evaluated with a genome-wide scan. These data, as well as selected phenotypic data, were made available in the dbGaP. DNA from AREDS participants, which is currently being stored in the AREDS Genetic Repository, is available for research purposes. However, not all of the 3,700+ AREDS participants who submitted a blood sample currently have DNA available. In addition to including the data from the genome-wide scan on the 600 original samples, this second version of the AREDS dbGaP database provides a comprehensive set of data tables with extensive clinical information collected for the 4,757 participants who participated in AREDS. The tables include information collected at enrollment/baseline, during study follow-up, fundus and lens pathology, nutritional estimates, quality of life measures and measures of morbidity and mortality. In November 2010, over 72,000 high quality fundus and lens photographs of 595 AREDS participants (of the original 600 selected for the genome-wide scan) were made available in the AREDS dbGaP. In addition to the genome-wide scan data, the fundus and lens grading data for these participants are also available through the AREDS dbGaP. Details about the ocular photographs that are available may be found in the document "Age-Related Eye Disease Study (AREDS) Ocular Photographs". In January 2012, a measure of daily sunlight exposure was added in a separate &#34;sunlight&#34; table. Furthermore, the &#34;followup&#34; table has been revised. The visual acuity for the right eye was inadvertently missing at odd-numbered visits (01, 03, 05, etc.). This data is now part of the table. In February 2014 over 134,500 high-quality fundus photographs (macular field F2) of 4613 AREDS participants were added to the existing AREDS dbGaP resource. The AREDS dbGaP image archive already contains over 72,000 high quality fundus and lens photographs of 595 AREDS participants for whom dbGaP-accessible genotype data exist. Information about the available ocular photographs found in the document "Age-Related Eye Disease Study (AREDS) Ocular Photographs" has been updated with an addendum. It is hoped that this resource will better help researchers understand two important diseases that affect an aging population. These data may be applied to examination and inference on genetic and genetic-environmental bases for age-related diseases of public health significance and may also help elucidate the clinical course of both conditions, generate hypotheses, and aid in the design of clinical trials of preventive interventions. Definitions of Final AMD Phenotype Categories Please see phd001138.1 for a detailed description of how AREDS participants&#39; final AMD phenotype was categorized. User&#39;s Guide for AREDS Phenotype Data A detailed User&#39;s Guide for the AREDS phenotype data is available. This User&#39;s Guide is meant to be a comprehensive document which explains the complexities of the AREDS data. It is recommended that all researchers using AREDS phenotype data make use of this User&#39;s Guide.

  Study phs000001

• 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&#39;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

• 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

• Privacy Notice for Data Access Committee Account

  Privacy Notice for EGA Data Access Committee Account 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: 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 you: Name Email address Title/Position Organisation Organisational affiliation Business address Telephone number IP addresses Date and time of a visit to the service website Operating system Amount of data transmitted Browser Username Password The data controller will use your personal data for the following purposes: To provide DAC user account and authenticated access to the service, To publicly publish some information to facilitate scientific research, To better understand the needs of the data subjects and guide future improvements of the service, To create anonymous usage statistics (from number of DACs, datasets per DAC). 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 (for all user account data), The general public via Internet will get access to your name, email address, business address, telephone number and organisation you belong to. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Data categories ‘name`, `email address`, `telephone number`, `business address`; `organisation’ of the DAC user are published on the Internet. They thus become accessible to recipients in countries outside the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI), is necessary for important reasons of public interest embedded in the aims of EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union 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-dac

• 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&#956;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&#174; (Ambion, ThermoFisher Scientific, Waltham, MA), and after 48 hours at +4&#176;C were stored at -80&#176;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

• Paired-end Whole Exome-seq analysis of the 3D evolution of glioma cell populations. Part 2.

  Dataset contains paired-end Whole Exome sequencing data from 257 glioma samples from 28 patients. 26 normal blood samples are also included.

  Dataset EGAD00001009496

• Providing safe access to sensitive human data across borders: Federated EGA becomes a reality

  Enabling discovery and access to sensitive data across national boundaries is vital for improving human health. It enables more powerful and efficient research by increasing the volume and diversity of data available for analysis. It allows us to better understand the causes of diseases – cancer, rare diseases, infectious diseases like COVID-19 – and develop new medicines and treatments. Sensitive human omics data are typically generated by research initiatives and shared using specialist repositories which provide services for data submission, discovery, and access. The EGA is one such repository. Established in 2008 at EMBL’s European Bioinformatics Institute (EMBL-EBI) in the UK, since 2012 the EGA (“Central EGA”) has been jointly managed by EMBL-EBI and the Centre for Genomic Regulation (CRG) in Spain. Many countries have emerging personalised medicine programmes which generate data from national initiatives. These programmes are driving a transition in human genomics from being research-driven to receiving funding through healthcare. Data generated in a clinical context are subject to stricter governance than research data and must follow national data protection legislation. To solve these challenges, the Federated EGA provides a network of connected resources to enable transnational discovery of and access to human omics data for research, while also respecting jurisdictional data protection regulations. In this way, the Federated EGA infrastructure supports the goals of European initiatives such as the 1+ Million Genomes initiative (1+MG), the European Health Data Space, and a number of EU-funded 1+MG implementation projects including Beyond 1 Million Genomes. The Federated EGA is made up of “Nodes” – typically nationally funded and operated – which store and manage data locally while allowing global discovery within the Federated EGA network. Since 2016, multiple parallel efforts, supported by ELIXIR and other transnational and national initiatives, have created technical and legal frameworks for establishing the Federated EGA. In 2022, the first five Nodes – Finland, Germany, Norway, Spain, and Sweden – officially joined the Federated EGA by signing Federated EGA Collaboration Agreements with Central EGA. The Finnish FEGA Node is operated by CSC - IT Center for Science and provides data management services according to national laws and the requirements of the EU General Data Protection Regulation (GDPR). These services provide tools and support for the whole life-cycle of sensitive research data from collating to analysis, publication, and authorised re-use. The development of the services has been a joint effort with the other Nordic nodes within NeIC's Tryggve and Heilsa projects, and funded by Finnish Ministry of Education and Culture and projects coordinated by ELIXIR Finland. Read more about Finnish FEGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. The German Human Genome-Phenome Archive (GHGA) strives to provide a national infrastructure as well as an ethical and legal framework that balances FAIR omics data usage and data protection needs for Germany. As a Germany-wide consortium funded by the German Research Foundation under the umbrella of the NFDI association, GHGA combines the expertise of 21 universities and research institutions to form a federated national infrastructure. Read more about GHGA signing. In Norway, a key component of the infrastructure is the services of The Sensitive Data Service (TSD) offered by USIT at University of Oslo. The Federated EGA Norway Node is developed by ELIXIR Norway and operated by the University of Oslo as the responsible legal entity. Core software modules are developed jointly with the other Nordic nodes in the NeIC Tryggve and Heilsa projects. Read more about FEGA Norway signing. The Spanish FEGA (es-FEGA) is a national service for storing sensitive biomedical data in Spain. Supported by the Spanish Institute of Bioinformatics (INB) in collaboration with Central EGA, sensitive research datasets are primarily hosted at the Barcelona Supercomputing Centre facilities. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. The Swedish Sensitive Data Archive is a secure data archive and sharing platform for sensitive datasets. It was developed by the National Bioinformatics Infrastructure Sweden (NBIS) in collaboration with other Nordic ELIXIR Nodes through the Tryggve and Heilsa projects funded by NeIC and coordinated with Central EGA through ELIXIR. Read more about the Swedish Node signing. By providing a solution for secure and efficient management of human omics data, the Federated EGA aims to foster data reuse, enable reproducibility, accelerate biomedical research, and improve human health. Find out more Interested in setting up your own Federated EGA Node? Check out the FEGA Onboarding Knowledge Base for more information. The ELIXIR Federated Human Data Community is a great entry point for anyone interested in learning more about the Federated EGA. You can: Join the ELIXIR Federated Human Data Community mailing list (select “Human Data”) Attend the ELIXIR Federated Human Data Community calls

  Blog safe-access-to-sensitive-human-data-federated-ega

• Genome-Wide Association Study of Patients with Coccidioidomycosis

  BackgroundValley Fever is typically an infection of the lungs caused by the fungi Coccidioides immitis and Coccidioides posadasii. The incidence of Coccidioidomycosis (CM), or infection with Coccidioides, has dramatically increased over the last 20 years. This is particularly true in the Southwest of the United States, where people often breathe fungal spores that arise from the soil. Reasons for increased infection rates are thought to include population growth and construction in these endemic regions, an increase in the number of people whose immune systems are compromised due to infection or treatment with drugs required for organ transplants, climate change, as well as improved testing practices and greater physician awareness.&#160;Mild CM most commonly presents itself with flu-like symptoms and rashes, which can last weeks to months. Individuals with compromised immune systems, specifically-- substantial suppression of the immune cells known as T cells, can develop severe pulmonary and disseminated disease. Infection that remains localized to the lungs is referred to as pulmonary disease, but when the infection spreads out of the lungs into other parts of the body it represents a more serious condition referred to as a disseminated disease, or disseminated CM. In nature, Coccidioides spp. exists as mold and lives in dust and soil. When the contaminated soil or dust is disturbed by human activity, animals, or weather, the Coccidiodies spores are released into the air. Airborne spores are taken up by breathing and settle in the lungs. Once in the moist and warm environment of the lung, spores transform into spherules, which divide and become filled with smaller spores, called endospores. When the spherules get large enough, they rupture and release these endospores, which can spread and disseminate to surrounding tissue. The cycle then repeats itself as these endospores develop into new spherules3.&#160;Different ethnic groups have been described to vary in their susceptibility to developing disseminated CM after initial infection with Coccidioides. For example, evidence suggests that African-American and Filipino patients suffer the disseminated disease at a greater rate than other ethnicities. The suggestion that race plays a role in the clinical expression of the disease is still a source of debate amongst the scientific community and any genetic mechanisms responsible for these differences have yet to be fully elucidated. If our genetic makeup influences our ability to limit the spread of infection, finding which DNA differences cause these variances could provide clues to how the body successfully fights infection, and provide opportunities to boost the body&#8217;s ability to do this. Further, if we are able to identify the specific genetic risk factors that correlate with the development of disseminated infection, physicians could perform genetic screenings to identify high-risk patients and provide them with preemptive antifungal therapy prior to developing disseminated disease.The genome, made up of DNA, contains all of the information needed for humans to develop and grow. Genome-wide association studies (GWAS) allow us to look for inherited differences that are more common between people who share a particular trait, for example, height or susceptibility to certain diseases, compared to those who do not share the trait. Although some traits and diseases are controlled by a single gene, the majority are influenced by contribution from several, or even many, different genes. To find evidence of genes that contribute to specific traits, GWAS typically compares genome information from large numbers of people who have a particular disease (referred to as &#8220;cases&#8221;) looking for DNA sequences that are common among these samples, and are different from DNA sequences seen in large numbers of people who lack the trait, but are as much like the cases as possible (referred to as &#8220;controls&#8221;). The DNA sequence data from each group, cases versus controls, are analyzed to see if there are specific genomic differences that tend to be associated with the disease.&#160;MethodsTwo separate GWAS approaches were taken to look for genetic differences that could be responsible for the observed differences between the different patient populations we are studying. The first method, known as genotyping, scans for differences at a set of positions across the genome, which includes both the genes that encode our proteins and the larger amount of DNA that does not. The second method, known as exome sequencing, allows us to compare the entire sequence of the portion of the genome that codes for proteins.&#160;&#160;For this study, DNA from patients with either pulmonary or disseminated CM were genotyped and exome sequenced to look for DNA differences that are associated with one condition or the other. All patients were at least 18 years old, had no evidence of immunosuppression, and had proven or probable pulmonary coccidioidomycosis according to established diagnostic criteria. Of these patients, a subset demonstrated disseminated disease, i.e., they showed evidence of coccidioidal infection outside of the thorax by biopsy/aspiration, had radiographic imaging, and show positive coccidioidal serology. Our criteria for including patients with the pulmonary disease were that they must not require ongoing antifungal treatment or show evidence of active CM (in skin test positive patients), show no evidence of extrapulmonary dissemination, and have no evidence of ongoing pulmonary infection (pulmonary nodules are accepted) beyond six months from diagnosis.Patient DNA was purified from blood or from sputum samples by the labs of our collaborators, Drs. George Thompson (UC Davis School of Medicine) and John Galgiani (University of Arizona Health Sciences). Genome-wide association (GWAS) analysis was carried out to look for candidate loci associated with pulmonary versus disseminated disease, taking into account the population structure of the samples. Single nucleotide or insertion/deletion variants were identified from whole-exome sequences (WES) using the Picard/BWA/GATK pipeline.&#160;ResultsTable 1. Pulmonary versus Disseminated Cases of Coccidiomycosis for GWAS, Sorted by EthnicityEthnicityPulmonary CasesDisseminated CasesAsian85Black/African American1664Caucasian/White4015Filipino03Hispanic/Latino3414Indian21Mexican American1039Pacific Islander01Samoan03Vietnamese10Unknown16917More than one race02Total373134Table 1 shows the number of samples analyzed from patients with pulmonary versus disseminated disease, and patient ethnicity, where known. In all, we worked with 507 samples, including 134 samples from patients with disseminated disease and 373 samples from patients with pulmonary disease. Of these, 505 samples were genotyped using the Multi-Ethnic Global Array from Illumina Inc. In addition, we were able to generate whole-exome sequence from 498 patient samples. No significant associations were detected that differed between samples from patients with pulmonary versus disseminated disease; that is, no particular DNA sequences were found to be significantly enriched in patients with disseminated disease compared to patients with pulmonary disease. The ability to detect genetic association between specific sequences and genetically determined traits is influenced by several factors, including how many patient samples are available to compare, how many different genes contribute to the trait and how strong their contributions are. When the number of genes is small and the contribution of each gene is great, smaller numbers of patient samples are needed to detect an association. When more genes are involved, or the contribution from each gene is more modest, larger numbers of patient samples must be examined. While we were not able to detect any associated within this study, it does not mean that subsequent studies would not find this connection. Our study suggests significantly more samples should be analyzed in further studies.Whole-exome sequences were generated from 498 samples and were aligned to reference sequences to identify positions where the sequences differed from the reference. These data are being analyzed to determine if any variants are associated with pulmonary, versus disseminated, disease.&#160;

  Study phs002170

• IMCISION DNAseq

  Whole-exome sequencing of 32 primary head and neck squamous cell carcinoma samples prior to treatment with neoadjuvant anti-PD-1 (n=6) or anti-PD-1 + anti-CTLA-4 (n=26) immunotherapy. DNA quantity used: 50ng. Library Preparation Kit: Twist Human Core Exome Plus (Twist Bioscience). Sequencing parameters: NovaSeq 6000, 2x 100 bp. File type: fastQ.

  Dataset EGAD00001008139

• 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 submission. 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” or “Read & Write”). If you want to invite all the collaborators from a previous submission, you can add them by selecting said submission.In the event that the submission has been closed, you will need to reopen it. To do this, you will need to modify one of the objects in the submission, for example, copy and paste the title. 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 batch 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 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 samples and 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 batch 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 in 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). Further information can be found in the Submission Tour 9. Finalise submission Once the files are ingested please delete them from your SFTP INBOX before 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 file to a closed submission, you will need to re-open the submission where the dataset was registered. 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, you must edit any object within the submission. For example, you can copy and paste the title. Take The Tour The Submitter Portal Take The Tour is a visual guidance 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

• NHGRI GREGoR Consortium: Genomics Research to Elucidate the Genetics of Rare Disease

  The NHGRI GREGoR (Genomics Research to Elucidate the Genetics of Rare Disease) Consortium was established in June 2021 with the goal of developing novel tools and approaches to advance the discovery of the genetic basis of rare conditions. Numerous types of molecular data are generated in GREGoR and available on the AnVIL cloud platform via dbGaP application, including short- and long-read genome and exome sequencing, transcriptomics, metabolomics, methylomics, and proteomics. De-identified clinical and demographic data is obtained, with a focus on standardized ontologies.Visit the GREGoR Consortium data webpage for summary information about the GREGoR Dataset, including numbers of participants and data types, methods documentation, and Release Notes. The Consortium comprises five Research Centers (RCs - see below), a Data Coordinating Center (DCC), and various partner members and external collaborators.Baylor College of Medicine Research Center (BCM-GREGoR) The Baylor College of Medicine GREGoR program, which is part of the GREGoR consortium, enrolls individuals, families, and cohorts with suspected rare disease across a range of syndromic and non-syndromic phenotypes. Subjects are enrolled from national and international collaborating physician referrals. Subjects provide written informed consent for future re-contact. Data generated and shared include family structure, detailed phenotypes, exome or short-read genome data, and in some cases long-read genome or RNA-sequencing, and these are shared upon completion of standard quality control checks and annotation. Broad Institute (Broad) The Broad Center for Mendelian Genomics, part of the GREGoR consortium uses next-generation sequencing (exome, genome, transcriptome, and long read sequencing), computational approaches, and functional studies to discover the variants and genes that underlie Mendelian conditions with a particularly focus on neuromuscular, neurodevelopmental, and syndromic phenotypes. Samples come from collaborators and direct enrollment through the Rare Genomes Project and we are committed to rapid data sharing without an embargo period. University of California, Irvine (UCI-GREGoR) To accelerate the pace of Mendelian disease gene discovery and clinical implementation, we propose a Mendelian Genomics Research Center, part of the GREGoR Consortium, leveraging the broad pediatric and adult clinical and research expertise at Children's National Hospital and University of California, Irvine. Our goal is to develop best practices to increase the diagnostic yield of rare diseases, engage the community to reduce health disparities for complex diagnoses, while creating a dataset accessible to all. Our Center will unite world class experts combining basic and translational research with innovative approaches to phenotyping, variant identification and functional investigation of both coding and non-coding sequence changes with the goals of discovering novel Mendelian gene variations and identifying variants not detected on current sequencing pipelines, disambiguating uncertain variants into disease-causing versus benign categorizations, and sharing information by working collaboratively with the GREGoR community.GREGoR Stanford Site (GSS) The goal of the GREGoR Stanford Site (GSS) is to provide a platform for functional genomics research and validation to improve diagnosis in Mendelian disease. Participants included individuals with undiagnosed suspected Mendelian disease who had non-diagnostic exome sequencing and their immediate family members. Participants and their family members provided written, informed consent and biological samples from which DNA, RNA, plasma, fibroblasts, PBMCs and other cell types were generated and stored. Samples from research participants and their immediate family members may have undergone short and long-read genome sequencing, transcriptome sequencing, metabolomics and/or lipidomics profiling, methyl-capture-sequencing and ATAC-sequencing. De-identified clinical data extracted from participant medical records are linked to the samples. University of Washington Center for Rare Disease Research (UW-CRDR) The goals of the University of Washington Center for Rare Disease Research are to: (1) maximize novel gene discovery for Mendelian conditions by recruitment, short- and long-read whole genome sequencing, transcriptome sequencing and analysis of families with rare conditions for which the gene is either unknown or the gene is known but no pathogenic variant can be identified via clinical testing; (2) develop new strategies for gene discovery for Mendelian conditions caused by variants that are difficult to detect using conventional testing strategies, variants of unknown function effect (e.g., regulatory, structural variants) or have unusual modes of inheritance; and (3) implement high-throughput screening and targeted follow-up functional studies to prioritize and validate candidate non-coding variants. De-identified data and phenotypic information are shared via MyGene2, ClinVar, and AnVIL.

  Study phs003047

• Paired-WGS Sequencing of Primary lymphomas of the central nervous system (PCNSL)

  26 Tumor/Control pairs of WGS data of PCNSL tumors, sequenced on either Illumina HiSeq2000/2500 instruments or HiSeq X Ten. The controls are blood or buffy coat samples in most cases.

  Dataset EGAD00001007806

• How to use EGA Webin?

  EGA Webin EGA Webin serves as a platform for registering metadata for array based submissions, large scale sequence submission as well as for legacy EGA submission accounts (ega-box-XXXX). For large scale submitters of sequence data you have also the option to submit metadata via XMLS programmatic submission, while new submitters are advised to utilise the Submitter Portal for their submissions. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. WEBIN actions: Register metadata for a sequence submission Register study, samples, experiments, runs, DAC, policy and dataset/s after file upload. Register components for your array-based metadata submission Register study, samples, DAC or policy before uploading files. Edit existing submission metadata Change or update previously submitted metadata. Register metadata for a sequence submission Ensure that all sequence files have been encrypted before uploading them to your submission account using the EgaCryptor. Go to the EGA Webin and log in using your submission account name (ega-box-XXX) and password. Register components of your metadata submission Study Samples Data Access Committee (DAC) Data access policy Dataset For array-base submissions: Study, Samples, Data Access Committee (DAC) and Data access policy may all be registered BEFORE file upload and dataset registration through the array-base template. Register your Study Go to the “Studies (Projects)” box Click on “Register Study” and fill in the information related to your study. Click on “Submit”, this will save the information and generate an EGA study ID. To use the study accession number in a publication, the study has to be previously released on the EGA website, we suggest the following format: "Sequence 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 on https://ega-archive.org and “The European Genome-phenome Archive in 202 "(10.1093/nar/gkab1059)" Register your Samples Go to the “Samples” box Click on “Register Samples” Select “Download spreadsheet to register samples” and customise your template, there is a default EGA template (EGA default checklist) but more attributes can be added if required. For the EGA default checklist, there are mandatory,recommended and optional attributes. As well custom fields which can be added if required. Mandatory attributes Field Name Description tax_id Taxonomy ID of the organism as in the NCBI Taxonomy database. Entries in the NCBI Taxonomy database have integer taxon IDs. See our tips for sample taxonomy here scientific_name Scientific name of the organism as in the NCBI Taxonomy database. Scientific names typically follow the binomial nomenclature. For example, the scientific name for humans is Homo sapiens. sample_alias Unique name of the sample. If not selected system will auto generate an unique alias sample_title Title of the sample sample_description Description of the sample phenotype *** Where possible, please use the Experimental Factor Ontology (EFO) to describe your phenotypes. Recommended attributes Field Name Description subject_id Identifier for the subject where the sample has been derived from gender * Sex Optional attributes Field Name Description sex sex of the organism from which the sample was obtained disease_site Affected organ sample type Affected organ donor_id ** Identifier of the donor where the sample has been derived from *Gender should be described as 'male', 'female' or 'unknown'. If 'unknown' due to a known sex chromosome aneuploidy, please create a user defined attribute called 'Sex chromosome karyotype' and add the appropriate value, for example, 'XXY'. **Donor id (Subject id) should be a de-identified subject handle. If unknown, please add 'unknown' to the field. ***Phenotypes should, where possible, be an Experimental Factor Ontology accession. If a term cannot be found to describe your phenotype please use free text. All sample phenotypes considered important for further analysis of the data should be provided (for example, tumour type), additional phenotype attributes can be created by defining your own attributes; use the notion 'phenotype2', 'phenotype3', etc. After you have customised the fields for the sample submission, download the template and fill in the information. Example of the sample template: Finally upload the sample template to get the EGA accession IDs for the samples. Register your Data Access Committee (DAC) Further information on the role of your DAC Go to the “Data Access” box Click on “Register Dacs” Input the information about the DAC and register at least one main DAC contact. Register your Data Access Policy Your Data Access Policy provides the terms and conditions of data use, this is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAC). Go to the “Data Access” box Click on “Register Policies” Select the DAC to which this policy will be linked to and fill in the policy information. Submitting your Runs and Analyses This section is only for sequence data submission, for array-based submission it can be skipped. Please refer to our Submitting array based metadata Runs Registration Go to the “Raw Reads (Experiments and Runs)” box Click on “Submit Reads” Select “Download spreadsheet template for Read submission” Select the template corresponding to your submission type For the templates you have the option to customise the optional fields. To check their description click on “Show Description “ Download the template and fill in the required information. Example of the runs template: We recommend that Fastq, BAM, and CRAM read files are submitted using Webin-CLI When using this interface instead of Webin-CLI, raw sequences must be uploaded in one of the supported data formats before they can be submitted. The files can be uploaded using FTP or Aspera. The study and the sequenced samples must be pre-registered before the raw reads are submitted. Please note that each individual study and sample should be registered only once. You will be asked to provide information about the sequencing libraries and instruments. Submitting your Dataset This section is only for sequence data submissions, for array based submissions it can be skipped. Please refer to our Submitting array based metadata The dataset describes the data files, defined by the run (EGARXXXXXXXXXXX) and analysis (EGAZXXXXXXXXXXX) accessions that make up the dataset and links the collection of data files to a specified Data Access Committee and Data Access Policy. As a result, you must have registered your Reads and experiments, Data Access Committee (DAC) and Data access policy before submitting your Dataset. 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. Please contact EGA Helpdesk for further assistance. Go to the “Data Access” box Click on “Register Dataset” Select the Data Access Committee (DAC) and Data access policy Register your dataset After submitting your dataset you should contact the EGA Helpdesk to provide a release date for your dataset. Datasets are automatically held (i.e. not released) unless they are affiliated to a study that has already been released. Edit/update existing submission metadata Go to the “Report” section of the object you would like to edit. Locate the object and click on the arrow under action. An option menu will be displayed. Objects can be edited through their XML or with the WEBIN menu. After an object has been edited, changes would be available on the website until the submission is released again. Please contact the EGA Helpdesk if you require further assistance.

  Documentation submission/metadata/submission/EGA_webin

• Influence of the Microbiome on Epigenetic Mechanisms in IBD

  Live CD4 T cells were sorted from inflamed and non-inflamed tissue samples of IBD patients or from healthy and IBD blood samples. ATAC-Seq libraries were generated from live CD4 T cells sorted from i) inflamed and non-inflamed tissue samples, ii) healthy and IBD blood samples, or from iii) CD4 T cell subsets polarised from healthy blood samples. After isolating crude nuclei, live CD4+ T cells were treated with Tagment DNA buffer and Tagment DNA Enzyme (Nextera DNA Library Prep Kit, Illumina), and then the DNA was purified by MinElute PCR Purification Kit (Qiagen). Transposed DNA fragments were amplified using specific adapters followed by purification with MinElute PCR Purification Kit (Qiagen). Fragments from 240-360pb were selected in the PippinHT system (Sage Science). The quality of the library and its DNA concentration were assessed by Bioanalyzer instruments (Agilent Technologies) and ultimately submitted for sequencing using Illumina HiSeq 2500 sequencer, V4 chemistry. On the other hand, single cell RNA-Seq libraries were generated exclusively from inflamed and non-inflamed tissue samples of Crohn’s disease patients. Briefly, live CD4 T cells were captured and encapsulated before cDNA amplification using the 10X Genomics Chromium Platform. Samples were prepared as outlined by 10x genomics Single Cell 3’ Reagent Kits v2 user guide. Samples were sequenced on a HiSeq 2500 with the following run parameters: Read 1 – 26 cycles, read 2 – 98 cycles, index 1 – 8 cycles.

  Dataset EGAD00001011066

• California Pacific Medical Center Research Breast Health Cohort

  Description of Cohort: The California Pacific Medical Center (CPMC) Breast Health Cohort is a cohort study based at CPMC and is linked to the San Francisco Mammography Registry, one of the sites of the NCI-funded Breast Cancer Screening Consortium (U01CA063740). CPMC is a community hospital in San Francisco, which has one of the highest volumes for mammography in San Francisco. Between September 2004 and June 2007, &gt;90,000 mammograms were performed at CPMC. The CPMC breast health cohort collects demographic and risk factor data on women receiving mammography through participation in the San Francisco Mammography Registry, as part of the Breast Cancer Screening Consortium (U01CA063740). The SFMR database collects information from all sources, including a questionnaire on demographic and risk factor information, the clinical results of the breast examination, the measures of breast density by Dr. John Shepherd and the women who agreed to donate a blood sample. By merging these various sources of information we have very efficiently developed a large sample of women who have donated blood and have had a measure of mamographic density. Blood Collection: Dr. Steve Cummings is leading an effort to collect and archive blood samples from women who are receiving mammography screening. All women who are sent for a screening mammogram at CPMC are considered eligible. Since the cohort began collecting blood samples in July 2004 until June 2007, samples have been collected from over 11,000 women. Measurement of Breast Density: Dr. John Shepherd is currently measuring breast density in a large fraction of the cohort using an automated approach with single X-ray absorptiometry. Dr. Shepherd has established a link with the CPMC mammography center that allows him to collect routine digital mammography information. Using the data from the mammogram, Dr. Shepherd and his group have developed the single X-ray absorptiometry (SXA) technique for measuring density which is described in more detail below. The table demonstrates the distribution of demographic variables and some breast cancer risk factors of women who donated blood and had a breast density measurement in the CPMC breast health cohort. Nearly 80% of the participants are Caucasian and most of the women are post-menopausal with a median age of ~52. Since it will be difficult to accrue a large enough sample from each ethnic group, our study will focus only on Caucasian women. Table: Demographic variables, reproductive history and family history of breast cancer among 2962 women participating in the CPMC cohort study who contributed blood samples between 1994-1997. Variable Median/Percentage Age (Median/IQR) 52 (46-59) Ethnicity Caucasian/White 0.76 Asian/Pacific Islander 0.141 Hispanic 0.029 Mixed Race/Ethnicity 0.039 African American/Black 0.022 American Indian 0.001 Other 0.009 First degree relative with breast cancer 0.17 Age at first birth Nulliparous 0.39 Age&lt;20 0.043 Age&gt;40 0.032 Age&lt;30, &#8805;20 0.251 Age&gt;30, &#8804;40 0.282 Measurement of Breast Density in Cohort: Measurement of breast density is accomplished using an automated technique for all mammograms obtained by Dr. Shepherd using Single X-Ray absorptiometry (SXA). SXA measurement of breast density is done on approximately 30% of all screening mammograms. Below we describe the method for measurement of breast density by SXA by Dr. Shepherd&#39;s group and its validation and association with breast cancer. As we demonstrate below, breast density, as measured by SXA, is an automated, highly reproducible measure of the density of breast tissue and is associated with breast cancer risk. SXA for Quantifying Breast Density: Single x-ray absorptiometry (SXA) was initially developed for measuring bone density. SXA can determine the fraction of each of two densities simultaneously using the fact the sample is a constant thickness, the thickness in known, and the total attenuation is known. In applying this technique to breast density, we assume a two compartment model: fat and non-fatty (fibroglandular tissue). We use a reference material composed of various concentrations of two materials: one which is the same density as fat and another which is the same density as fibroglandular tissue. The reference material (phantom) is placed in the X-ray field with each mammogram. We have been able to implement this in a way that is unintrusive to the patient and technologist at CPMC. Assuming this two-compartment model and a constant known breast thickness, we can then calculate the percent density at any region of the breast based on the assumption that % pixel grey-scale is proportion to the mass fractions of breast fat and lean tissue. If reference materials (a phantom) of fat and fibroglandular tissue are imaged with the patient&#39;s breast and the reference materials have the same thickness as the patient&#39;s breast, then the breast&#39;s grey-scale values can be converted to fat/fibroglandular mass fractions by interpolating between those two references. The total percent density is found by averaging the volume fraction over all breast pixels. The phantom being used for breast density assessment at CPMC began to be used in September 2004. The phantom does not have to be manipulated by the technologist and stays attached on the mammography device during standard craniocaudal (CC) views. Thus it creates minimal to no interference with the clinical mammogram. Reproducibility of breast density measures: Traditional measures of mammographic density require some human interpretation. A human reader outlines the area perceived to be dense and a computer then calculates the percent area outlined as a percent of the entire image. Thus, while traditional mammographic density is associated with breast cancer risk, it has some limitations. In a study by Drs. Shepherd, Kerlikowske, et al., the correlation coefficient (Pearson&#39;s R) between different readers was 0.8-0.9. In contrast to the traditional mammographic density measurement, the SXA measurement is fully automated and, therefore, the reproducibility of the measurement is higher. Dr. Shepherd and colleagues have performed a replication study of SXA as a measurement of breast density. They have estimated the correlation coefficient of the SXA measurement of breast density to be &gt;0.98. Thus, as expected for an automated measure, SXA is a highly reproducible measure of mammographic breast density. Drs. Shepherd and Kerlikowske have recently analyzed the association between breast cancer risk and breast density as measured by SXA (Shepherd et al., Cancer Epi Biomarkers and Prev, 2011, PMID: 21610220). They found that women in the highest quintile of % volumetric density had an odds ratio of 4.1 (95% CI: 2.3 - 7.2) for breast cancer risk compared to women in the lowest quintile of volumetric density. Thus volumetric density appears to be a highly reproducible, automated measure of breast cancer.

  Study phs000395

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp