6179 results for "get fc 26 coins Buyfc26coins.com is FC 26 coins official site..4xt1"

in 17.55 milliseconds.

• Alzheimer's Disease Sequencing Project (ADSP)

  NOTICE OF CHANGE IN LOCATION FOR ALZHEIMER'S DISEASE SEQUENCING PROJECT (ADSP) GENETIC AND PHENOTYPIC DATA: ADSP whole exome and whole genome sequence data that are shared through dbGaP were mapped to the Genome Reference Consortium human genome GRCh37 (build 37). These data are from the Discovery Phase of the project (described below) and will continue to be available at this site. Please see the ADSP Design page for the complete study description. All data that are mapped to GRCh38 (hg38) are being shared through the NIA Genetics of Alzheimer's Disease Data Storage Site (NIAGADS) Data Sharing Service (DSS). For instructions on how access the ADSP Build 38 data that are shared through NIAGADS DSS, visit the Application Instructions page. STUDY DESCRIPTION FOR dbGaP BUILD 37 ADSP DATA: The overarching goals of the Alzheimer's Disease Sequencing Project (ADSP) are to: (1) identify new genomic variants contributing to increased risk of developing Alzheimer's Disease (AD), (2) identify new genomic variants contributing to protection against developing AD, and (3) provide insight as to why individuals with known risk factor variants escape from developing AD. These factors will be studied in multi-ethnic populations in order to identify new pathways for disease prevention. Such a study of human genomic variation and its relationship to health and disease requires examination of a large number of study participants and needs to capture information about common and rare variants (both single nucleotide and copy number) in well phenotyped individuals. Using existing samples from NIH funded and other studies, three NHGRI funded Large Scale Sequencing and Analysis Centers (LSAC) - Broad, Baylor, and Washington University - produced the DNA sequence data. Variant call data are being made available to the scientific community through NIH-approved data repositories. Statistical analysis of the sequence data is anticipated to identify new genetic risk and protective factors. The ADSP will conduct and facilitate analysis of sequence data to extend previous discoveries that may ultimately result in new directions for AD therapeutics. Analysis of ADSP data will be done in two phases. The Discovery Phase analysis (2014-2018) is funded under PAR-12-183. The entire Discovery dataset contains whole-genome sequencing data on 584 subjects from 113 families, and pedigree data for > 4000 subjects; whole exome sequencing data on 5096 cases 4965 controls; and whole exome sequence data on an additional 853 (682 Cases [510 Non-Hispanic, 172 Hispanic]), and 171 Hispanic Control subjects from families that are multiply affected with AD. The Replication Phase (2016-2021) analysis will be funded under RFA-AG-16-001 and RFA-AG-16-002 and is expected to include a combination of genotyping and sequencing approaches on at least 30,000 subjects. Targeted sequencing will be done by the LSACs. GRCh37 Data Releases The first ADSP data release occurred on November 25, 2013. It included the whole-genome sequencing data in BAM file format on 410 individuals. The second ADSP data release occurred on March 31, 2014, and included the whole-genome sequencing data in BAM file format for an additional 168 individuals. The third ADSP data release occurred on November 03, 2014 and included whole-exome sequencing data in BAM file format for 10,939 individuals. The fourth ADSP data release occurred on February 13, 2015 and included revised ethnic data for subjects with whole-exome sequencing data. The fifth ADSP data release occurred on July 13, 2015 and included whole-genome genotypes and updated phenotypes as well as changes to pedigree structures and sample IDs. The sixth ADSP data release occurred on December 8, 2015, and included whole-exome genotypes and updated phenotypes as well as changes to subject IDs. This seventh ADSP data release on April 12, 2016 includes: (1) WES and WGS SNV VCF files (2) WES and WGS Indel PLINK files ADSP Data Available through dbGaP: ADSP - Whole Genome Sequencing ADSP - Whole Exome Sequencing Comments DNA-Seq (BAM) n=578 n=10913 Sequence data available (plus n=38 replications w/out genotype data) Concordant SNV Genotypes (PLINK format) N/A n=10913 QC'ed genotypes that are concordant between the Atlas (Baylor's) and GATK (Broad's) calling pipelines (a subset of the consensus genotype set) Consensus Genotypes (PLINK and VCF format) n=578 n=10913 QC'ed genotypes that are concordant between Atlas and GATK pipelines as well as those that that were called uniquely by Atlas or GATK Concordant Indel Genotypes (PLINK format) n=578 n=10913 QC'ed genotypes that are concordant between the Atlas and GATK calling pipelines Phenotype Data n=4735 n=10913 Data of n=53 phenotype variables available (plus administrative data), including APOE genotype. WGS phenotypes include data of connecting family members. Please use the release notes provided by dbGaP to obtain detailed information about study release updates. The ADSP data portal provides a customized interface for users to quickly identify and retrieve files by covariates, phenotypes, and data properties such as sequencing facility or coverage. For more information about the ADSP study and the data portal, please visit https://www.niagads.org/adsp/.

  Study phs000572

• Download Metadata

  Metadata Distribution Welcome to the realm of Metadata Distribution within the EGA ecosystem! Our Metadata REST API empowers you to effortlessly retrieve metadata from the expansive landscape of EGA. By utilising this API, you gain access to publicly available insights across various EGA domains, including studies, samples, experiments, runs, analyses, policies, DACs, and datasets. Furthermore, this API facilitates cross-referencing of objects, enabling you to gather, for example, all the datasets associated with a specific DAC, seamlessly. In addition, we have added the ability to query private data using the metadata API. If you possess the necessary permissions, you can access behind-the-login private data for a specified list of datasets. Metadata Distribution Index Identifiers Dataset Mappings Website Download Metadata API - Private Identifiers At the core of EGA's organisational structure are unique accessions that serve as essential tags for our diverse objects. Here's a quick overview of the accessions and their corresponding object types: EGA Accession ID EGA Object description EGAS EGA Study Accession ID EGAC EGA DAC Accession ID EGAP EGA Policy Accession ID EGAN EGA Sample Accession ID EGAR EGA Run Accession ID EGAX EGA Experiment ID EGAZ EGA Analysis Accession ID EGAD EGA Dataset Accession ID EGAB EGA Submission ID EGAF EGA File Unique Accession ID For further information check our metadata schema documentation. Dataset Mappings For authorised datasets, comprehensive mappings reveal meaningful connections: Sample_file: This file presents information about the linkage between samples and files available in the dataset. Study_experiment_run_sample: This file presents information about the linkage between studies, experiments, runs, and samples within the dataset. Study_analysis_sample: This file presents information about the linkage between studies, analyses, and samples contained within the dataset. Run_sample: This file presents information about the linkage between runs and samples within the dataset. Analysis_sample: This file presents information about the linkage between analyses and samples within the dataset. An empty file indicates the absence of corresponding information. Website Download Our website serves as your gateway to downloading metadata. Simply navigate to the dataset page, and you'll find a blue Metadata button. Once authenticated, you can click this button for authorised datasets. If you lack permissions for a particular dataset, request access by clicking the 'Request Access' button. For authorised datasets, choose your preferred metadata format: CSV, TSV, or JSON. Metadata API - Private Leverage the power of programmatic metadata downloads! Start by authenticating yourself with your credentials to obtain an access token. With this token, programmatically query private information. Queries mirror the structure of the Public Metadata API. However, behind the login, you can delve into specific mapping information (as mentioned above in dataset mappings) alongside object-level exploration. Authentication An active session is required to work with the API. Each time you log in with your credentials a new session is started, which is identified by an access_token. Below an example on how to obtain one using curl: curl https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token \ -d 'client_id=metadata-api' \ -d 'username=...' \ --data-urlencode 'password=...' \ -d 'grant_type=password' All responses from the API are in JSON format. A successful response should include a new token to be used for the session: {"access_token":"eyJhbGciOiJSUzI1NiIsInR5cCIgOiA...TNw", "expires_in":300, "refresh_expires_in":1800, "refresh_token":"eyJhbGciOiJIUzI1NiIsInR5cCIgOiA...pTX10", "token_type":"Bearer", ... } Save the access_token value and include it in the API call headers. Example query usage Below you can find some example of queries available behing authentication and authorisation. Querying study-experiment-run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_experiment_run_sample \ -H 'Authorization: Bearer access_token' Querying run-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/run_sample \ -H 'Authorization: Bearer access_token' Querying study-analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/study_analysis_sample \ -H 'Authorization: Bearer access_token' Querying analysis-sample mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/analysis_sample \ -H 'Authorization: Bearer access_token' Querying sample-file mappings: curl https://metadata.ega-archive.org/datasets/{datasetID}/mappings/sample_file \ -H 'Authorization: Bearer access_token' You can get a different output format by adding one of these options to the curl command: -H 'Accept: text/tsv' -H 'Accept: application/json' -H 'Accept: text/csv' For more detailed information, refer to the Metadata API Specification.

  Documentation access/download/metadata

• Genetic Basis of Early Onset Bicuspid Aortic Valve Disease

  The study protocol was approved by the Committee for the Protection of Human Subjects at the University of Texas Health Science Center at Houston (HSC-MS-11-0185). Study recruitment began on July 1, 2017, and concluded on March 30, 2022. After written informed consent, we enrolled probands with early onset BAV disease (EBAV), which we defined as individuals with BAV who were under the age of 30 at the time of first clinical event. Clinical events were defined as aortic replacement, aortic valve surgery, aortic dissection, moderate or severe aortic stenosis or aortic regurgitation, large aneurysm (Z > 4.5), or intervention for BAV-related conditions. Those with hypoplastic left heart, known genetic mutations, genetic syndromes, or complex congenital heart disease were excluded. Samples were collected and genotyped as previously reported. For comparison, we analyzed a cohort of older individuals of European ancestry with sporadic BAV disease selected from the International BAV Consortium (BAVGWAS). Phenotypes were derived from record review with confirmation of image data whenever possible [25-26]. The computational pipeline for CNV analysis of Illumina single nucleotide polymorphism (SNP) array data included three independent CNV detection algorithms.GenomeStudio was used to exclude samples with indeterminate sex or more than 5% missing genotypes, and single nucleotide polymorphisms (SNPs) with GenTrain = 0. Principal component analysis was used to remove outliers that did not cluster with European ancestry. Prior to CNV analysis, each dataset was trimmed by selecting a common set of 650,000 SNPs that were genotyped on each of the microarrays used in this study.Three independent algorithms (PennCNV, cnvPartition, and QuantiSNP) were used to generate CNV calls and sample-level quality statistics from SNP intensity data. PennCNV and QuantiSNP were run on Unix clusters and cnvPartition data were exported from GenomeStudio. The analysis was run using default configurations. PennCNV was used to generate QC data and remove CNV calls that intersect with polymorphic genomic regions. Samples that met any of the following criteria were excluded, standard deviation of the LogR ratio (obtained from PennCNV) > 0.35 or number of CNVs > 2 standard deviations above the mean for each data set. CNV calls less than 20 Kilobases in length and/or spanned by fewer than 6 probes were excluded. The overlap function for rare CNVs in PLINK was used to construct CNV regions (CNVRs) after adjacent regions were merged using PennCNV. LogR ratio (LRR) and B allele frequency (BAF) data at CNVRs and calls of interest were visualized in GenomeStudio for validation. For segregation analysis, GenomeStudio was used to determine the presence of CNVs in relatives.A total of 22,014 unselected control Illumina Genotypes obtained from the Database of Genotypes and Phenotypes were analyzed using identical methods (S1 Table). The Wisconsin Longitudinal Study (WLS) includes data on a cohort of 10,300 individuals who graduated from Wisconsin high schools in 1957. The Health and Retirement Study (HRS) includes data on 37,000 individuals aged 50 above from 23,000 households across the United States. Principal component analysis was used to select European ancestry genotypes from these datasets for analysis. Datasets were paired for case-control analysis based on the concordance of log-transformed sample-level quality control statistics (number of CNV calls and standard deviation of logR ratios). Chi-squared or Fisher exact tests were used to compare CNV frequencies in cases and controls.Rare CNV functions in PLINK (v1.7) were used to perform permutation-based burden tests or gene set-based enrichment tests. Case control burden tests were restricted to CNVs that were longer than 110 Kb and less than 0.1% in frequency. CNV overlap functions in PLINK were used to identify rare CNVs that intersect between datasets or involve specific BAV or CHD genes . The list of candidate genes included 190 CHD genes that have strong cumulative evidence to cause BAV or related congenital malformations from human or animal model data. Genome Reference Consortium Human Build 37 was used for CNV annotation [34].

  Study phs003705

• Privacy Notice for Data Access Committee Account

  Privacy Notice for EGA Data Access Committee Account This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by Mallory Freeberg, by: email at mfreeberg@ebi.ac.uk , orpost at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: email at dpo@embl.org, orpost at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, orpost at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eupost at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? We process your personal data on the grounds of important public interest. For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: NameEmail addressTitle/PositionOrganisationOrganisational affiliationBusiness addressTelephone numberIP addressesDate and time of a visit to the service websiteOperating systemAmount of data transmittedBrowserUsernamePassword The data controller will use your personal data for the following purposes: To provide DAC user account and authenticated access to the service,To publicly publish some information to facilitate scientific research,To better understand the needs of the data subjects and guide future improvements of the service,To create anonymous usage statistics (from number of DACs, datasets per DAC). 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions (for all user account data),The general public via Internet will get access to your name, email address, business address, telephone number and organisation you belong to. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Data categories ‘name`, `email address`, `telephone number`, `business address`; `organisation’ of the DAC user are published on the Internet. They thus become accessible to recipients in countries outside the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI), is necessary for important reasons of public interest embedded in the aims of EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union 6. How long do we keep your personal data? Any personal data directly obtained from you will be retained as long as the service is live. Such duration serves the purpose of enabling scientific research and ensures legal compliance and facilitates internal and external audits if they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration.Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period.Request information to understand data processing activities when the results of these activities are applied to you. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. Published at: February 6, 2019

  Documentation data-protection/privacy-notice/ega-dac

