← Clinical Trials
Infertility Phase 3 Continuous Endpoint NCT02047227

Phase 3 Study to Evaluate the Efficacy and Safety of Pergoveris® in Assisted Reproductive Technology (ESPART): Complete Statistical Analysis

The registry record describes a randomized Phase 3 comparison of Pergoveris and GONAL-f in poor ovarian responders undergoing assisted reproductive technology treatment. The primary outcome was the mean number of oocytes retrieved; pregnancy outcomes and safety are also described.

Trial start: 2014-01-31  ·  Enrollment: 939  ·  Sponsor: Merck KGaA, Darmstadt, Germany
Scope of this record

This page provides an independent statistical analysis and educational interpretation of publicly reported results. ClinicalTrials.gov provides the official trial registry record. Numerical trial results on this page are restricted to the results posted in the ClinicalTrials.gov record; calculations added by Clinical Biostats are labelled as such.

1. Trial at a Glance

This page covers the registry results for Phase 3 Study to Evaluate the Efficacy and Safety of Pergoveris® in Assisted Reproductive Technology (ESPART) (NCT02047227), a randomized phase 3 study. The primary outcome is Number of Oocytes Retrieved.

939
Enrollment
Phase 3
2
Arms
In the primary outcome
0.30
Mean difference
GONAL-f
-0.05–0.65
95% CI
Two-sided
FeatureRegistry value
ClinicalTrials.gov identifierNCT02047227
PhasePhase 3
ConditionInfertility
AllocationRandomized
Design modelParallel
MaskingSingle
Enrollment939
Arms in the primary outcome2
Lead sponsorMerck KGaA, Darmstadt, Germany
Results postedYes

2. Clinical Question

Population

The trial concerned poor ovarian responders undergoing an assisted reproductive technology treatment cycle. The registry describes this population as aligned with the European Society of Human Reproduction and Embryology criteria, referring to the 2011 Consensus Meeting. The primary analysis population was the intent-to-treat set: randomized subjects who received at least 1 dose of GONAL-f or Pergoveris.

Intervention

The intervention was Pergoveris®, described in the registry as follitropin alfa and lutropin alfa. The study assessed its use for multifollicular development as part of an assisted reproductive technology treatment cycle. Recombinant human chorionic gonadotrophin was also listed as a drug intervention; the registry record does not describe its arm-specific administration in detail.

Comparator

The comparator was GONAL-f®, described as follitropin alfa. The trial was randomized, controlled, single-blind, multicentre and parallel-arm. The registry record does not give additional detail about who was blinded or how blinding was maintained.

Primary question

The primary outcome was the mean number of oocytes retrieved at ovum pick up, approximately 34 to 38 hours after r-hCG administration (Day 113). The statistical question is whether the observed outcome distributions differ between the two randomized groups. This outcome reflects ovarian response during treatment; it is not itself a pregnancy or live-birth outcome.

The trial therefore addresses a specific treatment-cycle question in the registry-defined population, rather than a general comparison for all people receiving assisted reproductive technology. Its primary endpoint concerns the number of oocytes obtained, while ongoing pregnancy, live birth, clinical pregnancy, biochemical pregnancy and embryo implantation are listed as secondary outcomes. Results are posted for some, but not all, of those secondary measures.

3. Trial Design

The registry identifies this as a Phase 3, randomized, controlled, single-blind, multicentre, parallel-arm study. It compared Pergoveris with GONAL-f for multifollicular development in poor ovarian responders receiving an assisted reproductive technology treatment cycle. The record lists overall enrollment as 939 and marks the study as completed. The study start is listed as 2014-01-31 and primary completion as 2015-08-31.

The posted primary-outcome groups include 462 participants assigned to Pergoveris and 477 assigned to GONAL-f. The primary analysis population is described as the intent-to-treat set, including all randomized subjects who received at least 1 dose of either study treatment. That definition is narrower than simply “all randomized”: subjects who did not receive a dose are not included under the registry’s stated definition. The record does not explain how many, if any, randomized subjects were excluded under that condition.

Random allocation is a design feature intended to make the treatment groups comparable on average before treatment, including with respect to characteristics that may not have been measured. It does not guarantee identical groups in a particular trial. The registry does not report the sequence-generation procedure, allocation concealment, stratification factors, or details of the single-blind arrangement. The term multicentre is reported, but the number and locations of participating centres are not reported in the registry record.

