← Clinical Trials
Type 2 Diabetes Mellitus Phase 3 Binary Endpoint NCT04255433

A Study of Tirzepatide (LY3298176) Compared With Dulaglutide on Major Cardiovascular Events in Participants With Type 2 Diabetes: Complete Statistical Analysis

This analysis examines SURPASS-CVOT, a randomized comparison of tirzepatide and dulaglutide in participants with type 2 diabetes. The primary comparison concerns first occurrence of cardiovascular death, myocardial infarction, or stroke; the posted risk-difference estimate is imprecise and its confidence interval includes no difference.

Trial start: 2020-05-29  ·  Enrollment: 13299  ·  Sponsor: Eli Lilly and Company
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 A Study of Tirzepatide (LY3298176) Compared With Dulaglutide on Major Cardiovascular Events in Participants With Type 2 Diabetes (NCT04255433), a randomized phase 3 study. The primary outcome is Number of Participants From Randomization to First Occurrence of Death From MACE-3 [Composite Endpoint of Major Adverse Cardiovascular Events Death From Cardiovascular Causes, Myocardial Infarction (MI) or Stroke].

13299
Enrollment
Phase 3
2
Arms
In the primary outcome
+0.9 pts
Risk difference
1.5 mg Dulaglutide
-0.2 to 2.1 pts
95% CI
Two-sided
FeatureRegistry value
ClinicalTrials.gov identifierNCT04255433
PhasePhase 3
ConditionType 2 Diabetes Mellitus
AllocationRandomized
Design modelParallel
MaskingDouble
Enrollment13299
Arms in the primary outcome2
Lead sponsorEli Lilly and Company
Results postedYes

2. Clinical Question

Population

Participants with type 2 diabetes and increased cardiovascular risk were eligible. The primary outcome analysis used the modified intention-to-treat population: randomized participants grouped according to their assigned treatment. The registry record does not report further eligibility details or the demographic and clinical profile of the analyzed groups in the results.

Intervention

Participants assigned to tirzepatide began at 2.5 mg once weekly. The dose was escalated by 2.5 mg every 4 weeks to a maximum of 15 mg once weekly, or to a maximum tolerated dose of 5 mg or 10 mg, for up to 5 years.

Comparator

The comparison group received 1.5 mg dulaglutide as a subcutaneous injection once weekly for up to 5 years. The registry describes the study as randomized, double-masked, and parallel-group.

Primary question

Among participants with type 2 diabetes and increased cardiovascular risk, how did the number experiencing a first occurrence of cardiovascular death, myocardial infarction, or stroke differ between those assigned tirzepatide and those assigned dulaglutide? The posted comparison is an unadjusted risk difference, with dulaglutide contrasted against tirzepatide. It describes event counts over follow-up, rather than an adjusted time-to-event effect.

3. Trial Design

SURPASS-CVOT was a phase 3, randomized, double-masked, parallel-group trial sponsored by Eli Lilly and Company. The registry reports enrollment of 13299 and a completed status. The study began on 2020-05-29, and primary completion was recorded as 2025-06-12. The planned treatment period was up to 5 years.

Participants were assigned to tirzepatide or 1.5 mg dulaglutide. Tirzepatide began at 2.5 mg once weekly, with escalation by 2.5 mg every 4 weeks to a maximum of 15 mg weekly or a tolerated dose of 5 mg or 10 mg weekly. Dulaglutide was administered at 1.5 mg once weekly. Both were given by subcutaneous injection. The registry describes the study purpose as assessing the efficacy and safety of tirzepatide compared with dulaglutide in people with type 2 diabetes and increased cardiovascular risk.

The primary analysis population was modified intention-to-treat: all randomized participants grouped according to assigned treatment. The primary outcome was the first occurrence of cardiovascular death, myocardial infarction, or stroke. Follow-up for this outcome is described as from randomization through week 259. Participants without a recorded event were censored at their last known contact or at the end of follow-up.

