Clostridium difficile isolated from faecal samples in patients with ulcerative colitis
Bibliographic record
Abstract
BACKGROUND: Ulcerative colitis (UC) is an inflammatory bowel disease (IBD) that is widely identified worldwide. This study aimed to investigate the phenotypic characterization and molecular typing of Clostridium difficile isolates among patients with UC at an inflammatory bowel disease clinic in Iran. METHODS: In this cross-sectional study, conducted from April 2015 to December 2015, 85 UC patients were assessed for C.difficile infection (CDI). C. difficile isolates were characterized based on their toxin profile and antimicrobial resistance pattern. Multi-locus sequence typing analysis (MLST) and PCR ribotyping were performed to define the genetic relationships between different lineages of toxigenic strains. RESULTS: The prevalence of C. difficile isolates was 31.8% (27/85) in patients, of those 15 patients (17.6%) had CDI. Three different sequence types (STs) identified based on MLST among the toxigenic isolates, that is ST54 (33.3%), ST2 (53.3%), and ST37 (13.6%). C. difficile strains were divided into four different PCR-ribotypes (012, 014, 017 and IR1). The most common ribotype was 014 accounting for 48.3% (7/15) of all strains. The strains isolated during the first episode and recurrence of CDI usually belonged to PCR ribotype 014 (ST2). A high rate of CDI recurrence (14.1%, 12/85) experienced in UC patients. Colonization of the gastrointestinal tract with non-toxigenic C. difficile strains was frequent among patients with mild disease. All C. difficile isolates were susceptible to metronidazole, and vancomycin, 86 and 67% of isolates were resistant to clindamycin and erythromycin respectively. There was no correlation between the toxin type and antibiotic resistance (p > 0.05). CONCLUSION: Overall CDI is rather prevalent in UC patients. All patients with CDI experienced moderate to severe disease and exposed to different antimicrobial and anti-inflammatory agents. Close monitoring and appropriate management including early detection and fast treatment of CDI will improve UC outcomes.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 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.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".