eCTD v4 introduces a machine-first, metadata-driven approach to regulatory submissions, replacing the browser-friendly structure of eCTD v3. As a result, dossiers can no longer be viewed directly in standard web browsers.
This article explains the technical reasons behind this shift and why dedicated eCTD v4 viewers are now essential.
If you have ever attempted to open an eCTD v4 dossier in a standard web browser, the result is underwhelming: no intuitive structure, no clear navigation, you just see a raw XML that offers little immediate value. This is not a limitation as you might maybe think; it is a deliberate design choice.
From “Human-Readable” to “Machine-First”
The explanation lies in the fundamental evolution of the eCTD standard. In eCTD v3, submissions were largely organized as folder structures supported by XML and XSL stylesheets. These stylesheets acted as a transformation layer, enabling browsers to render the submission into a structured, human-readable view.
With eCTD v4, this paradigm shifts entirely. The standard is now based on an HL7 RPS-compliant XML payload, designed primarily for machine processing rather than direct human consumption. So instead of relying on folder hierarchies, eCTD v4 introduces:
This results in a highly structured and semantically rich data model, optimized for consistency and interoperability, but no longer suitable for direct rendering in a browser.
Why a Viewer Becomes Essential in eCTD v4
A key technical change in eCTD v4 is the removal of XSL stylesheets. eCTD v4 deliberately does not include built-in transformation logic for browser display. Without this layer, browsers lack the instructions required to convert XML into a meaningful visual structure. Moreover, modern web browsers no longer permit access to locally referenced stylesheets by default due to security restrictions.
Consequently, dedicated eCTD v4 viewers are now required. These tools interpret the underlying data model and reconstruct a usable interface by:
Without such functionality, navigating and understanding an eCTD v4 dossier becomes impossible. Therefore, a viewer is absolutely essential.
The Structural Shift Behind the Scenes
Beyond the rendering aspect, eCTD v4 also introduces important changes to the physical file structure:
As a result, file names alone no longer convey sufficient meaning. The contextual relationship and purpose of each document are defined within the XML metadata rather than the directory structure.
In essence: The logic has shifted from the file system to the data layer.
Comparison of the Changed Features in eCTD v4
A Brief Look at eCTD v4’s Benefits
While the transition to eCTD v4 increases technical complexity, it enables several key advantages:
A Shift to Machine-Driven Submissions
eCTD v4 represents a fundamental shift in how regulatory submissions are structured and managed. By prioritizing structured data, interoperability, and automation, the standard moves away from human-readable formats toward a machine-driven model. As a result, traditional browser-based viewing is no longer sufficient.
To effectively work with eCTD v4, a dedicated viewer is no longer optional, but essential. With the EXTEDOpulse Submission Viewing, EXTEDO offers an easy-to-use tool for viewing, sharing, and tracking submission content.
Want to understand better how the technical evolution of eCTD v4 impacts your submission processes? Download our white paper: White paper - Adapting to Thrive_The Evolution toward eCTD v4 | EXTEDO