Search Results - EGA European Genome-Phenome Archive

The Finland-United States Investigation of NIDDM Genetics (FUSION) Tissue Biopsy Study

The Finland-United States Investigation of NIDDM Genetics (FUSION) study is a long-term effort to identify genetic variants that predispose to type 2 diabetes (T2D) or that impact the variability of T2D-related quantitative traits (QTs). Most of the variants associated with T2D and related traits (glucose and insulin, anthropometrics, lipids) through genome-wide association studies (GWAS) occur in non-coding regions, suggesting a strong regulatory component to disease susceptibility. Regulatory element activity is often tissue-specific, which further complicates discovery of the causal/functional variation. Therefore, there is a critical need to identify the appropriate cell type, regulatory elements, target genes, and causal variants(s) in T2D-relevant tissues. We hypothesize that a subset of T2D and related variants alter gene expression regulation in skeletal muscle and adipose tissue - two major insulin target tissues and play key roles in insulin resistance. To that end, our study contains a comprehensive survey of genomics, epigenomics and transcriptomics in skeletal muscle and adipose tissue from individuals with glucose tolerance categories ranging from normal to T2D.For this FUSION Tissue Biopsy Study, we obtained RNA-Seq, microRNA (miRNA)-Seq, and DNA methylation (methyl)-Seq data on biopsy samples from 331 individuals from across the range of glucose tolerance: 124 normal glucose tolerance (NGT), 77 impaired glucose tolerance (IGT), 44 impaired fasting glucose (IFG), and 86 newly-diagnosed T2Ds. Participants completed two study visits, two weeks apart. First visits comprised most of the clinical phenotyping, including four-point OGTT (fasting, and 30, 60, and 120 minute post-load); BMI, WHR; lipids; blood pressure; and many other variables. Participants also completed FUSION health history, medication, and lifestyle questionnaires. On the second visit, we obtained ~250mg vastus lateralis skeletal muscle, ~750mg abdominal subcutaneous adipose, and a ~5x15mm section of abdominal skin. Visits were completed in March 2013. RNA isolation is ongoing in the Collins laboratory at the NIH, RNA and miRNA sequencing at the NIH Intramural Sequencing Center (NISC), and genotyping at the Center for Inherited Disease Research (CIDR). Individual-level data is available here for the 306 individuals who consented to data deposit. To focus on evaluation of gene expression and its regulation in skeletal muscle, we analyzed mRNA extracted from vastus lateralis skeletal muscle obtained from 271 of the 331 individual subjects from Finland, along with genome-wide genotypes. Individual-level data is available here for the 250 subjects who consented to the use of their data.Release phs001048.v2.p1 adds muscle data for an additional 42 subjects and data from adipose tissue for 276 subjects. Total RNA was isolated using Trizol extraction in the Collins laboratory at the NIH. The mRNA was poly-A selected, 24-plex libraries were generated using the Illumina TruSeq directional mRNA-seq library protocol and RNA sequencing was performed on HiSeq2000 sequencers using 101bp paired-end reads at NISC. miRNA libraries were prepared from total RNA from 296 muscle and 270 adipose samples, pooled and sequenced 50bp single-end reads on Illumina HiSeq2500. Data for 272 muscle and 251 adipose samples are available here for individuals with consent for data deposit. DNA was extracted from blood in the Collins laboratory, and genotyping on the Illumina Omni2.5M array was performed at CIDR. Genotypes were imputed using the HRC 2016 reference panel. In order to assess regions of open chromatin in skeletal muscle, we obtained muscle tissue from a commercial provider to perform ATAC-seq; these samples were sequenced at the University of Michigan DNA Sequencing Core.Release phs001048.v3.p1 adds single-nucleus (sn) RNA-seq and ATAC-seq data in 287 skeletal muscle samples out of the original 331 individuals. Individual-level data is available here for the 265 subjects who consented to the use of their data. The frozen tissue biopsy samples were processed in ten batches, each consisting of 40-41 samples. These batches were organized using a randomized block design to protect against experimental contrasts of interest including cohort, age, sex, BMI among others. Samples in each batch were pulverized, pooled together followed by nuclei isolation. The nuclei were processed on the 10X Genomics Chromium platform separately for snATAC-seq and snRNA-seq (v. 3.1 chemistry for snRNA-seq).Release phs001048.v4.p1 adds additional phenotypes and provides some corrections to several previous phenotypes.

Study phs001048

Disease Variant Landscape of a Large Multiethnic Population of Moyamoya Patients by Exome Sequencing

