GMP Impact of System Configuration Not Matching SOP Instructions

Introduction to the Audit Finding

1. Key Issue Identified

Auditors discovered that IT systems used in GMP environments were not configured as described in corresponding SOPs. For example, access privileges, password policies, and audit trail settings differed from documented procedures.

2. Regulatory Implications

• Violates principles of computerized system validation (CSV)
• Leads to data integrity concerns if audit trails or access control are misconfigured
• Breaks trust between documented procedures and actual system operations

3. Typical Audit Scenario

Audit trail was found disabled for certain operations even though the SOP mandated continuous tracking. Password change interval in the system was set to 180 days, while the SOP required 90 days.

Regulatory Expectations and Inspection Observations

1. 21 CFR Part 11.10(a) and (d)

Requires that systems used in regulated environments are validated and operate in accordance with pre-established written procedures.

2. EU GMP Annex 11, Clause 4 and 5

Emphasizes that configuration must reflect what is written in SOPs, particularly around access control and data retention.

3. GAMP 5 Principle

System configuration must be documented and traceable to functional requirements defined in SOPs and validation documentation.

4. Regulatory Findings

• FDA 483: “System password settings did not match the configuration described in the approved SOP.”
• CDSCO: “Audit trail not enabled for a critical system function, although mandated by SOP.”

Root Causes of Configuration-SOP Mismatch

1. Poor Communication Between IT and QA

System administrators implement settings without consulting QA or SOPs.

2. Inadequate SOP Review During System Setup

IT teams rely on vendor defaults rather than cross-checking against SOPs.

3. Lack of Change Management Discipline

System configurations are modified without proper change control, and SOPs are not updated accordingly.

4. Misalignment Between Validation and SOP Authors

Validation teams and SOP authors work in silos, resulting in diverging functional assumptions.

Prevention of System-SOP Misalignment

1. Cross-Functional Configuration Committees

Include QA, IT, and Validation representatives during system design, configuration, and SOP drafting phases.

2. Configuration Verification Checklists

• Establish SOP-linked verification points before releasing system for use
• Perform dry-runs comparing SOP steps vs. actual system behavior

3. Validation Alignment

Ensure that configuration documented in pharma validation protocols matches SOP steps one-to-one.

4. Periodic IT Compliance Audits

Internal IT auditors should review system setup vs. current SOPs quarterly or post-major change.

5. SOP for Configuration Management

Define a specific SOP that governs how system configurations must be documented, reviewed, and approved.

Corrective and Preventive Actions (CAPA)

1. Corrective Measures

• Revalidate all affected systems
• Reconfigure settings to match the active SOP
• Document discrepancy reports for all deviations

2. Preventive Strategies

Revise SOPs to include detailed configuration parameters, supported by screenshots or configuration logs.

3. Training Initiatives

Train IT and QA teams on interpreting and executing SOPs during system configuration activities.

4. Regulatory Best Practice Reference

Align practices with USFDA CSV guidance and TGA recommendations on computerized system lifecycle management.

Why Absence of SOPs for Data Integrity Threatens GMP Compliance

Introduction to the Audit Finding

1. The Core Issue

The complete absence of SOPs that define data integrity expectations, monitoring, and controls is a significant GMP gap.

2. Implications

This exposes the site to risks of falsified data, unverified audit trails, and non-compliance with regulatory requirements.

3. ALCOA+ Principles Neglected

Without documented SOPs, there is no guarantee that data is attributable, legible, contemporaneous, original, and accurate (ALCOA+).

4. Lack of Accountability

No written responsibilities for electronic system access, audit trail review, or deviation documentation creates systemic vulnerability.

5. Regulatory Red Flags

Data integrity is a cornerstone of GMP. Its absence triggers critical findings in USFDA, MHRA, and CDSCO inspections.

6. Broad Impact

Applies across QA, QC, production, engineering — any department generating or reviewing GMP data.

7. Common Violations

“No SOP for audit trail review,” “No documented data handling procedure,” “No controls for electronic data editing.”

8. Why SOPs Are Foundational

