ALCOA+ in practice: data integrity checks every EDC build should pass

ALCOA+ is easy to recite and harder to evidence. Here is how each principle maps to concrete EDC configuration, audit-trail behaviour and validation tests.

Inspectors rarely ask you to define ALCOA+. They ask you to show it: who entered this value, when, what it was before, and why it changed. A well-configured EDC answers those questions without a spreadsheet on the side.

The principles, mapped to the system

PrincipleWhat to verify in the EDC
AttributableUnique user accounts, no shared logins, role-based access; every entry carries the user ID.
LegibleValues readable for the record's full retention period, including exports and archives.
ContemporaneousServer-side timestamps (UTC with site offset), not client clocks.
OriginalSource documents or certified copies identified; eSource fields flagged.
AccurateEdit checks, range checks and query workflow validated against the DVS.
CompleteAudit trail retains every version; deletions are logical, never physical.
ConsistentSame date/time conventions and sequence across forms and exports.
EnduringBackups, restore tests and archive formats (e.g. PDF/A, XML) defined.
AvailableRecords retrievable for monitoring, audit and inspection within agreed timelines.

Audit trail: the 21 CFR Part 11 expectation

Part 11 §11.10(e) asks for secure, computer-generated, time-stamped audit trails that independently record the date and time of entries and actions that create, modify or delete electronic records, without obscuring previously recorded information. In EDC terms, confirm that:

  • Old and new values, user, timestamp and reason for change are captured for every edit.
  • Users cannot edit or disable the audit trail, including administrators.
  • The audit trail is exportable in a human-readable form for inspection.

Electronic signatures

Signature manifestations should show the printed name, date and time, and the meaning of the signature (for example, “Investigator approval”), and each signature must be linked to its record so it cannot be copied to another (§11.50 and §11.70).

Validation tests worth adding

  1. Edit a locked form as each role and confirm the expected denial is audited.
  2. Change a value twice and verify both prior values remain visible.
  3. Change the client clock and confirm stored timestamps do not move.
  4. Restore last night's backup to a sandbox and compare record counts and hashes.
Found this useful?Share it with your team or network.

Need help applying this to your study?

Our statisticians, programmers and quality specialists can review it with you.