Choosing the Right Bioinformatics Tools for Pathogen Genomics Surveillance

By Dr. Zubair Khalid, DVM, MS, PhD · 2026-08-27

Quick Answer

• Select tools by matching their algorithmic design to your surveillance question: read mapping and variant calling for SNP typing, whole-genome alignment for recombination detection, and phylogenomic placement for cluster tracking.
• Validate every pipeline component against authenticated reference strains and known outbreak datasets before deployment, because tool outputs drive public health decisions.
• No single tool covers all surveillance needs, and results depend heavily on input quality, reference choice, and parameter settings that require expert review.

At a Glance

Understanding the Surveillance Workflow

Pathogen genomics surveillance transforms raw sequencing data into actionable public health information. The workflow begins with DNA extraction and sequencing, moves through quality control and bioinformatic analysis, and ends with interpretation and reporting. Each stage requires distinct tools and expertise, and the choices made at every step influence the reliability of the final result.

The core facility manager faces a crowded field of software options. Many tools perform similar functions but differ in their underlying algorithms, input requirements, and output formats. Selecting the wrong tool for a specific surveillance question wastes computational resources and can produce misleading conclusions. This article provides a structured framework for evaluating and selecting bioinformatics tools across the major stages of bacterial pathogen genomics surveillance.

The global context for this work is urgent. Antimicrobial resistance threatens the effectiveness of treatments for bacterial infections worldwide, and genomic surveillance provides a powerful approach for tracking resistant strains and understanding their spread. The World Health Organization identifies antimicrobial resistance as a global health threat requiring coordinated surveillance and stewardship efforts. Genomic tools support these efforts by enabling rapid identification of resistance determinants and transmission clusters.

Core Principles of Tool Selection

Define the Surveillance Question First

Before evaluating any software, the facility manager must articulate the specific question the surveillance program must answer. Different questions demand different analytical approaches. A program tracking the emergence of resistance in a hospital setting requires different tools than one investigating a foodborne outbreak across multiple states.

The question determines the required resolution. Whole-genome sequencing provides the highest resolution for distinguishing closely related isolates, but the analytical approach determines whether that resolution is achieved. For example, comparing isolates from a suspected point-source outbreak requires tools that can identify single nucleotide polymorphisms (SNPs) among nearly identical genomes. Tracking the global spread of a lineage over years requires tools that can handle substantial genomic diversity and recombination.

The question also determines the required turnaround time. Outbreak investigations demand rapid analysis, sometimes within hours of sequencing completion. Long-term surveillance programs can tolerate longer analysis times in exchange for more thorough phylogenetic inference. The facility manager must match tool selection to these operational requirements.

Understand the Biology of the Target Organism

Bacterial species differ dramatically in their population structure and recombination rates. Some species, such as Mycobacterium tuberculosis, have highly clonal populations with minimal horizontal gene transfer. Others, such as Streptococcus pneumoniae and Escherichia coli, frequently exchange genetic material through recombination and mobile genetic elements.

These biological differences directly affect tool selection. Clonal organisms can be analyzed reliably with read mapping and variant calling approaches that assume a single reference genome represents the population. Recombining organisms require tools that detect and account for recombinant regions, otherwise phylogenetic trees will reflect the movement of genetic material instead of the ancestry of the organisms.

The facility manager must understand the biology of the target organism before selecting tools. This understanding comes from the scientific literature, from consultation with subject matter experts, and from preliminary analysis of local isolates. The American Society for Microbiology provides educational resources and professional networks that support laboratory professionals in developing this expertise.

Match Tool Capabilities to Laboratory Resources

Bioinformatics tools vary widely in their computational requirements. Some tools run on a standard laptop in minutes, while others require high-performance computing clusters and days of processing time. The facility manager must honestly assess available computational resources before committing to a tool.

Personnel expertise is equally important. Some tools require command-line proficiency and understanding of Unix systems. Others provide graphical interfaces that reduce the barrier to entry. The facility manager must consider whether existing staff can operate and troubleshoot the selected tools or whether additional training or hiring is necessary.

