Guidelines for Stability Data Reporting in CTD Format

1) Purpose

The purpose of this Standard Operating Procedure (SOP) is to outline the procedure for reporting stability data in the Common Technical Document (CTD) format for regulatory submissions. This SOP ensures that stability data is presented in a standardized manner that meets global regulatory requirements.

2) Scope

This SOP applies to all personnel involved in the preparation, compilation, and submission of stability data in CTD format for regulatory submissions in various global markets.

3) Responsibilities

Stability Testing Team: Responsible for generating accurate stability data and ensuring it is documented correctly in the CTD format.

Quality Assurance (QA) Team: Responsible for reviewing and approving the stability data documentation.

Regulatory Affairs Team: Responsible for ensuring that the stability data package meets the requirements of the target regulatory authorities.

4) Procedure

4.1 Preparation of Stability Data for CTD Format

4.1.1 Collect all stability data generated

from the approved stability studies, including long-term, accelerated, and intermediate studies.

4.1.2 Review the data for completeness, accuracy, and any out-of-specification (OOS) results or trends.

4.2 Organizing Stability Data in CTD Format

4.2.1 Organize the stability data into the relevant sections of Module 3 of the CTD, which typically includes:

• 3.2.P.8.1 Stability Summary and Conclusions: Provide an overview of the stability study results, trends, and any OOS results.
• 3.2.P.8.2 Post-approval Stability Protocol and Stability Commitment: Describe the ongoing stability program and commitment.
• 3.2.P.8.3 Stability Data: Present the raw data in a tabular format, including test results at each time point and storage condition.

4.3 Formatting and Presentation of Data

4.3.1 Prepare stability data tables and graphs that clearly illustrate the stability profile of the product over time.

4.3.2 Ensure that all data is presented in a clear and concise manner, with appropriate units, statistical analyses, and references to relevant guidelines.

4.4 Quality Assurance Review

4.4.1 Submit the compiled stability data package to the QA Team for review.

4.4.2 Address any discrepancies or omissions identified by the QA Team and revise the data package accordingly.

4.5 Submission to Regulatory Authorities

4.5.1 Prepare the electronic submission of the stability data package in the eCTD format as per the requirements of the target regulatory authorities.

4.5.2 Submit the stability data package electronically through the appropriate submission gateway of the respective regulatory authority.

4.5.3 Retain a copy of the submitted data package and maintain all relevant records as per internal SOPs.

5) Abbreviations, if any

CTD: Common Technical Document
OOS: Out-of-Specification
eCTD: Electronic Common Technical Document
QA: Quality Assurance

6) Documents, if any

Stability data sheets, stability testing records, compiled stability data package, electronic submission records.

7) Reference, if any

ICH M4: Common Technical Document for the Registration of Pharmaceuticals for Human Use, US FDA Guidance for Industry: Stability Testing of Drug Substances and Drug Products, CFR Title 21.

8) SOP Version

Version 1.0