MétaCan
Menu
Back to cohort
Record W2145070942 · doi:10.1093/humrep/den210

A 38 h interval between hCG priming and oocyte retrieval increases in vivo and in vitro oocyte maturation rate in programmed IVM cycles

2008· article· en· W2145070942 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHuman Reproduction · 2008
Typearticle
Languageen
FieldMedicine
TopicReproductive Biology and Fertility
Canadian institutionsMcGill UniversityRoyal Victoria Hospital
Fundersnot available
KeywordsOocyteIn vitro maturationAndrologyPolycystic ovaryBiologyPriming (agriculture)In vivoEmbryoEndocrinologyMedicineGenetics

Abstract

fetched live from OpenAlex

BACKGROUND: Our aim was to evaluate whether extending the interval between human chorionic gonadotrophin (hCG) priming and immature oocyte retrieval increases the oocyte maturation rate following in vitro maturation (IVM). METHODS: This study was performed retrospectively. IVM was performed on 113 polycystic ovary syndrome patients (n = 120 cycles). Oocyte collection was performed either 35 h (Group 1; n = 76) or 38 h (Group 2; n = 44) after 10,000 IU of hCG priming. Following oocyte retrieval, oocyte maturity was assessed and the remaining immature oocytes were cultured in IVM medium up to Day 2. RESULTS: The number of in vivo matured oocytes collected was significantly higher in Group 2 (13.6%, 114/840 versus 7.3%, 96/1312 in Group 1) (P < 0.01); the oocyte maturation rate after Day 1 was significantly higher (P < 0.01) in Group 2 (46.3 versus 36.0% in Group 1); and clinical pregnancy (40.9 versus 25%) and implantation rates (15.6 versus 9.6%) were better in Group 2 than those in Group 1. CONCLUSIONS: The results suggest that extending the period of hCG priming time from 35 to 38 h for immature oocyte retrieval promotes oocyte maturation in vivo and increases the IVM rate of immature oocytes. Therefore, oocyte retrieval after 38 h of hCG priming may improve subsequent pregnancy outcome in cycles programmed for IVM treatment.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.344
Threshold uncertainty score0.670

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.050
GPT teacher head0.306
Teacher spread0.256 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it