Sustainability matters for long-term surveillance programs. Tools that require ongoing manual intervention are difficult to maintain. Tools with active developer communities and regular updates are more likely to remain functional and compatible with evolving sequencing technologies. The facility manager should evaluate the maintenance status of candidate tools before adoption.

Read Mapping and Variant Calling Tools

Snippy for Rapid SNP Detection

Snippy is a widely used tool for detecting SNPs between bacterial isolates and a reference genome. It performs read mapping, variant calling, and produces a core genome alignment that can be used for phylogenetic analysis. The tool is designed for speed and reproducibility, making it suitable for outbreak investigations where rapid results are needed.

The primary strength of Snippy lies in its simplicity and speed. The tool automates the entire variant calling pipeline, from read mapping through variant filtering, and produces a clean output that can be directly used for phylogenetic inference. This automation reduces the potential for user error and makes the tool accessible to laboratories with limited bioinformatics expertise.

The main limitation of Snippy is reference bias. The tool maps reads to a single reference genome, and variants are defined relative to that reference. If the reference is distantly related to the isolates under investigation, the analysis may miss variants in regions that are absent from the reference or that have diverged substantially. This limitation is acceptable for closely related outbreak isolates but problematic for diverse collections.

Snippy also does not account for recombination. Variants in recombinant regions are treated the same as variants inherited vertically, which can distort phylogenetic inference. For recombining species, the facility manager should use Snippy in combination with recombination detection tools or select an alternative approach.

Lyve-SET for Outbreak Investigations

Lyve-SET is another read mapping and variant calling pipeline designed specifically for bacterial outbreak investigations. The tool emphasizes reproducibility and provides a structured workflow that includes quality control, read mapping, variant calling, and phylogenetic tree construction.

The key advantage of Lyve-SET is its focus on producing results that can be compared across laboratories. The tool uses standardized parameters and provides clear documentation of the analysis steps, which supports the transparency required for public health investigations. This standardization is valuable when multiple laboratories contribute data to a single investigation.

Lyve-SET includes a masking step that removes recombinant regions from the analysis, addressing one of the main limitations of simpler variant calling approaches. This feature makes the tool more suitable for recombining species than Snippy, although it adds computational time and complexity.

The facility manager should consider Lyve-SET when the surveillance program requires reproducible, comparable results across multiple sites or when the target organism is known to recombine. The tool requires more computational resources than Snippy but provides more robust results for outbreak investigations.

Evaluating Variant Calling Quality

Regardless of the specific tool selected, the facility manager must implement quality control measures to ensure reliable variant calls. Read depth, mapping quality, and base quality all influence the accuracy of variant detection. Low coverage regions may produce false negative calls, while mapping errors can produce false positives.

The facility manager should establish minimum quality thresholds for variant calling and document these thresholds in standard operating procedures. These thresholds should be based on the specific requirements of the surveillance program and validated using control strains with known genome sequences.

Validation is essential before deploying any variant calling pipeline. The facility manager should test the pipeline using authenticated reference strains from a culture collection such as the American Type Culture Collection. These strains provide a known ground truth against which the pipeline can be evaluated. The validation should include isolates with known variants, known resistance determinants, and known phylogenetic relationships.

Recombination Detection and Phylogenetic Inference

Gubbins for Recombination Masking

Gubbins is a tool that identifies recombinant regions in bacterial genomes and produces a phylogenetic tree based on the remaining vertically inherited variation. The tool uses an iterative approach that alternates between phylogenetic inference and recombination detection, refining the analysis until convergence.

The primary strength of Gubbins is its ability to produce more accurate phylogenetic trees for recombining species. By masking recombinant regions, the tool ensures that the tree reflects the ancestry of the organisms instead of the movement of genetic material. This accuracy is essential for understanding transmission patterns and evolutionary relationships.

Gubbins requires a set of closely related isolates to work effectively. The tool identifies recombination by comparing the phylogenetic signal across the genome, and this comparison requires sufficient similarity among the isolates. If the isolates are too diverse, the tool may not be able to distinguish recombination from vertical inheritance.

