Considerations beyond spine pain: do different co-occurring lower body joint pains differentially influence physical function and quality of life ratings?
Bibliographic record
Abstract
Abstract Background Patients seeking medical care for back pain often have coexisting painful joints and the effects of different combinations and number of coexisting pain sites (hip, knee, foot/ankle) to back pain on physical function domains and quality of life rating are not yet established. The purpose of this study was to determine the differences in functional outcomes and QOL among individuals with back pain who have concurrent additional pain sites or no pain sites. Methods Data from the Osteoarthritis Initiative (OAI) cohort were used for this cross-sectional analysis. Men and women aged 45–79 years with back pain were binned into nine groups by presence or not of coexisting hip, knee, ankle/foot pain and combinations of these sites (N = 1,642). Healthy controls reported no joint pain. Main outcomes included Knee Injury and Osteoarthritis Outcome score (KOOS; quality of life and function-sports-and-recreation), Western Ontario McMaster Universities Osteoarthritis Index (WOMAC; Activities of Daily Living, Pain), Medical Outcomes Short Form-12 (SF-12) Physical Component score, and self-reported function in last 7–30 days (lifting 25-pound objects, housework). 20-m and 400-m walk times and gait speed and repeated chair rise test times were collected. Results Compared to back pain alone, pain at all five sites was associated with 39%—86% worse KOOS, WOMAC, and SF-12 scores (p < .0001). Back-Hip and Back-Knee did not produce worse scores than Back pain alone, but Back-Hip-Knee and Back-Knee-Ankle/Foot did. The 20-m, 400-m walk, and repeated chair times were worse among individuals with pain at all five sites. Additional hip and knee sites to back pain, but not ankle/foot, worsened performance-based walk times and chair rise scores. Conclusions The number and type of coexistent lower body musculoskeletal pain among patients with back pain may be associated with perceived and performance-based assessments. Management plans that efficiently simultaneously address back and additional coexistent pain sites may maximize treatment functional benefits, address patient functional goals in life and mitigate disability.
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.005 | 0.018 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 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".