← Clinical Trials
HIV Infections Phase 4 Binary Endpoint NCT00931463

A Trial of 2 Options for Second Line Combination Antiretroviral Therapy Following Virological Failure of a Standard Non-nucleoside Reverse Transcriptase Inhibitor (NNRTI)+2N(t)RTI First Line Regimen: Complete Statistical Analysis

A randomized, open-label trial compared ritonavir-boosted lopinavir with a 2N(t)RTI backbone against ritonavir-boosted lopinavir with raltegravir after first-line NNRTI/2N(t)RTI virological failure. The primary outcome was plasma HIV RNA below 200 copies/mL at 48 weeks.

Trial start: 2009-09  ·  Enrollment: 558  ·  Sponsor: Kirby Institute
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 Trial of 2 Options for Second Line Combination Antiretroviral Therapy Following Virological Failure of a Standard Non-nucleoside Reverse Transcriptase Inhibitor (NNRTI)+2N(t)RTI First Line Regimen (NCT00931463), a randomized phase 4 study. The primary outcome is Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization.

558
Enrollment
Phase 4
2
Arms
In the primary outcome
+1.8 pts
Risk difference
Ritonavir-boosted Lopinavir and Raltegra
-4.7 to 8.3 pts
95% CI
Two-sided
FeatureRegistry value
ClinicalTrials.gov identifierNCT00931463
PhasePhase 4
ConditionHIV Infections
AllocationRandomized
Design modelParallel
MaskingNone (open label)
Enrollment558
Arms in the primary outcome2
Lead sponsorKirby Institute
Results postedYes

2. Clinical Question

Population

Participants with HIV infection who were virologically failing first-line NNRTI/2N(t)RTI therapy. The primary outcome is reported for a modified intention-to-treat population; the registry record does not report the precise definition of that population.

Intervention

Ritonavir-boosted lopinavir and raltegravir, described in the registry record as the experimental arm. The study rationale proposed this combination as an option likely to remain fully active in the presence of N(t)RTI mutations, with preliminary evidence suggesting potency and durability.

Comparator

Ritonavir-boosted lopinavir and 2N(t)RTI. The registry record describes this combination as the current standard of care for second-line therapy following failure of standard first-line NNRTI+2N(t)RTIs according to WHO guidelines.

Primary question

At 48 weeks after randomization, how did the number of participants with plasma HIV RNA < 200 copies/mL compare between the two regimens? The investigators hypothesized that the lopinavir and 2N(t)RTI regimen would offer comparable virological efficacy to lopinavir and raltegravir.

The clinical question is a comparison of two active combination regimens in a second-line treatment setting after virological failure, not a comparison with no treatment. The endpoint focuses on virological suppression at a specified follow-up time. It does not by itself cover the other outcomes named in the registry record, including immunological, safety, clinical, metabolic, adherence, resistance, or quality-of-life outcomes.

The posted primary results report suppression counts for each randomized arm and a risk difference comparing raltegravir with 2N(t)RTI. Those results describe the observed endpoint in the stated analysis population. They do not establish that the regimens are equivalent: interpreting comparability requires attention to the uncertainty around the estimated difference and to whether a non-inferiority or equivalence margin was specified. Such a margin is not reported in the registry record.

3. Trial Design

This was a phase 4, randomized, open-label, parallel-group study. The registry record lists an enrollment of 558. Participants were assigned to ritonavir-boosted lopinavir with 2N(t)RTI or ritonavir-boosted lopinavir with raltegravir. Masking is listed as none, so the trial was open-label rather than blinded.

The study was planned to run for 96 weeks, with the primary endpoint analyzed after 48 weeks. The primary completion date is listed as 2012-09, and the trial status is completed. The registry record lists the start as 2009-09 and the sponsor as the Kirby Institute. The primary outcome compares the number of participants with plasma HIV RNA < 200 copies/mL at 48 weeks after randomization.

