The sodium does not affect joint pain and functional activity of knee osteoarthritis patients
Bibliographic record
Abstract
Background: The sodium may aggravate synovial inflammation and cartilage thinning. This incidence can cause joint pain and reduce functional activity. Not many people know the effect of sodium on the incidence of osteoarthritis. Objective: This study aims to determine the relationship between sodium in the body and knee joint pain which results in functional activity. Methods: The quantitative descriptive study used accidental sampling. The study was conducted at three outpatient polyclinic orthopedics of hospitals and was approved by the Health Ethics Committee. All data were collected during the interview. The Semi-Quantitative Food Frequency Questionnaire and the Nutrisurvey Indonesia 2007 application were used as a tool to collect daily sodium intake (mg). Knee joint pain score was measured using the Visual Analog Scale (VAS), while functional body activity was measured using the Western Ontario McMaster Osteoarthritis Index (WOMAC). The Pearson and Spearman test (P<0.05) were used as a correlation test. Results: (54, 67.5%) and occupation (43, 53.75%). Average sodium intake = 2090.78±1084.33 mg, VAS score = 6.28±1.95 and WOMAC score = 32.65±14.88. The correlation sodium, VAS, and WOMAC were not significant (P=0.196, P=0.372). Conclusions: Increased sodium intake is not associated with knee joint pain and functional body activity.
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.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| 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.000 |
| 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".