Home / Resources / CSV guidance

CSV guidance · 6 min read

Computerised System Validation in Practice: What Inspectors Expect from GxP Systems

Computerised systems are widely used across pharmaceutical manufacturing, laboratory testing, quality management, warehousing, and regulatory documentation. Examples include Laboratory Information Management Systems (LIMS), Manufacturing Execution Systems (MES), electronic Quality Management Systems (eQMS), Enterprise Resource Planning (ERP) platforms, and electronic batch-record systems.

When these systems support GxP-regulated activities, organizations must demonstrate that they are suitable for their intended use and that they protect product quality, patient safety, and data integrity.

Computerised System Validation (CSV) is not simply a software-testing exercise. It is a documented, risk-based process for establishing and maintaining confidence that a system consistently performs its intended functions throughout its lifecycle.

This article explains the practical areas organizations should review when preparing for a GxP inspection or computerised-system audit.

1. Define the System's Intended Use

Validation begins with understanding what the system is expected to do and how it supports regulated activities.

The organization should document:

  • The system's intended purpose and GxP impact.
  • The business and quality processes it supports.
  • The functions that may affect product quality or data integrity.
  • User requirements and acceptance criteria.
  • Interfaces with other systems and external services.
  • Responsibilities of system owners, process owners, IT, Quality Assurance, and suppliers.

For example, a spreadsheet used to calculate a critical laboratory result may require different controls from a spreadsheet used only for routine administrative planning.

The extent of validation and control should be justified by the system's intended use and associated risks.

2. Apply a Risk-Based Validation Approach

Not every system function carries the same level of risk. A risk assessment helps determine the validation activities and controls necessary for each system.

Consider the potential consequences of:

  • Incorrect calculations or processing.
  • Loss, alteration, or unavailability of records.
  • Unauthorized access or changes.
  • Failure of interfaces between systems.
  • Incorrect configuration or software updates.
  • Inadequate backup, recovery, or retention.
  • System failures that interrupt critical operations.

Document the identified risks, the controls selected to address them, and the evidence used to demonstrate that those controls are effective.

Risk assessments should be reviewed when significant system changes, new uses, recurring failures, or other relevant circumstances arise.

3. Validation Documentation and Evidence

Inspectors may examine whether validation activities were planned, executed, reviewed, and approved appropriately.

Depending on the system and its risk, relevant documentation may include:

  • User requirements specifications (URS).
  • Functional and configuration specifications, where applicable.
  • System and data-flow diagrams.
  • Risk assessments.
  • Validation plans and reports.
  • Installation, operational, and performance testing evidence, where applicable.
  • Test scripts, actual results, and documented deviations.
  • Requirements traceability.
  • Supplier assessments and relevant supplier documentation.
  • Change-control and release records.
  • Procedures for operation, maintenance, and support.

Documentation should provide a traceable link between intended requirements, identified risks, implemented controls, testing, and the final decision that the system is fit for its intended use.

The objective is not to produce the maximum number of documents. It is to provide sufficient, reliable evidence that the system is appropriately controlled.

4. Audit Trails and Data Integrity

Data integrity is a major consideration for systems that create, process, modify, or retain GxP records.

The ALCOA+ principles provide a useful framework: data should be attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available.

During an audit, organizations should be able to demonstrate appropriate controls for:

  • Individual user identification and access privileges.
  • Audit-trail generation and review, where applicable.
  • Recording of relevant data changes and associated reasons.
  • Electronic signatures and their linkage to records.
  • Protection against unauthorized modification or deletion.
  • Data retention, retrieval, and archival.
  • Backup and recovery.
  • Management of system-generated records and interfaces.

An audit trail being enabled does not, by itself, demonstrate effective control. The organization should establish which events require review, who performs the review, how frequently it occurs, and how unusual activity is investigated.

5. User Access and System Security

Access controls should ensure that users can perform their assigned tasks without having unnecessary privileges.

