Compliance and data integrity

ALCOA+ as technical controls, not a poster

Attributable, legible, contemporaneous, original, accurate — plus complete, consistent, enduring and available. Every one of those should correspond to something configured in the environment, not just something written in a policy.

Laboratory sample records and analysis

The nine attributes, and what each one costs to actually enforce

Making ALCOA+ an explicit policy is the easy half. The harder and more useful half is deciding, for each attribute, which technical control enforces it and how someone would demonstrate that control working to an assessor.

Records must be attributable, legible, contemporaneous, original and accurate, and also complete, consistent, enduring and available. Below is how those translate in practice.

What that means technically

  • Analysts cannot casually delete raw chromatography files — deletion rights are restricted and separated
  • Acquisition timestamps are synchronised against one authoritative time source across every system
  • Audit trails are enabled wherever technically available and required
  • Source data is preserved, not replaced by a processed or reported derivative
  • Modifications remain traceable, with the previous value retained where the system supports it
  • Privileged access is controlled, so administration cannot silently alter results
  • Backups preserve regulated records, and restores are tested and documented
  • Data-flow diagrams exist, so it is clear where a record lives at each stage
A specific example

Why time synchronisation is a data-integrity control

The failure

One system records that a sample was analysed at 14:04. Another records 13:51 for the same event, because their clocks differ. Reconstructing the sequence of events becomes an argument rather than a lookup, and the record's credibility suffers for a reason that has nothing to do with the science.

The control

One authoritative time source, with firewalls, servers, domain controllers, LIMS, CDS, instrument workstations, security systems and network devices all synchronised to it wherever technically feasible. It is inexpensive to implement and awkward to retrofit after an observation.

Common questions

Who reviews audit trails?

QA should establish risk-based audit-trail review procedures — reviewing everything is neither practical nor useful, so the procedure defines what is reviewed, how often and on what risk basis. Our part is making sure the trails exist, are enabled, are protected from alteration and can be retrieved when someone asks.

Do these controls apply to exploratory research data too?

Not automatically, and applying full controls everywhere is a common waste. A documented GxP applicability assessment should come first and determine which systems and which data are in scope.

Our raw data currently sits on instrument PCs. How bad is that?

It is the most common finding we see, and it undermines several ALCOA+ attributes at once: enduring, available and often attributable. Moving raw data to protected central storage with restricted deletion rights is usually the single highest-value change a laboratory can make.

Where our responsibility ends

Pracoda provides technical infrastructure implementation and documentation support. Regulatory interpretation, GxP applicability decisions, audit-trail review procedures, validation approval, data review and final quality release remain with the client's authorized QA, system owner or qualified regulatory and validation specialists.

Review your data integrity controls

Tell us where your raw data currently lives and who can delete it. That answer usually tells us where to start.

  • Reply within one working day
  • Practical controls, not a policy template

We use your details only to reply to you. See our privacy policy.

Need a consultation?

Tell us what you are building.

Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.