6312 results for "fc coins pc Buyfc26coins.com is FC 26 coins official site..T357"

in 24.20 milliseconds.

• San Francisco Bay Area Latina Breast Cancer Study

  The genome-wide association study (GWAS) includes participants enrolled into two different studies. The first study, the San Francisco Bay Area Cancer Study (SFBCS) is a population-based case-control study of breast cancer conducted in the San Francisco Bay Area and included women ages 35-79 years from three racial/ethnic groups: Non-Hispanic whites, African Americans, and Hispanics/Latinas. For the GWAS, only Hispanic/Latina women were included. Women diagnosed with invasive breast cancer between 1995 and 2002 were identified through the Greater Bay Area Cancer Registry. Controls were identified by random digit dialing and were frequency-matched to cases by age in 5 year increments and by race/ethnicity. Hispanic/Latina ethnicity was assessed by self-report. 175 Hispanic/Latina cases and 307 Hispanic/Latina controls from the SFBCS had given adequate consent and provided biospecimens that were used in the GWAS to be included in this data submission. The second study is the Northern California site of the Breast Cancer Family Registry (NC-BCFR). This population-based family study recruited breast cancer cases ages 18-64 years diagnosed from 1995-2009 that were identified through the Greater Bay Area Cancer Registry. Cases included all women at increased genetic susceptibility for breast cancer who met one or more of the following criteria: (a) being diagnosed with breast cancer at age <35 years; b) having a personal history of ovarian cancer or childhood cancer; (c) being diagnosed with two different breast cancers (bilateral breast cancers), with the first one diagnosed at age <50 years; and d) having one or more first-degree relatives with breast cancer, ovarian cancer or childhood cancer. Cases not meeting these criteria were randomly sampled and racial/ethnic minorities were oversampled. Controls were recruited by random digit dialing and were matched by 5-year age increments and by race/ethnicity. For the current GWAS only Latina/Hispanic cases and controls were included. Latina/Hispanic ethnicity was assessed by self-report. 631 Hispanic/Latina cases and 61 Hispanic/Latina controls from the NC-BCFR had given adequate consent and provided biospecimens that were used in the GWAS to be included in this data submission.

  Study phs000912

