EU Telematics PIM � _
 

eCTD v3.2

_

Home

_

Human eSubmission
eCTD v3.2
eCTD EU M1 specification

_
Veterinary eSubmission
_
eSubmission expert group
_

eSubmission expert group documents

_

External Links

_

Systems:

Common Repository

eAF

eASMF
ePMF
CESP Portal
CESP Delivery

eSubmission Gateway & eSubmission Web Client

Delivery file UI

eSubmission Gateway

PAM submission form

PLM Portal eAF (DADI)

PLM Portal

_
PSUR Repository

Industry access

NCA access
_

Projects:

eCTD v4.0

Paediatric submissions

SPOR

eSignatures

_
_

 

The Common Technical Document (CTD) describes the organisation of modules, sections and documents to be used by an Applicant for a Marketing Authorisation for a medicinal product for human use agreed by the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH).  The electronic Common Technical Document (eCTD) allows for the electronic submission of the Common Technical Document (CTD) from applicant to regulator. While the table of content is consistent with the harmonised CTD, the eCTD also provides a harmonised technical solution to implementing the CTD electronically. In other words, an eCTD is the submission of PDF documents, stored in the eCTD directory structure, accessed through the XML backbone and with the files integrity guaranteed by the MD5 Checksum.

The current version of the eCTD specification to be used for CTD modules 2-5 is the Electronic Common Technical Document Specification V3.2.2 (PDF). More information about the standard can be found at the ICH eCTD webpage.

For eCTD submissions within EU, the EU Module 1 eCTD Specification (see link below) should be used.

The eCTD format is mandatory to use for all submission types related to Marketing Authorisation for products within all EU procedures (i.e. Centralised, Decentralised and Mutual Recognition Procedures). In accordance with the eSubmission Roadmap, Mandatory eCTD format is also stepwise introduced for National Procedures.

18-06-2024

eCTD 3.2.2 new package available

A new version of the EU eCTD M1 Specification, version 3.1, is now published on the eSubmission website

The version 3.1 sees the introduction of a number of changes across the specification, however, more specifically, the introduction of a new annex detailing the list of accepted file formats
(Reminder: the generally accepted file format is the PDF, however, in specific cases, other formats will be exceptionally accepted in the eCTD modules). The changes are reflected in the Release Notes.
The same changes are reflected in the additional files of the EU M1 Implementation Guide package (i.e. eu-envelope.mod, eu-regional.dtd, eu-regional.xsl)

A new version of the validation criteria has been published on the eSubmission website. The version is related to the EU Module 1 Specification version 3.1 and should be used in case of submitting a new sequence according to EU M1 specification v3.1. The new validation criteria will be used for the technical validation for all v3.1 electronic submissions received as of 1 March 2025 to the NCAs and EMA. The changes are reflected in the Release Notes.

During the initial period of 6 months from 18 June 2024 to 30 November 2024, applicants can only submit eCTD format submissions compliant with EU M1 v3.0.4 and validation criteria version 7.1.

From 1 December 2024 eCTDs compliant with EU M1 v3.0.4 or v3.1 and validation criteria v7.1 or v8.0 are accepted.

From 1 March 2025 only eCTDs compliant with EU M1 v3.1 and validation criteria v8.0 are accepted.

_

Documentation

NeeS format

NeeS has been used as a transitional format towards the mandatory use of eCTD and is now only accepted in some specific cases.

 

For the UK, as from 1.1.2021, EU Law applies only to the territory of Northern Ireland (NI) to the extent foreseen in the Protocol on Ireland/NI.

 

EMA
European Medicines Agency ©1995-2024 | Disclaimer |For technical support, please visit the EMA Service Desk (ServiceNow) portal using your user credentials for a system hosted by EMA (except Eudravigilance). If you do not have an account or have forgotten your credentials, please click here