21148 results for "Buy fc 26 coins Buyfc26coins.com is EA Sports official for FC 26 coins The process was smooth and quick..ivNx"

in 27.58 milliseconds.

• BIONi010-C / SAMEA3158050 WGS data

  The iPSC line BIONi010-C / SAMEA3158050 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line BIONi010-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001039

• UKKi019-C / SAMEA17626918 WGS data

  The iPSC line UKKi019-C / SAMEA17626918 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi019-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001042

• EDi011-B / SAMEA4459359 WGS data

  The iPSC line EDi011-B / SAMEA4459359 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi011-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001044

• EDi011-C / SAMEA4459360 WGS data

  The iPSC line EDi011-C / SAMEA4459360 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi011-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001045

• EDi012-A / SAMEA4459361 WGS data

  The iPSC line EDi012-A / SAMEA4459361 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi012-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001046

• EDi015-A / SAMEA4459373 WGS data

  The iPSC line EDi015-A / SAMEA4459373 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi015-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001047

• EDi015-C / SAMEA4459376 WGS data

  The iPSC line EDi015-C / SAMEA4459376 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi015-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001048

• EDi017-B / SAMEA4770418 WGS data

  The iPSC line EDi017-B / SAMEA4770418 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi017-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001049

• EDi011-A / SAMEA4459357 WGS data

  The iPSC line EDi011-A / SAMEA4459357 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi011-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001050

• EDi013-B / SAMEA4459367 WGS data

  The iPSC line EDi013-B / SAMEA4459367 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi013-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001052

• BIONi010-A / SAMEA3105765 WGS data

  The iPSC line BIONi010-A / SAMEA3105765 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line BIONi010-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001054

• UKKi019-B / SAMEA17626168 WGS data

  The iPSC line UKKi019-B / SAMEA17626168 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi019-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001096

• UKKi019-A / SAMEA17624668 WGS data

  The iPSC line UKKi019-A / SAMEA17624668 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi019-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001094

• EDi019-B / SAMEA4776418 WGS data

  The iPSC line EDi019-B / SAMEA4776418 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi019-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001091

• EDi016-C / SAMEA4768168 WGS data

  The iPSC line EDi016-C / SAMEA4768168 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi016-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001090

• UOXFi008-B / SAMEA103887561 WGS data

  The iPSC line UOXFi008-B / SAMEA103887561 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UOXFi008-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001089

• EDi017-C / SAMEA4771168 WGS data

  The iPSC line EDi017-C / SAMEA4771168 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi017-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001087

• EDi016-B / SAMEA4767418 WGS data

  The iPSC line EDi016-B / SAMEA4767418 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi016-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001086

• WTSIi009-A / SAMEA2593858 WGS data

  The iPSC line WTSIi009-A / SAMEA2593858 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line WTSIi009-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001085

• UKKi022-C / SAMEA103988349 WGS data

  The iPSC line UKKi022-C / SAMEA103988349 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi022-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001084

• UKKi021-B / SAMEA103988346 WGS data

  The iPSC line UKKi021-B / SAMEA103988346 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi021-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001083

• UKKi020-C / SAMEA103988344 WGS data

  The iPSC line UKKi020-C / SAMEA103988344 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi020-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001082

• EDi018-C / SAMEA4774168 WGS data

  The iPSC line EDi018-C / SAMEA4774168 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi018-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001081

• EDi018-B / SAMEA4773418 WGS data

  The iPSC line EDi018-B / SAMEA4773418 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi018-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001080

• UOXFi007-A / SAMEA103988274 WGS data

  The iPSC line UOXFi007-A / SAMEA103988274 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UOXFi007-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001079

• RCi007-C / SAMEA4084916 WGS data

  The iPSC line RCi007-C / SAMEA4084916 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RCi007-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001072

• RCi005-A / SAMEA3961534 WGS data

  The iPSC line RCi005-A / SAMEA3961534 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RCi005-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001071

• RCi004-B / SAMEA3106205 WGS data

  The iPSC line RCi004-B / SAMEA3106205 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RCi004-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001070

• RCi004-A / SAMEA3106011 WGS data

  The iPSC line RCi004-A / SAMEA3106011 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RCi004-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001069

• UKKi018-C / SAMEA103988380 WGS data

  The iPSC line UKKi018-C / SAMEA103988380 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi018-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001067

• EDi015-B / SAMEA4459375 WGS data

  The iPSC line EDi015-B / SAMEA4459375 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi015-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001066

• EDi013-C / SAMEA4459368 WGS data

  The iPSC line EDi013-C / SAMEA4459368 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi013-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001065

• EDi012-C / SAMEA4459364 WGS data

  The iPSC line EDi012-C / SAMEA4459364 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi012-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001064

• EDi012-B / SAMEA4459363 WGS data

  The iPSC line EDi012-B / SAMEA4459363 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi012-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001063

