A PHP Error was encountered

Severity: Warning

Message: Undefined array key "choices"

Filename: controllers/Detail.php

Line Number: 250

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 250
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: 250

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 250
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: 250

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 250
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: 250

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 250
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: 117

Backtrace:

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

File: /var/www/html/application/controllers/Detail.php
Line: 253
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: 8900

Backtrace:

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

File: /var/www/html/application/controllers/Detail.php
Line: 256
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: 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: 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: Undefined array key "usage"

Filename: controllers/Detail.php

Line Number: 261

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 261
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: 261

Backtrace:

File: /var/www/html/application/controllers/Detail.php
Line: 261
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: 261

Backtrace:

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

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

A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@pubfacts.com&api_key=b8daa3ad693db53b1410957c26c9a51b4908&a=1): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 176

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 176
Function: file_get_contents

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 250
Function: simplexml_load_file_from_url

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 1034
Function: getPubMedXML

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3152
Function: GetPubMedArticleOutput_2016

File: /var/www/html/application/controllers/Detail.php
Line: 575
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 489
Function: pubMedGetRelatedKeyword

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

A modified flexible GnRH antagonist protocol using antagonist early cessation and a gonadotropin step-down approach improves live birth rates in fresh cycles: a randomized controlled trial. | LitMetric

AI Article Synopsis

Article Abstract

Study Question: Can pregnancy outcomes following fresh elective single embryo transfer (eSET) in gonadotropin-releasing hormone (GnRH) antagonist protocols increase using a gonadotropin (Gn) step-down approach with cessation of GnRH antagonist on the day of hCG administration (hCG day) in patients with normal ovarian response?

Summary Answer: The modified GnRH antagonist protocol using the Gn step-down approach and cessation of GnRH antagonist on the hCG day is effective in improving live birth rates (LBRs) per fresh eSET cycle.

What Is Known Already: Currently, there is no consensus on optimal GnRH antagonist regimens. Studies have shown that fresh GnRH antagonist cycles result in poorer pregnancy outcomes than the long GnRH agonist (GnRHa) protocol. Endometrial receptivity is a key factor that contributes to this phenomenon.

Study Design, Size, Duration: An open label randomized controlled trial (RCT) was performed between November 2021 and August 2022. There were 546 patients allocated to either the modified GnRH antagonist or the conventional antagonist protocol at a 1:1 ratio.

Participants/materials, Setting, Methods: Both IVF and ICSI cycles were included, and the sperm samples used were either fresh or frozen from the partner, or from frozen donor ejaculates. The primary outcome was the LBRs per fresh SET cycle. Secondary outcomes included rates of implantation, clinical and ongoing pregnancy, miscarriage, and ovarian hyperstimulation syndrome (OHSS), as well as clinical outcomes of ovarian stimulation.

Main Results And The Role Of Chance: Baseline demographic features were not significantly different between the two ovarian stimulation groups. However, in the intention-to-treat (ITT) population, the LBRs in the modified antagonist group were significantly higher than in the conventional group (38.1% [104/273] vs. 27.5% [75/273], relative risk 1.39 [95% CI, 1.09-1.77], P = 0.008). Using a per-protocol (PP) analysis which included all the patients who received an embryo transfer, the LBRs in the modified antagonist group were also significantly higher than in the conventional group (48.6% [103/212] vs. 36.8% [74/201], relative risk 1.32 [95% CI, 1.05-1.66], P = 0.016). The modified antagonist group achieved significantly higher implantation rates, and clinical and ongoing pregnancy rates than the conventional group in both the ITT and PP analyses (P < 0.05). The two groups did not show significant differences between the number of oocytes retrieved or mature oocytes, two-pronuclear zygote (2PN) rates, the number of embryos obtained, blastocyst progression and good-quality embryo rates, early miscarriage rates, or OHSS incidence rates (P > 0.05).

Limitations, Reasons For Caution: A limitation of our study was that the subjects were not blinded to the treatment allocation in the RCT trial. Only women under 40 years of age who had a good prognosis were included in the analysis. Therefore, use of the modified antagonist protocol in older patients with a low ovarian reserve remains to be investigated. In addition, the sample size for Day 5 elective SET was small, so larger trials will be required to strengthen these findings.

Wider Implications Of The Findings: The modified GnRH antagonist protocol using the Gn step-down approach and cessation of GnRH antagonist on hCG day improved the LBRs per fresh eSET cycle in normal responders.

Study Funding/competing Interest(s): This project was funded by grant 2022YFC2702503 from the National Key Research & Development Program of China and grant 2021140 from the Beijing Health Promotion Association. The authors declare no conflicts of interest.

Trial Registration Number: The RCT was registered in the Chinese Clinical Trial Registry; Study Number: ChiCTR2100053453.

Trial Registration Date: 21 November 2021.

Date Of First Patient’s Enrollment: 23 November 2021.

Download full-text PDF

Source
http://dx.doi.org/10.1093/humrep/deae145DOI Listing

Publication Analysis

Top Keywords

gnrh antagonist
40
antagonist protocol
20
antagonist
16
step-down approach
16
modified antagonist
16
approach cessation
12
cessation gnrh
12
hcg day
12
modified gnrh
12
lbrs fresh
12

Similar Publications

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!