Data Integrity in QC Laboratories: what to know and why it is fundamental

Introduction

Data Integrity in QC laboratories is not a secondary requirement — it is the foundation of patient safety, product quality, and regulatory compliance.
QC labs generate the most critical datasets — batch release, stability, impurities, purity — and any weakness can lead to FDA Warning Letters, production stoppages and product recalls, as highlighted in major FDA inspection cases.

---

Regulatory context and practical implications

Global authorities (FDA, EMA, PIC/S) converge on one key concept:
What matters is not only the final result, but the full traceability of the data, from raw data to metadata to final reports.

The reference framework is defined by the ALCOA+ principles:

• Attributable – clearly indicating who generated the data
• Legible – readable and not modifiable
• Contemporaneous – recorded in real time
• Original – complete preservation of raw data
• Accurate – correct and verifiable
• Complete, Consistent, Enduring, Available – a dataset that is intact, durable and retrievable for years

Common violations cited by inspectors include:
unjustified reintegrations, missing data, shared accounts, audit trails not reviewed, uncontrolled backups, time-stamp manipulation (“time travelling”), and improper OOS handling.

---

Key risks for Data Integrity in QC

1. Human error and operational pressure

The guide highlights that time pressure and insufficient training are major contributors to deviations:
wrong transcriptions, omissions, late corrections, arbitrary manual reintegration of chromatographic peaks.

2. Outdated or poorly configured computerized systems

Systems without audit trails, without access controls or relying on manual backups expose the company to severe violations.
The FDA has repeatedly cited laboratories where analysts operated with administrator privileges or deleted data without traceability.

3. Undocumented processes

Lack of SOPs for audit trail review, backup, account management or OOS handling is one of the first red flags inspectors identify.

---

Quick list: Benefits of strong Data Integrity

• Dramatic reduction of inspection risk
• Higher scientific reliability of QC data
• Fewer unnecessary OOS/OOT cases
• More efficient data review processes
• Scalable digital processes (LIMS, Empower, ELN)

---

Real-world examples

• Unjustified peak reintegration → FDA findings include cases where analysts adjusted integration to bring OOS results back into specification.
• Deletion of raw data files → over 100 deleted results without formal investigation in one sanctioned case.
• Shared accounts → impossible to attribute responsibility for data actions.

---

Career impact

Strong Data Integrity knowledge enables QC/QA professionals to:

• take on roles such as Data Reviewer, QA Specialist, CSV/DI Specialist
• guide FDA/EMA audits without findings
• become internal reference points for digitalisation initiatives
• accelerate development toward supervisory or QP roles

---

FAQ

1. Is a printed chromatogram considered raw data?
No. It is only a static copy. The original raw data is the complete electronic file required to reconstruct every result.

2. Is Audit Trail Review mandatory?
Yes. FDA and MHRA consider ATR part of formal data review.

3. Can I reintegrate a peak without documenting the justification?
Absolutely not. Every modification must be justified, traceable and approved.

4. Must all data — even incorrect data — be retained?
Yes. Completeness means including failed injections and preliminary data.

5. Are shared accounts allowed?
No. They violate the Attributable principle.

---

Conclusion

Ensuring Data Integrity is not just a regulatory obligation — it is the foundation of a laboratory’s credibility. Explore the full guide on GuideGxP.com.