Data integrity and computerized systems
Why trustworthy data (ALCOA+) is inspection make-or-break, and how computerised systems must be validated and protected by access control, audit trails, and backups.
What a module is not
A module is a reading step, not training and not a qualification. Completing it evidences that you read it — SPEQ says exactly that on the credential — and the knowledge checks are a self-check, not an assessment.
Every decision rests on data; if the data cannot be trusted, neither can the decision.
ALCOA+ across the lifecycle; validated systems with access control, audit trails, and backups.
Data-integrity failures invalidate release decisions and drive enforcement — a market-access risk.
Why data integrity is make-or-break
Every release decision, every trial conclusion, every regulatory approval rests on data. If the data cannot be trusted, none of the decisions built on it can be either. That is why data integrity — the assurance that records are attributable, legible, contemporaneous, original, and accurate, plus complete, consistent, enduring, and available (ALCOA+) — is one of the most heavily inspected areas in all of GxP.
Falsified or unreliable data is not treated as a paperwork issue. It invalidates the decisions that depended on it, drives warning letters and import alerts, and can put a company out of a market. Newcomers should internalise early that the record is not an afterthought to the work — for a regulator, the trustworthy record is the work.
Computerised systems raise the stakes
Most GxP records now live in computerised systems, which brings both power and new risk. A system must be validated — shown to be fit for its intended use — and it must protect the data with access control, an audit trail that captures who changed what and when, and backups so records endure.
The classic failures are avoidable and specific: shared logins that make records un-attributable, audit trails switched off or ignored, and the ability to overwrite original results without a trace. Understanding computerised-system validation and Annex 11 / Part 11 expectations is where many practitioners spend their early technical energy, because so much of modern data integrity is enforced — or lost — in software configuration.
- 1Every regulated decision rests on data; if the data cannot be trusted, neither can the decision.
- 2ALCOA+ is the full test of a trustworthy record across its whole lifecycle.
- 3Data-integrity failures invalidate decisions and drive serious enforcement — they are not paperwork issues.
- 4Computerised systems must be validated and protected by access control, audit trails, and backups.
- 5Classic failures are specific and avoidable: shared logins, disabled audit trails, untraceable overwrites.
Why is data integrity so heavily inspected?
- Because paperwork is preferred
- Because every release and approval rests on trustworthy data ✓
- Because it is easy to check
Which is a classic computerised-system integrity failure?
- A validated system with backups
- A shared login that makes records un-attributable ✓
- An enabled audit trail
What must happen to an original result when a test is re-run?
- It is silently overwritten
- It is preserved with a full audit trail ✓
- It is deleted to avoid confusion
A lab analyst can re-run a test and the software silently overwrites the earlier result, keeping only the passing one.
What data-integrity principle does this violate?
Original results must be preserved and every change must be traceable. Silently discarding the first result destroys the original record and hides a repeated test — a textbook integrity failure. A compliant system keeps all results with a full audit trail, and any re-test is justified and documented.