Abstract
Abstract Purpose: To evaluate surgical outcomes of laparoscopic pyelolithotomy (LP) in relation to stone distribution within the kidney. Between August 2008 and February 2012, 77 patients underwent LP as first-line treatment for renal stone(s). Cases were classified into four groups, depending on stone location: Group I (located in only renal pelvis), Group II (located only in renal calyx), Group III (located in renal pelvis and in one calyx), and Group IV (located in renal pelvis and in multiple calyces). Patient and stone characteristics, surgical outcomes, and complications were evaluated. Sixty-seven (81.8%) cases were stone-free after LP for large renal stones. Stone-free rates in a single session significantly decreased with greater stone dispersion (p<0.001). Mean hospital stay in group IV was significantly longer than in other groups (p=0.038). However, there were no significant differences in mean operation times (p=0.214), mean change in serum hemoglobin (p=0.709), postoperative analgesics usages (p=0.153), and number of analgesics used on an as-needed basis (p=0.079). There were no complications of grade IIIb or of greater severity. One patient in group II received blood transfusion, and 1 in group III required percutaneous drainage due to perirenal urine collection. LP is an effective and safe modality for managing renal stones diseases. Distribution of stone burden, and total stone burden, is an important predictor of surgical outcome of LP in renal stone diseases.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.