Tutorials › Adaptive Clinical Trial Design › ACTIV-6 And Decentralized Platform Operations

Case Studies · Tutorial 790 of 799

ACTIV-6 And Decentralized Platform Operations

Learn how ACTIV-6 combined remote operations with intervention-specific monitoring, and how to interpret the operational and statistical trade-offs of a decentralized platform trial.

Advanced 11 min read

What You'll Learn

  • Describe how remote enrollment, medication delivery, and follow-up can support an outpatient platform trial.
  • Distinguish shared platform operations from the intervention-specific randomized comparison.
  • Explain why a futility decision for one intervention does not automatically stop the other platform arms.
  • Assess how missing remote outcome reports can affect interpretation.
  • Separate evidence of futility from proof that an intervention has no effect.
  • Identify operational and statistical limitations of decentralized trial data.

Why ACTIV-6 Is an Operations Case Study

Evaluating treatments for COVID-19 in outpatients posed a practical problem: participants were at home, illness could change quickly, and requiring repeated clinic visits could make participation difficult or unsafe. ACTIV-6 addressed this by using a decentralized, placebo-controlled platform to evaluate repurposed treatments in people with mild-to-moderate COVID-19. Participants could be enrolled and followed remotely, while trial teams coordinated study medication, outcome collection, safety monitoring, and analysis through common platform infrastructure.

The design point is not simply that a trial can operate online. A decentralized platform has to preserve the logic of a randomized comparison while handling remote consent, medication delivery, self-reported outcomes, and missed contacts. It also has to distinguish a decision about one treatment from a decision about the platform: evidence that one intervention is unlikely to provide worthwhile benefit does not, by itself, answer whether another intervention should continue to be evaluated.

Definition: A decentralized clinical trial conducts some or all study activities away from traditional research sites, using methods such as remote consent, direct medication delivery, telephone or electronic follow-up, or local health services. A platform trial uses a continuing protocol and shared operational structure to evaluate multiple interventions over time. The treatment effect of interest remains specific to an intervention and its defined comparison, even when trial operations are shared.

Remote Operations and the Randomized Comparison

In ACTIV-6, remote participation made it possible to study outpatient treatment without requiring routine in-person visits for every research contact. Participants received study medication and reported symptoms and other outcomes remotely. The primary outcome used in ACTIV-6 evaluations was time to sustained recovery, defined using a period of consecutive days without symptoms. The exact schedule, questions, and analysis rules are protocol matters: they determine what is measured, when it is measured, and how an incomplete report is handled.

Remote procedures change the means of collecting information, not the purpose of randomization. For an intervention-specific estimate, the relevant comparison is between participants assigned to that intervention and appropriate placebo controls under the applicable protocol and time period. A common platform can coordinate eligibility, data systems, safety oversight, and trial staff. But operational sharing does not make every participant in every arm interchangeable as a control. Calendar time, eligibility, follow-up, and the randomization scheme matter when deciding whether a control group is appropriate.

This distinction is especially important when interventions enter or leave a platform at different times. A comparison that uses concurrent randomized controls is generally easier to interpret than one that relies on controls recruited in a different period, when infection patterns, background care, or eligibility may have changed. Any use of shared controls must be justified by the design and analysis; it should not be inferred merely from the word “platform.”

Worked Example: Checking Remote Follow-Up by Arm

Hypothetical data: Suppose a decentralized study assigns 240 participants to an intervention and 240 to placebo. By the end of follow-up, 216 intervention participants and 204 placebo participants have returned the report needed to classify recovery status. Calculate the report-return proportions and their difference.

For the intervention group, the observed report-return proportion is

$$ \hat{p}_{I}=\frac{216}{240}=0.900. $$

For the placebo group, it is

$$ \hat{p}_{P}=\frac{204}{240}=0.850. $$

The difference is \(0.900-0.850=0.050\), or 5 percentage points. Thus, in these hypothetical data, five percentage points more participants in the intervention group returned the report. This is an operational comparison, not an estimate of treatment efficacy: returning a report is not the same outcome as recovering. The difference is a diagnostic signal to investigate whether reporting patterns, contact attempts, or other processes differed by assignment.

Stopping Decisions Belong to Interventions

