10994 results for "fc 26 best way to get coins Visit Buyfc26coins.com Gyors és hatékony szolgáltatás. Hamarosan visszatérek több FC 26 érmeért..4w1a"

in 17.59 milliseconds.

• Genome-Wide Association Studies of Prematurity and Its Complications

  Preterm labor resulting in the delivery of a premature child is a complex problem with an enormous impact on individuals, families and society. An estimated 500,000 children are born prematurely in the U.S. each year, and 5 million worldwide die annually of prematurity and its complications. Prematurity is also the single largest contributor to disability-adjusted life years, a measure of the lifetime impact of a disease. Despite the importance of the problem and its disproportionate occurrence in poor and minority populations, its underlying etiology (or etiologies) remains unknown; the single best predictor for preterm delivery is a previous preterm birth. The largest single cause of prematurity is spontaneous preterm labor, and suspected triggers for this include infection, stress, poor nutrition and genetic factors. Family and twin studies provide strong evidence that genetic factors underlie about 40% of the risk for prematurity. A major challenge in studying genetic factors in prematurity is maternal/uterine factors, fetal/placental factors, or both may influence risk. Thus, any approach to studying preterm birth should account for both infant and maternal risk, environmental covariates and interactions. The Danish National Birth Cohort (DNBC) is a well-established, prospective cohort that enrolled women early in pregnancy, prior to any adverse pregnancy outcomes, to minimize bias in data collection and sampling. See details at: http://www.ssi.dk/English. The DNBC followed over 100,000 pregnancies beginning in the first trimester and has extensive biological material and epidemiologic data on health outcomes in both mother and child. The current study posted on dbGaP contains data from a genome-wide case/control study using approximately 1,000 preterm mother-child pairs from the DNBC most with spontaneous onset of labor or preterm premature rupture of membranes (PPROM), along with 1,000 control pairs where the child was born at ~40 weeks' gestation. After data cleaning some small changes in case/control status and other variables resulted in minor changes in numbers of cases or controls in certain categories. Environmental variables are being used as covariates in the analysis. To replicate positive findings, we are using additional mother-child pairs from the DNBC and from the general Danish population, as well as 2200 samples coming primarily from an African-American population known to have high rates of preterm labor and delivery. This group includes over 1000 mostly very low birthweight infants, over 500 infant term controls, 326 term mother/baby pairs and 180 preterm mother/baby pairs. The data from these additional cohorts will be available in separate dbGaP postings. The study is expected to yield a better understanding of the biology of parturition, identify common genetic factors that play a role in preterm birth and its complications and suggest environmental modifications that can prolong gestation, with the goal of improving both neonatal and adult outcomes. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to prematurity and its complications through large-scale genome-wide association studies of a well-characterized cohort of Danish mothers and babies. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were done at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000103

• Impact of Respiratory Virus Infections and Bacterial Microbiome Shifts on Lymphocyte and Respiratory Function in Infants Born Prematurely or Full Term

  Public health importance: Babies born preterm, approximately 1 out of every 9 live births in the United States, have significant respiratory morbidity over the first two years of life, exacerbated by respiratory viral infections. Many (<50%) return to pediatricians, emergency rooms and pulmonologists with symptoms of respiratory dysfunction (SRD): intermittent or chronic wheezing, poor growth and an excess of upper and lower respiratory tract infections (LRTI). SRD correlate inversely with gestational age and weight at birth and is more common in those with chronic lung disease of prematurity, yet its incidence and severity varies widely among both the prematurely born and those born at term. There is evidence from clinical studies and animal models that risks of LRTI and recurrent wheezing is influenced by gut and respiratory flora and by T cell responses to infection. Information gained from this study will be used to identify characteristics, risk factors and potential mechanisms for early and persistent lung disease in children born at term and born preterm. This Clinical Research Study will investigate the relationships between sequential respiratory viral infections, patterns of intestinal and respiratory bacterial colonization, and adaptive cellular immune phenotypes which are associated with increased susceptibility to respiratory infections and long term respiratory morbidity in preterm and full term infants. We hypothesize that the timing and acquisition of specific viral infections and bacterial species are directly related to respiratory morbidity in the first year of life as defined by SRD and by measures of pulmonary function. We hypothesize that cellular and molecular immuno-maturity are altered due to factors presented by premature birth in such a way as to promote chronic inflammatory and cytotoxic damage to the lung, with subsequent enhanced, damaging responses to infectious agents and environmental irritants. Our preliminary studies demonstrate both feasibility and expertise in mutiparameter immunophenotyping of small volume peripheral blood samples obtained from premature infants including gene expression arrays of flow cytometry sorted cells. We will use new technologies for known viral identification, as well as high-throughput metagenome sequencing of RNA and DNA virus like particles (VLP) to be used for viral discovery in infant respiratory sample and use of high-throughput pyrosequencing (454T) of bacterial 16S rRNA to determine shifts in bacterial community structure, occurring in pre-term (PT) as compared to full term (FT) infants, over the first year of life. Finally, we present statistical approaches to stratify disease risk predictors using multivariate logistic regression modeling approaches. We propose to evaluate T cell phenotypic and functional profiles relative to viral and predominant bacterial exposures according to highly complementary, but independent, Specific Objectives. Objective 1: To determine if viral respiratory infections and patterns of respiratory and gut bacterial community structure (microbiome) in prematurely born babies predict the rate and degree of immunologic maturation, and pulmonary dysfunction, measured from birth to 36 weeks corrected gestational age (CGA). Objective 2: To determine the relationship between respiratory viral infections and disease severity up to one year CGA, and the lymphocyte (Lc) phenotypes documented at term gestation (birth for term infants and 36 wks/NICU discharge in preterm infants) and at one year CGA. Three secondary outcomes of this objective will be to a) relate the quantity, type and severity of viral infections with pulmonary function at one and three years of life, b) relate the viral community structure to severity of viral infections and c) to seek evidence of modulation of viral susceptibility by bacterial respiratory and gut community structure (microbiome). The relationship of colonization with known and non-identified bacterial species in both the respiratory tract and the gut will be evaluated. Flow cytometry data corresponding to this study can be found within Immport study SDY1302. Positive and negative controls for microbiome samples are uploaded under SRA bioproject PRJNA474485. Microbiome samples corresponding to PRISM2 are distinguished from PRISM1 via "_PRISM2" appended to the sample name. Within the positive and negative controls, PRISM1 controls are uploaded as bam files and PRISM2 controls are uploaded as paired fastq. Samples ending in -08 correspond to TLDA qPCR results for a given sample. There is a column for each pathogen tested and a column to indicate where that pathogen was bacteria or virus.

  Study phs001347

