eCTD 4.0 Readiness Guide: What Changes and How to Prepare
eCTD 4.0 readiness guide
Japan requires it for new applications. The FDA accepts it. Here is what actually changes from 3.2.2, and a plan your team can start now.
Six differences that drive the work
One message per submission unit, based on HL7 RPS, instead of a folder backbone plus a regional XML file.
Every document has a permanent identifier and can be referenced again rather than sent twice.
Operations act on a document’s context of use — where it sits and what it is for. Replace and suspend; no append, no delete.
Substance, product, manufacturer and similar attributes become keywords, defined once and reused.
Explicit priority numbers set the order; grouping in the message replaces Study Tagging Files.
Code lists are published by ICH and each authority as separate files and change on their own schedule.
Region by region, October 2026
Japan — PMDA
Required for new applications from 1 April 2026. Existing 3.2.2 dossiers continue in 3.2.2.
United States — FDA
Accepted for new applications since September 2024. No cutover date announced.
TGA, Health Canada, EU
Guidance published or planned; 3.2.2 remains the filing format.
Where teams get caught with PMDA
Conditions only in the text
Some rules apply only to a first-version submission — and say so only in the description. Read literally, the rules contradict each other.
Retired rules
PMDA switches rules off with an effective date. A validator that ignores it fails you on rules no longer in force.
Only checking your own output
Problems sit in packages from partners and previous vendors. Validate packages you did not build.
Characters and lengths
Titles, names and keyword values must use PMDA’s permitted character set and length limits.
The full readiness guide
A practical plan for regulatory operations, publishing and IT teams.
- What changes from 3.2.2, area by area
- Where each region stands, and what it means in practice
- Japan: the families of PMDA rules and where teams get caught
- A four-workstream readiness plan: data, process, technology, people
- Deciding when to move each application
Frequently asked
Do existing applications have to move to eCTD 4.0?
Not under current guidance. Japan’s mandate applies to new applications, and the FDA accepts 4.0 voluntarily for new applications. Existing applications continue in 3.2.2 unless an authority says otherwise.
What replaces append and delete in eCTD 4.0?
Lifecycle acts on a document’s context of use. A context of use can be replaced or suspended; there is no append, and suspend takes the place of delete.
What happens to Study Tagging Files?
They are not used in 4.0. Study grouping and the role of each file are carried in the submission message itself.
Can we prepare before our tools support 4.0?
Yes. Most of the work — stable document identifiers, structured titles, master data for keywords, a record of what is current where — is data and process, and it improves a 3.2.2 operation too.
See eCTD 4.0 on your own content
DnXT Publisher builds and validates Japan eCTD 4.0 against PMDA’s published rules, alongside eCTD 3.2.2 for every other region.
