FUNCTIONAL OUTCOME OF TOTAL KNEE REPLACEMENT WITH AND WITHOUT PATELLAR RESURFACING
Bibliographic record
Abstract
Introduction: Total knee replacement (TKR) is a commonly performed surgery that greatly improves the management of end-stage knee osteoarthritis and related conditions. While TKR is generally effective at reducing pain and improving knee function, there is ongoing debate in the orthopedic community about whether to include patellar resurfacing (PS) in the procedure. PS involves replacing the kneecap and is thought to relieve anterior knee pain (AKP), enhance patellar tracking, and improve functional outcomes. However, concerns persist about possible complications like component loosening and fractures associated with PS. Aims: To investigate the influence of patellar resurfacing on postoperative functional outcomes in patients undergoing TKR. Methods: The study conducted a prospective observational analysis, comparing functional outcomes in 80 patients, divided into two groups: those who had TKR with PS (n=40) and those who had TKR without it (n=40). All patients were over 18 years old and had Kellgren-Lawrence grade 4 knee osteoarthritis, undergoing primary TKR. Data was collected preoperatively and at several postoperative time points (6 months, 1 year, and 2 years) to assess changes in functional outcomes. Results: Both the PS and non-resurfacing groups demonstrated substantial progresses in clinical scores after TKR. At the 6-month postoperative mark, the PS group showed a remarkable mean improvement of 47.7 points on the knee pain scale, 46.2 points on the Knee Society Score (KSS), and 25.0 points on the Western Ontario and McMaster Universities Osteoarthritis Index (WOMAC). Similarly, the non-resurfacing group exhibited significant improvements with a mean improvement of 48.7 points on the knee pain scale, 50.0 points on the KSS, and 25.0 points on the WOMAC. However, there were no statistically significant differences between the two groups at any of the postoperative time points (p > 0.05), indicating that PS did not provide a significant advantage in terms of pain relief or functional outcomes. Conclusion: PS does not significantly improve functional outcomes or pain relief in TKR patients and does not increase the risk of complications. These findings provide crucial guidance for both orthopedic surgeons and patients in making informed decisions about TKR 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.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| 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.002 | 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".