The computational requirements of Gubbins are substantial. The tool performs multiple rounds of phylogenetic inference, each of which can take hours for large datasets. The facility manager must allocate sufficient computational resources and plan for extended analysis times when using Gubbins.

IQ-TREE for Maximum Likelihood Phylogenetics

IQ-TREE is a maximum likelihood phylogenetic inference tool that is widely used in bacterial genomics. The tool supports a range of evolutionary models, including models that account for rate heterogeneity across sites, and provides robust statistical support through ultrafast bootstrap approximation.

The primary strength of IQ-TREE is its flexibility and accuracy. The tool can handle large alignments, supports multiple substitution models, and provides a range of options for assessing phylogenetic support. This flexibility makes IQ-TREE suitable for a wide range of surveillance applications, from outbreak investigations to long-term evolutionary studies.

IQ-TREE requires an input alignment, which must be generated by a separate tool such as Snippy or Gubbins. The facility manager must ensure that the alignment is appropriate for phylogenetic inference, including removing recombinant regions and filtering poorly aligned positions.

The tool provides several options for model selection, and the facility manager should use the built-in model selection functionality to identify the best-fitting model for each dataset. Using an inappropriate model can produce misleading phylogenetic trees, particularly for datasets with substantial rate heterogeneity.

Nextstrain for Real-Time Visualization

Nextstrain provides a platform for real-time phylogenetic analysis and visualization. The tool combines phylogenetic inference with interactive visualization, allowing researchers to explore the relationships among isolates and track the emergence and spread of lineages over time.

The primary strength of Nextstrain is its accessibility. The web-based interface allows stakeholders without bioinformatics expertise to explore phylogenetic trees and understand the relationships among isolates. This accessibility is valuable for communicating results to public health officials, clinicians, and policymakers.

Nextstrain requires curated metadata to be effective. The tool displays isolates in the context of their collection date, location, and other epidemiological information, and this information must be accurate and complete. The facility manager must invest in metadata curation to realize the full value of Nextstrain.

The tool is best suited for ongoing surveillance programs instead of acute outbreak investigations. The analysis pipeline requires careful setup and the visualization is most useful when data are added over time, allowing the emergence of new lineages to be tracked as they appear.

Cluster Detection and Typing Methods

Core Genome MLST for Standardized Typing

Core genome multilocus sequence typing (cgMLST) provides a standardized approach for typing bacterial isolates based on the alleles present at a defined set of core genes. The approach produces a typing scheme that is portable across laboratories and comparable over time.

The primary strength of cgMLST is standardization. Because the scheme is defined by a fixed set of genes, results from different laboratories can be directly compared. This comparability is essential for national and international surveillance programs that aggregate data from multiple sites.

cgMLST provides higher resolution than traditional MLST, which uses only seven housekeeping genes. The core genome approach examines hundreds or thousands of genes, allowing closely related isolates to be distinguished. This resolution is valuable for outbreak investigations where traditional MLST cannot distinguish among isolates.

The main limitation of cgMLST is the requirement for a defined scheme. The facility manager must use a scheme that has been validated for the target organism and must ensure that the scheme is maintained as new isolates are characterized. Schemes are available through platforms such as EnteroBase and PubMLST, which provide curated allele definitions and isolate databases.

Resistance Gene Detection Tools

Resistance gene detection tools identify antimicrobial resistance determinants in bacterial genomes by comparing the genome sequence to databases of known resistance genes. These tools provide rapid screening for resistance mechanisms without requiring phenotypic testing.

The primary strength of resistance gene detection is speed. The tools can screen a genome for hundreds of resistance determinants in minutes, providing results much faster than phenotypic susceptibility testing. This speed is valuable for surveillance programs that need to track the emergence of resistance in real time.

The main limitation of resistance gene detection is that the presence of a resistance gene does not always correlate with phenotypic resistance. Gene expression, promoter mutations, and other factors influence whether a resistance gene produces a resistant phenotype. The facility manager must confirm resistance gene findings with phenotypic testing when clinical decisions depend on the result.

The Clinical and Laboratory Standards Institute provides standards for antimicrobial susceptibility testing that define the phenotypic methods used to confirm resistance. The facility manager should integrate genotypic and phenotypic approaches to provide a complete picture of antimicrobial resistance in the surveillance population.

Evaluating Cluster Detection Approaches

The choice of cluster detection approach depends on the surveillance question and the biology of the target organism. SNP-based approaches provide the highest resolution but require careful reference selection and recombination masking. cgMLST provides standardized results but may not distinguish among highly clonal isolates.

The facility manager should evaluate candidate approaches using a validation dataset with known epidemiological relationships. The validation should include isolates from known outbreaks, isolates from unrelated cases, and isolates with known resistance profiles. The evaluation should assess whether the approach correctly identifies the known clusters and distinguishes them from unrelated isolates.

The facility manager should also consider the scalability of the approach. Some approaches work well for small datasets but become computationally prohibitive for large collections. The evaluation should include testing with datasets of the size expected in routine surveillance.

Practical Implementation Steps

Step 1: Inventory Available Resources

The facility manager should begin by documenting the available computational resources, personnel expertise, and sequencing platforms. This inventory provides the foundation for tool selection and identifies constraints that must be addressed.

The inventory should include the number and specifications of available computing nodes, the amount of storage available for raw data and analysis outputs, and the network bandwidth available for data transfer. The inventory should also document the bioinformatics expertise of the laboratory staff, including their proficiency with command-line tools, scripting, and statistical analysis.

The inventory should be reviewed regularly as resources change. New sequencing platforms may produce different data formats or require different computational resources. Staff turnover may change the available expertise. The facility manager should update the inventory at least annually and after any significant change in laboratory operations.

Step 2: Define the Surveillance Objectives

The facility manager should work with stakeholders to define the specific objectives of the surveillance program. These objectives should be specific, measurable, and aligned with the public health priorities of the organization.

The objectives should specify the target organisms, the geographic scope of surveillance, the expected volume of samples, and the required turnaround time. The objectives should also specify the types of results required, such as lineage identification, cluster detection, or resistance profiling.

The objectives should be documented and reviewed regularly. As the surveillance program evolves, the objectives may change, and the tool selection should be revisited to ensure alignment.

Step 3: Evaluate Candidate Tools

The facility manager should identify candidate tools for each stage of the surveillance workflow and evaluate them against the defined objectives and available resources. The evaluation should include testing with representative datasets and documentation of performance.

The evaluation should assess accuracy, speed, ease of use, and maintenance status. The evaluation should also assess the compatibility of the tool with existing laboratory workflows and the availability of training and support.

The evaluation should be documented in a structured format that allows comparison across tools. The documentation should include the version of the tool tested, the test dataset used, the computational resources required, and the results obtained.

Step 4: Validate the Selected Pipeline

Before deploying a surveillance pipeline, the facility manager must validate the complete workflow using authenticated reference strains and known outbreak datasets. The validation should demonstrate that the pipeline produces accurate and reproducible results.

The validation should include testing with reference strains from a culture collection such as the American Type Culture Collection. These strains provide a known ground truth for evaluating the accuracy of variant calling, typing, and resistance detection.

The validation should also include testing with datasets from previously characterized outbreaks. These datasets provide a realistic test of the pipeline performance under operational conditions and allow the facility manager to assess the turnaround time and reliability of the workflow.

Step 5: Document Standard Operating Procedures

The facility manager should document the validated pipeline in standard operating procedures that provide step-by-step instructions for running the analysis. The procedures should include quality control checkpoints, troubleshooting guidance, and criteria for escalating problems.

The standard operating procedures should specify the exact commands and parameters used in the pipeline, the expected outputs at each stage, and the criteria for accepting or rejecting results. The procedures should also specify the records that must be maintained for each analysis.

The standard operating procedures should be reviewed and updated regularly. Changes to the pipeline, updates to software versions, or changes in the surveillance objectives should trigger a review of the procedures.

Records and Measurements

Maintaining Analysis Records

The facility manager must maintain comprehensive records of all surveillance analyses. These records provide the evidence base for public health decisions and support the reproducibility of the surveillance program.