We report a significant advance in Moyamoya disease (MMD) research through our unique access to a large MMD patient population combined with high depth exome sequencing and bioinformatics. We confirm a reported RNF213 founder mutation (FM), provide evidence for its ethnic specificity and identify novel variants in other genes that associate with Caucasian and non-RNF213 FM MMD. This work has a broader impact in vascular research by highlighting novel genetic aspects of cerebrovascular disease. Moyamoya Disease (MMD) is a rare cerebrovascular disorder characterized by unilateral or bilateral progressive stenosis or occlusion of the internal carotid artery, with frequent involvement of the anterior cerebral artery and the middle cerebral artery (MCA). Fragile collateral vessels subsequently develop and are particularly prone to hemorrhage. MMD patients are usually diagnosed angiographically following presentation of developmental delays, seizures, migraines, ischemia, and/or hemorrhage. The most common approach to re-establish normal blood flow is bypass surgery. While some progress has been made in identifying disease-associated genes, the underlying disease biology is not well understood. Moyamoya disease (MMD) is a rare cerebrovascular disease. Our unique access to a large MMD patient population combined with high depth exome sequencing and bioinformatics has led to a significant advance in the field. We confirm a reported RNF213 founder mutation (FM), provide evidence for its ethnic specificity and identify novel variants in other genes that associate with Caucasian and non-RNF213 FM MMD. This work has a broader impact in vascular research by highlighting novel genetic aspects of cerebrovascular disease. The 125 ethnically diverse, unrelated MMD patients were matched based on sex and broad ethnic category to 125 controls. Control DNA from the 1000 Genomes project was used to design a control Library by Personalis. 125 controls were selected from this Personalis Control DNA Library for our study. (The 1000 Genomes Project Consortium 2012). Genomic DNA was extracted using the Gentra Puregene kit (Qiagen, Valencia, CA). Libraries were prepared from approximately 3 µg of high quality genomic DNA (50-200 ng/µl) using Illumina TruSeq Genomic DNA High throughput Sample Prep Kits (Illumina, San Diego, CA) and exome enrichment (targeting 62Mb) was accomplished using the TruSeq Exome Target Enrichment kit (Illumina, San Diego, CA), all according to manufacturer's protocols. Target enrichment validation was confirmed by determining the concentration of the library by PicoGreen-based quantitation. Library yields ranged from 100-1000ng of DNA, a portion of which was run on the Bioanalyzer HS DNA chip (Agilent, Santa Clara, CA), with an average size of 300-550nt for DNA fragments. Exome Sequencing. Sequencing was performed using Illumina Hiseq2000 or HiSeq2500 sequencers with single lane, paired-end 2X100bp reads. DNA fragments were generated and amplified using Clonal Single Molecule Array technology (Illumina, San Diego, CA). The sequences were determined using the Clonal Single Molecule Array and Sequencing-by-Synthesis using Illumina's instrumentation and Reversible Terminator Chemistry. Each sequencing lane interrogated the DNA sequences of a pool of 3 individual sample libraries each carrying a unique index. Sequencing reads of at least 2x100bp in length for a total of approximately 8 Gb of sequence data were generated for each sample.

Study phs001700

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 International Consortium for Prostate Cancer Genetics Genome Wide Association Study of Familial Prostate Cancer

Initially, the ICPCG focused largely on high-risk prostate cancer pedigrees using linkage analysis. However, association studies have also been informative to find prostate cancer susceptibility variants in the genome. We hypothesize that genome-wide (GW) association studies of familial cases of prostate cancer will have the power to identify rarer and perhaps less penetrant risk variants associated with prostate cancer than have been identified to date. Our approach will be to examine evidence for association in selected, independent cases from high-risk pedigrees; we hypothesize that they represent a more homogeneous set of cases with potentially different associations. Use of the 5M plus exome SNP platform will allow us to include in our search more rare variants in our search than have ever been investigated for prostate cancer. Aim 1. Identify a set of independent prostate cancer cases selected from ICPCG high-risk prostate cancer pedigrees that have 3 or more related prostate cancer cases and have an average age at diagnosis ≤ 75 years. Identify appropriate matched controls from participating ICPCG groups/ populations. Aim 2. Perform GW SNP genotyping with the Illumina 5M plus exome SNP set on the set of independent prostate cancer cases and controls described in Aim 1. Aim 3. Perform association analyses appropriately matching controls for different ICPCG populations and groups. There will be a two-stage design for confirmation. Aim 4. Test reported associations using the extensive sample set available to us by collaboration with the PRACTICAL consortium that has access to 50 000 DNA samples from 34 groups internationally (over 7,000 of whom are positive for prostate cancer family history).

Study phs000733

Department of Human Genetics, Radboud University Nijmegen Medical Centre, Data Access Committee

Dac EGAC00001000076

MOSAIC Window DLBCL Data

This dataset will include Spatial Transcriptomics from the 10x Genomics Visium SD technology, Single-Cell RNA-Seq from the 10x Genomics Chromium Flex protocol, Bulk RNA-Seq (sequenced on Illumina), WES (sequenced on Illumina), H&E, and Clinical data from 10 DLBCL patients. For Visium and Chromium data we are sharing the outputs of respectively Space Ranger and Cell Ranger. For Bulk RNA-Seq we are including processed files such as counts.tsv, FPKM.tsv, fusion_genes.tsv, TPM count matrix.tsv, DESeq2 count matrix.tsv, multiqc_report. For WES, we are sharing the presence or absence of single nucleotide variants (SNVs), small insertions and deletions (indels), and copy number variants (CNVs).* Researchers from private or public institutions outside the MOSAIC Consortium will be able to apply to access this data and, pending approval, use the data for their research.

Dataset EGAD50000001702

MOSAIC Window Ovarian Data

This dataset will include Spatial Transcriptomics from the 10x Genomics Visium SD technology, Single-Cell RNA-Seq from the 10x Genomics Chromium Flex protocol, Bulk RNA-Seq (sequenced on Illumina), WES (sequenced on Illumina), H&E, and Clinical data from 15 Ovarian patients. For Visium and Chromium data we are sharing the outputs of respectively Space Ranger and Cell Ranger. For Bulk RNA-Seq we are including processed files such as counts.tsv, FPKM.tsv, fusion_genes.tsv, TPM count matrix.tsv, DESeq2 count matrix.tsv, multiqc_report. For WES, we are sharing the presence or absence of single nucleotide variants (SNVs), small insertions and deletions (indels), and copy number variants (CNVs).* Researchers from private or public institutions outside the MOSAIC Consortium will be able to apply to access this data and, pending approval, use the data for their research.

Dataset EGAD50000001704

MOSAIC Window Mesothelioma Data

This dataset will include Spatial Transcriptomics from the 10x Genomics Visium SD technology, Single-Cell RNA-Seq from the 10x Genomics Chromium Flex protocol, Bulk RNA-Seq (sequenced on Illumina), WES (sequenced on Illumina), H&E, and Clinical data from 10 Mesothelioma patients. For Visium and Chromium data we are sharing the outputs of respectively Space Ranger and Cell Ranger. For Bulk RNA-Seq we are including processed files such as counts.tsv, FPKM.tsv, fusion_genes.tsv, TPM count matrix.tsv, DESeq2 count matrix.tsv, multiqc_report. For WES, we are sharing the presence or absence of single nucleotide variants (SNVs), small insertions and deletions (indels), and copy number variants (CNVs).* Researchers from private or public institutions outside the MOSAIC Consortium will be able to apply to access this data and, pending approval, use the data for their research.

