Regulatory publishing guide
eCTD 4.0 vs 3.2.2
The same CTD content, a very different engine underneath. Here is exactly what changes and what it means for your dossiers.
Side by side
| Dimension | eCTD 3.2.2 | eCTD 4.0 |
|---|---|---|
| Backbone / message | Region-specific XML backbone | HL7 RPS (Regulated Product Submission) |
| Document reuse | Re-submitted or linked per location | One document referenced in many locations |
| Vocabularies | Fixed in the DTD | Controlled vocabularies maintained & updated separately |
| Metadata | Limited attributes | Keyword-based, richer context |
| Communication | Largely one-way | Two-way applicant↔agency |
| Lifecycle operators | new / replace / append / delete | Same intent, expressed through RPS |
Why it matters in practice
The headline gains are reuse and maintainability. In 3.2.2, a document that belongs in several places has to be handled in each one; in 4.0 it is submitted once and referenced wherever needed, which shrinks dossiers and removes a common source of version drift. Because controlled vocabularies are maintained outside the core standard, regulators can evolve the format without forcing a disruptive migration each time.
Migration planning
- eCTD 4.0 is phased in region by region through voluntary-then-mandatory windows; 3.2.2 stays valid throughout.
- The real risk is running two formats at once across markets — so your tooling and your publishing partner must handle both and manage lifecycle across the switch.
- Clean source documents and consistent metadata now are what make reuse and validation painless later.
“Teams fixate on the 4.0 deadline. The work that actually pays off is tidying your templates and metadata today — reuse only helps a dossier that was consistent to begin with.”Prashanth Krishna, Practice Head — Content Transformation & Regulatory Operations, B2K
Talk to B2K about your project
Tell us the scope and the deadline, and we will scope the work and commit to a date we can hold.
Start a project →Frequently asked questions
Is eCTD 4.0 replacing 3.2.2?
Eventually, but gradually. eCTD 4.0 is being introduced region by region with voluntary and then mandatory periods, and eCTD 3.2.2 remains valid throughout the transition. Most companies will run both formats in parallel for a time depending on their markets.
What is the main technical difference?
eCTD 3.2.2 uses a region-specific XML backbone; eCTD 4.0 is built on the HL7 Regulated Product Submission (RPS) message. That shift enables document reuse, separately-maintained controlled vocabularies, richer keyword metadata and two-way communication with the agency.
Do we have to re-publish existing 3.2.2 submissions in 4.0?
No. Existing 3.2.2 lifecycles continue to be accepted during the transition. New sequences can move to 4.0 where a region supports it, and a capable publishing partner manages the lifecycle across both formats.
How should we prepare for eCTD 4.0?
Confirm which of your regions have published 4.0 timelines, ensure your publishing partner can compile both 3.2.2 and 4.0, and clean up document templates and metadata now so the move to reuse-based structure is straightforward.