Search Results - EGA European Genome-Phenome Archive

Best Endovascular vs. Best Surgical Therapy in Patients With Critical Limb Ischemia (BEST CLI-BioLINCC)

Data Access NOTE Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives To compare the effectiveness of surgical treatment to the effectiveness of endovascular treatment in adults with chronic limb-threatening ischemia who are eligible for both treatment options. Background Peripheral artery disease (PAD) affects more than 200 million people worldwide. A portion of those individuals develop chronic limb-threatening ischemia (CLTI). CLTI is associated with severe health outcomes. CLTI is defined by ischemic foot pain at rest, ischemic ulcerations, or gangrene. Treatment for CLTI includes revascularization to improve limb perfusion and limit the risk of amputation. However, the choice of surgery or endovascular therapy for revascularization varies greatly. The extent to which this variability affects clinical outcomes in patients with CLTI is unknown. The BEST-CLI trial was initiated to determine whether endovascular revascularization was superior to surgical revascularization in patients with CLTI. Participants A total of 1434 participants with a single segment of great saphenous vein comprised cohort 1. Of these, 718 participants were randomly assigned to the surgical treatment group and 716 participants were randomly assigned to the endovascular therapy group. A total of 396 participants needing an alternative conduit comprised cohort 2. Of these, 197 participants were randomly assigned to the surgical treatment group and 199 participants were randomly assigned to the endovascular therapy group. Design BEST-CLI was an international, randomized, open-label trial. Participants were assigned to one of two cohorts based on the availability of a single segment of great saphenous vein. Participants in both cohorts were randomly assigned to either surgery or endovascular therapy. Follow-up was performed at 30 days after the procedure, 3 months, 6 months, and every 6 months thereafter up to 84 months after randomization. Telephone visits in lieu of clinic visits were planned at 30 months and every 12 months thereafter and at the end of the trial. Participants were followed for major adverse cardiovascular events (myocardial infarction, stroke, or death from any cause), quality of life, level of pain, and performance on the six-minute walk test. The primary outcome was a composite of major adverse limb events or death from any cause. A major adverse limb event was defined as above ankle amputation of the index limb or a major index-limb reintervention (new bypass, interposition graft revision, thrombectomy, or thrombolysis). Conclusions Among patients with CLTI who had an adequate great saphenous vein for surgical revascularization (cohort 1), the incidence of a major adverse limb event or death was significantly lower in the surgical group than in the endovascular group. Among the patients who lacked an adequate saphenous vein conduit (cohort 2), the outcomes in the two groups were similar. Farber A, Menard MT, Conte MS, et al. Surgery or Endovascular Therapy for Chronic Limb-Threatening Ischemia. N Engl J Med. 2022;387(25):2305-2316. PMID 36342173

Study phs003844

BLUE CORAL: Biology and Longitudinal Epidemiology of PETAL COVID-19 Observational Study

Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions.Available Data: Long Term Follow-up data has been added with version 2. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from PETAL BLUE CORAL include: Bronchial Lavage, Plasma, Tracheal Aspirate, Urine, Whole Blood Buffy Coat, DNA, Plasma, Serum, Urine, and Whole Blood. Please note that use of biospecimens is tiered for both non-genetic and genetic research.Objectives: To measure the incidence and changes over time in symptoms, disability, and financial status after COVID-19–related hospitalization.Background: For many individuals, the effects of COVID-19 persist after the acute phase and result in prolonged symptoms and disability. This has led to widespread efforts to characterize the epidemiologic characteristics of such post-COVID-19 sequelae. However, accurate data were limited, hindering the ability to counsel patients, caregivers, and policy makers and to plan relevant recovery-focused clinical research. Thus, the BLUE CORAL study was intended to address the knowledge gaps and provide critical data to help guide clinical care, public health, and scientific efforts.Participants: A total of 1376 COVID-19 patents were enrolled, with 825 (444 male, and 379 female) that completed at least one follow-up survey.A subset of the BLUE CORAL adult participants were enrolled in the extension study, FIRE CORAL. FIRE CORAL was a multicenter prospective cohort study of participants recovering from COVID-19 disease after discharge from the hospital. Design: BLUE CORAL was a prospective cohort study. Participants were enrolled between August 24, 2020, and July 20, 2021, with follow-up occurring through March 30, 2022. Posthospital surveys were administered by trained interviewers in English or Spanish to patients or their proxies at 1, 3, and 6 months after enrollment. Cardiopulmonary symptoms were assessed using the Airways Questionnaire 20, the Kansas City Cardiomyopathy Questionnaire, and the Seattle Angina Questionnaire. Fatigue was assessed using the Patient Health Questionnaire-9. Disability was assessed by self-report of limitations in activities of daily living (ADLs) or instrumental activities of daily living (IADLs). Financial problems were assessed using the World Health Organization Disability Assessment Schedule 2.0 question and questions regarding job changes, time off work, and insurance coverage developed with the Mi-COVID-19 study using qualitative interviews. Quality of life was measured using the European Quality of Life 5-dimension 5-level instrument.The primary outcomes were new or worsened cardiopulmonary symptoms, financial problems, functional impairments, perceived return to baseline health, and quality of life. Symptoms that were not present before hospitalization or specifically reported as increased in severity were counted as new or worsened. Conclusions: The findings of this cohort study of people discharged after COVID-19 hospitalization suggest that recovery in symptoms, functional status, and fatigue was limited at 6 months, and some participants reported new problems 6 months after hospital discharge.