• UKKi017-C / SAMEA17621668 WGS data

  The iPSC line UKKi017-C / SAMEA17621668 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line UKKi017-C is available for research use at www.EBiSC.org.

  Dataset EGAD50000001061

• EDi013-A / SAMEA4459365 WGS data

  The iPSC line EDi013-A / SAMEA4459365 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi013-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001057

• EDi010-B / SAMEA4459356 WGS data

  The iPSC line EDi010-B / SAMEA4459356 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line EDi010-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001056

• RBi001-A / SAMEA3368212 WGS data

  The iPSC line RBi001-A / SAMEA3368212 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RBi001-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001058

• RCi006-A / SAMEA3962402 WGS data

  The iPSC line RCi006-A / SAMEA3962402 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line RCi006-A is available for research use at www.EBiSC.org.

  Dataset EGAD50000001059

• BIONi010-B / SAMEA3158000 WGS data

  The iPSC line BIONi010-B / SAMEA3158000 has undergone whole genome sequencing. Whole genome sequencing was done using Illumina HiSeq X Five platform with a reference genome of GRCh38. Raw data as FASTQ files and analysed data as CRAM files are available for this sample, in this dataset. The iPSC line BIONi010-B is available for research use at www.EBiSC.org.

  Dataset EGAD50000001055

• Exome_trios_in_patients_with_gastroschisis

  Gastroschisis (MIM 230750) is a herniation of the intestines through a defect of the abdominal wall lateral to the umbilicus (usually on the right side), and it is not covered by a membrane [Ledbetter, 2012]. Gastroschisis is a congenital anomaly with increasing incidence, easy prenatal diagnosis and extremely variable postnatal outcomes. On the basis of clinical manifestations, epidemiologic charateristics, and the presence and type of additional malformations, gastroschisis could be considered a heterogeneous condition with no gene/s discovered yet. This congenital anomaly affects approximately 1-3 infancts per 10,000 live births [Calzolari et al.1995;Parker et al.,2010] Current knowledge about causative mutations/variants. To date, no single gene has been linked to gastroschisis. Some publications have tried to link this malformation to variants in genes (such as AEBP1 (adipocyte enhancer binding protein) gene [Feldkamp et al,. 2012] or the VEGF-NOS3 pathway [Lammer et al., 2008]. Previously, a Scribble mutant mouse model (circletail) was reported to exhibit gastroschisis, however recent studies demonstrated that the Scribble knockout fetus exhibits exomphalos phenotype of gastroschisis [Carnagham et al., 2013]. This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Study EGAS00001002664

• 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

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

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

  Study phs000547

• Whole exome sequencing of germline DNA was performed and subsequent polymorphisms in genes known and putatively involved in the innate immune response to fungi were identified

  Disease can be conceptualized as the result of interactions between infecting microbe and holobiont, the combination of a host and its microbial communities. It is likely that genomic variation in the host, infecting microbe, and commensal microbiota are key determinants of infectious disease clinical outcomes. However, until recently, simultaneous, multiomic investigation of infecting microbe and holobiont components has rarely been explored. Herein, we characterized the infecting microbe, host, micro- and mycobiomes leading up to infection onset in a leukemia patient that developed invasive mucormycosis. We discovered that the patient was infected with a strain of the recently described Mucor velutinosus species which we determined was hypervirulent in a Drosophila challenge model and has a predisposition for skin dissemination. After completing the infecting M. velutinosus genome and genomes from four other Mucor species, comparative pathogenomics was performed and assisted in identifying 66 M. velutinosus-specific putatively secreted proteins, including multiple novel secreted aspartyl proteinases which may contribute to the unique clinical presentation of skin dissemination. Whole exome sequencing of the patient revealed multiple non-synonymous polymorphisms in genes critical to control of fungal proliferation, such as TLR6 and PTX3. Moreover, the patient had a non-synonymous polymorphism in the NOD2 gene and a missense mutation in FUT2, which have been linked to microbial dysbiosis and microbiome diversity maintenance during physiologic stress, respectively. In concert with host genetic polymorphism data, the micro- and mycobiome analyses revealed that the infection developed amid a dysbiotic microbiome with low α-diversity, dominated by staphylococci. Additionally, longitudinal mycobiome data showed that M. velutinosus DNA was detectable in oral samples preceding disease onset. Our genome-level study of the host-infecting microbe-commensal triad extends the concept of personalized genomic medicine to the holobiont-infecting microbe interface thereby offering novel opportunities for using synergistic genetic methods to increase understanding of infectious diseases pathogenesis and clinical outcomes.

  Study EGAS00001001542

• Breast Cancer in Blacks: Impact of Genomics, Healthcare Use and Lifestyle on Outcomes (BRIGHT)

  Young Black females bear a disproportionate burden of breast cancer (BC) mortality compared to White females and are underrepresented in clinical studies. It remains critical to understand factors that contribute to the high mortality from BC among young Black females in order to improve outcomes. The higher BC mortality rate among young Black females with breast cancer is partially attributed to the disproportionately higher proportions who develop the aggressive triple-negative breast cancer (TNBC). In addition to biologic factors, timely access to care, and lifestyle factors contribute to this disparity. Consequently, we sought to evaluate the interplay between biologic and non-biologic contributors to BC outcomes (i.e., BC disease-free survival (DFS)), and to better characterize the highly aggressive TNBC among young Black females based on distinct molecular subtypes. Ultimately, it is critical to assess both biologic and non-biologic factors to fully understand and address existing health disparities in this population. Through prior and subsequent recruitment of a population-based study of young Black females diagnosed with invasive breast cancer spanning 2009-2016, we: 1) assessed the contribution of biologic and non-biologic factors on BC-DFS observed among young Black females with BC, and 2) investigated molecular features of the subgroup with TNBC. Through this study, consented participants were asked to provide a saliva sample from which DNA was extracted for germline analyses, including germline inherited cancer genetic testing and Infinium Expanded Multi-Ethnic Genotyping Array. Breast cancer tumor specimens were also collected, and tumor RNA was extracted from viable FFPE tumor samples. Tumor RNA analyses included gene expression profiling through NanoString PAM50.Data that will be available through dbGaP for this study include SNP array data and PAM50 data.

  Study phs003466

