1277 results for "get free coins fc 26 Visit Buyfc26coins.com Bardzo pod wrażeniem jakości usług..VZcl"

in 34.76 milliseconds.

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Genes and Blood Clotting Study (GABC)

  Objectives: Use genome-wide approaches to identify genetic variants that influence common thrombosis and hemostasis factors, as well as selected common human traits. Design/Methods: The GABC study was a prospective sibling cohort design. Siblings were recruited by targeted email to the undergraduate and graduate student email lists at the University of Michigan. Healthy persons between 14 and 35 years old who had healthy siblings within the same age restriction were able to participate. Study participants agreed to an online informed consent and subsequently completed a 52-question online survey describing their specific bleeding traits as well as many common human traits. Fifty milliliters of blood was collected into a citrate-dextrose solution (ACD) from each participant. An aliquot of whole blood was used for an automated complete blood count analysis and the remainder was processed into platelet poor plasma and buffy coat portions. Plasma and buffy coat aliquots were snap frozen and stored in liquid nitrogen for future studies. 1189 individuals representing 507 sibships were collected between 06/26/2006 and 01/30/2009. Phenotyping Survey Details: To characterize individual bruising and bleeding history, the online survey recorded answers to questions based on a modified von Willebrand Disease (VWD) screening questionnaire. To characterize a collection of participant&#39;s common human traits, the survey recorded answers to questions about height, weight, presence of skin tags, history of acne, eye color, hair color, hair line characteristics, skin sunburn sensitivity, skin tanning ability, natural skin color, freckling, cheek dimpling, earlobe shape, shoe size, foot arch characteristics, hand fifth digit morphology, history of dyslexia, history of migraine headaches, history of seasonal allergies, history of apthous ulcers, tendency to sneeze while walking into a bright sunny place, history of dental caries, need for corrective eye lenses, handedness and like or dislike of strongly flavored foods. Biochemical phenotyping: Assays for plasma Von Willebrand Factor (VWF) antigen were performed using ELISA and "Alphalisa" techniques. Automated complete blood count analysis was performed on a Bayer Advia 120 on all participants (including WBC differential, RBC indices, and platelet count.) For the dbGaP v2 update, new biochemical phenotypes have been submitted and include von Willebrand Factor, von Willebrand Factor propeptide, plasminogen, gamma prime fibrinogen, ADAMTS 13, antithrombin III, protein C, and protein S. All new phenotypes were obtained using "Alphalisa" techniques. Genotyping Details: SNP genotyping was performed using genomic DNA extracted from peripheral blood at the Broad Institute, (MIT/Harvard). Genotyping was performed on the Illumina Omni-1 quad chip at the Broad Institute. For the dbGaP v2 update, genotyping data from the Illumina Human Exome was deposited. 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 blood clotting through large-scale genome-wide association studies of siblings. Genotyping was performed at the Broad Institute of MIT and Harvard, a GENEVA genotyping center. Data cleaning and harmonization was performed by the primary investigators at the University of Michigan, Ann Arbor, and at the GEI-funded GENEVA Coordinating Center at the University of Washington. This study serves as a resource for investigators who are interested in the genetic determinants of specific plasma proteins in a healthy population. The sibling cohort design allows for linkage analysis in addition to association studies. Analysis of thrombosis and hemostasis related traits should help elucidate specific biochemical and genetic networks that maintain hemostasis. We hope to identify specific genetic determinants of VWF levels in order to better understand the factors that influence the development of VWD.

  Study phs000304

• 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

• Starr County Health Studies' Genetics of Diabetes Study

  An initial observation in the 1970s that Starr County, Texas, had the highest diabetes-specific mortality of any of the 254 Texas counties led to the establishment of a field office in Rio Grande City, Texas (the county seat of Starr County) and the initiation of a series of studies to understand the epidemiology and genetics of type 2 diabetes, its complications and related conditions in this predominantly (97%) Mexican American population. The field office opened in February 1981 and has operated continuously since then. During this time, three systematic surveys of the population have been conducted as well as family and longitudinal studies. Culturally sensitive diabetes education programs have been developed and implemented and also a weight loss intervention. In total, more than 23,000 Mexican American individuals have been examined with more than 200,000 aliquots of biological specimens stored. Collectively, these studies are known as the Starr County Health Studies. The present Genetics of Diabetes Study has the goal of identifying loci/alleles that underlie susceptibility to type 2 diabetes in this high risk population using genome wide markers and association testing. The study makes use of two primary resources that have been developed in order to identify 1,000 type 2 diabetes cases and 1,000 disease free controls. In the first instance we have identified a subset of unrelated cases from the total cases that we have identified. Where multiply affected sibships were available, the youngest onset case with detailed phenotyping (including assessment of diabetic retinopathy) was selected. Controls came from a recent survey to establish a representative sample of the Starr County population. Blocks were randomly selected, households on selected blocks enumerated and one individual randomly selected from each household for a detailed examination. The examination included an oral glucose tolerance test. Those included as controls are those with no prior diagnosis of diabetes and a negative oral glucose tolerance test. This collection of cases and controls provides the opportunity to identify susceptibility loci for type 2 diabetes and its complications, specifically diabetic retinopathy and albuminuria. The data set also allows the examination of impaired fasting glucose and impaired glucose tolerance. The samples are split between those born in the United States and those born in Mexico and this gives a natural contrast for examining genotype and environmental interactions. It is anticipated that the understanding that will come will lead to strategies for delaying and preventing the onset of diabetes and its complications.

  Study phs000143

• Diet, Genetic Factors, and the Gut Microbiome in Crohn's Disease

  We investigate the hypothesis that consistent changes in the human gut microbiome are associated with Crohn&#39;s disease, a form of inflammatory bowel disease, and that altered microbiota contributes to pathogenesis. Analysis of this problem is greatly complicated by the fact that multiple factors influence the composition of the gut microbiota, including diet, host genotype, and disease state. For example, data from us and others document a drastic impact of diet on the composition of the gut microbiome. No amount of sequencing will yield a useful picture of the role of the microbiota in disease if samples are confounded with uncontrolled variables. We aim to characterize the composition of the gut microbiome while controlling for diet, host genotype, and disease state. Diet is controlled by analyzing children treated for Crohn&#39;s disease by placing them on a standardized elemental diet, and by testing effects of different diets on the gut microbiome composition in adult volunteers. Genotype is analyzed by large scale SNP genotyping, which is already underway and separately funded--team member Hakon Hakonarson is currently genotyping 50 children a week at ~half a million loci each and investigating connections with inflammatory bowel disease. Clinical status is ascertained in the very large IBD practice in the UPenn/CHOP hospital system. Effects of diet, host genotype, and disease state on the gut microbiome are summarized in a multivariate model, allowing connections between microbiome and disease to be assessed free of confounding factors. This project is divided into four sub-studies. In the Fecal Storage Methods (FSM) study, methods of stool storage and DNA extraction are compared to examine their impact on DNA sequence analysis results. The Controlled Feeding Experiment (CaFE) addresses the effects of controlled diets on the gut microbiome. In the Cross-sectional Study of Diet and Stool Microbiome Composition (COMBO), the effects of diet analyzed using surveys and deep sequencing of stool specimens. The fourth study, Pediatric Longitudinal Study of Elemental Diet and Stool Microbiome Composition (PLEASE), examines the effects of an elemental diet treatment on pediatric patients diagnosed with inflammatory bowel disease (IBD), particularly Crohn&#39;s disease. Fecal Storage Methods (FSM): Cross-sectional study Controlled Feeding Experiment (CaFE): Controlled trial Cross-sectional Study of Diet and Stool Microbiome Composition (COMBO): Cross-sectional study Pediatric Longitudinal Study of Elemental Diet and Stool Microbiome Composition (PLEASE): Longitudinal cohort study

  Study phs000252