The study’s sponsor is Merck KGaA, Darmstadt, Germany. The registry gives the primary endpoint and its analysis population, but the full protocol and the trial’s original sample-size rationale are not reported in the registry record. The known planning assumptions accompanying the posted sample-size illustrations are distinct from those original design assumptions.

4. Participant Flow and Accounting

The registry reports how participants moved through each stage of the study. All counts below are exactly as posted; missing counts are not inferred from other stages.

Overall Study

StagePergoverisGONAL-f
STARTED462477
Completed Ovarian Stimulation Phase424440
COMPLETED318347
NOT COMPLETED144130

Reasons for not completing this period:

ReasonPergoverisGONAL-f
Adverse Event24
Lost to Follow-up03
Protocol Violation10
Spontaneous pregnancy10
Lack of ovarian response to stimulation3532
No oocytes retrieved2120
No fertilization6151
Intention to freeze all embryos10
All embryos discarded1211
Other109

Analysis population for the primary outcome, as defined in the registry: Intent-to-treat (ITT) analysis set included all subjects randomized who received at least 1 dose of GONAL-f or Pergoveris.

5. Baseline Characteristics

The table reproduces the baseline characteristics posted in the registry, which describe the participants analysed at baseline and help show whether the randomized groups were comparable.

Population: All Randomized Subjects Set included all subjects who were randomized.

CharacteristicUnitPergoverisGONAL-fTotal
Participants analysed462477939
Age, Continuousyears38.3 (SD 2.9)38.3 (SD 3.0)38.3 (SD 3.0)
Sex: Female, Male: FemaleParticipants462477939
Sex: Female, Male: MaleParticipants000

6. Primary Endpoint

The registry lists the primary outcome as Number of Oocytes Retrieved, measured over At approximately 34 to 38 hours after r-hCG administration (Day 113).

ElementRegistry entry
Result typeMean
Measure of spreadStandard Deviation
Unitoocytes
Endpoint classificationContinuous Endpoint

The primary endpoint is the number of oocytes retrieved, summarized as a mean and standard deviation for each treatment group. The registry defines the measurement as the mean number retrieved on the day of ovum pick up. It gives the timeframe as approximately 34 to 38 hours after r-hCG administration (Day 113). Oocyte retrieval is described as a technique used in in-vitro fertilization to remove oocytes from the ovary so that fertilization can occur outside the body.

As a general statistical explanation, a count of retrieved oocytes is a direct measure of ovarian response during the treatment cycle. Comparing group means gives a compact summary of the average count, while the standard deviation describes how widely individual counts vary around each group mean. Neither summary shows the full distribution of counts or how many participants had a particular value.

This endpoint is used to assess multifollicular development, the treatment objective named in the trial description. It is an intermediate treatment-cycle outcome, not a direct measure of whether a pregnancy continued or resulted in a live birth. Those later outcomes are listed separately as secondary endpoints, and the registry reports some of them independently. A difference in the mean number of retrieved oocytes should therefore be interpreted as a difference in the measured retrieval outcome, not as proof of a difference in pregnancy or live-birth outcomes.

7. Results Posted in the Registry

Mean difference: GONAL-f

0.30

95% CI: -0.05 to 0.65

Recalculated from the posted summary statistics

Primary outcome by arm, with 95% confidence intervals
Primary outcome by arm with 95% confidence intervals3.03.23.43.53.73.9Pergoveris (n=462)GONAL-f (n=477)oocytes (95% CI)
Treatment effect versus the control arm
Forest plot of mean difference vs control (95% CI)GONAL-f-0.110.050.220.380.550.71mean difference vs control (95% CI)

8. Secondary Efficacy Endpoints

The registry also posts results for secondary outcomes. For each outcome below, the endpoint type, the test applied to the posted summary statistics, the result and its interpretation are given in turn. Secondary endpoints are usually not adjusted for multiple testing, so they support rather than confirm the primary finding.

Secondary outcomeTypeEffect measureEstimate (95% CI)Planning size, 80% power
Ongoing Pregnancy RateBinary EndpointRisk difference+1.3 pts (-2.8 to 5.4)9,170 per arm
Live Birth RateBinary EndpointRisk difference+1.1 pts (-2.9 to 5.2)12,115 per arm
Clinical Pregnancy RateBinary EndpointRisk difference+2.7 pts (-1.9 to 7.3)2,803 per arm

Ongoing Pregnancy Rate

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)GONAL-f-3.44-1.530.382.284.196.10risk difference (percentage points) vs control (95% CI)

