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

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

How to upload Crypt4GH files

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

Documentation submission/data/uploading-files/inbox

Transcriptome atlas of brain organoid developent

Single-cell Cut&Tag of three histone modifications and chromatin accessibility over a timecourse of brain organoid development from pluripotency. We profiled 5 time points of brain organoid development and 2 time points of retinal organoid development. We used scRNA-seq to profile transcriptome. Library preparation was carried out with the 10x genomics platform.

Dataset EGAD50000000223

BIOMIROX

This dataset regroups RNAseq of paired primary colorectal cancers and liver metastases extracted from 113 patients In Paris and Besançon University Hospitals. 216 FASTQ files from single-end 3' PolyA (QuantSeq 3′mRNA-Seq Kit FWD for Illumina (Lexogen)) RNAseq samples were generated On NOVASEQ 6000 (ILLUMINA).

Dataset EGAD50000000443

MissionBio single cell DNA and protein seq for 2 samples

This dataset contains MissionBio Targeted single-cell DNA and Protein sequencing data from a primary sample and a patient-derived xenograft (PDX) model, which is used to investigate the clonal evolution in the FOXF1/FENDRR ALL subtype. All the 2 samples are in bam file type.

Dataset EGAD50000001793

Mixture of 4

Mixture of 4 unrelated individuals sequenced by 10x as a scRNA-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile. The clustering of SNPs is submitted as the processed file. The Sequencing fastqs are submitted as unprocessed files.

Dataset EGAD00001008724

Mixture of 3

Mixture of 3 unrelated individuals sequenced by 10x as a scRNA-seq. The dataset was then processed by Cell Ranger and deconvoluted to yield each individuals genetic profile. The clustering of SNPs is submitted as the processed file. The Sequencing fastqs are submitted as unprocessed files.

Dataset EGAD00001008729

KCL PRECSION Mutations targeted-seq

105 Normal, DCIS and recurrences samples target-sequenced

Dataset EGAD00001008376

Sequencing data

WES: (7 samples, BAM files), scRNA-Seq (4 samples, BAM files), TruSight (56 samples, BAM or FASTQ files)

Dataset EGAD00001007749

Young Boost Trial for Breast Cancer patients

The Young Boost Trial (YBT, YOUNG BOOST / BOOG 2004-01 (Borstkanker) | Kanker.nl investigated the optimal radiation dose for breast cancer patients aged 50 years or younger, treated with breast-conserving therapy (BCT). In this randomized study, participants were assigned to receive either a 26 Gy or a 16 Gy radiation boost, with the primary endpoint being local recurrence. To explore potential predictive biomarkers of treatment response in this patient group, whole exome sequencing (WES) was performed on tumor samples to identify genetic factors that could guide personalized treatment strategies and improve clinical outcomes for these young breast cancer patients.

Study EGAS50000000797

Clonal Evolution and Transcriptomic Analysis of Chronic Lymphocytic Leukemia Treated with Ibrutinib

Disease progression has been increasingly appreciated with the use of ibrutinib to treat chronic lymphocytic leukemia (CLL). Understanding the pattern of clonal evolution and transcriptomic changes during the early treatment period with ibrutinib may provide insight into the mechanisms of resistance. We performed whole exome sequencing on sequential samples with matched germline controls from 61 patients with CLL during the first 12 months of ibrutinib monotherapy or ibrutinib in combination with rituximab. Additionally, RNA sequencing was done on a subset of 14 patients treated with ibrutinib monotherapy. The presence of clonal shifts was associated with an increased risk of disease progression, suggesting that resistant clones are more likely to emerge in CLL with greater evolutionary capacity.This cohort was later augmented with additional data (including data from 15 additional patients). In total, this second set of data contained whole exome sequencing (31 samples), RNA sequencing (6 samples) and reduced representation bisulfite sequencing (67 samples) for CLL samples and used them to identify expression subtypes of CLL. In an integrative analysis of genetic, transcriptomic, and epigenetic data, incorporating known and newly identified subtypes of CLL, we built new models to improve patient prognostication.

Study phs001473

Resolving complex duplication variants using long read genome sequencing in autism spectrum disorder

The goal of the study is to resolve complex genomic rearrangements in individuals diagnosed with autism spectrum disorder (ASD). Families were identified where at least one individual had previously been diagnosed with ASD, and carried a complex genomic rearrangement as determined by short-read whole genome sequencing. In this study the parents, proband and additional siblings, a total of 20 individuals, were analyzed using Oxford Nanopore Technologies long-read sequencing. Each individual was sequenced on one PromethION flow-cell, providing approximately 25-30X coverage of the genome. The data is deposited as nanopore BAM files with methylation information included.

Study EGAS50000000390

14990 results for "cancer studies using rna-seq"

in 19.32 milliseconds.