• Submitter Portal API

  Submitter Portal API The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have an ega-box (submission account), you can skip this step.  Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal-api

• NHLBI GO-ESP: Heart Cohorts Exome Sequencing Project (Siblings with Ischemic Stroke Study, SWISS)

  The NHLBI "Grand Opportunity" Exome Sequencing Project (GO-ESP), a signature project of the NHLBI Recovery Act investment, was designed to identify genetic variants in coding regions (exons) of the human genome (the "exome") that are associated with heart, lung and blood diseases. These and related diseases that are of high impact to public health and individuals from diverse racial and ethnic groups will be studied. These data may help researchers understand the causes of disease, contributing to better ways to prevent, diagnose, and treat diseases, as well as determine whether to tailor prevention and treatments to specific populations. This could lead to more effective treatments and reduce the likelihood of side effects. GO-ESP is comprised of five collaborative components: 3 cohort consortia - HeartGO, LungGO, and WHISP - and 2 sequencing centers - BroadGO and SeattleGO. The Siblings with Ischemic Stroke Study (SWISS) is an affected sibpair (ASP) study of patients and their brothers/sisters who have had similar strokes. The study was conducted to determine the genes that contribute to an individual's risk of developing an ischemic stroke (a stroke due to sudden interruption of blood flow to a part of the brain). Over 600 people have participated in SWISS, with the coordination of the recruitment and flow of the samples occurring at the Mayo Clinic, Jacksonville, FL, under the direction of James F. Meschia, MD. The University of Virginia (Stephen S. Rich, PhD) served as the analytic site for the genetic data. Participants were excluded from SWISS if they had stroke following an invasive cerebrovascular or cardiovascular procedure, if their stroke occurred shortly following an aneurismal subarachnoid hemorrhage, if the stroke occurred in the setting of a mechanical aortic or mitral valve, if the patient had definite CNS vasculitis or if the patient had a Mendelian mitochondrial stroke disorder, including CADASIL, MELAS, Fabry disease, sickle cell anemia or homocysteinemia. For the NHLBI ESP, the youngest 51 ASPs (102 individuals) from SWISS were selected to undergo exome sequencing. These ASPs were selected from among all SWISS participants, excluding those pedigrees with individuals who had TOAST subtypes of stroke of other etiology or of stroke with undetermined etiology. In addition, the affected siblings were required to have the same TOAST subtype (both small vessel (lacunar) or both large vessel (atherosclerotic)). Of those selected, 98 samples passed initial quality control metrics, and 94 completed exome sequencing and were deposited in dbGaP. An additional set of 590 samples from the SWISS collection has been genotyped on the ExomeChip that contained a subset of rare/infrequent variants identified by exome sequencing. These samples include 495 affected individuals (from multiple affected family members) as well as 95 unaffected family members. These genetic and phenotypic data also will reside in dbGaP.

  Study phs000327