Live Birth Rate

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)GONAL-f-3.54-1.670.202.073.945.81risk difference (percentage points) vs control (95% CI)

Clinical Pregnancy Rate

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)GONAL-f-2.65-0.511.633.775.918.06risk difference (percentage points) vs control (95% CI)

The posted secondary results show a broadly consistent descriptive pattern: the recorded rates are numerically higher in the GONAL-f group for the pregnancy outcomes with results posted. That direction is also consistent with the direction of the observed primary group means, but the outcomes measure different stages of the treatment pathway. The primary endpoint is oocyte retrieval, whereas the secondary outcomes concern pregnancy or birth. A pattern across different endpoints does not by itself show that a difference in retrieval translates into a difference in later outcomes.

The recalculated unadjusted confidence intervals for ongoing pregnancy, live birth and clinical pregnancy each include zero for the risk difference. The corresponding unadjusted p-values do not establish a clear difference between groups. These analyses therefore describe uncertain comparisons, not proof that the groups have the same outcomes. The registry lists embryo implantation and biochemical pregnancy among the secondary outcomes, but results for those measures are not reported in the registry record.

Unadjusted secondary results generally carry less weight than a prespecified primary analysis when many outcomes are examined. As a general statistical explanation, testing multiple outcomes increases the chance that at least one result appears notable by chance if no adjustment or hierarchy is used. The registry record does not report a multiplicity adjustment, a testing hierarchy, or a plan specifying which secondary outcomes were confirmatory. The reported secondary p-values should therefore be read as unadjusted comparisons, not as independent confirmation of the primary result.

The primary and secondary measures also differ in timing and clinical meaning. The registry specifies distinct follow-up timeframes for the pregnancy outcomes, and outcomes later in the treatment pathway are not interchangeable with the retrieval count. Their joint pattern can help describe the trial results, but it does not remove uncertainty in any individual comparison or substitute for a documented analysis plan.

Secondary outcomes registered for this trial, for reference (only those above were recalculated):

9. Statistical Interpretation

Clinical Biostats interpretation

The posted group means for the primary outcome are 3.3 oocytes for Pergoveris and 3.6 for GONAL-f. The corresponding standard deviations are 2.71 and 2.82. These summaries show that the observed average was numerically higher in the GONAL-f group, while there was substantial variation among participants in both groups. The unadjusted recalculation gives a mean difference of 0.3 for GONAL-f versus Pergoveris, with a 95% confidence interval from -0.054 to 0.654 and p = 0.096.

The recalculated interval includes zero, so it is compatible with no difference in the group means as well as with differences in either direction within the interval. The unadjusted p-value does not provide strong evidence against a null difference under that calculation. This is an inferential statement about the data and calculation, not a conclusion that the treatments are equivalent. Establishing equivalence or non-inferiority would require a prespecified margin and an analysis designed for that purpose; such a margin is not reported in the registry record.

The registry also reports a Poisson regression analysis, with a net mean difference of -0.235, a 95% confidence interval from -0.474 to 0.003, and p = 0.054. That is a model-based result, not the same estimand and method as the simple unadjusted recalculation. The registry does not explain the model’s contrast coding or provide enough detail to reconcile the sign with the raw group means. Its confidence interval reaches across zero, and the reported p-value is close to, but above, the conventional 0.05 threshold specified in the planning illustration. Neither the closeness of a p-value to a threshold nor a numerical direction alone establishes a clinically meaningful effect.

The primary endpoint is a count outcome, but the posted group summaries and the recalculation describe it through means and a mean difference. A mean comparison can be useful for communicating average response, yet it does not describe how many participants had no retrieved oocytes, how skewed the counts were, or whether a small number of large counts influenced the means. Those distributional details are not reported in the registry record.

The results should be read alongside the endpoint’s scope and the analysis population. The primary comparison concerns the mean number of oocytes retrieved among the registry-defined intent-to-treat population. It is not a comparison of treatment success in every possible sense, and it does not establish a treatment effect on later pregnancy outcomes. Those outcomes are secondary, have their own uncertainty, and should not be treated as interchangeable with the primary measure.

10. Statistical Methods Explained

The posted evidence includes group means and standard deviations, an unadjusted recalculation of the mean difference, and a sponsor-reported regression analysis. These are related summaries, but they do not answer precisely the same statistical question. The unadjusted result is calculated from the posted group summaries; the regression result is the analysis reported by the registry. The registry does not provide the full statistical analysis plan or enough model details to reproduce that regression.

