The Efficacy and Safety of Atacicept in Combination With Mycophenolate Mofetil Used to Treat Lupus Nephritis: Complete Statistical Analysis

1. Trial at a Glance

This page covers the registry results for The Efficacy and Safety of Atacicept in Combination With Mycophenolate Mofetil Used to Treat Lupus Nephritis (NCT00573157), a randomized phase 2, phase 3 study. The primary outcome is Percentage of Participants With Confirmed Complete Renal Response (CRR), Partial Response, and Non-response.

2. Clinical Question

3. Trial Design

The registry classifies this as a Phase 2/3 study with randomized allocation, double masking, and a parallel-group model. It was placebo-controlled and included two named regimens: atacicept plus mycophenolate mofetil plus corticosteroids, and placebo plus mycophenolate mofetil plus corticosteroids. With a parallel design, participants are assigned to a group and the groups are compared; the registry record does not describe the randomization procedure or allocation concealment in further detail.

The record gives an enrollment of 6. The study status is terminated. Its start is recorded as 2007-12 and primary completion as 2009-04. The registry attributes early termination to unanticipated safety issues. It does not report further details about the timing or nature of the issues, the decision process, or whether any additional participants were screened or enrolled.

The registry identifies EMD Serono as sponsor. Its brief summary says the study was sponsored by Merck Serono International and that operational oversight was provided by ZymoGenetics. The record does not explain the relationship among these organizations. The arm descriptions do not provide dosing or administration details, and the record does not report eligibility criteria, recruitment locations, or baseline participant characteristics.

The intended primary assessment was at Week 52 and used confirmed renal-response categories. The record also lists normalization of renal function and new lupus flares as secondary outcomes. Although the record lists these measures, the primary outcome description states that the measure was not assessed because of early termination. No comparative efficacy results or analyses are reported in the registry record. The design therefore describes an intended randomized comparison, but the available record does not provide an outcome-based estimate of the treatment contrast.

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

Reasons for not completing this period:

Analysis population for the primary outcome, as defined in the registry: Due to early termination of the study caused by unanticipated safety issues, the outcome measure was not assessed.

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: Baseline analysis population included all the participants randomized in the trial.

6. Primary Endpoint

The registry lists the primary outcome as Percentage of Participants With Confirmed Complete Renal Response (CRR), Partial Response, and Non-response, measured over At Week 52.

The primary endpoint was the percentage of participants assigned to each of three categories at Week 52: confirmed complete renal response, partial response, and non-response. The categories were intended to capture different patterns of kidney-function and urine findings. Complete renal response required renal function, assessed by calculated glomerular filtration rate, to return to within 10% of normal; improvement in proteinuria to a urine protein/creatinine ratio below 0.5; and resolution of hematuria. Partial response required no more than 10% worsening in renal function, 50% improvement in proteinuria, and resolution of hematuria. Non-response meant neither response definition was met, with treatment failure also described as non-response.

The endpoint combines kidney-function and urine findings rather than relying on a single measure. Such composite response categories can summarize several clinically relevant features, while making clear that different components contribute to the classification. A complete response is more stringent than a partial response under the stated definitions. The registry describes confirmation rules using assessments around Week 48, Week 52, and Week 56, rather than treating a single Week 52 classification as sufficient in every circumstance.

The registry record says the outcome measure was not assessed because the study was terminated early due to unanticipated safety issues. It therefore reports no percentages for the three categories and no treatment comparison. The endpoint’s definition explains what the study intended to measure; it does not establish how participants were classified or whether either regimen changed renal outcomes.

7. Why No Re-analysis Is Shown

8. Statistical Interpretation

9. Statistical Methods Explained

The record describes a randomized, double-blind, parallel, placebo-controlled study. These design features define the intended comparison, but the record does not report a detailed statistical analysis plan. The primary endpoint is categorical, with participants classified as having confirmed complete renal response, partial response, or non-response at Week 52. The central statistical task would have been to describe and compare the distribution across those categories between the randomized groups. The registry does not report such a comparison.