• Rapid Acceleration of Diagnostics - Underserved Populations (RADx-UP): CO-CREATE-Ex: Community-engaged Optimization of COVID-19 Rapid Evaluation And TEsting Experiences

  Cases of COVID-19 infection in San Diego have persistently remained high in the county&#39;s central and southern communities near the US/Mexico border, home to primarily Latino residents who have been one of the ethnic minority communities most impacted by COVID-19. To address this, our Phase I RADx-UP project partnered with San Ysidro Health (SYH), a federally qualified health center, and the Global Action Research Center (Global ARC), a social change organization, to co-create and demonstrate the impact of a PCR-based COVID-19 testing program in San Ysidro. To date, we have administered approximately 15,000 PCR tests for >10,000 community members (92% Latino) and received requests from SYH to scale-out the testing program to additional primary care clinic sites. Responsive to RFA-OD-22-006, we will continue working with our community (Global ARC) and clinical (SYH) partners to refine, specify, implement, and evaluate an implementation strategy bundle that optimizes COVID-19 testing, expanding beyond current PCR testing to focus on FDA-authorized COVID-19 rapid antigen testing. Use of self-administered rapid antigen tests will allow participants to build capacity to self-test and use health information technology to access additional clinic services. Based on initial implementation mapping with the project&#39;s established Community and Scientific Advisory Board, three implementation strategies were prioritized to accelerate sustained uptake of rapid COVID-19 testing. These three strategies include: (1) current, walk-up onsite free testing; (2) promotores-led COVID-19 test counseling and preventive care reminders; (3) vending machines that dispense FDA-authorized self-testing kits. Our primary objectives are to: 1) refine and operationalize our multi-component implementation strategy bundle and a related set of measures of success for rapid FDA- authorized COVID-19 testing and 2) implement and evaluate impact of our innovative, multilevel, and multicomponent implementation strategy bundle to optimize COVID-19 rapid testing among underserved, Latino communities using a roll-out implementation optimization study design across four clinics over 18 months. The COVID-19 pandemic has underscored the urgent and essential need to engage invested community parties continuously and meaningfully in public health research to reduce health disparities. This proposal is well-positioned to provide a set of strategies and measures of success that can be used in settings serving underserved communities while maintaining flexibility to adjust to the changing COVID-19 landscape.

  Study phs003686

• MediMer: A versatile do-it-yourself peptide-receptive MHC class I multimer platform for tumor neoantigen-specific T cell detection

  Peptide-loaded MHC class I (pMHC-I) multimers have revolutionized our capabilities to monitor disease-associated T cell responses with high sensitivity and specificity. To improve the discovery of T cell receptors (TCR) targeting neoantigens of individual tumor patients with recombinant MHC molecules, we developed a peptide-loadable MHC class I platform termed MediMer. MediMers are based on soluble disulfide-stabilized β2-microglobulin/heavy chain ectodomain single-chain dimers (dsSCD) that can be easily produced in large quantities in eukaryotic cells and tailored to individual patients’ HLA allotypes with only little hands-on time. Upon transient expression in CHO-S cells together with ER-targeted BirA biotin ligase, biotinylated dsSCD are purified from the cell supernatant and are ready to use. We show that CHO-produced dsSCD are free of endogenous peptide ligands. Empty dsSCD from more than 30 different HLA-A,B,C allotypes, that were produced and validated so far, can be loaded with synthetic peptides matching the known binding criteria of the respective allotypes, and stored at low temperature without loss of binding activity. We demonstrate the usability of peptide-loaded dsSCD multimers for the detection of human antigen-specific T cells with comparable sensitivities as multimers generated with peptide-tethered β2m-HLA heavy chain single-chain trimers (SCT) and wild-type peptide-MHC-I complexes prior formed in small-scale refolding reactions. Using allotype-specific, fluorophore-labeled competitor peptides, we present a novel dsSCD-based peptide binding assay capable of interrogating large libraries of in silico predicted neoepitope peptides by flow cytometry in a high-throughput and rapid format. We discovered rare T cell populations with specificity for tumor neoepitopes and epitopes from shared tumor-associated antigens in peripheral blood of a melanoma patient including a so far unreported HLA-C*08:02-restricted NY-ESO-1-specific CD8+ T cell population. Two representative TCR of this T cell population, which could be of potential value for a broader spectrum of patients, were identified by dsSCD-guided single-cell sequencing and were validated by cognate pMHC-I multimer staining and functional responses to autologous peptide-pulsed antigen presenting cells. By deploying the novel CHO producer cell-based dsSCD MHC-I MediMer platform, we hope to significantly improve success rates for the discovery of personalized neoepitope- specific TCR in the future by being able to also cover rare HLA allotypes.

  Study EGAS50000000065

• TNBC ctDNA Targeted Panel

  Circulating tumour DNA (ctDNA) detection in liquid biopsy is an emerging alternative to tissue biopsy, but its utility in treatment response monitoring and prognosis in triple negative breast cancer (TNBC) remains to be well understood. In this study, we determined the presence of early stage TNBC ctDNA detectable actionable mutations with a clinically validated hotspot treatment indication panel. Sequencing of plasma DNA from 130 TNBC patients collected within 7 months of primary treatment completion revealed that 7.7% had detectable residual disease with a hotspot panel. Among neoadjuvant treated patients, we observed a trend where patients with incomplete pathologic response and positive ctDNA within 7 months of treatment completion were at risk of reduced progression free survival. We propose that a high risk subset of early TNBC patients treated in NAT protocols may be identifiable by combining tissue response and sensitive ctDNA detection.

  Study EGAS00001006937

