ICH E5(R1) Bridging Data Gaps in Global Clinical Trials

When Foreign Clinical Data Meets a New Region’s Regulatory Requirements — and the Architecture Behind the Submission Fails First

A recurring pattern in the r/clinicalresearch community signals something that experienced regulatory professionals recognise immediately: clinical researchers entering the UK, EU, or US markets from non-ICH regions frequently underestimate the structural complexity of getting foreign clinical data accepted — not because the science is insufficient, but because the data governance architecture supporting that science does not map cleanly onto the receiving region’s evidentiary framework. The question is rarely about the quality of the Phase I or Phase II work done in one region. It is about whether the data package, as assembled, satisfies the regulatory requirements of the new region under ICH E5(R1) — and whether the bridging data package has been structured to demonstrate that satisfaction explicitly.

ICH E5(R1), published as CPMP/ICH/289/95 and operative since September 1998, establishes the framework for accepting foreign clinical data in a new region. Its central premise — that it is not necessary to repeat the entire clinical drug development programme in the new region — is broadly understood. What is less well understood is the compliance surface that premise creates. Under Section 2 of ICH E5(R1), all data in the clinical data package, including foreign data, must meet the standards of the new region with respect to study design and conduct. This is not a formality. It is a data quality requirement that maps directly onto the eCTD module structure of a centralised procedure submission, and gaps in this mapping are among the most commonly identified deficiencies in Day 80 CHMP assessments of applications relying on multi-regional clinical trial data.

The Bridging Study Requirement Is a Data Architecture Problem, Not Just a Clinical Design Problem

Section 3.2 of ICH E5(R1) defines the bridging data package as the data that allow extrapolation of foreign clinical data to the new region. The bridging study itself — whether pharmacokinetic, pharmacodynamic, or a full dose-response study — is the most visible component. But the architecture around it determines whether the CHMP accepts the extrapolation. Specifically, under Section 3.1, the sponsor must characterise the medicine’s sensitivity to ethnic factors, classifying both intrinsic factors (genetic, physiologic, pathologic) and extrinsic factors (medical practice, diet, regulatory environment) as set out in Appendix A of the guideline. If this characterisation is absent or incomplete in the submission dossier, the bridging study result — however clean — may be insufficient to close the Day 80 question list.

The ICH E5(R1) Q&A document (CPMP/ICH/5746/03, transmitted to CHMP in June 2006) clarifies that for drugs sensitive to ethnic factors, where the medical settings in which the drug is used may vary among regions, a controlled study in the new region is likely required. Critically, the Q&A confirms that a single such study may be sufficient — but only if the foreign data otherwise meet all the requirements of the new region. That conditional is where most submission architectures fail. The foreign data must be shown to meet those requirements, not merely asserted to do so. This distinction transforms what many sponsors treat as a narrative regulatory argument into a structured data verification exercise: each study in the foreign data package must be traceable to the specific evidentiary standard it satisfies in the new region’s framework.

Genomic Data Adds a Compliance Layer That Is Frequently Understructured in Multi-Regional Programmes

Where the clinical development programme includes pharmacogenomic or pharmacogenetic components — increasingly common in oncology and rare disease, and increasingly expected by CHMP as part of the biomarker-stratified efficacy story — ICH E18 (EMA/CHMP/ICH/11623/2016, date for coming into effect 28 February 2018) adds a parallel compliance surface that intersects with the ICH E5(R1) ethnic factors analysis in ways that are not always structurally managed. ICH E18 Section 2.1 specifies 6 parameters governing genomic sample collection: specimen type, timing of collection, preservation conditions, stability and degradation, volume and composition, and parameters influencing sample quality. If foreign clinical data includes genomic biomarker analyses that will be cited in the bridging data package, the specimen documentation for those samples must satisfy ICH E18 Section 2.1 parameters as interpreted in the new region — not merely in the originating region.

ICH E15 (EMEA/CHMP/ICH/437986/2006, operative May 2008) defines the coding categories for genomic data and samples — identified, coded, anonymised, anonymous — and these categories carry direct implications for how genomic data from foreign studies can be re-used in a bridging context under GDPR-adjacent data protection requirements in the EU. A genomic dataset coded in the originating region under one data governance framework may not map cleanly onto the EU’s anonymisation standard without structural remediation. This is not a theoretical concern. It is a data architecture gap that, if unaddressed before Day 0 of the centralised procedure assessment clock, may trigger a 90-day clock stop at Day 120 under Regulation (EC) No 726/2004.