• RNA-sequencing from duodenal bipsies of Celiac disease patients

  Samples, in a form of PAXgene fixed and paraffin-embedded biopsies, were collected from the multi-site, double-blind, randomized, placebo-controlled trial, aimed at dose-finding and assessing the efficacy and tolerability of a 6-week treatment with ZED1227 capsules vs. placebo in subjects with well-controlled celiac disease undergoing gluten challenge. Total RNA was extracted from the PaxFPE biopsy specimens (n = 116) using additional cuttings from the samples on which histomorphometry was previously assessed. For the extraction, an RNeasy Kit (Qiagen, Hilden, Germany) was used according to the manufacturer’s instructions. Library preparation and next-generation sequencing (NGS) were performed by the Qiagen NGS Service. A total of 10 ng of purified RNA was converted into cDNA NGS libraries. Library preparation was quality controlled using capillary electrophoresis. Based on the quality of the inserts and the concentration measurements, the libraries were pooled in equimolar ratios and then sequenced on a NextSeq (Illumina Inc., San Diego, USA) sequencing instrument according to the manufacturer’s instructions, with 100 bp read length for read 1 and 27bp for read 2. The raw data were de-multiplexed, and FASTQ files for each sample were generated using bcl2fastq2 software (Illumina Inc., San Diego, USA).

  Dataset EGAD50000000491

