Inconsistent PCR detection of Shiga toxin-producing Escherichia coli: Insights from whole genome sequence analyses
Bibliographic record
Abstract
Shiga toxin-producing Escherichia coli (STEC) have been linked to food-borne disease outbreaks. As PCR is routinely used to screen foods for STEC, it is important that factors leading to inconsistent detection of STEC by PCR are understood. This study used whole genome sequencing (WGS) to investigate causes of inconsistent PCR detection of stx1, stx2, and serogroup-specific genes. Fifty strains isolated from Alberta feedlot cattle from three different studies were selected with inconsistent or consistent detection of stx and serogroup by PCR. All isolates were initially classified as STEC by PCR. Sequencing was performed using Illumina MiSeq® with sample library by Nextera XT. Virtual PCRs were performed using Geneious and bacteriophage content was determined using PHASTER. Sequencing coverage ranged from 47 to 102x, averaging 74x, with sequences deposited in the NCBI database. Eleven strains were confirmed by WGS as STEC having complete stxA and stxB subunits. However, truncated stx fragments occurred in twenty-two other isolates, some having multiple stx fragments in the genome. Isolates with complete stx by WGS had consistent stx1 and stx2 detection by PCR, although one also having a stx2 fragment had inconsistent stx2 PCR. For all STEC and 18/39 non-STEC, serogroups determined by PCR agreed with those determined by WGS. An additional three WGS serotypes were inconclusive and two isolates were Citrobacter spp. Results demonstrate that stx fragments associated with stx-carrying bacteriophages in the E. coli genome may contribute to inconsistent detection of stx1 and stx2 by PCR. Fourteen isolates had integrated stx bacteriophage but lacked complete or fragmentary stx possibly due to partial bacteriophage excision after sub-cultivation or other unclear mechanisms. The majority of STEC isolates (7/11) did not have identifiable bacteriophage DNA in the contig(s) where stx was located, likely increasing the stability of stx in the bacterial genome and its detection by PCR.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".