Dataset EGAD50000001706

Reference Standards for Mosaic Variant Detection

After conception, postzygotic mutations continuously occur throughout life in humans, causing somatic mosaicism in an individual. The variant type, time of origination, and locations of the mosaic mutations result in unique mosaic patterns in a combinatorial manner and further affect phenotypes, including various noncancerous diseases. Several efforts have, thus, been made to identify the mutational landscape and mechanisms underlying the mosaic mutations. From a technical aspect, the accurate detection of mutations is at the core of the mosaicism research, and the construction of a standard reference is a critical first step to serve as the basis for analytical validation and benchmarks for germline and somatic mutation detection. Furthermore, a reference standard for mosaic mutations is urgently needed to enable more advanced research.Herein, we generated robust, large-scale, and cell line mixture-based reference standards that contain abundant mosaic SNVs and INDELs along with wild-type sites and germ line variants. Moreover, the whole reference standard set mimics the cumulative aspect of mosaic variant acquisition in the early developmental stage through a progressive cell line mixing with confirmed genotypes. It can be used for optimizing the current use of mosaic variant detection strategies, as well as developing algorithms for future improvements.We previously generated an NCBI BioProject (PRJNA758606) to release much of these data. Only the data that are subject to authorized access constraints have been included in this submission to dbGaP. The two data sources are thus, complementary to each other.

Study phs003399

Exploration of CNV’s and SNV’s in cancers with well-known genetic rearrangements: Identification of additional genetic changes in rearrangements-driven cancer

Specific cancers are well known to have specific gene rearrangements. Representative cancer is chronic myeloid leukemia (CML) which is famous for BCR/ABL gene rearrangements. By the way, also genetic rearrangements are not infrequently found in acute leukemia, and those include CBFB/MYH11 rearrangements, PML/RARA rearrangements, AML/ETO rearrangements, and BCR/ABL rearrangements. The situation is same is for lung adenocarcinoma of non-smokers and prostate cancers, and ALK and RET gene rearrangements are recently found. However, not all these rearrangements are sufficient to develop cancer, and it is suggested that some genetic aberrations are required for the development and progression of cancer in addition to these genetic rearrangements. In this study, we have a plan to explore the existence of additional genetic changes including single nucleotide variants (SNV’s) and copy number variations (CNV’s) in cancers with specific genetic rearrangements so as to define additional genetic changes that confer full oncogenic potential to cancer cells. So as to look at SNV’s and small indels, we are going to use whole exome sequencing (WES) data. And as for CNV’s, we are going to use array-CGH data. Also, to check the functionality of these genetic changes, we are going to use whole transcriptome data (WTS). In addition, in samples with whole genome sequencing (WGS ) data, we are going to explore genetic changes in intronic regions also. In fact, we sequenced 10 AML samples which are known to have specific genetic rearrangements. Analysis of these WGS, WES and WTS data are under the way. If we have a chance to access WES, array-CGH and WTS data of other cancer samples with specific genetic rearrangements, we would be able to compare additional genetic changes required for oncogenesis in cancer cells with various genetic rearrangements. We hope this result will enlighten our understanding of cancer genetics further.

Study EGAS00001000673

Single cell transcriptional characterization of human megakaryocyte lineage commitment and maturation

Single cell RNA-sequencing of sternal bone marrow reciding Hematopoietic Stem Cells (HSCs) and Megakaryocytes (MKs) from individuals undergoing elective open heart valve replacement. HSCs were defined as Lineage-, CD34+, CD38-, CD45RA-, CD90+, CD49f+ cells. MKs where CD41a+, CD42b+ and ploidy was determined with Hoechst. A sternal bone marrow scraping was taken directly following median sternotomy using a Volkmann’s spoon. The sample was collected into an EDTA Vacutainer tube containing 1.8mg/ml EDTA. 4mL of Dulbecco’s phosphate buffered saline (PBS, Sigma) containing 10% human serum albumin (HSA, Gemini Bio Products) was added and the whole volume was resuspended by pipetting 2-3 times. The sample was then put on metallic thermal beads (ThermoFisher Scientific) at a temperature between 0-4°C and transported to the University of Cambridge for further processing. For HSC isolation the cells were stained with the following antibody cocktail: PECy5 conjugated anti-lineage specific antibodies: CD2 (BD), CD3 (BD), CD10 (BD), CD11b (BD), CD11c (BD), CD19 (BD), CD20 (BD), CD56 (BD), biotinylated CD42b (Pab5, NHS Blood and Transplant, International Blood Group Reference Laboratory [IBGRL]), biotinylated GP6 (Pab5, NHS Blood and Transplant, International Blood Group Reference Laboratory [IBGRL]) used in combination with PECy5 conjugated streptavidin (Biolegend). Alexa Fluor 700 conjugated anti-CD34 (BD), PerCP-Cy5.5 conjugated anti-CD38 (BD), Pacific Blue conjugated anti-CD45RA (Invitrogen), PECy7 conjugated anti-CD90 (BD),PE conjugated anti-CD49f (BD). After staining cells were kept at 4°C before sorting using a FACS Aria Fusion flow sorter (BD). Single HSCs defined as Lineage-, CD34+, CD38-, CD45RA-, CD90+, CD49f+ cells were sorted by FACS directly into individual wells of a 96-well plate. Index sort data was collected for each single cell. For MK isolation the cells were stained for surface MK markers with mouse anti-human CD41a APC conjugated antibody (BD) and mouse anti-human CD42b PE conjugated antibody (BD) and for ploidy analysis with 1ug/ml Hoechst 33342 (Invitrogen). After incubation at 37°C for 30 minutes, the cells were kept at 4°C before sorting using a FACS Aria Fusion flow sorter (BD). Single cells and MK pools of 20 cells were sorted by FACS according to ploidy level using a 100uM nozzle directly into individual wells of a 96-well plate. cDNA synthesis and poly(A) enrichment was performed following the G&T-seq protocol (Macaulay et al. 2015), a variation of the Smart-seq2 protocol1. ERCC spike-in RNA (Ambion) was added to the lysis buffer in a dilution of 1:4,000,000.