• Sickle Cell Disease Implementation Consortium Registry (SCDIC Registry-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 understand the barriers to care and other factors related to reduced healthcare utilization after the transition from pediatric to adult SCD care which may contribute to increased morbidity and mortality.Background: Fifty years ago, it was rare for individuals with SCD to live beyond childhood. Advances in care delivery and treatment have more than doubled the life expectancy of individuals with sickle cell disease (SCD) since 1972. Beginning in the 1970s, measures such as newborn screening, prophylactic administration of penicillin, and immunization against bacterial infections decreased complications and morbidity, increasing the length and quality of life of children with SCD. Blood transfusions are currently the only proven way to prevent some of the major complications of SCD, especially recurrent stroke. They are also used frequently to help manage some of the acute complications of SCD. More recently, the use of hydroxyurea (HU) as a therapeutic agent to increase fetal hemoglobin has been shown to further reduce the debilitating symptoms of and improve survival in SCD. L-glutamine and crizanlizumab are additional treatments to reduce pain crises and voxelotor is approved to lower the risk of anemia and improve blood flow. In the absence of a widely accessible cure, treatment for SCD is usually aimed at avoiding crises, relieving symptoms, and preventing complications. Many of the advances in treatment have not translated into an increase in longevity or quality of life for adolescents and adults because of disparities in access to routine primary health care.Individuals with SCD experience a markedly increased mortality beginning in the second decade of life. The third and later decades of life are frequently associated with severe chronic pain progressive organ damage and frequent hospitalizations. The provision of evidence-based and expert opinion-based care in SCD is complicated by the difficulties that many patients experience in obtaining access to the health care system and in receiving long-term care from knowledgeable providers. A registry of 2,400 people with SCD was established to provide a rich resource to study the natural history of SCD and to understand barriers to care during the transition from pediatric to adult care. Participants: 2,438 participants with a confirmed diagnosis of SCD were enrolled into the registry over an 18-month period. At the time of enrollment, all participants were 15-45 years of age, English speaking, and without a bone marrow transplant.Design: The SCDIC Registry is a longitudinal observational cohort study. At enrollment, data collection included a medical record abstraction of clinical history, the most recent lab results, and a participant survey which included several patient reported outcomes from PROMIS, ASCQ-Me and NeuroQoL. Similar surveys were administered at annual follow-up. Four to five years after enrollment, a second record abstraction was completed with all clinical events that occurred since enrollment and another set of recent labs. There were many research questions proposed to be answered with the study data thus there was no primary outcome.Conclusions: As noted previously, there were no primary outcomes determined at the start of the study. Research questions included examination of co-morbidities, healthcare utilization, and patient reported outcomes. Key findings from the Registry include:Executive dysfunction, learning difficulties, and poor comprehension significantly associated with poor activities of daily living skills. Executive dysfunction also associated with HU non-adherence. Continuing HU after conception increased odds of miscarriage or stillbirth compared to women who were not using HU. Continuing HU after conception increased odds of low birth weight in infants. Compared to adolescents, young adults had significantly more severe pain, organ dysfunction, mental health disorders, sleep problems, and barriers to medical care. Young adults were significantly less likely to see a sickle cell specialist in the past 2 years. Females had higher pain frequency and severity, more pain episodes, anxiety, depression, hospitalizations, and higher fetal hemoglobin levels. Males had more respiratory, musculoskeletal, genitourinary, and cardiovascular complications, more skin ulcers, and more use of HU. Among 128 subjects that died during the study period, iron overload, pulmonary hypertension, and depression, were significant predictors of the risk of death in multivariate analyses.

  Study phs004203

• Acute Respiratory Distress Network Early Versus Delayed Enteral Feeding to Treat People with Acute Lung Injury or Acute Respiratory Distress Syndrome (ARDSNet EDEN-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. Biospecimens: Access to Biospecimens is through the NHLBI Biologic Specimen and Data Repository Information Coordinating Center (BioLINCC). Biospecimens from ARDSNet-EDEN include bronchial lavage, plasma, DNA, and urine. Please note that use of biospecimens in genetic and non-genetic research is subject to a tiered consent. Objectives: To determine if initial lower-volume trophic enteral feeding would increase ventilator-free days (VFDs) and decrease gastrointestinal intolerances compared with initial full enteral feeding. Background: Mechanically ventilated patients cannot eat normally and if not fed for long periods become malnourished. Because malnutrition is associated with poor outcomes in critically ill patients, artificial nutrition is often provided, especially in those with acute lung injury (ALI) and with expected longer duration of mechanical ventilation. When feasible, enteral nutrition targeting full caloric needs has been advocated over parenteral nutrition. However, feeding intolerance and common care practices often serve as practical barriers to reaching recommended goals. Although confounded by indication and severity of illness, several observational studies have shown improved clinical outcomes, including fewer infections, shorter duration of mechanical ventilation, and lower mortality for patients receiving a higher percentage of calculated caloric needs. Nonetheless, the best timing, formulation, and amount of enteral nutrition remain unknown. Participants: A total of 1,000 participants were enrolled. Design: Participants were randomized, stratified by site and presence of shock at enrollment, to receive either trophic or full enteral feeding for the first 6 days of mechanical ventilation. The initial 272 patients were also simultaneously randomized to a separate trial (the OMEGA study) comparing a nutritional supplement containing omega-3 fatty acids and antioxidants with an isocaloric, isovolemic control in a 2 × 2 factorial design.The designated feeding strategy was initiated within 6 hours of randomization and continued until death, extubation, or day 6. The care of mechanically ventilated patients still receiving enteral feedings after day 6 was managed according to the full feeding strategy in both groups. In extubated patients who then required reintubation, enteral nutrition was restarted and managed according to the study protocol.In the full-feeding group, enteral nutrition was initiated at 25 mL/h and advanced to goal rates as quickly as possible. Gastric residual volumes were checked every 6 hours while enteral feeding was increased. Patients randomized to the initial trophic-feeding group had enteral nutrition initiated at 10 mL/h (10-20 kcal/h) for the first 272 patients who also received the omega-3 or control supplement (240 mL volume per day). After the data and safety monitoring board stopped the OMEGA portion of the factorial design, the initial trophic feeding rate was changed to 20 kcal/h to approximate the calories that had been delivered in the OMEGA study. Gastric Residual Volumes (GRVs) were checked every 12 hours during trophic feeding. In patients randomized to trophic feeding, enteral nutrition was advanced to full-energy feeding rates following the same protocol used for the full-feeding group if they were still receiving mechanical ventilation at 144 hours. Conclusions: There was no difference between groups with regard to the primary end point, VFDs to day 28. There also were no differences in 60-day mortality, organ failure−free days, ICU-free days, or the incidence of infection between groups. Similarly, there were no differences between groups in VFDs or survival when analyzed by body mass index category or when subsets of patients with shock or more severe lung injury (acute respiratory distress syndrome) were examined.JAMA. 2012 Feb 22;307(8):795-803

  Study phs004168

• Everything you need to know about Federated EGA Affiliates: Q&A

  Addressing common questions about Federated EGA (FEGA) Affiliates and providing answers. FEGA Affiliates have recently been defined as the third tier within the newly approved “Federated EGA Structure and Organisation” document, alongside Central EGA (CEGA) and the FEGA Nodes. In this blog post, we aim to answer the questions that may arise on this topic. For more general information about FEGA Affiliates, you can refer to this blog post. Let's now start with the questions and answers! What is the difference between a FEGA Affiliate and a FEGA Node? FEGA Nodes A FEGA Node is a national-level service that accepts submissions and provides archiving and access services within a single country's jurisdiction. Nodes provide end-to-end services for submitters in that jurisdiction, including submission support, processing, permissions management, and distribution. FEGA Affiliates A FEGA Affiliate is not a national submission service. Instead, it archives data from its own legal entity and/or selected partner institutions (for example, consortium partners). Affiliates are designed for organisations and consortia that need to keep data stewardship and access decisions within their own governance model, while still enabling discovery through the broader FEGA ecosystem. What do Affiliates commit to? Here is a practical checklist of the core expectations for a FEGA Affiliate. FEGA Affiliate checklist Discovery and metadata Submit non-personal metadata to CEGA to obtain EGA accessions and enable discovery (with metadata validation handled by the CEGA Helpdesk). Operations and resilience Maintain a data storage system and a defined backup/recovery approach. Ensure operational capacity (personnel and infrastructure) to deliver Affiliate services. Maintain systems and practices that support local data security and align with EGA best-practices. Access and user support Provide data distribution or access (e.g in a trusted research environment) to authorised users to datasets hosted at the Affiliate. Provide permissions management for datasets archived by the Affiliate (the CEGA DAC (Data Access Committee) Portal is always at your disposal to use). Provide a minimal helpdesk with sufficient capacity to support relevant DACs and approved users. Membership term Commit to a minimum membership term of four years. Governance and participation (lightweight by design) Affiliates integrate into the FEGA network operationally, but without the committee obligations associated with Nodes. When is becoming an Affiliate the right fit? Consider the Affiliate tier if: You host (or plan to host) controlled-access datasets that must be managed under your organisation’s or consortium’s governance, you want studies to be discoverable through EGA, but need access control and/or distribution to remain local, and you are not aiming to operate a national submission service tier.. What if a FEGA Node already exists in my jurisdiction? We encourage any potential Affiliate to reach out to their national FEGA Node to explore collaboration at the national level. Why? Federated models within a country already exist in FEGA, where a national Node operates like a Central EGA for their country. FEGA Nodes can also represent the interests of any Affiliates within their jurisdiction at the FEGA Committees. FEGA Nodes have experience and can support you on your FEGA journey. Ready to join as a FEGA Affiliate? We’re excited to open this formally defined pathway for organisations and consortia to participate in the federation. If you think the FEGA Affiliate tier fits your needs, start by assessing: Your scope (organisation/consortium-held data rather than public external submissions), Your ability to provide the core services (permissions, distribution/access, helpdesk, monitoring), and Your readiness to submit non-personal metadata to CEGA for accessioning and discovery. To express interest, please contact us here, and we'll help you understand the onboarding steps and how Affiliates integrate into the FEGA network.

  Blog fega-affiliates-q&a

• T2D-GENES Project 2: San Antonio Mexican American Family Studies

  The Type 2 Diabetes (T2D) Genetic Exploration by Next-generation sequencing in Ethnic Samples (T2D-GENES) Consortium is a collaborative international effort to identify genes influencing susceptibility to T2D in multiple ethnic groups using next generation sequencing. T2D-GENES Project 2 is a complex pedigree-based study designed to identify low frequency or rare variants influencing susceptibility to T2D, using whole genome sequence (WGS) information from 1,043 individuals in 20 Mexican American T2D-enriched pedigrees from San Antonio, Texas. The major objectives of this study are to identify low frequency or rare variants in and around known common variant signals for T2D, as well as to find novel low frequency or rare variants influencing susceptibility to T2D. The sampled individuals are obtained from two studies: the San Antonio Family Heart Study (SAFHS) and the San Antonio Family Diabetes/Gallbladder Study (SAFDGS), collectively referred to as the San Antonio Mexican American Family Studies (SAMAFS). The strategy is to sequence approximately 600 individuals at an average of 50x coverage across the entire genome, then impute genome wide genotypes for about 440 additional family members. The 600 sequenced individuals are specifically chosen for their value in imputing sequence information into other family members. By studying large pedigrees, we expect to find multiple individuals carrying each genetic variant, even if this variant is very rare in the population at large. Thus, a pedigree-based approach provides an excellent opportunity for identifying rare novel variants influencing risk of T2D and quantitative variation in T2D-related phenotypes. The whole genome sequencing has been done commercially by Complete Genomics, Inc. (CGI). The final data set includes whole genome sequence data for 607 individuals. After quality control, 585 sequenced individuals provide data for family based imputation, using Merlin linkage analysis software, into approximately 440 additional family members for whom chip based genotypes are available to indicate which parental haplotype is transmitted. Extensive phenotype data is provided for 1048 individuals. These include 5 sequenced individuals who do not belong to any of the 20 large pedigrees. Phenotype information was collected between 1991 and 2011 in the two contributing longitudinal studies. SAFHS participants may have information from up to 5 visits, and SAFDGS participants may have up to 4 visits. The clinical variables reported are coordinated with T2D-GENES Project 1 (multi-ethnic exome sequencing) and include T2D status and age at diagnosis, glycemic traits (fasting and 2 hour glucose and insulin), blood pressure, blood lipids (total cholesterol, HDL cholesterol, calculated LDL cholesterol and triglycerides), clinical chemistry (cystatin c, glutamic acid decarboxylase antibody titer (GadAb), creatinine, adiponectin and leptin). Glycated hemoglobin (HbA1c) was not measured for these individuals and insulin C-peptide is not included in this data set. Additional phenotype data include the medication status at each visit, classified in four categories as any current use of diabetes, hypertension or lipid-lowering medications, and, for females, current use of female hormones. Anthropometric measurements include age, sex, height, weight, hip circumference, waist circumference and derived ratios. Each phenotype variable has an initial summary column containing the most recent non-missing measurement for each individual, followed by the five potential time points for each individual, the number of non-missing measurements, and the age and year for the most recent non-missing measurement. For historical reasons, the order in which variables are presented on the dbGaP web site differs from their order in the data download file. When reading the comment fields for each variable, please note that commas are omitted to support data exchange in .csv format.

  Study phs000462

• Systolic Blood Pressure Intervention Trial (SPRINT-Imaging)

  Available DataSystolic Blood Pressure Intervention Trial, SPRINT-Imaging, provides access to ECG signals data from the SPRINT clinical trial. The clinical phenotyping and outcomes data from the trial are associated with SPRINT-BioLINCC, phs003483.ObjectiveThe Systolic Blood Pressure Trial (SPRINT) was conducted to test the hypothesis that treating systolic blood pressure to a target of less than 120 mm Hg, as compared to a target of less than 140 mm Hg, would reduce the incidence of cardiovascular disease. BackgroundHypertension is a highly prevalent condition among adults and is a leading risk factor for myocardial infarction and stroke. Further, isolated systolic hypertension is the most common form of hypertension in adults over 50 years of age. Observational studies have shown a monotonic increase in cardiovascular risk with systolic blood pressures above 115 mm Hg; however, general population clinical trials have only documented the benefits of lowering systolic blood pressure to a target of 150 mm Hg. A 2007 expert panel sponsored by the National Heart, Lung, and Blood Institute designated the hypothesis that lowering the systolic blood pressure goal to a level SubjectsA total of 9361 participants were enrolled, with 4,678 randomized to the intensive-treatment group and 4,683 randomized to the standard-treatment group. DesignSPRINT was a randomized, single blinded (outcome adjudicators were blinded to treatment assignment) treatment trial with participants randomized to a systolic blood-pressure target of either less than 140 mm Hg (the standard-treatment group) or less than 120 mm Hg (the intensive-treatment group). Following randomization, baseline hypertensive regimens were adjusted in accordance with study treatment algorithms established for each group. The study formulary included all major classes of antihypertensive agents. Investigators could prescribe other antihypertensive medications, but the use of drug classes with the strongest evidence for reduction in cardiovascular outcomes was encouraged. This included thiazide-type diuretics as the first-line agent, loop diuretics for participants with advanced chronic kidney disease, and beta-adrenergic blockers for participants with coronary artery disease. Medications for participants in the intensive-treatment group were adjusted on a monthly basis to target a systolic blood pressure of less than 120 mm Hg. Medications for participants in the standard-treatment group were adjusted to target a systolic blood pressure of 135 to 139 mm Hg, and the dose was reduced if systolic blood pressure was less than 130 mm Hg on a single visit or less than 135 mm Hg on two consecutive visits. Lifestyle modification was encouraged as part of the management strategy. Participants were seen monthly for the first 3 months and every 3 months thereafter. Demographic data were collected at baseline. Clinical and laboratory data were obtained at baseline and every 3 months thereafter. A structured interview was used in both groups every 3 months to obtain self-reported cardiovascular disease outcomes. Medical records and electrocardiograms were obtained for documentation of events. Incidences of hypotension, syncope, injurious falls, electrolyte abnormalities, and bradycardia that were evaluated in an emergency department were included in adverse event reporting. Occurrences of acute kidney injury or acute renal failure requiring hospitalization were also monitored. The primary outcome was a composite outcome of myocardial infarction, other acute coronary syndromes, stroke, heart failure, or death from cardiovascular causes. ConclusionsThe blood pressure intervention was stopped in August of 2015 (median follow-up of 3.26 years) after the cardiovascular outcome results exceeded the boundary for efficacy at two consecutive time points. Compared with a systolic blood pressure target of less than 140 mm Hg, an intensive systolic blood pressure target of 120 mm Hg resulted in lower rates of fatal and nonfatal major cardiovascular events and death from any cause. Significantly higher rates of some adverse events were observed in the intensive-treatment group.

  Study phs003566

• eMERGE Network's Multi-Center Pilot of Pharmacogenetic Sequencing in Clinical Practice

  eMERGE-PGx is a multi-site test of the concept that sequence information can be coupled to electronic medical records (EMRs) for use in healthcare. The promise of personalized medicine - health care guided by each individual's biological characteristics - is being fostered by increasingly powerful and economical methods to acquire clinically relevant biomarkers from large numbers of people. One therapeutic area that seems especially ripe for an early test of the personalized medicine concept is pharmacogenomics (PGx) - the idea that individual variation in drug response includes a genomic component. Drug response variation is an accepted feature of virtually all drug treatments, and contemporary molecular biologic tools continue to identify key genes mediating drug metabolism, transport, and targets. Importantly, common variation in these genes is an increasingly well-recognized contributor, sometimes with large effects, to variation in drug responses. As a result, recommendations for genotype-guided therapy are increasing. These evidence-based recommendations, if implemented in health care practice, could reduce adverse drug events and improve time to therapeutic response. Through eMERGE-PGx, we are developing strategies for the optimal implementation of genetic sequence data into the clinical environment with the ultimate goal of improving patient care. Site and participants include: 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. The PGx population selected for sequencing with the PGRNseq panel at CHOP is 1,650 children from CAG's biorepository with well-documented drug-related severe adverse events (SAEs) or EHR-based drug response profiles. SAEs were extracted from EPIC records and from CHOP's Adverse Event (AE) database, which documents every AE at CHOP. These AEs are classified by a medical review panel according to the causal relationship with the suspected drug into 'doubtful', 'possible', and 'probable'. Individuals with events classified as probable, severe and objective, were selected for sequencing. The drugs more frequently associated with adverse events are antibiotics, antineoplastics, immunosuppressants and psychotropic drugs. This cohort constitutes 50% of the target population. The remaining subjects were selected using EHR-based algorithms that we have developed and validated at CAG for identifying patients not responding to ADHD medication (primarily atomoxetine) and patients refractory to antiepileptic treatment from responders. Cincinnati Children's Hospital Medical Center/Boston's Children's Hospital (CCHMC/BCH): 811 CCHMC samples were obtained from children, adolescents or young adults exposed to medication or at risk for needing medication of study interest. 55% of participants were exposed to one or more opioids and their DNA source was a CCHMC study-specific biobank; while 27% of participants were at risk for needing an opioid for surgical pain management and were newly recruited. The remainder of the cohort was exposed to methylphenidate and their DNA samples were obtained from a CCHMC study-specific biobank. The focus of Boston Children's Hospital eMERGE PGx project is on individuals with epilepsy. Samples were taken from a current pharmacogenomics study already in place through which DMET analysis was run and used as confirmation for PGRN-Seq results. A total of 109 samples were sent for PGRN-Seq analysis at University of Washington. The remaining 141 epilepsy samples were from Children's Hospital of Philadelphia and underwent testing with PGRN-Seq at CHOP. 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 data are from Geisinger patients who consent to participate in the MyCode project. MyCode participants agree to provide biological samples for broad research use, including genomic analysis, and for linking of sample data to information in the participant's Geisinger health record. The consent also permits sharing of de-identified data for research purposes. Group Health(GH)/University of Washington (UW): Potential GH participants for the PGx project 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~6300). Participants were eligible if aged 50 - 65 years old at the time of their enrollment into the NWIGM repository, living, enrolled in GH'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 Group Health: 1. Demographics - participants with self-reported race as Asian or African ancestry were prioritized and selected to enrich for non-European ancestry; 2. Diagnosis and procedure codes - participants were selected if found to have a history of hypertension, atrial fibrillation (AF,) or congestive heart failure (CHF). Participants with a history of arrhythmia were added if the entire selection algorithm did not generate 900 individuals. We also enriched for participants with EHR evidence of actionable indications related to PGRNSeq genes. Participants were selected if found to have an ICD9 code for malignant hyperthermia, hypertension, atrial fibrillation, congestive heart failure or long QT syndrome (LQTS); 3. Laboratory values - if a participant had any laboratory event of creatine kinase (CK) > 1000, and were dispensed statins within 6 months of the event, then they were selected; and 4. Medications - participants were excluded if ever on carbamazepine or had a current regimen of warfarin. Essentia Institute of Rural Health, Marshfield Clinic, Pennsylvania State University (Marshfield): For this study, 750 subjects were selected and enrolled into PGx based on Vanderbilt's algorithm designed to enrich for patients who are most likely to receive one of three common drugs (Clopidogrel, Warfarin or Simvastatin) in the next 2-3 years. These patients were sent a letter of invitation and description of the PGx project. Follow-up phone calls were made, and interested subjects came in for a one time meeting to discuss the project and go through the informed consent with the research coordinator. If they were interested they signed the consent and HIPAA forms and gave blood. Subjects were chosen and enrolled into PGx independently of previous biobank participation. Mayo Clinic: The Right Drug, Right Dose, Right Time - Using Genomic Data to Individualize Treatment (The RIGHT Protocol) enrolled 1013 patients to test the hypothesis that prescribers could deliver genome-guided drug therapy at the point-of-care by using pharmacogenomic data preemptively integrated in the electronic medical record. Complete details regarding the study population have been previously described (Bielinski et al., 2014). Icahn School of Medicine at Mount Sinai School (Mt Sinai): Our study site is the Primary Care Associates (PCA) practice group of the Mount Sinai Faculty Practice Associates (FPA) of the Mount Sinai Medical Center in New York City. This practice has 12 physician providers. All patient encounters are documented and managed with EpicCare ambulatory electronic medical record. Active PCA Patients eligible for enrollment fulfilled the following criteria: a) age 50 or older receiving clinical care at Mount Sinai FPA PCA practice with at least one practice encounter within 18 months prior to commencement of enrollment; b) no history or current use of clopidogrel, warfarin, or simvastatin. Eligible patients were invited to participate through de novo recruitment by letter sent by their provider. Interested patients were screened for eligibility and enrolled to participate in the eMERGE PGX study on site by a dedicated research coordinator. In addition to de novo enrollment from clinical practice, patients of FPA PCA who had previously enrolled in Mount Sinai's BioMe Biobank program AND fulfilled eligibility criteria as stated under a) and b) were identified by chart review and samples sequenced at CIDR using PGRNseq platform (N=300). PGRNseq data from 291 samples passed stringent quality control and are included in the current data set. Furthermore, 56 of these patients carrying known and validated 'actionable' variants affecting prescribing of clopidogrel, warfarin, and/or simvastatin were enrolled in the eMERGE PGX study following invitation through recontacting by the Principal Investigator of the BioMe Program. Northwestern University: Participants for this study were recruited from the General Internal Medicine (GIM) clinic at Northwestern Medical Group (NMG). Patients were selected for invitation to participate if they had been seen a minimum of two times over the last four years, having a high likelihood to receive a prescription for warfarin, Plavix, or a statin, and are seeing a physician who has agreed to allow their patients to be contacted for the study. We utilized an algorithm developed at Vanderbilt and tailored to our population which uses our EHR to estimate the probability that individuals will receive a prescription for warfarin, Plavix, or a statin in the next three years. Participants were sent a letter explaining the study prior to their GIM appointment and offered participation at the time of their visit. Participants were consented on-site and blood drawn after consent was obtained. The GIM clinic consists of 39 primary care physicians who provide approximately 80,000 patient encounters per year. As with any large primary care clinic, a significant proportion of patients in GIM clinic suffer from a variety of chronic health conditions, such as diabetes, hypertension, and coronary artery disease. Over 50,000 individuals have been seen by GIM doctors in the past 5 years; 11,562 of these patients have evidence of a statin prescription in the EHR, 3,436 have evidence of a warfarin prescription, and 1,872 have evidence of a Plavix prescription. Vanderbilt University: The more than 1000 participants enrolled into Vanderbilt's eMERGE PGx study were newly recruited from the Cardiology and Internal Medicine Clinics and the Hillsboro Medical Group within Vanderbilt University Medical Center (VUMC). Patients were selected based on a predictive algorithm estimating the patient's likelihood of receiving Clopidogrel, Warfarin, and/or Simvastatin. The algorithm identifies primarily older middle-aged patients, and the mean age of the study group is 74. The cohort is approximately 45% female with 75% of subjects self-identified as EA and 24% as AA. Subjects were consented in person by study personnel following a routine clinic visit and an introduction to the study staff by their doctor. VUMC is a comprehensive health care facility dedicated to patient care, research, and the education of health care professionals. Translational research into the causes and treatment of disease as well as studying fundamental biological properties is the primary focus of discovery at Vanderbilt. Clinical research is conducted in Vanderbilt University Hospital, the Nashville Veterans Administration Hospital, Meharry General Hospital and in their associated outpatient clinics. These hospitals and clinics, all associated with the Vanderbilt system, each have full time Vanderbilt faculty and medical housestaff and provide clinical care and participate in research programs. The Vanderbilt Clinic is comprised of more than 95 adult outpatient specialty practices and received over 1.5 million ambulatory visits in 2012-13. The Vanderbilt Heart and Vascular Institute offers a comprehensive heart program offering diagnosis, medical treatment, minimally invasive therapies, surgical intervention and disease management, tailored to each individual's unique needs. All programs within the Vanderbilt Clinic have survival figures that surpass the national average.

  Study phs000906

