A PHP Error was encountered

Severity: Warning

Message: fopen(/var/lib/php/sessions/ci_sessionjrtt442at7n204sb0r78t72k9j04u6rl): 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

Hysteroscopic myomectomy and case volume hysteroscopic myomectomy performed by high- and low-volume surgeons. | LitMetric

Hysteroscopic myomectomy and case volume hysteroscopic myomectomy performed by high- and low-volume surgeons.

J Reprod Med

Department of Obstetrics and Gynecology, Spaarne Ziekenhuis, Hoofddorp, the Netherlands.

Published: July 2009

AI Article Synopsis

Article Abstract

Objective: To determine whether surgical volume influences efficiency of hysteroscopic myomectomy as a treatment for uterine fibroids.

Study Design: This retrospective cross-sectional study performed at a university teaching hospital included all patients who underwent hysteroscopic myomectomy between 2001 and 2005 by a faculty surgeon. We used 3 outcomes as measures of efficiency: amount of tissue resected per case, operating department time per case and amount of tissue resected per minute.

Results: High-volume surgeons resected more tissue than low-volume surgeons (p = 0.01), had shorter operating department times (p = 0.018) and resected more tissue per time (p = 0.015).

Conclusion: High-volume surgeons have higher efficiency performing hysteroscopic myomectomy as a treatment for uterine fibroids.

Download full-text PDF

Source

Publication Analysis

Top Keywords

hysteroscopic myomectomy
20
low-volume surgeons
8
myomectomy treatment
8
treatment uterine
8
amount tissue
8
tissue resected
8
operating department
8
high-volume surgeons
8
resected tissue
8
hysteroscopic
5

Similar Publications

A case report on the loss of an Iglesias resectoscope beak during hysteroscopic myomectomy.

J Minim Access Surg

December 2024

Maternal and Child Department, Complex Operative Unit of Obstetrics and Gynecology, Hospital of Gubbio and Gualdo Tadino, ASL 1 Umbria, Perugia, PG, Italy.

This case report describes the dynamics of the detachment of the ceramic beak of an Iglesias resectoscope that was lost in the uterine cavity during 'cold loop' hysteroscopic myomectomy. Our aim is to increase awareness of this issue and caution our colleagues against using Iglesias resectoscopes for hysteroscopies. The ceramic beak of an Iglesias resectoscope can detach itself if hard tissue is encountered during operative hysteroscopy.

View Article and Find Full Text PDF

Submucosal uterine fibroids are the rarest type of fibroids. They can lead to abnormal uterine bleeding and may play a role in infertility and miscarriage. Hysteroscopic myomectomy is the preferred treatment to relieve bleeding caused by these fibroids and to restore the normal structure of the uterine cavity.

View Article and Find Full Text PDF

Possible new application of high-intensity focused ultrasound: degradation of uterine myoma classification.

Int J Hyperthermia

December 2024

Department of Obstetrics and Gynecology, West China Second University Hospital, Sichuan University, Chengdu, China.

Hysteroscopic myomectomy is widely used to treat submucosal myomas. However, performing hysteroscopic surgery on certain type II (and even type III) or large myomas remains challenging. High-intensity focused ultrasound (HIFU) has recently emerged as a promising alternative for treating various gynecologic conditions.

View Article and Find Full Text PDF

A new uterine endometrium preservation hysteroscopic myomectomy: Introduction of improved procedures and a retrospective analysis of 94 cases.

Eur J Obstet Gynecol Reprod Biol X

December 2024

Department of Obstetrics and Gynecology, Maruyama Memorial General Hospital, 2-10-5, Honchou, Iwatsuki-ku, Saitama City, Saitama 339-8521, Japan.

Objective: To reduce the damage of uterine endometrium caused during hysteroscopic myomectomy (HM) for reproductive aged patients, a new uterine endometrium preservation hysteroscopic myomectomy (UEP-HM) has been developed. In this study, we introduced this technique with comparing to the conventional hysteroscopic myomectomy (C-HM).

Study Design: The data from 94 patients aged 42 or younger who underwent HM (38 cases with UEP-HM and 56 cases with C-HM) for treating single Type 1 or Type 2 submucosal leiomyoma (SL) were analysed retrospectively for comparing the characteristics of both patient and target SL.

View Article and Find Full Text PDF
Article Synopsis
  • This study compared the outcomes of myomectomy performed with preoperative uterine artery embolization (UAE) versus myomectomy alone, focusing on blood loss and complications.
  • Results showed that blood loss was significantly lower in the UAE group, but there were similar rates for postoperative complications between the two groups.
  • Long-term fertility outcomes were concerning for the UAE group, with higher rates of adhesions, miscarriages, and obstetrical complications compared to the non-UAE group.
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!