Dataset EGAD00001006677

Guiding Evidence Based Therapy Using Biomarker Intensified Treatment in Heart Failure (GUIDE-IT-BioLINCC)

Accessing Data: Please refer to “Authorized Access” below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP.Objective: To determine whether an amino-terminal pro-B-type natriuretic peptide (NT-pro-BNP)-guided treatment strategy improves clinical outcomes vs usual care in high-risk patients with heart failure (HF) and reduced ejection fraction (HFrEF).Background: Heart failure is a common disorder. Standard treatment for HF includes diuretics to control fluid, and drugs called "neurohormonal antagonists" (such as beta-blockers and ACE-inhibitors) to help the heart work more efficiently. The natriuretic peptides, specifically NT-pro-BNP, are biomarkers that reflect HF severity and are significantly associated with adverse outcomes in HF. Smaller studies have evaluated adjusting HF therapy based on natriuretic peptide levels (“guided therapy”) with inconsistent results.Participants: A total of 894 participants were enrolled at 45 sites in the United States and Canada, with 446 randomized to the NT-pro-BNP-guided strategy treatment group and 448 randomized to the usual care treatment group.Design: GUIDE-IT was a multicenter randomized clinical trial with participants randomized to either the NT-pro-BNP-guided therapy strategy or usual care. Given the nature of the study intervention, treatment assignment was not blinded. For participants randomized to the NT-pro-BNP-guided strategy, clinicians were instructed to titrate HF therapy to target an NT-pro-BNP level After an initial visit at 2 and 6 weeks, visits occurred every 3 months throughout the remainder of the study. After therapy adjustment for HF (whether driven by NT-pro-BNP levels or clinical reasons), participants had a 2-week follow-up visit for reassessment. All participants in either group also had blinded NT-pro-BNP concentrations measured in a core laboratory at each study visit. The primary end point was the composite of time-to-first HF hospitalization or cardiovascular mortality. Secondary end points included all-cause mortality, total hospitalizations for HF, days alive and not hospitalized for cardiovascular reasons, the individual components on the primary end point, and adverse events. Conclusions: The guided strategy intervention was stopped in July of 2016 (median follow-up of 15 months) after the study met prespecified inefficacy criteria. Compared to usual care, a strategy of NT-pro-BNP-guided therapy was not more effective in improving time-to-first HF hospitalization or cardiovascular mortality in high-risk participants with HFrEF.

Study phs003621

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

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

Cell and Circuit-Specific Exploration of HIV Neurogenomics in Context of Opiate and Cocaine Misuse

Utilizing frozen postmortem brain tissue from the Manhattan HIV Brain Bank, we performed cell-type-specific, genome-wide sequencing of three different types: 1) single-nucleus RNA-sequencing (snRNA-seq), 2) in situ Hi-C, and 3) HIV integration site sequencing (IS-seq). We assayed tissue from three different donor types: 1) HIV-uninfected control (HIV-), HIV-infected (HIV+), and HIV-infected with HIV encephalitis (HIVE), who served as a positive control for active CNS viral infection. The diagnosis of HIVE was made by a board-certified neuropathologist on routine histopathology, based on the presence of a microglial nodule encephalitis with characteristic multinucleated syncytial cells and staining for HIV p24 antigen. Other HIV-infected individuals (the HIV+ group) did not have this histologic evidence of active HIV brain replication, and were variable with regard to cART status and virologic control prior to death. Donor characteristics, including ante-mortem plasma HIV loads, CD4 counts, and cART status, were documented. Quality controls were used for each assay: For snRNA-seq we applied filters to remove low quality nuclei from analysis and performed experiments in which mouse tissue was mixed with human tissue to determine a reliable HIV read count threshold. For Hi-C, we used paired HIV- and HIVE samples and processed all samples in parallel, at the same time. Correlation analysis was used to ensure biological replicates were aligned. For IS-seq, each time the assay was run, a positive and negative control were included. This allowed us to ensure a lack of contamination in IS-seq libraries and that, when a particular sample failed to yield library, this was due to low levels of HIV rather than a failure of the assay. Altogether, we built an integrative dataset from 79 sequencing files, including snRNA-seq, and cell type specific Hi-C, IS-seq, and ChIP-seq datasets. Human autopsy brain samples were collected by the Manhattan HIV Brain Bank (MHBB, U24MH100931), using protocols under the supervision of the Icahn School of Medicine at Mount Sinai (ISMMS) Institutional Review Board. Written informed consent was obtained either from decedents or their primary next of kin. Major Findings: Reorganization of open/repressive (A/B) compartment structures in HIVE microglia encompassing 6.4% of the genome was linked to transcriptional activation of interferon (IFN) signaling and cell migratory pathways and was partially recapitulated by IFN-gamma stimulation of cultured microglia. In contrast, decreased expression and repressive compartmentalization of genes regulating neuronal health and signaling was seen in both HIVE and HIV+ microglia. IS-seq recovered 1,221 integration sites in the brain that displayed distinct genomic patterns as compared to peripheral lymphocyte integration and were enriched for chromosomal domains newly mobilized into a permissive chromatin environment in HIVE microglia. Viral transcription occurred in a subset of highly activated microglia comprising 0.003% of all nuclei in HIVE brain. Our findings point to a disruption of microglia-neuronal interactions in the HIV infected brain and an interrelation of retroviral integration and expression with interferon-associated remodeling of the microglial 3D genome during progression to HIVE. Search terms: HIV, postmortem brain, microglia, substance abuse, viral integration, chromosomal conformation capture, Hi-C, chromatin, single nuclei RNA-seq, Irf8, NeuN, HIV encephalitis, neuron-microglia interaction, cytokine

Study phs003080

The EGA Helpdesk team: 2025 in review and what we are building next

Behind every dataset submitted, every access request processed, and every technical question answered, there is a team working quietly to keep things moving: the Helpdesk (HD). With the onset of 2026, this feels like the right moment to look back on what 2025 has been like for the HD team: the challenges we faced, how we adapted, and where we're heading next. Why the Helpdesk matters to EGA The EGA Helpdesk is more than a support channel. It plays a key role in maintaining trust in the EGA ecosystem. By supporting data submitters, researchers, Data Access Committees (DACs), and institutional partners, the HD helps ensure that data can flow securely, efficiently, and reliably. When issues arise, the Helpdesk is often the first place where their impact is felt and addressed. In that sense, the HD sits at the intersection of technology, policy, and people. One Helpdesk, two locations, one shared mission The EGA Helpdesk is a joint, distributed team working closely across two locations: CRG (Barcelona, Spain) and EMBL-EBI (Cambridge, UK). Although we are based in different institutions, we operate as a single Helpdesk, with shared workflows, priorities, and responsibility towards users. At CRG, the HD team is formed by: Andrea Max Àlex and me At EMBL-EBI, we work closely with: Silvia Coline Aravind What defines us as a team is simple: we work user-first, even under pressure. In a highly technical environment, clarity, empathy, and consistency matter just as much as tools and processes. A close collaboration across sites is essential to making that happen. What does the EGA Helpdesk do? The HD supports users across the full lifecycle of data in EGA. This includes: Data submissions, uploads, and encryption workflows. Data access requests and permissions. Questions around policies, consent, and data usage. Technical and system-related issues. Coordination between users, internal teams, and external partners. 2025: growth, change, and recalibration 2025 was a year of growth, but not always a predictable one. Early in the year, several technical and system-related challenges required us to adjust our original plans. Priorities shifted, timelines changed, and some improvements had to be rethought. For the HD team, this is often the hardest part of the job: we see delays through the eyes of users and understand the real impact they can have on ongoing research. One of the key lessons from 2025 was that stability is not only a technical challenge, but also an organisational one. Teamwork proved to be essential: anticipating peak periods, sharing context early, and coordinating closely across teams made a tangible difference. When things became complex, working together across roles and locations was what allowed us to keep moving forward. In 2025, the Helpdesk received 5.313 tickets and resolved 5.511 requests, reflecting both increased adoption of EGA and the team’s ability to absorb higher demand. At the same time, demand continued to grow. Compared to 2024, ticket creation increased by over 6%, while resolution capacity grew by more than 11%. The team not only kept up with incoming requests but also resolved part of the accumulated backlog, finishing the year having solved more tickets than were created. The real challenge of 2025 was not overall performance, but how the workload was concentrated during peak months. Seasonality and demand spikes placed pressure on the system, even while overall efficiency remained strong. On a team level, 2025 was also a year of transition. I joined the HD leadership role in January 2025, stepping into a period of change and rapid learning. Later in the year, in October, we said goodbye to Raül, and in January 2026, we welcomed Àlex, strengthening the team for the next phase. What users needed most in 2025 While requests vary widely, some themes stood out throughout the year: Support with data submissions and uploads Data access requests and permissions Technical and system-related issues As EGA matures, day-to-day operations have become more complex. Many long-running tickets are not delayed due to a lack of follow-up, but because they depend on external approvals, cross-institutional coordination, or multi-step processes. Understanding these patterns helps us focus not just on resolving tickets, but on improving how work flows through the system. Looking ahead to 2026 With a reinforced team and clearer insights from 2025, our focus for 2026 shifts from throughput to flow. Key priorities include: Strengthening our web content and documentation Reducing structural backlog Improving cross-team and cross-system coordination Anticipating peak demand earlier and planning capacity accordingly Challenges will continue to arise in 2026, as they always do. However, 2025 reinforced something important: a stable, empathetic, and well-aligned Helpdesk team is essential to supporting EGA's mission at scale. Supporting users well means supporting research, and that remains at the core of what we do.

Blog ega-helpdesk-team-2025-in-review-and-upcoming-improvements

REDS-IV-P Epidemiology, Surveillance and Preparedness of the Novel SARS-CoV-2 Epidemic (RESPONSE)