What randomization contributes

In general, random assignment aims to make treatment groups comparable at the point of assignment with respect to both measured and unmeasured characteristics. It supports an interpretation of group differences as related to assignment, provided that follow-up, outcome measurement, and analysis are handled appropriately. Randomization does not guarantee balance in every realized study, especially with a small enrollment. The record gives an enrollment of 6 but does not describe the randomization method, any stratification factors, or the baseline characteristics needed to evaluate group comparability.

What masking contributes

Double masking generally means that treatment assignment is concealed from more than one relevant party, which can reduce the risk that expectations influence care, reporting, or outcome assessment. The registry labels the study double-blind, but does not identify the masked parties or explain how masking was maintained. It also does not report whether masking was assessed or whether it was interrupted.

How the response endpoint works

The endpoint assigns each participant to one of three response categories, using multiple renal measures. General statistical interpretation of a categorical endpoint depends on both the number of participants in each category and the denominator used to calculate each percentage. A comparison of the category distributions would need to account for the small group sizes and to follow a prespecified analysis method. The registry gives the clinical definitions and timing but does not report the category counts or the method planned for comparing groups.

The definition includes a confirmation rule. A complete renal response at Week 52 was to be confirmed by a complete response at Week 48 when that assessment was available and at least 4 weeks apart from Week 52. If the Week 48 assessment was missing or less than 4 weeks from Week 52, the Week 56 response was to be used for confirmation. If the Week 52 value was missing, Week 48 and Week 56 both had to show complete response. These rules describe endpoint confirmation; they do not specify a general method for handling all missing observations or other outcome categories.

What uncertainty would mean

In general, an estimate describes the observed treatment contrast, while a confidence interval communicates the range of values compatible with the data under the chosen statistical method. A p-value addresses compatibility with a specified null hypothesis under model assumptions; it is not a measure of clinical importance. These concepts require an observed estimate and a defined analysis. The registry record reports neither a primary comparison nor an interval or p-value, so these quantities cannot be interpreted for renal response.

For event counts, sparse data create substantial uncertainty about the underlying frequency of events in a broader population. General methods for sparse categorical data may differ in their assumptions and performance from methods suited to larger samples. The registry record does not report inferential tests or adjusted estimates for the adverse-event counts. The counts should therefore be read descriptively, without treating them as precise estimates of comparative risk.

What the planning assumptions do and do not establish

The record describes a planning-illustration framework using a two-sided significance level of 0.05, equal allocation between the groups, and a normal approximation. It says that the effect to detect is expressed as a stated fraction of the observed effect. In general, such calculations explore the sample size associated with assumed effects and modeling choices; they are not observed power and are not evidence that a study was adequately powered. The record does not report the study’s own sample-size justification, and the primary endpoint was not assessed. No numerical planning result or usable observed primary effect is reported in the registry record, so the illustration assumptions do not resolve the uncertainty about the intended efficacy comparison.

Overall, the design labels and endpoint definition identify the intended analysis question, but key statistical implementation details are absent. The record does not report the statistical model or test, estimand, confidence-interval method, analysis population, covariate adjustment, or handling of intercurrent events. Those omissions limit any attempt to reconstruct or evaluate an analysis beyond the descriptive information in the registry.

10. Multiplicity, Missing Data and Analysis Populations

The study lists a primary measure with three response categories and two secondary outcomes: normalization of renal function and new lupus flares. Considering multiple outcomes or categories can raise a multiplicity issue: when several hypotheses are tested, the chance of at least one apparently unusual result can increase unless the analysis plan accounts for the testing strategy. The registry record does not report a multiplicity procedure, a hierarchy among outcomes, or a plan for interpreting secondary analyses. It also reports no analyses, so no adjustment or unadjusted testing result can be evaluated.

