Clozapine-Related Myocarditis and Rechallenge
Bibliographic record
Abstract
PURPOSE/BACKGROUND: That clozapine is the only agent with an indication for treatment-resistant schizophrenia presents real challenges if clozapine-related myocarditis (CIM) occurs. Clinicians have chosen to rechallenge with a second trial of clozapine in the face of CIM. However, there is very limited literature of this topic. METHODS/PROCEDURES: Three cases who underwent clozapine rechallenge after CIM are reviewed and discussed in the context of existing literature and current recommendations. FINDINGS/RESULTS: We present 3 young male patients with schizophrenia and schizoaffective disorder who developed CIM during a first clozapine trial, stopped treatment, and subsequently underwent a second clozapine trial. In all cases, the rechallenge was discontinued owing to suspected CIM. A review of the literature includes reports of both successful and unsuccessful clozapine rechallenges after CIM and suggests certain risk factors. Clozapine rechallenge after CIM may be undertaken, as now occurs on occasion with agranulocytosis, although rates of success may be lower. Any such undertaking calls for education, careful monitoring, cautious titration, and a multidisciplinary approach. The balance of risk versus benefits must be considered, and strategies may include a drug holiday, more frequent monitoring upon reinitiation, and slower titration. IMPLICATIONS/CONCLUSIONS: Pressure to undertake a rechallenge reflects clozapine's unique role in treatment-resistant schizophrenia and absence of other comparable options. However, it is not without risk, and more research is needed to understand those at increased risk, as well as established strategies that diminish this.
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.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".