What does a mean difference describe?

As a general statistical explanation, a group mean is the arithmetic average of participants’ outcome values. The mean difference compares those averages in a stated direction. In the recalculation, the stated contrast is GONAL-f versus Pergoveris, and the estimate is 0.3 oocytes. A positive value in that contrast means the observed mean is higher in the GONAL-f group. This is a summary of observed group averages; it is not an estimate adjusted for participant characteristics or centre unless such adjustment is explicitly part of the method.

The standard deviations, 2.71 for Pergoveris and 2.82 for GONAL-f, describe the spread of participant outcomes within their respective groups. Standard deviation is not the same as the uncertainty in a group mean. The uncertainty of a mean difference also depends on the amount of information in each group and on the variability of the outcome. The recalculation reports standard errors of 0.126 and 0.129 for the respective group means, and a pooled standard deviation of 2.766 for the comparison.

How should the confidence interval be read?

As a general explanation, a confidence interval expresses the sampling uncertainty around an estimate under the method used to construct it. The recalculated 95% interval for the mean difference extends from -0.054 to 0.654. Because the interval includes zero, the results do not rule out a zero mean difference under that calculation. The interval also includes nonzero differences in either direction. It is not a probability statement that the true effect has a 95% chance of lying within these particular endpoints; rather, the confidence level describes the long-run behavior of the interval procedure under its assumptions.

The interval is unadjusted and based on posted summary statistics. It does not incorporate an adjustment for multiple outcomes or covariates. The registry’s own interval is based on its Poisson regression model and therefore reflects that model’s analysis rather than the simple summary-statistic calculation. The registry does not report the regression specification, covariates, model diagnostics, or the precise contrast coding.

Why use a Poisson regression for this outcome?

As a general statistical explanation, Poisson regression is commonly used for count outcomes and relates the expected count to predictors through a model. Depending on the specification, such a model can estimate a treatment contrast while accounting for covariates. The registry reports a Poisson Regression Model and labels its parameter as a net mean difference. It does not report which covariates were included or whether the model included other adjustments, so those features should not be assumed.

As a general point, count data may show greater variability than a basic Poisson model allows, a condition often called over-dispersion. If the model’s variance assumptions do not match the data, standard errors and confidence intervals can be affected. The registry record does not report a diagnostic assessment of over-dispersion, an alternative variance method, or the distributional checks performed. This is a question about model assessment, not evidence that over-dispersion did or did not occur in this trial.

What does the p-value contribute?

As a general explanation, a p-value measures how unusual data at least as inconsistent with a specified null model would be if that null model and the analysis assumptions were correct. It is not the probability that the null hypothesis is true, nor does it measure the size or clinical importance of a difference. The unadjusted recalculation reports p = 0.096; the regression analysis reports p = 0.054. Their difference is expected to be possible when methods and estimands differ. The registry does not describe whether the reported model was prespecified in the analysis plan.

The primary outcome is accompanied by a single reported analysis in the registry record. A count of analyses in the registry does not establish how many analyses were planned in the protocol or whether any were conducted but not reported. That information is not reported in the registry record.

Why do analysis populations matter?

The registry defines the primary intent-to-treat analysis set as all randomized subjects who received at least 1 dose of GONAL-f or Pergoveris. In general, an intent-to-treat approach aims to preserve the comparison created by random allocation, while the exact definition used in practice matters for deciding who is included. Because the posted definition includes a treatment-receipt condition, it should be read as written rather than assumed to include every randomized participant. The handling of missing primary endpoint values and any additional analysis populations are not reported in the registry record.

11. Confidence Intervals and Precision

The primary recalculation estimates a mean difference of 0.3 oocytes, with a 95% confidence interval from -0.054 to 0.654. The interval is informative because it gives a range of values compatible with the data under the calculation’s assumptions, rather than presenting the point estimate alone. It includes zero and extends to values on both sides of zero. Thus, the observed data do not precisely establish the direction of a mean difference in the population.

The group standard deviations, 2.71 for Pergoveris and 2.82 for GONAL-f, are large relative to the observed separation between the group means. As a general statistical explanation, substantial within-group variability makes group averages less distinct and can widen uncertainty around comparisons. The posted standard errors for the group means are 0.126 and 0.129. They describe uncertainty in the estimated means, not the spread of individual outcomes.

