Why Interim Efficacy Displays Need a Structured Read
An interim efficacy table or plot is a snapshot, not a final verdict. Participants may have different amounts of follow-up, some may not yet have reached the endpoint assessment, and a small number of observations may noticeably affect a summary. Even an accurately calculated percentage can be misleading if its denominator or observation window is unclear.
The first task is therefore not to decide which treatment “looks better.” It is to establish what data the display summarizes, how mature those data are, and whether the displayed summaries agree with one another. These checks help a reviewer describe the pattern faithfully while avoiding conclusions that the interim information cannot support.
Start With the Endpoint, Time Point, and Denominator
Before interpreting a value, identify the endpoint, its measurement time or event definition, the data cut, and the population included in its denominator. In a trial with a response assessed at week 12, for example, a participant randomized shortly before the cut may not yet have had the opportunity to complete that assessment. A week-12 response percentage among participants assessed is not automatically the same quantity as a response percentage among everyone randomized.
Common denominators include the number randomized, the number who started treatment, the number with an assessment in the endpoint window, and the number included in a particular analysis. These are not interchangeable. A display should make clear which is used, and whether unavailable or missing outcome values are excluded or handled by a specified rule. A count of responses without its denominator is insufficient for interpreting a response proportion.
For a binary endpoint, the observed proportion among assessed participants is \(r/n_{\mathrm{assessed}}\), where \(r\) is the number meeting the endpoint and \(n_{\mathrm{assessed}}\) is the number with an evaluable assessment. This is a descriptive summary of those assessed. It does not, without further assumptions or a prespecified missing-data method, establish the response proportion in all randomized participants.
Worked Example: Seeing What an Assessed-Participant Rate Leaves Out
Suppose a hypothetical trial has 100 participants assigned to each arm at an interim cut. In arm A, 60 have a week-12 assessment and 36 of those meet the response definition. In arm B, 80 have an assessment and 44 meet the definition. For this calculation, assume the endpoint is binary and the displayed assessment counts and response counts are accurate.
Among assessed participants, the rates are:
Thus, the observed response proportions are 60.0% in arm A and 55.0% in arm B, a descriptive difference of 5.00 percentage points among assessed participants. The assessment coverage is \(60/100=60.0\%\) in A and \(80/100=80.0\%\) in B. The denominators show that the two observed proportions are based on different fractions of the randomized groups.
For arm A, 40 participants have no observed week-12 assessment in this snapshot. If one asks only what the eventual all-randomized response proportion could be under the extreme possibilities that none or all of these 40 respond, the corresponding range is \(36/100=36.0\%\) to \((36+40)/100=76.0\%\). This range is not an estimate; it illustrates how much the unobserved outcomes could matter without assumptions about them. The assessed-participant comparison alone does not resolve that uncertainty.
Assess Maturity and Follow-Up Balance
Maturity should be judged against the endpoint’s required observation period and the data cut, not inferred from enrollment totals alone. Useful display information includes the number randomized, time since randomization, number reaching the endpoint window, number assessed, and number still awaiting assessment. For a time-to-event endpoint, relevant context includes the amount and distribution of follow-up, events observed, and participants censored or still event-free at the cut. The median follow-up by itself may not reveal all differences in the follow-up distributions.
Unequal follow-up matters because participants observed for longer have had more opportunity to experience an event. Comparing raw event counts between arms with different follow-up can therefore be uninformative. A crude rate per person-time can provide a descriptive adjustment for unequal exposure time, but it does not automatically account for differences in event timing, changing risk, or informative censoring. A time-to-event curve or model-based summary may use the available event-time information differently; it still requires its own assumptions and sufficient maturity.
Worked Example: Comparing Event Rates With Unequal Follow-Up
Imagine a hypothetical interim summary of a time-to-event efficacy endpoint. Arm A has 18 events over 720 person-years of follow-up, and arm B has 16 events over 480 person-years. Assume the person-time totals use the same event definition, follow-up rules, and data cut in both arms. Compute crude event rates as events divided by accumulated person-time.
The rates are:
Although A has more observed events, it also contributes more follow-up. The descriptive rate ratio, calculated from the unrounded rates, is:
In this snapshot, the crude event rate in A is 0.750 times the crude rate in B, or 25.0% lower on this rate scale. This is not by itself a treatment-effect estimate with quantified uncertainty, and it does not establish that the eventual endpoint experience will have the same pattern. The rates do not describe when events occurred or show whether follow-up was distributed similarly across participants. A reviewer would check the time-to-event display and follow-up summaries before interpreting the crude comparison further.
Look for Influential Observations and Internal Consistency
A summary can be numerically correct yet depend heavily on one observation. This is especially important for small interim samples, continuous endpoints with extreme values, and subgroup displays. A simple diagnostic is to compare the reported summary with a version recalculated after omitting one observation at a time. This is a sensitivity check, not a license to remove an inconvenient value. An observation should be excluded only if a prespecified rule or a documented data-quality reason supports exclusion.
For a mean difference, the leave-one-out calculation makes the source of influence visible: remove one value, recompute the group mean using the remaining observations, and compare the resulting contrast with the original. If the contrast changes substantially, investigate the observation’s provenance, units, endpoint derivation, visit timing, and any relevant data query. The check does not decide whether the value is valid or what the treatment effect is.
Worked Example: A Single Value Changes the Interim Pattern
Suppose a hypothetical efficacy endpoint is improvement in a symptom score at a specified visit, measured in points, with larger positive values indicating greater improvement. At an early cut, the six recorded improvements in arm A are 8, 7, 7, 6, 6, and 30 points; in arm B they are 8, 8, 7, 7, 6, and 6 points. Assume, for this descriptive check, that all values use the same scale and visit definition.
The arm means and their difference are:
The observed mean difference, A minus B, is \(10.67-7.000=3.667\) points. Now omit the 30-point value from A solely as a diagnostic:
The contrast changes from 3.667 points favoring A on the stated scale to 0.200 points lower in A after this one-value sensitivity check. That is a reason to examine the value and the data-generating context carefully, not to discard it automatically. With only six observations per arm, both summaries are also highly unstable and should not be treated as a firm efficacy conclusion.
Consistency checks apply across the entire package. Recalculate displayed percentages from their counts and denominators; verify units, endpoint labels, visit windows, treatment-arm labels, and data-cut dates; and compare tables with plots that purport to show the same analysis. Different displays can legitimately use different populations or denominators, but that distinction must be explicit.
Worked Example: Reconciling a Percentage With Its Denominator
A hypothetical week-12 table reports 44 responses among 80 assessed participants in arm A and 39 among 75 assessed participants in arm B. Its proportions are:
A companion plot labels the same assessed-participant percentages as 55.0% for A and 50.0% for B. The A label agrees with the table, but the B label does not: 39 divided by 75 is 52.0%, not 50.0%. Before interpreting the apparent difference, verify that the plot is intended to show the same analysis and denominator. If so, the B label is inconsistent and should be checked against the validated source summary. If the plot instead uses a different analysis population, its denominator and rule need to be stated; the two values should not be compared as though they were the same quantity.
Interpret Patterns Without Overreading Them
A practical reading sequence separates data checks from efficacy interpretation:
Read the endpoint definition, time point or event rule, analysis population, and data cut before reading the displayed value.
Compare randomized, followed, endpoint-ready, assessed, and analyzed counts where relevant. Note how much information is still pending.
Review follow-up summaries and denominators across arms, and examine whether a small number of observations drives a summary.
Verify arithmetic, labels, units, dates, and whether tables and plots summarize the same analysis.
Describe the observed pattern and its limitations; do not turn an unstable or incomplete pattern into a definitive efficacy claim.
The main alternatives to a raw interim count or percentage are summaries suited to the endpoint and observation process, such as a time-to-event display or a model-based estimate. Those alternatives can be more informative about timing or adjustment, but they do not remove the need to check maturity, definitions, and assumptions. A raw rate, a curve, and a model estimate may differ for legitimate reasons; their interpretation depends on what each estimates and which data it uses.
Common failure modes include treating “not yet assessed” as “no response” without a prespecified rule, comparing event counts when follow-up differs, relying on a mean without checking extreme values, and assuming a discrepancy must indicate a treatment effect or a data error before checking populations and denominators. The correction is to trace each display back to its endpoint, data cut, analysis set, and calculation. In an adaptive trial, interim efficacy displays are particularly easy to overread because the information is still accumulating; a visually clear separation is not a substitute for checking how much and what kind of information produced it.
Check Your Understanding
Answer each question, then compare your reasoning with the brief solutions below.
- A trial has 120 participants randomized per arm. At an interim cut, week-8 assessments are available for 72 in A and 96 in B. What two distinct features should be checked before comparing response percentages among those assessed?
- Arm A has 12 events over 300 person-years and arm B has 10 events over 200 person-years. Calculate the crude rates and their ratio, A to B.
- Why is a leave-one-out change in a mean not, by itself, justification for excluding the observation?
- A table reports 27 responses among 45 assessed participants. A plot says 60%. Is the arithmetic consistent? What additional display detail should be checked?
- State one cautious interpretation of an early difference in response percentages when many participants have not yet reached the assessment time.
Solutions. (1) Check assessment coverage and the denominators, and determine whether participants had comparable opportunity to reach the week-8 assessment; also verify the endpoint definition and handling of missing assessments. (2) The rates are \(12/300=0.0400\) and \(10/200=0.0500\) events per person-year; their ratio is \(0.0400/0.0500=0.800\). These are crude descriptive rates. (3) The value may be valid, and influence alone does not establish a data error or a prespecified reason for exclusion; investigate its source and report the sensitivity appropriately. (4) Yes: \(27/45=0.600=60.0\%\). Check whether the plot uses the same assessed-participant denominator, endpoint, and data cut. (5) The observed proportions differ among participants assessed at this cut, but the comparison may be unstable because substantial endpoint information is not yet available; it is not a definitive estimate of the eventual pattern.