Although GAMP 4 is now obsolete, its core philosophy—risk-based, lifecycle validation—remains intact in . The shift to GAMP 5 brought greater flexibility for evolving technologies (e.g., AI, blockchain, SaaS) and aligned with ICH Q8–Q10 (Quality by Design, Quality Systems). Nevertheless, many long-standing industry professionals still reference GAMP 4 concepts when understanding validation fundamentals.
, a linear and sequential approach to software validation. At the time, this "Waterfall" method was the gold standard. It focused on a rigid hierarchy of documentation: User Requirements Specification (URS): What the user needs. Functional Specification (FS): What the system does. Design Specification (DS): How the system is built. Testing (IQ/OQ/PQ): Verifying each of those layers through Installation, Operational, and Performance Qualification. Under GAMP 4, validation was often treated as a "finish line" activity—something you did at the very end of a project before going live. The Software Categories of GAMP 4 One of the most lasting contributions of GAMP 4 was its categorization of software, which helped teams decide how much documentation was necessary: Category 1: Infrastructure Software (e.g., Operating Systems). Category 2: Standard Software (Replaced in later versions). Category 3: Non-Configurable Software (e.g., simple firmware or calculators). Category 4: Configurable Software (e.g., LIMS or ERP systems where you can change settings but not the core code). Category 5: Bespoke (Custom) Software. Why Did We Move Away from It? While GAMP 4 provided much-needed structure, it had its drawbacks. Its prescriptive nature often led to a gamp 4 guidelines