# FDA doesn't ask if the batch record was accurate. It asks if you can prove it was created when it claims.

ALCOA+ requires contemporaneous records. 21 CFR Part 11 requires tamper-evident audit trails. MHRA requires data integrity across the product lifecycle. Every standard applies the same test: can the record prove when it was created? immut generates a SHA-256 hash of each GxP record in your browser and anchors it to the public XRP Ledger. No file leaves your infrastructure, and the proof is independently verifiable by any inspector.

## What does ALCOA+ require, and which criterion is hardest?

ALCOA+ stands for Attributable, Legible, Contemporaneous, Original, Accurate, plus Complete, Consistent, Enduring, Available. The "C" (Contemporaneous) is the one current electronic systems cannot prove: records must be created at the time the activity occurs, and FDA and MHRA inspectors treat records that cannot prove their creation date as failing the standard. immut solves the contemporaneity criterion by anchoring an independent, tamper-evident timestamp at the moment of record creation.

## What does each regulation require for data integrity?

Eight instruments across FDA, MHRA, EMA and ICH, all requiring contemporaneous, independently verifiable records.

- **FDA 21 CFR Part 11.10(b), audit trail.** Computer-generated, time-stamped audit trails must independently record the date and time of operator entries and actions. The word "independently" carries the entire evidential weight: a timestamp generated and stored by the same system that stores the record is self-attesting, and FDA investigators treat self-attesting audit trails as insufficient during data integrity inspections.
- **FDA 21 CFR Part 11.10(d), tamper-evident records.** Controls must detect invalid or altered records. An electronic record whose timestamp can be altered without detection does not satisfy Part 11. This control is routinely cited in Warning Letters where systems lacked controls to prevent or detect unauthorised deletion or modification.
- **FDA 21 CFR Part 11.10(e), sequenced audit trail.** Secure, computer-generated time stamps in an unbroken chronological sequence. Gaps in an audit trail are a standard warning letter trigger; if the trail cannot be shown to be complete, it is presumptively incomplete.
- **ALCOA+, Contemporaneous.** MHRA guidance is explicit: "contemporaneous" means at the time of performance, not reconstructed later from memory, laboratory notebooks, or instrument printouts. A batch record completed at the end of a shift rather than at the point of each step may fail the standard even if the underlying manufacturing was compliant.
- **EU GMP Annex 11, Clause 9.** Audit trails must record creation, modification and deletion of GMP-relevant data, including old and new values plus the reason for change. EMA inspectors require the integrity of the trail itself to be independently demonstrable, not merely asserted.
- **MHRA GxP Data Integrity Guidance (2021), original data.** Original data is the first-captured data at the time of observation. Data transferred between formats or recreated after system failure must be demonstrably equivalent to the original; where equivalence cannot be demonstrated through an independent, tamper-evident record, the data's integrity is in doubt.
- **FDA Data Integrity and Compliance Guidance (2018), static vs dynamic records.** Static formats such as PDFs must include an audit trail showing original data, changes, and who made them. A static record whose trail is stored within a modifiable system does not satisfy the guidance.
- **ICH Q10, Pharmaceutical Quality System.** Knowledge must be managed throughout the product lifecycle, including experimental data, the evolution of process understanding, and decisions at each stage. The temporal sequence of knowledge creation is part of the regulated record.

## What does FDA enforcement look like when records cannot be verified?

In every case below, the products may or may not have been unsafe. The records could not be independently verified, and the consequence followed the documentation gap.

- **Ranbaxy Laboratories, $500M (US FDA / DOJ, GMP, 2013).** FDA inspections found broken documentation trails: incomplete batch records, inaccurate cleaning records, inadequate failure investigations. The agency could not verify whether manufacturing had been conducted to Good Manufacturing Practice. The consent decree covered all 30 plus of Ranbaxy's manufacturing facilities. The core finding was not that products were unsafe; it was that records could not independently verify that GMP had been followed.
- **Zydus Pharmaceuticals, Warning Letter plus Import Alert (FDA, GMP, 2023).** Audit trails had been disabled on manufacturing systems; data had been deleted and re-entered. FDA's finding: "Your firm failed to exercise appropriate controls over computerised systems to assure that only authorised personnel institute changes."
- **Sun Pharmaceutical, multiple Warning Letters (FDA / MHRA, GMP).** Electronic data was being manipulated after initial entry: analysts retested samples and deleted failing results, recording only passing results in the official batch record. The problem was not that tests failed; it was that the records could not be trusted to reflect reality at the time of testing.
- **Bharat Serums, Import Alert (FDA Warning Letter, GMP, 2022).** Audit trails disabled; batch records could not be corroborated against raw instrument data because raw data had been altered. FDA's observation: "You have not demonstrated that your data management practices ensure complete, consistent, and accurate data." The ALCOA+ standard was cited explicitly.

## How does immut work in a GxP environment?

ALCOA+ compliant, and no file leaves your infrastructure. immut generates the hash in your browser and anchors it to the public XRP Ledger; the original document stays where it is.

1. **Hash generated on your device.** The SHA-256 hash of your batch record, lab notebook, or audit log is computed locally. No data leaves your infrastructure.
2. **Anchored to the XRP Ledger.** The hash is recorded on the public ledger with a cryptographic timestamp. The ledger is immutable: no party, including immut, can alter or delete the entry.
3. **ALCOA+ contemporaneous record.** immut issues a certificate with the hash, XRPL transaction ID, ledger sequence number, and UTC timestamp. The certificate satisfies the "C" in ALCOA+.
4. **Verifiable by any inspector.** An FDA inspector, MHRA auditor, or EMA assessor can verify the record independently, without trusting immut, your systems, or your representations.

## The question to ask yourself

If an FDA inspector asked you to demonstrate that a batch record was created at the time of manufacture, not reconstructed afterward, could you?

## Links

- Live page: https://www.immut.io/evidence/gxp
- Developer docs: https://www.immut.io/docs
- For AI agents: https://www.immut.io/ai-agents