The primary result is labeled modified intention-to-treat. The registry record does not describe the exact rules used to define this population, such as how post-randomization exclusions or missing endpoint values were handled. Four secondary outcome descriptions are posted, including per-protocol analyses, a per-protocol analysis classifying non-completers as failures, and per-protocol analyses by baseline viral-load category. The posted results do not include reported analyses for those outcomes.

The registry record identifies the allocation as randomized but does not report the sequence-generation method, allocation concealment, or details of how assignment was implemented. It also does not report the original sample-size justification, the target difference used in planning, or a statistical analysis plan. These details matter when judging how closely the posted outcome analyses follow the trial's original design and how the study was intended to assess the hypothesis of comparable efficacy.

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: 558 participants were enrolled in the study. 14 were excluded because of unverifiable data at one site and 3 dropped out before analysis, never received study treatment

Overall Study

StageRitonavir-boosted Lopinavir and 2N(t)RTIRitonavir-boosted Lopinavir and Raltegravir
STARTED271270
COMPLETED254265
NOT COMPLETED175

Reasons for not completing this period:

ReasonRitonavir-boosted Lopinavir and 2N(t)RTIRitonavir-boosted Lopinavir and Raltegravir
Death84
Withdrawal by Subject50
Lost to Follow-up41

Analysis population for the primary outcome, as defined in the registry: modified intention-to-treat

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.

CharacteristicUnitRitonavir-boosted Lopinavir and 2N(t)RTIRitonavir-boosted Lopinavir and RaltegravirTotal
Participants analysed2712701082
Age, Continuousyears39 (SD 8.81)38.55 (SD 8.84)38.78 (SD 8.82)
Sex: Female, Male: FemaleParticipants115128243
Sex: Female, Male: MaleParticipants156142298
Region of Enrollment: Africaparticipants10096196
Region of Enrollment: Southeast Asiaparticipants116113229
Region of Enrollment: Europeparticipants123
Region of Enrollment: Australiaparticipants101
Region of Enrollment: South Americaparticipants5359112

6. Primary Endpoint

The registry lists the primary outcome as Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, measured over 48 weeks following randomization.

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

The primary endpoint counts participants whose plasma HIV RNA was below 200 copies/mL 48 weeks after randomization. It is a binary outcome at the participant level: each participant either meets the stated suppression threshold at the specified time or does not. The registry record reports counts in the modified intention-to-treat population, with 219 of 271 in the lopinavir and 2N(t)RTI arm and 223 of 270 in the lopinavir and raltegravir arm.

A threshold-based virological endpoint gives a clinically interpretable way to compare whether participants achieved suppression at a fixed follow-up point. It reduces a laboratory measurement to a yes-or-no outcome, which can be summarized as a proportion in each arm and contrasted using a risk difference. That convenience comes with a limitation: it does not show how far above or below the threshold individual viral-load values were, or how suppression changed over time. Those details are not included in the primary result.

The endpoint is used as the primary outcome because the study question concerns virological suppression after second-line therapy. The registry record also names other outcome domains, but the primary endpoint alone cannot summarize safety, resistance, adherence, quality of life, or longer-term clinical outcomes. The 48-week result is therefore evidence about the specified virological measure at that time, rather than a complete account of every potential benefit or harm.

7. Results Posted in the Registry

Risk difference: Ritonavir-boosted Lopinavir and Raltegravir

+1.8

95% CI: -4.7 to 8.3 percentage points

Recalculated from the posted summary statistics