The registry record does not report the original sample-size justification, the trial’s planned statistical analysis, or details of any interim analyses. It also does not report adjusted treatment-effect estimates in the results. These omissions limit how closely the posted unadjusted comparisons can be connected to the trial’s original inferential plan.

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

StageTirzepatide - Maximum Tolerated Dose (MTD)1.5 mg Dulaglutide
STARTED66486651
Safety Population66476647
Modified Intention-to-Treat (mITT) Population65866579
COMPLETED65246505
NOT COMPLETED124146

Reasons for not completing this period:

ReasonTirzepatide - Maximum Tolerated Dose (MTD)1.5 mg Dulaglutide
Withdrawal by Subject1715
Lost to Follow-up4559
Discontinued due to ''Randomization in Error''6272

Analysis population for the primary outcome, as defined in the registry: Modified Intention-to-treat (mITT) Population included all randomized participants who were grouped according to the treatment assigned at randomization.

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 participants.

CharacteristicUnitTirzepatide (MTD)1.5 mg DulaglutideTotal
Participants analysed6648665113299
Age, Continuousyears64.00 (SD 8.83)64.10 (SD 8.72)64.10 (SD 8.77)
Sex: Female, Male: FemaleParticipants190319463849
Sex: Female, Male: MaleParticipants474547059450
Ethnicity (NIH/OMB): Hispanic or LatinoParticipants200720034010
Ethnicity (NIH/OMB): Not Hispanic or LatinoParticipants432643168642
Ethnicity (NIH/OMB): Unknown or Not ReportedParticipants315332647
Race (NIH/OMB): American Indian or Alaska NativeParticipants489481970
Race (NIH/OMB): AsianParticipants5805901170
Race (NIH/OMB): Native Hawaiian or Other Pacific IslanderParticipants9918
Race (NIH/OMB): Black or African AmericanParticipants111109220
Race (NIH/OMB): WhiteParticipants5349534810697
Race (NIH/OMB): More than one raceParticipants222648
Race (NIH/OMB): Unknown or Not ReportedParticipants8888176
Region of Enrollment: ArgentinaParticipants8128151627
Region of Enrollment: AustraliaParticipants194194388
Region of Enrollment: AustriaParticipants414081
Region of Enrollment: BelgiumParticipants6566131
Region of Enrollment: BrazilParticipants310312622
Region of Enrollment: CanadaParticipants227227454
Region of Enrollment: ChinaParticipants175175350
Region of Enrollment: CzechiaParticipants114113227
Region of Enrollment: FranceParticipants7674150
Region of Enrollment: GermanyParticipants489488977

6. Primary Endpoint

The registry lists the primary outcome as Number of Participants From Randomization to First Occurrence of Death From MACE-3 [Composite Endpoint of Major Adverse Cardiovascular Events Death From Cardiovascular Causes, Myocardial Infarction (MI) or Stroke], measured over From randomization (week 0) up to week 259.

ElementRegistry entry
Result typeNumber
Measure of spreadnot applicable
Unitparticipants
Endpoint classificationBinary Endpoint

The primary endpoint counts participants whose first recorded event was cardiovascular death, myocardial infarction, or stroke. It is a composite: a participant is counted when any one of these components occurs first. The registry describes event timing from randomization and says that participants without an event were censored at their last known contact or the end of follow-up. The stated timeframe runs from randomization through week 259.

Composite cardiovascular endpoints are used to capture several important types of cardiovascular event in one outcome. In general, combining components can make an overall endpoint more informative than considering only one event type, especially when the events are related to the clinical question. But a composite does not mean its components are equally frequent or carry equal clinical importance. A difference in the composite can be influenced more by some components than others, so component results should be considered separately where they are reported.

The posted primary result is a number of participants with an event and an unadjusted risk difference. It is not a hazard ratio, and it does not express how quickly events occurred or account for their timing in the same way as a time-to-event model. The registry record describes the endpoint in time-to-event terms, but the posted comparison gives the event counts and risk difference rather than a model-based estimate of event timing.

7. Results Posted in the Registry

