A PHP Error was encountered

Severity: Warning

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

A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@gmail.com&api_key=61f08fa0b96a73de8c900d749fcb997acc09): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 143

Backtrace:

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

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

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

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

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

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

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

The euploid blastocysts obtained after luteal phase stimulation show the same clinical, obstetric and perinatal outcomes as follicular phase stimulation-derived ones: a multicenter study. | LitMetric

AI Article Synopsis

Article Abstract

Study Question: Are the reproductive outcomes (clinical, obstetric and perinatal) different between follicular phase stimulation (FPS)- and luteal phase stimulation (LPS)-derived euploid blastocysts?

Summary Answer: No difference was observed between FPS- and LPS-derived euploid blastocysts after vitrified-warmed single embryo transfer (SET).

What Is Known Already: Technical improvements in IVF allow the implementation non-conventional controlled ovarian stimulation (COS) protocols for oncologic and poor prognosis patients. One of these protocols begins LPS 5 days after FPS is ended (DuoStim). Although, several studies have reported similar embryological outcomes (e.g. fertilization, blastulation, euploidy) between FPS- and LPS-derived cohort of oocytes, information on the reproductive (clinical, obstetric and perinatal) outcomes of LPS-derived blastocysts is limited to small and retrospective studies.

Study Design, Size, Duration: Multicenter study conducted between October 2015 and March 2019 including all vitrified-warmed euploid single blastocyst transfers after DuoStim. Only first transfers of good quality blastocysts (≥BB according to Gardner and Schoolcraft's classification) were included. If euploid blastocysts obtained after both FPS and LPS were available the embryo to transfer was chosen blindly. The primary outcome was the live birth rate (LBR) per vitrified-warmed single euploid blastocyst transfer in the two groups. To achieve 80% power (α = 0.05) to rule-out a 15% difference in the LBR, a total of 366 first transfers were required. Every other clinical, as well as obstetric and perinatal outcomes, were recorded.

Participants/materials, Setting, Methods: Throughout the study period, 827 patients concluded a DuoStim cycle and among them, 339 did not identify any transferable blastocyst, 145 had an euploid blastocyst after FPS, 186 after LPS and 157 after both FPS and LPS. Fifty transfers of poor quality euploid blastocysts were excluded and 49 patients did not undergo an embryo transfer during the study period. Thus, 389 patients had a vitrified-warmed SET of a good quality euploid blastocyst (182 after FPS and 207 after LPS). For 126 cases (32%) where both FPS- and LPS-derived good quality blastocysts were available, the embryo transferred was chosen blindly with a 'True Random Number Generator' function where '0' stood for FPS-derived euploid blastocysts and '1' for LPS-derived ones (n = 70 and 56, respectively) on the website random.org. All embryos were obtained with the same ovarian stimulation protocol in FPS and LPS (GnRH antagonist protocol with fixed dose of rec-FSH plus rec-LH and GnRH-agonist trigger), culture conditions (continuous culture in a humidified atmosphere with 37°C, 6% CO2 and 5% O2) and laboratory protocols (ICSI, trophectoderm biopsy in Day 5-7 without assisted hatching in Day 3, vitrification and comprehensive chromosome testing). The women whose embryos were included had similar age (FPS: 38.5 ± 3.1 and LPS: 38.5 ± 3.2 years), prevalence of male factor, antral follicle count, basal hormonal characteristics, main cause of infertility and previous reproductive history (i.e. previous live births, miscarriages and implantation failures) whether the embryo came from FPS or LPS. All transfers were conducted after warming in an artificial cycle. The blastocysts transferred after FPS and LPS were similar in terms of day of full-development and morphological quality.

Main Results And The Role Of Chance: The positive pregnancy test rates for FPS- and LPS-derived euploid blastocysts were 57% and 62%, biochemical pregnancy loss rates were 10% and 8%, miscarriage rates were 15% and 14% and LBRs were 44% (n = 80/182, 95% CI 37-51%) and 49% (n = 102/207, 95% CI 42-56%; P = 0.3), respectively. The overall odds ratio for live birth (LPS vs FPS (reference)) adjusted for day of blastocyst development and quality, was 1.3, 95% CI 0.8-2.0, P = 0.2. Among patients with euploid blastocysts obtained following both FPS and LPS, the LBRs were also similar (53% (n = 37/70, 95% CI 41-65%) and 48% (n = 27/56, 95% CI 35-62%) respectively; P = 0.7). Gestational issues were experienced by 7.5% of pregnant women after FPS- and 10% of women following LPS-derived euploid single blastocyst transfer. Perinatal issues were reported in 5% and 0% of the FPS- and LPS-derived newborns, respectively. The gestational weeks and birthweight were similar in the two groups. A 5% pre-term delivery rate was reported in both groups. A low birthweight was registered in 2.5% and 5% of the newborns, while 4% and 7% showed high birthweight, in FPS- and LPS-derived euploid blastocyst, respectively. Encompassing the 81 FPS-derived newborns, a total of 9% were small and 11% large for gestational age. Among the 102 LPS-derived newborns, 8% were small and 6% large for gestational age. No significant difference was reported for all these comparisons.

Limitations, Reasons For Caution: The LPS-derived blastocysts were all obtained after FPS in a DuoStim protocol. Therefore, studies are required with LPS-only, late-FPS and random start approaches. The study is powered to assess differences in the LBR per embryo transfer, therefore obstetric and perinatal outcomes should be considered observational. Although prospective, the study was not registered.

Wider Implications Of The Findings: This study represents a further backing of the safety of non-conventional COS protocols. Therefore, LPS after FPS (DuoStim protocol) is confirmed a feasible and efficient approach also from clinical, obstetric and perinatal perspectives, targeted at patients who need to reach the transfer of an euploid blastocyst in the shortest timeframe possible due to reasons such as cancer, advanced maternal age and/or reduced ovarian reserve and poor ovarian response.

Study Funding/competing Interest(s): None.

Trial Registration Number: N/A.

Download full-text PDF

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

Publication Analysis

Top Keywords

euploid blastocysts
28
obstetric perinatal
24
fps- lps-derived
24
fps lps
24
lps-derived euploid
20
euploid blastocyst
20
clinical obstetric
16
perinatal outcomes
16
embryo transfer
16
euploid
15

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!