Complications related to the use of spinal cord stimulation for managing persistent postoperative neuropathic pain after lumbar spinal surgery
Bibliographic record
Abstract
OBJECT Structural spinal surgery yields improvement in pain and disability for selected patients with spinal stenosis, spondylolisthesis, or a herniated intervertebral disc. A significant fraction of patients exhibit persistent postoperative neuropathic pain (PPNP) despite technically appropriate intervention, and such patients can benefit from spinal cord stimulation (SCS) to alleviate suffering. The complication profile of this therapy has not been systematically assessed and, thus, was the goal of this review. METHODS A comprehensive literature search was performed to identify prospective cohorts of patients who had PPNP following structurally corrective lumbar spinal surgery and who underwent SCS device implantation. Data about study design, technique of SCS lead introduction, and complications encountered were collected and analyzed. Comparisons of complication incidence were performed between percutaneously and surgically implanted systems, with the level of significance set at 0.05. RESULTS Review of 11 studies involving 542 patients formed the basis of this work: 2 randomized controlled trials and 9 prospective cohorts. Percutaneous implants were used in 4 studies and surgical implants were used in 4 studies; in the remainder, the types were undefined. Lead migration occurred in 12% of cases, pain at the site of the implantable pulse generator occurred in 9% of cases, and wound-related complications occurred in 5% of cases; the latter 2 occurred more frequently among surgically implanted devices. CONCLUSIONS Spinal cord stimulation can provide for improved pain and suffering and for decreased narcotic medication use among patients with PPNP after lumbar spinal surgery. This study reviewed the prospective studies forming the evidence base for this therapy, to summarize the complications encountered and, thus, best inform patients and clinicians considering its use. There is a significant rate of minor complications, many of which require further surgical intervention to manage, including lead migration or implant infection, although such complications do not directly threaten patient life or function.
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.003 | 0.017 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.007 | 0.009 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".