Risk difference: 1.5 mg Dulaglutide

+0.9

95% CI: -0.2 to 2.1 percentage points

Recalculated from the posted summary statistics

Primary outcome by arm, with 95% confidence intervals
Primary outcome by arm with 95% confidence intervals11.111.812.413.013.614.2Tirzepatide (MTD) (n=6586)1.5 mg Dulaglutide (n=6579)% of participants (95% CI)
Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)1.5 mg Dulaglutide-0.380.150.681.201.732.26risk difference (percentage points) 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
Number of Participants From Randomization to Time to Occurrence of All-Cause DeathBinary EndpointRisk difference+1.6 pts (0.6 to 2.6)5,381 per arm
Number of Participants From Randomization to Time of Occurrence of CV DeathBinary EndpointRisk difference+0.6 pts (-0.2 to 1.4)21,973 per arm
Number of Participants From Randomization to Time to First Occurrence of Myocardial Infarction (MI)Binary EndpointRisk difference+0.7 pts (-0.0 to 1.5)15,246 per arm

Number of Participants From Randomization to Time to Occurrence of All-Cause Death

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)1.5 mg Dulaglutide-0.210.390.991.582.182.78risk difference (percentage points) vs control (95% CI)

Number of Participants From Randomization to Time of Occurrence of CV Death

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)1.5 mg Dulaglutide-0.300.070.440.821.191.56risk difference (percentage points) vs control (95% CI)

Number of Participants From Randomization to Time to First Occurrence of Myocardial Infarction (MI)

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)1.5 mg Dulaglutide-0.170.180.530.881.231.57risk difference (percentage points) vs control (95% CI)

The secondary outcomes broaden the clinical questions beyond the primary composite, including all-cause death, cardiovascular death, myocardial infarction, stroke, revascularization, heart-failure events, and nephropathy. Among the numerical secondary comparisons reported, the observed risk differences have a consistent direction, with higher event proportions in the dulaglutide group. Their uncertainty is not uniform: the all-cause death interval does not include zero, whereas the cardiovascular death and myocardial infarction intervals do.

These results add context to the primary composite but do not establish that every component or related outcome differs between groups. The primary endpoint combines event types, and component-specific comparisons can be less precise than a composite comparison because each concerns a narrower outcome. Conversely, a composite result should not be assumed to be driven by every component in the same way. The record does not report numerical results for every listed secondary endpoint, so no broader pattern across all secondary outcomes can be concluded from the outcomes listed alone.

Secondary comparisons generally carry less confirmatory weight when many outcomes are examined without a reported multiplicity procedure. If many tests are considered, some may appear notable by chance even when there is no underlying difference. The registry record does not report multiplicity adjustment or a hierarchy for the secondary outcomes. Their estimates should therefore be interpreted as descriptive and considered alongside the primary result, rather than as independent proof of treatment effects. They do not override the uncertainty in the primary comparison.

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

9. Statistical Interpretation

Clinical Biostats interpretation

The primary comparison records 801 participants with the composite event in the tirzepatide group and 862 in the dulaglutide group. The posted risk difference is 0.009, with a 95% confidence interval from -0.002 to 0.021 and an unadjusted p-value of 0.104. The contrast is dulaglutide minus tirzepatide, so the positive point estimate reflects a higher observed event proportion in the dulaglutide group. The interval includes zero, meaning that the posted estimate is compatible with no risk difference as well as with differences in either direction.

This result does not establish that the treatments are equivalent. A confidence interval that includes zero does not demonstrate that any difference is absent; it indicates that the estimate remains uncertain under this analysis. Equivalence or non-inferiority conclusions require prespecified margins and an analysis designed for that purpose. Those details are not reported in the registry record. Nor should the unadjusted p-value be treated as a complete summary of the evidence: the point estimate, the interval, endpoint definition, and analysis plan all matter.