SOPs serve as binding instructions for data reliability, review frequency, corrective measures, and retention periods.

Regulatory Expectations and Inspection Observations

1. 21 CFR Part 11 and 211

Mandates procedural controls to ensure data authenticity, accuracy, and confidentiality — through documented instructions.

2. MHRA GxP Data Integrity Guidance

States data integrity SOPs are essential for every GxP process, especially around audit trail generation and review.

3. WHO Annex 5 TRS 996

Calls for SOPs that cover electronic and paper data generation, processing, review, and archiving practices.

4. EMA’s Q&A on Data Integrity

Emphasizes need for SOPs that detail the entire data lifecycle and how integrity is maintained at each stage.

5. USFDA Warning Letters

“Failure to establish SOPs for controlling laboratory data modification,” “No procedure to review audit trails for chromatographic systems.”

6. CDSCO Observations

Indian authorities often cite lack of SOPs for audit trail review and data backup in their inspection reports.

7. Key Terminology in Observations

“Absence of procedural controls,” “No documented data integrity assurance,” “Gaps in record lifecycle management.”

8. International Trends

Global agencies are harmonized in expecting SOP-governed data integrity practices across all GxP processes.

Root Causes of SOP Absence for Data Integrity

1. Underestimation of Digital Risks

Firms assume computerized systems are self-compliant without procedural reinforcement.

2. Legacy System Dependence

Older equipment lacks audit trail features, and no SOPs were written to address manual integrity controls.

3. Inadequate QA Oversight

Quality units may lack digital literacy to draft effective SOPs for computerized system governance.

4. Decentralized Data Ownership

No clarity on who is responsible for generating, verifying, and reviewing data in each department.

5. Overlooked by Change Control

Implementation of new systems without concurrent SOP development or updates.

6. Absence of Regulatory Awareness

Teams unfamiliar with data integrity guidance from ICH guidelines for pharmaceuticals or MHRA documentation.

7. Poor Document Control System

No SOPs were drafted due to non-functional document management or lack of trained SOP writers.

8. Lack of SOP Writing Templates

Organizations may not have standardized templates for writing data governance SOPs.

Prevention of SOP Absence in Data Integrity

1. Conduct Data Integrity Gap Assessment

Audit each department for missing SOPs on data handling, audit trail review, and backup processes.

2. Use a Master List of Data Integrity SOPs

Create and maintain a centralized tracker showing which data SOPs exist and which are pending.

3. Adopt Standardized SOP Templates

Use predefined templates that enforce inclusion of critical ALCOA+ elements and procedural controls.

4. Form a Cross-Functional DI Taskforce

Establish a team across QA, QC, IT, and Production to co-own SOP writing and implementation.

5. Link SOPs to System Lifecycle

Mandate that every new computerized system must have SOPs before it goes live.

6. Reference Global Guidelines

Incorporate elements from USFDA, WHO, EMA, and MHRA data guidance in SOP structure.

7. Integrate with Training Matrix

Make data integrity SOP training mandatory for all system users, supervisors, and reviewers.

8. Ensure Periodic Review of SOPs

Build review timelines into SOPs to account for system upgrades or regulatory changes.

Corrective and Preventive Actions (CAPA)

1. Draft and Approve Core SOPs

Immediately create SOPs for audit trail review, data backup, access control, and change tracking.

2. Review All Computerized Systems

Identify which systems lack associated data governance SOPs and assign owners to draft them.

3. Revise Existing SOPs

Update older SOPs to include specific data integrity controls like time-stamped entries and audit trail monitoring.

4. Train All Staff

Roll out targeted data integrity SOP training sessions — ensure completion is documented.

5. Conduct DI Audits

Perform internal audits focused exclusively on data integrity practices and SOP compliance.

6. Strengthen QA Oversight

Assign QA responsibility for data integrity SOP implementation and monitoring effectiveness.

7. Set SOP Development KPIs

Make timely creation of data integrity SOPs a performance metric for QA and compliance teams.

8. Review Industry Best Practices

Refer to Stability Studies protocols and global inspection outcomes to build best-in-class SOP systems.