eCTD XML Backbone: Complete Technical Guide to Structure, DTD, and Validation
The eCTD XML backbone consists of index.xml and regional.xml files that serve as the navigational foundation for regulatory submissions. Index.xml defines the structure of Modules 2-5 using leaf elements with unique IDs, MD5 checksums, and lifecycle operations (new, replace, append, delete), while regional.xml files contain Module 1 content specific to FDA, EMA, Health Canada, or PMDA requirements. XML validation errors account for 23% of all eCTD gateway rejections, making backbone validation critical for submission success.
Key Takeaways
Key Takeaways
- XML validation errors account for 23% of all eCTD gateway rejections, the single largest failure category
- Index.xml defines the structure of Modules 2-5 using leaf elements with unique IDs, MD5 checksums, and lifecycle operations
- Regional.xml files (us-regional.xml, eu-regional.xml) contain Module 1 content specific to each regulatory authority
- Each leaf element must have a unique ID, correct MD5 checksum, and valid lifecycle operation (new, replace, append, delete)
- The DTD (Document Type Definition) specifies the schema rules that the XML backbone must conform to for each ICH region
- The eCTD XML backbone is the foundational XML file structure that provides navigation, metadata, and lifecycle management for Electronic Common Technical Document (eCTD) submissions. Consisting of the index.xml master file and region-specific XML files (us-regional.xml, eu-regional.xml), the eCTD XML backbone creates the hyperlinked structure that enables regulatory reviewers to navigate through thousands of documents efficiently.
- For regulatory teams, understanding the eCTD XML backbone is essential for successful submission publishing. XML validation errors account for 23% of all gateway rejections - the single largest category of eCTD failures. A malformed backbone file means your entire submission cannot be processed, regardless of how perfect your PDF documents are.
- In this guide, you'll learn:
- The complete technical structure of index.xml and how leaf elements define document metadata
- Regional.xml requirements for FDA, EMA, Health Canada, and PMDA submissions
- DTD and schema specifications including ich-ectd-3-2.dtd and v4.0 XSD
- Lifecycle operations (new, replace, append, delete) and when to use each
- Common eCTD XML validation errors and how to prevent them
- ---
What Is the eCTD XML Backbone?
The eCTD XML backbone is the set of XML files (index.xml and regional.xml) that serve as the structural foundation and navigation layer for an eCTD submission, defining document inclusion, location, relationships, and lifecycle changes across submission sequences. The backbone enables regulatory reviewers and automated systems to process submissions and validates against Document Type Definition (DTD) or XML Schema (XSD) specifications.
The eCTD XML backbone is the set of XML files that serve as the structural foundation and navigation layer for an eCTD submission. These XML files define which documents are included, where they are located, how they relate to each other, and how they change across submission sequences.
Key characteristics of the eCTD XML backbone:
- Creates the navigable table of contents for regulatory reviewers
- Stores metadata for every document (title, location, checksum, operation)
- Enables lifecycle management across multiple submission sequences
- Validates against Document Type Definition (DTD) or XML Schema (XSD)
- Supports hyperlinked navigation between related documents
The eCTD XML backbone was introduced in ICH M8 version 1.0 (2003) and has evolved through version 3.2.2 (DTD-based) to version 4.0 (XSD-based), with v3.2.2 remaining the most widely implemented globally as of 2026.
The backbone consists of two primary file types that work together:
| File Type | Purpose | Scope |
|---|---|---|
| index.xml | Master navigation file containing Modules 2-5 structure | Global (harmonized) |
| regional.xml | Region-specific Module 1 content and metadata | Regional (varies by agency) |
Together, these files create a complete map of the submission that both human reviewers and automated validation systems use to process the eCTD.
Understanding eCTD XML Structure: index.xml Explained
The index.xml file is the heart of the eCTD XML backbone. It serves as the master table of contents for the entire submission, defining the structure of harmonized Modules 2 through 5 and linking to regional XML files for Module 1 content.
index.xml File Location and Purpose
The index.xml file must be located at the root of each sequence folder:
index.xml Structure Breakdown
The index.xml follows a hierarchical structure matching the eCTD module organization:
Always validate your index.xml against the correct DTD version before submission. Version mismatches (e.g., using v3.2.2 DTD when your XML declares v4.0) are among the easiest errors to introduce and hardest to catch without proper validation tools. Use XML editors with built-in DTD validation to catch these errors in real-time.