The secondary comparisons show a similar direction in the posted risk-difference estimates, but their uncertainty differs. The all-cause death comparison has a confidence interval that does not include zero, while the cardiovascular death and myocardial infarction intervals include zero. These are unadjusted secondary comparisons, and the record does not report a multiplicity procedure for interpreting them. They therefore provide additional descriptive context, not a substitute for the primary analysis or evidence that can be read as a set of independent confirmatory tests.

The registry lists other secondary outcomes, including stroke, revascularization, heart-failure events, and nephropathy. Numerical results for all listed outcomes are not reported in the registry record. The reported endpoint counts also do not show how effects varied across participant subgroups. The primary estimate should consequently be read as an average comparison in the specified modified intention-to-treat population, rather than as a finding about every outcome or every kind of participant.

Overall, the posted primary result gives a modest positive point estimate for the dulaglutide-minus-tirzepatide risk difference, but its confidence interval is wide enough to include no difference. The data as posted do not provide a precise basis for concluding that the observed difference represents a clear treatment contrast. That interpretation is limited to this unadjusted endpoint comparison; it is not a clinical recommendation and does not by itself resolve safety, component-specific effects, or other outcomes.

10. Statistical Methods Explained

The primary outcome is binary for the posted count comparison: each participant is either counted as having experienced the composite event during follow-up or is not counted as having experienced it. The endpoint itself combines cardiovascular death, myocardial infarction, and stroke. The registry also describes when an event occurred and how participants without an event were censored, which are time-to-event features. However, the posted effect estimate is a risk difference based on event proportions, not a time-to-event model estimate.

What does the risk difference compare?

The risk difference is the event proportion in the dulaglutide group minus the event proportion in the tirzepatide group. A positive estimate means the observed proportion was higher in the first group named in that contrast; a negative estimate means it was lower. A value of zero represents no difference in the proportions. The estimate is unadjusted, so it is a direct comparison of the posted group-level event proportions rather than an estimate adjusted for other participant characteristics or time-to-event modeling.

Risk differences are expressed on an absolute scale. In general, they answer how far apart the observed event proportions are, rather than how many times larger one is than the other. This makes the result relatively direct to interpret, but the meaning still depends on the outcome definition, follow-up, population, and uncertainty around the estimate. A risk difference does not show whether the difference is statistically reliable by itself; the confidence interval and analysis context are also needed.

How should the confidence interval be read?

A confidence interval describes the uncertainty around an estimated effect under the statistical method used. In general, a 95% confidence interval is produced by a procedure that, across repeated samples under its assumptions, would cover the underlying effect 95% of the time. It is not a statement that there is a 95% probability that this particular interval contains the true effect. For the primary risk difference, the interval runs from -0.002 to 0.021. Because zero lies within that range, the posted data are compatible with no difference as well as with values on either side of zero.

The unadjusted p-value is 0.104. In general, a p-value describes how unusual data at least as discrepant as those observed would be under a specified null hypothesis and statistical model. It is not the probability that the null hypothesis is true, nor does it measure the size or clinical importance of an effect. Here it should be considered alongside the estimate and confidence interval. The registry record does not report an adjusted p-value or a model-based primary treatment effect.

Why do event counts and censoring matter?

The primary result reports the number of participants with an event, while the endpoint description also specifies follow-up time. Participants without a recorded event are censored at their last known contact or the end of follow-up. In general, censoring means that a participant contributes information up to a known point without being counted as having experienced the event after that point. A time-to-event analysis can use the timing of events and censoring; a simple event proportion does not use that timing in the same way. The posted risk difference therefore should not be interpreted as a comparison of event rates or of time until an event.

The record does not state additional missing-data procedures, such as how any other unavailable endpoint information was handled. It also does not report the assumptions or analysis details needed to assess whether censoring was treated in a way that matches the trial’s planned statistical method. No assumptions about these procedures should be inferred from the event counts alone.

What do the secondary comparisons add?

The reported secondary outcomes use the same broad idea of comparing participant event proportions between groups. Each outcome is a separate question, and their estimates need not have the same precision or represent the same clinical event. Secondary comparisons can help describe the pattern across outcomes, but interpreting many outcomes increases the chance that some findings look notable by chance alone. In general, multiplicity procedures address this by controlling the error associated with making multiple inferences. The registry record does not report whether such a procedure was planned or used.