Primary outcome by arm, with 95% confidence intervals
Primary outcome by arm with 95% confidence intervals74.677.279.982.585.187.7Ritonavir-boosted Lopinavir a… (n=271)Ritonavir-boosted Lopinavir a… (n=270)% of participants (95% CI)
Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)Ritonavir-boosted Lopinavir a…-5.78-2.750.273.296.319.34risk 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
Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol PopulationBinary EndpointRisk difference+1.0 pts (-5.2 to 7.3)18,477 per arm
Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol Population, Non-completer Classed as FailureBinary EndpointRisk difference+1.0 pts (-6.0 to 8.1)26,245 per arm
Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol Population, Baseline VL >100,000 Copies Per mLBinary EndpointRisk difference+5.4 pts (-12.6 to 23.4)1,271 per arm

Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol Population

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)Ritonavir-boosted Lopinavir a…-6.21-3.31-0.422.485.388.28risk difference (percentage points) vs control (95% CI)

Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol Population, Non-completer Classed as Failure

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)Ritonavir-boosted Lopinavir a…-7.17-3.89-0.612.665.949.22risk difference (percentage points) vs control (95% CI)

Participants With Plasma HIV RNA < 200 Copies/mL 48 Weeks After Randomization, Per-protocol Population, Baseline VL >100,000 Copies Per mL

Treatment effect versus the control arm
Forest plot of risk difference (percentage points) vs control (95% CI)Ritonavir-boosted Lopinavir a…-15-7.131.219.561826risk difference (percentage points) vs control (95% CI)

The secondary outcomes examine the same 48-week virological threshold through different analysis populations and baseline viral-load categories. Taken together, their recalculated point estimates are positive, in the direction of a higher suppression proportion with lopinavir and raltegravir. Each reported interval includes zero, so none of these alternate comparisons sharply distinguishes a difference from no difference. This broad pattern is consistent with the primary result's uncertain, modest positive point estimate rather than presenting a clear reversal.

The secondary analyses are related to, but do not replace, the primary analysis. A per-protocol population asks how results look among participants included under protocol-based criteria, while the non-completer-as-failure version imposes a particular approach to participants who did not complete follow-up. The baseline viral-load analyses ask whether results look different within listed categories, but separate subgroup estimates do not by themselves show that treatment effects differ between categories. Such a claim would require an interaction assessment, which is not reported in the registry record.

These secondary results should carry less weight than the primary outcome because they are additional analyses, involve altered populations or subgroup definitions, and are not accompanied by reported sponsor analyses. Multiple looks at outcomes or subgroups increase the chance that some estimates appear notable by chance. The registry record does not report a multiplicity plan or adjusted secondary inferential results. The posted unadjusted values therefore should be interpreted as exploratory or supportive descriptions, rather than as independent confirmation of a treatment difference.

The registry record lists four secondary outcome descriptions and no reported analyses for them. The counts and recalculated comparisons make it possible to describe the pattern, but they do not reveal whether these analyses were prespecified, how missing values were handled across all versions, or whether any were designated as confirmatory. The secondary endpoints can add context about sensitivity to analysis choices, but the lack of those details means they cannot settle the primary uncertainty or establish comparability on their own.

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

9. Statistical Interpretation

Clinical Biostats interpretation

In the modified intention-to-treat analysis, plasma HIV RNA was below 200 copies/mL in 219 of 271 participants receiving ritonavir-boosted lopinavir and 2N(t)RTI, and in 223 of 270 receiving ritonavir-boosted lopinavir and raltegravir. The posted arm proportions are 0.808 and 0.826, respectively. The recalculated, unadjusted risk difference, comparing raltegravir with 2N(t)RTI, is 0.018, with a reported interval from -0.047 to 0.083. The unadjusted p-value is 0.592.

The point estimate is positive, meaning that the observed suppression proportion was higher in the raltegravir arm. The interval, however, extends across zero and includes values in either direction. The result is therefore compatible with a modest advantage for either regimen as well as little difference, within the range represented by that interval. The unadjusted p-value does not provide evidence of a statistically detectable difference under a conventional null-hypothesis test, but it does not show that the regimens are equivalent or that their effects are identical.

The investigators framed the hypothesis as comparable efficacy. A failure to detect a difference is not, by itself, a demonstration of comparability. A formal non-inferiority or equivalence conclusion generally depends on a prespecified margin and an analysis designed for that purpose. A margin, the original statistical plan, and sponsor-reported inferential analyses are not reported in the registry record. The posted estimate and its uncertainty should therefore be read as a description of the observed comparison, not as proof of equivalence.