Review whether:

  • Access is approved and assigned according to role.
  • User accounts are individual and traceable.
  • Privileges are removed or modified when responsibilities change.
  • Administrator access is appropriately restricted.
  • Access reviews are performed according to procedure.
  • Passwords and authentication mechanisms meet applicable requirements.
  • Security incidents are documented and assessed.
  • Supplier and remote access are controlled.

Shared accounts, excessive privileges, inactive accounts, and poorly controlled administrator access can weaken accountability and data reliability.

6. Supplier and Service-Provider Oversight

Many GxP systems depend on external software vendors, cloud services, IT infrastructure providers, or outsourced support teams.

Organizations should assess the supplier's relevance to the system's intended use and the risks associated with outsourced activities.

Important considerations include:

  • Supplier capability and quality-system controls.
  • Defined responsibilities and service expectations.
  • Documentation and testing evidence provided by the supplier.
  • Management of system updates and security patches.
  • Incident notification and support arrangements.
  • Data ownership, access, retention, and retrieval.
  • Backup, recovery, and business continuity.
  • Change notification and service termination arrangements.

Using a reputable vendor does not transfer the organization's responsibility for ensuring that its GxP systems remain suitable and controlled.

7. Change Control and Periodic Review

A validated system must remain in a controlled state after implementation.

Changes to software, infrastructure, configuration, interfaces, intended use, or business processes should be assessed before implementation through an appropriate change-control process.

Depending on the change, the organization may need to perform risk reassessment, regression testing, updated documentation, user training, or additional validation activities.

Periodic reviews should assess whether the system remains fit for its intended use. Relevant inputs may include:

  • System incidents and deviations.
  • Change history and recurring problems.
  • Audit-trail review outcomes.
  • User access and security controls.
  • Backup and recovery evidence.
  • Outstanding risks and CAPAs.
  • Supplier performance and support status.
  • Current system documentation and validation status.

The review frequency and depth should be justified by risk, system criticality, and applicable procedures.

8. Common Findings During GxP System Audits

Potential weaknesses include:

  • Validation evidence that does not adequately cover intended use.
  • Requirements that cannot be traced to testing or other verification.
  • Incomplete investigation of failed tests.
  • Uncontrolled changes to validated systems.
  • Inadequate access management.
  • Audit trails that are not reviewed effectively.
  • Missing evidence of backup restoration or recovery testing.
  • Unclear responsibility for supplier-managed services.
  • Outdated procedures or system documentation.
  • Periodic reviews that do not evaluate continuing fitness for use.

The significance of each issue depends on the system, the records involved, and its potential impact on product quality, patient safety, and data integrity.

9. A Practical CSV Readiness Checklist

  • System intended use and GxP impact are documented.
  • Risk assessment is approved and reflects actual system use.
  • Requirements and validation evidence are traceable.
  • Test failures and deviations are documented and assessed.
  • User access and administrator privileges are controlled.
  • Audit trails and electronic signatures are appropriately managed.
  • Backup, recovery, and data-retention controls are supported by evidence.
  • Supplier responsibilities and outsourced services are assessed.
  • Changes are controlled and assessed before implementation.
  • Periodic reviews and required CAPAs are current.

Conclusion

Effective computerised system validation requires a lifecycle approach that combines risk management, reliable documentation, data-integrity controls, supplier oversight, and ongoing system review.

The key question is not merely whether a system was validated at implementation, but whether the organization can demonstrate that it remains suitable, secure, and controlled throughout its use.

PharmaTrak helps organizations assess GxP compliance through independent, evidence-based audits, supporting the identification of system-control gaps and data-integrity risks.

Regulatory note: This article is for general educational purposes. Validation expectations should be determined using the applicable GMP requirements, system risk assessment, and approved procedures. EU GMP Annex 11 and related guidance should be checked in their current official versions before being used to support a compliance decision.

Discuss your audit requirements

Independent, evidence-based GxP audits from PharmaTrak.

Request an Audit