Why we need eCTD 4.0
Update notice
On the applicants’ side, the eCTD compilation workflow adaptations and additional user training will not cause exorbitant costs; the work processes will mostly remain unchanged. The problem is that eCTD version 4.0, especially with the limited features foreseen at the time in agencies’ implementations, raises some doubts about its benefits over eCTD version 3.2 and the justification for the change.
What eCTD 4.0 offers
- The ability to more easily reference previously used documents, without dependence on the knowledge of agency file and folder structures.1
- The ability to update metadata (document titles, manufacturers, etc.) entered erroneously, or that needs to be changed for any reason, without having to delete and re-add documents in a dossier.
- The ability to change document granularity while retaining the relationship with the previous version.
- Clear, consistent means of grouping or bundling submissions into a regulatory activity (most agencies support this, but in different ways).
- A simple way to update the Common Technical Document Table of Contents without rewriting software.
This last one is a big deal. Each time an agency updates their Regional DTD (Document Type Definition) for Module 1, it has a serious impact on software vendors’ systems. Their software must then parse a different XML structure and know how to display any new or changed elements. eCTD 4.0 should make it possible for those sorts of changes to be done without a software update, by just entering in new metadata for the changed items (where it belongs in the TOC, how many of that item can be included, and any other validation specifications). This alone should make eCTD 4.0 attractive to the software vendors, and their customers, by lowering the cost of maintaining those systems.
A look back at eCTD 3.2
The other shortfall is that the RPS standard on which eCTD 4.0 is built was targeted by FDA for all submissions by all divisions, but they have declined to leverage the available standard. In the last few years, FDA has created new submission formats for device registration2 and provided documentation on an “Alternate Electronic Format”3 that could have been done using RPS. However, it does not appear that there are any initiatives to implement RPS-based review at the Centers for Veterinary Medicine (CVM), Device and Radiological Health (CDRH), Food Safety and Applied Nutrition (CFSAN) or Tobacco Products. Doing so would amortize the agency’s costs of implementing eCTD 4.0 across more than just drugs, providing substantial value to taxpayers and the regulated industries.
Further discussion
eCTD 4.0 does not impact the progress toward data submissions: the content doesn’t change. But it does have the benefits described above. We still need a specification for all the sets of information to be delivered, regardless of whether it is data or narrative. Nevertheless, it does not prevent but rather paves the way for future enhancements without enforcing a completely new technology.
After more than a decade of living with eCTD 3.2, industry has learned to circumvent some of its shortcomings, or to simply live with it, but that doesn’t mean that the pain points are no longer there. The FDA’s goals of a single, changeable, simple format for multiple centers was one of the primary drivers, and that was not being met at the time.
Software vendors already provide updates and enhancements of their eCTD software on a regular and frequent basis. For most of them, the switch to eCTD 4.0 will not be an immense additional task, especially as most eCTD 4.0 concepts have already been known for a decade, and there has been plenty of time to accommodate or prepare for them. In the long run, eCTD 4.0 will reduce or simplify software updates, such as adjusting to changing regional specifications.
A minor update to eCTD 3.2 would require substantial software changes to handle a new DTD. IDMP is relatively irrelevant to eCTD, although the EU’s implementation4 will use SPOR data for administrative information.
Using the gateway for two-way communication has major benefits, primarily the ability for sponsor systems to notify, track, plan, and archive agency communications. We certainly manage today, but this could be a big enhancement to productivity, accuracy, and timeliness, especially for companies without an integrated RIM/eSubmission environment.
A strategic question
Is the need for eCTD 4.0 for all other types of regulated products, which currently have no solution, a driver which supersedes the change management needed for existing eCTD in pharma?
As Neal noted in his discussion questions, this should decrease the cost of the change by spreading it among multiple industries. In the discussions at the DIA RIM meeting, he asked whether eCTD version 4.0 should be skipped in favor of something more forward-looking or data oriented. There is nothing in eCTD version 4.0 that couldn’t handle projected data-oriented submissions such as PQ/CMC.5
While there are things in eCTD version 4.0 that could be improved, it is flexible enough to handle pretty much anything that needs to be sent between sponsors and agencies, between agencies, or between sponsors. We cannot forget that even with the move toward increasingly complex submission of structured data, there will still be a need to also submit human readable documents to put the data into the right context. Improving the ways we submit data should not prevent us from improving the way we submit documents.
Zřeknutí se:
Informace v tomto článku mají za cíl informovat čtenáře o tématu souvisejícím se schopnostmi společnosti Cencora a nejsou právním ani nákupním poradenstvím. Společnost Cencora, Inc. doporučuje čtenářům, aby si prostudovali odkazy citované v tomto článku a při rozhodování využili své vlastní znalosti a zkušenosti.
Related solutions
References
1. International Council for Harmonisation. "ICH Electronic Common Technical Document (eCTD) v4.0 Implementation Guide v1.7." May 5, 2026.
2. U.S. Food and Drug Administration. "Electronic Submission Template for Medical Device 510(k) Submissions: Guidance for Industry and Food and Drug Administration Staff." October 2, 2023.
3. U.S. Food and Drug Administration. "Providing Regulatory Submissions in Alternate Electronic Format: Guidance for Industry." Revision 1, June 2022.
4. European Medicines Agency. "Electronic Common Technical Document (eCTD) v4.0 EU Module 1 Implementation Guide," draft for updates, Version 1.2. October 2024. Table 3.
5. U.S. Food and Drug Administration. "Pharmaceutical Quality: Chemistry, Manufacturing & Controls." April 2024.
6. U.S. Food and Drug Administration. "FDA’s Reorganization Approved for Establishing Unified Human Foods Program, New Model for Field Operations and Other Modernization Efforts." May 30, 2024.
7. U.S. Food and Drug Administration. "FDA Modernization Efforts for Establishing a Unified Human Foods Program, New Model for Field Operations and More." October 1, 2024.