Across the posted secondary endpoint estimates, the risk differences are also positive, while their reported intervals include zero. This broad pattern does not overturn the primary result or provide a separate, definitive demonstration of a difference. The secondary outcomes use different analysis populations or subgroup definitions, and their inferential results are not reported as sponsor analyses. Their results are best viewed as additional descriptive checks on whether the primary comparison looks broadly consistent under alternate definitions.

These are unadjusted recalculations from posted summary counts and do not replace a trial analysis using individual-level data and the original analysis plan. The registry record lists no reported analyses. No conclusion about viral-load trajectories, longer-term comparative effects, or the total balance of benefits and harms follows from the primary endpoint alone.

10. Statistical Methods Explained

What does a risk difference describe?

A risk difference subtracts the event proportion in one group from the event proportion in the other. For this trial, the comparison is oriented as ritonavir-boosted lopinavir and raltegravir relative to ritonavir-boosted lopinavir and 2N(t)RTI. A positive estimate means the event proportion is higher in the raltegravir arm; a negative estimate means it is lower. Here, the event is meeting the endpoint of plasma HIV RNA < 200 copies/mL. The primary risk difference is 0.018. It is a contrast between the observed proportions, not a statement about each participant's individual response.

Risk differences are expressed on the absolute probability scale. They can be easier to interpret as a direct comparison of event proportions than a relative measure, but their meaning still depends on the endpoint, analysis population, and follow-up time. A risk difference at 48 weeks does not describe when suppression occurred or whether it was sustained throughout follow-up.

What does an interval around an estimate add?

A confidence interval represents uncertainty in an estimated effect under the assumptions of the method used to calculate it. It gives a range of values reasonably compatible with the observed data and that method. It is not a guarantee that the true effect lies in the interval, and it does not express the probability that one treatment is better. The primary reported interval runs from -0.047 to 0.083. Because it includes zero, the results do not distinguish a zero risk difference from effects in either direction at the interval's stated level. The confidence level for the posted intervals is not reported in the registry record.

Intervals are generally more informative than a p-value alone because they show both the direction and scale of effects that remain plausible under the analysis. An interval can include zero while still allowing effects that may matter clinically. Deciding what range is clinically important requires context and, for a non-inferiority or equivalence question, a prespecified margin. The registry record does not report such a margin.

What is the role of a p-value?

A p-value measures how unusual data at least as discrepant as those observed would be under a specified null hypothesis and model. It is not the probability that the null hypothesis is true, and it does not measure the size or clinical importance of an effect. The primary unadjusted p-value is 0.592. That value does not establish sameness; it indicates that the observed contrast is not statistically distinguishable from zero by this unadjusted test. The registry record does not report a sponsor analysis or a complete inferential plan, so the recalculated p-value should not be treated as a substitute for the trial's prespecified analysis.

Why distinguish analysis populations?

The primary result is labeled modified intention-to-treat, while the posted secondary results use per-protocol populations or alternate endpoint handling. An intention-to-treat approach is generally intended to preserve the benefits of random assignment by analyzing participants according to their randomized groups. A modified version may apply exclusions or other rules; the specific definition is not reported in the registry record. A per-protocol analysis generally focuses on participants meeting protocol-defined conditions, but the conditions and exclusions used in this trial are not described in the registry record.

Different analysis populations can produce different denominators and estimates because they include different sets of participants or handle endpoint availability differently. Such analyses can help assess robustness, but they can also lose some protection against bias associated with randomization. In this trial, one secondary endpoint explicitly classifies non-completers as failures. That is a different missing-outcome assumption from simply analyzing observed outcomes, and it is informative as a sensitivity approach only if interpreted as such. The exact handling of other missing data is not reported.

Why do these recalculations have limits?

