1654 results for "fc coins xbox one Navštivte Buyfc26coins.com Mezinárodně uznávaná společnost v herním průmyslu..L14h"

in 14.80 milliseconds.

• CyTOF of 27 DLBCLs

  Diffuse large B-cell lymphoma (DLBCL) is the most common histologic subtype of non-Hodgkin lymphoma and is notorious for its clinical heterogeneity. Patient outcomes can be predicted by cell-of-origin (COO) classification, demonstrating that the underlying transcriptional signature of malignant B-cells informs biological behavior in the context of standard combination chemotherapy regimens. In the current study, we used mass cytometry (CyTOF) to examine tumor phenotypes at the protein level with single cell resolution in a collection of 27 diagnostic DLBCL biopsy specimens from treatment naïve patients. We found that malignant B-cells from each patient occupied unique regions in 37-dimensional phenotypic space with no apparent clustering of samples into discrete subtypes. Interestingly, variable MHC class II expression was found to be the greatest contributor to phenotypic diversity. Within individual tumors, a subset of cases showed multiple phenotypic subpopulations, and in one case we were able to demonstrate direct correspondence between protein-level phenotypic subsets and DNA mutation-defined subclones. In summary, CyTOF analysis can resolve both inter- and intra-tumoral heterogeneity among primary samples, and reveals that each case of DLBCL is unique and may be comprised of multiple, genetically distinct subclones.

  Dataset EGAD00001005419

• TRACERx100 metastatic samples

  Whole exome sequencing of 10 metastatic biopsies from four TRACERx100 patients (see EGA dataset EGAS00001002247), collected either after relapse or death. The data from these samples are initially published with Abbosh, C. et al. Phylogenetic ctDNA analysis depicts early stage lung cancer evolution. Nature, http://dx.doi.org/10.1038/nature22364 (2017). Abstract: Earlier detection of relapse following primary surgery for non-small cell lung cancer and the characterization of emerging subclones seeding metastatic sites might offer new therapeutic approaches to limit tumor recurrence. The potential to non-invasively track tumor evolutionary dynamics in ctDNA of early-stage lung cancer is not established. Here we conduct a patient-specific approach to ctDNA profiling in the first 100 lung TRACERx (TRAcking Cancer Evolution through therapy (Rx)) study participants, including one patient co-recruited to the PEACE (Posthumous Evaluation of Advanced Cancer Environment) post-mortem study. We identify independent predictors of ctDNA release in early-stage non-small cell lung cancer and perform tumor volume limit of detection analyses. Through blinded profiling of post-operative plasma, we observe evidence of adjuvant chemotherapy resistance and identify patients destined to experience recurrence of their lung cancer. Finally, we show that phylogenetic ctDNA profiling tracks the subclonal nature of lung cancer relapse and metastases, providing a new approach for ctDNA driven therapeutic studies.

  Dataset EGAD00001003301

• P647 Targeted resequencing project

  In collaboration with Dr Robert Semple we have identified a family harbouring an autosomal dominant variant, which leads to severe insulin resistance (SIR), short stature and facial dysmorphism. This family is unique within the SIR cohort in having normal lipid profiles, preserved adiponectin and normal INSR expression and phosphorylation. DNA is available for 7 affected and 7 unaffected family members across 3 generations. All 14 samples have been genotyped using microsatellites and the Affymetrix 6.0 SNP chip. Linkage analysis identified an 18.8Mb haplotype on chromosome 19 as a possible location of the causative variant. However, Exome sequencing of 3 affected and 1 unaffected family members has not identified the causative variant suggesting the possibility of an intronic or intergenic variant in this region or elsewhere in the genome. We propose to conduct whole genome sequencing of 5 members of the pedigree at a depth of 20X. The chosen samples are two sets of parents plus one member of an unaffected branch of the pedigree who shares the risk haplotype on chromosome 19. Sequencing of the two sets of parents will be used along with the genome-wide SNP data to impute 4 affected children giving an effect sample size of 6 affected individuals.

  Dataset EGAD00001000383

• Ethiopia Genome Project (low coverage)

  The Ethiopian area stands among the most ancient ones ever occupied by human populations and their ancestors. Particularly, according to archaeological evidences, it is possible to trace back the presence of Hominids up to at least 3 million years ago. Furthermore, the present day human populations show a great cultural, linguistic and historic diversity which makes them essential candidate to investigate a considerable part of the African variability. Following the typing of 300 Ethiopian samples on Illumina Omni 1M (see Human Variability in Ethiopia project, previously approved by the Genotyping committee) we now have a clearer idea on which populations living in the area include the most of the diversity.This project therefore aims to sequence the whole genome of 300 individuals at low (4-8x) depth belonging to the six most representative populations of the Ethiopian area to produce a unique catalogue of variants peculiar of the North East Africa. Furthermore 6 samples (one from each population) will also be sequenced at high (30x) depth to ensure full coverage of the diversity spectrum.The retrieved variants will be of great help in evaluating the demographic dynamics of those populations as well as shedding light on the migrations out of Africa.

  Dataset EGAD00001000598

