MétaCan
Menu
Back to cohort
Record W1985482581 · doi:10.1007/s13181-012-0256-9

A Case of Sodium Chlorite Toxicity Managed with Concurrent Renal Replacement Therapy and Red Cell Exchange

2012· article· en· W1985482581 on OpenAlexaff
Adam Romanovsky, Dennis Djogovic, Dat Chin

Bibliographic record

VenueJournal of Medical Toxicology · 2012
Typearticle
Languageen
FieldMedicine
TopicOccupational exposure and asthma
Canadian institutionsUniversity of Alberta HospitalUniversity of Alberta
Fundersnot available
KeywordsMedicineSodium chloriteAcute kidney injuryHemofiltrationRenal replacement therapyAnesthesiaSurgeryHemodialysisIntensive care medicineInternal medicineChemistry

Abstract

fetched live from OpenAlex

INTRODUCTION: Sodium chlorite is a powerful oxidizing agent with multiple commercial applications. We report the presentation and management of a single case of human toxicity of sodium chlorite. CASE REPORT: A 65-year-old man presented to hospital after accidentally ingesting a small amount of a sodium chlorite solution. His principal manifestations were mild methemoglobinemia, severe oxidative hemolysis, disseminated intravascular coagulation, and anuric acute kidney injury. He was managed with intermittent hemodialysis, followed by continuous venovenous hemofiltration for management of acute kidney injury and in an effort to remove free plasma chlorite. Concurrently, he underwent two red cell exchanges, as well as a plasma exchange, to reduce the burden of red cells affected by chlorite. These interventions resulted in the cessation of hemolysis with stabilization of serum hemoglobin and platelets. The patient survived and subsequently recovered normal renal function. DISCUSSION: This is only the second case of sodium chlorite intoxication reported in the medical literature and the first to report the use of renal replacement therapy in combination with red cell exchange in its management.

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 imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.004
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Case report · Consensus signal: Case report
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.008
Threshold uncertainty score0.015

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.004
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0030.002
Science and technology studies0.0040.002
Scholarly communication0.0020.002
Open science0.0020.002
Research integrity0.0080.005
Insufficient payload (model declined to judge)0.0020.001

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.

Opus teacher head0.038
GPT teacher head0.315
Teacher spread0.278 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designCase report
Domainnot available
GenreEmpirical

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".

Quick stats

Citations25
Published2012
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Medical ToxicologySame topicOccupational exposure and asthmaFrench-language works237,207