Blog

eCTD 4.0 replaces the v3.2.2 folder hierarchy with an HL7-based format. Learn what's changing and how authoring teams can transition efficiently.

eCTD 4.0 replaces the static folder hierarchy of v3.2.2 with a dynamic, HL7-based structured message format. It changes how submission content is organized, referenced, and managed across the drug development lifecycle.

For authoring and regulatory operations teams, the transition involves more than a software upgrade. Publishing infrastructure, validation tooling, document workflows, and cross-functional training all require attention before mandation deadlines arrive.

What is eCTD 4.0 and What is the Purpose of eCTD?

The electronic Common Technical Document (eCTD) is the internationally standardized format for submitting regulatory information to health authorities. Across all versions, it provides a machine-readable submission structure that enables regulators to receive, navigate, and review pharmaceutical applications consistently across global markets.

eCTD 4.0 is the successor to v3.2.2, which has served as the dominant global submission format since the mid-2000s. The two versions differ at the architectural level:

• v3.2.2 organizes content into a static file folder tree anchored by a fixed XML backbone. 

• v4.0 is structured around the Health Level Seven (HL7) Regulated Product Submissions (RPS) standard, the same data interchange framework for many health information systems.

The International Council for Harmonisation (ICH) endorsed the eCTD v4.0 implementation package at Step 4 in 2015. Development had begun several years earlier, driven by recognized limitations in the v3.2.2 architecture, particularly its inability to accommodate document reuse, dynamic content organization, and multi-sequence lifecycle management at the scale modern dossiers require.

At a glance, v4.0 advances the standard across four areas:

• Submission Architecture: A single structured XML message replaces the multi-file folder tree

• Document Referencing: UUID-based identifiers enable content reuse across sequences and applications

• Content Organization: Sender-defined controlled vocabularies replace fixed folder tags

• Lifecycle Management: Metadata updates no longer require full document resubmission

v4.0 also lays the groundwork for two-way communication between sponsors and regulatory authorities, a capability not supported in v3.2.2.

What Changed from eCTD v3.2.2 to v4.0?

These changes have operational implications for regulatory and authoring teams:

• UUID-Based Document Reuse: Each content file in eCTD v4.0 is assigned a Universally Unique Identifier (UUID), allowing previously submitted documents to be referenced across new sequences by identifier alone. This eliminates the physical file duplication that inflates submission sizes in v3.2.2.

• Flexible Content Organization: The static file tags and fixed folder hierarchy of v3.2.2 are replaced with dynamic Document Types and sender-defined controlled vocabularies, allowing sponsors to structure content according to the submission's logic rather than a predetermined folder tree.

• Enhanced Lifecycle Management: v4.0 introduces advanced lifecycle operators, including the ability to update metadata without resubmitting the underlying document file, a capability v3.2.2 does not support. Documents can also be replaced on a one-to-many or many-to-one basis, and content granularity can be adjusted while preserving lifecycle history.

• HL7 RPS Architecture: The submission is delivered as a single structured XML message rather than a folder of files. This change enables better automated parsing, processing, and future interoperability with regulatory information management systems.

Teams managing cross-module consistency and NDA submission workflows manually will find that v4.0's UUID-based referencing makes inconsistencies between documents more visible to automated regulatory processing. Large dossiers with multiple lifecycle sequences become easier to manage, duplicate file handling is reduced, and traceability across submission histories improves. But the cost of content fragmentation across modules also rises.

Is eCTD 4.0 Mandatory?

eCTD 4.0 is not universally mandatory, but the transition is advancing across all major regulatory markets on distinct timelines. The window to prepare is shorter than the dates suggest, because publishing infrastructure, validation tooling, and authoring workflows all require sequential updates before a v4.0 submission can be run and verified.

The current status by agency:

• FDA (United States): Accepting voluntary new applications (NDAs, BLAs, ANDAs, INDs, and Master Files) in v4.0 format since September 2024. Mandatory transition timelines have not been formally announced, and industry analysts and regulatory bodies project a mandate around 2029. The FDA has stated it will provide advance notice before requiring v4.0 exclusively.