• Systolic Blood Pressure Intervention Trial (SPRINT-BioLINCC)

  Available DataThe available data include all elements of the previously released SPRINT Primary Outcome Paper (SPRINT-POP) data, the full SPRINT clinical data including the MRI and MIND data, and select ancillary study data (Ambulatory Blood Pressure Monitoring, APOL1, Acute Kidney Injury, ASK, Heart, FAST, PWV, Renal Resistance, Biomarkers, Plasma AD).ObjectiveThe Systolic Blood Pressure Trial (SPRINT) was conducted to test the hypothesis that treating systolic blood pressure to a target of less than 120 mm Hg, as compared to a target of less than 140 mm Hg, would reduce the incidence of cardiovascular disease.BackgroundHypertension is a highly prevalent condition among adults and is a leading risk factor for myocardial infarction and stroke. Further, isolated systolic hypertension is the most common form of hypertension in adults over 50 years of age. Observational studies have shown a monotonic increase in cardiovascular risk with systolic blood pressures above 115 mm Hg; however, general population clinical trials have only documented the benefits of lowering systolic blood pressure to a target of 150 mm Hg. A 2007 expert panel sponsored by the National Heart, Lung, and Blood Institute designated the hypothesis that lowering the systolic blood pressure goal to a level SubjectsA total of 9361 participants were enrolled, with 4,678 randomized to the intensive-treatment group and 4,683 randomized to the standard-treatment group.DesignSPRINT was a randomized, single blinded (outcome adjudicators were blinded to treatment assignment) treatment trial with participants randomized to a systolic blood-pressure target of either less than 140 mm Hg (the standard-treatment group) or less than 120 mm Hg (the intensive-treatment group). Following randomization, baseline hypertensive regimens were adjusted in accordance with study treatment algorithms established for each group. The study formulary included all major classes of antihypertensive agents. Investigators could prescribe other antihypertensive medications, but the use of drug classes with the strongest evidence for reduction in cardiovascular outcomes was encouraged. This included thiazide-type diuretics as the first-line agent, loop diuretics for participants with advanced chronic kidney disease, and beta-adrenergic blockers for participants with coronary artery disease. Medications for participants in the intensive-treatment group were adjusted on a monthly basis to target a systolic blood pressure of less than 120 mm Hg. Medications for participants in the standard-treatment group were adjusted to target a systolic blood pressure of 135 to 139 mm Hg, and the dose was reduced if systolic blood pressure was less than 130 mm Hg on a single visit or less than 135 mm Hg on two consecutive visits. Lifestyle modification was encouraged as part of the management strategy.Participants were seen monthly for the first 3 months and every 3 months thereafter. Demographic data were collected at baseline. Clinical and laboratory data were obtained at baseline and every 3 months thereafter. A structured interview was used in both groups every 3 months to obtain self-reported cardiovascular disease outcomes. Medical records and electrocardiograms were obtained for documentation of events. Incidences of hypotension, syncope, injurious falls, electrolyte abnormalities, and bradycardia that were evaluated in an emergency department were included in adverse event reporting. Occurrences of acute kidney injury or acute renal failure requiring hospitalization were also monitored. The primary outcome was a composite outcome of myocardial infarction, other acute coronary syndromes, stroke, heart failure, or death from cardiovascular causes.ConclusionsThe blood pressure intervention was stopped in August of 2015 (median follow-up of 3.26 years) after the cardiovascular outcome results exceeded the boundary for efficacy at two consecutive time points. Compared with a systolic blood pressure target of less than 140 mm Hg, an intensive systolic blood pressure target of 120 mm Hg resulted in lower rates of fatal and nonfatal major cardiovascular events and death from any cause. Significantly higher rates of some adverse events were observed in the intensive-treatment group.

  Study phs003483

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal