Search Results - EGA European Genome-Phenome Archive

Heart Failure Network - Xanthine Oxidase Inhibition for Hyperuricemic Heart Failure Patients (HFN EXACT-BioLINCC)

ObjectivesTo determine the effect of allopurinol after 24 weeks on a composite clinical endpoint that classifies subject's clinical status (improved, worsened, unchanged) in patients with heart failure and high uric acid levels.BackgroundMorbidity and mortality rates for patients with heart failure are high, despite guideline-recommended therapy. Heart failure is characterized by an imbalance between left ventricular (LV) performance and myocardial energy consumption. There is a growing body of evidence that suggests oxidative stress contributes to ventricular and vascular remodeling, and disease progression in heart failure. Targeting potential source(s) of oxidative stress, e.g. Xanthine oxidase (XO), was the focus of recent clinical trials and epidemiological studies. Increased XO activity has been shown to lead to production of superoxide and uric acid (UA). Serum uric acid levels are included in heart failure risk scores, and hyperuricemia is present in about 25% of patients with heart failure. Hyperuricemia is associated with exercise intolerance, reduced survival, and worsening symptoms. The EXACT-HF trial tested allopurinol, an inhibitor of XO, as a potential target therapy for hyperuricemic heart failure patients.Subjects253 subjects were enrolled in the EXACT-HF study. 128 participants were randomized to the allopurinol arm, and of those participants, 119 completed the trial and 9 did not. 125 participants were randomized to the placebo arm, and of those participants, 116 completed the trial and 9 did not.DesignEXACT-HF was a multi-center, double-blind, placebo controlled, 24-week trial of allopurinol. Eligible participants had to be receiving a stable regimen for at least two weeks (3 months for beta-blockers) prior to randomization. Participants were randomized by an automated system to either the allopurinol or placebo arm, and started treatment within 12 hours of completing the baseline visit. During the first week, participants in both treatment arms received 300mg daily of the respective medications. For the following 23 weeks, participants in both treatment arms received 600mg daily of the respective medications. Patients unable to tolerate 600 mg were maintained on 300 mg.The primary endpoint was a composite clinical endpoint (CCE) that classified a subject's clinical status as improved, worsened, or unchanged at 24 weeks. The CCE was determined based on the following: death; hospitalization, emergency room visit or emergent clinic visit for worsening HF; medication change for worsening HF; and Patient Global Assessment using a 7-point scale. Secondary endpoints at 12 and 24 weeks included changes in quality of life as assessed by the Kansas City Cardiomyopathy Questionnaire, and submaximal exercise capacity as assessed by a 6-minute walk test.ConclusionsParticipants who received allopurinol had significantly less serum uric acid laboratory levels after 24 weeks; however, no significant difference was observed in the primary and secondary endpoints between the allopurinol and placebo-treated patients. Therefore, in high-risk HF patients with reduced ejection fraction and elevated uric acid levels, xanthine oxidase inhibition with allopurinol failed to improve clinical status, exercise capacity, quality of life, or LVEF at 24 weeks (Circulation. 2015 May 19; 131(20):1763-71).

Study phs003533

HeartShare - Extant Datasets - Harmonized Clinical Trials Collection

