Abstract

Robust data comparing the timing of voiding trials following prolapse surgery are lacking. Filling in these knowledge gaps would be helpful in counseling patients preoperatively about the concerns regarding same-day discharge. We aimed to compare the rate of a failed void trial after apical pelvic organ prolapse (POP) repair between patients who were discharged on the day of surgery versus those discharged on postoperative day 1. This was a retrospective matched case-control study of women who underwent either a laparoscopic/robotic or transvaginal apical POP surgery with or without concurrent hysterectomy. Patients who were discharged on postoperative day 0 (POD0) were identified as cases and matched to control patients discharged on postoperative day 1 (POD1). Patients were matched 1:1 based on age and surgical approach. A total of 59 patients in each group met the inclusion criteria. Of the entire cohort, 34 (28.8%) patients failed their void trial, with no statistically significant difference between those who were discharged on POD0 versus POD1 (33.9% vs 23.7%, p=0.47). Patients who were discharged on POD0 were more likely to be diagnosed with a urinary tract infection (22.0% vs 8.4%, p=0.041) during the postoperative period. In patients undergoing surgery for apical prolapse, there was no difference in the rate of void trial failure in those who had a catheter removal on the day of surgery compared with those who experienced removal the following day.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

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.