Laparoscopic isolated caudate lobe resection

Maulik Parikh, Ho Seong Han, Jai Young Cho, Mizelle D’Silva

Research output: Contribution to journalArticlepeer-review


Previously, isolated caudate lobectomy was rarely performed and the caudate lobe was usually resected along with other segments. Isolated caudate lobe resection is a challenging procedure even for an experienced surgeon. Our aim was to evaluate the feasibility, safety and outcomes of laparoscopic isolated caudate lobectomy and to compare these with the open technique. We retrospectively analyzed 21 patients who underwent isolated caudate lobectomy between January 2005 and December 2018 at Seoul National University Bundang Hospital. Patients who underwent either anatomical or non-anatomical resection of the caudate lobe were included. Patients were divided into two groups according to whether they underwent laparoscopic or open surgery. Intra-operative and postoperative outcomes were compared with a median follow-up of 43 months (4–149). A total of 21 patients were included in the study. Of these, 12 (57.14%) underwent laparoscopic and nine (42.85%) underwent open caudate lobectomy. Median operation time (204.5 vs. 200 minutes, p = 0.397), estimated blood loss (250 vs. 400 ml, p = 0.214) and hospital stay (4 vs. 7 days, p = 0.298) were comparable between laparoscopy and open group. The overall post operative complication rate was similar in both groups (p = 0.375). The 5-year disease free survival rate (42.9% vs 60.0%, p = 0.700) and the 5-year overall survival rate (76.2% vs 64.8%, p = 0.145) was similar between laparoscopy and open group. Our findings demonstrate that with increasing surgical expertise and technological advances, laparoscopic isolated caudate lobectomy can become a feasible and safe in selected patients.

Original languageEnglish
Article number4328
JournalScientific Reports
Issue number1
StatePublished - Dec 2021

Fingerprint Dive into the research topics of 'Laparoscopic isolated caudate lobe resection'. Together they form a unique fingerprint.

Cite this