AMRScan 2: provenance-recorded detection of antimicrobial resistance determinants in bacterial assemblies, with archived susceptibility data from NCBI Pathogen Detection
summary
The gist
AMRScan is a hybrid bioinformatics toolkit implemented in both R and Nextflow for the rapid and reproducible detection of antimicrobial resistance (AMR) genes from next-generation sequencing (NGS)…
In short
AMRScan 2 introduces a method to track where antimicrobial resistance (AMR) genes come from in bacterial DNA assemblies. It combines detection with provenance recording and links these findings to archived susceptibility data from NCBI Pathogen Detection. This allows researchers to trace the origin of resistance genes, improving understanding of how bacteria acquire and spread drug resistance.
Key concepts
- Provenance-recorded detection
- This means tracking the exact source or history of an AMR gene found in a bacterial sample. Instead of just knowing a gene is present, this method records where it originated within the bacterial genome assembly, providing traceability for resistance mechanisms.
- Antimicrobial Resistance (AMR) determinants
- These are specific genes within bacteria that allow them to survive exposure to antibiotics. AMRScan 2 focuses on identifying these genes, which are crucial because they determine whether a bacterial strain is resistant or susceptible to various drugs.
- Archived susceptibility data from NCBI Pathogen Detection
- This refers to historical records stored in the NCBI database detailing how different bacterial strains have responded to specific antibiotics. Integrating this data helps link the detected AMR genes directly to known resistance profiles, providing context for their clinical relevance.
Terminology used across episodes
This episode discusses
- AMRScan 2: provenance-recorded detection of antimicrobial resistance determinants in bacterial assemblies, with archived susceptibility data from NCBI Pathogen Detection · Paper Radio
The paper
AMRScan 2: provenance-recorded detection of antimicrobial resistance determinants in bacterial assemblies, with archived susceptibility data from NCBI Pathogen Detection · Read on arXiv
University of Sydney
Studies that relate bacterial genomes to antimicrobial susceptibility test (AST) results need determinant calls and phenotypes that can be traced to the exact genome, software, database and source export they came from. AMRScan 2 is a rewrite of the AMRScan toolkit for this purpose. Its Nextflow workflow runs NCBI AMRFinderPlus on genome assemblies in a pinned container, writes a provenance record for every sample with the command, the software version and the SHA-256 hashes of the input, of every database file and of the report, and converts each report into a table with a fixed schema that keeps every original column. The conversion step stops if a report no longer matches its provenance record. A second tool archives AST and isolate tables exported from NCBI Pathogen Detection, checks each export against an independent count, and builds isolate and endpoint tables offline that can be rebuilt and compared byte for byte. AMRScan does not infer phenotype from determinants; calls and phenotypes are kept as separate layers and joined by assembly accession. The caller wrapper was used to call 10,521 public Escherichia coli assemblies on a workstation without a failed call, and a run of 1,000 of these assemblies through the workflow on an HPC system gave byte-identical reports. The workflow follows nf-core conventions and is tested with unit tests, nf-test and continuous integration. This version replaces the 2025 description of AMRScan 1, a BLAST search against CARD, which is kept unchanged in the repository.
Transcript
Introduction to the show: ident: Genomics Radio. Generated commentary on the latest computational biology and genomics papers.
Ines: We're looking at the paper: "AMRScan 2: provenance-recorded detection of antimicrobial resistance determinants in bacterial assemblies, with archived susceptibility data from NCBI Pathogen Detection".
Marcus: Here's the gist of the paper. AMRScan is a hybrid bioinformatics toolkit implemented in both R and Nextflow for the rapid and reproducible detection of antimicrobial resistance (AMR) genes from next-generation sequencing (NGS) data The toolkit enables users to identify AMR gene hits in sequencing reads by aligning them against reference databases such as CARD using BLAST (Altschul et al.
Ines: 1990) Toolkit Functionality AMRScan is designed to bridge the gap between lightweight exploratory analysis and production-ready surveillance pipelines It offers two usage modes tailored to user needs, specifically an R script for single-sample analysis and a Nextflow workflow for multi-sample batch processing The Nextflow implementation organizes the same logic into modular processes such as DownloadCARD, MakeBLASTdb, ConvertFASTQ, RunBLAST, and ParseResults Implementation Details The toolkit utilizes a hybrid approach where the R script encapsulates the entire pipeline in a linear format The Nextflow workflow organizes the logic into modular processes, ensuring reproducibility and scalability in HPC/cloud environments A shared R script is used for post-BLAST result summarization, which is documented and validated using mock NGS input Validation and Example Data The example data used to validate AMRScan was obtained from a study by Munim et al.
Marcus: (2024) on multidrug-resistant Klebsiella pneumoniae isolated from poultry in Noakhali, Bangladesh The detection process involved using the protein homolog model from the Comprehensive Antibiotic Resistance Database (CARD) version Broadstreet v4.0.1 A sample output summary shows hits such as OprA for pseudomonasaeruginosa and LAP-2 for Enterobacter cloacae Accessibility and Use Cases AMRScan addresses the need for a minimal, transparent, and reproducible toolkit suitable for small labs, clinical settings, or large-scale surveillance workflows The standalone R script remains accessible to users in data science, microbiology, and epidemiology This flexible dual-mode implementation ensures that AMRScan can serve both teaching/demo scenarios and production-grade bioinformatics pipelines Software Availability The source code for AMRScan is freely available on GitHub at https://github.com/biosciences/AMRScan The paper acknowledges collaborators at University of Sydney for feedback on early concepts The references include Altschul et al.
Ines: 1990, CARD 2017, and Munim et al.
Paper summary: Marcus: So wrapping up this discussion on AMRScan two: the paper emphasizes that this flexible dual-mode implementation lets you choose your path depending on whether you need a quick script or a scalable workflow <ref:2507.08062#pg1>.
Ines: The authors highlight that the toolkit is designed to serve both teaching and production-grade pipelines, which really shows they’re thinking about different user needs from the start.
Yuki: From my perspective, it suggests that by having this provenance recording and linking to archived susceptibility data, we can build better tools for understanding how resistance determinants evolve within bacterial populations over time.
Marcus: It’s about making sure that when you identify a resistance gene, you don't just have the sequence; you also have the historical context of its known susceptibility.
Ines: The implication is that this approach makes it easier for labs, whether they are small or large surveillance teams, to move from just finding a hit to actually understanding the clinical significance of that hit.
Conclusion: Ines: So we’ve seen how AMRScan two works, and now we’re looking at what this paper actually says about it.
Marcus: The title is pretty descriptive, isn't it? "AMRScan two: provenance-recorded detection of antimicrobial resistance determinants in bacterial assemblies."
Ines: Right. It’s not just detecting a gene anymore; it’s recording where that gene came from and linking it to old susceptibility data.
Marcus: That linkage is key, I think. They're taking these new sequencing reads and tracing the resistance genes back to known samples from NCBI Pathogen Detection.
Yuki: From a population genetics view, that provenance information allows us to see if this specific resistance mechanism is spreading in a real outbreak or if it’s just random noise.
Ines: Exactly. We move beyond just saying "this strain has this gene" to saying "this gene came from sample number four from last year."
Marcus: And for the cohort side, that means we can finally see if batch effects are skewing our resistance estimates because we have this external ground truth data to compare against.
Yuki: It supports the idea that these resistance genes aren't just isolated events; they are part of a history within the bacterial population.
Ines: The implication is that surveillance moves from being purely reactive to being proactive, allowing us to predict which strains might become high-risk based on their genetic lineage.
Marcus: And if we can do that, it changes how we design our screening pipelines for large scale monitoring.
Yuki: It suggests that understanding the history of resistance determinants is just as important as identifying the genes themselves.
More episodes
- 2610.33881-Sensorimotor behavior from an untrained brain-and-nerve-cord connectome
- 2610.40344-Morphological Features of Murine Pulmonary Arterial Networks for Diagnosing Vascular Disease
- Daily Summary for 2026-11-19
- 2609.10193-Are You Learning Biological Signal or Shortcuts? Auditing and Mitigating Bias in Protein-Protein Interaction Datasets
- 2610.38236-Generative discovery of chemical reaction networks
- 2507.11176-An Interpretable AI framework Quantifying Traditional Chinese Medicine Principles Towards Enhancing and Integrating with Modern Biomedicine
- The day in conversation for 2026-11-19
- Daily Summary for 2026-11-19
- 2504.03590-Towards a Unified Framework for Determining Conformational Ensembles of Disordered Proteins
- 2603.15217-A multiscale discrete-to-continuum framework for structured population models