0
Views
0
CrossRef citations to date
0
Altmetric
Original Article

Loop Ileostomy: Technical Aspects and Complications

&
Pages 140-143 | Received 01 Sep 2001, Published online: 04 Dec 2011
 

Abstract

Objective: To study the incidence of complications of construction and closure of loop ileostomies and the final outcome for the patients.

Design: Retrospective study.

Setting: University hospital, Norway.

Subjects: 100 patients with 103 loop ileostomies, operated on between 1980 and 1990.

Main outcome measures: Number of complications after ileostomy construction and closure.

Results: 7 required re-operation after construction of the loop ileostomy and 11 after its closure. The most common cause was small intestinal obstruction (4 after construction and 6 after closure). 2 developed stomal necrosis. The mean duration of hospital stay was 13 and 10 days for primary and secondary loop ileostomy, respectively, and the mean time before closure was 31 weeks. After closure another 6 developed leaks from the ileal anastomosis that required further operation. Patients with secondary loop ileostomies had their stomas significantly longer than those with primary loop ileostomies (21 compared with 43 weeks, p ≥ 0.00005).

Conclusion: Despite the number of complications, we think that faecal diversion is still justified in complex pelvic surgery and we should try to reduce the complication rate further.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.