The records should include the raw sequencing data, the analysis parameters used, the software versions, and the results obtained. The records should also include the quality control metrics for each sample and the decisions made during the analysis.

The records should be stored in a structured format that allows retrieval and review. The facility manager should implement a naming convention that allows samples to be traced through the analysis workflow and should maintain a database that links sample identifiers to analysis results.

Tracking Quality Control Metrics

The facility manager should track quality control metrics for each analysis to identify problems early and ensure the reliability of results. The metrics should include read depth, mapping rate, variant call quality, and assembly statistics.

The quality control metrics should be reviewed regularly to identify trends that may indicate problems with the sequencing platform, the analysis pipeline, or the sample preparation. The facility manager should establish thresholds for acceptable quality and should investigate any samples that fall below these thresholds.

The quality control metrics should be reported alongside the analysis results. This reporting provides transparency about the reliability of the results and supports the interpretation of the findings by stakeholders.

Measuring Pipeline Performance

The facility manager should measure the performance of the surveillance pipeline to identify bottlenecks and opportunities for improvement. The measurements should include turnaround time, computational resource usage, and error rates.

The turnaround time should be measured from the receipt of sequencing data to the delivery of the final report. The measurement should include the time required for quality control, analysis, and interpretation. The facility manager should track turnaround time over time to identify trends and address delays.

The computational resource usage should be measured to ensure that the pipeline operates within available capacity. The measurement should include CPU time, memory usage, and storage requirements. The facility manager should use these measurements to plan for capacity upgrades and to identify analyses that require excessive resources.

Common Failure Patterns

Reference Bias and Misleading Variant Calls

A common failure in variant calling pipelines is reference bias, where the choice of reference genome influences the variants detected. This bias occurs when the reference is distantly related to the isolates under investigation, causing reads from divergent regions to map poorly or not at all.

The facility manager should evaluate the reference genome used in the pipeline and ensure that it is appropriate for the isolates under investigation. The evaluation should include assessing the phylogenetic distance between the reference and the isolates and testing the pipeline with alternative references.

The facility manager should also consider using a reference-free approach, such as assembly-based analysis, when the target organism is diverse or when no suitable reference is available. These approaches avoid reference bias but require different analytical tools and expertise.

Recombination Confounding Phylogenetic Inference

Another common failure is the confounding of phylogenetic inference by recombination. When recombinant regions are included in the analysis, the resulting tree may reflect the movement of genetic material instead of the ancestry of the organisms.

The facility manager should use recombination detection tools for species known to recombine. The analysis should include a recombination masking step, and the resulting tree should be compared with trees generated without masking to assess the impact of recombination.

The facility manager should also be aware that recombination can produce false clusters in cluster detection analyses. Isolates that share recombinant regions may appear closely related even when they are not epidemiologically linked.

Metadata Errors and Misleading Interpretations

Metadata errors are a common source of misleading interpretations in genomic surveillance. Incorrect collection dates, locations, or sample identifiers can lead to incorrect conclusions about transmission patterns and cluster relationships.

The facility manager should implement quality control measures for metadata, including validation against source records and cross-checking with laboratory records. The facility manager should also establish procedures for correcting metadata errors and for documenting the corrections.

The facility manager should recognize that metadata quality is as important as sequence quality for surveillance. A well-analyzed genome with incorrect metadata can produce misleading conclusions that undermine the surveillance program.

Safety and Regulatory Context

Biosafety Considerations for Genomic Surveillance

Genomic surveillance involves working with pathogenic bacteria, and the facility manager must ensure that all laboratory work is conducted safely. The Biosafety in Microbiological and Biomedical Laboratories provides guidance for risk assessment, containment, and decontamination in laboratories working with infectious agents.

The facility manager should conduct a risk assessment for the organisms under surveillance and implement appropriate biosafety measures. The assessment should consider the pathogenicity of the organisms, the routes of transmission, and the laboratory procedures used.

The facility manager should ensure that all personnel are trained in biosafety procedures and that the laboratory facilities meet the containment requirements for the organisms under investigation. The biosafety measures should be reviewed regularly and updated as new information becomes available.

