No difference in clinical outcome after rotator cuff repair performed within or later than 3 months after trauma: a retrospective cohort study
Bibliographic record
Abstract
PURPOSE: Rotator cuff (RC) tear is one of the most common injuries of the shoulder. Patients with RC tears often report a trauma initiating shoulder pain and impaired function. The aim of this retrospective analysis of a prospectively registered cohort was to elucidate whether the time interval between the trauma and RC repair, using a cut off of 3 months, affects the functional outcome after 2 years. METHODS: In a single orthopedic unit, 819 consecutive patients were treated with rotator cuff repair during the period from 2010 to 2014 and 733 of the patients completed the Western Ontario Rotator Cuff (WORC) index preoperatively and at 2-year follow-up. The Constant-Murley (CM) score was completed by trained physiotherapists after a clinical examination both preoperatively and at 2-year follow-up. Preoperative magnetic resonance imaging (MRI) was performed in all patients and postoperatively in 65% of the included patients. Re-tears and partial repairs were excluded, as were patients with pseudoparalysis who were given high priority and underwent surgery during the first 3 weeks after trauma. RESULTS: Of the 733 treated patients, 437 (60%) reported having had a shoulder trauma in their medical history initiating their shoulder symptoms, and of these, 358 met the inclusion criteria. 296 patients with non-traumatic tears, 9 repairs done within 3 weeks after trauma, 25 partial repairs, 33 re-tears and 12 others were excluded. At 2-year follow-up there was no significant difference in WORC index (n.s.) or CM score (n.s.) between patients who had their RC repaired within or more than 3 months after trauma. In patients where RC repair was performed within 3 months, the WORC index improved by 42.9%, and in the group of patients operated later than 3 months, the increase was 38.7%. This difference between the groups was neither statistically significant (n.s.) nor clinically relevant. On postoperative MRI, 80% of the repairs were healed in both groups. CONCLUSION: In this retrospective cohort study, no differences in clinical outcome were found when RC repair was performed between 3 weeks and 3 months or later than 3 months after injury in patients describing their onset of symptoms as traumatic. LEVEL OF EVIDENCE: III.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| 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.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".