USP General Chapters
USP <785> - Osmolality and Osmolarity
Plain-language explanation, inspection context and common violation patterns.
What it says
Osmolality and osmolarity of a formulation must be measured using appropriate, validated methods, particularly important for parenteral and ophthalmic products where a mismatch with physiological tonicity can cause patient discomfort or tissue damage upon administration.
Paraphrased for plain-language clarity. Always verify against the current published regulation text.
What it means in practice
- Osmolality testing connects directly to patient comfort and safety at the point of administration, an injectable or ophthalmic product with inappropriate tonicity can cause pain, tissue irritation or hemolysis regardless of how well it otherwise meets its chemical specifications.
- This measurement is particularly relevant for formulations intended for sensitive administration routes, including ophthalmic, intrathecal and certain parenteral products, where the margin for tonicity deviation is narrow.
- A formulation change involving excipients that affect osmotic contribution, even one not intended to change tonicity, can shift osmolality enough to warrant retesting.
What inspectors look for
- Whether osmolality or osmolarity testing was performed on formulations intended for sensitive administration routes where tonicity affects patient comfort or safety.
- Whether formulation changes affecting osmotic contribution were evaluated for their impact on measured osmolality before being implemented.
- Whether the test method used is validated and appropriate for the specific formulation type being measured.
Most common violation
A formulation change to an injectable or ophthalmic product that affects osmotic contribution, implemented without retesting osmolality to confirm the product remains within an appropriate tonicity range.
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 →