Prevalence, Timing, Causes, and Outcomes of Hyponatremia in Hospitalized Orthopaedic Surgery Patients
Bibliographic record
Abstract
BACKGROUND: Hyponatremia is common among orthopaedic patients and is associated with adverse clinical outcomes. We examined the prevalence, timing, causes, and outcomes of hyponatremia in adult hospitalized orthopaedic surgery patients. METHODS: We evaluated the medical records of 1067 consecutive orthopaedic surgery patients admitted to a tertiary academic institution. The medical records were reviewed to investigate hyponatremia (serum sodium <135 mEq/L) that (1) had been present on hospital admission or (2) had developed postoperatively. The primary outcomes were the prevalence and timing of, and risk factors for, presentation with or development of hyponatremia. Secondary outcomes were hospital length of stay, total hospital cost, and discharge disposition. Multivariable logistic regression models were used to assess the variables associated with hyponatremia and the effects of hyponatremia on clinical outcomes. RESULTS: Of the 1067 patients, seventy-one (7%) had preoperative hyponatremia and 319 (30%) developed hyponatremia postoperatively. Of the latter, 298 (93%) developed hyponatremia within forty-eight hours postoperatively. Compared with patients with normonatremia, those who presented with hyponatremia, on the average, were older (67.2 versus 60.5 years, p < 0.001), had longer hospital stays (4.6 versus 3.3 days, p < 0.001), incurred higher hospital costs ($19,200 versus $17,000, p = 0.006), and were more likely to be discharged to an extended-care facility (odds ratio [OR] = 2.87, p < 0.001). Developing hyponatremia postoperatively resulted, on average, in a longer hospital stay (3.7 versus 3.3 days, p = 0.002) and greater hospital cost ($18,800 versus $17,000, p < 0.001). Age (OR = 1.13 per decade, p = 0.012), spine surgery (OR = 2.76 versus knee, p < 0.001), hip surgery (OR = 1.76 versus knee, p < 0.001), and the amount of lactated Ringer solution used (OR = 1.16, p = 0.002) increased the risk of developing hyponatremia. CONCLUSIONS: Hyponatremia in orthopaedic patients is associated with longer, costlier hospitalizations. The factors that significantly increased the risk of developing postoperative hyponatremia were an older age, spine fusion, hip arthroplasty, and the amount of lactated Ringer solution used.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".