Outcomes Associated with Reducing the Urine Alkalinization Threshold in Patients Receiving High‐Dose Methotrexate
Bibliographic record
Abstract
STUDY OBJECTIVES: Urine alkalinization increases methotrexate (MTX) solubility and reduces the risk of nephrotoxicity. The objectives of this study were to determine whether a reduction in the urine pH threshold from 8 to 7 in patients receiving high-dose methotrexate (HDMTX) results in a shorter length of hospital stay, delayed MTX clearance, or higher rates of nephrotoxicity; and to determine whether specific factors were associated with prolonged MTX clearance. DESIGN: Retrospective cohort study. SETTING: Hematology service of a large university-affiliated teaching hospital in Ottawa, Canada. PATIENTS: Sixty-five adults with 150 HDMTX exposures who had elective admissions for HDMTX between September 1, 2014, and December 18, 2015, were included. Thirty-four patients (with 79 HDMTX exposures) had their urine alkalinized to a pH of 8 or higher, and 31 patients (with 71 HDMTX exposures) had their urine alkalinized to a pH of 7 or higher, after an institutional change in the urine pH threshold from 8 to 7 was implemented on May 1, 2015. MEASUREMENTS AND MAIN RESULTS: Data related to patient demographics, urine alkalinization, MTX serum concentration monitoring, hospital length of stay, and renal function were collected retrospectively from patients' electronic health records. Lowering the urine pH threshold from 8 to 7 did not significantly affect hospital length of stay (absolute difference 3.5 hrs, 95% confidence interval -4.0 to 10.9) or clearance of MTX (elimination rate constant 0.058 in the pH of 7 or higher group vs 0.064 in the pH of 8 or higher group, p=0.233). Nephrotoxicity rates were similar between groups (15.5% in the pH of 7 or higher group vs 10.1% in the pH of 8 or higher group, p=0.34). Higher MTX dose and interacting medications (e.g., proton pump inhibitors and sulfonamide antibiotics) were significantly associated with delayed MTX elimination. CONCLUSION: No significant differences in HDMTX-associated hospital length of stay, MTX clearance, or rates of nephrotoxicity were noted between patients in the urine pH of 7 or higher and 8 or higher groups. Interacting medications and higher MTX dose were associated with delayed MTX elimination, suggesting that a closer review of interacting medications before HDMTX administration may be warranted.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| 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".