The model-reported estimate is -0.235, with a 95% confidence interval from -0.474 to 0.003. Its interval also reaches across zero, although it is based on a different method and parameter label from the unadjusted recalculation. The registry does not explain the model contrast coding, so the two estimates should not be treated as directly interchangeable or their signs compared without qualification.

Precision is distinct from clinical importance. A confidence interval can describe statistical uncertainty, but the registry does not report a threshold for a clinically important difference in the number of oocytes. It also does not report the original sample-size justification. Therefore, the interval should be used to understand the range of estimates compatible with the analysis, not to declare equivalence or a clinically meaningful benefit.

12. Planning a Similar Trial: Sample Size

This is a planning illustration, not a re-evaluation of the original trial. It asks: if a new study wanted to detect a difference like the one observed, or a smaller one, how large would it need to be? It is deliberately not “observed power” of the finished trial, which is not a meaningful quantity.

Effect to detectParticipants per arm, 80% powerParticipants per arm, 90% power
100% of the observed effect1,3351,787
75% of the observed effect2,3743,177
50% of the observed effect5,3407,148
Sample size needed versus the size of the effect to detect
Sample size needed versus size of effect to detect1,0002,0005,00010,00020,00040%60%80%100%80% power90% powersize of effect to detect, as % of the effect observed (log vertical scale: participants per arm)
Treat these figures cautiously. The observed difference is imprecise: its confidence interval includes no difference at all. A sample size built on a noisy estimate can be far too small or too large, so the smaller-effect rows are the more cautious guide.
Method and assumptions. Two-sided α = 0.05, 1:1 allocation, two-sample comparison of means with the pooled standard deviation. Calculated for the comparison: GONAL-f.

The sample-size illustrations are planning calculations based on the observed effect, not the original design rationale for this trial. The stated assumptions are a two-sided significance level of 0.05, equal allocation between the two arms, and a normal approximation. Each planning row considers detecting the stated fraction of the observed effect. The trial’s own original sample-size assumptions are not reported in the registry record.

For the primary continuous outcome, the listed figures are participants per arm. The 80% power column describes the number of participants per arm that the planning calculation estimates would be needed to have an 80% chance of detecting the specified effect under the stated assumptions, if that effect and those assumptions were correct. The 90% power column describes the corresponding planning target for a 90% chance. They are planning targets, not descriptions of the trial’s observed results.

The rows consider 100% of the observed effect, 75% of the observed effect, and 50% of the observed effect. Smaller effects are harder to distinguish from random variation, so the planning calculations require more participants to detect them at the same stated power. The values are illustrations rather than a retrospective claim about what the trial could detect in practice. This is not observed power.

The assumptions used for the illustration do not establish that the original investigators chose the same significance level, allocation, model, or target effect. The protocol’s sample-size calculation and any allowances for missing outcomes are not reported in the registry record. For these primary and posted secondary outcome calculations, the figures are participants per arm, not total event counts.

13. How the Sample Size Is Derived

Power is the probability that a study of a given size rejects the null hypothesis when a specific true effect exists. It depends on four things: the effect to detect, the variability of the outcome, the significance level (here a two-sided α of 0.05, so z1−α/2 = 1.960) and the desired power (z1−β = 0.842 for 80% and 1.282 for 90%).

Formula

n = 2 (z1−α/2 + z1−β)2 σ2 / Δ2

n is the number of participants in each arm, Δ is the difference in means to detect and σ is the common standard deviation.

Worked calculation for this trial

  1. Observed difference Δ = 0.300; pooled standard deviation σ = 2.766.
  2. n = 2 × (1.96 + 0.842)2 × 2.7662 / 0.3002 = 1,334.9, rounded up to 1,335 participants per arm for 80% power.

The smaller-effect rows in the table above repeat the same calculation with the effect multiplied by 0.75 and 0.5 (for ratios, applied to the logarithm of the ratio).

R code

alpha <- 0.05
z_a   <- qnorm(1 - alpha / 2)          # two-sided
delta <- 0.3                      # observed difference in means
sigma <- 2.76642711756487                     # pooled standard deviation
n_per_arm <- function(power, frac = 1) {
  ceiling(round(2 * (z_a + qnorm(power))^2 * sigma^2 / (delta * frac)^2, 6))
}
for (f in c(1, 0.75, 0.5))
  cat(sprintf("%3.0f%% of observed effect: n per arm = %s (80%% power), %s (90%% power)\n", 100 * f,
              format(n_per_arm(0.80, f), big.mark = ","), format(n_per_arm(0.90, f), big.mark = ",")))

