Gamp Category 4 Examples Guide

Just then, the validation script failed on Test ID 47. The configured workflow rule “Retest on OOS” had been set to “2 retests max”—but the system allowed a third.

Here’s a short story built around examples (configured software products). Title: The Validation Window gamp category 4 examples

“Example four.” She smiled. “We mapped fields between LIMS and ERP—so a ‘pass’ result in LIMS automatically creates a ‘release order’ in ERP. The mapping is configuration. The underlying software doesn’t change.” Just then, the validation script failed on Test ID 47

Lena sighed. “Document the deviation. Change the config, re-run the test. That’s GAMP Category 4 life.” Title: The Validation Window “Example four

By midnight, the corrected configuration passed. The batch was saved—not by writing new code, but by proving that the configured system did exactly what they intended.

Tom frowned. “What about the ERP integration?”

GAMP Category 4 refers to configured software —off-the-shelf products that are customized through settings, parameters, or user-defined rules (e.g., ERP systems, LIMS, SCADA, or a laboratory instrument’s configuration). They require validation of the configuration, not the base code.