ICH E17: The Regional Question Belongs in Your SAP

A multi-regional clinical trial is not simply one protocol executed at sites in several countries. ICH E17 — General Principles for Planning and Design of Multi-Regional Clinical Trials, reaching Step 4 on 16 November 2017 — expects a sponsor to decide, before the trial starts, how it will demonstrate that the treatment effect holds across the regions it plans to submit to. Sponsors that treat this as a question to answer after unblinding, once a regulator asks whether the data applies to their population, have already missed where E17 puts the obligation.

What E17 actually asks a sponsor to plan

The most consequential thing E17 does is procedural, not statistical: it asks a sponsor to pre-specify, before the trial begins, how it intends to evaluate whether a treatment's effect is consistent across the regions the trial will support. That evaluation plan — along with how the sponsor will allocate sample size across regions — belongs in the protocol and the statistical analysis plan, decided while the trial is still being designed. A sponsor that waits until the data are in to figure out how it will address a region-specific question has already run the trial without the plan E17 expects to see.

Where E17 comes from: E5, applied earlier

E17 did not invent the idea that a treatment effect can vary by population. ICH E5, finalized in 1998, gave the field its vocabulary for that variation: intrinsic factors — genetic and physiological characteristics such as age, sex, organ function, and genetic polymorphisms — and extrinsic factors — environmental and cultural variables such as diet, medical practice, and regulatory requirements. E5's job was retrospective: given clinical data already collected in one region, assess whether it could bridge to support approval in another. E17's contribution is to take the same intrinsic/extrinsic framework and move it to the front of the process — designing a single trial upfront to generate the cross-regional evidence a bridging exercise would otherwise have to reconstruct later.

Consistency isn't a pass/fail gate

E17 does not ask a sponsor to prove every region behaves identically; it asks the sponsor to have a pre-specified way to look. When a clinically relevant regional difference does turn up, the guideline calls for a structured post-hoc analysis — examining whether the difference is plausibly explained by an imbalance in the intrinsic or extrinsic factors the trial was designed to track, rather than treating an outlier region as evidence the whole result is unreliable. That analysis sits on top of the general statistical principles ICH E9 already establishes for any clinical trial; E17 does not replace that foundation, it adds a regional lens to it.

E5 asked whether foreign data could bridge to a new region after the fact. E17 asks a sponsor to design a trial that never has to ask. Why E17 sits downstream of E5

The practical stakes are highest for sponsors pursuing simultaneous global submission across FDA, EMA, and PMDA — including through parallel-review arrangements like Project Orbis, where a trial that satisfies one region's reviewers but leaves another asking an unanswered regional-consistency question loses exactly the timing advantage the arrangement exists to create. The same discipline applies wherever a single pivotal trial is expected to carry regional consistency across more than one regulatory audience: the question is cheaper to answer by design than to answer by explanation after the fact.