# Check against R's built-in function (t-based, so very slightly larger)
cat("power.t.test:", round(power.t.test(delta = delta, sd = sigma, power = 0.80)$n, 1), "\n")

# Simulation: exact two-sample t-test using simulated means and variances
set.seed(2047227)
n    <- n_per_arm(0.80)
reps <- 20000
m_diff <- rnorm(reps, delta, sigma * sqrt(2 / n))             # difference in sample means
s2     <- sigma^2 * rchisq(reps, 2 * (n - 1)) / (2 * (n - 1))   # pooled sample variance
tstat  <- m_diff / sqrt(s2 * 2 / n)
cat(sprintf("Simulated power at n = %s per arm: %.3f (%d replicates)\n", format(n, big.mark = ","), mean(abs(tstat) > qt(0.975, 2 * (n - 1))), reps))

Output from running the code

100% of observed effect: n per arm = 1,335 (80% power), 1,787 (90% power)
 75% of observed effect: n per arm = 2,374 (80% power), 3,177 (90% power)
 50% of observed effect: n per arm = 5,340 (80% power), 7,148 (90% power)
power.t.test: 1335.8 
Simulated power at n = 1,335 per arm: 0.798 (20000 replicates)

The simulation draws many sets of group means and variances at the planned sample size and counts how often the two-sample t-test rejects the null. It should land close to the target power; at very small required sample sizes it can fall below it, because the normal approximation is rough there.

14. Analyses Reported by the Sponsor

MethodEstimate95% CIP-value
Poisson Regression ModelMean Difference (Net) -0.235-0.4741 to 0.0030.054

The registry reports a Poisson regression analysis for the primary outcome: a net mean difference of -0.235, a 95% confidence interval from -0.474 to 0.003, and p = 0.054. The separate recalculation from the posted group summaries is unadjusted: it estimates a mean difference of 0.3 for GONAL-f versus Pergoveris, with a 95% confidence interval from -0.054 to 0.654 and p = 0.096.

These results should be kept distinct. The recalculation compares the posted group summaries without the reported regression model; the registry analysis uses Poisson regression and labels its parameter a net mean difference. The registry record does not specify model covariates or contrast coding, so it does not establish exactly why the estimates differ in sign or magnitude. They should not be combined into a single estimate or treated as duplicate calculations of an identical estimand.

The registry record does not flag a discrepancy between the posted result and the recalculation. The sponsor’s reported analysis remains the trial’s own model-based result; the recalculation is a simple unadjusted check based on summary data, not a replacement for the trial analysis. Neither result alone demonstrates equivalence, and both confidence intervals include zero.

15. Multiplicity, Missing Data and Analysis Populations

The registry record identifies a primary endpoint and lists secondary outcomes, but it does not report a multiplicity strategy. In particular, no adjustment method, testing hierarchy, or distinction between confirmatory and exploratory secondary analyses is reported in the registry record. The posted secondary comparisons are unadjusted. When several outcomes are tested, the chance of at least one apparently unusual result can increase; that is a general statistical concern, not a claim that any particular result in this trial is spurious.

The primary analysis population is defined as the intent-to-treat set of randomized subjects who received at least 1 dose of GONAL-f or Pergoveris. The registry does not report the number of randomized subjects excluded from that definition, whether all included subjects had primary outcome data, or how missing outcome values were handled. Imputation, sensitivity analyses for missing data, and additional analysis populations are not reported in the registry record.

The registry describes the trial as randomized, single-blind and multicentre, but it does not give the randomization sequence method, allocation concealment procedures, or details about who was blinded. It also does not report whether outcome assessors were blinded or whether the blind was maintained throughout follow-up. These omissions limit assessment of potential bias beyond what can be inferred from the design labels.

The sponsor-reported Poisson regression result is presented without a full model specification. Covariates, model diagnostics, handling of over-dispersion, and the exact contrast coding are not reported in the registry record. The registry also does not report interim analyses, stopping rules, protocol deviations, or the statistical analysis plan. Their absence from the registry description should not be interpreted as evidence that they were or were not part of the trial; they are simply not reported in the registry record.

16. Safety Results

The registry reports serious adverse events as affected participants divided by participants at risk.