Heart failure with preserved ejection fraction (HFpEF) prevalence is rising with an aging population and contributing comorbidities, such as obesity and diabetes. The Get With The Guidelines - Heart Failure (GWTG-HF) study showed that the proportion of hospitalized HFpEF patients rose from 2005 to 2010, and this trajectory continued to increase through 2020. HFpEF patients have a poor 5-year outcome with a 75% mortality rate. Taken together, these data suggest that HFpEF may be the dominant HF subtype in the future, affecting approximately 1 in 10 adults during their lifetime.In addition to its increasing prevalence, HFpEF is a heterogeneous syndrome with multiple pathophysiological processes and varied clinical presentations. There is an urgent need to improve understanding of different HFpEF phenotypes to match patients with interventions based on their unique subtype. Phenomapping studies have identified between two and six HFpEF clusters/phenogroups with shared features. Of these, three overlapping phenotypes repeatedly arise: an 'older, vascular aging' phenotype, 'metabolic, obese' phenotype, and 'relatively younger, natriuretic peptide (NP) deficiency' phenotype. Continued refinement of these HFpEF subtypes is needed to identify distinct characteristics and underlying biologic and molecular mechanisms towards therapeutic development and future precision trials with improved diagnostic criteria and treatment including prevention.The HeartShare extant datasets collection consists of selected completed trials on HFpEF which have been harmonized for the purpose identifying and defining subtypes. The goal is to identify HFpEF subtypes that have a common pathophysiology. Through the HeartShare extant datasets collection, users can request access to both the harmonized data and the individual trial datasets.To request access to this study collection, select phs003989 in the dbGaP when submitting a data access request. The following clinical trials and harmonized data is available through this collection:Study NameHandleAccessionConsent GroupsSurgical Treatment for Ischemic Heart FailureBioLINCC_STICHphs003493.v1.p1GRUHeart Failure Network Aldosterone Targeted Neurohormonal Combined with Natriuresis TherapyBioLINCC_HFN_ATHENAphs003506.v1.p1GRUHeart Failure Network - Effectiveness of Ultrafiltration in Treating People With Acute Decompensated Heart Failure and Cardiorenal SyndromeBioLINCC_HFN_CARRESSphs003510.v1.p1GRUHeart Failure Network: Diuretic Optimization Strategies Evaluation in Acute Heart FailureBioLINCC_HFN_DOSEphs003524.v1.p1GRUHeart Failure Network - Xanthine Oxidase Inhibition for Hyperuricemic Heart Failure PatientsBioLINCC_EXACT_HFphs003533.v1.p1GRUHeart Failure Network: Functional Impact of GLP-1 for Heart Failure TreatmentBioLINCC_HFN_FIGHTphs003542.v1.p1GRUHeart Failure Network - Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection FractionBioLINCC_HFN_NEATphs003548.v1.p1GRUHeart Failure Network - Phosphodiesterase-5 Inhibition to Improve Clinical Status and Exercise Capacity in Diastolic Heart FailureBioLINCC_HFN_RELAXphs003565.v1.p1GRUHeart Failure Network - Renal Optimization Strategies Evaluation in Acute Heart Failure and Reliable Evaluation of DyspneaBioLINCC_HFN_ROSEphs003589.v1.p1GRUHeart Failure: A Controlled Trial Investigating Outcomes of Exercise TrainingBioLINCC_HF_ACTIONphs003599.v1.p1HMBHeart Failure: A Controlled Trial Investigating Outcomes of Exercise TrainingBioLINCC_HF_ACTIONphs003599.v1.p1HMB-NPUGuiding Evidence Based Therapy Using Biomarker Intensified Treatment in Heart FailureBioLINCC_GUIDE_ITphs003621.v1.p1GRUSudden Cardiac Death in Heart Failure TrialBioLINCC_SCD_HeFTphs003654.v1.p1GRUTreatment of Preserved Cardiac Function Heart Failure With an Aldosterone AntagonistBioLINCC_TOPCATphs003665.v1.p1HMB-MDSHeart Failure Network - Inorganic Nitrite Delivery to Improve Exercise Capacity in HFpEFBioLINCC_HFN_INDIEphs003667.v1.p1GRUStudies of Left Ventricular DysfunctionBioLINCC_SOLVDphs003668.v1.p1GRUEvaluation Study of Congestive Heart Failure and Pulmonary Artery Catheterization EffectivenessBioLINCC_ESCAPEphs003782.v1.p1GRU

Study phs003989

Copy number profile of ctDNA in ovarian cancer patients

This study analyzes the copy number profiles from circulating tumor DNA (ctDNA) in plasma samples withdrawn from ovarian cancer patients, in a subset of samples from the MITO16A clinical trial.

Study EGAS00001008226

