American College of Rheumatology White Paper on Antimalarial Cardiac Toxicity
Bibliographic record
Abstract
Hydroxychloroquine (HCQ) and chloroquine (CQ) are well-established medications used in treating systemic lupus erythematosus and rheumatoid arthritis, as well as skin conditions such as cutaneous lupus erythematosus. In rare cases, arrhythmias and conduction system abnormalities, as well as cardiomyopathy, have been reported in association with HCQ/CQ use. Recently, however, the corrected QT interval (QTc)-prolonging potential of these medications, and risk of torsade de pointes (TdP) in particular, have been highlighted in the setting of their experimental use for COVID-19 infection. This report was undertaken to summarize the current understanding of HCQ/CQ cardiac toxicity, describe QTc prolongation and TdP risks, and discuss areas of priority for future research. A working group of experts across rheumatology, cardiology, and dermatology performed a nonsystematic literature review and offered a consensus-based expert opinion. Current data clearly indicate that HCQ and CQ are invaluable medications in the management of rheumatic and dermatologic diseases, but they are associated with QTc prolongation by directly affecting cardiac repolarization. Prescribing clinicians should be cognizant of this small effect, especially in patients taking additional medications that prolong the QTc interval. Long-term use of HCQ/CQ may lead to a cardiomyopathy associated with arrhythmias and heart failure. Risk and benefit assessment should be considered prior to initiation of any medication, and both initial and ongoing risk-benefit assessments are important with regard to prescription of HCQ/CQ. While cardiac toxicity related to HCQ/CQ treatment of rheumatic diseases is rarely reported, it can be fatal. Awareness of the potential adverse cardiac effects of HCQ and CQ can increase the safe use of these medications. There is a clear need for additional research to allow better understanding of the cardiovascular risk and safety profile of these therapies used in the management of rheumatic and cutaneous diseases.
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.001 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.005 | 0.005 |
| Insufficient payload (model declined to judge) | 0.086 | 0.037 |
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".