expiry terms ICH WHO – StabilityStudies.in https://www.stabilitystudies.in Pharma Stability: Insights, Guidelines, and Expertise Fri, 11 Jul 2025 15:21:05 +0000 en-US hourly 1 https://wordpress.org/?v=6.8.3 ICH and WHO Interpretations of Expiry Terminology Explained https://www.stabilitystudies.in/ich-and-who-interpretations-of-expiry-terminology-explained/ Fri, 11 Jul 2025 15:21:05 +0000 https://www.stabilitystudies.in/ich-and-who-interpretations-of-expiry-terminology-explained/ Read More “ICH and WHO Interpretations of Expiry Terminology Explained” »

]]>
In the global pharmaceutical industry, the terms “shelf life”, “expiry date”, and “retest date” carry significant regulatory meaning. Misinterpreting or misapplying these terms can lead to non-compliance, labeling deviations, and product recalls. This tutorial unpacks how two major international regulatory bodies—ICH and WHO—define and use expiry-related terminology, and how pharma professionals can ensure consistency across submissions, labels, and quality systems.

🌐 Why Global Consistency in Expiry Terminology Matters

Multinational pharmaceutical companies often market the same product across various regions. However, expiry-related terms may differ in meaning between jurisdictions:

  • ❌ “Retest date” may be accepted in one region and rejected in another
  • ❌ Shelf life vs. expiry might be used interchangeably, causing confusion
  • ❌ Inconsistent use of terms across dossiers can result in questions during review

To harmonize these differences, the ICH and WHO have developed structured guidance.

ICH Interpretation of Expiry Terminology

The International Council for Harmonisation (ICH) provides guidance primarily through ICH Q1A(R2), Q1B, and Q7. Key definitions include:

  • Shelf Life: The time period during which a drug product is expected to remain within approved specifications, stored under defined conditions.
  • Expiry Date: The date placed on the label designating the time during which the product is expected to remain stable.
  • Retest Date: The date by which an API should be re-examined to ensure it is still suitable for use.

Key Point: ICH encourages using “retest date” for APIs and “expiry date” for finished products, as detailed in ICH Q7.

WHO Interpretation of Expiry Terminology

The World Health Organization (WHO), through its stability and prequalification guidelines, aligns closely with ICH definitions but adds clarity in global health contexts.

According to WHO:

  • Expiry Date: The date after which the product is not guaranteed to remain within specifications and should not be used.
  • Retest Date: For APIs, the date beyond which testing is required prior to further use, provided storage is under defined conditions.
  • Labeling Requirements: WHO explicitly requires clear indication of expiry or retest date depending on material type and regulatory filing.

WHO also emphasizes expiry control as a GMP principle, especially for medicines supplied through procurement programs.

📋 Case Comparison: API Labeling for Retest vs Expiry

Consider a bulk API manufactured in India and exported to the EU and Africa. The same material may be labeled as follows:

  • ✅ For EU (ICH territory): “Retest date: MM/YYYY”
  • ✅ For WHO procurement: “Expiry date: MM/YYYY” based on receiving country’s guideline

This dual terminology must be addressed in regulatory documentation, quality agreements, and COAs.

For guidance on aligning terminology in SOPs, see Pharma SOPs best practices.

🎯 Common Challenges with Expiry Terminology

  • ❌ Labeling APIs with both expiry and retest dates inconsistently
  • ❌ Not updating ERP master data to reflect ICH-compliant terms
  • ❌ Misinterpreting WHO’s requirement as mandatory expiry for all materials
  • ❌ Using “shelf life” in documents without defining it clearly

Each of these can be addressed through cross-functional training and regulatory review.

✅ Best Practices for Aligning with ICH and WHO

Here’s a checklist to align expiry terminology across your systems:

  • ✅ Define “shelf life”, “retest date”, and “expiry date” in all SOPs
  • ✅ Align ERP and labeling logic with ICH Q1A and Q7 terminology
  • ✅ Use retest dates for APIs unless local regulation demands expiry
  • ✅ Avoid using “shelf life” alone—tie it to a defined specification or condition
  • ✅ Train Regulatory Affairs and QA on WHO vs. ICH interpretations

These steps help ensure consistency across labeling, submission documents, and inspection responses.

📂 Integration in Dossiers and CTDs

In Common Technical Documents (CTDs), expiry and shelf life terms appear in Module 3 (Quality), particularly in sections:

  • 3.2.P.8 – Stability Summary and Conclusion
  • 3.2.S.7 – Stability of APIs
  • Labeling section for Module 1 (country-specific)

Ensure terminology matches across modules and appendices to prevent delay in approvals.

📦 Impact on Labeling and Packaging Control

Both WHO and ICH require clear labeling of expiry or retest dates on all containers:

  • ✅ Finished Products: “Expiry date” is mandatory
  • ✅ APIs: “Retest date” may be used unless national regulation states otherwise
  • ✅ Secondary packaging must display the date clearly and be resistant to smearing or abrasion

Reconciliation of expiry labeling must be part of QA release procedures. For guidance, review GMP guidelines.

📊 Table: Summary of Differences

Aspect ICH WHO
API Term Retest Date Retest or Expiry (based on context)
Finished Product Expiry Date Expiry Date
Use of “Shelf Life” Refers to period before expiry or retest Similar, but emphasized in procurement guidance
Label Requirement Depends on form (API vs product) Always mandate one or the other

Conclusion

Clear understanding and consistent application of expiry terminology—as defined by ICH and WHO—are vital for regulatory success, global compliance, and patient safety. While both organizations offer aligned guidance, their emphasis and context can vary depending on the type of product and country of sale.

Pharma professionals should ensure SOPs, ERP systems, submission documents, and labels reflect harmonized terminology, supported by sound stability data and regulatory knowledge.

References:

]]>