Study phs003419

Antihypertensive and Lipid-Lowering Treatment to Prevent Heart Attack Trial (ALLHAT-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. ObjectivesHypertension Study: To determine whether treatment with a calcium channel blocker or an angiotensin-converting enzyme inhibitor lowers the incidence of coronary heart disease (CHD) or other cardiovascular disease (CVD) events vs treatment with a diuretic.Lipid Study: To determine whether pravastatin compared with usual care reduces all-cause mortality in older, moderately hypercholesterolemic, hypertensive participants with at least an additional CHD risk factor. BackgroundHypertension Study: Antihypertensive therapy is well established to reduce hypertension-related morbidity and mortality, but the optimal first-step therapy is unknown.Lipid Study: Studies have demonstrated that statins administered to individuals with risk factors for coronary heart disease (CHD) reduce CHD events. However, many of these studies were too small to assess all-cause mortality or outcomes in important subgroups.ParticipantsHypertension Study: A total of 33,357 participants. Lipid Study: A total of 10,355 participants. Baseline mean total cholesterol was 224 mg/dL; LDL-C, 146 mg/dL; high-density lipoprotein cholesterol, 48 mg/dL; and triglycerides, 152 mg/dL. Mean age was 66 years; 49% were women, 38% black and 23% Hispanic, 14% had a history of CHD, and 35% had type 2 diabetes. DesignHypertension Study: A randomized, double-blind, active-controlled clinical trial conducted from February 1994 through March 2002. Participants were randomly assigned to receive chlorthalidone, 12.5 to 25 mg/d (n = 15,255); amlodipine, 2.5 to 10 mg/d (n = 9048); or lisinopril, 10 to 40 mg/d (n = 9054) for planned follow-up of approximately 4 to 8 years. The primary outcome was combined fatal CHD or nonfatal myocardial infarction, analyzed by intent-to-treat. Secondary outcomes were all-cause mortality, stroke, combined CHD (primary outcome, coronary revascularization, or angina with hospitalization), and combined CVD (combined CHD, stroke, treated angina without hospitalization, heart failure (HF), and peripheral arterial disease).Lipid Study: Multicenter (513 primarily community-based North American clinical centers), randomized, non-blinded trial conducted from 1994 through March 2002 in a subset of participants from the Antihypertensive and Lipid-Lowering Treatment to Prevent Heart Attack Trial (ALLHAT). The interventions in the trial were pravastatin, 40 mg/d, vs usual care. The primary outcome was all-cause mortality, with follow-up for up to 8 years. Secondary outcomes included non-fatal myocardial infarction or fatal CHD (CHD events) combined, cause-specific mortality, and cancer.ConclusionsHypertension Study: Thiazide-type diuretics are superior in preventing one or more major forms of CVD and are less expensive. They should be preferred for first-step antihypertensive therapy.Lipid Study: Pravastatin did not reduce either all-cause mortality or CHD significantly when compared with usual care in older participants with well-controlled hypertension and moderately elevated LDL-C. The results may be due to the modest differential in total cholesterol (9.6%) and LDL-C (16.7%) between pravastatin and usual care compared with prior statin trials supporting cardiovascular disease prevention.

Study phs004021

A_study_of_the_genetic_basis_of_evation_by_Acute_Myeloid_Leukaemia_of_Graft_vs_Leukaemia_effects_after_allogeneic_bone_marrow_transplantation

Acute myeloid leukaemia (AML) is an aggressive and molecularly diverse disease with a poor overall survival of 20-25%. With an annual incidence of 2.9 per 100,000, AML is currently the commonest myeloid malignancy in Europe, yet the two main therapeutic options for this disease, anthracyclines and purine analogues, have remained unchanged for over 20 years. Currently patients are stratified at diagnosis according to a series of clinicopathological parameters (e.g. age, white cell count and presence/absence of previous clonal haematological disease) and molecular markers (e.g. chromosomal translocations/deletions, aneuploidy and mutations in genes such as FLT3 and NPM1). Patients with adverse prognostic features, whose prognosis is particularly poor (e.g. <15% long-term survival) are offered treatment with allogeneic bone marrow transplantation (allo-BMT) if a sibling or unrelated donor is available. This can significantly improve survival (e.g. up to 40% long-term survival in some contexts), albeit at the expense of significant toxicity and transplant-related mortality (TRM). Allo-BMT is thought to work in part by allowing the delivery of large doses of chemotherapy followed by haemopoietic "rescue" with donor haemopoietic stem cells (haemopoietic failure would otherwise ensue). However, potentially the most potent effect of allo-BMT is the cytotoxic effect of donor lymphocytes against AML blasts, a phenomenon known as graft-vs-leukaemia (GVL) effect. Increasingly, transplants using reduced chemotherapy intensity (mini-allografts) are being used that partially circumvent the toxicity from chemotherapy and rely on GVL to effect cure. Nevertheless, AML relapse after allo-BMT still occurs at a significant rate of up to 80% depending on the type of transplant. There is accumulating evidence that genetic events in residual leukaemic cells enable them to evade immunodetection and therefore survive the GVL effect and expand to cause relapse. The most striking example of this is the loss of HLA antigens after transplants in which donor and recipient are not fully HLA-matched. In these cases, the leukaemia "deletes" the genomic region containing the disparate HLA antigen which was preferentially targeted as "foreign" by the GVL effect. However, the genetic basis of immune evasion in the majority of transplants, which are fully HLA matched, is not known. One possibility is that loss of genes coding for antigens outside the HLA locus but which are also targets of GVL may operate, alternatively genetic events that affect processes downstream of immunological cytotoxicity may be responsible.The identification of genetic events that mediate immune evasion would not only facilitate the understanding of this process but can help plan therapeutic interventions that improve the outcomes of allogeneic transplantation for AML and other disorders. We intend to study this by conducting exome sequencing on 6 cases of AMLs from patients that attend my clinic at Addenbrooke's hospital and have relapsed after allogeneic transplantation. Samples from AML diagnosis, remission/normal and AML relapse (total n=18) will be studied to identify somatic mutations in the primary AML and those acquired by the relapsed clone. The 18 samples will also be studied by array CGH to detect regions of genomic amplification or deletion.

Study EGAS00001000145

eMERGE Network Phase III: HRC SNV and 1000 Genomes SV Imputed Array Data of 105,000 Participants

The Electronic Medical Records and Genomics (eMERGE) Network is a National Institutes of Health (NIH)-organized and funded consortium of U.S. medical research institutions. The primary goal of the eMERGE Network is to develop, disseminate, and apply approaches to research that combine biorepositories with electronic medical record (EMR) systems for genomic discovery and genomic medicine implementation research. eMERGE was announced in June 2007 and began its third phase in September 2015. eMERGE Phase III (June 2015 - June 2020) consists of 10 study sites, two central sequencing and genotyping facilities, and a coordinating center. Included in this study are: Human Reference Consortium (HRC) single nucleotide variants and 1000 Genomes structural variants imputed array data of 105,108 eMERGE participants from nine Phase III study sites and three Phase II study site collaborators. Corresponding demographics, body mass index measurements. Case/control status for the following phenotypes: Abdominal aortic aneurysm; Ace-Inhibitor/Cough; Attention Deficit Hyperactivity Disorder; Age-related macular disease; Appendicitis; Asthma; Atopic Dermatitis; Autism; Benign Prostatic Hyperplasia; Carotid artery disease as a Quantitative Measure; caMRSA; Cataract; Clostridium difficile colitis; Extreme Obesity; Chronic Kidney Disease; Chronic Kidney Disease and Type 2 Diabetes; Chronic Kidney Disease, Type 2 Diabetes and Hypertension; Colon Polyps; Cardiorespiratory Fitness; Dementia; Diverticulosis; Diabetic retinopathy; Gastroesophageal Reflux Disease; Glaucoma; Height; Heart failure; Hypothyroidism; Lipids; Ocular hypertension; Peripheral Arterial Disease; QRS duration; Red blood cell indices; Remission of Diabetes after ROUX-EN-Y gastric bypass surgery; Resistant hypertension; MACE while on Statins; Type 2 Diabetes; Venous Thromboembolism; White blood cell indices; and Zoster virus infection. Study sites and participants include: Boston Children's Hospital: The Gene Partnership (TGP) is a prospective longitudinal registry at Boston Children's Hospital (BCH) to study the genetic and environmental contributions to childhood health and disease, collect genetic information on a large number of children who have been phenotyped, and implement the Informed Cohort and the Informed Cohort Oversight Board (ICOB). The term "The Gene Partnership" reflects a partnership between researchers and participants. Children seen at BCH are offered enrollment, as are their parents and siblings. DNA is collected on all enrollees. BCH has a comprehensive EMR system, and virtually all inpatient and outpatient data are captured electronically. Clinical data in the BCH EMR is loaded in the i2b2 data warehouse which is available to investigators. Cases, phenotypes, and covariates are ascertained using the i2b2 database. Participants at BCH in TGP have consented to receive any research result and/or incidental finding that arises from studies using TGP that is approved by the Informed Cohort Oversight Board (ICOB) and is in accordance with the participants'preferences;results are returned through the Personally Controlled Health Record (PCHR). BCH and Cincinnati Children's Hospital Medical Center (CCHMC) have partnered as the Pediatric Alliance for Genomic and Electronic Medical Record (EMR) Research (PAGER) site for the eMERGE Phase II network for pediatric institutions, and the cohort for eMERGE at BCH is TGP. Children's Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children's Hospital of Philadelphia (CHOP) is a high-throughput, highly automated genotyping and sequencing facility equipped with state-of-the-art genotyping and sequencing platforms. Children who are treated at the Children's Hospital Healthcare Network and their parents may be eligible to take part in a major initiative to collect more than 100,000 blood samples, covering a wide range of pediatric diseases. A large majority of participants consenting to prospective genomic analyses also consent to analysis of their de-identified electronic health records (EHRs). EHRs are longitudinal, with a mean duration of 6.5 years. Cincinnati Children's Hospital Medical Center/Boston's Children's Hospital (CCHMC/BCH): Cincinnati Children's Hospital Medical Center (CCHMC) is a pediatric institution dedicated to improving health and welfare of children and to the discovery and practical application of new genomic information to the ordinary care of children. CCHMC brings an extraordinary faculty to eMERGE III who are committed to gain a better understanding of the genesis of disease and to elucidate the mechanisms of diseases that afflict children, specifically pediatric disease phenotypes that will leverage the available eMERGE adult genomic data and electronic medical records (EMRs) to discover meaningful use results. Generation of EMR phenotype algorithms, informed by natural language processing, using heuristic and machine learning methods is ongoing. CCHMC has developed tools to evaluate adolescent return of results preferences, examined the ethical and legal obligations and potential to reanalyze results, and developed clinical decision support for phenotyping, test ordering, and returning sequencing results. The success of these eMERGE III studies is enhanced by the ongoing institutional investment made in the CCHMC Biobank, the comprehensive EMR (EPIC), the i2b2 de-identified medical record data warehouse, and hundreds of faculty and senior staff who make genomics or informatics an active focus of their research. Columbia University: Columbia University Medical Center/New York Presbyterian (CUMC/NYP) Hospital system is one of the nation's largest and most comprehensive hospital systems with over 2 million inpatient and outpatient yearly visits that serves a racially and ethnically diverse urban patient population. The Columbia University GENomic Integration with EHR (GENIE) research study contributed and shared phenotype and genotype data for individuals who were recruited as part of a diverse array of initiatives within the hospital, including Northern Manhattan Study (NOMAS), Pediatric Cardiac Genomic Consortium (PCGC), Caribbean Hispanics with Familial and Sporadic Late Onset Alzheimer's disease (AD), Alzheimer's Disease Sequencing Project (ADSP), and Genetics of Chronic Kidney Disease study. Some of these individuals had kidney or neurological problems, some were healthy adult volunteers with self-reported health status information from the medically underserved Northern Manhattan community, and others were pediatric patients with cardiac conditions. For the kidney disease cohort, patients with the diagnosis of Chronic Kidney Disease (CKD) and healthy controls were recruited to the Columbia University CKD biobank. For the NOMAS cohort, eligible participants were stroke-free, were 40 years old, and resided for at least 3 months in a Northern Manhattan household with a telephone. The PCGC study recruited parent-offspring trios with pediatric probands diagnosed with congenital heart defects (CHD). For the Caribbean Hispanics with Alzheimer's disease project, individuals from families affected by AD and with sporadic AD were recruited, along with unrelated controls. Samples for the ADSP study have been selected from well-characterized cohorts of individuals with AD diagnosis. Geisinger Health System: A research cohort of adult Geisinger Clinic patients was enrolled from community-based primary care clinics of the Geisinger Health System. Patients were eligible for enrollment if they were a primary care patient of a Geisinger Clinic physician and were scheduled for a non-emergent clinic visit. All participants provided written informed consent and HIPAA authorization. Consenting patients agreed to provide blood samples for broad biomedical research use, and permission to access data in their Geisinger electronic medical record for research. The enrollment rate was 90% of patients approached. The demographics of the cohort approximate those of the Geisinger Clinic outpatient population. Research blood samples were collected during an outpatient clinical phlebotomy encounter. Research blood samples are coded and stored in a central biorepository. Samples are linkable to clinical data in a de-identified manner for research via an IRB-approved data broker process. For genomic analysis, DNA is extracted from EDTA-anticoagulated whole blood. Partners Health Care (Harvard): The Partners HealthCare Biobank is a large research program designed to help researchers understand how people's health is affected by their genes, lifestyle, and environment. This large research data and sample repository provides access to high-quality, consented blood samples to help foster research, advance our understanding of the causes of common diseases, and advance the practice of medicine. For the Partners research community (Massachusetts General Hospital and Brigham and Women's Hospital), the Biobank provides: Banked samples (plasma, serum, and DNA) collected from consented patients Blood samples that were discarded after clinical testing in the Crimson Cores maintained in the Brigham and Women's Hospital and Massachusetts General Hospital Pathology Departments Sample handling and preparation services Link to the biobank data to the Partners Research Patient Data Registry (RPDR) a research instance of our electronic clinical chart Data access through our research portal. To date, over 60,000 Partners patients have given their consent to enroll, give a blood sample, receive research results and agreed to be re-contacted for additional research studies. The Biobank has enabled Partners investigators to compete for nationally recognized grants in personalized medicine such as a clinical electronic Medical Records and Genomics network (eMERGE) site and the national All of US program. The Biobank currently supports over 120 Partners investigators and over 100 million dollars in NIH research. Kaiser Permanente Washington with the University of Washington and the Fred Hutchinson Cancer Research Center: KPWA participants were enrolled in the eMERGE Network through the Northwest Institute of Genetic Medicine (NWIGM) biorepository, and provided the appropriate consent to receive clinically relevant genetic results (N~8,073.) NWIGM is based at the University of Washington and co-managed by the University of Washington and KPWA. The purpose of the NWIGM biorepository is to build infrastructure and resources to carry out a broad range of future genetic research. KPWA members enrolled in the biorepository are asked to provide informed consent to providing a DNA sample for storage in the NWIGM biorepository. The consent is purposefully broad to serve the dual purpose of reducing the burden on researchers who wish to use this biorepository and the IRB committees who will be responsible for reviewing these requests in the future. Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in KPWA's integrated group practice, and had completed an online Health Risk Appraisal. The selection algorithm was based on several data sources from the EHR at KPWA. 1) Demographics - participants with self-reported race as Asian ancestry were prioritized and selected to enrich for non-European ancestry. The KPWA eMERGE cohort includes n=1,245 members of Asian ancestry. 2) Participants were also selected for a history of colorectal cancer (n=1,002), in order to allow us to enrich germline pathogenic variants. Essentia Institute of Rural Health, Marshfield Clinic, Pennsylvania State University (Marshfield): The Marshfield Clinic Personalized Medicine Research Project is a population-based biobank in central Wisconsin with more than 20,000 adult subjects who provided written, informed consent to access their medical records and provided a blood sample from which DNA was extracted and plasma and serum stored. In addition to an average of 30 years of medical history data, a questionnaire about environmental exposures, including a detailed food frequency questionnaire, is available to facilitate gene/environment studies. Mayo Clinic: The Mayo Vascular Disease Biorepository is a disease-specific biobank for vascular diseases including peripheral arterial disease (PAD). PAD patients were identified from individuals referred to the non-invasive vascular laboratory for lower extremity arterial evaluation. Since 1997, laboratory findings have been recorded into an electronic database employing an in-house software package for data archiving and retrieval;this data becomes part of the Mayo EMR. Patients referred to the center with suspected PAD undergo a comprehensive non-invasive evaluation including the ankle-brachial index (ABI) - the ratio of blood pressure measured in the upper arms divided by blood pressure measured at the ankles. Controls subjects are identified from patients referred to the Cardiovascular Health Clinic for stress ECG. The prevalence of PAD in patients with normal exercise capacity who do not have inducible ischemia on the stress ECG , was <1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR. Case control study of venous thromboembolism (PI John Heit) Controls from a case control study of pancreatic cancer (PI Gloria Petersen) Mayo Clinic Biobank. Icahn School of Medicine at Mount Sinai School (Mt. Sinai): The Institute for Personalized Medicine (IPM) Biobank Project is a consented, EMR-linked medical care setting biorepository of the Mount Sinai Medical Center (MSMC) drawing from a population of over 70,000 inpatients and 800,000 outpatient visits annually. MSMC serves diverse local communities of upper Manhattan, including Central Harlem (86% African American), East Harlem (88% Hispanic Latino), and Upper East Side (88% Caucasian/white) with broad health disparities. IPM Biobank populations include 28% African American (AA), 38% Hispanic Latino (HL) predominantly of Caribbean origin, 23% Caucasian/White (CW). IPM Biobank disease burden is reflective of health disparities with broad public health impact: average body mass index of 28.9 and frequencies of hypertension (55%), hypercholesterolemia (32%), diabetes (30%), coronary artery disease (25%), chronic kidney disease (23%), among others. Biobank operations are fully integrated in clinical care processes, including direct recruitment from clinical sites, waiting areas and phlebotomy stations by dedicated Biobank recruiters independent of clinical care providers, prior to or following a clinician standard of care visit. Recruitment currently occurs at a broad spectrum of over 30 clinical care sites. Northwestern University: 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 self-reported questionnaire 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 Medical Center: BioVU, Vanderbilt's DNA databank, was designed as an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses. 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. BioVU is currently the largest single site DNA collection world-wide, at >235,000 samples as of spring 2017.

Study phs001584

A Genome-Wide Association Study in Breast Cancer Patients from the Prospectively Randomized SUCCESS Trial

The SUCCESS-A Study (http://www.success-studie.de) is a randomized Phase III study of response to treatment of early primary breast cancer with adjuvant therapy after surgical resection. The primary outcome is disease-free survival and secondary outcomes are overall survival and toxicity. The study design includes comparison of two pairs of treatment regimes performed in sequence. The first randomization contrasts treatment with and without Gemcitabine (3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC)-chemotherapy, followed by 3 cycles of Docetaxel(D)-chemotherapy versus 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC), followed by 3 cycles of Gemcitabine-Docetaxel(DG)-chemotherapy). The second randomization contrasts treatment with Zoledronate for two versus five years. Patients were recruited from 2005 to 2007 and a total of 3754 patients were included from 250 study sites across Germany. Genome-wide SNP microarray data and phenotype outcomes for the first phase of the study (treatment with and without Gemcitabine) are included in the GARNET (Genomics and Randomized Trials Network) pharmacogenomic study in this dbGaP submission. (The Zoledronate treatments are still underway). SUCCESS-A is a an open-label, multicenter, 2x2 factorial design, randomized controlled, Phase III study comparing the disease free survival after randomization in patients treated with 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC)-chemotherapy, followed by 3 cycles of Docetaxel(D)-chemotherapy versus 3 cycles of Epirubicin-Fluorouracil-Cyclophosphamide(FEC), followed by 3 cycles of Gemcitabine-Docetaxel(DG)-chemotherapy, and to compare the disease free survival after randomization in patients treated with 2 years of Zoledronate versus 5 years of Zoledronate in patients with early primary breast cancer. Patients were required to have histopathological proof of axillary lymph node metastases (pN1-3) or high risk node negative, defined as: pT>2 or histopathological grade 3, or age , ≤ 35 or negative hormone receptor, but were not allowed to have evidence of distant disease. Patients were entered into the study no later than 6 weeks after complete resection of the primary tumor. No antineoplastic treatment other than surgical treatment, the defined cytotoxic and endocrine treatment, and radiotherapy was allowed prior to study entry and during the course of the study. After surgery, leading to complete resection of the invasive and intraductal components of the primary tumor, patients were randomized to one of the following two treatments for the first phase of the project (which is included in this GARNET pharmacogenomics study): AA: 3 cycles of 5-Fluorouracil 500 mg/m² i.v. body surface area and Epirubicin 100 mg/m² i.v. and Cyclophosphamide 500 mg/m² i.v., (FEC100), each administered on day 1, repeated on day 22, subsequently followed by 3 cycles of Docetaxel 75 mg/m² body surface area i.v. (D), and Gemcitabine 1000 mg/m² i.v. (30 min infusion) (G), administered on day 1, followed by Gemcitabine 1000 mg/m² i.v. (30 min infusion) on day 8, repeated on day22 AB: 3 cycles of 5-Fluorouracil 500 mg/m² i.v. body surface area and Epirubicin 100 mg/m² i.v. and Cyclophosphamide 500 mg/m² i.v., (FEC100), each administered on day 1, repeated on day 22, subsequently followed by 3 cycles of Docetaxel 100 mg/m² body surface area i.v. (D), administered on day 1, repeated on day 22 A second randomization was made for assigning patients to one of the following two subsequent treatments for the second phase of the project (NOT included in the pharmacogenetic study in this dbGaP submission): BA: Zoledronic acid 4 mg i.v., every 3 months for the duration of two years, subsequently followed by zoledronic acid 4 mg i.v., every 6 months for the duration of additional three years BB: Zoledronic acid 4 mg i.v., every 3 months for the duration of two years Patients with positive hormone receptor status (≥10% positively stained cells for estrogen and/or progesterone) of the primary tumor were recommended to receive Tamoxifen treatment 20 mg p.o. per day for 2 years, after the end of chemotherapy . Subsequent to chemotherapy, postmenopausal patients with positive hormone receptor status were recommended to be treated with Anastrozole (Arimidex®) 1 mg p.o. for additional 3 years, premenopausal patients will continue Tamoxifen treatment for those additional 3 years. In addition to tamoxifen, all patients with positive hormone receptor status of the primary tumor and under the age of 40 or restart of menstrual bleeding within 6 months after the completion of cytostatic treatment or with premenopausal hormone levels as defined below were recommended to receive Goserelin (Zoladex®) 3.6 mg subcutaneously every 4 weeks over a period of 2 years following chemotherapy. Premenopausal endocrine status will be assumed, if the following serum levels are met: LH < 20 mIE/ml, FSH < 20 mIE/ml and E2 > 20 pg/ml. Endocrine therapy will start after the end of chemotherapy. All patients with breast conserving therapy or more than 3 axillary lymph node metastases or in the following cases after mastectomy will receive adjuvant radiotherapy: T3/T4-carcinoma, T2-carcinoma > 3 cm, multicentric tumor growth, lymphangiosis carcinomatosa or vessel involvement, involvement of the pectoralis fascia or a safety margin < 5 mm. Radiotherapy was usually performed after the chemotherapy and parallel to the beginning of the zoledronic acid therapy. Initially, DNA was extracted for performing SNP microarray assays using blood collected at baseline prior to the first randomization. However, the first set of SNP microarray results indicated a quality problem with approximately 50% of the DNA samples. A majority of the problematic samples were replaced with DNA extracted from redrawn blood. The remaining problematic samples were 'restored' using an Illumina FFPE Restoration procedure. A total of 3322 subjects (1638 from arm AA and 1684 from arm AB) were successfully genotyped. Among those, 1771 were from original blood samples, 1092 from redrawn blood samples and 459 from restored blood samples. The SUCCESS-A study is part of the Genomics and Randomized Trials Network (GARNET, http://www.garnetstudy.org) funded by the National Human Genome Research Institute (NHGRI). The overarching goal is to identify novel genetic factors that contribute to disease-free survival for breast cancer patients using different forms of chemotherapy through large-scale genome-wide association studies of treatment response in randomized clinical trials. The study was conducted at the University Hospital Erlangen, Friedrich-Alexander University Erlangen-Nuremberg, Germany. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were performed at the GARNET Coordinating Center at the University of Washington.

Study phs000547

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

Distribution of data using Live Distribution

Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_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 EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys 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_OUTBOX_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 access/download/files/live-outbox

Treatment of Pulmonary Hypertension and Sickle Cell Disease with Sildenafil Therapy (Walk-PHaSST)

Pulmonary arterial hypertension (PAH) is a progressive condition characterized by narrowing or stiffening pulmonary arterioles resulting in increased pulmonary blood pressure and reduced delivery of oxygenated blood to the body. It is a common complication of sickle cell disease and initially presents with the symptom of shortness of breath (dyspnea) on exertion. As the condition worsens, other symptoms such as dizziness, lower extremity edema, and chest pain can develop. The drug, sildenafil, works by relaxing blood vessels in the lungs which reduces pulmonary blood pressure and allows more oxygenated blood to circulate. Increased levels of oxygenated blood allows individuals with PAH to tolerate more activity, but guidelines for using sildenafil in patients with PAH and sickle cell disease were unavailable at the time of the Walk-PHaSST trial.Participants were screened for the existence of pulmonary hypertension with a six minute walk test and a Doppler echocardiogram that assessed TRV, diastolic function, and valvular and systolic function. Subjects with TRV ≥ 2.7 m/s received further clinical evaluation for possible causes of pulmonary hypertension. Other screening data included medical history, a physical exam, and standard laboratory testing. For individuals with moderate to severe pulmonary hypertension (TRV ≥ 3.0), a cardiac catheterization was done at the baseline and week 16 data collection periods.Subjects eligible for the main intervention trial based on screening results were randomized in a 1:1 double blind fashion to receive sildenafil or placebo for 16 weeks. Subjects received 20 mg of oral sildenafil or matching placebo 3 times daily for 6 weeks, followed by 40 mg 3 times daily for 4 weeks, followed by 80 mg 3 times daily for 6 weeks, as tolerated. Participants could also receive other therapies as needed to manage sickle cell and related complications. The primary outcome measure of the trial was change in the six minute walk test, a standard indicator of a person's heart and lung function and exercise capacity, from baseline to week 16. After completing the study treatment (or placebo), participants could choose to be part of the open-label follow-up phase of the study and continue to be assessed for up to one year.The study was intended to screen about 1000 subjects and randomize 132 subjects, however it was terminated early due to the unforeseen increase in adverse events in participants treated with sildenafil as compared to placebo. When the study was stopped, 33 participants had completed the trial. Subjects continued to be monitored, but were instructed to taper sildenafil treatment over three to seven days.There was no evidence that treatment with sildenafil impacted the six minute walk distance from baseline to week 16. In addition, treatment with sildenafil appeared to increase rates of hospitalization due to sickle cell disease pain.Due to in part to the early termination of the trial, the majority of subject data was collected from the screening phase of the study (n=720), as opposed to the main intervention trial (n=74).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 phs002383

A Genomic Approach to Warfarin Dose Prescription in Admixed Caribbean Hispanics

Warfarin is an oral anticoagulant and one of the most used drugs in the world accounting for up to 1.5% of prescriptions globally. Warfarin inhibits vitamin K epoxide reductase complex 1 (VKORC1), an enzyme responsible for the vitamin K recycling that is required for the activation of clotting factors. Warfarin is prescribed at an average dose of 5 mg/day for most of the indications but significant inter-patient variability has been observed. Single nucleotide variations at the VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559) genes alone explain from 28 to 35% of variability in warfarin dose requirements and up to 56% when clinical factors (age, gender, body surface area, diabetes and heart valve) are incorporated into regression analysis. However, genetic-guided dosing algorithms are mostly derived from studies in Europeans. The objective of the present study was to identify genetic polymorphisms that can explain variability in warfarin dose requirements among Caribbean Hispanics of Puerto Rico. VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559), the most important genetic predictors of warfarin response, were sequenced using Next Generation sequencing. Other candidate genes in DMET Plus Assay were assessed to identify genetic variants with relevance in warfarin dose requirements among Puerto Ricans. Our study used the Extreme Discordant Phenotype approach to perform a case-control association analysis that were confirmed with univariate and conditioned regressions. Accordingly, patients were stratified based on stable warfarin doses as sensitive (<4 mg/day), control (4-6 mg/day) and resistant (>6 mg/day). Genetic variants associated with warfarin response among the study cohort were used to perform a multivariate regression analyses to develop a genetic-guided dosing algorithm tailored for Puerto Ricans. The CYP2C9rs2860905 SNP was found to be strongly associated with warfarin dose requirements in Puerto Ricans. The CYP2C9 rs2860905 SNP tags four haplotypes that represent the trihybrid admixture of Puerto Ricans. Therefore, haplotypes harboring the rs2860905 variant are more informative in predicting warfarin dose among Puerto Ricans than the common single segregating SNPs (i.e., CYP2C9*2 and CYP2C9*3) relevant to Europeans. DMET Plus array confirmed the strong association of VKORC1 (GeneID: 79001) and CYP2C9 (GeneID: 1559) with warfarin dose requirements, but also identified other polymorphisms in CES2 (GeneID: 8824) and ABCB1 (GeneID: 5243) associated with warfarin resistance (>6 mg/day). Ancestry analysis showed that Puerto Ricans from Veteran Affairs Caribbean Healthcare System (VACHS) using warfarin had higher Native American proportions than Puerto Ricans from the 1000 Genomes project; however, this difference was not significant. Incorporation of rs2860905 in a regression model (R2=0.60 MSE=0.38) that also included additional genetic predictors (i.e., VKORC1-1639G>A; CYP2C9 rs1856908; ABCB1 rs10276036; CES2 rs4783745) and non-genetic factors (i.e., hypertension, diabetes and age) showed better prediction of warfarin dose requirements than CYP2C9*2 and CYP2C9*3 combined (partial R2=0.132 versus 0.023 and 0.007, respectively, p<0.001). Interestingly, deep vein thrombosis and diabetes were found associated with high warfarin dose requirements among Puerto Ricans. Our results support the use of CYP2C9 rs2860905 along with other genetic markers [e.g., VKORC1(GeneID: 79001 )] and clinical covariates to predict warfarin dose in Puerto Ricans. Although our findings need further replication, this study contributes to the field of Pharmacogenetics and to improve anticoagulation therapy among Puerto Ricans.

Study phs001496

1567 results for "Sweden+NDA+enforceability+one+party+signed"

in 19.70 milliseconds.