Consequences of spilt gallstones during laparoscopic cholecystectomy.

OA: closed
📄 Open PDF View on PubMed View at publisher
⚙ AI-generated summary by qwen3.7-flash, 2026-08-23 ⓘ

This prospective study of 150 laparoscopic cholecystectomies found a 19.04% incidence of spilled gallstones, which resulted in a low complication rate but highlights the need for careful retrieval to prevent long-term issues.

One-sentence paraphrase of the abstract; not a substitute for reading it. No clinical advice. How this works

Abstract

To document the incidence of spilt gallstones during laparoscopic cholecystectomy, the cause and consequences of such spillage. The study included 150 consecutive laparoscopic cholecystectomies performed between October 2007 and November 2008. Data was collected in a prospective manner in accordance to proforma. Follow up were performed at the end of 1 week, 1 month, 6 months and 1 year. The spillage of gall stones during surgery occurred in 19.04 % of the cases. Majority of the spillage occurred due to perforation of the gall bladder during dissection, followed by application of toothed grasper. Although all visible spilt stones were retrieved during surgery, complication rate of 0.66 % was observed. The incidence and complications secondary to the spillage of gall stones during standard laparoscopic cholecystectomy is low but avoidable. Various complications can occur, over a large period of time. Thus it is advisable to retrieve as many gallstones as possible short of converting to a laparotomy Dasari and Loan (JSLS 13(1):73-76, 2009), Daradkeh and Suwan (World J Surg 22:75-77, 1998).

My notes (saved in your browser only)

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. The paper's references may be in our DB but unresolved to ``paper_id`` (resolution happens at ingest when the cited DOI matches a row we already have). Run the cross-source citation reconcile pass to retry.

Source provenance

europepmc
last seen: 2026-10-04T09:26:46.659050+00:00