Perioperative pregabalin does not reduce opioid requirements in total knee arthroplasty
Bibliographic record
Abstract
PURPOSE: The purpose of this prospective, randomized, double-blinded, placebo-controlled study was to determine if pregabalin, when given perioperatively in addition to patient-controlled analgesia morphine, paracetamol and etoricoxib, is effective in reducing morphine requirements and moderating pain scores after primary total knee arthroplasty. We hypothesize that there would be no difference in postoperative opioid requirements, postoperative pain scores, and functional scores with the use of perioperative pregabalin. METHODS: Eighty-seven patients who underwent primary total knee arthroplasty were randomised and allocated to two groups. One group received capsules containing pregabalin 75 mg, and the other a placebo-one capsule before surgery and one capsule once per night up till postoperative day 2. Multimodal analgesia provided for all patients in this study included femoral nerve block, intravenous patient-controlled analgesia (morphine), paracetamol and etoricoxib. The primary outcome of patient's pain control was based on the measurement of cumulative morphine consumption during the first 72 h postoperatively. RESULTS: Pregabalin did not reduce the cumulative or effective morphine consumption at 48 h and 72 h post-operation. There were also no significant differences noted in pain scores at 48 h and 72 h after surgery, functional range of motion of the operated knee at 72 h post-op, or outcomes recorded on the Knee Society Score (KSS), Western Ontario and McMaster Universities Osteoarthritis Index (WOMAC) and 36-Item Short Form Survey (SF-36) questionnaires at 3 and 6 months post-op. None of the patients demonstrated common adverse reactions to pregabalin. CONCLUSION: This study showed no reduction in postoperative opioid requirements, or improvement in early postoperative pain scores or functional outcomes at 6 months, with perioperative use of pregabalin. Orthopaedic surgeons may consider this when selecting an analgesic regimen for their patients. LEVEL OF EVIDENCE: II.
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.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| 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".