What is Dr. Zubair Khalid's research focus?

Dr. Zubair Khalid specializes in molecular virology, mRNA vaccine development, and computational biology, with a focus on avian pathogens like IBDV and Avian Reovirus.

Where is Dr. Zubair Khalid currently working?

Dr. Zubair Khalid is a Postdoctoral Research Associate at the University of Maryland (UMD), specifically within the Department of Animal and Avian Sciences.

Amplicon Sequencing for Viral Surveillance: Design and Quality Considerations

Amplicon sequencing uses multiplexed primer pools to amplify specific genomic regions from viral samples, producing targeted genome sequences for surveillance. This guide is for laboratory scientists, bioinformaticians, and public health teams who design, evaluate, or interpret amplicon-based workflows for monitoring viral outbreaks and evolution. The approach is especially useful when viral loads are low or when rapid, cost-effective whole genome coverage is needed from large sample sets. Understanding primer scheme performance, controls, coverage gaps, consensus rules, and transparent metadata is essential before deploying these methods in a surveillance setting. The NCBI Bookshelf provides foundational technical references for sequencing and quality control.

Amplicon sequencing has become a workhorse for genomic surveillance of RNA viruses like SARS CoV 2, influenza, and emerging pathogens such as Usutu virus. A recent evaluation of a highly sensitive amplicon workflow for Usutu virus showed that careful primer design and quality filtering can recover near complete genomes even from low titer samples source: A highly sensitive amplicon sequencing workflow for genomic surveillance of Usutu virus. That study highlights why primer scheme performance must be validated before field deployment. This guide covers the core considerations that separate reliable surveillance from data that cannot support public health decisions.

At a Glance

Aspect	Key Consideration
Primer scheme design	Number of amplicons, amplicon overlap, melting temperature, GC content, and tolerance to known viral variants
Multiplex pools	Balanced pool sizes, avoidance of primer dimer, and even amplification across targets
Positive controls	Synthetic or characterized viral RNA of known sequence to confirm amplification and analysis pipeline
Negative controls	No template controls (NTC) and extraction blanks to detect contamination
Coverage gaps	Strategies include using overlapping primers, filling gaps with alternative pools, or Sanger finishing
Consensus calling	Depth threshold (e.g. 10x or 20x), frequency cutoff for minority variants, and handling of ambiguous bases
Metadata requirements	Sample origin, collection date, primer scheme version, instrument, and quality metrics for public repositories

Decision Criteria for Using Amplicon Sequencing

Before adopting an amplicon approach for viral surveillance, evaluate these factors.

Viral genome size and diversity. Amplicon sequencing works well for viruses with genomes under 30 kb and known conserved regions for primer binding. For highly diverse viruses like African swine fever virus (ASFV) that circulate in multiple genotypes, primer schemes must be validated against circulating strains. A study on ASFV from ticks in Tanzania used amplicon sequencing to characterize viral genomes and highlighted the need for primer sets that cover diverse lineages source: Detection and molecular characterization of African swine fever virus recovered from Ornithodoros ticks of the Serengeti Ecosystem, Tanzania.

Sample type and viral load. Amplicon methods are more tolerant of degraded nucleic acids than metagenomic approaches because short overlapping amplicons can amplify fragmented templates. However, samples with very low viral load (Ct > 30 or equivalent) may produce incomplete coverage even with optimized primer pools.

Throughput and turnaround time. Amplicon library preparation is typically faster and cheaper than whole genome shotgun sequencing, making it ideal for real time surveillance. The trade off is that the approach is limited to known targets and may miss novel recombinant or divergent strains.

Availability of validated primer schemes. Many public resources provide primer schemes for common viruses. Before designing custom primers, check repositories like EMBL-EBI Training for protocol databases and community standards.

Primer Scheme Performance

Primer scheme performance is the foundation of reliable amplicon sequencing. Key metrics include amplification efficiency, uniformity across amplicons, and tolerance to sequence variation at primer binding sites.

Amplicon length and overlap. Typical amplicon lengths range from 200 to 1000 base pairs. Shorter amplicons are more robust with degraded RNA but require more primers to cover the genome. Overlap between adjacent amplicons (typically 50 to 150 bp) is necessary to allow stitching of contiguous sequences and to rescue coverage if one amplicon fails.