• Center for Common Disease Genomics [CCDG] - Cardiovascular ATVB: Atherosclerosis Thrombosis and Vascular Biology

  Italian Atherosclerosis Thrombosis and Vascular Biology study is a prospective, nationwide, case-control study involving 125 coronary care units in Italy. The cases were patients who were hospitalised for a first MI before the age of 45 years and underwent coronary angiography. Acute MI was defined as resting chest pain lasting more than 30 minutes, accompanied by persistent electrocardiographic changes, and confirmed by an increase in total creatine kinase or in the MB fraction to more than twice the upper normal limits. The controls were healthy subjects without a history of thromboembolic disease who were unrelated to the patients, but individually matched with them by age, gender and geographical origin. They were enrolled from among the blood donors or staff of the same participating hospitals. Recruitment of cases and controls took place between 1994 and 2007. This site hosts data from ~60 whole exomes.

  Study phs001592

• Combined MEK and BCL-2/XL inhibition is effective in high-grade serous ovarian cancer patient-derived xenograft models and BIM levels are predictive of responsiveness

  Most patients with late stage high-grade serous ovarian cancer (HGSOC) initially respond to chemotherapy but inevitably relapse and develop resistance, highlighting the need for novel therapies to improve patient outcomes. The MEK/ERK pathway is activated in a large subset of HGSOC, thus making it an attractive therapeutic target. Here, we systematically evaluated the extent of MEK/ERK pathway activation and efficacy of pathway inhibition in a large panel of well-annotated HGSOC patient-derived xenograft (PDX) models. The vast majority of models were nonresponsive to the MEK inhibitor cobimetinib (GDC-0973) despite effective pathway inhibition. Proteomic analyses of adaptive responses to GDC-0973 revealed that GDC-0973 upregulated the pro-apoptotic protein BIM, thus priming the cells for apoptosis regulated by BCL2-family proteins. Indeed, combination of both MEK inhibitor and dual BCL-2/XL inhibitor (ABT-263) significantly reduced cell number, increased cell death and displayed synergy in vitro in most models. In vivo, the GDC-0973 and ABT-263 combination was well tolerated and resulted in greater tumor growth inhibition than single agents. Detailed proteomic and correlation analyses identified two subsets of responsive models – those with high BIM at baseline that was increased with MEK inhibition and those with low basal Bim and high pERK levels. Models with low BIM and low pERK were non-responsive. Our findings demonstrate that combined MEK and BCL-2/XL inhibition has therapeutic activity in HGSOC models and provide a mechanistic rationale for clinical evaluation of this drug combination as well as the assessment of the extent to which BIM and/or pERK levels predict drug combination effectiveness in chemoresistant HGSOC.

  Study EGAS00001003427

