USP General Chapters
USP <51> - Antimicrobial Effectiveness Testing
Plain-language explanation, inspection context and common violation patterns.
What it says
Multi-dose and certain other aqueous-based formulations must be tested to demonstrate that their antimicrobial preservative system effectively reduces or maintains microbial challenge organisms within defined limits over a specified time period, confirming the preservative system is adequate for the product's intended use.
Paraphrased for plain-language clarity. Always verify against the current published regulation text.
What it means in practice
- Antimicrobial effectiveness testing is not the same as sterility testing, it specifically evaluates whether the preservative system in a non-sterile or multi-dose product can control contamination introduced during normal use.
- A formulation change, even one that seems unrelated to preservative content, such as a change in pH, viscosity or a different excipient, can affect preservative effectiveness and may require retesting.
- This testing is particularly critical for multi-dose containers that are opened and used repeatedly by patients, where the container's closure integrity alone cannot prevent microbial ingress.
What inspectors look for
- Whether antimicrobial effectiveness testing was performed on the actual marketed formulation and container-closure system, not just an early development formulation.
- Whether formulation or process changes that could plausibly affect preservative effectiveness were evaluated for a need to retest.
- Whether the challenge organisms and acceptance criteria used match what the applicable USP category requires for that product type.
Most common violation
A formulation or excipient change implemented without reassessing antimicrobial effectiveness, despite the change having a plausible effect on the preservative system's performance.
Want a deeper, interactive breakdown?
GMPify's Regulation Explainer tool gives subscribers an AI-powered analysis of any 21 CFR, EU GMP, USP or ICH reference, with live inspection context.
Try the Regulation Explainer →