Standard Operating Procedure for XML Backbone Review and Validation
| Department | Regulatory Affairs |
| SOP No. | RA/2026/688 |
| Supersedes | NA |
| Page No. | 1 of X |
| Issue Date | 12/04/2026 |
| Effective Date | 12/04/2026 |
| Review Date | 12/04/2028 |
Purpose
This Standard Operating Procedure (SOP) provides a structured and controlled approach for the systematic review and validation of the XML Backbone within electronic Common Technical Document (eCTD) submissions. It ensures accuracy, completeness, and compliance with regulatory requirements and internal quality standards to facilitate successful submissions and minimize regulatory risks.
Scope
This SOP applies to all activities related to the preparation, review, and validation of the XML Backbone files in eCTD submissions prepared by the Regulatory Affairs department. It covers XML Backbone validation during submission QC and prior to dispatch to regulatory authorities. The SOP is applicable to all pharmaceutical products, dosage forms, and submission types managed electronically. It excludes non-XML submission documentation and IT system validation unrelated to eCTD backbone content.
Responsibilities
– Regulatory Affairs Document Specialist: Responsible for initial XML Backbone preparation and QC.
– Regulatory Affairs Reviewer: Responsible for detailed XML Backbone review ensuring coding accuracy and linkage validation.
– Regulatory Affairs Supervisor: Oversees compliance, monitors workflow, and approves final XML Backbone validation.
– Quality Assurance (QA): Verifies adherence to internal and regulatory standards and performs periodic audits.
– Submission Coordinator: Manages submission timelines and document control post-validation.
Accountability
The Regulatory Affairs Head holds overall accountability for ensuring this SOP is effectively implemented, maintained, and reviewed. This role is responsible for enforcing compliance, escalating deviations, ensuring periodic review and continuous improvement, and authorizing final XML Backbone submission readiness.
Procedure
The XML Backbone review and validation process shall be conducted through the following detailed steps:
1. Preparation and Prerequisites:
– Ensure the XML Backbone files generated by the publishing software correspond to the submission content.
– Verify that all submission modules and documents are final and approved.
– Confirm the use of the latest validation tools and software versions.
2. Initial XML Check:
– Perform a preliminary validation using XML validation tools to check for syntax errors or missing required elements.
– Document any errors found and liaise with the publishing team for corrections.
3. Structural Validation:
– Validate the backbone structure against the eCTD specification, including correct node hierarchy, attribute use, and schema compliance.
– Confirm accuracy of leaf nodes and linkage between the backbone and submission files.
– Ensure language and regional code attributes are correctly applied.
4. Linkage Verification:
– Verify all href links in the backbone correctly point to actual submission files.
– Check for broken links or references to obsolete files and resolve defects promptly.
– Confirm all mandatory files are present and linked.
5. Compliance and GMP Checks:
– Ensure the XML Backbone meets all applicable regulatory requirements and internal SOPs.
– Confirm that metadata such as submission type, sequence number, and filing dates are accurate.
– Check for completeness regarding module inclusion as per dossier type.
6. Quality Control and Peer Review:
– The reviewer independently re-checks the backbone validation, focusing on areas frequently prone to error.
– Document all findings, clarifications, and corrective actions.
– Obtain necessary supervisory approvals before proceeding.
7. Documentation and Record Keeping:
– Complete the XML Backbone Validation Checklist (Annexure-1) capturing all validation outcomes.
– File validation reports and signed checklists in the regulatory document management system.
– Retain records as per retention policies for audit readiness.
8. Deviation Management & Escalation:
– If deviations or non-conformities occur, log the incidents per the deviation reporting SOP.
– Notify the Regulatory Affairs Head for risk assessment and remediation planning.
– Re-validate corrected XML Backbone as necessary.
9. Final Approval and Submission Dispatch:
– Obtain documented approval from Regulatory Affairs Supervisor.
– Release the validated XML Backbone files for inclusion in the eCTD submission.
– Coordinate with Submission Coordinator for dispatch and tracking.
This procedure must be strictly followed to maintain compliance, reduce regulatory risks, and ensure timely product approvals.
Abbreviations
eCTD – electronic Common Technical Document
XML – Extensible Markup Language
SOP – Standard Operating Procedure
QC – Quality Control
QA – Quality Assurance
GMP – Good Manufacturing Practices
Documents
The following documents are specific to the XML Backbone Review and Validation SOP and required for the controlled execution of the procedure:
- XML Backbone Validation Checklist (Annexure-1)
- XML Backbone Validation Report (Annexure-2)
- Deviation Report Form for XML Backbone Non-Conformance (Annexure-3)
References
– ICH M2 eCTD Specifications
– FDA eCTD Guidance for Industry
– EMA eCTD Validation Criteria
– Internal Document Control and Quality Management System Policies
– PIC/S GMP Guidelines Section on Documentation and Submission Controls
Version
1.0
Approval
| Prepared By | |
| Checked By | |
| Approved By |
Annexures
Annexure-1: XML Backbone Validation Checklist
| Field | Description | Example/Dummy Data |
|---|---|---|
| Checklist ID | Unique identifier for the checklist | XMLBC-VAL-20260412-001 |
| Date of Validation | Date when validation was performed | 12/04/2026 |
| XML File Name | Name of the backbone XML file reviewed | submission_sequence_001.xml |
| Syntax Validation | Result of XML syntax check | Passed |
| Structural Validation | Result of eCTD schema and node hierarchy check | Passed |
| Linkage Verification | Verification of hrefs and linked files | All links verified, no broken links |
| Metadata Accuracy | Verification of submission metadata correctness | Sequence number, filing date accurate |
| Deviations Found | Any deviations or non-conformities identified | None |
| Remarks | Additional notes | XML backbone ready for submission |
| Validated By | Role and signature placeholder | Regulatory Affairs Document Specialist |
| Date | Validation signature date | 12/04/2026 |
| Reviewed By | Role and signature placeholder | Regulatory Affairs Reviewer |
| Date | Review signature date | 12/04/2026 |
| Approved By | Role and signature placeholder | Regulatory Affairs Supervisor |
| Date | Approval signature date | 12/04/2026 |
Annexure-2: XML Backbone Validation Report
| Field | Description | Example/Dummy Data |
|---|---|---|
| Report ID | Unique validation report identifier | XMLBC-VAL-RPT-20260412-001 |
| Document Reviewed | Backbone file name and version | submission_sequence_001.xml |
| Date of Review | Date when review was conducted | 12/04/2026 |
| Scope of Review | Details on what was validated | Syntax, structure, linkage, metadata accuracy |
| Validation Outcome | Overall result of validation activities | Pass, no critical findings |
| Findings/Comments | Summary of issues identified and resolutions | Minor typographical error in metadata corrected prior to final approval |
| Conclusion | Validation conclusion statement | XML Backbone meets all regulatory and internal quality standards. |
| Prepared By | Role placeholder | Regulatory Affairs Document Specialist |
| Date | Date of preparation | 12/04/2026 |
| Reviewed By | Role placeholder | Regulatory Affairs Reviewer |
| Date | Review date | 12/04/2026 |
| Approved By | Role placeholder | Regulatory Affairs Supervisor |
| Date | Approval date | 12/04/2026 |
Annexure-3: Deviation Report Form for XML Backbone Non-Conformance
| Field | Description | Example/Dummy Data |
|---|---|---|
| Deviation ID | Unique identifier for deviation | DEV-XMLBC-20260412-01 |
| Date of Occurrence | Date when deviation was detected | 12/04/2026 |
| Description of Deviation | Detailed description of the issue | Broken href link detected in XML Backbone pointing to missing document |
| Impact Assessment | Evaluation of deviation impact on submission | Potential rejection of sequence by regulatory authority |
| Root Cause Analysis | Findings on cause of deviation | Publishing software error causing link omission |
| Corrective Action Taken | Measures implemented to resolve deviation | Republished XML Backbone after manual correction of href links |
| Preventive Action | Steps to avoid recurrence | Enhanced QC checks and updated publishing SOP |
| Deviation Reported By | Role placeholder | Regulatory Affairs Document Specialist |
| Date Reported | Date report filed | 12/04/2026 |
| Reviewed By | Role placeholder | Regulatory Affairs Supervisor |
| Date Reviewed | Date of review | 13/04/2026 |
| Closure Approved By | Role placeholder | Regulatory Affairs Head |
| Date Approved | Approval date for deviation closure | 14/04/2026 |
Revision History
| Revision Date | Revision No. | Revision Details | Reason for Revision | Approved By |
| 12/04/2026 | 1.0 | Initial issue | New SOP creation |