PDFs RNA-seq and scRNA/TCR-seq data for Pharmacologic inhibition of nonsense-mediated mRNA decay enhances anti-tumour immunity
In the last 10 years, most human omics data has been generated in the context of research consortia while recently there has been an emergence of large cohorts of human data generated by healthcare initiatives. Many countries in Europe now have nascent personalised medicine programmes. Thus, human genomics is shifting from being predominantly research-driven to being funded through healthcare systems. Genetic data generated in a healthcare context is subject to more stringent information governance than research data and nonetheless all data must adhere to national data protections laws. In this context, EGA identified the need for the development of a federated network to enable secure sharing of data whilst enabling genetic data to remain within the jurisdiction in which it was generated. The Federated EGA is designed to support national data management requirements for genomic and clinical data collected from citizens as part of healthcare or biomedical research projects. It includes a secure authorised access mechanism to support research use of these data across Europe and worldwide. We have engaged with over 14 ELIXIR countries to develop the federation model. The EGA federated configuration is composed of Central EGA, Federated EGA nodes and Community EGA nodes: Central EGA offers international submissions and helpdesk support, currently EGA co-managed by EMBL-EBI and CRG, Federated EGA nodes offer EGA services to researchers within their national jurisdiction, Community EGA nodes are individual institutions or initiatives with human genetic data intended to be shared with the research community. Key services available in the Federated EGA structure are: Central EGA Federated EGA node Community EGA nodes Data submission Offers international submissions service Offers submission service in a particular jurisdiction Does not offer an external submissions service Helpdesk support Provides external international helpdesk Provides helpdesk support for submitters in its jurisdiction and for approved users of data managed at its facilities Provides helpdesk support only for approved users of data managed at its facilities Data distribution Manages worldwide distribution for data hosted at Central EGA Manages worldwide distribution for data hosted at Federated EGA node Distribution for data hosted at Community EGA node EMBL-EBI and CRG have prepared a series of documents describing the overall governance and coordination framework. These describe the Federated EGA structure, the rights and responsibilities of the different parties and governing committees, and node operation guidelines. The federation governance proposal is under review by the first countries invited to join as Federated nodes, with further interested countries likely to join in the coming years. The Central EGA team has been working closely with many ELIXIR partners, including ELIXIR Finland, Luxembourg, Germany, Norway, Spain and Sweden.
Background: Use of aspirin and other non-steroidal anti-inflammatory drugs (NSAIDs) has been shown to protect against tetraploidy, aneuploidy, and chromosomal alterations in the metaplastic condition Barrett's esophagus (BE) and to lower the incidence and mortality of esophageal adenocarcinoma (EA). The esophagus is exposed to both intrinsic and extrinsic mutagens resulting from gastric reflux, chronic inflammation and exposure to environmental carcinogens such as those found in cigarettes. Here we test the hypothesis that NSAID use inhibits accumulation of point mutations/indels during somatic genomic evolution in BE. Methods: Whole exome sequences were generated from 82 purified epithelial biopsies and paired blood samples from a cross-sectional study of 41 NSAID users and 41 nonusers matched by sex, age, smoking, and continuous time using or not using NSAIDs. Results: NSAID use reduced overall frequency of point mutations across the spectrum of mutation types, lowered the frequency of mutations even when adjusted for both TP53 mutation and smoking status, and decreased the prevalence of clones with high variant allele frequency. Never smokers who consistently used NSAIDs had fewer point mutations in signature 17, which is commonly found in EA. NSAID users had on average a 50% reduction in functional gene mutations in nine cancer-associated pathways and also had less diversity in pathway mutational burden compared to nonusers. Conclusions: These results indicate NSAID use functions to limit overall mutations on which selection can act and supports a model in which specific mutant cell populations survive or expand better in the absence of NSAIDs. Galipeau PC, et al. Genome Med. 2018 Feb 27;10(1):17. PMID: 29486792.
Recent genome-wide association studies (GWAS) have successfully identified genetic variants that influence diabetes risk in European populations, however most do not have a major impact on diabetes risk in populations of African descent. The African American (AA) population from the Sea Islands of coastal South Carolina and Georgia has high rates of type 2 diabetes, low levels of admixture, and in general, consume a diet rich in saturated fats. We postulate that this unique combination of ancestral and environmental factors results in a more consistent penetrance of diabetes risk alleles, as well as enrichment of risk alleles of African origin. The existing DNA samples and rich phenotypic data from the Sea Island Families Project comprise a unique resource for genetic studies of type 2 diabetes and related metabolic traits such as dyslipidemia. Our central hypothesis is that the increased risk for T2DM in AA compared with European American (EA) is due, in part, to susceptibility alleles of African origin, and that these alleles can be identified using a GWAS. The Specific Aims are to: 1) Identify genetic risk factors for type 2 diabetes utilizing DNA samples and data from the Sea Island Families Project, Reasons for Geographic and Racial Differences in Stroke (REGARDS) Study recruited from SC, GA, NC, and AL; and a GWAS approach; 2) Identify genetic contributors to lipoprotein subclasses in African Americans using the lipoprotein subclass profile (particle size and concentration for multiple subclasses of VLDL, LDL, and HDL) assessed by NMR at LipoScience, Inc., and the GWAS data from Aim 1. The rationale for this project is that identification and validation of novel pathophysiological pathways and informed selection of candidate genes for diabetes risk will inform development of new, targeted prevention and treatment strategies in this underserved, high risk population.
Methylation of anaplastic meningiona samples
The study is composed of two sub-studies. The first study, conducted by NYU Grossman School of Medicine, is a case-control study of 89 cases with gastric intestinal metaplasia (IM) and 89 matched controls who underwent upper gastrointestinal endoscopy at three sites affiliated with NYU Langone Health. Shotgun metagenomic sequencing using oral wash samples from the 89 case-control pairs and antral mucosal brushing samples from 55 case-control pairs were conducted. The other study, conducted by Vanderbilt University Medical Center, is a prospective case-control study on the oral microbiome and gastric cancer risk, utilizing shotgun metagenomic sequencing data of pre-diagnostic buccal samples from 319 Asians, 118 African Americans and 51 European Americans. This study includes data from three population-based studies: the Southern Community Cohort Study (SCCS), the Shanghai Women's Health Study (SWHS), and the Shanghai Men's Health Study (SMHS). The SWHS and SMHS include 74,941 women aged 40-70 years and 61,480 men aged 40-74 years, respectively, who were permanent residents of Shanghai and recruited to the cohorts between 1997 and 2006. The SCCS is an ongoing prospective cohort study, including ~86,000 participants recruited during 2002 and 2009 from 12 Southeastern states. Nearly 67% of study participants are African Americans (AAs) and the remaining are European American (EA) subjects.
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.
Intestinal metaplasia (IM) is a pre-malignant condition of the gastric mucosa associated with increased gastric cancer (GC) risk. We analyzed 1256 gastric samples (1152 IMs) from 692 subjects from a 10-year prospective study. We identified 26 IM driver genes in diverse pathways including chromatin regulation (ARID1A) and intestinal homeostasis (SOX9), largely occurring as subclonal events. Analysis of clonal dynamics between and within subjects, and also longitudinally across time, revealed that IM clones are likely transient but increase in size upon progression to dysplasia, with eventual transmission of genetic events to paired GCs. Single-cell and spatial profiling highlighted changes in tissue ecology and lineage heterogeneity in IM, including an intestinal stem-cell dominant cellular compartment linked to early malignancy. Expanded transcriptome profiling revealed expression-based molecular subtypes of IM, including a body-resident “pseudoantralized” subtype associated with incomplete histology, antral/intestinal cell types, ARID1A mutations, inflammation, and microbial communities normally associated with the healthy oral tract. We demonstrate that combined clinical-genomic models outperform clinical-only models in predicting IMs likely to progress. Our results raise opportunities for GC precision prevention and interception by highlighting strategies for accurately identifying IM patients at high GC risk and a role for microbial dysbiosis in IM progression.
The present series corresponds to 24 whole genome sequencing (12 Tumoral/Non-tumoral pairs). Hepatocellular carcinoma (HCC) accounts for more than 90% of liver cancers, and is a major health problem. It is the 3rd cause of cancer-related mortality. Advances in genomic analyses have formed a comprehensive understanding of different underlying pathobiological layers resulting in hepatocarcinogenesis. Thus, the development of next-generation sequencing technologies has made it possible to generate more comprehensive catalogues of somatic alteration events (single nucleotide substitutions, structural variations, and epigenetic changes) in liver cancer genome than ever before.
A diagnostic non-invasive biomarker test for prostate cancer at an early stage, with high sensitivity and specificity, would improve diagnostic decision making. Extracellular RNAs present in seminal plasma might contain biomarker potential for the accurate detection of clinically significant prostate cancer. So far, the extracellular messenger RNA (mRNA) profile of seminal plasma has not been interrogated for its biomarker potential in the context of prostate cancer. Here, we investigate the mRNA transcriptome in seminal plasma samples obtained from prostate cancer patients (n=25), patients with benign prostate hyperplasia (n=26) and individuals without prostatic disease (n=6). Seminal plasma harbors a complex mRNA repertoire that reflects prostate as its tissue of origin. The endogenous RNA content is higher in the prostate cancer samples compared to the control samples. Prostate cancer antigen 3 (PCA3), a long non-coding RNA with prostate cancer-specific overexpression, and ATP-binding cassette transporter 1 (ABCA1), known to be involved in the prostate cancer pathogenesis, were more abundant in the prostate cancer group. In addition, twelve high confidence fusion transcripts could be detected in prostate cancer samples, including the bona-fide prostate cancer fusion transcript TMPRSS2-ERG. Our findings provide proof-of-principle that the extracellular transcriptome of seminal plasma can reveal information of an underlying prostate cancer.