• National Human Genome Research Institute (NHGRI) Clinical Sequencing Exploratory Research (CSER) The MedSeq Project: Integration of Whole Genome Sequencing into Clinical Medicine (HG006500)

  Whole genome sequencing (WGS) and whole exome sequencing (WES) services are currently available to and being utilized by physicians and their patients in both research and clinical settings, and recently to anyone in the general public via direct-to-consumer companies. But the widespread availability and use of WGS and WES in the practice of clinical medicine is imminent. In the very near future, sequencing of individual genomes will be inexpensive and ubiquitous, and patients will be looking to the medical establishment for interpretations, insight and advice to improve their health. Developing standards and procedures for the use of WGS information in clinical medicine is an urgent need, but there are numerous obstacles related to integrity and storage of WGS data, interpretation and responsible clinical integration. The MedSeq Project is an exploratory trial of WGS in clinical medicine. At the conclusion of this study, we will have helped create innovative protocols and novel outcome measures that can be applied safely in future large-scale multi-site randomized clinical trials with larger numbers of physicians from broad specialties and with more economically and ethnically diverse patients. Together with our colleagues from across the nation through the U01 consortium formed as a result of this funding from the NIH, we will have invented a process of implementation and evaluation whereby the fruits of the Human Genome Project can be applied for the first time to the daily practice of medicine for the betterment of human health. The objectives of the MedSeq Project are to: Recruit, consent and enroll 2 study groups: 10 primary care physicians and 100 of their healthy middle-aged patients 10 cardiologists and 100 of their patients with cardiomyopathy. Randomize each study group to receive standard of care versus standard of care plus WGS. Monitor the entire protocol for subject safety. Only half the enrolled patients were selected for sequencing. Fifty subjects were selected from the primary care cohort and fifty were selected from the cardiomyopathy cohort. Whole genome sequencing was performed at 30x coverage in Illumina's CLIA-certified laboratory on these 100 individuals. Generate and optimize an algorithm for interpreting WGS data covering the spectrum of human genetic variation, in terms of both previously reported and novel variants likely to influence the health of patients. Create patient reports and provide an interface for communicating clinically relevant genomic information to practicing physicians. Describe physicians' and patients' attitudes toward, and preferences for, the disclosure of WGS results at the start of the study. Evaluate physicians' experiences with receiving and interpreting patients' genetic test results and how they communicate these results to their patients. Explore how patients respond to and use WGS results by administering validated scales of psychological impact, personal utility, and behavioral responses, as well as economic and health outcomes. Although we do not have a large enough sample size for statistical comparisons of outcomes, we will conduct exploratory comparisons: Exploratory Hypotheses: Patients who receive WGS results will show equivalent levels of distress compared to patients who receive family history only. Patients with higher genetic literacy and better understanding will report greater satisfaction and less decisional regret. Patients who receive WGS will (a) be more likely to change health behaviors and (b) utilize more health care resources than those who do not receive WGS.

  Study phs000958