• PMDA (Japan): The earliest mandatory deadline among major agencies. The PMDA mandated eCTD 4.0 for new submissions effective April 2026, making Japan the first ICH region to require the new format.

• EMA (European Union): Optional use for Centrally Authorized Product Marketing Authorization Applications became available in December 2025. Mandatory use for centrally authorized products is currently targeted for 2027, with a formal compliance deadline for Q1 2028 under current EMA planning.

eCTD 4.0 applies to new applications and new sequences going forward. Existing dossiers submitted under v3.2.2 remain valid, and sponsors are not required to convert them. Forward compatibility functionality, which would allow v3.2.2 applications to transition into v4.0 sequences, is not yet available from the US FDA and is being developed in phased stages across agencies.

What eCTD 4.0 Means for Pharma Authoring and Operations Teams

The transition to eCTD 4.0 has operational implications that extend beyond IT infrastructure upgrades. Publishing, validation, authoring, and training workflows have major updates, and the teams most exposed are those currently relying on disconnected, manually managed processes.

Regulatory and authoring teams must revisit their workflows in these areas before mandatory deadlines arrive:

• Publishing Tool Updates: Publishing platforms must be updated or replaced to output HL7 RPS-compliant message structures rather than v3.2.2 folder trees. The submission architecture differs structurally, and existing publishing software cannot produce v4.0-compliant output without modification.

• Validation Workflow Changes: The XML backbone structure and submission message format require updated validators before test submissions can be run and verified against v4.0 specifications.

• Authoring Platform Compatibility: Authoring platforms that generate document content must output metadata and document identifiers compatible with v4.0's UUID-based referencing system. Platforms that cannot generate or track UUIDs at the document level will require replacement or reconfiguration.

• Cross-Functional Training: Regulatory operations, medical writing, and submission management teams require training on the new document model and lifecycle logic before mandation creates a compliance deadline, particularly on controlled vocabularies, Context of Use terminology, and the new lifecycle operators that replace the familiar append/replace model.

• Content Fragmentation Risk: v4.0's UUID-based document referencing and dynamic content model amplify the cost of inconsistency and fragmentation across modules. Where v3.2.2 could obscure mismatches within a folder structure, v4.0 surfaces them. Audit-ready traceability across document versions and submission sequences is a core operational requirement under the new format.

How AuroraPrime Prepares Teams for the eCTD 4.0 Transition

AuroraPrime's authoring architecture is designed around the cross-module consistency and audit-ready traceability that eCTD 4.0 demands at scale. 

The FDA's evolving submission review infrastructure, including AI-assisted review tooling, is moving toward consistent and auditable submission content that can be parsed and verified reliably. AuroraPrime addresses this at the authoring stage, before content reaches the publishing layer.

Key capabilities relevant to the v4.0 transition include:

• Cross-Module Consistency Validation: AuroraPrime ensures content across eCTD Modules 2, 3, 4, and 5 remains aligned before submission. In v4.0, UUID-based document referencing makes cross-module inconsistencies more visible to automated regulatory processing, making pre-submission consistency checks a compliance requirement.

• End-to-End Audit-Ready Traceability: Every authoring decision is tracked and documented across document versions and submission sequences, supporting the enhanced lifecycle management v4.0 requires and maintaining the inspection-ready audit trail.

• Structured, Configurable Template Architecture: AuroraPrime's configurable templates can be aligned to evolving regulatory format requirements as v4.0 specifications are adopted market by market, without requiring a full platform reconfiguration for each regional mandate.

• Veeva RIM Integration: AuroraPrime connects to regulatory information management infrastructure via Veeva RIM integration. v4.0's structured message model depends on precisely this kind of integration between authoring and submission management systems for seamless lifecycle management.

As an automation writing tool for drug development, AuroraPrime addresses the workflow challenges the eCTD 4.0 transition creates. It functions as an AI writing solution for pharmaceutical companies managing both current v3.2.2 submissions and the v4.0 architecture.

Book a demo to see how AuroraPrime produces submission-ready content aligned to current eCTD v3.2.2 requirements and the eCTD 4.0 format.