A platform can continue operating while one intervention stops enrolling. In ACTIV-6, intervention evaluations were monitored separately, and the fluvoxamine evaluation stopped enrollment after interim monitoring indicated that continuing was unlikely to establish a worthwhile benefit under its decision criteria. That decision concerned the fluvoxamine comparison; it was not a conclusion that all treatments being considered in ACTIV-6 were futile.

A futility decision is a prospective decision rule, not a declaration that the true effect is exactly zero. In a Bayesian monitoring framework, one possible rule is to stop for futility when the posterior probability of reaching a prespecified clinically meaningful benefit falls below a chosen threshold. The probability is conditional on the model, the data observed so far, and the prior distribution. A rule of this kind is an illustration of the logic; it should not be mistaken for ACTIV-6’s exact operational threshold.

Definition: Intervention-specific futility stopping is a decision to stop enrollment or treatment evaluation for a particular intervention because the accumulating evidence makes a prespecified worthwhile benefit sufficiently unlikely under the trial’s monitoring rule. It does not establish that the effect is exactly zero, and it does not automatically determine whether other interventions or the platform should continue.

Worked Example: Applying an Illustrative Futility Rule

Hypothetical monitoring result: Let \(\theta\) denote the odds ratio for a more favorable recovery outcome, with values above 1 favoring the intervention. Suppose the protocol defines a worthwhile benefit as \(\theta>1.10\), and the prespecified futility rule says to stop if \(P(\theta>1.10\mid\text{data})<0.20\). At an interim analysis, suppose the posterior probability is 0.14.

The rule requires comparing the computed probability with 0.20:

$$ P(\theta>1.10\mid\text{data})=0.14<0.20. $$

The illustrative rule therefore signals futility for this intervention. It does not say \(P(\theta=1)=0.86\), nor does it show that every possible benefit has been excluded. It says that, given this model and the interim data, the posterior probability of exceeding the specified worthwhile-benefit threshold is below the rule’s cutoff. A different intervention with different data has its own posterior probability and may have a different decision.

The rationale can be stated directly. If the decision target is a meaningful benefit rather than any nonzero effect, then monitoring asks whether the data still support that target strongly enough to justify continued enrollment. Writing the rule as an inequality makes the decision auditable:

$$ \text{Stop for futility if }P(\theta>\theta_{\mathrm{worthwhile}}\mid\text{data})<c, $$

where \(\theta_{\mathrm{worthwhile}}\) is the prespecified effect threshold and \(c\) is the prespecified probability cutoff. These values must be set in the protocol or monitoring plan, not selected after seeing an interim result. The rule’s operating characteristics depend on the model, prior assumptions, timing of interim analyses, and the cutoff; a single posterior probability is not a complete assessment of those properties.

Why Remote Missingness Matters

A remote trial can reduce travel and make follow-up more convenient, but it cannot guarantee that outcomes will be observed. Participants may stop answering because symptoms resolve, because they become too ill, because technology or connectivity fails, or for reasons unrelated to their health. If outcome availability is related to recovery, a comparison among respondents alone may not represent the randomized groups.

The basic issue can be shown with a mixture. Let \(R=1\) indicate that an outcome is reported, and let \(Y\) be a binary outcome such as meeting a prespecified recovery definition by a given time. The full-group recovery proportion is

$$ P(Y=1)=P(Y=1\mid R=1)P(R=1)+P(Y=1\mid R=0)P(R=0). $$

The observed reports identify the first conditional proportion, but not necessarily the second. If unreported outcomes are systematically better or worse than reported outcomes, the respondent-only proportion can differ from the full-group proportion. This is why follow-up completeness, reasons for missingness, and sensitivity analyses matter alongside the primary model.

Worked Example: How Missing Outcomes Can Change a Proportion

Hypothetical data: In one assigned group of 100 participants, 80 return an outcome report; 60 of those 80 meet the recovery definition. The observed respondent proportion is

$$ \frac{60}{80}=0.750. $$

If all 20 unreported participants had not met the recovery definition, the full-group proportion would be \(60/100=0.600\). If all 20 had met it, the proportion would be \(80/100=0.800\). The data alone therefore permit a range from 0.600 to 0.800 under these extreme assignments. This range is not a recommended estimate; it demonstrates why the 0.750 respondent proportion does not automatically equal the full-group proportion.

An actual analysis should follow its prespecified estimand and missing-data plan, use available auxiliary information where appropriate, and examine whether conclusions change under plausible assumptions about unobserved outcomes. Simply treating every missing report as non-recovery, or excluding every participant without a complete report, can each impose an unexamined assumption.

