Abstract
BACKGROUND: Scientific evidence is not clear regarding the routine use of acromioplasty in the treatment of rotator cuff repair. The aim of this study was to compare clinical outcomes between patients undergoing arthroscopic rotator cuff repair with and without concomitant acromioplasty. METHODS: Medline, Cochrane Library, and EMBASE databases were searched to identify eligible studies focused on arthroscopic rotator cuff repair with and without acromioplasty from January 2000 to February 2018. Postoperative functional outcomes, visual analog scale (VAS) for pain and reoperation rate were extracted for systemic analysis. RESULTS: Six randomized controlled trials (RCTs) and one cohort study (CS), including 651 patients, fulfilled our selection criteria. The results showed a significant difference in American Shoulder and Elbow Surgeons (ASES) score, but not in the Constant score, University of California-Los Angeles (UCLA) score, or Simple Shoulder Test (SST) score, in the treatment of rotator cuff tear with or without concomitant acromioplasty at the final follow-up. In the subgroup analysis, the results showed no significant differences between the two treatments in reoperation rate at the final follow-up or VAS score at 6 months postoperatively and final follow-up, but there was a significant difference in VAS score at 12 months postoperatively in favor of acromioplasty treatment. The evidence quality for each outcome evaluated by the GRADE system was low. CONCLUSIONS: In summary, our present study demonstrated that acromioplasty treatment is significantly superior to nonacromioplasty in shoulder pain relief at 12 months postoperatively and in ASES score improvement at the final follow-up in conjunction with rotator cuff repair. However, these significant differences were not clinically relevant. Thus, there were no differences in shoulder function or pain scores for patients undergoing rotator cuff repair with and without acromioplasty. Further high-quality studies with larger sample sizes and long-term follow-ups are needed to clarify this issue.