New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Pharma data integrity for environmental monitoring: audit trails, timestamps and who changed what

An inspector asks who changed a value, when and why. ALCOA+, audit trails and clock accuracy, read from the WHO guideline, Annex 11 and 21 CFR Part 11.

Pharma data integrity means GMP records stay attributable, legible, contemporaneous, original and accurate, and also complete, consistent, enduring and available: the ALCOA+ principles of the WHO data integrity guideline. For environmental monitoring, that comes down to three questions: who did it, when it happened, and whether the original value survived every change.

A developer asks how to stamp a reading with the right time. A GMP inspector asks who changed an alarm limit, when, and why. In pharma environmental monitoring, both questions are about the same record.

What is ALCOA in data integrity?

ALCOA stands for attributable, legible, contemporaneous, original and accurate. The WHO guideline on data integrity (TRS 1033, Annex 4) lists complete, consistent, enduring and available alongside them, a set commonly referred to as ALCOA+. For sensor data, I look at four of them first.

PrincipleWhat it asks of a monitoring record
AttributableTraceable to an individual and, where relevant, the measurement system: the user who acted and the sensor that measured
ContemporaneousRecorded when generated; electronic data automatically date- and time-stamped
OriginalThe first capture of the data stays available; under 21 CFR 11.10(e), record changes must not obscure previously recorded information
Enduring and availableKept and retrievable throughout the data life cycle, for the defined retention period

What should an audit trail record?

An audit trail records who did what, when and why. The WHO guideline says audit trails should reflect users, dates, times, original data and results, changes and reasons for changes (when required), and the enabling and disabling of the audit trail itself.

21 CFR 11.10(e) asks for secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify or delete electronic records, kept at least as long as the records. The January 2011 revision of EU GMP Annex 11 says consideration should be given, based on a risk assessment, to a system-generated record of all GMP-relevant changes and deletions. It asks for a documented reason for each change or deletion of GMP-relevant data, and for audit trails to be regularly reviewed.

For a cleanroom or a warehouse, I would check that alarm limit changes, calibration offsets, alarm acknowledgements, user and role changes and any change to audit settings all land in the trail. Who may make those changes is a separate decision, covered in least privilege in OT.

Hermetry connects field devices to live dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Its audit log records sensitive actions such as sign-ins, member and role changes, credential changes, high-impact commands, deletions and setting changes, and the application never edits its rows. Each row is hash-chained to the one before it, so any change or deletion of a kept row breaks the chain, and a member with the Admin role can check the chain over the API. With the default retention of 0 days, rows are kept forever.

Why do accurate timestamps matter for GMP records?

A contemporaneous record needs a correct clock. The WHO guideline asks for time accuracy of the system that generates the record, verified time zone and time synchronisation, and restricted ability to change dates, time zones and times. Annex 11 asks that systems record the identity of operators entering, changing, confirming or deleting data, including date and time.

I store every timestamp in UTC and record which clock produced it: the device’s own clock, or the time the server received the reading. A gateway that loses time sync after a power cut can otherwise place a temperature excursion in the wrong hour. For a full cleanroom design, see cleanroom differential pressure, temperature and humidity monitoring.

Frequently asked questions

How often should audit trails be reviewed?

The WHO guideline says the routine review of GxP data should include audit trails, and that the review frequency should take into account the criticality of the system and the category of audit trail information, such as batch-specific, administrative or system activity. Evidence of the review should be kept. Annex 11 asks for audit trails to be regularly reviewed.

Can an audit trail be switched off?

The WHO guideline says GxP-relevant audit trails should be enabled when the software is installed and remain enabled at all times, with evidence of enabling and periodic checks. Where an audit trail can be disabled, that action should itself appear in the audit trail.

Is an exported spreadsheet a valid copy of the original record?

Only if it is a true copy. The WHO guideline defines a certified true copy as one verified, by a dated signature or a validated process, to hold the same information as the original, including the data that describe its context, content and structure. A spreadsheet that drops metadata or allows silent edits does not meet that.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.