For this reason, the secondary p-values and intervals should be treated as unadjusted descriptive evidence unless the registry record documents an appropriate confirmatory plan. The record lists 13 secondary outcomes, but only some have numerical comparisons described in the available results. It does not report a complete adjusted analysis across these outcomes. A favorable direction on one secondary measure does not establish a broad effect across all of them.

What do the planning calculations represent?

Planning illustrations use the observed effect as a starting point and consider smaller fractions of that effect. In general, power is the probability that a specified analysis will detect an effect of a stated size under its assumptions. A planned power target is not evidence that the observed result has that probability of being correct. The planning calculations for this study are illustrations rather than the trial’s original design justification, which is not reported in the registry record. They should not be confused with an observed power calculation or with the actual inferential analysis of the trial.

11. Confidence Intervals and Precision

The primary risk-difference estimate is 0.009, and its 95% confidence interval extends from -0.002 to 0.021. The interval includes zero, so the observed data do not pin down a single direction of difference with high precision. Values below zero and above zero remain within the interval. The posted p-value of 0.104 is consistent with this uncertainty, but the interval conveys more than a threshold-based decision: it shows the range of effects that remain compatible with the analysis.

Precision depends in part on the number of observed events and the variability of the data. In general, a confidence interval is narrower when an estimate is more precise and wider when it is less precise. The primary endpoint combines several event types, and the posted count comparison does not include an adjusted time-to-event estimate. The interval therefore describes uncertainty for the reported risk-difference comparison, not uncertainty for every possible treatment-effect measure.

The confidence interval should not be read as a range of likely individual outcomes or as proof that effects outside it are impossible. It also does not establish equivalence: the registry record does not report an equivalence margin or a non-inferiority analysis. Interpretation should remain tied to the specified endpoint, population, and unadjusted comparison. The secondary endpoint intervals vary in whether they include zero, and their individual precision does not remove the multiplicity concern or establish a consistent effect across outcomes.

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 effect19,60126,239
75% of the observed effect34,56946,277
50% of the observed effect77,154103,286
Sample size needed versus the size of the effect to detect
Sample size needed versus size of effect to detect20,00050,000100,000200,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, pooled-variance normal approximation for two proportions (control proportion held at the observed value). Calculated for the comparison: 1.5 mg Dulaglutide.

The planning figures illustrate how many participants per arm might be required under stated assumptions to detect effects at different fractions of the observed effect. For a binary participant-count endpoint such as the primary comparison, the figures are participants per arm. For a time-to-event calculation using the Schoenfeld method, figures refer instead to the total number of events. The planning assumptions are a two-sided significance level of 0.05, equal allocation between the two arms, and a normal approximation; the effect to detect is the stated fraction of the observed effect.

The 80% power column represents a planning target under which, if the assumed effect were the true effect and the calculation assumptions held, the design would detect that effect in 80% of repeated studies. The 90% power column uses a higher detection probability under the same kind of assumptions. These are planning targets, not guarantees for an individual study. Smaller effects are harder to distinguish from random variation, so the calculations require more participants per arm when the target is a smaller fraction of the observed effect.

The values are planning illustrations calculated from the observed effect, not the trial’s original design justification; that justification is not reported in the registry record. They are not observed power. They also do not establish that a future study will have the stated performance: the assumptions about allocation, significance level, approximation, and effect size would need to be appropriate for that future design.

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 = [ z1−α/2 √(2p̄(1−p̄)) + z1−β √(p0(1−p0) + p1(1−p1)) ]2 / (p1 − p0)2

n is the number of participants in each arm, p0 and p1 are the control and treatment proportions, and p̄ is their average.

Worked calculation for this trial

  1. Control proportion p0 = 0.122; treatment proportion p1 = 0.131; average p̄ = 0.126.
  2. First term: z1−α/2 × √[2p̄(1−p̄)] = 1.96 × 0.4698 = 0.9208.
  3. Second term: z1−β × √[p0(1−p0) + p1(1−p1)] = 0.842 × 0.4698 = 0.3954.
  4. n = (0.9208 + 0.3954)2 / (0.0094)2 = 19,600.4, rounded up to 19,601 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
p0 <- 0.121621621621622                          # control proportion
p1 <- 0.131022951816385                          # treatment proportion
n_per_arm <- function(power, frac = 1) {
  q1 <- p0 + (p1 - p0) * frac               # smaller effect = fraction of the observed difference
  pbar <- (p0 + q1) / 2
  z_b <- qnorm(power)
  ceiling(round((z_a * sqrt(2 * pbar * (1 - pbar)) + z_b * sqrt(p0 * (1 - p0) + q1 * (1 - q1)))^2 / (q1 - p0)^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 (unrounded n per arm)
cat("power.prop.test:", round(power.prop.test(p1 = p0, p2 = p1, power = 0.80)$n, 1), "\n")

# Simulation: how often does the z-test reject at the 80%-power sample size?
set.seed(4255433)
n    <- n_per_arm(0.80)
reps <- 20000
x0 <- rbinom(reps, n, p0); x1 <- rbinom(reps, n, p1)
ph <- (x0 + x1) / (2 * n)
z  <- ((x1 - x0) / n) / sqrt(ph * (1 - ph) * 2 / n)
cat(sprintf("Simulated power at n = %s per arm: %.3f (%d replicates)\n", format(n, big.mark = ","), mean(abs(z) > z_a, na.rm = TRUE), reps))

Output from running the code

100% of observed effect: n per arm = 19,601 (80% power), 26,239 (90% power)
 75% of observed effect: n per arm = 34,569 (80% power), 46,277 (90% power)
 50% of observed effect: n per arm = 77,154 (80% power), 103,286 (90% power)
power.prop.test: 19600.4 
Simulated power at n = 19,601 per arm: 0.800 (20000 replicates)

The simulation draws many pairs of event counts at the planned sample size and counts how often the two-proportion z-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. Multiplicity, Missing Data and Analysis Populations

The registry record lists a primary cardiovascular composite and multiple secondary outcomes. It does not report a statistical plan describing a hierarchy among those outcomes, a family of hypotheses, or a multiplicity adjustment. When several statistical tests are conducted, the chance of at least one result appearing notable by chance can increase. In general, multiplicity procedures are designed to address that issue, but the record does not say whether any were used. The reported secondary p-values should therefore be regarded as unadjusted rather than as a set of confirmatory findings.

The primary comparison itself is also presented as an unadjusted risk difference. The registry record does not report an adjusted estimate, the covariates that might have been used in an adjusted model, or further details of the primary statistical analysis. The stated population is modified intention-to-treat, with randomized participants analyzed according to assigned treatment. That population definition is reported, but the registry record does not describe additional analysis populations or sensitivity analyses.

The primary endpoint definition states that participants without an event were censored at their last known contact or the end of follow-up. This gives a basic description of how event-free follow-up was handled. It does not specify other missing-data methods, the amount of missing endpoint information, or assumptions about censoring. Those details are not reported in the registry record.

The original sample-size justification, planned interim analyses, and broader statistical analysis plan are also not reported. As a result, the posted unadjusted comparisons cannot be checked against a documented confirmatory testing strategy in the record. This does not show that such methods were absent from the trial; it means they are not reported in the registry record.

15. Safety Results

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

ArmParticipants with serious adverse eventsParticipants at riskPercentage
Tirzepatide (MTD)2117664731.8%
1.5 mg Dulaglutide2121664731.9%
Participants with at least one serious adverse event
Serious adverse events by armTirzepatide (MTD)31.8%1.5 mg Dulaglutide31.9%% of participants with at least one serious adverse event

Deaths

ArmDeaths (participants affected of at risk)
Tirzepatide (MTD)568 of 6648
1.5 mg Dulaglutide670 of 6651

Other (non-serious) adverse events

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

ArmParticipants affected of at risk
Tirzepatide (MTD)4718 of 6647
1.5 mg Dulaglutide4297 of 6647

Most frequent serious adverse event terms

Event termOrgan systemTirzepatide (MTD)1.5 mg Dulaglutide
PneumoniaInfections and infestations126 of 6647158 of 6647
Acute kidney injuryRenal and urinary disorders93 of 664792 of 6647
Covid-19Infections and infestations60 of 664785 of 6647
Covid-19 pneumoniaInfections and infestations62 of 664767 of 6647
Cardiac failure chronicCardiac disorders62 of 664762 of 6647
Peripheral arterial occlusive diseaseVascular disorders59 of 664765 of 6647
Angina unstableCardiac disorders63 of 664758 of 6647
Atrial fibrillationCardiac disorders57 of 664755 of 6647
Urinary tract infectionInfections and infestations57 of 664752 of 6647
Cholecystitis acuteHepatobiliary disorders56 of 664742 of 6647

Most frequent non-serious adverse event terms

Event termOrgan systemTirzepatide (MTD)1.5 mg Dulaglutide
NauseaGastrointestinal disorders1665 of 66471484 of 6647
DiarrhoeaGastrointestinal disorders1644 of 66471258 of 6647
Covid-19Infections and infestations1041 of 66471005 of 6647
Decreased appetiteMetabolism and nutrition disorders1136 of 6647647 of 6647
ConstipationGastrointestinal disorders836 of 6647771 of 6647
VomitingGastrointestinal disorders757 of 6647637 of 6647
DyspepsiaGastrointestinal disorders658 of 6647540 of 6647
Urinary tract infectionInfections and infestations442 of 6647462 of 6647
DizzinessNervous system disorders462 of 6647407 of 6647
ArthralgiaMusculoskeletal and connective tissue disorders406 of 6647419 of 6647

Serious events with the highest arm-level rate: pneumonia (2.4%), acute kidney injury (1.4%), covid-19 (1.3%), covid-19 pneumonia (1.0%), peripheral arterial occlusive disease (1.0%).

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 lists serious adverse events for groups with 6647 participants at risk in each group. Serious adverse events affected 2117 participants in the tirzepatide group and 2121 in the dulaglutide group. The counts of other adverse events were 4718 and 4297, respectively, among groups with 6647 at risk. Deaths listed in the adverse-event data were 568 and 670, respectively. These are counts, not adjusted comparisons, and the registry data do not establish that a treatment caused an event or difference.

Frequently listed serious-event terms include pneumonia (2.4%), acute kidney injury (1.4%), Covid-19 (1.3%), Covid-19 pneumonia (1.0%), peripheral arterial occlusive disease (1.0%), and angina unstable (0.9%). Such terms describe recorded events; they do not by themselves provide a complete comparison of the event’s seriousness, duration, relationship to treatment, or clinical course. The registry record does not report an adjusted safety analysis in the results. Counts should be interpreted within the registry’s reporting context, not as a stand-alone estimate of comparative risk.

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

The primary result is a comparison of observed event proportions for the first occurrence of cardiovascular death, myocardial infarction, or stroke in the modified intention-to-treat population. The point estimate is positive for the dulaglutide-minus-tirzepatide risk difference, but the 95% confidence interval includes zero. The posted result therefore leaves uncertainty about the direction and size of the underlying difference under this analysis.

This does not establish that the treatments are equivalent, and it does not establish a clear difference. Equivalence or non-inferiority requires a prespecified margin and an analysis designed to test that question; those details are not reported in the registry record. Nor does a non-significant unadjusted p-value prove that the treatments have identical effects. The estimate and its uncertainty are more informative than a binary label based only on a p-value.

The result is specific to the endpoint, follow-up description, and analysis population recorded for this trial. It does not show whether the pattern is the same for each component of the composite, for every secondary outcome, or for participant subgroups. The record lists a range of secondary outcomes, but numerical findings for all of them are not reported. The posted unadjusted analysis also does not answer every possible time-to-event question, because it presents a risk difference rather than a model-based estimate of event timing.

Safety counts provide additional descriptive information but do not, by themselves, identify treatment causation or establish a comparative safety profile. A complete interpretation would consider the study’s prespecified analyses, outcome definitions, missing-data handling, and safety methods; some of these details are not reported in the registry record. The statistics describe the posted data and their uncertainty, not an individualized prediction or a treatment recommendation.

17. Why This Trial Matters Statistically

This trial raises statistical questions that are common in cardiovascular outcome research: how to compare treatments using a composite endpoint, how to interpret an absolute risk difference, and how much certainty to attach to a point estimate when its confidence interval includes zero. The primary comparison is not simply a contest between event counts. It is an estimate with uncertainty, tied to a defined population, endpoint, and follow-up approach.

The composite endpoint combines cardiovascular death, myocardial infarction, and stroke. That can make a broad cardiovascular question more tractable, but interpretation still depends on the components. The secondary comparisons offer some component-level context, while their unadjusted status and the lack of reported multiplicity methods constrain how strongly they can be interpreted. The distinction between a composite result and its component outcomes is therefore central to reading this record.

The registry also illustrates the difference between a trial’s original design and retrospective planning illustrations based on an observed effect. The latter can show how assumed effect size and target power relate to required sample size, but they do not reveal the original design rationale or the probability that the observed result is correct. Here, the original justification is not reported in the registry record.

Finally, the primary result is posted as a risk difference even though the endpoint description includes time-to-event features and censoring. Keeping the estimand clear matters: event proportions and event timing answer related, but not identical, questions. Reading the estimate, confidence interval, endpoint definition, and analysis limitations together supports a more measured interpretation than relying on a single threshold.

18. Limitations

Several limitations are specific to the posted record. The primary comparison is an unadjusted risk difference based on participant event counts. Although the endpoint definition describes time to event and censoring, the results do not include a hazard ratio or other model-based estimate that uses event timing. The posted effect therefore should not be extended to conclusions about how quickly events occurred.

The confidence interval for the primary risk difference includes zero, leaving uncertainty about the direction and magnitude of the difference. The record does not report a prespecified equivalence or non-inferiority margin, so the result cannot be interpreted as demonstrating equivalence. It also does not report the original sample-size rationale, planned analysis details, interim analyses, or a multiplicity approach for secondary outcomes.

The registry lists several secondary endpoints, but numerical results for all of them are not reported in the registry record. The reported secondary comparisons are unadjusted, and the record does not document a strategy for interpreting multiple tests. There is also no subgroup analysis described in these results, so the average comparison should not be assumed to apply identically across participant groups.

For missing information, the primary endpoint description says participants without an event were censored at last known contact or the end of follow-up. Other missing-data procedures and the amount of unavailable endpoint information are not reported in the registry record. The displayed adverse-event counts are descriptive and do not establish causation or replace a comparative safety analysis. These limitations reflect what is reported in the registry record, not proof that additional analyses were not conducted.

19. Related Tutorials

20. Related Statistical Calculators

21. 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.

22. Record Summary

SURPASS-CVOT was a completed phase 3, randomized, double-masked, parallel-group trial sponsored by Eli Lilly and Company. The registry reports enrollment of 13299 participants with type 2 diabetes and increased cardiovascular risk. The comparison was tirzepatide, titrated to a maximum tolerated dose, versus 1.5 mg dulaglutide, with both treatments administered once weekly for up to 5 years.

The primary outcome counted participants with a first occurrence of cardiovascular death, myocardial infarction, or stroke through week 259. In the modified intention-to-treat population, the posted unadjusted risk difference was 0.009, with a 95% confidence interval from -0.002 to 0.021 and an unadjusted p-value of 0.104. The interval includes zero, so the posted primary comparison remains uncertain about the direction and size of the difference. The registry record does not report the original sample-size justification, multiplicity strategy, or a complete adjusted analysis.

Clinical Biostats