Laparoscopic Colon Surgery: Does Operative Time Matter?
Bibliographic record
Abstract
PURPOSE: The purpose was to determine if the perioperative benefits associated with laparoscopic colectomies are maintained as operative time increases. METHODS: A retrospective review was performed of a database that was prospectively collected from April 1991 to May 2005. Since operative time distributions were different, patients were divided into three groups: laparoscopic right colectomy or ileocecal resection, sigmoid resection, and total abdominal colectomy. The following outcomes were assessed: intraoperative and postoperative complications, days to surgical diet, length of stay, 30-day mortality, and the presence of a learning curve. RESULTS: Following exclusions, there were 231 right colon and ileocecal resections, 210 sigmoid colectomies, and 46 total abdominal colectomies. With increasing operative time in both right/ileocecal and sigmoid resections, logistic regression demonstrated no significant association between intraoperative and postoperative complications, days to surgical diet, or length of stay. Weight was significantly correlated with increasing operative time in the right/ileocecal and sigmoid resection groups. In the total abdominal colectomy group, significant relationships between increased operative time and postoperative complications (P = 0.04), days to surgical diet (P = 0.02), and hospital stay (P = 0.03) were found. An operative time cut-point was determined in the total abdominal colectomy group. Patients with operative times >270 minutes were more likely to have postoperative complications (P = 0.024), longer ileus (five vs. three median days to surgical diet, P = 0.003), and longer length of stay (seven vs. five days, P = 0.04). This increased risk remained significant after adjusting for weight and diagnosis. No significant learning curve was identified. CONCLUSION: Increasing operative time does not appear to adversely affect perioperative outcomes in segmental colectomies. Total abdominal colectomies lasting more than 270 minutes were associated with increased postoperative complications, days to surgical diet, and length of stay.
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.025 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".