Laparoscopic incisional hernia repair after colorectal surgery. Is it possible to maintain a mini-invasive approach?

Abstract

Several benefits have been described in laparoscopic surgery. However, there is a lack of evidence concerning laparoscopic repair of incisional hernia after laparoscopic colorectal surgery (LCRS). We aimed to evaluate the feasibility and the results of laparoscopic incisional hernia repair after LCRS. Between May 2001 and March 2014, all charts of consecutive patients who underwent LCRS and developed an incisional hernia were evaluated. Patients with parastomal hernias or those with less than 6 months of follow-up were excluded. Patients were assigned to laparoscopic repair group (LR) and open repair group (OR). Demographics, surgical factors, and 30-day postoperative complications were analyzed. The incisional ventral hernia rate was 7 % (90/1290), and 82 incisional hernia repairs were performed. In 49 patients (60 %) an open approach was performed, and there were 33 laparoscopic repairs (2 converted due to small bowel injury). Mean age was 62 years. Average body mass index was 27.4 ± 5.2 kg/m². The mean defect size was 56 (4–527) cm², and there were no differences between the groups (LR: 49 cm² vs OR: 63 cm²; p = NS). Average operative time was 107 (45–240) minutes (LR: 93 min vs OR: 116 min, p = 0.02). OR showed a higher rate of postoperative complications (OR: 51 % vs LR: 18 %, p = 0.003) and increased hospital stay (OR: 2.77 ± 4 days vs LR: 0.7 ± 0.4 days; p = 0.02). The recurrence rate was 15 % (12 patients, 6 each group; p = NS) after a follow-up of 48 (r: 6–141) months. Laparoscopic approach for incisional hernia repair after LCRS seems to be safe and feasible. Patients who received laparoscopic approach showed significantly less postoperative complications and shorter hospital staying. These observations suggest that mini-invasive surgery may be the initial approach in patients who develop an incisional hernia after LCRS.

from Endoscopy via xlomafota13 on Inoreader http://ift.tt/1ToD0Wo
via IFTTT