Balancing multiplex pools. Most schemes divide primers into two pools to reduce primer interactions and improve amplification uniformity. Each pool should generate similar depth across its targets. Uneven amplification leads to coverage gaps or excessive sequencing of overrepresented amplicons.

Validating with known variants. A primer scheme designed against a reference may fail when new mutations appear at primer binding sites. In the study of a previously unrecognized measles virus cluster in Burundi, whole genome amplicon sequencing detected clusters that would have been missed with subgenomic targets, but required updating primers periodically as sequences evolved source: Whole genome sequencing reveals a previously unrecognized measles virus cluster in Burundi. Regular monitoring of primer binding site conservation is essential.

In silico evaluation. Tools like Primer3 or custom scripts can check primers against known variant databases. The Galaxy Training Network offers tutorials on primer design and evaluation for viral amplicon panels.

Controls Every Workflow Needs

Controls are not optional in surveillance, they are the only way to distinguish real signals from contamination or technical artifacts.

Positive controls. Use a characterized viral RNA or synthetic control of known sequence. This control should go through the entire workflow from extraction to consensus calling. It confirms that the assay can detect the target and that the bioinformatics pipeline produces correct consensus sequences. For example, the Usutu virus study used in vitro transcribed RNA as a positive control to benchmark sensitivity.

Negative controls. Include a no template control (NTC) at the PCR step and an extraction blank. These controls should show no amplification or minimal background. Any reads mapping to the target in negative controls indicate contamination and may invalidate nearby samples.

Mock community or spike ins. For quantitative surveillance, adding a known concentration of an exogenous RNA (such as a synthetic spike in) allows estimation of viral load from sequencing read counts.

Handling Coverage Gaps

Coverage gaps are inevitable in amplicon sequencing, especially when primer binding sites mutate or when amplification fails in GC rich regions.

Strategies for gap filling. (1) Use overlapping primer schemes so that a single failed amplicon can be covered by its neighbors. (2) Prepare a third primer pool targeting known problematic regions. (3) For critical gaps, use Sanger sequencing of a separate PCR product. (4) Report gaps transparently in the final consensus sequence using IUPAC codes or indicating missing regions.

Dynamic primer balancing. Some workflows adjust primer concentrations after a pilot sequencing run to balance coverage. This iterative approach improves uniformity but adds turnaround time.

Assessing gap impact on downstream analysis. A missing region may not affect clade assignment if the region is not phylogenetically informative. However, gaps in key genes (e.g., the spike protein in SARS CoV 2) can hinder variant classification. The Bioconductor community provides R packages like ShortRead and Rsamtools to analyze coverage depth and identify gaps systematically.

Consensus Rules and Quality Thresholds

Generating a consensus genome from amplicon data requires careful rule setting.

Depth thresholds. The minimum depth for a high confidence base call is typically 10x to 20x. Lower depth calls may be reliable if all reads agree, but they carry higher uncertainty. Record the threshold used.

Minority variant frequency. Amplicon sequencing often uses a majority rule consensus (e.g., call the base if it appears in >50% of reads above threshold). For surveillance, a lower frequency cutoff (e.g., 5%) may be used to detect emerging variants, but this increases false positives. Document the cutoff.

Handling mixed infections. In settings where coinfection or recombination may occur, the consensus sequence may not represent a single viral strain. Tools for haplotype reconstruction can help, but for routine surveillance, reporting ambiguous bases or separate consensus sequences for dominant variants is more transparent.

Validation against a reference. After generating the consensus, compare it to a trusted reference or positive control to confirm no systematic errors. The systematic evaluation of single nucleotide polymorphism based genotyping methods for varicella zoster virus surveillance shows how careful rule setting and validation improve accuracy in molecular epidemiology source: Systematic Evaluation and Application of Single-Nucleotide Polymorphism Based Genotyping Methods in Varicella Zoster Virus Molecular Epidemiology Surveillance, China, 2017 2026.

Transparent Metadata Requirements

Public health surveillance data is only useful if it includes complete metadata.

Sample metadata. Collection date, geographic location, host species, sample type, and clinical context. Without collection date, temporal trends cannot be analyzed.

Technical metadata. Primer scheme version, protocol, sequencing platform, read length, depth of coverage, and quality scores. Many public repositories like the NCBI Sequence Read Archive require submission of raw reads with metadata. Incomplete metadata can lead to exclusion from downstream analyses.

