Trimethoprim-sulfamethoxazole induced hyperkalaemia in elderly patients receiving spironolactone: nested case-control study
Bibliographic record
Abstract
OBJECTIVES: To characterise the risk of admission to hospital for hyperkalaemia in elderly patients treated with trimethoprim-sulfamethoxazole in combination with spironolactone. DESIGN: Population based nested case-control study. SETTING: Ontario, Canada, from 1 April 1992 to 1 March 2010. PARTICIPANTS: Cases were residents of Ontario aged 66 years or above receiving chronic treatment with spironolactone and admitted to hospital with hyperkalaemia within 14 days of receiving a prescription for either trimethoprim-sulfamethoxazole, amoxicillin, norfloxacin, or nitrofurantoin. Up to four controls for each case were identified from the same cohort, matched on age, sex, and presence or absence of chronic kidney disease and diabetes, and required to have received one of the study antibiotics within 14 days before the case's index date. MAIN OUTCOME MEASURES: Odds ratio for association between admission to hospital with hyperkalaemia and receipt of a study antibiotic in the preceding 14 days, adjusted for conditions and drugs that may influence risk of hyperkalaemia. RESULTS: During the 18 year study period, 6903 admissions for hyperkalaemia were identified, 306 of which occurred within 14 days of antibiotic use. Of these, 248 (81%) cases were matched to 783 controls. 10.8% (17,859/165,754) of spironolactone users received at least one prescription for trimethoprim-sulfamethoxazole. Compared with amoxicillin, prescription of trimethoprim-sulfamethoxazole was associated with a marked increase in the risk of admission to hospital for hyperkalaemia (adjusted odds ratio 12.4, 95% confidence interval 7.1 to 21.6). The population attributable fraction was 59.7%, suggesting that approximately 60% of all cases of hyperkalaemia in older patients taking spironolactone and treated with an antibiotic for a urinary tract infection could be avoided if trimethoprim-sulfamethoxazole was not prescribed. Treatment with nitrofurantoin was also associated with an increase in the risk of hyperkalaemia (adjusted odds ratio 2.4, 1.3 to 4.6), but no such risk was found with norfloxacin (adjusted odds ratio 1.6, 0.8 to 3.4) CONCLUSIONS: Among older patients receiving spironolactone, treatment with trimethoprim-sulfamethoxazole was associated with a major increase in the risk of admission to hospital for hyperkalaemia. This drug combination should be avoided when possible.
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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".