InferAMP, a python web app for copy number inference from discrete gene-level amplification signals noted in clinical tumor profiling reports

Introduction

Focal somatic gene copy number changes are a widespread event in tumor evolution¹. Although these regions of amplification may be large, encompassing many hundreds of genes, typically only one or a small number of genes within the amplified regions are involved in driving tumor growth. Identification of the key driver genes within recurrent amplicons has led to the approval of some therapies that have changed clinical practice (e.g. anti-ERBB2 agents²); however, targeting other amplified genes such as FGFR family members^3,4, EGFR⁵ or KIT⁶ has frequently proved disappointing. Nevertheless, even some of the more negative trials include occasional strong responses, indicating that sub-populations of patients with amplification of these oncogenes may experience clinical benefit if they can be identified.

With the goal of individualizing treatment for cancer patients, next-generation sequencing from tumor specimens is becoming widely adopted⁷. In addition to somatic point mutations, several of these assays report copy number changes in assayed genes. Reports for physicians typically present a list of amplified genes without providing a genomic context, leaving physicians and molecular tumor boards to hypothesize which of the listed genes might be driver genes suitable for therapeutic targeting. Given the poor response rates that have often been observed in clinical studies with amplified genes (compared to targeting genes activated by point mutation or fusion), physicians are often appropriately cautious about deciding whether a reported amplified gene may be actionable. Thus, many patients are spared receiving ineffective therapies, but a subgroup of patients who may experience clinical benefit do not get that opportunity.

Here we provide an easy-to-use web tool for analyzing clinical genomics reports of amplified genes. It determines (1) the likely size of amplified genomic regions, (2) which reported genes are co-amplified and (3) which other cancer-relevant genes that were not evaluated in the assay may also be co-amplified in the specimen.

The primary goals are to allow healthcare professionals to determine whether the amplification region surrounding a particular oncogene is relatively small and lacking in other likely candidate cancer drivers (which may indicate increased likelihood that the analyzed gene is a driver) from larger amplicons with additional candidate driver genes (which would suggest a reduced probability that the reported gene is a driver). The approach was developed to analyze the widely used Foundation One test (329 genes) provided by Foundation Medicine but, by simply editing the target gene list, it can be generalized to tests from other vendors which report copy number variation throughout the genome.

Methods

Implementation

InferAMP is written in Python 2.7 with Flask and implemented as a web service running on the Google App Engine (http://inferamp.org). Additional supplied requirements are (1) the coordinates of genes in the human genome, ‘coordinates.txt’ (hg38, UCSC genome browser), (2) The gene list from the assay of interest, ‘foundationone.txt’ and (3) a file listing genes recurrently altered in cancer from COSMIC⁸ (retrieved 5/3/2018), ‘cosmic.txt’.

An html page with a single query window allows the user to enter a comma-delimited list of genes reported as being amplified. The entry is passed to the script and parsed into individual gene names. An error check is performed to confirm that all entered gene names correspond to gene names in the genome used. The entered genes are considered to be amplified, while the other genes in the assay are considered to be not amplified.

A simplified schema of how the algorithm works is presented in Figure 1, which depicts a chromosomal region containing 30 genes. Seven cancer-relevant genes are present, five of which are evaluated by the genomic assay (Figure 1A). In this test example, three genes were reported to be amplified (Figure 1B). Running the algorithm identifies these amplified genes (8, 13, 20) as well as the nearby assayed genes that are not reported amplified (4, 27). The algorithm considers all genes located between genes reported as amplified to also be amplified (Figure 1C, red shaded region). Because not every gene is assayed, precisely delineating the boundaries of an amplicon is not possible. To address this, the algorithm determines the nearest non-amplified gene at each end of the amplicon and infers that the genes located up to, but not including that gene may be possibly amplified (Figure 1D). The script then returns an html report page listing the entered genes, the amplicons into which they fall (in many cases, several discrete genes will be consolidated into a single amplicon), and also the other cancer-relevant genes within these regions that may be co-amplified with the reported genes. All genes reported include hyperlinks to that gene’s page on COSMIC.

Figure 1. Schematic representation of amplicon boundary inference approach.

(A). Schematic diagram of a model genomic region with 30 numbered genes, which include a total of 7 cancer-relevant genes. (B) Input scenario for algorithm: a clinical genomics report noting amplification of three genes in this region. (C) Copy number inference for genes in regions bounded by reported amplified genes. (D) Copy number inference for genes surrounding regions bounded by reported amplified genes.

Use cases

Three use cases taken from genomic reports of patients at our clinic are presented:

Discussion

We have described a straightforward tool to provide additional genomic context to aid interpretation of amplifications in somatic cancer sequencing reports. Use of this tool may aid decision-making by healthcare professionals about therapeutic options.

The method relies on the accuracy with which test vendors report gene amplification calls. In testing, we identified a small number of cases in which two amplicons were inferred in very close proximity (e.g. Use case 3), which raises the possibility that the assayed gene between the two regions is erroneously not called as amplified. In cases with two or more closely co-located amplicons, users should consider that there is a strong possibility of a regional amplification encompassing both predicted amplicons. Future assays with larger number of genes or more sensitive amplification calling algorithms will likely permit more accurate refining of the boundaries of individual amplicons.

Because the coverage across the genome is somewhat sparse, refining the amplicon boundaries is more challenging than with a more high-density approach like SNP arrays. The primary purpose is to list genes that are potentially co-amplified with a gene identified by a test vendor as possibly actionable in order to allow healthcare professionals to gain further insight into the likelihood that the listed gene is truly the driver gene in that amplicon. Accordingly, we do not distinguish in the report between genes that are likely co-amplified (red genes, Figure 1) from the boundary region genes which are possibly co-amplified (green genes, Figure 1). In any case in which a healthcare professional might consider targeting a non-assayed gene predicted by this algorithm to be amplified (e.g. LIFR¹¹ in Use case 2 and Use case 3), further clinical testing to directly confirm gene amplification would be warranted.

Data availability

All data underlying the results are available as part of the article and no additional source data are required.

Software availability

Software available at: http://inferamp.org.

Source code available from: https://github.com/paraickenny/inferAMP.

Archived source code at time of publication: http://doi.org/10.5281/zenodo.3249201¹².

License: MIT License.