ArmParticipants with serious adverse eventsParticipants at riskPercentage
Pergoveris84621.7%
GONAL-f174773.6%
Participants with at least one serious adverse event
Serious adverse events by armPergoveris1.7%GONAL-f3.6%% of participants with at least one serious adverse event

Other (non-serious) adverse events

Participants with at least one non-serious event at or above the registry's 0% reporting threshold.

ArmParticipants affected of at risk
Pergoveris111 of 462
GONAL-f151 of 477

Most frequent serious adverse event terms

Event termOrgan systemPergoverisGONAL-f
Abortion missedPregnancy, puerperium and perinatal conditions1 of 4623 of 477
AbortionPregnancy, puerperium and perinatal conditions0 of 4622 of 477
Abortion spontaneousPregnancy, puerperium and perinatal conditions1 of 4621 of 477
Premature labourPregnancy, puerperium and perinatal conditions1 of 4621 of 477
Ectopic pregnancyPregnancy, puerperium and perinatal conditions0 of 4621 of 477
Foetal deathPregnancy, puerperium and perinatal conditions0 of 4621 of 477
Hyperemesis gravidarumPregnancy, puerperium and perinatal conditions0 of 4621 of 477
Imminent abortionPregnancy, puerperium and perinatal conditions1 of 4620 of 477
Premature babyPregnancy, puerperium and perinatal conditions1 of 4620 of 477
Premature deliveryPregnancy, puerperium and perinatal conditions1 of 4620 of 477

Most frequent non-serious adverse event terms

Event termOrgan systemPergoverisGONAL-f
HeadacheNervous system disorders46 of 46258 of 477
Hot flushVascular disorders19 of 46210 of 477
NauseaGastrointestinal disorders15 of 46212 of 477
Abdominal painGastrointestinal disorders12 of 46213 of 477
Abortion spontaneousPregnancy, puerperium and perinatal conditions6 of 46212 of 477
DizzinessNervous system disorders4 of 4628 of 477
DysmenorrhoeaReproductive system and breast disorders6 of 4626 of 477
DiarrhoeaGastrointestinal disorders4 of 4627 of 477
Abdominal pain lowerGastrointestinal disorders5 of 4625 of 477
Back painMusculoskeletal and connective tissue disorders4 of 4626 of 477

Serious events with the highest arm-level rate: abortion missed (0.6%), abortion (0.4%), abortion spontaneous (0.2%), premature labour (0.2%), imminent abortion (0.2%).

Do not overextend the safety comparison. Serious-adverse-event counts are safety observations, not efficacy outcomes, and should not be combined with the primary result into a single benefit-risk number.

The registry reports serious adverse events for 8 of 462 participants in the Pergoveris group and 17 of 477 in the GONAL-f group. It also reports other adverse events for 111 of 462 and 151 of 477, respectively. These are counts in the posted safety record; they should be read as descriptive event summaries rather than as proof that treatment caused or prevented an event. The registry does not provide an adjusted comparative safety analysis in the record.

The listed serious-event terms and percentages are Abortion missed (0.6%), Abortion (0.4%), Abortion spontaneous (0.2%), Premature labour (0.2%), Imminent abortion (0.2%) and Premature baby (0.2%). The record does not give enough detail in these listings to determine the group-specific distribution of each term, the number of recurrent events, or the relationship of each event to treatment. The terms should not be interpreted as causal findings.

Deaths are not reported in the registry record. The adverse-event figures do not by themselves provide information about severity beyond the serious-event classification, duration, resolution, or exposure-adjusted rates. Those details are not reported in the registry record.

17. What the Result Does, and Does Not, Mean

The results describe a randomized comparison of Pergoveris and GONAL-f in poor ovarian responders receiving assisted reproductive technology treatment. For the primary outcome, the observed mean number of oocytes retrieved was numerically higher in the GONAL-f group. The unadjusted recalculation has a confidence interval that includes zero, and the registry’s Poisson regression result also has a confidence interval reaching across zero. These findings leave uncertainty about the direction and size of a population mean difference.

This does not establish that the treatments are equivalent, nor does it establish that one treatment is better. A failure to rule out zero is not proof of no difference. Equivalence would require a prespecified margin and an appropriate analysis; such a margin is not reported in the registry record. The observed means and model estimate also do not, on their own, determine whether a difference would matter clinically, because a threshold for clinical importance is not reported.

The primary endpoint measures oocyte retrieval, not pregnancy or live birth. The registry posts several later pregnancy outcomes, but their comparisons also remain uncertain and they are secondary outcomes. A result on oocyte count should not be treated as a substitute for a result on pregnancy or birth, and a descriptive pattern across endpoints does not establish a causal pathway.

