Retrospective study demonstrates favorable one-year survival after uniportal robotic esophagectomy in esophageal cancer, indicating feasible oncologic efficacy.
Topic Esophageal Cancer: Surgical Treatment of Esophageal Cancer – technique Background Uniportal robotic-assisted minimally invasive esophagectomy has demonstrated perioperative safety in preliminary experience; however, its oncologic outcomes remain to be established. This study aimed to evaluate one-year overall survival and disease-free survival after uniportal robotic-assisted minimally invasive esophagectomy. Methods Patients who underwent uniportal robotic-assisted minimally invasive esophagectomy between September 2024 and July 2025 were retrospectively reviewed. The primary outcome was one-year overall survival and disease-free survival. Oncologic adequacy, including the complete resection rate with microscopically negative margins and lymph node yield, was also assessed. Perioperative outcomes were analyzed descriptively. Results Twenty-one patients underwent uniportal robotic-assisted minimally invasive esophagectomy. Squamous cell carcinoma accounted for 81%, and 62% had stage III–IV disease; 71% received neoadjuvant therapy. Complete resection with microscopically negative margins was achieved in 95%, with a median lymph node yield of 34. At a median follow-up of 11.1 months, the overall survival and disease-free survival for the entire cohort were 83% and 76%, respectively. In stage I–II disease, both overall survival and disease-free survival were 100%. In stage III–IV disease, overall survival and disease-free survival were 74% and 62%, respectively. Conclusion Uniportal robotic-assisted minimally invasive esophagectomy is feasible and demonstrates encouraging early oncologic outcomes, even in a cohort with predominantly advanced-stage disease.
No takes yet. Share an insight, caveat, or question.
Kuo et al. (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: