← Clinical Trials
Psoriasis Phase 3 Binary Endpoint NCT02660580

MSB11022 in Moderate to Severe Chronic Plaque Psoriasis: Complete Statistical Analysis

This analysis examines the primary Week 16 PASI 75 response in the randomized comparison of MSB11022 with EU-Humira for adults with moderate to severe chronic plaque psoriasis. It also considers the reported sponsor analysis, selected secondary outcomes, safety counts, and the precision and limits of the available results.

Trial start: 2016-02-16  ·  Enrollment: 443  ·  Sponsor: Fresenius Kabi SwissBioSim GmbH
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 MSB11022 in Moderate to Severe Chronic Plaque Psoriasis (NCT02660580), a randomized phase 3 study. The primary outcome is Percentage of Participants Who Achieved Psoriasis Area and Severity Index 75 (PASI 75) at Week 16.

443
Enrollment
Phase 3
2
Arms
In the primary outcome
+2.0 pts
Risk difference
EU-Humira
-3.8 to 7.7 pts
95% CI
Two-sided
FeatureRegistry value
ClinicalTrials.gov identifierNCT02660580
PhasePhase 3
ConditionPsoriasis, Plaque Type Psoriasis, Moderate to Severe Plaque Psoriasis
AllocationRandomized
Design modelParallel
MaskingDouble
Enrollment443
Arms in the primary outcome2
Lead sponsorFresenius Kabi SwissBioSim GmbH
Results postedYes

2. Clinical Question

Population

Adults with moderate to severe chronic plaque psoriasis were enrolled. The primary endpoint analysis used the per-protocol population: randomized and treated participants without major protocol deviations during the Core Treatment Period that were likely to affect treatment efficacy.

Intervention

MSB11022 was given subcutaneously, beginning with 80 mg on Day 1 of Week 1, followed by 40 mg every other week from Week 2 through Week 14 during the Core Treatment Period.

Comparator

EU-Humira was given subcutaneously on the same initial and every-other-week schedule during the Core Treatment Period.

Primary question

What percentage of participants in each treatment group achieved PASI 75 at Week 16—that is, at least a 75% improvement in PASI score from baseline—and how precisely does the comparison estimate the difference between groups?

The registry describes a randomized, double-blind, parallel-group Phase 3 study. The overall enrollment was 443. The primary result is based on the per-protocol population, rather than all enrolled participants: 203 participants were included in the MSB11022 group and 191 in the EU-Humira group for this endpoint. The distinction matters because the primary analysis population excludes participants with certain major protocol deviations during the core period.

The registry also describes an Extended Treatment Period. Participants who had achieved PASI 50 and received MSB11022 in the core period continued MSB11022. Participants who had received EU-Humira and achieved PASI 50 were re-randomized to continue EU-Humira or switch to MSB11022. Those later treatment paths address questions different from the initial randomized comparison at Week 16, and the Week 16 primary result should not be read as a comparison of the extended-period groups.

The study’s stated purpose included efficacy, safety, and immunogenicity. The primary endpoint addressed one specific efficacy question: the proportion reaching a prespecified level of improvement by Week 16. The registry record does not report the original sample-size justification or the trial’s full statistical analysis plan.

3. Trial Design

This was a randomized, double-blind, parallel-group Phase 3 trial sponsored by Fresenius Kabi SwissBioSim GmbH. The registry lists a total enrollment of 443 and a completed status. The recorded study start was 2016-02-16, and primary completion was 2016-12-31. The registry record does not report further details about how the randomization sequence was generated, how allocation was concealed, or how masking was maintained.

During the Core Treatment Period, the two groups followed the same dosing schedule, with MSB11022 in one group and EU-Humira in the other. The primary Week 16 PASI 75 comparison used the per-protocol analysis set. This set included randomized and treated participants who did not have major protocol deviations during the core period that were likely to affect efficacy. The primary endpoint group sizes were 203 for MSB11022 and 191 for EU-Humira.

The trial also had an Extended Treatment Period. Entry into the described continued-treatment paths depended on achieving PASI 50 during the core period. Participants who had received EU-Humira and met that condition were re-randomized to EU-Humira or MSB11022. This conditional later phase should be distinguished from the initial randomized comparison: its groups are defined by prior treatment and response as well as later allocation. The registry record does not report enough detail to reconstruct all extended-period analysis populations or their statistical methods.

The record lists 38 outcome measures and 37 posted secondary outcomes. These include additional PASI response thresholds and time points, change in PASI, physician global assessment, time to PASI 50, quality of life, and safety measures. Their presence does not by itself establish that each was part of a prespecified confirmatory testing sequence. The multiplicity plan and the original statistical analysis plan are not reported in the registry record.

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.

Before assignment: Participants were randomized to either MSB11022 or EU-Humira in Core Treatment Period till Week 16. Participants who achieved PASI50 at Week 16 entered Extension Period where participants in MSB11022 were continued to receive MSB11022 \& participants in EU-Humira were re-randomized to receive either MSB11022 or EU-Humira for additional 37 weeks.

Core Treatment Period (Week 1 to 16)

StageMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
STARTED222221000
Treated221220000
COMPLETED213202000
NOT COMPLETED919000

Reasons for not completing this period:

ReasonMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
Randomized, not treated11000
Protocol Violation31000
Other un-specified10000
Lack of Efficacy02000
Adverse Event29000
Withdrawal by Subject14000
Lost to Follow-up12000

Extended Treatment Period(Week 16 to 52)

StageMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
STARTED00213101101
COMPLETED001959090
NOT COMPLETED00181111

Reasons for not completing this period:

ReasonMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
Protocol Violation00201
Other un-specified00101
Lack of Efficacy00422
Adverse Event00864
Withdrawal by Subject00322
Lost to Follow-up00011

Analysis population for the primary outcome, as defined in the registry: The per-protocol (PP) Analysis Set included all randomized and treated participants who did not have any major protocol deviations during the Core Treatment Period with respect to factors likely to affect the efficacy of treatment.

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.

CharacteristicUnitMSB11022 (Core Treatment Period)EU-HumiraTotal
Participants analysed222221443
Age, Continuousyears44.5 (SD 12.8)42.7 (SD 12.0)43.6 (SD 12.5)
Sex: Female, Male: FemaleParticipants7573148
Sex: Female, Male: MaleParticipants147148295
Race: WhiteParticipants205200405
Race: Black or African AmericanParticipants213
Race: AsianParticipants5914
Race: American Indian or Alaska NativeParticipants10818
Race: Native Hawaiian or Other Pacific IslanderParticipants000
Race: OtherParticipants011
Race: Missing/Not collected at this siteParticipants022
Ethnicity: Hispanic or LatinoParticipants232346
Ethnicity: Not Hispanic or LatinoParticipants199196395
Ethnicity: MissingParticipants022

6. Primary Endpoint

The registry lists the primary outcome as Percentage of Participants Who Achieved Psoriasis Area and Severity Index 75 (PASI 75) at Week 16, measured over Week 16.

ElementRegistry entry
Result typeNumber
Measure of spreadnot applicable
UnitPercentage of Participants
Endpoint classificationBinary Endpoint

The primary endpoint was the percentage of participants who achieved PASI 75 at Week 16. PASI is a composite assessment of psoriasis symptoms and affected body area. It incorporates redness, thickness, and scaliness of lesions, along with the extent of involvement across the head, arms, trunk to groin, and legs to the top of the buttocks. Each symptom parameter is graded from 0 to 4, and the total score ranges from 0 to 72; higher scores indicate greater disease severity.

A PASI 75 response means that a participant’s score improved by at least 75% from baseline. The endpoint therefore converts a change in a continuous score into a binary outcome: each participant either meets the response threshold or does not. The group percentage expresses how common that threshold response was in the analyzed population. It is clinically interpretable as a responder proportion, but it does not show the full distribution of score changes or distinguish participants just below the threshold from those with little change.

Using a defined response threshold permits a direct comparison of the proportion reaching that level by a specified time. The meaning of the result still depends on the analysis population and on the uncertainty around the between-group estimate. The registry record identifies the endpoint and the per-protocol population, but the detailed method used for the sponsor’s primary endpoint analysis is not reported.

7. Results Posted in the Registry

Risk difference: EU-Humira

+2.0

