A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_sessionpeh6s55qupr6urtalgfkd4jk8nl00ldo): Failed to open stream: No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 177

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Failed to read session data: user (path: /var/lib/php/sessions)

Filename: Session/Session.php

Line Number: 137

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

GDH and toxin immunoassay for the diagnosis of Clostridioides (Clostridium) difficile infection is not a 'one size fit all' screening test. | LitMetric

AI Article Synopsis

Article Abstract

Diagnosing Clostridioides (Clostridium) difficile infection is challenged by lack of a clear gold standard. We sought to determine if the two-step algorithm (screening GDH and toxin lateral flow assay followed by tcdB PCR) would have adequate clinical performance at a tertiary care center. Of 486 patients, 310 (63.8%) were immunocompromised. Of 150 PCR-positive specimens, 52 (34.7%) were toxin-positive and 126 (84.0%) were GDH positive. Positive GDH or toxin results corresponded to lower PCR cycle threshold values (P < 0.01). PCR-positive patients had more frequently documented antibiotic usage (78.4% vs 66.9%, P = 0.05) and diarrhea (91.0% vs. 79.4%, P < 0.01) and less frequent alternate etiologies of diarrhea (27.3% vs. 41.1%, P = 0.004) or laxative use (24.6% vs 36.1%, P = 0.02). Toxin positivity was associated with antibiotic use (P < 0.01), but not with neutropenia, diarrhea, malignancy, or chemotherapy (P > 0.05). The application of the 2-step algorithm should be thoroughly evaluated in immunocompromised patient populations before implementation.

Download full-text PDF

Source
http://dx.doi.org/10.1016/j.diagmicrobio.2018.12.010DOI Listing

Publication Analysis

Top Keywords

gdh toxin
12
clostridioides clostridium
8
clostridium difficile
8
difficile infection
8
gdh
4
toxin immunoassay
4
immunoassay diagnosis
4
diagnosis clostridioides
4
infection 'one
4
'one size
4

Similar Publications

[Evaluation of Quick Chaser CD GDH/TOX, a Rapid Diagnostic Kit for Simultaneous Detection of Antigen and Toxin A/B, in Fecal Specimens].

Rinsho Biseibutshu Jinsoku Shindan Kenkyukai Shi

December 2024

Department of Clinical Laboratory, Medical Kouhoukai Takagi Hospital. Department of Medical Laboratory Science, Graduate school of Health and Welfare Sciences, International University of Health and Welfare Graduate School.

For infections, highly sensitive rapid diagnostic test kits are necessary for prompt diagnose and infection control. In this study, we evaluated "Quick Chaser CD GDH/TOX" (evaluation kit), a rapid diagnostic kit for , using 65 clinical stool specimens, comparing with GE test immunochromato-CD GDH/TOX "Nissui" (GE test) and TECHLAB QUIK CHEK COMPLETE (QUIK CHEK). The results of the evaluation kit showed a high concordance rate; 100% the positive concordance rate (31/31) and 97.

View Article and Find Full Text PDF

A quantitative PCR to detect non-toxigenic .

Microbiol Spectr

December 2024

Department of Pharmacy Practice and Translational Research, University of Houston College of Pharmacy, Houston, Texas, USA.

species lacking toxin genes (non-toxigenic or NTCD) may confer protection against CDI. However, current diagnostic tests detect either toxin proteins or toxin genes and cannot detect NTCD. This study developed a molecular testing method that uniquely identified NTCD and assessed its prevalence in a clinical cohort.

View Article and Find Full Text PDF

Current guidelines recommend a two-step algorithm rather than relying solely on a single test for diagnosing infection. This algorithm starts with enzyme immunoassay (EIA) for detecting glutamate dehydrogenase (GDH) and toxins A/B, followed by nucleic acid amplification test (NAAT) for GDH-positive but toxin-negative cases. This study compared the performance of three commercial NAATs: the STANDARD M10 , Xpert , and BD MAX Cdiff assays, utilized as confirmatory testing of the two-step algorithm.

View Article and Find Full Text PDF

[Clostridioides difficile infections: Update and therapeutic guidelines].

Geriatr Psychol Neuropsychiatr Vieil

October 2024

CHU de Grenoble-Alpes, Président du Collège National des Enseignants de Gériatrie, France.

Article Synopsis
  • * Complications from CDI, such as pseudomembranous colitis and toxic megacolon, require prompt diagnosis through clinical evaluation, microbiological tests, and potentially imaging studies.
  • * Treatment typically involves halting harmful antibiotics and using specific antimicrobial therapies, with options like fidaxomicin, oral vancomycin, and fecal microbiota transplantation for recurrent cases.
View Article and Find Full Text PDF

Biofilm formation and toxin production are some of the virulence factors of Clostridioides difficile (C. difficile), which causes hospital-acquired C. difficile infection (HA-CDI).

View Article and Find Full Text PDF

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!