Suprascapular and Interscalene Nerve Block for Shoulder Surgery
Bibliographic record
Abstract
BACKGROUND: Interscalene block provides optimal shoulder surgery analgesia, but concerns over its associated risks have prompted the search for alternatives. Suprascapular block was recently proposed as an interscalene block alternative, but evidence of its comparative analgesic effect is conflicting. This meta-analysis compares the analgesic effect and safety of suprascapular block versus interscalene block for shoulder surgery. METHODS: Databases were searched for randomized trials comparing interscalene block with suprascapular block for shoulder surgery. Postoperative 24-h cumulative oral morphine consumption and the difference in the area under curve for pooled rest pain scores were designated as primary outcomes. Analgesic and safety outcomes, particularly block-related and respiratory complications, were evaluated as secondary outcomes. Results were pooled using random-effects modeling. RESULTS: Data from 16 studies (1,152 patients) were analyzed. Interscalene block and suprascapular block were not different in 24-h morphine consumption. The difference in area under the curve of pain scores for the 24-h interval favored interscalene block by 1.1 cm/h, but this difference was not clinically important. Compared with suprascapular block, interscalene block reduced postoperative pain but not opioid consumption during recovery room stay by a weighted mean difference (95% CI) of 1.5 cm (0.6 to 2.5 cm; P < 0.0001). Pain scores were not different at any other time. In contrast, suprascapular block reduced the odds of block-related and respiratory complications. CONCLUSIONS: This review suggests that there are no clinically meaningful analgesic differences between suprascapular block and interscalene block except for interscalene block providing better pain control during recovery room stay; however, suprascapular block has fewer side effects. These findings suggest that suprascapular block may be considered an effective and safe interscalene block alternative for shoulder 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.004 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.003 | 0.009 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 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".