Sequencing of Plasma DNA from breast cancer patients

Dataset contains plasma DNA whole genome sequencing on 4 breast cancer patients. It also includes matched germline and tumour whole genome sequencing data. Two benign cancer patients were also sequenced and their plasma DNA and matched germline whole genome sequencing data are included in the dataset. Samples were sequenced on Illumina HiSeqX Ten.

Dataset EGAD00001006869

Whole exome and transcriptome sequencing of biliary tract cancer

To uncover the full repertoire of genetic and transcriptomic landscape of biliary tract cancer (BTC), we molecularly characterized BTC based on genetic and transcriptomic alteration profiles.

Study EGAS00001000950

Submitting array based metadata

Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. 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. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, 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 "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering 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 (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

Documentation submission/metadata/submission/array

EGAD00010000584

WTCCC2 Glaucoma samples using Illumina 670k array

Dataset EGAD00010000584

Average_5mC_DIFF_Roadmap

Average methylation difference 12 months vs 0 months at Roadmap Epigenomics chromatin state annotations from different cell types using nanopolish. Data from 8 individuals.

Dataset EGAD00010002410

postQC Genotypes

postQC genotype data from the Affymetrix AxiomTM HGCoV2 1 array in plink binary format. QC was carried out using PLINK v1.9

Dataset EGAD00010002436

HRR gene mutation analysis

Mutation analysis of cfDNA from urine (stored at various storage conditions) and plasma using the QIAseq HRR panel

Dataset EGAD50000001586

Cord blood sequencing data

SmMIP libraries using cord blood DNA were generated in replicates and were sequenced on the NovaSeq SP platform (Illumina)

Dataset EGAD00001007789

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

Understanding human fetal pancreas development using subpopulation sorting and RNA sequencing

To decipher the populations of cells present in the human fetal pancreas and their lineage relationships, we developed strategies to isolate pancreatic progenitors, endocrine progenitors and endocrine cells. Transcriptome analysis of the individual populationsrevealed a large degree of conservation among vertebrates in the drivers of gene expression changes occurring at different steps of differentiation, althoughnotably, sometimes, different members of the same gene family are expressed. The transcriptome analysis establishes a resource to identify novel genes and pathways involved in human pancreas development. Single cell profiling further captured intermediate stages ofdifferentiation and enabled us to decipher the sequence of transcriptional events occurring during human endocrine differentiation. Furthermore, we evaluate how well individual pancreatic cells derived in vitro from human pluripotent stem cells mirror the natural processoccurring in human fetuses. This comparison uncovers a few differences at the progenitor steps, a convergence at the steps of endocrine induction and the current inability to fully resolve endocrine cell subtypes in vitro.

Study EGAS00001003127

Deep sequencing of 151 cancer genes

Deep sequencing of 151 cancer genes in 6 synchronous CRC of 3 patients

Dataset EGAD00001001870

Whole genome sequencing of 64 HER2-Positive Breast Cancer

Dataset EGAD00001001844

Cancer and germline exomes consisting of FASTQ paired-end reads from melanoma and lung cancer samples

Efforts to precisely identify tumor human leukocyte antigen presented peptides (HLAp) capable of mediating T cell based tumor rejection still face important challenges. Recent reports suggest that non-canonical cancer HLAp could be immunogenic but their identification requires highly sensitive and accurate mass-spectrometry (MS)-based proteogenomics approaches. Here, we present a MS-based analytical pipeline that can precisely characterize the non-canonical HLAp repertoire, incorporating whole exome sequencing, bulk and single cell transcriptomics, ribosome profiling, and a combination of two MS/MS search tools. This approach results in the accurate identification of hundreds of shared and tumor-specific non-canonical HLAp. Albeit often at low levels and in distinct subpopulations of cells, numerous non-canonical HLAp are shared across tumors. This analytical platform holds great promise for the discovery of novel cancer antigens for cancer immunotherapy.

Study EGAS00001003723

15012 results for "cancer studies using rna-seq"

in 18.97 milliseconds.