The safety counts provide a summary of reported events in each group, not a complete account of risk or evidence that a treatment caused a particular event. The registry record does not report deaths, detailed event-level follow-up, or a comparative safety model. Interpretation is further limited by missing information on missing-data handling, multiplicity, regression specification and the trial’s original sample-size rationale.

The appropriate conclusion is bounded: the registry reports the observed group summaries and its own model-based analysis, while the unadjusted recalculation offers a transparent comparison of those summaries. Together they show uncertain estimates rather than a definitive separation between treatments on the primary endpoint.

18. Why This Trial Matters Statistically

This trial illustrates why a reported point estimate should not be read in isolation. The raw group means and the simple unadjusted comparison offer one view of the primary outcome, while the registry’s Poisson regression offers a model-based view. Because the registry does not give enough detail to align the model’s contrast coding and specification with the recalculation, the methods should be described separately rather than blended into a single result.

It also demonstrates the distinction between statistical evidence and clinical importance. Confidence intervals describe uncertainty, and p-values summarize compatibility with a null model under stated assumptions; neither determines whether a difference matters to patients or clinicians. The registry does not report a clinically important threshold for oocyte counts, so interpretation should remain tied to the measured outcome and the uncertainty around it.

The trial’s outcome sequence is statistically important as well. Oocyte retrieval is an early treatment-cycle measure, while pregnancy and birth are later outcomes. Their numerical patterns may be considered together, but they address different questions and should not be substituted for one another. The secondary results are unadjusted, and the registry does not document how multiple comparisons were handled.

Finally, registry transparency affects how confidently an analysis can be evaluated. The record identifies the primary population and reports an analysis method, but it does not give the original sample-size rationale, detailed model specification, missing-data methods, or multiplicity plan. Recognizing these limits is part of interpreting the reported estimates; it is not a reason to disregard the data that are posted.

19. Limitations

Several limitations specific to this registry record constrain interpretation. The participant group is described as poor ovarian responders aligned with ESHRE criteria, but detailed eligibility rules and the number of participating centres are not reported in the registry record. Randomization, single blinding and multicentre conduct are stated, while the sequence-generation method, concealment procedures and details of who was blinded are not reported.

The registry defines the primary analysis set as randomized subjects who received at least 1 dose of either treatment. It does not report whether any randomized subjects were outside this set, the extent of missing primary endpoint data, or how missing values were handled. Other analysis populations and sensitivity analyses are not reported in the registry record.

The sponsor-reported model is identified as Poisson regression, but its covariates, diagnostics, variance specification and contrast coding are not described. This limits direct comparison with the unadjusted mean-difference recalculation. The record does not report the trial’s original sample-size assumptions, a clinically important effect threshold, or the basis for the chosen enrollment target.

Several secondary outcomes are listed, but results are posted for only some of them. The registry does not describe a multiplicity adjustment or testing hierarchy. Safety summaries give event counts and selected serious-event terms, but not event-level details, exposure-adjusted rates, or deaths; deaths are not reported in the registry record. These limitations concern the available registry information and do not establish that unreported procedures or analyses were absent from the full trial documentation.

20. Related Tutorials

21. Related Statistical Calculators

22. Sources

Continue through the Clinical Biostats statistical pathway

Use this trial's endpoint as a starting point for deeper study of effect measures, confidence intervals, and sample-size planning.

23. Record Summary

The registry record identifies NCT02047227, a completed Phase 3 randomized, controlled, single-blind, multicentre, parallel-arm study sponsored by Merck KGaA, Darmstadt, Germany. It compared Pergoveris with GONAL-f for multifollicular development in poor ovarian responders undergoing assisted reproductive technology treatment. Overall enrollment is listed as 939.

The primary endpoint was the mean number of oocytes retrieved at approximately 34 to 38 hours after r-hCG administration (Day 113), in an intent-to-treat analysis set defined as randomized subjects receiving at least 1 dose. The record reports group means and standard deviations, a Poisson regression analysis, secondary pregnancy outcomes and adverse-event summaries.

The unadjusted recalculation and the registry-reported model result both have confidence intervals that include zero. The record does not report the original sample-size rationale, detailed regression specification, missing-data methods or multiplicity plan. The posted estimates therefore describe the trial results but leave important aspects of analysis and precision uncertain.

Clinical Biostats