Missing-data information is limited. The primary endpoint description gives rules for confirming complete renal response using Week 48, Week 52, and, in specified circumstances, Week 56 assessments. These are endpoint-specific confirmation rules, not a general missing-data strategy. The registry record does not report how missing measurements for partial response or non-response were handled, whether participants who discontinued treatment were followed for outcomes, or how missing data were addressed in any group comparison. It also does not report the analysis populations or denominators for the intended efficacy endpoint.

Early termination is particularly relevant because the stated primary outcome was not assessed. The record does not report which participants had measurements at each scheduled time, or whether any partial outcome data were collected before termination. Without such information, the extent and pattern of missingness cannot be characterized. Statistical methods for missing data rely on assumptions about why observations are missing; those assumptions cannot be assessed from the registry record. No imputation approach, sensitivity analysis, or treatment of post-termination observations is reported. Consequently, neither multiplicity control nor the potential impact of missing outcome data can be evaluated from the posted results.

11. Safety Results

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

Other (non-serious) adverse events

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

Most frequent serious adverse event terms

Most frequent non-serious adverse event terms

Serious events with the highest arm-level rate: pneumothorax (25.0%), pulmonary embolism (25.0%), syncope (25.0%), anaemia (25.0%), empyema (25.0%).

The registry reports serious adverse events among 3 of 4 participants at risk in the atacicept plus mycophenolate mofetil plus corticosteroids group, and among 0 of 2 at risk in the placebo plus mycophenolate mofetil plus corticosteroids group. For other adverse events, it reports 4 of 4 participants at risk in the atacicept-containing group and 1 of 2 in the placebo-containing group. These are participant counts within the registry’s stated risk sets; they are not adjusted comparisons, and they do not establish the cause of an event.

The record lists pneumothorax, pulmonary embolism, syncope, anaemia, empyema, and pneumonia among the top serious-event terms, each paired with 25.0%. It does not make clear in this listing which treatment group each term belongs to, whether participants could contribute more than one term, or the detailed event-level circumstances. Death counts are not reported in the registry record.

The study was terminated early because of unanticipated safety issues, but the record does not state which specific events led to that decision. The counts should be read as a limited descriptive account from a small study, not as precise estimates of event frequency or proof of a causal difference between regimens.

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

The record establishes that a randomized, double-blind, placebo-controlled comparison was intended, and that the primary renal-response outcome was defined for assessment at Week 52. It also records that the study was terminated early because of unanticipated safety issues and that the primary outcome measure was not assessed. These registry entries describe the study’s status and the limits of the available outcome evidence; they do not answer whether the atacicept-containing regimen changed renal response.

In particular, absence of an assessed primary outcome is not evidence that there was no treatment effect. There is no reported response distribution, estimate of between-group difference, confidence interval, or p-value from which to determine the direction or precision of an efficacy contrast. The secondary outcomes listed in the registry likewise do not have reported comparative results. The intended clinical question therefore remains unresolved in this record.

The adverse-event counts provide descriptive information for the recorded risk sets, but they do not by themselves establish that a regimen caused an event or explain why the study was stopped. The record’s reference to unanticipated safety issues is important context, while the specific events, decision rationale, and causal assessments are not reported in the registry record. The listed serious-event terms should not be treated as a complete account of the safety review.

More generally, a randomized design is useful for comparing assigned regimens, but design features cannot replace observed endpoint data. The enrollment of 6 and the early termination constrain the amount of information available. The record does not describe baseline characteristics, follow-up completeness, or analysis populations, which further limits interpretation. The appropriate conclusion is narrowly descriptive: the intended efficacy endpoint was not assessed, and the posted results do not permit a reliable statistical comparison of renal response.

13. Why This Trial Matters Statistically

This trial is statistically notable because it has a clear randomized comparison and a detailed composite renal-response definition, yet the registry record says the primary endpoint was not assessed. It illustrates the distinction between a planned estimand and an observed result. A precise endpoint definition can make the intended question understandable, but it cannot generate evidence when outcome measurements and a treatment comparison are not reported.