Quality Assurance and Laboratory Standards

The facility manager should implement quality assurance measures that ensure the reliability of the surveillance results. These measures should include the use of authenticated reference strains, the validation of analytical methods, and the participation in proficiency testing programs.

The American Society for Microbiology provides professional education and laboratory practice resources that support quality assurance in microbiology laboratories. The facility manager should use these resources to stay current with best practices and to support the professional development of laboratory staff.

The facility manager should also be aware of the regulatory requirements that apply to the surveillance program. These requirements may include laboratory accreditation, data reporting, and quality control standards. The facility manager should ensure that the surveillance program complies with all applicable requirements.

Antimicrobial Resistance Surveillance Context

Antimicrobial resistance surveillance is a global priority, and genomic tools play an increasingly important role in tracking resistant strains. The World Health Organization provides context for the global threat of antimicrobial resistance and the need for coordinated surveillance and stewardship efforts.

The facility manager should understand how the genomic surveillance program contributes to the broader antimicrobial resistance surveillance efforts. The program should produce data that can be aggregated with data from other laboratories and used to inform public health policy.

The facility manager should also recognize the limitations of genomic surveillance for antimicrobial resistance. Genomic data identify resistance determinants but do not replace phenotypic susceptibility testing for clinical decision-making. The facility manager should ensure that the surveillance program integrates genomic and phenotypic approaches.

Professional Escalation Criteria

When to Escalate Technical Problems

The facility manager should establish criteria for escalating technical problems that cannot be resolved within the laboratory. These criteria should include problems with the analysis pipeline, unexpected results, and computational failures.

Technical problems should be escalated when they affect the reliability of the results or the ability to meet the surveillance objectives. The escalation should include documentation of the problem, the steps taken to resolve it, and the impact on the surveillance program.

The facility manager should maintain relationships with software developers and bioinformatics support services to facilitate the resolution of technical problems. The facility manager should also participate in professional networks where technical problems can be discussed and solutions shared.

When to Escalate Public Health Concerns

The facility manager should establish criteria for escalating public health concerns identified through genomic surveillance. These concerns include the detection of novel resistance mechanisms, the identification of transmission clusters, and the detection of organisms with epidemic potential.

Public health concerns should be escalated to the appropriate public health authorities in accordance with local requirements. The escalation should include the genomic data, the epidemiological context, and the interpretation of the findings.

The facility manager should recognize that genomic surveillance data can have significant public health implications and should ensure that the data are interpreted and communicated appropriately. The facility manager should work with epidemiologists and public health officials to ensure that the findings are used effectively.

When to Escalate Quality Concerns

The facility manager should establish criteria for escalating quality concerns that affect the reliability of the surveillance results. These concerns include contamination, sample mix-ups, and systematic errors in the analysis pipeline.

Quality concerns should be escalated when they affect the validity of the results or the integrity of the surveillance program. The escalation should include documentation of the concern, the investigation conducted, and the corrective actions taken.

The facility manager should implement procedures for investigating quality concerns and for preventing their recurrence. The procedures should include root cause analysis, corrective action planning, and verification of the effectiveness of the corrective actions.

Frequently Asked Questions

What is the difference between read mapping and assembly-based approaches for bacterial genomics?

Read mapping approaches align sequencing reads to a reference genome and identify variants relative to that reference. Assembly-based approaches reconstruct the genome sequence without a reference and then analyze the assembled contigs. Read mapping is faster and more sensitive for detecting variants in closely related isolates, while assembly-based approaches avoid reference bias and can detect novel genetic content. The choice depends on the surveillance question and the diversity of the target organism.

How do I choose between SNP-based and cgMLST approaches for cluster detection?

SNP-based approaches provide the highest resolution for distinguishing closely related isolates and are well suited for outbreak investigations. cgMLST approaches provide standardized results that are comparable across laboratories and are well suited for long-term surveillance programs. The choice depends on whether the priority is maximum resolution or cross-laboratory comparability. Some surveillance programs use both approaches, with cgMLST for initial screening and SNP analysis for detailed investigation of identified clusters.

