Reduction of Inpatient Hospital Length of Stay in Lumbar Fusion Patients With Implementation of an Evidence-Based Clinical Care Pathway
Bibliographic record
Abstract
STUDY DESIGN: Quality improvement with before and after evaluation of the intervention. OBJECTIVE: To improve lumbar spine postoperative care and quality outcomes through a series of Lean quality improvement events designed to address root causes of error and variation. SUMMARY OF BACKGROUND DATA: Lumbar spine fusion procedures are common, but highly variable in process of care, outcomes, and cost. METHODS: We implemented a standardized lumbar spine fusion clinical care pathway through a series of Lean quality improvement events. The pathway included an evidence-based electronic order set; a patient visual tool; and multidisciplinary communication, and was designed to delineate expectations for patients, staff, and providers. To evaluate the effectiveness of the intervention, we performed a quality improvement study with before and after evaluation of consecutive patients from January 2012 to September 2014. Outcomes were hospital length of stay and quality measures before and after the April 1, 2013 intervention. Data were analyzed with chi-square and t tests for before and after comparisons, and were explored graphically for temporal trends with statistical process control charts. RESULTS: Our study population was 458 patients (mean 65 years, 65% women). Length of stay decreased from 3.9 to 3.4 days, a difference of 0.5 days (CI 0.3, 0.8, P < 0.001). Discharge disposition also improved with 75% (183/244) being discharged to home postintervention versus 64% (136/214) preintervention (P = 0.002). Urinary catheter removal also improved (P = 0.003). Patient satisfaction scores were not significantly changed. CONCLUSION: Applying Lean methods to produce standardized clinical pathways is an effective way of improving quality and reducing waste for lumbar spine fusion patients. We believe that quality improvements of this type are valuable for all spine patients, to provide best care outcomes at lowest cost. LEVEL OF EVIDENCE: 4.
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.006 | 0.017 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| 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".