Non-Clinical Safety Data Sequencing Compounds the Risk Surface for Global Development Programmes

For programmes where the global development strategy involves initiating clinical trials in one ICH region and expanding to another, ICH M3(R2) (EMA/CPMP/ICH/286/1995, date for coming into effect December 2009) creates a third compliance dimension. Section 5.1 of ICH M3(R2) specifies the duration of repeated dose toxicity studies required to support each phase of clinical development. Where clinical data from a foreign region was generated under a repeated dose toxicity support package that met that region’s Phase II or Phase III requirements, the receiving region must independently verify that the non-clinical support package meets its own requirements for the same development phase. A repeated dose toxicity study of duration adequate for a 6-month clinical trial in one region may not satisfy the requirements for an equivalent trial in another if the study design parameters differ. This sequencing question is most acute when in-licensing a late-stage asset from a non-EU region for EU centralised procedure submission — the due diligence process must include a gap analysis mapped to ICH M3(R2) Section 5.2 before the term sheet is signed, not after.

The Data Infrastructure Problem Behind the Submission Problem

What connects the ICH E5(R1) bridging architecture, the ICH E18 specimen documentation requirement, the ICH E15 coding compliance question, and the ICH M3(R2) non-clinical sequencing gap is not a regulatory affairs failure in the conventional sense. It is a data infrastructure problem. Each of these compliance surfaces requires that foreign data be queryable against a structured set of new-region criteria — and in most multi-regional programmes, that queryability does not exist at the time of submission preparation. The data are there. The studies were conducted. The results are valid. But the metadata layer — the documentation of how each datapoint maps to each new-region standard — is absent, inconsistent, or buried in study report appendices that were not designed to support cross-regional regulatory mapping.

Vestango’s programmatic intelligence capability addresses this gap as a pre-submission exercise. Rather than reconstructing the compliance mapping reactively during a clock-stop, Vestango’s automated monitoring pipeline cross-references the foreign clinical data package against the specific evidentiary requirements of the target region — under ICH E5(R1) Section 2, ICH E18 Section 2.1, ICH E15 coding categories, and ICH M3(R2) Section 5.1 — and delivers a scored compliance profile identifying each gap, its regulatory basis, and the remediation path available before Day 0. The output is a structured dataset: every identified deficiency is tagged with the exact article or section number it maps to, ranked by probability of triggering Day 120 questions under the centralised procedure, and accompanied by a calendar-day estimate of the remediation window available before the assessment clock starts.

What This Means for In-Licensing Valuation and Series A/B Timeline Risk

For investors and business development teams working with assets that carry foreign clinical data packages — particularly assets originating from Asia-Pacific or Latin American development programmes entering EU or US registration pathways — the ICH E5(R1) compliance architecture is a direct valuation variable. An asset where the bridging data package has not been structured to satisfy CHMP’s ethnic factors characterisation requirement under Section 3.1 carries a Day 80 deficiency risk that, if it materialises, typically extends the centralised procedure timeline by at least one clock-stop cycle. That is a calendar consequence that is measurable and, more importantly, that is identifiable before the term sheet is signed. A pre-licensing compliance gap analysis mapped to ICH E5(R1), ICH E18, and ICH M3(R2) is not a regulatory formality — it is a valuation instrument. The difference between an asset that enters the assessment clock with a clean bridging architecture and one that enters with a partially documented ethnic factors characterisation may not be visible in the clinical results, but it is structurally visible in the dossier — if someone looks before Day 0.

If your programme relies on foreign clinical data for EU centralised procedure submission and you need a scored compliance profile mapped to ICH E5(R1) Section 2 and Section 3.2, ICH E18 Section 2.1, and ICH M3(R2) Section 5.1 — Vestango delivers this structured gap analysis before the assessment clock starts. Contact Vestango.

The analysis in this article draws on publicly available regulatory data, published guidelines, and the accumulated experience of Vestango Life Sciences in EU and Polish regulatory affairs. It reflects patterns we observe — not universal conclusions. Every regulatory situation is product-specific, market-specific, and jurisdiction-specific. What applies to one portfolio may not apply to yours. If any of the issues raised here resonate with your situation, the right next step is a structured, case-specific conversation — not the application of general conclusions. With our founder Paweł Wojtaszczyk, Ph.D. Eng., we work at the intersection of data science and regulatory affairs, translating that combination into real market implementations. We solve problems and build companies operating in the life sciences market. Contact Vestango.