Does the addition of iPACK to adductor canal block in the presence or absence of periarticular local anesthetic infiltration improve analgesic and functional outcomes following total knee arthroplasty? A systematic review and meta-analysis
Bibliographic record
Abstract
Background When combined with adductor canal block (ACB), local anesthetic infiltration between popliteal artery and capsule of knee (iPACK) is purported to improve pain following total knee arthroplasty (TKA). However, the analgesic benefits of adding iPACK to ACB in the setting of surgeon-administered periarticular local infiltration analgesia (LIA) are unclear. Objectives To evaluate the analgesic benefits of adding iPACK to ACB, compared with ACB alone, in the setting of LIA following TKA. Evidence review We conducted a meta-analysis of randomized trials comparing the effects of adding iPACK block to ACB versus ACB alone on pain severity at 6 hours postoperatively in adult patients undergoing TKA. We a priori planned to stratify analysis for use of LIA. Opioid consumption at 24 hours, functional recovery, and iPACK-related complications were secondary outcomes. Findings Fourteen trials (1044 patients) were analyzed. For the primary outcome comparison in the presence of LIA (four trials, 273 patients), adding iPACK to ACB did not improve postoperative pain at 6 hours. However, in the absence of LIA (eight trials, 631 patients), adding iPACK to ACB reduced pain by a weighted mean difference (WMD) (95% CI) of −1.33 cm (−1.57 to –1.09) (p<0.00001). For the secondary outcome comparisons in the presence of LIA, adding iPACK to ACB did not improve postoperative pain at all other time points, opioid consumption or functional recovery. In contrast, in the absence of LIA, adding iPACK to ACB reduced pain at 12 hours, and 24 hours by a WMD (95% CI) of −0.98 (−1.79 to –0.17) (p = 0.02) and −0.69 (−1.18 to –0.20) (p=0.006), respectively, when compared with ACB alone, but did not reduce opioid consumption. Functional recovery was also improved by a log(odds ratio) (95% CI) of 1.28 (0.45 to 2.11) (p=0.003). No iPACK-related complications were reported. Conclusion Adding iPACK to ACB in the setting of periarticular LIA does not improve analgesic outcomes following TKA. In the absence of LIA, adding iPACK to ACB reduces pain up to 24 hours and enhances functional recovery. Our findings do not support the addition of iPACK to ACB when LIA is routinely administered.
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.012 | 0.029 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.019 | 0.036 |
| Bibliometrics | 0.005 | 0.006 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 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".