The study’s early termination also matters for interpretation. The stated reason was unanticipated safety issues, but the record does not provide details sufficient to connect those issues to particular events or treatment assignments. In statistical reporting, this distinction prevents the reason for stopping from being mistaken for a quantified treatment effect. The safety counts remain descriptive, and the record does not report an efficacy analysis that could be weighed against them.

The enrollment of 6 underscores how limited the reported participant experience is. Small samples generally yield imprecise estimates and make group-level patterns sensitive to the experience of individual participants. Here, the main endpoint has no reported estimate at all, so the issue is not merely wide uncertainty around a comparison; the comparison is unavailable in the registry record.

The case also highlights the value of reporting analysis populations, missing-data handling, multiplicity plans, and uncertainty estimates. These details help readers distinguish an unassessed outcome from a null result and assess how much the data can support. Their absence, alongside early termination, means the registry is informative about design, endpoint definitions, and limited safety counts, but not about the primary efficacy contrast.

14. Limitations

• The posted summary statistics are the only data these results rest on; patient-level data, full protocols and statistical analysis plans are not available.
• Recalculated results are simple, unadjusted calculations from posted summaries. They do not replace the sponsor's prespecified analysis.

The most consequential limitation is explicit: early termination due to unanticipated safety issues meant the primary outcome was not assessed. The registry therefore supplies no primary response counts or comparative efficacy estimate. The enrollment was 6, and the record does not report how many participants had complete follow-up at the intended Week 52 assessment.

The record does not provide detailed eligibility criteria, baseline characteristics, treatment doses, treatment duration, adherence, or concomitant-care information beyond the named mycophenolate mofetil and corticosteroids. It also does not describe randomization implementation, the specific parties who were masked, or whether masking was maintained. These omissions limit assessment of the enrolled population and the conduct of the intended comparison.

Statistical reporting is also limited. The record does not report the analysis plan, analysis populations, model or test, confidence intervals, p-values, multiplicity strategy, or general missing-data approach. Although the primary endpoint description gives rules for confirmation of complete renal response, it does not establish how other missing measurements or post-termination data would have been handled. The listed secondary outcomes have no reported results.

Safety information is sparse and descriptive. The record gives group-level counts and a list of serious-event terms, but does not report event-level timing, severity detail beyond the serious classification, causal assessments, or the specific safety issues that prompted termination. Death counts are not reported in the registry record. Together, these limitations prevent a detailed assessment of comparative efficacy or safety from the registry record alone.

15. Related Tutorials

16. Related Statistical Calculators

17. Sources

• ClinicalTrials.gov: The Efficacy and Safety of Atacicept in Combination With Mycophenolate Mofetil Used to Treat Lupus Nephritis — NCT00573157.
• Registry record last updated 2016-03-23; status last verified 2016-02.
• Results first posted 2016-03-23.
• Data retrieved from ClinicalTrials.gov on 2026-11-09.
• Group sizes, means, event counts and sponsor-reported p-values are reproduced as posted. Effect estimates, confidence intervals and p-values not attributed to the sponsor are independently calculated from the posted summary statistics.

18. Record Summary

This registry record concerns a Phase 2/3 randomized, double-blind, parallel, placebo-controlled study of atacicept combined with mycophenolate mofetil and corticosteroids for lupus nephritis. The comparison group received placebo with mycophenolate mofetil and corticosteroids. Enrollment was 6; the recorded start was 2007-12, primary completion was 2009-04, and the status is terminated.

The intended primary outcome was the percentage of participants with confirmed complete renal response, partial response, or non-response at Week 52. The registry says this measure was not assessed because early termination followed unanticipated safety issues. It lists normalization of renal function and new lupus flares as secondary outcomes but reports no analyses. Descriptive adverse-event counts are recorded for the two groups; deaths are not reported in the registry record. The available record documents the intended design and endpoint, but does not provide a primary efficacy comparison.