Chrome Extension
WeChat Mini Program
Use on ChatGLM

Fibrosis in the rotator interval associated with articular vs. bursal side partial-thickness rotator cuff tears

JSES International(2020)

Cited 1|Views5
No score
Abstract
Background The pathogenesis of articular- and bursal-sided partial-thickness rotator cuff tears (PTRCTs) is considered to be different, and associated lesions with PTRCTs need to be examined. Methods The current study consisted of 76 shoulders of 73 patients (27 men, 46 women, 64.0 ± 8.3 years old) who underwent mini-open repair after conversion to full-thickness tears for either articular side (group A; n = 56) or bursal side (group B; n = 20) PTRCT with at least a 2-year follow-up. Clinical outcomes and their images were compared between the groups. Plain radiographs were used with the arm passively elevated in maximum elevation to assess restriction of glenohumeral motion. Results The retear rate was not significantly different between the groups. Both groups showed significant improvement in functional scores at the final follow-up. Patients in group A showed a higher incidence of preoperative fibrosis in the rotator interval (69.6% vs. 35.0%, respectively; P = .006) and a lower incidence of an acromial spur (7.1% vs. 35.0%, respectively; P = .008) compared with group B. Plain radiographs with arm elevation showed restriction of glenohumeral movement in 49 of 76 shoulders (64.5%) preoperatively, including 36 of the 46 shoulders with fibrosis and 13 of the other 30 shoulders. Conclusion Both articular- and bursal-sided PTRCTs showed significant functional improvements after surgery. The articular-sided tears had a lower incidence of an acromial spur, but had a higher incidence of fibrosis in the rotator interval, which led to a limitation in glenohumeral motion.
More
Translated text
Key words
Rotator cuff tear,partial thickness,rotator interval,shoulder stiffness,MRI,mini open repair
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined