SaLTy: a novelStaphylococcus aureusLineage Typer

preprint OA: closed
📄 Open PDF View at publisher

Abstract

Staphylococcus aureus asymptomatically colonises 30% of humans and in 2017 was associated with 20,000 deaths in the USA alone. Dividing S. aureus into smaller sub-groups can reveal the emergence of distinct sub-populations with varying potential to cause infections. Despite multiple molecular typing methods categorising such sub-groups, they do not take full advantage of S. aureus WGS when describing the fundamental population structure of the species. In this study, we developed Staphylococcus aureus Lineage Typing (SaLTy), which rapidly divides the species into 61 phylogenetically congruent lineages. Alleles of three core genes were identified that uniquely define the 61 lineages and were used for SaLTy typing. SaLTy was validated on 5,000 genomes and 99.12% (4,956/5,000) of isolates were assigned the correct lineage. We compared SaLTy lineages to previously calculated clonal complexes (CCs) from BIGSdb (n=21,173). SALTy improves on CCs by grouping isolates congruently with phylogenetic structure. SaLTy lineages were further used to describe the carriage of Staphylococcal chromosomal cassette containing mecA ( SCCmec ) which is carried by methicillin-resistant S. aureus (MRSA). Most lineages had isolates lacking SCC mec and the four largest lineages varied in SCC mec over time. Classifying isolates into SaLTy lineages, which were further SCC mec typed, allowed SaLTy to describe high-level MRSA epidemiology We provide SALTy as a simple typing method that defines phylogenetic lineages ( https://github.com/LanLab/SaLTy ). SALTy is highly accurate and can quickly analyse large amounts of S. aureus WGS. SALTy will aid the characterisation of S. aureus populations and the ongoing surveillance of sub-groups that threaten human health.

My notes (saved in your browser only)

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. The paper's references may be in our DB but unresolved to ``paper_id`` (resolution happens at ingest when the cited DOI matches a row we already have). Run the cross-source citation reconcile pass to retry.

Source provenance

europepmc
last seen: 2026-05-19T01:45:01.086888+00:00