• Losartan Effects on Emphysema Progression (LEEP-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives To evaluate the efficacy of losartan, an angiotensin receptor blocker, to reduce emphysema progression in patients with COPD and mild to moderate emphysema. Background Chronic obstructive pulmonary disease (COPD) is a heterogeneous disease comprising chronic bronchitis and emphysema. COPD is a major cause of morbidity and mortality. Smoking cessation slows the progression of the disease, and bronchodilators can provide sustained improvement in lung function, but there are no pharmacologic agents that clearly modify emphysema progression. Angiotensin receptor blockers (ARBs) have been suggested as potential drugs to slow the progression of COPD. A few trials have shown that patients treated with ARBs had slower progression of radiographic emphysema. The LEEP study was initiated to test the hypothesis that the ARB losartan would reduce the progression of emphysema in patients with COPD with mild to moderate emphysema.ParticipantsA total of 220 participants were enrolled. 108 participants were randomized to receive losartan, and 112 participants were randomized to receive the placebo.Design LEEP was a randomized, placebo-controlled multicenter trial. Participants were randomly assigned (1:1) to receive losartan or placebo. The dose was 50 mg losartan or placebo given as one capsule daily for 2 weeks, and, if well tolerated and the systolic blood pressure was >90 mm Hg, it was increased to two capsules. Participants and site investigators were masked to treatment assignment. Participant responses to the St George's Respiratory Questionnaire, the modified Medical Research Council dyspnea scale, the COPD Assessment Test, and the Physical Function–Short Form 20a were collected. The number and severity of COPD exacerbations were recorded. COPD exacerbations were defined as two or more new or worse symptoms for ≥3 days and classified by treatment as mild (neither antibiotics nor oral steroids), moderate (an antibiotic or oral steroid), or severe (hospitalization). The primary outcome measure was the change in quantitative whole-lung emphysema score after 48 weeks measured by the percentage of lung voxels less than -950 Hounsfield units (PCT950) on full inspiratory HRCT. Conclusions Losartan does not prevent progression of emphysema in patients with COPD who have mild to moderate pulmonary emphysema.

  Study phs004313

• Whole Exome Sequencing of Congenital Diaphragmatic Hernia Patients and Trios

  Congenital diaphragmatic hernia (CDH) is a common and severe birth defect characterized by structural defects of the diaphragm and by pulmonary hypoplasia. Congenital diaphragmatic hernia patient may present either as an isolated phenotype or together with other congenital anomalies in a complex phenotype. Despite the clinical significance of CDH, the underlying genetic and developmental pathways are incompletely understood. In order to establish a catalog of human genetic variation for this condition, we performed whole exome sequencing (WES) on 275 carefully phenotyped individuals with CDH in the Pediatric Surgical Research Laboratories at the Massachusetts General Hospital (Boston, MA, USA) and Boston Children's Hospital (Boston, MA, USA). The exome data generated are valuable for comparison of candidate genes derived from WES of other CDH cohorts or affected kindreds, and to provide ideal candidates for further functional studies with the ultimate goal of enhancing our understanding of the heterogeneous and, possibly, oligogenic molecular etiology of CDH. While familial clustering has been reported in rare kindreds, the majority of probands with CDH have no family history of CDH leading to the hypothesis that de novo variants are an important and relatively frequent etiological mechanism. In the second version of the study, we performed WES analysis on 87 trios, to assess the contribution of de novo mutations in the etiology of diaphragmatic and pulmonary defects and to identify previously unknown candidate genes. This dbGaP submission includes WES data on: (a) 20 new probands, (b) 9 probands also reported in the previous version (dbGaP accession no. phs000783.v1.p1), (c) 174 unaffected parents, including the parents of 67 previously reported probands. Combined analysis with other available cohorts of congenital diaphragmatic hernia revealed a genome-wide enrichment of likely gene-disrupting de novo variants (i.e., nonsense, frameshift or splice site), and missense de novo variants predicted in silico to be damaging.

  Study phs000783

• 10x Genomics raw data of intestinal plasma cells

  The dataset contains raw fastq files (fastq.gz) for Chromium Single Cell 5’ gene expression (GEX), human B cell VDJ and feature barcode (CSP) sequencing from transglutaminase 2-specific and other small intestinal plasma cells isolated from four untreated celiac disease patients. Single cell 5’ gene expression, V(D)J-enriched and cell surface protein libraries were generated using Chromium single cell kits, and barcoded cDNA from a total of 5,000-10,000 cells per sample was generated using the 10x Genomics Chromium Controller. The libraries were pooled prior to sequencing on a NovaSeq 6000 instrument (Illumina) using the following configuration: read 1: 26 cycles, read 2: 89 cycles, index read 1: 8 cycles.

  Dataset EGAD50000000342

• ICR96 exon CNV validation series

  A resource for assessment of exon CNV calling methods in targeted NGS data, we here present the ICR96 exon CNV validation series. The dataset includes high-quality sequencing data from a targeted NGS assay (the TruSight Cancer Panel) together with Multiplex Ligation-dependent Probe Amplification (MLPA) results for 96 independent samples. 66 samples contain at least one validated exon CNV and 30 samples have validated negative results for exon CNVs in 26 genes. The dataset includes 46 exon CNVs in BRCA1, BRCA2, TP53, MLH1, MSH2, MSH6, PMS2, EPCAM and PTEN, giving excellent representation of the cancer predisposition genes most frequently tested in clinical practice. Moreover, the validated exon CNVs include 25 single exon CNVs the most difficult exon CNV to detect.

  Dataset EGAD00001003335

• FEGA and European GDI: working together to improve human health

  The Federated EGA is a global resource for discovery of and access to sensitive human omics and associated data consented for secondary use, through a network of human data repositories to accelerate biomedical research and improve human health. The Federated EGA network was launched in September 2022 with five inaugural nodes, and since 2023 seven operational nodes can share data across national borders in adherence to European and national laws. A few weeks after FEGA's official launch, in November 2022, the European Genomic Data Infrastructure (GDI) project was kicked-off . This European Commission co-funded project, coordinated by ELIXIR, is aimed to deliver federated, sustainable and secure data infrastructure to access genomic and related phenotypic and clinical data across Europe. This project supports the aim of the 1+MG initiative (25 EU countries, Norway and UK) to enable personalised medicine and health through a shared framework and infrastructure for securely accessing and integrating high quality genomic data and other health data across borders.1+MG will be an integral component of the European Health Data Space (EHDS) for secondary use (Healthdata@EU) as an authorised participant. How are Federated EGA and GDI similar? Given their shared visions, the Federated EGA and European GDI networks have a lot in common. To begin, they share the same overall goal of establishing networks of “nodes” that host sensitive human data within a jurisdiction and connecting these nodes in a global network to support data discovery and promote human genome data access for research and healthcare. FEGA and GDI are both initially focused on enabling access to human genomic data, while FEGA ambition is to expand the scope to clinical research data and other omics data in the future. FEGA and GDI are both built on open and interoperable software solutions, a subset of which are based on the LocalEGA components. FEGA and GDI implementation solutions are based on international community standards, for example those developed by the Global Alliance for Genomics and Health, which contributes to making them interoperable. Both FEGA and GDI allow for the nodes to make use of any solution that is fully compatible. As illustrated in Figure 1, a final key point is the significant overlap of institutions involved in envisioning and operating FEGA and GDI nodes, with the clear wish to keep them interoperable in the future. What distinguishes Federated EGA from GDI? Despite being largely similar, there are some differences between the FEGA and GDI networks, which we aim to clarify in this post. The first difference is the governance model that the nodes will operate to comply with national laws and GDPR. In the FEGA network, nodes have taken inspiration from the EGA data access model, where the infrastructure is a data processor of the hosted data and data controllership remains with the originating Data Access Committees (i.e. Data controllers) for each dataset. On the other hand, in the GDI network the controllership of datasets will be transferred to a 1+MG European Digital Infrastructure Consortium (EDIC) legal entity created by the Member States (MS), who will make data access decisions, with data holders having veto powers for their datasets. Importantly, FEGA nodes have the flexibility to choose another model to fit with their data protection framework, including becoming data controllers for their datasets. The second difference is the inclusion criteria for data. While FEGA nodes are designed to accept almost any type of omics data in need of control access (e.g. genomics, transcriptomics, genotyping, single cells sequencing, patient-tracked metagenomics), GDI nodes are initially, but not only, focused on accepting whole genome and exome sequencing data and affiliated data from sources such as (i) the Genome of Europe use case of the 1+MG initiative which specifically aims to fulfil the mission of building “a European network of national genomic reference cohorts of at least 500,000 citizens”) (ii) data collection of other types of genomic data identified by countries through the 1+MG dashboard and (iii) genomic data coming from data holders which would need to fulfil EHDS requirements. The third difference is the maturity of the software stacks. The FEGA network provides a set of software for data and metadata submission, storage, permissions management, and file distribution (the LocalEGA package). GDI is building a complete set of open source reference for the five functionalities covering the full data life cycle (a few more compared to the LocalEGA) including federated processing (analytics, AI/ML), which is still under active development. Notably, one of the GDI functionalities - storage and interfaces - can be satisfied by using the LocalEGA storage solution, highlighting the ability of FEGA and GDI to be interoperable. In both FEGA and GDI, nodes are allowed to use alternative solutions as long as they are fully interoperable with the networks. Figure 1 provides a simple overview of these described commonalities and differences. Figure1: schematic overview of the main commonalities and difference among a FEGA and a GDI node Can the same institute run a FEGA and a GDI node at the same time? The answer is Yes! We believe this is entirely possible and encouraged. As long as 1+MG requirements are continuously fulfilled in the implementation. The same trained personnel could operate the infrastructure and leverage the same national funding to run a FEGA and a GDI node. Several European nodes, especially GDI vanguard nodes like Norway, Sweden, Finland and Spain are following this model. The idea is that a lot of the work can be reused, given the overlapping scope and the interoperable technology. Thus, the hosted datasets can be discovered via the two catalogues, perhaps accessible under the same or different governance models. From a FEGA node perspective, the GDI datasets could simply be a subset of the datasets hosted in the FEGA node, which have their specific governance as any other. What's next? So, the amazing teams of people building the Federated EGA network and the European GDI network are working together to create infrastructures able to provide secure access to human genomic and associated data around Europe. Because we all know how much human genomics can improve healthcare and precision medicine. And we all want to collaborate to make it happen. This article has been reviewed collectively by members of the EGA and the GDI coordination team.

  Blog fega-and-gdi

• National Institute on Aging Genetics of Alzheimer's Disease Data Storage Site (NIAGADS)

  NIAGADS is an NIH controlled-access data repository that collaborates with researchers around the world to facilitate data access and sharing for genomic and associated omics data related to Alzheimer's Disease (AD), Alzheimer's Disease Related Dementias (ADRD), as well as healthy aging. Serving as the data coordinating center for the Alzheimer's Disease Sequencing Project (ADSP), NIAGADS hosts all ADSP-generated whole-exome, whole-genome and associated phenotypes. Other data types hosted by NIAGADS include genotype SNP arrays, functional omics, fluid biomarkers, aggregated imaging data (such as volumetric data for brain regions of interest), and summary statistics. In adherence with NIH security best practices and genome data sharing policies, NIAGADS supports data access requests through review by an NIH-appointed and registered Data Access Committee. Data stored within NIAGADS cannot be requested via dbGaP. Data requests must go through the NIAGADS Data Sharing Service (DSS) via the following NIAGADS url: https://dss.niagads.org/. Questions related to the request of data should be directed to the NIAGADS admin team at: niagads@pennmedicine.upenn.edu. DSS is a FISMA certified platform built by a team of data scientists at the University of Pennsylvania to support the request and access of AD/ADRD data by qualified researchers internationally. Questions related to the use of data hosted in the DSS should be directed to the Portal admin team at: help@niagads.org.

  Study phs004180

• PyEGA3 download client

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

  Documentation access/download/files/pyega3

• 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

• Single-nucleus RNA-sequencing data of kidney biopsies from patients with primary FSGS, maladaptive FSGS, proteinuric controls and healthy controls

  This dataset includes FASTQ files of single-nucleus RNA sequencing of cryopreserved kidney biopsy cores from adult patients with diagnosed primary FSGS (n = 9, all nephrotic), maladaptive FSGS (n = 9, not nephrotic), proteinuric controls (PLA2R-positive membranous nephropathy, n = 3), and healthy controls (n = 4). A total of 120,751 high-quality nuclei were identified, including 2,471 podocytes and 1,574 parietal epithelial cells (PECs). In addition to the raw FASTQ files, the dataset includes processed data files from all 25 samples, generated using Seurat in R: barcode files, features, count matrices, and associated metadata. Details regarding the bioinformatics pipeline can be found at https://github.com/lambrechtslab/FSGS_Deleersnijder_et_al

  Dataset EGAD50000001557