• Long-Term Oxygen Treatment Trial (LOTT-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives: To evaluate the efficacy of long-term treatment with supplemental oxygen in people with stable chronic obstructive pulmonary disease (COPD) and resting or exercise-induced moderate desaturation. Background: COPD is the fourth leading cause of death in the United States, with more than twelve million people currently diagnosed with the disease. In 2011, Medicare reimbursements for oxygen-related costs for people with COPD exceeded two billion dollars. The quality of life of a person with COPD decreases as the disease progresses, making treating and managing COPD in the moderate stages important. The benefits of oxygen supplementation were studied in the 1970s, but these benefits were specific to people with COPD who have severe resting hypoxemia. The LOTT trial was designed to address the effectiveness of supplemental oxygen therapy in treating people with COPD who have moderately low blood oxygen levels at rest or who have normal blood oxygen levels at rest, but have low or very low blood oxygen levels during exercise. Participants: There were a total of 1759 people screened for eligibility for the LOTT trial. Of the 1759 screened, 738 people with COPD were selected for randomization with 368 randomly assigned to the supplemental-oxygen group and 370 to the no-supplemental-oxygen group. Of the 738 people with COPD who underwent randomization, 133 (18%) had resting desaturation only, 319 (43%) had exercise-induced desaturation only, and 286 (39%) had both types of desaturation. Furthermore, in the supplemental-oxygen group, 220 people were prescribed 24-hour oxygen and 148 were prescribed oxygen during exercise and sleep only. Design: The LOTT trial was originally designed to test whether the use of supplemental oxygen would result in a longer time to death for people with COPD and moderate resting desaturation. After seven months, the trial design was judged to be infeasible; therefore, the trial was redesigned to include people with exercise-induced desaturation with a primary composite outcome of death or first hospitalization for any cause, whichever occurs first. Other outcomes measured included: death, health care utilization, COPD exacerbation, quality of life measurements, anxiety, depression, and measures of functional status. Potential participants were screened using questionnaires, a breathing test, a brief physical exam, a blood draw, and measurements of resting and walking blood oxygen levels. Based on those results, eligible participants returned for a second screening visit for further evaluations. At the end of the second visit, eligible participants were assigned randomly to supplemental oxygen therapy or no oxygen therapy. Participants assigned to supplemental oxygen therapy received stationary and/or portable oxygen systems. Participants were required to return for a one hour visit to determine how much oxygen to use while walking and to learn how to use the equipment. Participants who had low blood oxygen levels during rest were instructed to use supplemental oxygen 24 hours per day. Participants with normal resting blood oxygen levels, but low or very low blood oxygen levels during exercise were instructed to use it during physical activity and sleep. Throughout the treatment period, participants were asked to keep records of the number of oxygen tanks emptied or pounds of oxygen delivered, meter readings, and changes in equipment. Study officials contacted participants weekly for the first month, monthly for the next five months, and then every two months until the Year 1 study visit. Participants assigned to receive no oxygen treatment were contacted one week after assignment for a check-up. All participants returned for study visits once a year for up to seven years. At each of these visits, participants completed some of the same tests and questionnaires from the screening visit. Participants underwent a blood draw during the one year study visit. Participants in both treatment groups received two phone calls each year to check on status and use of oxygen. In addition, participants in both groups were asked to complete a quality of life questionnaire by mail at four months and sixteen months. Medicare claims were collected for the duration of each participant's enrollment in the study. Conclusions: In participants with stable COPD and resting or exercise-induced moderate desaturation, the prescription of long-term supplemental oxygen did not result in a longer time to death or first hospitalization than no long-term supplemental oxygen, nor did it provide sustained benefit with regard to any of the other measured outcomes. Long-Term Oxygen Treatment Trial Research Group, Albert RK, Au DH, Blackford AL, Casaburi R, Cooper JA Jr, Criner GJ, Diaz P, Fuhlbrigge AL, Gay SE, Kanner RE, MacIntyre N, Martinez FJ, Panos RJ, Piantadosi S, Sciurba F, Shade D, Stibolt T, Stoller JK, Wise R, Yusen RD, Tonascia J, Sternberg AL, Bailey W. A Randomized Trial of Long-Term Oxygen for COPD with Moderate Desaturation. N Engl J Med. 2016 Oct 27;375(17):1617-1627.

  Study phs003933

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• PyEGA3 download client

  PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

  Documentation access/download/files/pyega3

• Adipose Tissue Omics In Obesity

  This project used a multi-omics approach to study the adipose tissue transcriptome in humans with and without obesity. Our human cohort included males and females between the ages of 18-80 who underwent elective abdominal surgery at the University of Michigan and the Ann Arbor Veterans Affairs Healthcare System.Patients with advanced cancer or immuncompromised status were excluded. Visceral adipose tissue (VAT/omental) and subcutaneous adipose tissue (SAT/abdominal wall) were collected from subjects with obesity (BMI>=35) at the beginning of elective surgical procedures, placed on ice, and transported back to the laboratory for immediate processing. For adipose tissue stromal cells (ASC) isolation, adipose tissue was digested with Type II collagenase (2 mg/mL in PBS/2% BSA) at 37oC, 60min, centrifuged at 250 rcf, and the stromal-vascular cell pellet was retrieved, plated overnight, and the adherent cells passaged three times to enrich for ASC, which were then frozen in DMEM/F12, 15% fetal calf serum, and 10% DMSO in liquid nitrogen until use. Single nuclear sequencing was performed on preparations from intact adipose tissue. Bulk RNA sequencing and single cell sequencing were performed on ASC isolated from intact adipose tissue and cultured in 2D and 3D culture systems. We currently apply bulk, single cell, and single nuclear sequencing analyses to these tissues. One component of this project studies single nuclear sequencing in nuclei isolated from intact adipose tissues from human subjects with obesity, focusing on depot comparisons (VAT vs. SAT). This cohort also permits comparisons of adipose tissue transcriptomes between male and female subjects, controlling for age and BMI. Primary findings to date include identification of multiple ASC, adipocyte, and endothelial cell (EC) subpopulations, T-cell, and macrophage (MAC) populations that are in concordance with and expand upon other published datasets. Of two dominant ASC subpopulations, one (inflammatory-mesothelial, IM- ASC) is present in VAT, but absent in SAT, while the other (fibroadipogenic, FA-ASC) is present in both VAT and SAT. We identified multiple EC subtypes with features of lymphatic, venous, and arterial EC, and a PRDM16 expressing population with features of an EC progenitor. Immune cell populations match recent experimental validation of lipid-activated macrophage (LAM) phenotypes, TIM4 macrophages, and a prominent population of MRC1/CD206+ resident AT macrophages with expression signatures related to glucocorticoid activation. These data support depot-specific differences in ASC subpopulations and previously unrecognized EC heterogeneity within human AT, with the potential to shed light on functional differences in AT depot and disease state. Planned future studies include ATAC-Seq and other omics analyses. Another component of this project studies transcriptional responses of ASC in vitro to various stimuli, including different matrix environments. Current data includes bulk RNA Sequencing of human ASC from VAT and SAT differentiated into mature adipocytes in hydrogels of differing stiffness (3%, 5%, 10%) to define transcriptional responses to matrix environments of different stiffness. Primary findings to date include enrichment of adipogenesis and lipid and oxidative metabolic gene pathways in adipocytes in 5% relative to 3% hydrogels, while fibrotic gene pathways have been enriched in 3% hydrogels. These data demonstrate that intermediate density matrix promotes a more adipogenic, less fibrotic adipocyte phenotype geared towards increased lipid and aerobic metabolism. Planned future studies include expansion of intact tissues from our cohort studied with single nuclear sequencing, as well as further study of ASC responses in vitro to different biologic stimuli, including different matrix environments.

  Study phs003390

• Heart Failure Network - Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection Fraction (HFN NEAT-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Related StudiesEcho images are available with HFN-NEAT Imaging.ObjectivesTo determine the effect of isosorbide mononitrate on daily activity in patients with heart failure and preserved ejection fraction.Background Nitrates are commonly prescribed for symptom relief in patients with heart failure. Early studies in patients with heart failure with a reduced ejection fraction concluded that long-acting nitrates improve activity tolerance; however, approximately half of heart failure patients have preserved ejection fraction. The effects of nitrates in patients with heart failure and a preserved ejection fraction have not been extensively studied and the overall effect of nitrates on activity tolerance in such patients is uncertain. ParticipantsThere were a total of 110 participants enrolled with 51 participants assigned to receive isosorbide mono-nitrate first and placebo second, and 59 participants assigned to receive placebo first and isosorbide mononitrate second. Design Enrolled participants underwent baseline assessments, including echocardiography, quality-of-life scores, 6-minute walk test distance, and NT-proBNP levels. participants were also supplied with two kinetic activity monitors containing high-sensitivity triaxis accelerometers, to be worn 24 hours per day. The accelerometer measurements were expressed as arbitrary accelerometer units and stored every 15 minutes equaling 96 data points per day. The 15-minute cumulative accelerometer units were totaled over a 24-hour period to provide daily accelerometer units. Participants were assigned to one of two treatment groups: 6 weeks of placebo first with crossover to 6 weeks of isosorbide mononitrate, or 6 weeks of isosorbide mononitrate first with crossover to 6 weeks of placebo. The study drugs were prepared as 30-mg tablets of isosorbide mononitrate and matching placebo. During each 6-week period, participants were instructed to take no study drug for the first 2 weeks followed by one tablet (30 mg daily) for 1 week, two tablets (60 mg once daily) for 1 week, and four tablets (120 mg once daily) until the next study visit, for a treatment duration of at least 2 weeks and up to 4 weeks. After each 6-week period, participants returned to the study center to repeat end-point assessments. The primary outcome for the study was the comparison of average daily accelerometer units during the period in which participants were receiving the 120-mg dose of isosorbide mononitrate compared to the period in which participants received the placebo. Other secondary end points included the 6-minute walk distance and the post-walk Borg dyspnea score, scores on the Kansas City Cardiomyopathy Questionnaire and the Minnesota Living with Heart Failure Questionnaire, and NT-proBNP levels. In addition, participants completed a questionnaire indicating in which period (first, second, no preference) they felt better. Conclusions Participants were active for fewer hours of the day during the 120-mg phase of receipt of isosorbide mononitrate as compared with placebo. Furthermore, during all study-drug regimens combined (30 mg to 120 mg), participants were less active during receipt of isosorbide mononitrate as compared with placebo. There was no significant effect of isosorbide mononitrate on secondary outcomes.

  Study phs003548

• Heart Failure Network - Imaging from Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection Fraction (HFN NEAT-Imaging)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To determine the effect of isosorbide mononitrate on daily activity in patients with heart failure and preserved ejection fraction.Background: Nitrates are commonly prescribed for symptom relief in patients with heart failure. Early studies in patients with heart failure with a reduced ejection fraction concluded that long-acting nitrates improves activity tolerance; however, approximately half of heart failure patients have preserved ejection fraction. The effects of nitrates in patients with heart failure and a preserved ejection fraction have not been extensively studied and the overall effect of nitrates on activity tolerance in such patients is uncertain.Subjects: There were a total of 110 patients enrolled with 51 patients assigned to receive isosorbide mono-nitrate first and placebo second, and 59 patients assigned to receive placebo first and isosorbide mononitrate second.Design: Enrolled subjects underwent baseline assessments, including echocardiography, quality-of-life scores, 6-minute walk test distance, and NT-proBNP levels. Subjects were also supplied with two kinetic activity monitors containing high-sensitivity triaxis accelerometers, to be worn 24 hours per day. The accelerometer measurements were expressed as arbitrary accelerometer units and stored every 15 minutes equaling 96 data points per day. The 15-minute cumulative accelerometer units were totaled over a 24-hour period to provide daily accelerometer units.Subjects were assigned to one of two treatment groups: 6 weeks of placebo first with crossover to 6 weeks of isosorbide mononitrate, or 6 weeks of isosorbide mononitrate first with crossover to 6 weeks of placebo. The study drugs were prepared as 30-mg tablets of isosorbide mononitrate and matching placebo. During each 6-week period, patients were instructed to take no study drug for the first 2 weeks followed by one tablet (30 mg daily) for 1 week, two tablets (60 mg once daily) for 1 week, and four tablets (120 mg once daily) until the next study visit, for a treatment duration of at least 2 weeks and up to 4 weeks. After each 6-week period, patients returned to the study center to repeat end-point assessments. The primary outcome for the study was the comparison of average daily accelerometer units during the period in which patients were receiving the 120-mg dose of isosorbide mononitrate compared to the period in which patients received the placebo. Other secondary end points included the 6-minute walk distance and the post-walk Borg dyspnea score, scores on the Kansas City Cardiomyopathy Questionnaire and the Minnesota Living with Heart Failure Questionnaire, and NT-proBNP levels. In addition, subjects completed a questionnaire indicating in which period (first, second, no preference) they felt better. Conclusions: Patients were active for fewer hours of the day during the 120-mg phase of receipt of isosorbide mononitrate as compared with placebo. Furthermore, during all study-drug regimens combined (30 mg to 120 mg), patients were less active during receipt of isosorbide mononitrate as compared with placebo. There was no significant effect of isosorbide mononitrate on secondary outcomes.

  Study phs004254