Data Integrity Across ELN and LIMS: The ALCOA+ Gap Most Teams Miss at the Integration Boundary

ALCOA+ at the ELN-LIMS boundary: element by element

• Attributable. The LIMS record must carry the identity of the person who created the original ELN entry — not the identity of the service account that performed the transfer. If the LIMS record shows "integration-service" as the author rather than the analyst who ran the experiment, the attribution chain is broken.
• Legible. Numeric values, units, and text fields must arrive in the LIMS in human-readable form. A value that arrives as a raw binary or an unformatted float with incorrect precision is a legibility failure — and a potential accuracy failure if the precision change alters the interpretation.
• Contemporaneous. The LIMS record must carry the timestamp of when the original ELN entry was created — not the timestamp of the transfer. If the ELN result was created at 09:00 and transferred at 23:00 (because the integration runs nightly), the LIMS record must not show 23:00 as the result time.
• Original. If the ELN result was produced by an instrument, the LIMS must reference the original instrument data file — not just the extracted value. Many integrations transfer only the result; the original file stays in the ELN and may not be accessible to LIMS users reviewing the release record.
• Accurate. The quality gate at the integration layer must verify that the transferred value matches the source value exactly — not just that a value arrived. A floating-point precision change, a unit conversion error, or a truncated string are accuracy failures that a simple "record received" delivery confirmation does not catch.
• Complete. Every approved ELN record that should transfer to the LIMS must be confirmed to have arrived. A completeness check — comparing the count of records approved in the ELN over a period against the count received in the LIMS — must run on a schedule and produce an alert when the counts diverge.

The attribution problem: who is the author in LIMS?

The most common ALCOA+ gap at the ELN-LIMS boundary is attribution. The ELN record has a clear author — the analyst who created and approved it. The integration service account performs the transfer. The LIMS record is created by the service account. When an inspector reviews the LIMS record and asks "who entered this result?" the answer is "an automated integration service" — which is not a person. The compliant solution: the LIMS record must carry both the service account identity (for the technical action of creating the record) and the ELN analyst identity (for the scientific action of generating the result). These are different fields with different meanings, and both must be populated and auditable.

The contemporaneous timestamp problem

Contemporaneous documentation means the record is created at the time the activity occurs — not the next day, not at the end of the shift, not when the integration service runs its nightly batch. When an ELN integration runs on a scheduled batch, the LIMS record is created hours after the ELN result was entered. If the LIMS record shows the batch run time as the result timestamp, it is not contemporaneous with the experimental activity. The correct design: the LIMS record carries two timestamps — the ELN creation timestamp (when the analyst entered the result) and the LIMS receipt timestamp (when the integration transferred it). The ELN creation timestamp is the contemporaneous record; the LIMS receipt timestamp is a system record of the data movement. Both must be present, clearly labelled, and tamper-evident.

Building the compliant integration: the technical requirements

• The ELN must expose the analyst identity, original creation timestamp, and original instrument file reference as separate, structured fields in its API — not embedded in a PDF or a narrative text field.
• The integration must carry all three data elements across the boundary without transformation — the analyst identity must not be re-mapped to the service account; the creation timestamp must not be replaced by the transfer timestamp.
• The LIMS must have separate fields for analyst identity (from ELN) and integration service identity (the transfer author), with both populated on every transferred record.
• Quality gates at the integration layer must verify field-level value accuracy — not just delivery confirmation — before the LIMS accepts a record.
• A completeness reconciliation must run on a schedule and alert when records are missing.

Detecting and remediating existing ALCOA+ gaps

If you have an existing ELN-LIMS integration that was not built with these requirements in mind, the remediation sequence is: first, inventory the ALCOA+ gaps by running the element-by-element check against a sample of recently transferred records; second, document the gaps in a CAPA and assess the scope (how many records are affected, what is the regulatory risk of each gap?); third, design the technical remediation (API changes, new fields in LIMS, updated integration logic); fourth, validate the remediated integration under GAMP 5; and fifth, assess whether historical records require a retrospective data review or whether a prospective correction is sufficient. Our data integrity (ALCOA+) team performs these ALCOA+ gap assessments and remediation validations as a service.