Professional Documents
Culture Documents
1 6 Stability APIs
1 6 Stability APIs
WHO PQ Requirements
Presented by
Rutendo Kuwana
Accra, Ghana
December 2009
Overview
Scope of presentation Generic/Multisource preparations
API - Stress Testing
Selection of Batches
Container Closure System
Specifications: Stability indicating quality parameters
Testing Frequency
Storage Conditions
2|
Overview
Evaluation/Extrapolation of data
Statements/Labelling
Ongoing Stability Studies
3|
Stability Assessment
References
Main Generics Guideline
Supplement 2 to Main Generics Guideline
TRS 863 Annex 5, current stability guideline
TRS 937 (amendment of above)
TRS 908 (modification of storage conditions)
TRS 929 Annex 5 and Appendix 3
TRS 948
ICH Q1A, B, C, D and E
TRS 943 Variation Guide Appendix 4 (Stability Requirements for Variations)
EMR Regional Guideline based on QAS/06.179
QAS/06.179/Rev.3
Manual for Drug Regulatory Authorities (Annex 11) Etc
4|
Stability Assessment
References
Practical Approach:
Main Generics Guideline (2005) and Supplement 2 (2006)
[Referred to as Main Guide and S2 in this talk]
ICH Q1A (2003)
New WHO Stability Guide in TRS953 (2009): Annex 2:
Stability Testing of APIs and FPPs
5|
Stability - purpose
To establish a re-test period* for the API or a shelf-life for
the FPP.
To establish storage conditions.
*In exceptional cases, eg for unstable APIs, a shelf-life is
given.
6|
API
Stress Studies
Stress testing is an important part of developmental
studies. Used to:
- establish degradation pathways and intrinsic stability,
- validate stability-indicating power of methods
In considering drug stability, attention must be paid to
processes which may lead to instability of the product.
7|
API
Stress Studies
When available, it is acceptable to provide relevant data
published in the scientific literature to support the
identified degradation pathways and products.
When no data are available, stress testing should be
performed.
8|
9|
API stability
Stress testing
Requirement: 1 API batch.
Photostability testing: generally as per Q1B, however for
PQP, literature data can support/replace experimental
data:
If the PhInt, USP or EP states in the monograph for the
API or FPP, "Protect from light", there is no need to
request photostability data or testing.
10 |
API stability
Stress testing
Main Generic guideline 2.7.1 suggested conditions
11 |
(Source Handbook of stability testing and pharmaceutical development regulations, methodologies, and best practices)
12 |
Stress studies:
Approach
The impurities/degradants that must be closely investigated are those appearing
at greater than (or approaching) the identification threshold, (the limit on
individual unknowns) when stored at long-term and accelerated conditions.
A mass balance assessment may be necessary and should be based on the
decrease in assay value and the increase in the amount of degradation products.
Process related impurities to be monitored at release only with no need to
monitor during long-term stability. However, if any of these impurities are shown
to increase during storage, or if new impurities are developed, they should be
considered as degradants or degradation products, and analytical methods
must be developed to monitor them.
13 |
Selection of Batches
Definition of Primary Batches : Batches used in stability
studies to establish retest (API) or shelf-life (FPP). [ICH
Q1A and New Guide]
3 pilot batches* : For stable API, 2 pilot batches.
*For API - Pilot batches must be of the same synthesis
route, and method of manufacture and procedure that
simulate the final process for production batches.
14 |
15 |
PART TWO
16 |
API Stability:
Specifications
Specifications:
Test Methods
19 |
Polymorphism
If there is evidence that polymorph stability may be an
issue, polymorphic stability should be demonstrated as
part of routine stability studies.
For solid dosage forms, the solubility, efficacy, and
stability of a drug may depend on the particular crystalline
state of the drug. The polymorphic content may be
characterized by techniques such as x-ray powder
diffraction, Raman and infrared spectroscopy.
20 |
Testing Frequency
Long term:
Year 1: every 3 months
Year 2: every 6 months
Subsequent years: annually
Accelerated:
Minimum three points including t0 and tfinal, eg 0, 3, 6.
Intermediate:
Four points including t0 and tfinal, eg 0, 6, 9, 12.
21 |
Storage Conditions
Requirements at time of submission:
Stable API: (Supplement 2)
6 months at 40C/75%
6 months at 30C/65%
Other API:
6 months at 40C/75%
12 months at 30C/65%
PQP is moving towards long term at 30C/75% being the preferred
22 |
API Stability
Appendix 1 to TRS953
Long term stability testing conditions are determined by the
climatic condition under which the API or FPP is intended to
be stored.
Zone I: temperate
21C/45%RH
25C/60%RH
23 |
30C/65%RH
30C/75%RH
Storage Conditions II
When long term data is conducted at 25C/60% and
significant change is observed at accelerated conditions,
data should be provided at intermediate conditions (eg
30C/65%).
Tolerances - The chamber temperature must be
controlled within 2C, and the humidity controlled within
5% relative humidity.
24 |
25 |
Stability
Evaluation
Establish the retest period and storage conditions based
on stability data. The approved retest date should be
displayed on the container label and CoA. (Main Guide).
If little variability, statistical analysis is not necessary.
26 |
Evaluation
Extrapolation of data:
Common scenario: Data (6 months Accelerated and "x"
months LT) is within specifications with no significant
change under accelerated conditions. The allowed retest (API) or shelf life (FPP) is double the long-term
period "x", but NMT "x" + 12 months.
Stable API: 24 months re-test is allowed based on 6
months accelerated + 6 months long term data.
27 |
Evaluation
In prequalification, extensions beyond 24 months are not
accepted without real-time long term data on production
batches.
e.g. for a stable API, a re-test (API) or Shelf Life (FPP) of
24 months may have been accepted based on 6months
accelerated + 6months long-term, but to accept a longer
re-test period, real-time data is required.
28 |
API Stability
Evaluation
Definition: re-test period
The period of time during which the API is expected to remain
within its specification and, therefore, can be used in the
manufacture of a given FPP, provided that the API has been stored
under the defined conditions. After this period, a batch of API
destined for use in the manufacture of an FPP should be re-tested
for compliance with the specification and then used immediately. A
batch of API can be re-tested multiple times and a different portion
of the batch used after each re-test, as long as it continues to
comply with the specification. For most substances known to be
labile, it is more appropriate to establish a shelf life than a re-test
period. The same may be true for certain antibiotics.
29 |
Stability
Statements/Labeling
Recommended labeling statements provided in Appendix 3 of the
New Guide. Note that store below is no longer an option.
Storage is stated as, Do not store above
Storage statement and re-test (API) or shelf life (FPP) should be
based on evaluation, based on:
-Extent of data provided (x LT + 6 mo Acc);
-Change(s) observed;
-Actual LT storage conditions;
-Batches (all production?), etc.
30 |
31 |
32 |
Stability Commitment
Provide the post-approval stability protocol and stability-testing
commitment, when applicable (Ref to ICH Q1A/B/E)
33 |