• Federated discovery and sharing of genomic data using Beacons

  The Beacon Project is a Global Alliance for Genomics & Health (GA4GH) initiative that enables genomic and clinical data sharing across federated networks. The project is working toward developing regulatory, ethics and security guidance to ensure proportionate safeguards for distribution of data according to the GA4GH-developed “Framework for Responsible Sharing of Genomic and Health-Related Data”. Within this Nature Biotechnology Correspondence a description of the Beacon protocol and how it can be used as a model for the federated discovery and sharing of genomic data is offered to the community. A Beacon is defined as a web-accessible service that can be queried for information about a specific allele. A user of a Beacon can pose queries of the form “Have you observed this nucleotide (e.g., C) at this genomic location (e.g., position 32,936,732 on chromosome 13)?” to which the Beacon responds with either “yes” or “no.” In this way, a Beacon allows allelic information of interest to be discovered by a remote searcher with no reference to a specific sample or patient, thereby mitigating privacy risks. The Beacon API (represented as a RESTful web application) provides a technical specification that a Beacon server must implement. The specification is open source and available online here. To simplify the process of lighting a Beacon, a free, open-source reference implementation of the latest specification has been developed. GA4GH is promoting different levels of data access (open, registered, and controlled) for convenience and for compatibility across its projects. Each so-called access tier has distinct visibility and requirements for authorization. For example, ‘open access’ Beacons are accessible to anonymous users of the internet, whereas ‘registered access’ Beacons are accessible to registered users (for example, bona fide researchers and clinicians) who have agreed to a set of conditions of data use. Many of the largest genomic archives, such as dbGaP, the European Genome-phenome Archive and the European Variation Archive, have provided access to variation data through Beacons for some or all of their datasets. Beacons can be interconnected through the Beacon Network, a directory and search engine for Beacons. Although individual Beacons answer the question “Have you observed this allele?”, the Beacon Network answers the question “Who has observed this allele?”. Beacons can be freely registered to the Beacon Network and can be searched independently or in aggregate with other connected Beacons.

  Blog federated-discovery-using-beacons

• Cell-free DNA analysis reveals POLR1D-mediated resistance to bevacizumab in colorectal cancer

  Bevacizumab is an approved anti-angiogenic drug for patients with metastasized colorectal cancer (mCRC) targeting VEGF. The survival benefit of anti-VEGF therapy in mCRC patients is limited to a few months and acquired resistance mechanisms are greatly unknown. Using plasma DNA, we studied the evolution of tumor genomes in a cohort of patients with mCRC (n=150) and observed a recurrent focal amplification (8.7% of cases) on chromosome 13q12.2. Analysis of TCGA data (n=619) suggested an association with later stages, which we confirmed by longitudinal plasma analyses. We defined the minimally amplified region and studied the mechanistic consequences of copy number gain of the involved genes. The amplification of one gene, POLR1D, impacted cell proliferation, resulting in upregulation of VEGFA, an important regulator of angiogenesis which has been implicated in the resistance to bevacizumab. In several patients, we observed the emergence of this 13q12.2 amplicon under bevacizumab treatment, which was invariably associated with evolution of therapy resistance. Hence, we describe a novel resistance mechanism against a widely applied treatment in mCRC patients which will impact clinical management

  Study EGAS00001003791

• CM067 WES - Clinical Outcomes by Tumor Mutational Burden and Inflammatory Gene Expression With Combined Nivolumab and Ipilimumab or Monotherapy in Advanced Melanoma

  Purpose Exploratory analyses of CheckMate 066 and 067 trials were conducted to investigate associations of tumor mutational burden (TMB), a 4-gene inflammatory gene expression signature, and BRAF mutation status with tumor response, progression-free survival (PFS), and overall survival (OS) in patients with advanced melanoma. Patients and Methods Patients with known programmed death ligand 1 (PD-L1) expression and BRAF mutation status received nivolumab (NIVO) or dacarbazine in CheckMate 066 and either NIVO, ipilimumab (IPI), or NIVO+IPI in CheckMate 067. Whole exome sequencing and RNA sequencing were used to determine TMB and inflammatory gene expression signature scores, respectively. These biomarkers were evaluated in terms of their association with PFS and OS. Results In the NIVO, NIVO+IPI, and IPI arms of CheckMate 067, longer survival was associated with high (&gt; median) versus low (≤ median) TMB with hazard ratios (HRs) (95% confidence interval [CI]) for PFS of 0.45 (0.30–0.65), 0.55 (0.38–0.81), and 0.60 (0.43–0.82), and for OS of 0.46 (0.30–0.71), 0.53 (0.34–0.82), and 0.52 (0.36–0.74), respectively. For NIVO-treated patients, these results were confirmed in CheckMate 066. A survival benefit was observed with high TMB and absence of BRAF mutation. Survival was associated with high versus low inflammatory signature scores with HRs (95% CI) for PFS of 0.56 (0.34–0.94), 0.40 (0.23–0.72), and 0.43 (0.27–0.70), and for OS of 0.37 (0.20–0.66), 0.38 (0.19–0.74), and 0.46 (0.27–0.79), in the NIVO, NIVO+IPI, and IPI arms, respectively. Weak correlations were observed between PD-L1, TMB, and the inflammatory signature. Conclusions Combined assessment of TMB, inflammatory gene expression signature, and BRAF mutation status may be predictive for response to immunotherapy in advanced melanoma.

  Dataset EGAD00001007573

• Medulloblastoma cfDNA low-coverage WGS

  Whole genome sequencing of cell free DNA from CSF across timepoints from medulloblastoma clinical trial patients.

  Dataset EGAD00001008277

