A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_session0l6hoturqdeqdm8cjub84a5mrsfjc1q8): Failed to open stream: No space left on device

Filename: drivers/Session_files_driver.php

Line Number: 177

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Failed to read session data: user (path: /var/lib/php/sessions)

Filename: Session/Session.php

Line Number: 137

Backtrace:

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 249

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 249
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated

Filename: models/Detail_model.php

Line Number: 71

Backtrace:

File: /var/www/html/application/models/Detail_model.php
Line: 71
Function: strpos

File: /var/www/html/application/controllers/Detail.php
Line: 252
Function: insertAPISummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated

Filename: helpers/my_audit_helper.php

Line Number: 8919

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 8919
Function: str_replace

File: /var/www/html/application/controllers/Detail.php
Line: 255
Function: formatAIDetailSummary

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 256

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 256
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 257

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 257
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 258

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 258
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 259

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 259
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: Trying to access array offset on value of type null

Filename: controllers/Detail.php

Line Number: 260

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 260
Function: _error_handler

File: /var/www/html/index.php
Line: 316
Function: require_once

Treatment of vesicovaginal fistulas: an experience of 30 cases. | LitMetric

AI Article Synopsis

Article Abstract

Background: Vesicovaginal fistulas (VVF) are rare. In developed countries, the majority of vesicovaginal fistulas occur after gynecological procedures such as total hysterectomies.

Objective: The evaluation of successfulness of VVF surgical repairs with transvesical, transvaginal and transabdominal approach with omental flap in 30 patients.

Methods: This is a retrospective study of patients suffering from VVF who were treated with transvesical, transvaginal and transabdominal approach with omental flap from July 2004 until December 2012. During that period, 30 patients with VVF underwent a surgical treatment at the Clinic of Urology, University Clinical Center of Banjaluka. Ten patients had previously taken radiotherapy due to cervical cancer and as a consequence of that VVF developed. In 19 patients, fistula occurred after total hysterectomy, and in one patient it occurred after the cesarean section. In six patients, primary surgical repair was performed by supravesical urinary diversion. The average size of fistula was 14 mm.

Results: The primary repair of VVF was successful in 75.00% of patients (18/24). In six patients (25.00%), it was not successful, and they remained incontinent. The successfulness of primary repairs with transvaginal and transabdominal approach with the use of omental flap was 100%, and with transvesical approach, it was 68.42%. The secondary surgical repair was performed in the remaining five patients, and it was successful in two patients (40.00%), but cumulatively speaking, the successfulness was 83.33% (20/24). In the secondary repair, the successfulness of transvaginal approach was 50.00%, and of transvesical one, it was 33.33%. Three patients underwent the tertiary surgical repair and its successfulness was 0%, and the approaches were transvaginal in one patient, transvesical in another one, and combination of transvesical with additional stitches with transvaginal approach in the third patient. When the surgical repair was undertaken for the fourth time, the successfulness was 100%. In two patients, the approach was transabdominal with interposition of omental flap, and in one patient, the approach was transvaginal. When everything is taken into consideration, 23 out of 24 patients had a successful closure of fistula, and we lost track of one patient whose primary repair was unsuccessful.

Conclusion: The selective approach to the repair of VVF mostly depends on the surgeons skill and experience. The successfulness of the repair depends on the excision of the pathological tissue, the closure of fistula in a well vascularized tissue and on urine drainage.

Download full-text PDF

Source
http://dx.doi.org/10.5455/medarh.2013.67.266-269DOI Listing

Publication Analysis

Top Keywords

omental flap
16
surgical repair
16
vesicovaginal fistulas
12
transvaginal transabdominal
12
transabdominal approach
12
approach omental
12
patients
12
approach
9
repair
9
transvesical transvaginal
8

Similar Publications

Background: Oncoplastic surgery for breast cancer patients poses the challenge of achieving optimal aesthetic outcomes without increasing the risk of complications. Omental flap has emerged as n reconstructive option in breast surgery, yet the efficacy and safety of large omental flaps remain uncertain. This study aims to conduct a systematic review and single-arm meta-analysis to comprehensively evaluate the effectiveness, safety, and cosmetic outcomes of large omental flap breast reconstruction, providing updated evidence for clinical practice.

View Article and Find Full Text PDF

Blunt esophageal injury is an exceptionally rare condition, with complete esophageal avulsion being almost unprecedented in adults. This case study details the clinical presentation, surgical management, and postoperative course of a 50-year-old male who sustained a complete esophageal avulsion following blunt abdominal trauma. The patient presented with increasing abdominal pain two hours after falling while stepping up onto a high truck step, striking his upper abdomen on the step.

View Article and Find Full Text PDF

Oncoplastic breast reconstruction with single-port laparoscopically harvested omental flap: insights from a ten-year tertiary center experience.

Breast Cancer Res Treat

December 2024

Department of Surgery, Seoul National University Bundang Hospital, Seoul National University College of Medicine, 82, Gumi-Ro 173 Beon-Gil, Bundang-Gu, Seongnam-Si, Gyeonggi-Do, 13620, Republic of Korea.

Purpose: To evaluate the 10-year functional and oncological outcomes of single-port laparoscopically harvested omental flap (SLOF) for immediate breast reconstruction after breast cancer surgery. The technical feasibility and oncologic safety of breast reconstruction using a laparoscopically harvested omental flap remain controversial.

Methods: We examined 236 patients with breast cancer (including 2 patients with malignant phyllodes tumors) who underwent nipple-sparing mastectomy or breast-conserving surgery followed by immediate SLOF reconstruction between February 2015 and March 2024 at our institution.

View Article and Find Full Text PDF

Background: Driveline infections (DLI) caused by nontuberculous mycobacteria (NTM) in patients with implantable left ventricular assist devices (iLVAD) are rare but fatal, requiring early diagnosis and appropriate treatment. Herein, we present a rare case of DLI caused by Mycobacterium chelonae, which was promptly diagnosed using Gram stain and Ziehl-Neelsen stain and followed a favorable clinical course.

Case Presentation: A 51-year-old man with an iLVAD complicated by DLI was admitted to our center.

View Article and Find Full Text PDF

Objective: To characterize and identify factors associated with long-term morbidity of definitive urosymphyseal fistula (USF) treatment.

Methods: Retrospective chart review of a single institution database identified 57 patients who underwent operative treatment of USF between 2009 and 2022 with at least 90 days of follow-up. Delayed complications were considered those occurring ≥90 days following surgery.

View Article and Find Full Text PDF

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!