The posted risk differences, intervals, relative measures, and unadjusted p-values are simple unadjusted recalculations from the registry's summary statistics. They do not adjust for baseline characteristics, account for any design features beyond the posted information, or use individual participant data. The registry record does not report adjusted analyses, the confidence-interval method, or the statistical model used for a sponsor analysis. Since no reported analyses are listed, the recalculations are a transparent descriptive aid rather than a replacement for the trial's own prespecified methods.

Binary outcomes count participants meeting a definition, rather than measuring a continuous distribution. This makes interpretation depend on the threshold and on how participants without a measured endpoint are treated. The primary threshold is stated, but the modified intention-to-treat rules are not. The secondary results offer some alternate population and missing-outcome definitions, yet do not resolve every uncertainty about endpoint ascertainment or analysis choices. Those methodological limits should be kept in view when comparing estimates or drawing conclusions from the trial.

11. Confidence Intervals and Precision

The primary risk difference is 0.018, with a reported interval from -0.047 to 0.083. Its span across zero indicates that the observed data do not pin down the direction of the difference. The interval allows values favoring either arm, as well as values close to no difference. The arm proportions, 0.808 for lopinavir and 2N(t)RTI and 0.826 for lopinavir and raltegravir, are close as point estimates, but point estimates alone do not convey how uncertain the comparison is.

The interval is the main guide to precision: a range extending in both directions should not be read as evidence that the regimens have identical effects. Nor does the interval establish that any particular effect within its bounds is clinically important. Clinical interpretation would require a judgment about what difference matters, and an equivalence or non-inferiority assessment would require a suitable prespecified margin. Neither is reported in the registry record. The confidence level and calculation method for the posted interval are also not reported in the registry record.

The secondary intervals likewise include zero, with some extending across a broad range of possible differences. The per-protocol subgroup defined by baseline viral load has less information than the overall primary analysis, reflected in a notably broad interval, so its estimate is especially uncertain. These secondary estimates should not be used to claim a subgroup-specific effect without a prespecified interaction analysis, which is not reported in the registry record.

Precision is distinct from statistical significance and from clinical importance. A narrow interval would indicate more precise estimation, while a broad interval leaves more uncertainty. The primary result provides an estimate in the positive direction but does not tightly determine the true difference or rule out effects in the other direction. The registry record's absence of sponsor-reported analyses and details of the interval method further limits what can be inferred about the precision calculation.

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 effect7,4009,905
75% of the observed effect13,27917,776
50% of the observed effect30,15540,369
Sample size needed versus the size of the effect to detect
Sample size needed versus size of effect to detect5,00010,00020,00050,000100,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: Ritonavir-boosted Lopinavir and Raltegravir.

The planning illustration is based on the primary observed effect and gives participants per arm, not a total across arms or a count of events. Its stated 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 set to the stated fraction of the observed effect. The original trial's own sample-size assumptions and justification are not reported in the registry record.

For planning at 100% of the observed effect, the illustration gives 7,400 participants per arm for 80% power and 9,905 participants per arm for 90% power. For planning at 75% of the observed effect, it gives 13,279 participants per arm for 80% power and 17,776 participants per arm for 90% power. For planning at 50% of the observed effect, it gives 30,155 participants per arm for 80% power and 40,369 participants per arm for 90% power.

In plain terms, the 80% power column describes a planning target intended to give the specified test an 80% chance of detecting the assumed effect if that effect were the true one and the stated assumptions held. The 90% column uses a higher detection probability under the same kind of planning assumptions. Smaller effects are harder to distinguish from random variation, so planning for a smaller fraction of the observed effect requires more participants per arm. The curve represents this general relationship between the assumed effect size and the number of participants needed.

These figures are planning illustrations, not observed power. They are derived from the observed effect for illustration and do not establish the rationale used when the trial was originally designed. In particular, they should not be used to conclude that the completed trial was adequately or inadequately powered without the original target effect, planned analysis, and design assumptions.

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.808; treatment proportion p1 = 0.826; average p̄ = 0.817.
  2. First term: z1−α/2 × √[2p̄(1−p̄)] = 1.96 × 0.5468 = 1.0717.
  3. Second term: z1−β × √[p0(1−p0) + p1(1−p1)] = 0.842 × 0.5467 = 0.4601.
  4. n = (1.0717 + 0.4601)2 / (0.0178)2 = 7,399.1, rounded up to 7,400 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.808118081180812                          # control proportion
p1 <- 0.825925925925926                          # 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(931463)
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 = 7,400 (80% power), 9,905 (90% power)
 75% of observed effect: n per arm = 13,279 (80% power), 17,776 (90% power)
 50% of observed effect: n per arm = 30,155 (80% power), 40,369 (90% power)
power.prop.test: 7399.1 
Simulated power at n = 7,400 per arm: 0.802 (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 does not report a multiplicity strategy for the primary and secondary outcomes, a hierarchy of hypotheses, or a plan for controlling the chance of false-positive findings across multiple tests. Without such information, unadjusted secondary p-values should be treated cautiously. When many outcomes, populations, or subgroups are examined, the chance of at least one apparently notable result can increase even if there is no real effect. That general concern applies to interpreting a collection of secondary analyses, but the registry record does not establish how many were planned beyond the listed outcome descriptions.

The record lists no reported analyses. It therefore does not provide sponsor-reported model results, adjusted estimates, multiplicity-adjusted p-values, or a complete statistical analysis plan. The comparison statistics discussed for the posted outcomes are recalculated, unadjusted summaries. Whether they correspond to the original prespecified analysis is not reported in the registry record.

Missing-data handling is only partly visible from the outcome descriptions. The primary result is labeled modified intention-to-treat, but the exact definition and handling of participants without an available 48-week measurement are not reported. One secondary outcome explicitly classifies non-completers as failures. This is a meaningful sensitivity definition, but the registry record does not state how other missing observations were treated, whether missingness was common for particular reasons, or whether additional approaches were used.

The primary modified intention-to-treat and secondary per-protocol populations answer related but not identical questions. Modified intention-to-treat analyses can exclude some randomized participants depending on their definition; per-protocol analyses can also depart from the original randomized groups. The registry record does not report the rules behind these populations, so the potential impact of exclusions cannot be fully assessed. The posted denominators show which counts were used in each summary, but do not explain why participants were or were not included.

Interim analyses, stopping rules, sequence generation, allocation concealment, and the original sample-size justification are not reported in the registry record. Their absence does not show that these procedures were absent from the trial; it means their details cannot be evaluated from this record. Together, these missing analysis and design details limit assessment of prespecification, missing-data bias, and the strength of inferences from the secondary results.

15. Safety Results

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

ArmParticipants with serious adverse eventsParticipants at riskPercentage
Ritonavir-boosted Lopinavir and 2N(t)RTI232718.5%
Ritonavir-boosted Lopinavir and Raltegravir242708.9%
Participants with at least one serious adverse event
Serious adverse events by armRitonavir-boosted Lopinavir a…8.5%Ritonavir-boosted Lopinavir a…8.9%% 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 2% reporting threshold.

ArmParticipants affected of at risk
Ritonavir-boosted Lopinavir and 2N(t)RTI243 of 271
Ritonavir-boosted Lopinavir and Raltegravir232 of 270

Most frequent serious adverse event terms

Event termOrgan systemRitonavir-boosted Lopinavir and 2N(t)RTIRitonavir-boosted Lopinavir and Raltegravir
PregnancyPregnancy, puerperium and perinatal conditions5 of 2717 of 270
pneumoniaInfections and infestations3 of 2713 of 270
AnaemiaBlood and lymphatic system disorders1 of 2712 of 270
Death, cause unknownGeneral disorders and administration site conditions2 of 2711 of 270
Acute gastroenteritisGastrointestinal disorders0 of 2712 of 270
Acute Asthma AttackRespiratory, thoracic and mediastinal disorders1 of 2711 of 270
CMV RetinitisInfections and infestations1 of 2711 of 270
Pulmonary tuberculosisInfections and infestations0 of 2712 of 270
Renal failure resulted in deathRenal and urinary disorders2 of 2710 of 270
Abdominal Pain- deathGastrointestinal disorders1 of 2710 of 270

Most frequent non-serious adverse event terms

Event termOrgan systemRitonavir-boosted Lopinavir and 2N(t)RTIRitonavir-boosted Lopinavir and Raltegravir
Gastrointestinal motility and defaecation conditionsGastrointestinal disorders128 of 271102 of 270
Infections - pathogen class unspecifiedInfections and infestations103 of 271124 of 270
Epidermal and dermal conditionsSkin and subcutaneous tissue disorders66 of 27166 of 270
Gastrointestinal signs and symptomsGastrointestinal disorders72 of 27151 of 270
Respiratory disorders NECRespiratory, thoracic and mediastinal disorders51 of 27158 of 270
Musculoskeletal and connective tissue disorders NECMusculoskeletal and connective tissue disorders39 of 27144 of 270
Viral infectious disordersInfections and infestations40 of 27141 of 270
Fungal infectious disordersInfections and infestations33 of 27147 of 270
HeadachesGeneral disorders and administration site conditions41 of 27130 of 270
General system disorders NECGeneral disorders and administration site conditions34 of 27133 of 270

Serious events with the highest arm-level rate: pregnancy (2.6%), pneumonia (1.1%), acute gastroenteritis (0.7%), anaemia (0.7%), pulmonary tuberculosis (0.7%).

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 record reports serious adverse events in 23 of 271 participants receiving ritonavir-boosted lopinavir and 2N(t)RTI, and in 24 of 270 receiving ritonavir-boosted lopinavir and raltegravir. These are counts of participants recorded with serious adverse events, not a complete description of event timing, duration, severity patterns, or causal attribution. The registry record does not report death counts in the adverse-event summary.

The serious-event terms listed include Pregnancy (2.6%), pneumonia (1.1%), Acute gastroenteritis (0.7%), Anaemia (0.7%), Pulmonary tuberculosis (0.7%), and Death, cause unknown (0.7%). These percentages are listed as serious-event terms; the registry record does not provide the term-specific denominators or arm-specific breakdowns alongside them. They should not be interpreted as direct comparative risks between the trial arms.

Serious adverse-event counts are useful for describing events recorded during the study, but they do not establish that a regimen caused an event or that the two regimens have the same safety profile. The record does not provide detailed comparative safety analyses, confidence intervals, event adjudication, or a full account of adverse events by severity and timing. These figures should be read as registry safety summaries, not as a complete causal assessment.

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

The posted primary result shows that suppression below the stated threshold was common in both randomized groups at 48 weeks. The observed proportions were 0.808 with ritonavir-boosted lopinavir and 2N(t)RTI and 0.826 with ritonavir-boosted lopinavir and raltegravir. The recalculated risk difference is 0.018 in the direction of the raltegravir arm, but the interval from -0.047 to 0.083 leaves uncertainty about both the direction and size of the difference.

This result does not prove that the regimens are equivalent, interchangeable, or equally effective. A non-significant unadjusted test is not an equivalence test, and the registry record does not report an equivalence or non-inferiority margin. The estimate also does not show that either regimen caused suppression in every participant, because the posted result is a group-level comparison and does not describe individual outcomes beyond the counts.

The result is limited to the specified endpoint, analysis population, and follow-up time. It does not establish longer-term durability, changes in viral load across the full study period, resistance outcomes, adherence, quality of life, metabolic effects, immunological outcomes, or clinical outcomes. Although the registry record lists these domains among secondary and exploratory endpoints, the posted results do not report their analyses. The serious adverse-event summary supplies counts and listed event terms, but not enough detail to establish causal safety differences between regimens.

A balanced reading is that the observed primary proportions are close, while the interval leaves meaningful uncertainty around the contrast. The trial's stated hypothesis was comparable efficacy, but a conclusion about comparability requires the intended margin and design-based analysis, neither of which is reported in the registry record. The available summaries can inform an understanding of the observed 48-week result, but they cannot answer every clinical or safety question about these regimens.

17. Why This Trial Matters Statistically

This trial illustrates why an observed difference, a significance test, and a claim of equivalence are distinct statistical ideas. The primary estimate favors the raltegravir arm numerically, but the reported interval crosses zero and the unadjusted p-value is 0.592. That combination does not establish a difference, yet it also does not demonstrate that the regimens perform identically. The distinction is central whenever a study question is framed around comparable efficacy.

The trial also shows how analysis populations affect interpretation. The primary summary uses a modified intention-to-treat population, while the secondary summaries include per-protocol analyses and an explicit non-completer-as-failure approach. These alternative views can test whether the broad pattern changes under different definitions, but their meaning depends on transparent population rules and missing-data assumptions. Those details are not reported in the registry record.

Finally, the posted planning illustration highlights the relationship between effect size and required sample size. When the assumed effect is reduced to a smaller fraction of the observed effect, the planning values increase. This helps explain why a small estimated difference can be difficult to assess precisely, but the illustration is not the trial's original design calculation and is not observed power. Together, the results provide a useful case for separating descriptive estimates from confirmatory claims and for asking whether registry reporting contains the design information needed to interpret each claim.

18. Limitations

The registry record does not provide an equivalence or non-inferiority margin, even though the study rationale describes comparable efficacy as the hypothesis. Without that margin and the original analysis plan, the primary result cannot establish whether the observed uncertainty meets a formal criterion for comparability. Sponsor-reported analyses are not listed, so the posted comparison rests on recalculated unadjusted summary statistics.

The definition of the modified intention-to-treat population is not reported. Nor are the reasons for missing endpoint data, the handling of missing values in the primary analysis, or the exact rules defining the per-protocol populations. The secondary analysis that classifies non-completers as failures offers one alternate approach, but does not resolve uncertainty about other missing-data assumptions or whether missingness differed by arm.

Further details relevant to evaluating conduct and analysis are not reported in the registry record, including allocation concealment, randomization implementation, the original sample-size justification, interim analyses, stopping rules, and a multiplicity plan. The confidence level and method used for the posted intervals are also not reported. These omissions limit assessment of prespecification and of how the posted summaries relate to the trial's intended analysis.

The endpoint is a thresholded measure at 48 weeks, so it does not show individual viral-load values, the timing or durability of suppression, or outcomes beyond that measurement. The secondary results are unadjusted and include subgroup analyses; they should not be treated as independent confirmation of an effect. Safety reporting is also summarized: serious-event counts and a list of terms do not provide detailed timing, attribution, or a full arm-specific account of each event. These limitations do not invalidate the posted counts, but they constrain the conclusions that can be drawn from them.

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

NCT00931463 is a completed, phase 4, randomized, open-label, parallel-group study sponsored by the Kirby Institute. It compared ritonavir-boosted lopinavir with 2N(t)RTI against ritonavir-boosted lopinavir with raltegravir in participants virologically failing first-line NNRTI/2N(t)RTI therapy. The primary endpoint was plasma HIV RNA < 200 copies/mL at 48 weeks after randomization.

In the modified intention-to-treat result, the posted proportions were 0.808 and 0.826, and the recalculated unadjusted risk difference was 0.018, with an interval from -0.047 to 0.083. The interval includes zero, so the direction and size of the difference remain uncertain. The record does not report sponsor analyses, a statistical analysis plan, or a non-inferiority or equivalence margin; the findings therefore do not establish comparable efficacy. Secondary results offer alternate analysis views, while safety summaries report serious-event counts and selected event terms without detailed comparative analysis.

Clinical Biostats