• Resuscitation Outcomes Consortium (ROC) Cardiac Epidemiologic Registry (Cardiac Epistry) Versions 1 and 2 (ROC-Cardiac Epistry 1 and 2-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. Available Data: The ROC Cardiac Epistry versions 1 and 2 include all cardiac arrest cases entered into the ROC database from December 1, 2005 to April 1, 2011. ROC Cardiac Epistry 3 includes cardiac arrest cases captured between 2011 and 2015, and introduced significant changes in how and which data were collected.For ROC traumatic injury Epistry data, please see: ROC-Trauma Epistry Objectives: To build a prospective population-based registry of participants with out-of-hospital cardiac arrest responded to by Emergency Medical Services (EMS). Specific aims: to establish whether the results of Resuscitation Outcomes Consortium (ROC) trials can be generalized to the larger population of participants that experience cardiac arrest;to more fully establish the burden of cardiac arrest; and to examine the relationships between variation in EMS structure and process, regional and periodic factors, and participant outcomes.Background: Cardiac arrest is a common, serious, debilitating and costly public health problem. Although there has been a steady decline in morbidity and mortality from most cardiovascular diseases, high mortality rates for out-of-hospital cardiac arrests continue to pose a challenge for healthcare providers and a significant public health burden. The Resuscitation Outcomes Consortium (ROC) was established in 2004 to conduct clinical research in the areas of cardiopulmonary arrest and life-threatening traumatic injury with the overall goal of improving resuscitation outcomes. Participant and care characteristics can predict favorable outcomes in cardiac arrests, but there is still a wide variation in outcomes that is not well understood. EMS factors such as service level, number of responding providers, use of procedures or drugs in the field, training, quality assurance/feedback, and response time intervals also vary significantly by region. Variations in geographic, socioeconomic and periodic factors may also be associated with differences in outcomes.Prior to ROC Cardiac Epistry, there were no North American population-based registries for out-of-hospital cardiac arrests. Therefore there was a need for standardized data collection of out-of-hospital cardiac arrests in diverse geographic locations in order to identify the independent effects of prognostic or treatment factors accounting for variations in survival. Participants: The registry included 109,326 cardiac arrest events from 264 EMS agencies transporting to 287 acute care hospitals from the following regional centers: Birmingham, Alabama; Dallas, Texas; Iowa City, Iowa; Milwaukee, Wisconsin; Pittsburgh, Pennsylvania; Portland, Oregon; San Diego, California; Seattle/King County, Washington; Ottawa, Ontario; Toronto, Ontario; and Vancouver, British Columbia.Design: ROC Epistry collected standardized data regarding episode-specific factors, participant demographics, clinical information, pre-hospital interventions and disposition, hospital information, and participant outcome for all out-of-hospital cardiac arrests in the ROC regions. Each ROC site had to ensure capture of all eligible cases within the EMS service areas. Out-of-hospital data were extracted from existing databases whenever possible and augmented with targeted review of EMS reports. Hospital data were abstracted directly from the hospital file in most cases. Alternative methods included linkage to death registries and obituaries if the death occurred within 30 days. Sites submitted data using a web-based interface or batch uploads. Participants were not contacted directly.

  Study phs003803

• Pomalidomide for the Treatment of Bleeding in HHT (PATH-HHT)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To determine efficacy (reduction in severity of epistaxis), tolerability, and improvement in quality of life of pomalidomide compared to placebo after 24 weeks of treatment.Background: This study addresses the efficacy of pomalidomide in the treatment of epistaxis in patients with Hereditary Hemorrhagic Telangiectasia (HHT) who have anemia and/or require blood transfusion or iron infusion for treatment of bleeding-induced anemia and iron deficiency. HHT (also known as Osler-Weber-Rendu disease) is an inherited bleeding disorder. Over 95% of patients develop recurrent epistaxis, which may be severe and result in chronic anemia, need for iron infusions and blood transfusions, substantial psychiatric comorbidity (including depression and post-traumatic stress disorder) and reduction in health-related quality of life (HRQoL). HHT is clinically diagnosed using the Curacao criteria, which consists of 1) spontaneous and recurrent epistaxis, 2) telangiectasias at characteristic sites, 3) visceral arteriovenous malformations (AVMs) or telangiectasias, and 4) a first degree relative with HHT (inheritance is usually autosomal dominant). Patients with three criteria are considered to have definite HHT, and those with 2 criteria probable HHT. HHT affects approximately 1 in 3,800 individuals. Significant manifestations of HHT often do not appear until the third or fourth decades, sometimes later.Participants: 144 patients from 11 clinical centers were enrolled.Design: This is a multi-center, double blind, randomized placebo-controlled trial that investigated the efficacy and safety of pomalidomide in patients with HHT and chronic epistaxis leading to iron-deficiency anemia or requiring intravenous iron infusions or blood transfusion.Screening evaluation included the Epistaxis Severity Score (ESS) with three-month recall, which reflected the patient's history of epistaxis and bleeding over the prior three months, as well as detailed review of iron infusion and red cell transfusion over the preceding six months. Eligible patients were provided a diary to record the duration of each epistaxis event that occurred during the 4 weeks prior to the baseline visit, and then returned for the baseline randomization visit, at which time patients underwent genetic testing, if this had not been previously performed, and completed an ESS with 4-week recall and quality of life assessments. Patients were randomized 2:1, stratified by study site, to either pomalidomide 4 mg/day or matching placebo during each of six 28 day cycles (24 weeks). Patients were seen every four weeks during treatment, and at a 4-week post-treatment follow-up visit to measure the ESS (with 4-week recall), laboratory assessments including iron stores and need for iron infusion, CBC, and metabolic profile. Patients were assessed for adverse events (AE) throughout the study. Treatment dosage could be reduced, or temporarily or permanently discontinued following AE-specific guidelines related to fatigue, cytopenias or other toxicities.Quality of life assessments were completed at baseline, and the 12- and 24-week visits, and the 4-week post-treatment follow-up visit using validated NIH instruments of 1) Neuro-QOL satisfaction with social roles and activities, 2) PROMIS emotional distress – depression, and 3) PROMIS fatigue, and the HHT-specific quality of life instrument developed specifically for this study. The effect of pomalidomide on duration of epistaxis was assessed via diary between weeks 8-12, 20-24 and the 4-week post-treatment period.Conclusions: Among patients with HHT, pomalidomide treatment resulted in a significant, clinically relevant reduction in epistaxis severity. No unexpected safety signals were identified (Al-Samkari et al., 2024; PMID: 39292928)

  Study phs003948