Leveraging access to the blood supply and blood donors, the REDS-IV-P program began conducting the RESPONSE study (REDS-IV-P Epidemiology, Surveillance and Preparedness of the Novel SARS-CoV-2 Epidemic) in early 2020 in order to 1) evaluate if SARS-CoV-2 RNA was found in blood donations in the U.S. using an assay that could potentially be used to screen the blood supply if evidence of SARS-CoV-2 transfusion-transmission became apparent 2) conduct serosurveys using optimized assays/algorithms to monitor antibody reactivity in blood donor populations over time, 3) enroll SARS-CoV-2 positive donors and others into a longitudinal cohort study to answer fundamental questions about the evolution of viremia and immune responses, and 4) establish a sharable biorepository that includes specimens collected early on in the infection and potentially large volumes of plasma from infected/convalescent donors.Screening for SARS-CoV-2 RNAemia was completed using a SARS-CoV-2 nucleic acid test (NAT) performed on retained blood donor minipool samples from six geographic regions in the US. The study also included serosurveillance (i.e. testing for antibody directed against the SARS-CoV2 spike protein) of donations from the same six regions to document accruing seroincidence in blood donor populations and to project these rates in the general population. To enrich for donors with acute SARS-CoV-2 infection, another part of the study focused on donors reporting post-donation information (PDI) consistent with COVID-19 by testing plasma from all available PDI donations for SARS-CoV-2 RNA by NAT. Subjects who were diagnosed with COVID-19 based on PDI reports or who tested positive by SARS-CoV-2 NAT on index donation plasma were enrolled into a longitudinal follow-up study which collected multiple samples for up to one-year post-infection. The longitudinal follow-up study also enrolled community members who reported a new positive SARS-CoV-2 NAT test in the prior 7-14 days. The specific aims of the RESPONSE study were to: Establish the incidence of SARS-CoV-2 RNAemia in blood donations from the American Red Cross (ARC) regions in Los Angeles, Boston, and Minneapolis metropolitan areas, Bloodworks Northwest (BWNW), New York Blood Center (NYBC), and Vitalant San Francisco Bay Area, monthly between March and September of 2020 Conduct serosurveys to study antibody reactivity in same six areas as above monthly for March to August 2020 Document rates of Post Donation Information (PDI) reports to determine PDI rates relevant to SARS-CoV-2 clinical disease and test index donation plasma from PDI donors for SARS-CoV-2 RNA Enroll SARS-CoV-2 infected subjects into a longitudinal cohort study to answer fundamental questions on the evolution of viremia, early immune responses and waning of immunity over 3-12 months of follow-up Establish a sharable biorepository of samples from all of the above Aims for future research The data from Aims 3 and 4 above is being made available in BioData Catalyst.Biospecimens for these Aims are managed by Vitalant Research Institute (VRI). More information on biospecimens is available.

Study phs003578

Jackson Heart Study (JHS) Cohort

The Jackson Heart Study (JHS) is a large, community-based, observational study whose participants were recruited from urban and rural areas of the three counties (Hinds, Madison and Rankin) that make up the Jackson, MS metropolitan statistical area (MSA). Participants were enrolled from each of 4 recruitment pools: (1) random, 17%, (2) volunteer, 30%, (3) currently enrolled in the Atherosclerosis Risk in Communities (ARIC) Study, 31%, and (4) secondary family members, 22%. The final cohort of 5,306 participants included 6.59% of all African American Jackson MSA residents, aged 35-84, during the baseline exam (N-76,426, US Census 2000). Among these, approximately 3,600 gave consent that allows genetic research and deposition of data into dbGaP. Major components of three clinic examinations (see study history) include medical history, physical examination, blood/urine analytes, and interview questions on areas such as physical activity, stress, coping and spirituality, racism and discrimination, socioeconomic position, and access to health care. Extensive clinical phenotyping includes anthropometrics, electrocardiography, carotid ultrasound, ankle-brachial blood pressure index, echocardiography, CT chest and abdomen for coronary and aortic calcification, liver fat, and subcutaneous and visceral fat measurements, and cardiac MRI. At 12-month intervals after the baseline clinic visit (Exam 1), participants have been contacted by telephone to update information, confirm vital statistics, document interim medical events, hospitalizations and functional status, and obtain additional sociocultural information. Questions about medical events, symptoms of cardiovascular disease and functional status are repeated annually. Ongoing cohort surveillance includes abstraction of medical records and death certificates for relevant International Classification of Diseases (ICD) codes and adjudication of nonfatal events and deaths. CMS data are currently being incorporated into the dataset. Note: Regarding date variables warehoused in the Jackson Heart Study (JHS) Cohort on dbGaP, the coordinating center has developed an algorithm that will systematically review and de-identify any of the (nearly 100) date-related variable types stored in the data package. To simultaneously minimize (i) de-identifiability of the data and (ii) impact on analyses utilizing sensitive data elements, a participant-level random number was generated to avoid the necessity of sharing any potentially sensitive data. The coordinating center maintains an archived linkage of these data in their raw form and regularly reviews ad hoc requests to utilize the raw data on a project-by-project basis. The JHS Cohort is utilized in the following dbGaP substudies. To view genotypes, other molecular data, and derived variables collected in these substudies, please click on the following substudies below or in the "Substudies" section of this top-level study page phs000286 JHS Cohort. phs000402 ESP Heart GO JHS phs000498 JHS Allelic Spectrum Seq phs000499 JHS CARephs001069 MI Gen JHS phs001098 T2D GENES Exome Seq phs001356 Exome Chip phs002256 Cardiometabolic Renal Proteomics phs002369 Metabolomics Insulin Resistance

Study phs000286

Center for Craniofacial and Dental Genetics: Exome Sequencing of Orofacial Cleft Families

Orofacial Clefts (OFCs) are genetically complex structural birth defects caused by genetic factors, environmental exposures, and their interactions. OFCs are the most common craniofacial anomalies in humans. Affect about 1 in 800 newborns, OFCs are also one of the most common structural birth defects worldwide. OFCs can impose a substantial personal cost resulting from the associated emotional and financial burden. On average a child undergoes 6 surgeries, spends 30 days in hospital, receives 5 years of orthodontic treatment, and participates in ongoing speech therapy, leading to an estimated total lifetime treatment cost of about $200,000. Individuals born with an OFC have higher infant mortality (especially in developing countries with limited access to care), higher mortality rates at all other stages of life, increased incidence of mental health problems, and higher risk for other disorders (notably including breast, brain, and colon cancers). Prior genetic studies have focused on the contribution of common genetic variants through genome-wide linkage and association studies. These studies have revealed a significant etiologic heterogeneity. One promising approach to dissect the etiology of OFCs into focus on subclinical phenotypic features present in the non-cleft family members of affected individuals. These subclinical features are subtle phenotypic features that may represent mild manifestations of the same risk genes; thus, their inclusion in family-based studies may clarify the inheritance patterns in OFC families. In this project, we conducted whole exome sequencing in multiplex families with both overt OFCs and subclinical phenotypes to identify high-impact genes causing OFCs.

Study phs001675

Human Skin Cancer Atlas, Medical University of Vienna Data Access Policy

Cancer-associated fibroblasts (CAFs) play a key role in cancer progression and treatment outcome. Here, we elucidate the yet unresolved intra-tumoral CAF variety in three skin cancer types at molecular and spatial single-cell resolution in a large cohort. We show that two out of three CAF subtypes contribute to tumor immune surveillance with distinct mechanisms. Matrix CAFs (mCAFs) ensheath tumor nests and synthesize extracellular-matrix to prevent T cell invasion. Immunomodulatory CAFs (iCAFs), which express proinflammatory and immunomodulatory factors, are only detected in high abundance in aggressive tumors. Strikingly, iCAFs but not tumor cells are (apart from immune cells) the exclusive cell type producing chemokines and, thus, play a key role in immune cell recruitment and activation. Mechanistically, we show that cancer cells transform adjacent healthy fibroblasts into cytokine-expressing iCAFs, which subsequently recruit immune cells and modulate the immune response. In conclusion, targeting CAF variants holds promise for improved efficacy of immunotherapy.

Dac EGAC50000000154

Genetic Discovery and Application in a Clinical Setting: Continuing a Partnership (eMERGE Phase II)

The electronic Medical Records and Genomics (eMERGE) Network is a consortium of ten participating sites funded by the NHGRI to investigate the use of electronic medical record systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 19,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. The eMERGE Network brings together researchers with a wide range of expertise in genomics, statistics, ethics, informatics, and clinical medicine from leading medical research institutions across the country. Each center participating in the consortium is uniquely situated to provide critical resources to this highly collaborative and productive network. Each site combines a biobank or study cohort with extensive genomic data and access to clinical data derived from electronic medical records. Sites are geographically dispersed and have diverse patient populations, including two sites focusing specifically on pediatrics. The eMERGE Network is comprised of 9 sites and one coordinating center. Each site maintains its own biorepository where DNA specimens are linked to phenotypic data contained within EMRs. Children's Hospital of Pennsylvania, PI: Hakon Hakonarson, MD, PhD Cincinnati Children's Medical Center with Boston Children's Hospital, PI: John Harley, MD, PhD - CCHMC and Ingrid Holm, MD, MPH - BCH Geisinger Health System, PI: David Carey, PhD and Marc Williams, MD Group Health Cooperative with University of Washington, PI: Eric Larson, MD, MPH - GHC and Gail Jarvik, MD, PhD - UW Marshfield Clinic with Essentia Institute of Rural Health, PI: Catherine McCarty, PhD, MPH - Essentia and Murray Brilliant, PhD - Marshfield Mayo Clinic, PI: Christopher Chute, MD, DrPH and Iftikhar Kullo, MD Icahn School of Medicine at Mount Sinai, PI: Erwin Bottinger, MD Northwestern University, PI: Rex Chisholm, PhD and Maureen Smith, MS Vanderbilt University, PI: Dan Roden, MD eMERGE Coordinating Center - Vanderbilt University, PI: Paul Harris, PhD Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of red cell indices, white blood count (WBC) differential, diabetic retinopathy, height, serum lipid levels, specifically total cholesterol, HDL (high density lipoprotein), LDL (low density lipoprotein), and triglycerides, and autoimmune hypothyroidism as well as using the phenome-wide association study (PheWAS) paradigm to replicate and discover relationships between targeted genotypes with multiple phenotypes.

Study phs000948

Capturing the Genetic Diversity of the Himba Population

The Himba people are a semi-nomadic, Bantu-speaking pastoralist group from the northwestern Kunene region of Namibia. Because of their limited population size, restricted geographic distribution, and endogamy, founder populations represent an ideal system for genetic analyses due to reduction of the confounding environmental and cultural variables. The original study used genotype data and demographic interview data to understand family dynamics and ancestry in a population of Himba pastoralists. HLA allele calls and genome-wide methylation array data were later generated for a subset of the initial dataset for 2 additional studies. These 3 molecular datasets, available through dbGaP, are relevant to broader studies of ancestry, allele frequencies and the relationship of Himba to other ethnic groups in sub-Saharan Africa. The Himba population provides a unique opportunity to study questions regarding extra-pair paternity and mate selection because Himba culture allows both men and women, married and not, to take multiple partners. Previous estimates of extra-pair paternity rates in human populations have been very low, but these estimates lack global and cultural diversity in population representation. Thus, investigating the rate of extra-pair paternity in the Himba greatly aids in understanding the global variation in non-paternity rates among human populations. Saliva samples were collected from parents and children, and were genotyped on Illumina SNP array platforms (MEGAex and H3Africa). In total, 678 individuals' genotype array data are deposited. Paternity results were de-identified and protected by a double blind protocol (no researcher has full knowledge of individual paternity results). Due to the sensitive nature of this study, paternity assertions are not available for access. For a subset of 360 individuals, HLA class 1 (A, B, C) and class 2 (DPA1, DPB1, DQA1, DQB1, DRB1) genes were targeted for DNA sequencing using a probe-based capture method. HLA alleles at the four field resolution were determined from the sequence capture using the consensus calls obtained from two algorithms: NGSengine® 2.10.0 (GenDX, Utrecht, the Netherlands) and HLA Explore™ (Omixon Biocomputing Ltd. Budapest, Hungary). These data were used to investigate evidence for mate selection based on HLA dissimilarity in the Himba. Himba cultural norms permit concurrent arranged marriages and chosen sexual partnerships allowing us to directly test for evidence of disassortative mate selection based on HLA genotype. Due to the sensitive nature of this study, partnership data are not available for access.For a subset of 51 Himba individuals methylation array data was generated from the saliva-derived DNA. These data were generated in order to investigate the accuracy of epigenetic age predictors in this population and to construct population-specific epigenetic age predictors in a subsequent publication. Chronological ages are available for these 51 individuals.

