System validation in the pharmaceutical industry is a crucial process to ensure that computerized systems are fit for their intended use and meet current regulatory requirements. This is a mandatory requirement of cGMP (current Good Manufacturing Practices) and is essential for managing the quality of manufactured products. Any computerized system that could affect Patient Safety, Product Quality, and Data Integrity must be appropriately validated.

Read further or listen to our AI podcast:

Validation aims to build upon existing industry good practice in an efficient and effective manner. It involves demonstrating through documented evidence that each computerized system consistently produces expected results. Key regulatory requirements and guidelines informing validation in this industry include GxP (Good Practice) regulations, EudraLex Volume 4, Annex 11 on Computerised Systems, the US FDA’s 21 CFR Part 11 on Electronic Records and Electronic Signatures, and the ISPE GAMP Guide: A Risk-Based Approach to Complaint GxP Computerized Systems (GAMP 5). GAMP 5, for instance, provides practical guidance, establishes common language, and promotes a system life cycle approach based on good practice.

A computerized system in this context such as MES or EBR systems from Accevo is a set of software and hardware components that together fulfill certain functionalities. The application software should be validated, while the underlying IT infrastructure should be qualified. If a computerized system replaces a manual operation, it should not decrease product quality, process control, or quality assurance, nor should it increase the overall risk of the process.

The V-Model in System Validation

The general approach to validating a computerized system like MES or EBR integrates validation activities with the system’s implementation, typically following a System Life Cycle. This life cycle often includes phases such as Planning and Specification, Design and Development, Verification, Operation, and Retirement. The level of validation effort is commensurate with the system’s complexity (categorization) and the risk associated with its specified intended use (cGxP Criticality). The validation process is often depicted using a V-Model.

Typical validation activities and associated documentation include:

Who Validates?

Validation is carried out by various roles, including the Process owner (responsible for company process, reviewing validation documents, change management), System owner (responsible for technical issues, infrastructure, approving stages), Quality unit (responsible for quality issues, reviewing/approving specific deliverables, ensuring compliance), Project manager (overall responsibility for delivering the solution, reviewing deliverables), and the Supplier (provides system implementation, consultant services, testing).

Maintaining Validation Throughout the System Lifecycle

Validation is not just a one-time activity at implementation. Maintaining the validated state during the system’s operational life and through its retirement phase is also crucial. Activities in these phases include handover, support management, performance monitoring, incident management, CAPA, change management, repair, periodic review, backup and restore, business continuity, security management, system administration, data migration, and system retirement/disposal.

A computerized system in this context is a set of software and hardware components that together fulfill certain functionalities. The application software should be validated, while the underlying IT infrastructure should be qualified. If a computerized system replaces a manual operation, it should not decrease product quality, process control, or quality assurance, nor should it increase the overall risk of the process.

The general approach to validating a computerized system integrates validation activities with the system’s implementation, typically following a System Life Cycle. This life cycle often includes phases such as Planning and Specification, Design and Development, Verification, Operation, and Retirement. The level of validation effort is commensurate with the system’s complexity (categorization) and the risk associated with its specified intended use (cGxP Criticality). The validation process is often depicted using a V-Model.

Typical validation activities and associated documentation include:

The bottom line

Validation is carried out by various roles, including the Process owner (responsible for company process, reviewing validation documents, change management), System owner (responsible for technical issues, infrastructure, approving stages), Quality unit (responsible for quality issues, reviewing/approving specific deliverables, ensuring compliance), Project manager (overall responsibility for delivering the solution, reviewing deliverables), and the Supplier (provides system implementation, consultant services, testing).

Validation is not just a one-time activity at implementation. Maintaining the validated state during the system’s operational life and through its retirement phase is also crucial. Activities in these phases include handover, support management, performance monitoring, incident management, CAPA, change management, repair, periodic review, backup and restore, business continuity, security management, system administration, data migration, and system retirement/disposal.

Worth to know! There is a possibility to implement computerized system such as OEE in pharmaceutical industry without validation to support local non-critical system, read more here: How to implement an OEE monitoring system without validation in 3 months? – Case study.  

Check also:

MES Pharma. Software for pharma manufacturing.

Electronic Batch Records (EBR) Software