• Heart Failure Network - Renal Optimization Strategies Evaluation in Acute Heart Failure and Reliable Evaluation of Dyspnea (HFN ROSE-BioLINCC)

  ObjectivesTo test the two independent hypotheses that when compared to placebo, addition of: (1) low dose dopamine; or (2) low dose nesiritide to diuretic therapy will enhance decongestion and preserve renal function in patients with acute heart failure and renal dysfunction.Background A primary treatment goal in acute heart failure is to achieve adequate decongestion while avoiding renal dysfunction and other side effects. Patients with acute heart failure and moderate or severe renal dysfunction are at risk for inadequate decongestion and worsening renal function - both of which are associated with worse outcomes. Renal adjuvant therapies that enhance decongestion and preserve renal function during treatment of acute heart failure are needed. Dopamine is an endogenous catecholamine which, at low doses, may selectively activate dopamine receptors and promote renal vasodilatation. Previous studies have suggested that the addition of low dose dopamine to diuretic therapy enhances decongestion and preserves renal function during diuretic therapy in acute heart failure; however, these studies were small with variable study designs and dopamine doses. B-type natriuretic peptide (BNP) is a cardiac peptide with vasodilating, renin and aldosterone inhibiting, natriuretic and diuretic properties. Nesiritide is human recombinant BNP approved for management of acute heart failure. The recommended dose lowers blood pressure and atrial pressures and produces modest improvement in dyspnea, but does not favorably impact clinical outcomes or renal function, potentially due to its hypotensive effects. Small studies using low dose nesiritide in acute heart failure and cardiac surgery patients have demonstrated favorable effects on urine output and renal function. Therefore, the Renal Optimization Strategies Evaluation (ROSE) trial was initiated to determine the benefits and safety of intravenous administration of low dose nesiritide or low dose dopamine in patients with congestive heart failure and kidney dysfunction. ParticipantsA total of 360 participants were enrolled. Design Participants were enrolled within 24 hours of hospital admission and randomized in a 1:1 ratio to the nesiritide or dopamine strategies. Participants randomized to the dopamine strategy were randomized in a double-blind 2:1 ratio to low dose dopamine (2 &#181;g/kg/min for 72 hours infused via local guideline stipulated vascular access) or placebo. Participants randomized to the nesiritide strategy were randomized in a double-blind 2:1 ratio to low dose nesiritide (0.005 &#956;g/kg/min for 72 hours infused via peripheral intravenous access without initial bolus) or placebo. All participants received open-label, intravenous loop diuretic treatment with a recommended total daily dose equal to 2.5x the total daily oral outpatient furosemide (or equivalent) dose at 7 days prior to admission up to a maximum of 600 mg/day. Participants naive to outpatient loop diuretics received 80 mg/day of intravenous furosemide. One-half of the total daily diuretic dose was administered as a bolus twice daily for at least 24 hours. Use of other medications and diuretic dosing after 24 hours were at the discretion of the clinician. All participants were placed on a 2000 mg sodium diet and 2000 cc fluid restriction. After the primary endpoint assessment at 72 hours, study drug was discontinued and subsequent treatment was at the clinician's discretion. The two co-primary endpoints were the 72-hour cumulative urinary volume as an index of decongestion efficacy and the change in cystatin-C from randomization to 72 hours as a measure of renal function preservation. Conclusions In participants with acute heart failure and renal dysfunction, neither low-dose dopamine nor low-dose nesiritide enhanced decongestion or improved renal function when added to diuretic therapy.

  Study phs003589

• IMMUcan Lung NSCLC2 cohort

  The goal of IMMUcan is to understand how the immune system interacts with tumors and how therapeutic interventions influence this interaction. This cohort includes patients with non-small cell lung cancer who had surgical resection. This is a subcohort of the EORTC SPECTAlung study. Comprehensive profiling data are integrated with longitudinally collected clinical information. Cellular profiling of the same tumor samples was performed using multiplex immunofluorescence imaging, imaging mass cytometry, and H&E staining.

  Study EGAS50000001558

• MutWP1__CRUK_Grand_Challenge__matched_blood_Nanoseq

  The Mutographs project aims to advance our understanding of the causes of cancer through studies of mutational signatures. Led by Mike Stratton, together with Paul Brennan, Ludmil Alexandrov, Allan Balmain, David Phillips and Peter Campbell, this large-scale international research endeavour was awarded a Cancer Research UK Grand Challenge. Different patterns of somatic mutation are generated by the different environmental, lifestyle and genetic factors that cause cancer, many of them are still unknown. Within Mutographs, the International Agency for Research on Cancer is coordinating the recruitment of 5000 individuals with cancer (colorectal, renal, pancreatic, oesophageal adenocarcinoma or oesophageal squamous cancers) across 5 continents to explore whether different mutational signatures explain marked variation in incidence. In brief, through an international network of collaborators around the world, biological materials are collected, along with demographic, histological, clinical and questionnaire data. Whole genome sequences of tumour-germline DNA pairs are generated at the Wellcome Trust Sanger Institute. Non-tumour DNA is also studied for some cancer types. Somatic mutational signatures are subsequently extracted by non-negative matrix factorisation methods and correlated with risk factors data. Through an enhanced understanding of cancer aetiology, Mutographs unprecedented effort is anticipated to outline modifiable risk factors, lead to new approaches to prevent cancer, and provide opportunities to empower early detection, refine high-risk groups and contribute to further therapeutic development.

  Study EGAS00001006774