95% CI: -3.8 to 7.7 percentage points

Recalculated from the posted summary statistics

Primary outcome by arm, with 95% confidence intervals
Primary outcome by arm with 95% confidence intervals83.786.188.590.993.495.8MSB11022 (Core Treatment Peri… (n=203)EU-Humira (n=191)% of participants (95% CI)
Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)EU-Humira-4.69-2.030.643.305.978.63risk 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
Percent Change From Baseline in PASI at Week 16Continuous EndpointMean difference-1.10 (-3.19 to 0.99)1,470 per arm
Number of Participants With Clinically Significant Abnormalities in 12-Electrocardiogram (12-ECG)Binary EndpointRisk difference+0.5 pts (-0.4 to 1.4)n/a
Dermatology Life Quality Index (DLQI) at Week 16Continuous EndpointMean difference0.10 (-0.58 to 0.78)18,700 per arm

Percent Change From Baseline in PASI at Week 16

Treatment effect versus the control arm
Forest plot of mean difference vs control (95% CI)EU-Humira-3.53-2.56-1.59-0.610.361.33mean difference vs control (95% CI)

Number of Participants With Clinically Significant Abnormalities in 12-Electrocardiogram (12-ECG)

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)MSB11022 (Extended Treatment …EU-Humira-0.60-0.170.260.681.111.53risk difference (percentage points) vs control (95% CI)

Dermatology Life Quality Index (DLQI) at Week 16

Treatment effect versus the control arm
Forest plot of mean difference vs control (95% CI)EU-Humira-0.69-0.38-0.060.260.580.89mean difference vs control (95% CI)

The secondary outcomes span several related domains: additional PASI response thresholds and assessment times, change in PASI, physician global assessment, time to PASI 50, dermatology quality of life, and safety measures. This breadth provides context around the primary Week 16 responder outcome, but the measures do not all ask the same question. A threshold response, a continuous score change, and a quality-of-life score capture different aspects of the recorded outcomes.

The posted Week 16 summaries for PASI change and DLQI have group means close to one another. The ECG abnormality outcome has very few reported participants with clinically significant abnormalities. These broad patterns do not establish a general result across all secondary outcomes: the registry lists many outcomes, while their analysis populations, methods, and uncertainty are not uniformly available in the record. Detailed secondary endpoint results should be interpreted on their own scales and with their own intervals rather than combined into a single conclusion.

Secondary findings can support or qualify interpretation of the primary endpoint, but they do not supersede it. They may also be less conclusive when many outcomes are examined without a reported adjustment plan. General statistical explanation: testing many outcomes increases the chance that at least one apparently notable result will arise by chance, even when no true effect exists for any outcome. Adjustments or a prespecified hierarchy can address this issue, but the multiplicity strategy is not reported in the registry record.

The Week 16 PASI 75 endpoint remains the primary comparison described in the record. The secondary outcomes add dimensions and time points, but the available information does not establish which secondary comparisons were confirmatory, how missing values were handled, or whether results were adjusted for multiple testing. Those limitations counsel against treating isolated secondary findings as independent proof of a treatment difference.

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

9. Statistical Interpretation

Clinical Biostats interpretation

In the per-protocol analysis, PASI 75 at Week 16 was reported for 89.7% of participants in the MSB11022 group and 91.6% in the EU-Humira group. The recalculated unadjusted comparison estimates a risk difference of 0.020 in the direction EU-Humira minus MSB11022. The recalculated confidence interval extends from -0.038 to 0.077, and the unadjusted p-value is 0.503. The estimate is close to zero relative to the interval’s width, and the interval includes values on either side of zero.

These data describe the observed responder proportions in the analyzed population. They do not establish that the treatments are identical. A confidence interval that includes zero is compatible with no difference under the calculation’s assumptions, but it also includes nonzero differences. The estimate should therefore be read together with its uncertainty, rather than as a definitive ranking based only on the two percentages.

The registry’s reported analysis is labelled as an equivalence analysis. It gives a percentage difference of -1.9 with a 95% confidence interval from -7.82 to 4.07. No p-value or analysis method is listed for that result. The reported interval spans zero, but the equivalence margin and the complete analysis specification are not reported in the registry record. Without the margin, the label alone does not establish whether the sponsor’s formal equivalence criterion was met.

The recalculation is an unadjusted comparison based on the posted group summaries. It is not a replacement for the sponsor’s analysis. The sponsor’s reported analysis takes precedence when interpreting the trial’s own result, particularly because the registry reports a designated equivalence analysis but does not give its method or margin. The recalculated estimate is useful as a transparent check on the direction and approximate scale of the posted group results, not as an independent confirmatory test.

Other reported outcomes cover additional PASI assessments, physician global assessment, quality of life, and safety. The Week 16 PASI change and DLQI group means are close between the two core-treatment groups, while the ECG outcome counts are sparse. Those outcomes provide related but distinct information; they do not replace the primary PASI 75 comparison. Their interpretation also depends on analysis populations, uncertainty, missing-data handling, and multiplicity procedures, many of which are not reported in the registry record.

10. Statistical Methods Explained

For the primary endpoint, each participant is classified according to whether PASI improved by at least 75% from baseline at Week 16. A binary outcome comparison can be expressed in several ways. The risk difference subtracts one group’s response proportion from the other’s; it is zero when the proportions are equal. A risk ratio compares the proportions by division, while an odds ratio compares the odds of response. These measures describe the same binary outcome on different scales, so their numerical values are not interchangeable. The direction of a contrast also depends on which group is subtracted from which.

The recalculated primary comparison is an unadjusted risk difference, with EU-Humira contrasted against MSB11022. Its estimate is 0.020, with a confidence interval from -0.038 to 0.077 and an unadjusted p-value of 0.503. The recalculation uses posted summary counts: 182 of 203 participants in the MSB11022 group and 175 of 191 in the EU-Humira group achieved the endpoint. These are summary-statistic calculations, not an adjusted model. The registry record does not report the full model or method used for the sponsor’s endpoint analysis.

What does the confidence interval convey?

General statistical explanation: a confidence interval describes the range of estimates reasonably compatible with the data under the method’s assumptions. A wider interval indicates less precision than a narrower interval. When an interval for a difference includes zero, the data do not clearly distinguish a positive difference from a negative one at the interval’s stated confidence level. That does not prove equality, and it does not measure the probability that a particular treatment effect is true.

The sponsor’s reported primary analysis is labelled as equivalence and presents a percentage difference with a 95% confidence interval. Equivalence testing asks whether the uncertainty interval falls within a prespecified range of differences considered acceptably small. The boundaries of that range—the equivalence margin—are essential to interpreting such a test. The margin and method are not reported in the registry record, so the formal equivalence conclusion cannot be independently assessed from the posted result alone.

Why distinguish the analysis populations?

The primary analysis population is per protocol. It includes randomized and treated participants who did not have major protocol deviations during the Core Treatment Period that were likely to affect treatment efficacy. This is a narrower definition than simply including everyone enrolled. The registry record does not report a corresponding intention-to-treat primary result, the number excluded from the per-protocol analysis by reason, or how missing Week 16 outcomes were handled. These omissions limit assessment of how the analysis population and incomplete observations may affect the comparison.

A per-protocol result can answer a question about participants meeting the specified protocol conditions, but it may be sensitive to exclusions after randomization. That is a general concern in trial interpretation, not evidence that exclusions biased this result. The available record does not establish whether excluded participants differed in outcome or treatment response.

How should the p-value be read?

General statistical explanation: a p-value measures how incompatible the observed data are with a specified null model, assuming that model and the analysis assumptions hold. It is not the probability that the null hypothesis is true, and it does not quantify the size or clinical importance of a difference. The recalculated p-value is unadjusted; the registry does not report an adjustment for multiple comparisons for this calculation. The sponsor’s reported equivalence result has no p-value listed.

The registry reports a risk ratio and odds ratio for the primary comparison as well as the risk-difference calculation. Such measures can help describe relative contrasts, but they do not remove uncertainty or resolve questions about analysis populations and multiplicity. They should be interpreted using their own intervals and their stated group orientation.

What does over-dispersion mean?

General statistical explanation: over-dispersion occurs when the observed variability in data is greater than a model assumes. It can make standard errors too small and confidence intervals too narrow if the model does not account for the extra variation. The primary endpoint is binary and the posted recalculation uses group-level response counts; no over-dispersion parameter is listed for that calculation. The registry record does not report a model-based analysis that would permit a more specific discussion of this issue.

For continuous outcomes, the posted summaries include group means and standard deviations. A mean difference describes the contrast on the outcome’s original scale, while a standardized effect expresses a difference relative to variability. These summaries are descriptive unless interpreted with a clearly specified analysis model and uncertainty interval. The registry reports a Week 16 PASI change comparison as an equivalence analysis, but its method is not reported. The record likewise does not report a complete plan for handling covariates, missing observations, or repeated measurements.

11. Confidence Intervals and Precision

The primary recalculated estimate is accompanied by a confidence interval from -0.038 to 0.077 for the EU-Humira minus MSB11022 risk difference. Because the interval includes zero, the recalculation does not sharply distinguish a positive contrast from a negative one. Its range also shows that the point estimate alone should not be treated as a precise description of the underlying difference. The unadjusted p-value is 0.503, which is consistent with substantial uncertainty about the direction of the contrast under the recalculation’s assumptions.

The sponsor’s reported percentage difference is -1.9, with a 95% confidence interval from -7.82 to 4.07. That interval also includes zero. The sponsor’s contrast is reported in a different form and direction from the recalculated risk difference, so the signs should not be compared without accounting for the group order and the scale. The registry record does not report the equivalence margin, which is needed to judge the formal precision requirement for an equivalence conclusion.

General statistical explanation: confidence intervals summarize sampling uncertainty under a method’s assumptions. They do not account automatically for every source of uncertainty, such as missing outcomes, deviations from the analysis plan, or selection into an analysis population. Nor does an interval that crosses zero demonstrate that the groups are equivalent. Precision is therefore a combination of the interval’s width, the outcome scale, the analysis population, and the validity of the analysis method.

The posted per-protocol group sizes are 203 and 191 for the primary endpoint. The registry record does not provide enough information to determine how missing observations or exclusions affected the interval. The estimate is consequently best read as an uncertain comparison among the participants in the reported analysis set, not as a highly precise statement about every participant enrolled.

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 effect3,4394,603
75% of the observed effect6,2578,376
50% of the observed effect14,40119,279
Sample size needed versus the size of the effect to detect
Sample size needed versus size of effect to detect2,0005,00010,00020,00050,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. Counts were reconstructed from the posted percentages and arm sizes, so small rounding differences are possible. Calculated for the comparison: EU-Humira.

The planning figures are illustrations based on the observed effect, not a reconstruction of the trial’s original design. For the primary binary endpoint, the figures are participants per arm. The stated assumptions are a two-sided significance level of 0.05, equal allocation between two arms, and a normal approximation; each scenario targets the stated fraction of the observed effect. The registry record does not report the original sample-size justification or its design assumptions.

For 100% of the observed effect, the illustration gives 3,439 participants per arm for 80% power and 4,603 participants per arm for 90% power. For 75% of the observed effect, it gives 6,257 participants per arm for 80% power and 8,376 participants per arm for 90% power. For 50% of the observed effect, it gives 14,401 participants per arm for 80% power and 19,279 participants per arm for 90% power.

In plain language, the 80% power column describes the number of participants per arm that the stated planning method estimates would be needed to detect the selected effect with 80% power under its assumptions. The 90% column uses a higher target probability of detecting that effect, if it is present under the planning model, and therefore requires more participants in these illustrations. Smaller effects are harder to distinguish from random variation, so the scenarios targeting a smaller fraction of the observed effect require more participants.

These values are not observed power. They are hypothetical planning estimates derived from the observed effect, not evidence about the probability that this completed trial detected an effect. For any time-to-event planning figures, the stated convention is total events; all other planning figures are participants per arm. The primary endpoint figures are participants per arm.

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.897; treatment proportion p1 = 0.916; average p̄ = 0.906.
  2. First term: z1−α/2 × √[2p̄(1−p̄)] = 1.96 × 0.4119 = 0.8074.
  3. Second term: z1−β × √[p0(1−p0) + p1(1−p1)] = 0.842 × 0.4117 = 0.3465.
  4. n = (0.8074 + 0.3465)2 / (0.0197)2 = 3,438.2, rounded up to 3,439 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.896551724137931                          # control proportion
p1 <- 0.916230366492147                          # 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(2660580)
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 = 3,439 (80% power), 4,603 (90% power)
 75% of observed effect: n per arm = 6,257 (80% power), 8,376 (90% power)
 50% of observed effect: n per arm = 14,401 (80% power), 19,279 (90% power)
power.prop.test: 3438.2 
Simulated power at n = 3,439 per arm: 0.798 (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. Analyses Reported by the Sponsor

MethodEstimate95% CIP-value
not statedPercentage difference -1.9-7.82 to 4.07not reported

The sponsor’s posted primary analysis is labelled as an equivalence analysis. It reports a percentage difference of -1.9 and a 95% confidence interval from -7.82 to 4.07. The registry does not list a p-value or the analysis method for this result. It also does not report the equivalence margin, so the posted values alone are insufficient to determine whether a prespecified equivalence criterion was satisfied.

The simple recalculation uses the posted primary group counts and estimates an unadjusted risk difference of 0.020 for EU-Humira minus MSB11022, with a confidence interval from -0.038 to 0.077 and an unadjusted p-value of 0.503. This calculation and the sponsor’s result use different reported forms and apparent contrast orientations. Their signs should not be compared as if they expressed the same contrast without first aligning the group order and scale.

The recalculation is a consistency check from summary statistics, not an alternative to the sponsor’s own analysis. The sponsor’s analysis takes precedence for the trial’s reported inferential result. Because the registry record does not provide the analysis method or equivalence margin, readers cannot fully reproduce or evaluate the sponsor’s formal equivalence assessment from the posted information alone.

15. Multiplicity, Missing Data and Analysis Populations

The registry record does not report a multiplicity strategy for the numerous listed outcomes and analyses. This matters because repeated testing across endpoints, time points, and response thresholds can increase the chance of apparently noteworthy findings due to chance. A prespecified testing hierarchy or adjustment procedure can help control that risk, but neither is described in the available record. The unadjusted recalculated primary p-value should not be mistaken for a multiplicity-adjusted result.

The primary endpoint population is the per-protocol analysis set, defined as randomized and treated participants without major protocol deviations during the Core Treatment Period that were likely to affect efficacy. The registry record does not report a parallel intention-to-treat result for the primary endpoint or a full accounting of participants excluded from the per-protocol set. It also does not report the analysis populations used for every secondary outcome in enough detail to assess whether they match the primary population.

Missing-data methods are not reported in the registry record. The record does not specify how participants without a Week 16 assessment were handled, whether any values were imputed, or whether sensitivity analyses examined alternative assumptions. These details matter because the primary outcome is a responder classification at a specific time point, and incomplete assessments can affect the estimated response proportions.

The registry record also does not report interim analyses, stopping rules, or the original statistical analysis plan. The sponsor’s reported primary result is labelled as equivalence, but the method and equivalence margin are not reported. These gaps prevent a complete assessment of prespecification, multiplicity control, missing-data sensitivity, and the formal equivalence criterion. Their absence from the registry record is a limit on interpretation, not evidence that a particular procedure was or was not used outside the 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
MSB11022 (Core Treatment Period)82213.6%
EU-Humira62202.7%
MSB11022 (Extended Treatment Period)122135.6%
EU-Humira/EU-Humira31013.0%
EU-Humira/MSB1102241014.0%
Participants with at least one serious adverse event
Serious adverse events by armMSB11022 (Core Treatment Peri…3.6%EU-Humira2.7%MSB11022 (Extended Treatment …5.6%EU-Humira/EU-Humira3.0%EU-Humira/MSB110224.0%% of participants with at least one serious adverse event

Deaths

ArmDeaths (participants affected of at risk)
MSB11022 (Core Treatment Period)0 of 221
EU-Humira0 of 220
MSB11022 (Extended Treatment Period)0 of 213
EU-Humira/EU-Humira1 of 101
EU-Humira/MSB110220 of 101

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
MSB11022 (Core Treatment Period)30 of 221
EU-Humira34 of 220
MSB11022 (Extended Treatment Period)59 of 213
EU-Humira/EU-Humira32 of 101
EU-Humira/MSB1102225 of 101

Most frequent serious adverse event terms

Event termOrgan systemMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
Atrial FibrillationCardiac disorders1 of 2210 of 2201 of 2130 of 1010 of 101
Cardiac failureCardiac disorders0 of 2210 of 2200 of 2132 of 1010 of 101
NeutropeniaBlood and lymphatic system disorders0 of 2211 of 2200 of 2130 of 1010 of 101
Acute myocardial infarctionCardiac disorders0 of 2210 of 2201 of 2130 of 1010 of 101
CardiomyopathyCardiac disorders0 of 2210 of 2201 of 2130 of 1010 of 101
Coronary artery stenosisCardiac disorders0 of 2210 of 2201 of 2130 of 1010 of 101
Hypertensive cardiomyopathyCardiac disorders0 of 2210 of 2200 of 2131 of 1010 of 101
Mitral valve incompetenceCardiac disorders0 of 2210 of 2200 of 2131 of 1010 of 101
Myocardial infarctionCardiac disorders0 of 2210 of 2200 of 2130 of 1011 of 101
Conjunctival cystEye disorders0 of 2210 of 2200 of 2130 of 1011 of 101

Most frequent non-serious adverse event terms

Event termOrgan systemMSB11022 (Core Treatment Period)EU-HumiraMSB11022 (Extended Treatment Period)EU-Humira/EU-HumiraEU-Humira/MSB11022
NasopharyngitisInfections and infestations13 of 22115 of 22031 of 21312 of 10116 of 101
Injection site erythemaGeneral disorders11 of 22113 of 2209 of 2135 of 1016 of 101
Injection site painGeneral disorders11 of 22111 of 22012 of 2134 of 1015 of 101
PsoriasisSkin and subcutaneous tissue disorders0 of 2210 of 22011 of 21310 of 1013 of 101
Upper respiratory tract infectionInfections and infestations0 of 2210 of 22011 of 2135 of 1014 of 101

Serious events with the highest arm-level rate: cardiac failure (2.0%), hypertensive cardiomyopathy (1.0%), mitral valve incompetence (1.0%), myocardial infarction (1.0%), conjunctival cyst (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.

During the Core Treatment Period, serious adverse events were reported for 8 of 221 participants in the MSB11022 group and 6 of 220 participants in the EU-Humira group. The record lists 30 other adverse events for the MSB11022 group and 34 for the EU-Humira group, with the same respective group denominators. No deaths were reported in either core-period group.

For the extended-period groups, serious adverse events were reported for 12 of 213 participants continuing MSB11022, 3 of 101 participants continuing EU-Humira, and 4 of 101 participants switching from EU-Humira to MSB11022. The record lists one death in the EU-Humira/EU-Humira group and none in the other extended-period groups. These groups reflect different treatment histories and selection into the extended phase, so their raw counts are not a simple randomized comparison of the initial treatments.

The listed serious-event terms include cardiac failure, hypertensive cardiomyopathy, mitral valve incompetence, myocardial infarction, conjunctival cyst, and appendicitis. The registry record does not provide enough detail to establish causality or make a comparative safety conclusion. Counts should be read as reported events in the named groups, not as proof that treatment caused or prevented an event.

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

The primary result shows that PASI 75 response was common in both per-protocol groups at Week 16: 89.7% for MSB11022 and 91.6% for EU-Humira. The recalculated unadjusted comparison is close to zero, but its confidence interval includes zero and extends in both directions. The posted data therefore leave uncertainty about the direction and size of the difference in this analysis population.

The result does not establish that the treatments are identical. A failure to distinguish a difference in an unadjusted comparison is not proof of equivalence. The sponsor’s analysis is labelled as equivalence, but the registry record does not report the equivalence margin or method needed to assess that formal claim. The sponsor’s result should be treated as the reported analysis, while recognizing that the information needed to evaluate its criterion is incomplete.

The finding also does not, by itself, settle questions about outcomes other than Week 16 PASI 75. The secondary outcomes address different measures and time points, and their multiplicity plan and missing-data handling are not reported. The safety counts are descriptive and do not establish causation. Neither the primary endpoint nor these counts provide a complete account of every potential benefit or harm.

General statistical explanation: an estimate applies to the population and analysis method used to produce it. Here, the primary endpoint population is per protocol, not all enrolled participants. The result should therefore be understood as a comparison among participants included in that defined analysis set. The registry record does not show how alternative populations or missing-data assumptions would change the estimate.

These findings are statistical descriptions of posted trial results. They are not medical advice and do not determine what treatment is appropriate for an individual. The record supports a careful reading of the Week 16 responder proportions and their uncertainty, rather than a claim that one treatment works or does not work.

18. Why This Trial Matters Statistically

This trial illustrates why a similar-looking pair of response percentages is not enough to establish a precise comparison. The primary endpoint is a binary threshold: participants either achieved PASI 75 or did not. The group percentages give an accessible summary, while the confidence interval communicates how uncertain the between-group estimate remains. Reading both is essential to avoid treating a small point estimate as proof of no difference.

It also illustrates the importance of distinguishing an equivalence analysis from an ordinary test for a difference. Equivalence requires a prespecified acceptable range and an analysis that evaluates whether the confidence interval falls within that range. The registry labels the sponsor’s analysis as equivalence, but does not report the margin or method. The label and reported interval are informative, but are not enough to independently verify the formal criterion.

The analysis population is another key statistical detail. The primary endpoint uses a per-protocol set, while the trial enrolled 443 participants overall. Interpretation depends on understanding which participants contributed to the endpoint and how exclusions and missing outcomes were handled. The registry record defines the per-protocol population but does not report all details needed to assess the impact of exclusions or missing data.

Finally, the many listed outcomes make multiplicity relevant. Secondary measures can add context, but without a reported testing strategy they should not be treated as a collection of independent confirmatory tests. The record is a useful example of how endpoint definition, analysis population, uncertainty, sponsor analysis, and reporting completeness all shape the statistical meaning of a clinical trial result.

19. Limitations

The registry record leaves several trial-specific statistical details unavailable. It does not report the original sample-size justification, the full statistical analysis plan, the method used for the sponsor’s primary analysis, or the equivalence margin. As a result, the formal basis for the sponsor’s equivalence assessment cannot be fully evaluated from the posted record.

The primary endpoint is reported for a per-protocol population. The registry defines that population but does not give a complete account of exclusions by reason or a corresponding intention-to-treat primary estimate. Missing-data handling for the primary endpoint is not reported. These gaps limit evaluation of how the analysis population and incomplete Week 16 observations may affect the result.

The record lists many outcome measures, but does not report a multiplicity strategy. It also does not report interim analyses or stopping rules. Without those details, the extent to which the endpoints and analyses were prespecified and how repeated testing was handled cannot be assessed from the registry record.

Interpretation of the extended-period results is also constrained by the design described in the record. Continued treatment and re-randomization were conditional on achieving PASI 50 during the core period, and later groups had different treatment histories. Those groups should not be treated as if they were a direct continuation of the original two-arm randomized comparison. The record does not provide complete methods for all extended-period analyses.

Finally, adverse-event counts are descriptive. The registry information cited for serious events does not establish causality, and raw counts across groups with different denominators and treatment histories do not alone establish comparative safety. These limitations do not negate the posted findings; they define what can and cannot be concluded from the registry record.

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

NCT02660580 is a completed, randomized, double-blind, parallel-group Phase 3 trial comparing MSB11022 with EU-Humira in adults with moderate to severe chronic plaque psoriasis. Overall enrollment was 443. The primary endpoint was the percentage achieving PASI 75 at Week 16 in a per-protocol analysis set.

Reported Week 16 response was 89.7% for MSB11022 and 91.6% for EU-Humira. The recalculated unadjusted comparison has a risk difference of 0.020, a confidence interval from -0.038 to 0.077, and an unadjusted p-value of 0.503. The sponsor’s result is labelled as an equivalence analysis, but the registry record does not report its method or equivalence margin.

The record includes a range of secondary outcomes and safety results. Multiplicity procedures, missing-data methods, and the original sample-size justification are not reported. These omissions limit assessment of the full statistical plan and the formal interpretation of the posted analyses.

Clinical Biostats