Shared Infrastructure: Benefits and Limits

Shared infrastructure can make a multi-intervention program more efficient. A platform may reuse staff training, eligibility screening, remote-contact systems, outcome instruments, data management, and safety oversight. It can also reduce the time needed to initiate a new evaluation compared with building a separate trial from the ground up. These are operational efficiencies; they do not eliminate the need to justify each intervention’s randomization, control group, endpoint, and analysis.

The main alternative is a collection of separately run, conventional randomized trials. Separate trials can make intervention-specific procedures and comparisons straightforward, but duplicate infrastructure and may take longer to launch. A platform emphasizes common operations and the ability to evaluate interventions within a shared structure, but requires careful governance: which interventions are open, which participants are eligible, which controls are concurrent, and how each arm’s results are monitored must remain clear.

FeatureDecentralized platform approachSeparate conventional trials
OperationsCan reuse remote systems and trial infrastructure across evaluationsOften requires separate setup and coordination for each trial
Intervention inferenceRequires an explicit intervention-specific randomized comparisonUsually centered on one trial-specific comparison
StoppingOne intervention may stop while others continue, subject to governanceStopping generally applies to that individual trial
Key vulnerabilityConfusing shared operations with automatically exchangeable controlsDuplication, slow startup, and fragmented infrastructure

Decentralization also has limits. Remote self-report can be affected by recall, participant burden, and inconsistent access to devices or internet. Medication delivery does not by itself establish that the medication was taken as assigned. Safety events that need examination may require local care or an in-person assessment. A platform must therefore plan escalation pathways, adherence measurement, and consistent outcome definitions rather than treating remote contact as a substitute for all clinical oversight.

Diagnostics and Common Pitfalls

Useful diagnostics include arm-specific follow-up completeness, timing of reports, reasons for withdrawal or nonresponse, medication delivery and adherence measures, and protocol deviations. These should be examined across relevant participant groups and calendar periods. Imbalances do not prove bias, but they can show where the assumptions behind the intended comparison need scrutiny. A monitoring committee also needs timely, reliable data; a theoretically sound stopping rule is not useful if outcome collection is too delayed or incomplete to support it.

Common mistake: “The platform stopped one treatment for futility, so the platform showed that repurposed treatments do not work.” This overgeneralizes from an intervention-specific decision. The correction is to identify the treatment, comparison, endpoint, interim evidence, and rule involved. A futility decision says that continuing that evaluation was not justified under its prespecified criteria; it neither proves a zero effect nor supplies a result for other interventions.

Key takeaway: ACTIV-6 illustrates that decentralized operations and platform adaptation must be assessed together but not confused. Remote follow-up makes outpatient research feasible; shared infrastructure can support multiple evaluations; and each intervention still requires a clearly defined randomized comparison, reliable outcome collection, and its own justified stopping decision.

Check Your Understanding

Answer each question, then compare your reasoning with the solutions below.

  1. Why does a remote trial need to report outcome completeness separately from treatment outcomes?
  2. In an illustrative futility rule, \(P(\theta>1.10\mid\text{data})=0.18\), and the cutoff is 0.20. What decision follows, and what does it not establish?
  3. Why does a platform’s shared infrastructure not automatically make all placebo participants appropriate controls for every intervention?
  4. In a group of 150 participants, 120 return outcome reports and 90 meet a recovery definition. What is the respondent recovery proportion, and why might it not equal the full-group proportion?
  5. What is the difference between stopping one intervention for futility and stopping the platform?

Solutions. (1) Missing reports may be related to health or treatment assignment, so the observed outcomes may not represent all randomized participants; completeness helps diagnose this risk. (2) Since \(0.18<0.20\), the illustrative rule signals futility for that intervention. It does not prove a zero effect or give the probability that the null hypothesis is true. (3) Controls must be appropriate under the protocol’s randomization and time period; background care, eligibility, and calendar conditions may differ. (4) The respondent proportion is \(90/120=0.750\), or 75.0%. The 30 participants without reports may have different outcomes, so the respondent proportion need not represent all 150. (5) An intervention-specific decision concerns whether to continue evaluating that treatment; stopping the platform is a broader governance decision about the shared trial structure and its remaining evaluations.

Clinical Biostats