Functional Recovery after Surgery for Lumbar Spinal Stenosis in Patients with Hypertension
Bibliographic record
Abstract
Hypertension is a prevalent condition that is associated with lower health status in patients with lumbar spinal stenosis. The study determined whether hypertension is a prognostic factor associated with functional recovery after spine surgery for lumbar spinal stenosis. This was a secondary analysis of the Alberta Lumbar Spinal Stenosis Study in which patients were identified as participants at the time of lumbosacral magnetic resonance imaging or computed tomography in Calgary, Alberta, Canada. Multivariable linear regression analyses were performed to examine hypertension as a prognostic factor of functional recovery after surgery (Oswestry Disability Index, the Swiss Spinal Stenosis (SSS)-Symptom Severity and SSS-Physical Function scales). Of the 97 surgical participants, 49 who were hypertensive were older (76.8, SD 11.4 years) than the 48 non-hypertensive participants (66.7, SD 12.4 years) (p < 0.001). No significant associations between hypertension and post-operative function in any of the three multivariable models were seen. The Oswestry Disability Index mean score improved after surgery (effect size: 1.73; 95%CI: 1.39, 2.06), with no differences seen between those with and without hypertension (p = 0.699). Large changes were seen after surgery for the SSS-Symptom Severity (effect size: 1.0, 95%CI 0.7, 1.3) and SSS-Physical Function (effect size: 0.9, 95%CI 0.6, 1.2) scales. Hypertension alone does not negatively impact functional recovery following surgery.
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.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 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.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".