Why does my phylogenetic tree show unexpected relationships among isolates?

Unexpected phylogenetic relationships can result from recombination, which moves genetic material between isolates and can make distantly related isolates appear closely related. The relationships can also result from errors in the analysis, including reference bias, poor quality alignments, or inappropriate evolutionary models. The facility manager should use recombination detection tools, review the quality of the input alignment, and evaluate the model selection to identify the cause of unexpected relationships.

How should I validate a new bioinformatics pipeline before deployment?

Validation should include testing with authenticated reference strains with known genome sequences and with datasets from previously characterized outbreaks. The validation should assess the accuracy of variant calling, typing, and resistance detection, as well as the reproducibility of the results. The validation should also assess the turnaround time and computational requirements of the pipeline to ensure that it meets operational needs.

What quality control metrics should I track for genomic surveillance?

The facility manager should track read depth, mapping rate, variant call quality, and assembly statistics for each sample. The facility manager should also track metadata quality, including the completeness and accuracy of collection dates, locations, and sample identifiers. These metrics should be reviewed regularly to identify trends and to ensure the reliability of the surveillance results.

How do genomic resistance data relate to phenotypic susceptibility testing?

Genomic data identify resistance determinants, including resistance genes and mutations associated with resistance. Phenotypic susceptibility testing measures the actual susceptibility of the organism to antimicrobial agents. The presence of a resistance gene does not always correlate with phenotypic resistance, and phenotypic resistance can occur through mechanisms that are not detected by genomic analysis. Genomic and phenotypic approaches are complementary and should be used together for antimicrobial resistance surveillance.

What biosafety considerations apply to genomic surveillance of bacterial pathogens?

Genomic surveillance involves working with pathogenic bacteria, and all laboratory work should be conducted in accordance with biosafety guidelines. The facility manager should conduct a risk assessment for the target organisms and implement appropriate containment measures. The Biosafety in Microbiological and Biomedical Laboratories provides guidance for risk assessment, containment, and decontamination. All personnel should be trained in biosafety procedures and the facilities should meet the containment requirements for the organisms under investigation.

How should I document the analysis pipeline for reproducibility?

The analysis pipeline should be documented in standard operating procedures that specify the exact commands, parameters, and software versions used. The documentation should include the quality control checkpoints, the expected outputs at each stage, and the criteria for accepting or rejecting results. The documentation should also include the records that must be maintained for each analysis, including the raw data, the analysis parameters, and the results obtained.

Using the Evidence

Related Bacteriology Guides

• Tuberculosis in Wildlife: Mycobacterium bovis Surveillance and Diagnostic Tools
• Avian Influenza in Australia: Epidemiology and Surveillance
• Avian Influenza in Wales: Surveillance and Control
• Swine Erysipelas in Pigs: Pathogen, Symptoms, and Control
• Avian Influenza: Global Surveillance and Pandemic Preparedness

References and Further Reading

• Biosafety in Microbiological and Biomedical Laboratories. CDC and NIH.
• Microbiology Resources. American Society for Microbiology.
• Antimicrobial Resistance. World Health Organization.
• Bacteriological Analytical Manual. U.S. Food and Drug Administration.
• Antimicrobial Susceptibility Testing. Clinical and Laboratory Standards Institute.
• Culture Collections. American Type Culture Collection.
• NCBI Pathogen Detection. National Center for Biotechnology Information.
• Comparison of three bioinformatics tools in the detection of ASD candidate variants from whole exome sequencing data.. Scientific reports, 2023.
• Typing methods based on whole genome sequencing data.. One health outlook, 2020.
• Real-time plasmid transmission detection pipeline.. Microbiology spectrum, 2024.
• Typhi Mykrobe: fast and accurate lineage identification and antimicrobial resistance genotyping directly from sequence reads for the typhoid fever agent Salmonella Typhi.. Genome medicine, 2025.

This article is educational and does not replace validated laboratory procedures, clinical diagnosis, institutional biosafety review, or public-health guidance.