Identification of virulence factors in <i>Vibrio cholerae</i> isolated from Iraq during the 2007–2009 outbreak
Bibliographic record
Abstract
Thousands of people were infected with Vibrio cholerae during the outbreak in Iraq in 2007-2009. Vibrio cholerae was shown to be variable in its content of virulence determinants and in its antibiotic sensitivity. This study was designed to isolate and characterize clinical and environmental V. cholerae isolates and to determine antibiotic sensitivity, enzyme and toxin production, and the presence of virulence genes. Eighty clinical and five environmental bacterial isolates were collected and diagnosed by subjecting them to microscopic, biochemical, serological, and molecular analysis. The results revealed that 55% of clinical isolates belonged to the Inaba serotype, 32.5% to the Ogawa serotypes, and 12.5% to the Non-O1 serotype. All environmental V. cholerae isolates belonged to the Non-O1 serotype. All environmental isolates were sensitive to all examined antimicrobial agents, while all clinical isolates showed a high sensitivity (100%) to ampicillin, gentamicin, cephalothin, tetracycline, erythromycin, and ciprofloxacin, and a high resistance (97.5%) to co-trimoxazole, nalidixic acid, and chloramphenicol. It was found that all V. cholerae (O1) isolates were resistant to the Vibrio static O129 and all Non-O1 V. cholerae isolates were sensitive to the Vibrio static O129. All clinical and environmental isolates produced hemolysin (100%) and lecithinase (100%), while they showed various production rates of protease (90% of clinical and 60% of environmental) and lipase (50% of clinical and 20% of environmental). The ompW gene was amplified in all the clinical and environmental V. cholerae isolates, but not in other related and nonrelated bacteria. Multiplex PCR analysis showed that the toxR gene was amplified in all clinical and environmental isolates, while ctxA, ctxB, tcpA genes were amplified only in clinical (O1) isolates. This study indicates the differences in the production of some enzymes and toxins and in the content of virulence genes between clinical and environmental isolates in Iraq during the outbreak (2007-2009).
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| 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.001 | 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".