Skip to Content

eCTD Radar EMA R2 & R3 Validation: What It Means for Your Submissions

August 6, 2026 by
eCTD Radar EMA R2 & R3 Validation: What It Means for Your Submissions
EMCO Egypt

eCTD Radar EMA R2 & R3 Validation: What It Means for Your Submissions

Among the first Egyptian-built regulatory tools to be validated by the European Medicines Agency — twice.

See eCTD Radar Contact Us

In 2022, EMCO Egypt's eCTD Radar software completed EMA R2 validation — becoming one of a small number of Egyptian-built regulatory tools to receive technical certification from the European Medicines Agency. In 2024, eCTD Radar completed R3 validation under the updated EMA technical specification. EMA validation is a technical verification process conducted by the regulatory body that will receive the submissions the software generates. It confirms that the software produces eCTD output meeting the EMA's technical specification in format, structure, XML architecture, and controlled vocabulary.

What EMA eCTD validation means

The EMA publishes technical specifications for eCTD submissions — format, structure, file naming, XML backbone requirements, and controlled vocabulary. Software generating eCTD dossiers must produce output meeting these specifications. The validation is tiered by specification release:

  • R2 covers the eCTD specification governing EMA submissions up to the transition to the updated standard — defining structure, XML schema, and controlled vocabulary for eCTD v3.2 submissions.
  • R3 covers the updated EMA eCTD specification, introducing changes to controlled vocabulary, structural requirements, and submission portal integration.

Software that has not completed EMA validation has not been tested against EMA's technical requirements. Submissions from unvalidated software may contain technical errors invisible to the regulatory affairs team but flagged at the EMA's submission gateway.

eCTD dossier software validation and regulatory submission

Why it matters for Gulf submissions

GCC authorities — including SFDA in Saudi Arabia — align their eCTD technical requirements closely with EMA specifications. Dossiers prepared for Gulf authorities using eCTD Radar benefit from the same technical rigour that EMA validation certifies. A technically invalid eCTD submission will be rejected by the authority's submission system before it reaches a reviewer. Technical rejection means resubmission, which means delay. For Gulf submissions with defined windows or associated with market launches, delay has direct commercial consequences. eCTD Radar eliminates the category of error that comes from software non-conformance.

What EMA validation means in practice

Technical risk minimised

The XML backbone generated by eCTD Radar has been tested against EMA requirements. Software non-conformance errors are not a risk your team carries.

Gulf on the same foundation

GCC authority requirements align with EMA technical specifications. The same validated output serves both — no separate toolchain needed.

Always current

R3 validation confirms eCTD Radar has been updated and tested against the most current EMA technical standard.

eCTD software technical validation XML backbone

What R3 validation involved

The EMA's R3 specification introduced revised controlled vocabulary, updated structural requirements, changes to submission portal integration, and additional XML backbone validation rules. R3 validation required eCTD Radar to be updated across all affected areas and re-validated. For EMCO Egypt's eCTD outsourcing clients, this meant no service interruption. Learn more about eCTD Radar, EMCO Egypt, or contact us to discuss your eCTD submission requirements.

Common Questions About eCTD Radar

See the only Egyptian-built eCTD software with EMA R2 and R3 validation.

Demos are conducted by regulatory practitioners who use eCTD Radar for real submissions.

Book a Demo Learn About eCTD Radar
EDA Pharmacovigilance Inspection: What to Expect and How to Prepare