Consensus genome metadata. Include a column for “completeness” or “percent coverage” to flag genomes with large gaps. Also record the consensus calling rules (depth threshold, frequency cutoff). When analyzing canine parvovirus antigenic variants, metadata on vaccination status and outcome helped link genomic variants with clinical severity, demonstrating the value of comprehensive data source: Canine parvovirus type 2 antigenic variants and in hospital mortality in central Spain.

Practical Workflow Implementation

A reproducible workflow for amplicon sequencing surveillance should include these steps.

Primer scheme design or selection. Download a validated scheme from a public resource or design custom primers. Evaluate in silico against known variant sequences.
Sample preparation. Extract nucleic acid using a method compatible with downstream PCR. Include positive and negative controls.
Multiplex PCR. Set up two primer pools. Optimize annealing temperature and cycle number to minimize primer dimer and non specific amplification.
Library preparation. Pool amplicons from both primer pools, attach sequencing adapters, and barcode samples.
Sequencing. Run on an appropriate platform (Illumina, Ion Torrent, or Nanopore). Target depth should allow at least 100x mean coverage across the genome.
Bioinformatics. Trim adapter sequences and primer sequences. Align reads to a reference genome using a mapper tolerant to mismatches (e.g., BWA, minimap2). Call variants and generate consensus using a tool like iVar, LoFreq, or custom scripts. Assess coverage depth per amplicon.
Quality control. Check negative controls for contamination. Flag any sample with mean depth below the threshold or with coverage gaps exceeding 10% of the genome. Compare positive control to expected sequence.
Metadata compilation. Record all sample and technical metadata in a standardized spreadsheet or database.
Submission. Upload raw reads to SRA and consensus sequences to GenBank or GISAID with complete metadata.

Common Mistakes

Primer dimer contamination. When primers hybridize to each other, they produce short fragments that consume sequencing reads. Solutions include rebalancing pool concentrations, using touchdown PCR, and performing a bead cleanup between PCR and library preparation.

Ignoring primer binding site mutations. Using the same primer scheme for months without checking for emerging variants leads to dropout. Regularly update primers based on circulating sequences.

Insufficient depth for low coverage regions. Some amplicons may amplify poorly. Without additional gap filling, the final consensus will have missing bases, which can be mistaken for deletions or misidentified as variants.

Using a single consensus rule for all samples. A fixed 50% frequency cutoff may miss true minority variants in early outbreak detection. Conversely, using a 5% cutoff without validation can produce false positives from sequencing errors.

Skipping contamination checks. If positive control samples show contamination or negative controls have reads mapping to the target, the entire batch may be unreliable. Always assess controls before analyzing sample data.

Limits and Uncertainty

Amplicon sequencing cannot detect viruses that are highly divergent from the primer targets. Novel emerging strains or recombinant viruses may not amplify. The method is also limited by the length of individual amplicons, which constrains the ability to phase variants across long distances. For some applications, such as detecting low frequency introduction events, additional orthogonal methods like serology or CRISPR based detection may be needed. The CRISPR Cas toolkit for mosquito borne virus surveillance offers complementary approaches for screening before sequencing, but does not replace whole genome characterization source: The CRISPR Cas toolkit for mosquito borne virus surveillance: detection, tracing, and discovery. Uncertainty around coverage gaps and consensus quality should always be reported so that downstream users can assess the reliability of each genome.

Frequently Asked Questions

How many amplicons are typically needed for a 10 kb viral genome? For a 10 kb genome with 400 bp amplicons and 50 bp overlap, approximately 30 amplicons per pool are needed. Actual numbers depend on primer design constraints and genome complexity.

Can I use amplicon sequencing for virus discovery? No, it is not designed for discovery of novel viruses because it relies on known primer binding sites. Metagenomic sequencing is more appropriate for identifying unknown pathogens.

What is the minimum viral load required for successful amplicon sequencing? It depends on the sensitivity of the assay and the number of cycles. Many protocols work well with Ct values up to 30 or 32, but viral loads should be validated for each scheme.

How do I decide between one pool and two pool designs? Two pool designs reduce primer interactions and improve uniformity. One pool designs are simpler but risk more dropout and primer dimer. For viruses with high diversity, two pools are recommended.

Zubair Khalid