• A Randomized Trial of Combined PD-L1 and CTLA-4 Inhibition with Targeted Low-Dose or Hypofractionated Radiation for Patients with Metastatic Colorectal Cancer

  Brief SummaryThis randomized phase II trial studies the side effects of durvalumab and tremelimumab to see how well they work with or without high or low-dose radiation therapy in treating patients with colorectal (CRC) or non-small cell lung cancer (NSCLC) that has spread to other parts of the body (metastatic). Immunotherapy with durvalumab and tremelimumab may induce changes in body's immune system and may interfere with the ability of tumor cells to grow and spread. Radiation therapy uses high energy x-rays to kill tumor cells and shrink tumors. Giving durvalumab and tremelimumab with radiation therapy may work better in treating patients with colorectal or non-small cell lung cancer.Detailed DescriptionPRIMARY OBJECTIVES:I. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 (durvalumab) and tremelimumab alone or with high or low-dose radiation in non-small cell lung cancer (NSCLC). (NSCLC Cohort) II. To compare the overall response (excluding the irradiated lesion[s]) between combined checkpoint blockade with MEDI4736 and tremelimumab alone or combined checkpoint blockade with low or high dose radiation. (NSCLC Cohort) III. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 and tremelimumab with high or low-dose radiation. (Colorectal Cohort) IV. To determine the overall response rate (excluding the irradiated lesion[s]) with combined checkpoint blockade with MEDI4736 and tremelimumab with either low or high dose radiation. (Colorectal Cohort)SECONDARY OBJECTIVES:I. To estimate median progression-free survival and overall survival. (NSCLC Cohort) II. To determine local control within the irradiated field(s) and abscopal response rates. (NSCLC Cohort) III. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells and overall response. (NSCLC Cohort) IV. To explore changes in PD-L1 expression, circulating T-cell populations, T-cell infiltration, ribonucleic acid (RNA) expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (NSCLC Cohort) V. To estimate median progression-free survival and overall survival. (Colorectal Cohort) VI. To determine local control within the irradiated field and abscopal response rates. (Colorectal Cohort) VII. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+ CD8+ T-cells and overall response. (Colorectal Cohort) VIII. To evaluate changes between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells induced by targeted low or high dose radiation. (Colorectal Cohort) IX. To explore changes in circulating T-cell populations, T-cell infiltration, RNA expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (Colorectal Cohort)OUTLINE: Patients are assigned to 1 of 2 cohorts. NOTE: This Study is only for Cohort 2. Please see phs003295 for Cohort 1COHORT 1: Patients with NSCLC are randomized to 1 of 3 arms.ARM A: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.ARM C: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses.COHORT 2: Patients with CRC are randomized to 1 of 2 arms.ARM A: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.After completion of study treatment, patients are followed for up to 12 weeks.Official TitleA Phase 2 Study of MEDI4736 (Durvalumab) and Tremelimumab Alone or in Combination With High or Low-Dose Radiation in Metastatic Colorectal and NSCLC Conditions Metastatic Colorectal CarcinomaMetastatic Lung Non-Small Cell CarcinomaStage IV Colorectal Cancer AJCC v7Stage IV Lung Non-Small Cell Cancer AJCC v7Stage IVA Colorectal Cancer AJCC v7Stage IVB Colorectal Cancer AJCC v7 Intervention/Treatment Biological: DurvalumabRadiation: Radiation TherapyBiological: Tremelimumab Other Study ID Numbers NCI-2016-01325NCI-2016-01325 ( Registry Identifier ) (REGISTRY: CTRP (Clinical Trial Reporting Program))17-71910021 ( Other Identifier ) (OTHER: Dana-Farber - Harvard Cancer Center LAO)10021 ( Other Identifier ) (OTHER: CTEP) Molecular Technologies/AssaysIHCmIFOlinkCyTOFRNAseqWES

  Study phs003294

• Durvalumab Plus Tremelimumab Alone or in Combination with Low-Dose or Hypofractionated Radiotherapy in Metastatic Non-Small-Cell Lung Cancer Refractory to Previous PD(L)-1 Therapy: an Open-Label, Multicentre, Randomised, Phase 2 Trial

  Brief SummaryThis randomized phase II trial studies the side effects of durvalumab and tremelimumab and to see how well they work with or without high or low-dose radiation therapy in treating patients with colorectal or non-small cell lung cancer that has spread to other parts of the body (metastatic). Immunotherapy with durvalumab and tremelimumab, may induce changes in body's immune system and may interfere with the ability of tumor cells to grow and spread. Radiation therapy uses high energy x-rays to kill tumor cells and shrink tumors. Giving durvalumab and tremelimumab with radiation therapy may work better in treating patients with colorectal or non-small cell lung cancer.Detailed DescriptionPRIMARY OBJECTIVES:I. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 (durvalumab) and tremelimumab alone or with high or low-dose radiation in non-small cell lung cancer (NSCLC). (NSCLC Cohort) II. To compare the overall response (excluding the irradiated lesion[s]) between combined checkpoint blockade with MEDI4736 and tremelimumab alone or combined checkpoint blockade with low or high dose radiation. (NSCLC Cohort) III. To assess safety and tolerability of combined checkpoint blockade with MEDI4736 and tremelimumab with high or low-dose radiation. (Colorectal Cohort) IV. To determine the overall response rate (excluding the irradiated lesion[s]) with combined checkpoint blockade with MEDI4736 and tremelimumab with either low or high dose radiation. (Colorectal Cohort)SECONDARY OBJECTIVES:I. To estimate median progression-free survival and overall survival. (NSCLC Cohort) II. To determine local control within the irradiated field(s) and abscopal response rates. (NSCLC Cohort) III. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells and overall response. (NSCLC Cohort) IV. To explore changes in PD-L1 expression, circulating T-cell populations, T-cell infiltration, ribonucleic acid (RNA) expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (NSCLC Cohort) V. To estimate median progression-free survival and overall survival. (Colorectal Cohort) VI. To determine local control within the irradiated field and abscopal response rates. (Colorectal Cohort) VII. To evaluate associations between PD-L1 expression as well as levels of infiltrating CD3+ CD8+ T-cells and overall response. (Colorectal Cohort) VIII. To evaluate changes between PD-L1 expression as well as levels of infiltrating CD3+, CD8+ T-cells induced by targeted low or high dose radiation. (Colorectal Cohort) IX. To explore changes in circulating T-cell populations, T-cell infiltration, RNA expression, spatial relationship of immune markers, and mutational burden as a result of low or high dose radiation. (Colorectal Cohort)OUTLINE: Patients are assigned to 1 of 2 cohorts. NOTE: This Study is only for Cohort 1. Please see phs003294 for Cohort 2COHORT 1: Patients with NSCLC are randomized to 1 of 3 arms.ARM A: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab and durvalumab and as in Arm C. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.ARM C: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses.COHORT 2: Patients with CRC are randomized to 1 of 2 arms.ARM A: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive high dose radiation therapy once per day (QD) over 10 days for up to 3 fractions.ARM B: Patients receive tremelimumab intravenously (IV) and durvalumab IV over 60 minutes every 4 weeks for up to 16 weeks in the absence of disease progression or unacceptable toxicity. Patients then receive durvalumab IV over 60 minutes 4 weeks after last combination dose for up to 9 additional doses. Beginning at week 2, patients receive low dose radiation therapy every 6 hours twice per day (BID) on weeks 2, 6, 10 and 14.After completion of study treatment, patients are followed for up to 12 weeks.Official TitleA Phase 2 Study of MEDI4736 (Durvalumab) and Tremelimumab Alone or in Combination With High or Low-Dose Radiation in Metastatic Colorectal and NSCLC Conditions Metastatic Colorectal CarcinomaMetastatic Lung Non-Small Cell CarcinomaStage IV Colorectal Cancer AJCC v7Stage IV Lung Non-Small Cell Cancer AJCC v7Stage IVA Colorectal Cancer AJCC v7Stage IVB Colorectal Cancer AJCC v7 Intervention/Treatment Biological: DurvalumabRadiation: Radiation TherapyBiological: Tremelimumab Other Study ID Numbers NCI-2016-01325NCI-2016-01325 ( Registry Identifier ) (REGISTRY: CTRP (Clinical Trial Reporting Program))17-71910021 ( Other Identifier ) (OTHER: Dana-Farber - Harvard Cancer Center LAO)10021 ( Other Identifier ) (OTHER: CTEP) Molecular Technologies / AssaysCyTOFIHCmIFOlinkRNAseqWES

  Study phs003295