Study phs001995

eMERGE: Northwestern (NUgene) WGS

The NUgene Project is a biorepository with longitudinal medical information from participating patients at Northwestern Medicine affiliated hospitals and outpatient clinics. Participants' DNA samples are coupled with data from a self-reported questionnaire (2 versions were used, 1 before and 1 after February 2006, both are included) and continuously updated data from our Electronic Medical Record (EMR) representing actual clinical care events. Northwestern has a state-of-the art, comprehensive inpatient and outpatient EMR system of over 3 million patients. NUgene has broad access to participant data for all outpatient visits as well as inpatient data via a consolidated enterprise data warehouse. NUgene participants consent to distribution and use of their coded DNA samples and data for a broad range of genetic research by third-party investigators. The electronic MedicalRecords and Genomics (eMERGE) Network is a consortium of 9 clinical sites with EMR linked DNA biobanks, including Northwestern University and its NUgene biobank, funded by the NHGRI (National Human Genome Research Institute) to investigate the use of electronic medical record systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 100,000 individuals using EMR-derived phenotypes and DNA from linked biorepositories. Using electronic phenotyping methods, the consortium has been and is using DNA samples from all participating sites to explore the genetic determinants of approximately 80 phenotypes, including both diseases and traits, for which the electronic phenotyping algorithms have or are being published on PheKB.org. Thus, for the eMERGE network, ~900 NUgene subjects were selected, as described in the study inclusion/exclusion criteria section below, to be genotyped using whole genome sequencing (WGS), for use in the eMERGE network as eMERGE subjects. The criteria used below were selected so that these subjects will likely meet the criteria to be cases and/or controls, of diverse races and/or ethnicities, for at least 1 of the ~80 phenotypes being studied within eMERGE, and could be recontacted for future research if needed.

Study phs001191

Hematopoietic Cell Transplant for Sickle Cell Disease (HCT for SCD)

The Center for International Blood and Marrow Transplant Research (CIBMTR) is a hematopoietic cell transplant registry that was established in 1972 at the Medical College of Wisconsin. The overarching goal of the registry is to study trends in transplantations and to advance the understanding and application of allogeneic hematopoietic cell transplantation for malignant and non-malignant diseases. Included in this dataset are children, adolescents and young adults with severe sickle cell disease who received an allogeneic hematopoietic cell transplant in the United States and provided written informed consent for research.Hematopoietic cell transplant for sickle cell disease is curative. Offering this treatment for patients with severe disease is challenging as only about 20-25% of patients expected to benefit have an HLA-matched sibling. Consequently, several transplantations have utilized an HLA-matched or mismatched unrelated adult donor and HLA-mismatched relative. Transplantation strategies have also evolved over time that has included transplant conditioning regimens of varying intensity, grafts other than bone marrow and novel approaches to overcome the donor-recipient histocompatibility barrier and limit graft-versus-host disease. The data that is available for sickle cell disease transplants have been utilized to report on outcomes after transplantation and compare outcomes after transplantation of grafts HLA-matched related, HLA-mismatched related, HLA-matched and HLA-mismatched unrelated donors. Collectively, these data have advanced our knowledge and understanding of hematopoietic cell transplant for this disease. These data can also serve as "contemporaneous controls" for comparison with other more recent curative treatments like gene therapy and gene editing.Data available for request include allogeneic hematopoietic cell transplants for sickle cell disease (Hb SS and Hb Sβ thalassemia) in the United States from 1991 to 2019. Follow-up data through December 2020 are available.Instructions for requesting individual-level data are available on BioData Catalyst at https://biodatacatalyst.nhlbi.nih.gov/resources/data/. Apply for data access in dbGaP. Upon approval, users may begin accessing requested data in BioData Catalyst. For questions about availability, you may contact the BioData Catalyst team at https://biodatacatalyst.nhlbi.nih.gov/contact.

Study phs002385

Northwestern NUgene Project: Type 2 Diabetes

The ability to correlate genetic variation with disease susceptibility and response to drug therapy depends on genotype or sequence analysis of large numbers of richly characterized DNA samples. Eight years agoWe are a part of NHGRI's electronic Medical Records and Genomics (eMERGE) Network, whose goal is to conduct genome-wide association studies in thousands of individuals using EMR-derived phenotypes and DNA from linked biorepositories. For eMERGE, Northwestern University (NU) is studying type 2 diabetes as a phenotype. In addition, in order to explore race differences in the prevalence of type 2 diabetes, NU collaborated with Vanderbilt University to study a mix of both Caucasian and African-Americans. Northwestern University: In 2002, Northwestern committed to the development of a DNA repository to serve as a platform for the identification and validation of genotype-phenotype associations that will impact healthcare. The NUgene Project is a repository with longitudinal medical information from participating patients at affiliated hospitals and outpatient clinics from the Northwestern University Medical Center. Participants' DNA samples are coupled with data from a questionnaire (2 versions were used, 1 before and 1 after February 2006, both are included) and continuously updated data from our Electronic Medical Record (EMR) representing actual clinical care events. Northwestern has a state-of-the art, comprehensive inpatient and outpatient EMR system of over 2 million patients. NUgene has broad access to participant data for all outpatient visits as well as inpatient data via a consolidated data warehouse. NUgene participants consent to distribution and use of their coded DNA samples and data for a broad range of genetic research by third-party investigators. Vanderbilt University: BioVU, Vanderbilt's DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt's EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations.

Study phs000237

14308 results for ""Pennsylvania+German"+ACS+study+'Socius'+open+access"

in 34.93 milliseconds.