Management of Rhabdomyolysis in a Patient Treated with Clozapine: A Case Report and Clinical Recommendations
Bibliographic record
Abstract
Clozapine has a unique efficacy in treatment-resistant schizophrenia. Its use is, however, associated with potential adverse events. Among those, clozapine induced rhabdomyolysis can compromise clozapine treatment. Recommendations surrounding the management of this rare adverse event are limited. We present a case of clozapine-induced rhabdomyolysis. A 20-year-old Caucasian male diagnosed with resistant schizophrenia developed, after a 5-month total exposition and a significant response to treatment, a marked creatine kinase (CK) elevation and important myalgia in the weeks following an increment from 175 to 200 mg of the daily dose of clozapine. This event also coincided with weight training as reported by the patient. The patient was hospitalized, and the clozapine was stopped following the diagnosis of rhabdomyolysis (CK 45,564 U/L). The cause of rhabdomyolysis was thoroughly investigated, and clozapine was held accountable for most. Clozapine cessation led to a severe psychotic relapse. Clozapine rechallenge while strictly monitoring CK was then performed allowing a significant clinical response. Clozapine was pursued despite two other episodes of mild CK elevations observed following weight training. Rhabdomyolysis comes as a rare adverse event of clozapine and its mechanism is poorly understood. Evidence on clozapine rechallenge following this adverse event is lacking and the innocuity of such practice is unknown. The unique aspect of our case report is that a shared decision with the medical team, patient and family led to a proactive clozapine rechallenge. More research is needed to provide robust guidelines and evidenced based approaches for clinicians in such a clinical dilemma.
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.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.007 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
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".