Incidence and Resolution Strategies for Early-Onset Postoperative Leg Pain Following Lumbar Total Disc Replacement
Bibliographic record
Abstract
BACKGROUND: Lumbar total disc replacement (TDR) has produced results similar or superior to fusion in treating symptomatic disc degeneration. Some patients have reported onset of leg pain early after surgery. Little information is available specifically on this problem. The purpose of this study was to investigate the incidence of early-onset postoperative leg pain following lumbar TDR and to describe strategies for its treatment. METHODS: The study was based on a post hoc analysis of prospectively collected adverse event data from 283 patients in the activL Food and Drug Administration investigational device exemption study. Early-onset leg pain was defined as occurring between 0 and 4 weeks postprocedure, and the baseline visual analog scale score in the affected leg(s) was <25 (of 100). The treatment types these patients received were analyzed. RESULTS: Among 283 patients, 26 (9.2%) had an early-onset leg pain event. The majority of these events resolved (20/26, 76.9%). Of those resolving, 55% (11/20) did so within 3 months. Most patients received at least 1 drug treatment for leg pain (92.3%). Of those receiving drug therapy, the most common type was neurogenic (61.5%), followed by narcotics (46.2%). Steroid use was prescribed in 30.8%. The majority of resolved cases were not on narcotics and resolved with neurogenic drugs. Three patients went on to have surgery, none of whom benefited from it. Age, body mass index, and baseline disability scores were predictive of time to resolution. CONCLUSION: Early-onset postoperative leg pain occurred in approximately 10% of lumbar TDR patients. The majority of events resolved, often within 3 months. Treatment with conservative care, including medication(s), was more effective in resolving symptoms rather than surgery. CLINICAL RELEVANCE: This study provides useful information for providers and patients on the incidence, treatment, and resolution of leg pain with onset after lumbar TDR and not related to direct neural compression identified by imaging. LEVEL OF EVIDENCE: 2.
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.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 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".