• eMERGE Network Imputed GWAS for 41 Phenotypes

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of ten participating sites (Cincinnati Children&#39;s Hospital Medical Center/Boston Children&#39;s Hospital, Children&#39;s Hospital of Philadelphia, Essentia Institute of Rural Health, Marshfield Clinic Research Foundation and Pennsylvania State University, Geisinger Clinic, Group Health Cooperative/University of Washington, Mayo Clinic, Icahn School of Medicine at Mount Sinai, Northwestern University, Vanderbilt University Medical Center) funded by the NHGRI to investigate the use of electronic medical record (EMR) systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 55,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of over forty phenotypes, including 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, as well as using the phenome-wide association study (PheWAS) paradigm to replicate and discover relationships between targeted genotypes with multiple phenotypes. Sites and participants include: Children&#39;s Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children&#39;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&#39;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 medical records (EMRs). EMRs are longitudinal, with a mean duration of 6.5 years. Cincinnati Children&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): Cincinnati Children&#39;s Hospital Medical Center (CCHMC) and Boston Children&#39;s Hospital (BCH) are pediatric institutions dedicated to improving health and welfare of children and to the shared purpose of discovery and practical application of new genomic information to the ordinary care of children. The CCHMC/BCH site has been built on a five-year history of collaboration, particularly in patient electronic record (ERM)-related informatics, the basis of much of eMERGE II. CCHMC and BCH together bring an extraordinary faculty to eMERGE II who are committed to diseases that afflict children, specifically phenotypes that focus upon diseases of children in ways that will leverage the available eMERGE adult GWAS and EMRs to discover meaningful use results. CCHMC/BCH plans to demonstrate real-time execution of phenotypic selection across their two distinct pediatric institutions as a model for ensuring phenotypic standardization and for national scalability. They will also look carefully at parents&#39; responses to results and use of their children&#39;s research results and better understand the factors that influence their decisions about learning incidental findings. In addition to patient and parent perceptions CCHMC/BCH will also explore clinician perceptions of pharmacogenetic research results after EMR integration. 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. Group Health(GH)/University of Washington (UW): 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&#39;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 participants had any laboratory event of creatine kinase (CK) &#62;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): 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 biobank 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 &#60;1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR. 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&#39; 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: BioVU, Vanderbilt&#39;s DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt&#39;s EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations.

  Study phs000888

• Women's Health Initiative Clinical Trial and Observational Study

  The Women&#39;s Health Initiative (WHI) is a long-term national health study that has focused on strategies for preventing heart disease, breast and colorectal cancer, and osteoporotic fractures in postmenopausal women. The original WHI study included 161,808 postmenopausal women enrolled between 1993 and 1998. The Fred Hutchinson Cancer Research Center in Seattle, WA serves as the WHI Clinical Coordinating Center for data collection, management, and analysis of the WHI. The WHI has two major parts: a partial factorial randomized Clinical Trial (CT) and an Observational Study (OS); both were conducted at 40 Clinical Centers nationwide. The CT enrolled 68,132 postmenopausal women between the ages of 50-79 into trials testing three prevention strategies. If eligible, women could choose to enroll in one, two, or all three of the trial components. The components are: Hormone Therapy Trials (HT): This double-blind component examined the effects of combined hormones or estrogen alone on the prevention of coronary heart disease and osteoporotic fractures, and associated risk for breast cancer. Women participating in this component with an intact uterus were randomized to estrogen plus progestin (conjugated equine estrogens [CEE], 0.625 mg/d plus medroxyprogesterone acetate [MPA] 2.5 mg/d] or a matching placebo. Women with prior hysterectomy were randomized to CEE or placebo. Both trials were stopped early, in July 2002 and March 2004, respectively, based on adverse effects. All HT participants continued to be followed without intervention until close-out. Dietary Modification Trial (DM): The Dietary Modification component evaluated the effect of a low-fat and high fruit, vegetable and grain diet on the prevention of breast and colorectal cancers and coronary heart disease. Study participants were randomized to either their usual eating pattern or a low-fat dietary pattern. Calcium/Vitamin D Trial (CaD): This double-blind component began 1 to 2 years after a woman joined one or both of the other clinical trial components. It evaluated the effect of calcium and vitamin D supplementation on the prevention of osteoporotic fractures and colorectal cancer. Women in this component were randomized to calcium (1000 mg/d) and vitamin D (400 IU/d) supplements or a matching placebo. The Observational Study (OS) examines the relationship between lifestyle, environmental, medical and molecular risk factors and specific measures of health or disease outcomes. This component involves tracking the medical history and health habits of 93,676 women not participating in the CT. Recruitment for the observational study was completed in 1998 and participants were followed annually for 8 to 12 years. Extension Studies: The original protocol allowed for follow-up until March 2005, after which participants were invited to enroll in the first WHI Extension Study for follow-up through 2010. Participants were invited again to participate in the second WHI Extension Study with continued follow up from 2010 to at least 2015. As of March 31, 2011 there were 93,122 women enrolled in the second extension. In Extension Study 2, the overall WHI study population was divided into two new subsamples, the Medical Records Cohort (MRC) and the Self-Report Cohort (SRC). The MRC consists of all former hormone trial participants and all African American and Hispanic participants from all study components. The SRC consists of the remaining participants. The extent of outcome information collected differs between the two cohorts, with more extensive outcomes information collection on the MRC. As part of Extension Study 2, selected older WHI participants were invited to participate in an In Person Visit (a.k.a., Long Life Study) at their homes during which additional blood samples were collected and various measurements were taken (such as blood pressure, height, weight, waist circumference, grip strength, etc.). In October 2015, Extension Study 2 was renewed with continued follow-up planned through October 2020, pending annual contract review and renewal. Additional Information: The WHI website, https://www.whi.org/about/SitePages/About%20WHI.aspx has much more information about the study. For WHI data collection forms used over the years, please see https://www.whi.org/researchers/studydoc/SitePages/Forms.aspx. For additional dataset documentation, see https://www.whi.org/researchers/data/Pages/Available%20Data.aspx. For data preparation and use, please refer to &#39;WHI dbGaP Cohort Data Release Data Preparation Guide May 2018&#39; for additional details about the WHI data. The WHI Cohort is utilized in the following dbGaP substudies. To view genotypes, analysis, expression data, other molecular data, and derived variables collected in these substudies, please click on the following substudies below or in the "Substudies" box located on the right hand side of this top-level study page phs000200 WHI Cohort. phs000386 WHI SHARe phs000281 GO-ESP WHISP phs000315 WHI GARNET phs000503 WHISE phs000227 PAGE WHI phs000675 WHIMS+ phs000746 WHI Harmonized and Imputed GWAS phs001334 WHI Metabolomics of CHD phs001335 WHI BA23 phs001614 WHI LLS Phase III GWAS

  Study phs000200

• International Standards for Cytogenomic Arrays

  The International Standards for Cytogenomic Arrays (ISCA) Consortium is a rapidly growing group of clinical cytogenetics and molecular genetics laboratories committed to improving quality of patient care related to clinical genetic testing using new molecular cytogenetic technologies including array comparative genomic hybridization (aCGH) and quantitative SNP analysis by microarrays or bead chip technology. The ISCA Consortium is now working with the sequencing community to extend the goals of standardization, collaboration, and data sharing. To reflect this combined effort, we are becoming ICCG, or the International Collaboration for Clinical Genomics. Efforts of the Consortium include: Clinical Utility: The ISCA Consortium has made recommendations regarding the appropriate clinical indications for cytogenetic array testing (Miller et al. AJHG 2010, PMID: 20466091). Currently, discussions are focused on pediatric applications for children with unexplained developmental delay, intellectual disability, autism and other developmental disabilities. A separate committee has been developed to address appropriate cancer genetic applications (http://www.urmc.rochester.edu/ccmc/). Evidence-based standards for cytogenomic array design: The Consortium will develop recommendations for standards for the design, resolution and content of cytogenomic arrays using an evidence-based process and an international panel of experts in clinical genetics, clinical laboratory genetics (cytogenetics and molecular genetics), genomics and bioinformatics. This design is intended to be platform and vendor-neutral (common denominator is genome sequence coordinates), and is a dynamic process with input from the broader genetics community and evidence-based review by the expert panel (a Steering Committee with international representation). Public Database for clinical and research community: It is essential that a publicly available database be created and maintained for cytogenetic array data generated in clinical testing laboratories. This will be integrated into the current dbGaP database at NCBI/NIH and released through dbVar, and curated by a committee of clinical genetics laboratory experts. The very high quality of copy number data (i.e., deletions and duplications) coming from clinical laboratories combined with expert curation will produce an invaluable resource to the clinical and research communities. Standards for interpretation of cytogenetic array results: Using the ISCA Database, along with other genomic and genetics databases, the Consortium will develop recommendations for the interpretation and reporting of pathogenic vs. benign copy number changes as well as imbalances of uncertain clinical significance. Membership in the ISCA Consortium is open to all individuals and laboratories involved in cytogenetic array testing who are committed to free data sharing and to participation in a process to develop evidence-based standards and guidelines to improve patient care. ISCA is available through dbVar: http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd37/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd75/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd45/ http://www.ncbi.nlm.nih.gov/dbvar/studies/nstd101/

  Study phs000205

• Exploratory novel biomarker and resistance mechanism of milademetan, an MDM2 inhibitor, in MDM2 amplified intimal sarcoma from an open-label phase 1b/2 trial ���NCCH1806/MK004���

  Amplified Murine double minute 2 (MDM2) is found in > 70% of intimal sarcoma, known as one of the ultra-rare sarcomas. Milademetan (DS3032, RAIN-32) is a novel, specific, small-molecule MDM2 inhibitor that disrupts MDM2 and the tumor suppressor protein p53 interactions in tumor cells. We conducted a phase 1b/2 trial (Trial registration No: JMA-IIA00402) in patients with amplified MDM2 wild-type TP53 intimal sarcoma as a sub-study under the nationwide large registry for rare cancers in Japan (MASTERKEY Project). Eleven patients were enrolled, and ten were included in the efficacy analysis. Two (20%) patients had durable responses for > 15 months. Milademetan provided clinical benefits in patients with amplified MDM2 intimal sarcoma. Predictive biomarkers other than amplified MDM2 and acquired resistance mechanisms for milademetan are unknown. Whole-exome and RNA sequencing analyses of pre-treatment tissue samples were conducted to identify determinants of response. Genomic alterations were analyzed for 10 patients, and gene expression was analyzed for 9 patients using their pre-treatment tissue samples. Targeted sequencing of cell-free DNA (cfDNA) samples (liquid biopsy) was also conducted sequentially at three points [before treatment with milademetan (baseline), at Cycle 2 Day1, and at the time of disease progression] to identify determinants of response and resistance. From whole-exome and RNA sequencing analyses of pre-treatment tissue samples, we could not find any molecular pathways associated with the anti-tumor activity of milademetan. Focusing on 8 genes (CDK4, CDKN2A, CDKN2B, EGFR, ERBB3, MDM2, PDGFRA, TP53) known to be frequently affected in intimal sarcoma and 10 genes (AKT1, ATM, BBC3, CDKN1A, CDKN1C, CHEK2, MDM4, PMAIP1, PPM1D, TWIST1) reported to be associated with MDM2 inhibitor responses; we found that anti-tumor activity correlated with amplified TWIST1 (p-value = 0.028) and negatively with CDKN2A loss (p-value = 0.071). Eight of the 10 patients had their cfDNA collected sequentially at baseline, at Cycle 2 Day1 and disease progression; however, one did not consent to the exploratory analysis study using cfDNA, and one had cfDNA collected at baseline but not at disease progression due to ongoing treatment. Of the eight patients, TP53 mutations in cfDNA were detected in one and five patients at baseline and disease progression, respectively. The cfDNA allele frequency of TP53 mutations increased with disease progression. CDKN2A loss and amplified TWIST1 could be associated with the anti-tumor activity of milademetan in patients with MDM2 amplified intimal sarcoma. Acquired TP53 mutations were detected in sequential liquid biopsies as loss-of-function mutations, and these TP53 mutations might compromise the anti-tumor activity.

  Study JGAS000619

• GEnomics and Transcriptomics of Human INsulinoma (GETHIN)

  The Genomics and Transcriptomics of Human Insulinoma (GETHIN) The common forms of diabetes - Types 1 and 2 - ultimately result from a deficiency of insulin-producing pancreatic beta cells. The Genomics and Transcriptomics of Human Insulinoma (GETHIN) study was performed in order to identify novel approaches to inducing human pancreatic beta cells to replicate and regenerate. As a corollary, developing drugs that are able to expand human beta cell mass in people with diabetes should reverse diabetes. Unfortunately, identifying druggable pathways that can enhance human beta cell replication has been a major challenge. In 2017, there is only one class of drugs - the harmine analogues - that can induce human beta cells to replicate, and in this case, higher replication rates are desirable. Thus, identifying additional drugs and druggable pathways is a priority in diabetes research. Insulinomas are rare, benign adenomas of the pancreatic beta cell that cause excess insulin production and hypoglycemia: exactly the opposite of Types 1 and 2 diabetes. Beta cell proliferation rates in insulinomas are abnormally high. Thus, the premise for The Genomics and Transcriptomics of Human Insulinoma study is that benign human insulinomas hold the genomic and transcriptomic "recipe", and the repertoire of druggable pathways, that can be exploited to induce regeneration or replication of human beta cells in diabetes. Because, insulinomas are so rare, are almost always benign (non-malignant), and are easily resected by laparoscopic surgery, little attention has been paid to understanding the genomics or transcriptomics of insulinoma. There are at present only three published studies employing next-gen sequencing in insulinoma (PMID:24326773; PMID:25787250; and PMID:25763608). These studies contained 10, 7 and 8 insulinomas, respectively, and highlighted likely mutations in YY1 and MEN1. Our goal was to markedly expand the database and to add RNAseq to these earlier studies. The GETHIN study reports next-gen sequencing on 38 insulinomas, by far the largest series of human insulinomas subjected to next-gen sequencing (see the Selected publications section for reference). This includes paired (genomic plus tumor) whole exome sequencing on 26 human insulinomas (22 sequenced at Mount Sinai, 4 downloaded from Cao et al, PMID:24326773), and 25 sets of RNAseq from insulinomas, some of which also had paired whole exome sequencing, and some of which did not. The insulinoma RNAseq was compared to RNAseq from 22 sets of FACS-sorted normal human beta cells. Since insulinomas are so rare, the 38 insulinomas were collected by several investigators at several institutions over several decades, but most (22 whole exome sets, and all RNAseq) were sequenced at the Icahn School of Medicine at Mount Sinai in New York. The current dataset contains whole exome sequencing and RNAseq on the 11 insulinomas harvested at Mount Sinai. The four from Cao et al can be retrieved from Cao et al PMID:24326773. Fastq files from the remaining 23 insulinomas will be added as the local IRBs and Institutional Certifications are acquired. Complete patient data are provided in our Nature Communications report. Going forward, our intention is to expand this series, with the goal of sequencing 100 human insulinomas. These will be added to dbGaP as they accrue. Paired-end whole exome sequencing (mean usable sequencing depth 79X and 105X for blood and insulinoma, respectively) was performed using an Illumina HiSeq 2500. Insulinoma and sorted normal beta cell RNAseq was performed on Ribozero and polyA paired end libraries using the Illumina HiSeq 2500. Complete sequencing and bioinformatic details are provided in our Nature Communications report. The principal findings from the study are that although each insulinoma has a different set of presumptive driver mutations, the majority converge on genes that are members of the Polycomb Complex, Trithorax Complex and other epigenetic modifying enzymes. In addition, 20% of insulinomas have copy number loss or loss of heterozygosity of all or most of chromosome 11, and the majority display abnormalities in CpG methylation and imprinting control on the imprinted Chr 11 p15.5-15.4 region that contains INS, IGF2, CDKN1C, KCNQ1, and other genes involved in beta cell specification and proliferation.

  Study phs001422

• TRanscriptomic ANalySis of left ventriCulaR gene Expression (TRANSCRibE)

  Myocardial ischemia occurs when there is a mismatch between coronary oxygen delivery and metabolic requirements of the myocardium, which may be clinically manifested during angina, coronary angioplasty or cardiopulmonary bypass (CPB). Myocardial ischemia may lead to a spectrum of myocardial stunning, hibernating myocardium, and ultimately cell death if the ischemic insult is severe. In the human heart, irreversible damage begins after approximately 20 to 40 minutes of oxygen deprivation. Observed molecular and cellular changes of myocardial ischemia are characteristic of an inflammatory response, but the exact mechanisms that underlie this pathological process are unclear and may not be full emulated by animal models of ischemia or infarction. Thus, we felt it valuable to investigate a human ischemia model. During cardiac surgery, CPB with aortic cross-clamping (AoXC) and cardioplegic arrest is associated with excellent clinical outcomes and suitable operative conditions. However, despite the use of cardioprotective strategies, AoXc during CPB is accompanied by a variable, yet obligate ischemic period lasting 1 to 3 hours, resulting in hypoxia, metabolic substrate depletion, reperfusion injury, apoptosis, and necrosis. Cardiac specific biomarkers of ischemia and infarction, including troponin, are elevated even after routine coronary artery bypass graft surgery and correlate with the duration of ischemia from AoXc.This process of CPB provides us with the ability to examine the transcriptional profile before and after an expected, consistent, and reproducible human ischemic event, albeit induced by cold cardioplegic arrest and not coronary occlusion. In addition, the absence of reperfusion in this time period allows us to examine the transcriptomic response to intermittent ischemia, without having to account for the perturbations of reperfusion injury. Although various animal models have been used to examine the effects of ischemia on cardiac function, no human data exist which examine the early transcriptomic response to a left ventricular (LV) ischemic insult. We therefore characterized the effect of cold cardioplegia induced acute ischemia on the transcriptional profile of the LV by performing whole transcriptome next-generation RNA-sequencing (RNA-seq) in patients undergoing cardiac surgery by sampling human LV tissue prior to, and after, the obligate ischemia during AoXC. We hypothesized that the cold cardioplegia induced ischemic injury will dramatically alter transcription in the human myocardium, and that we would identify genes and pathways, which will identify interventional targets for pharmacological therapy. Methods:We have collected left ventricle tissue samples and blood sample from patients undergoing heart surgery. We obtained punch biopsies (~3-5&#956;g total RNA content) from the site of a routinely placed surgical vent in the anterolateral apical left ventricular wall of patients undergoing elective aortic valve replacement surgery with cardiopulmonary bypass. After an average of 79 minutes of aortic cross-clamping with intermittent cold blood cardioplegia for myocardial protection every 20 minutes, a second biopsy was obtained in the same manner. Tissue samples were immediately placed in RNAlater&#174; (Ambion, ThermoFisher Scientific, Waltham, MA), and after 48 hours at +4&#176;C were stored at -80&#176;C until RNA extraction. Total RNA was isolated with Trizol and RNA quality was assessed using the Agilent Bioanalyzer 2100 (Agilent, Santa Clara, CA). Libraries were prepared by poly(A) mRNA isolation and reverse transcription Polymerase Chain Reaction (RT-PCR), then sequenced on the Illumina HiSeq2000 or HiSeq2500 (Illumina, San Diego, CA). As samples were analyzed at different times, different read lengths were employed, initially using single-end reads (n=20) and then transitioning to paired end reads (n=216), ranging from 36 - 100 base pairs. Raw sequencing files were processed using Sickle, Skewer, and STAR software, and aligned to GrCh37 or UCSC Hg19. DNA was isolated from whole blood using standard methods. SNP genotyping was performed using the Illumina Omni2.5Exome-8 BeadChip array with additional exome content (Illumina, San Diego, CA) chip, version 1.1. We first phased and imputed 93 subjects using a phasing tool called SHAPEIT and an imputation tool called MINIMAC, with 1000 Genomes phase 1 version 3 for the reference panel. We then phased and imputed 26 more subjects using SHAPEIT, an imputation tool called IMPUTE2, and 1000 Genomes phase 3 version 5.

  Study phs001679

• 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

• 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&#39;s Hospital: The Gene Partnership (TGP) is a prospective longitudinal registry at Boston Children&#39;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&#39;preferences;results are returned through the Personally Controlled Health Record (PCHR). BCH and Cincinnati Children&#39;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&#39;s Hospital of Pennsylvania (CHOP): The Center for Applied Genomics (CAG) at the Children&#39;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&#39;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&#39;s Hospital Medical Center/Boston&#39;s Children&#39;s Hospital (CCHMC/BCH): Cincinnati Children&#39;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&#39;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&#39;s disease (AD), Alzheimer&#39;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&#39;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&#39;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&#39;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&#39;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&#39;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 &#60;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&#39;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&#39;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&#39;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 &#62;235,000 samples as of spring 2017.

  Study phs001584

• eMERGE Network Study of the Genetic Determinants of Resistant Hypertension

  The electronic Medical Records and Genomics (eMERGE) Network is a consortium of five participating sites (Group Health Seattle, Marshfield Clinic, Mayo Clinic, Northwestern University, and Vanderbilt University) funded by the NHGRI to investigate the use of electronic medical record systems for genomic research. The goal of eMERGE is to conduct genome-wide association studies in approximately 19,000 individuals using EMR-derived phenotypes and DNA from linked Biorepositories. Using electronic phenotyping methods, the consortium used DNA samples from all participating sites to explore the genetic determinants of resistant hypertension. Treatment resistant hypertension is a common health problem in the clinical setting. A basic definition of resistant hypertension included subjects with uncontrolled blood pressure despite use of three antihypertensive medications or subjects requiring four or more medications to maintain control. Other conditions, such as secondary causes of hypertension, were exclusions. Site and participants include: Vanderbilt University: BioVU, Vanderbilt&#39;s DNA databank, is an enabling resource for exploration of the relationships among genetic variation, disease susceptibility, and variable drug responses, and represents a key first step in moving the emerging sciences of genomics and pharmacogenomics from research tools to clinical practice. BioVU acquires DNA from discarded blood samples collected from routine patient care. The biobank is linked to de-identified clinical data extracted from Vanderbilt&#39;s EMR, which forms the basis for phenotype definitions used in genotype-phenotype correlations. Marshfield Clinic: 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. 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&#39; 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. Group Health(GH)/University of Washington (UW): Aging and Dementia eMERGE study biorepository leverages rich population-based longitudinal data from both electronic medical records and in-depth research data to explore genome wide associations. Participants include Seattle-area members of GH (a large integrated health care system in Washington State) consented and enrolled in 1) the UW Alzheimer&#39;s Disease Patient Registry (ADPR) and 2) the Adult Changes in Thought (ACT) study. The ADPR (PI: Eric B. Larson; NIH/NIA U01 AG 006781) is a population-based registry of incident dementia cases designed to identify all new Alzheimer&#39;s Disease cases within GH from 1987 to 1996. Medical history, physical, laboratory testing, and neuropsychological testing were performed on all consenting potential cases for determination of dementia status by a consensus conference. The study base of the ADPR population was stable with an attrition rate of less than 1%/year. The ACT study (PI: Eric B. Larson; NIH/NIA U01 AG 006781) is an ongoing community-based cohort study of aging and dementia. The original cohort of 2,581 randomly selected dementia-free members age 65 and older was enrolled in 1994-1996 and expanded by 811 in 2000-2002. Continuous enrollment to maintain a cohort of 2,000 dementia free persons began in 2005. Participants receive biennial assessment including cognitive status determination. The ACT sub-sample is stable; for the original cohort, median enrollment in GH was 19 years prior to joining the ACT study, and 85% of the cohort has &#8805; 10 years of GH enrollment. DNA for the ADPR participants were obtained through a companion study, Genetic Differences in Cases and Controls (PI: Walter Kukull; NIH/NIA R01 AG007584). DNA obtained through both studies were extracted from blood using Gentra Systems Puregene methods. DNA concentration is determined by UV optical density. All samples are checked for quality by 260/280 ratio. For long-term storage, samples are aliquoted and stored at -70&#176;C. Mayo Clinic: The Mayo biobank 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 &lt;1%. Data regarding risk factors for atherosclerosis such as diabetes, dyslipidemia, hypertension, and smoking are ascertained from the EMR.

  Study phs000297

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Genome-Wide Association Study of Celiac Disease

  Celiac disease (gluten-sensitive enteropathy, celiac sprue) is a common disease with significant morbidity and mortality. It is caused by sensitivity to the dietary protein gluten, resulting in a chronic enteropathy in the small intestine. Celiac disease is now recognized to be a common disease, with reports that the disease frequency is 1:133 in the United States, similar to European estimates. There is recent evidence to suggest that the incidence of the disease is rising. Occult disease is frequently present with minimal classic symptoms or signs. The ratio of symptomatic to asymptomatic celiac disease is estimated to be 1:7. Some complications of celiac disease include lymphoma, osteoporosis, anemia, miscarriages, seizures, vitamin deficiencies, and co-occurrence of other autoimmune diseases. The only treatment is a gluten-free diet, so that recurrence of symptoms and complications may occur after minor dietary indiscretions. Identifying the underlying genetic causes of celiac disease may allow us to identify susceptible individuals, as well as advance new ways to prevent the disease and to treat it once it occurs. Several genome-wide linkage studies and one genome-wide association study of celiac disease have been conducted. Other than the common locus at HLA, few putative celiac disease loci have been replicated between studies, suggesting that the disease is heterogeneous and complex. A portion of the genetic predisposition can be attributed to HLA, but the etiology is likely due to a number of rare, high penetrant genes (as would be identified in linkage analysis) and to more common, low penetrant genes (as would be identified in association studies). The objective of this study is to identify new loci that increase risk to develop celiac disease. We will capitalize on existing North American resources, including three large collections of celiac cases and controls (Aim 1) and an independent set of celiac cases and their families (Aim 3). We propose a comprehensive multi-stage approach, with the following specific aims. In Aim 1, we will conduct a genome-wide association (GWA) study of single nucleotide polymorphisms (SNPs) and copy number variants (CNVs). The GWA will include1900 disease cases and 3400 matched controls, genotyped using the Illumina Human 610-quad chip. Statistical analyses will be performed to test for associations with celiac disease. In Aim 2, we will conduct a combined analysis of our GWA dataset from Aim 1 and a previous GWA dataset to identify additional low-penetrance loci. In Aim 3, we will attempt to replicate significant findings from the GWA study in two independent sample sets. At the conclusion of this study, we expect to have validated a number of SNPs and CNPs from regions in the genome that alter the risk of developing celiac disease. These SNPs may prove useful at both the clinical and research level. The data from the study will be shared with the scientific community.

  Study phs000274