21 CFR 211.194 makes the laboratory record a reconstructable test chain
For drug CGMP laboratory records within its scope, 21 CFR 211.194 connects the sample, method, raw data, calculations, result, performer, and second-person review. A final result in a LIMS is not the complete record when the source observations and review path cannot be reconstructed.
Editorial figure by Lab Systems Index. Source context: Electronic Code of Federal Regulations — 21 CFR 211.194.
The result is one link in the record
Section 211.194 does not reduce a laboratory record to a pass, fail, or numeric output. It connects the tested material to its sample description and source, the method, observations, calculations, units, result, standard, and people who performed and reviewed the work. That chain lets an authorized reviewer understand what was tested and how the reported result was produced.
A laboratory informatics design should preserve stable links among the sample or lot, receipt and sampling context, specification version, method version, instrument or source data, calculation logic, result, analyst, reviewer, and dates. This is a systems interpretation for evaluation. The regulation and the organization’s approved procedures determine the required record in a specific drug-manufacturing context.
Raw observations need durable identity
The provision expressly includes complete data from tests, including graphs, charts, and spectra from laboratory instrumentation when applicable, properly identified to the material and lot tested. A rendered PDF or copied value can be useful, but it may not preserve the relationship to the original observation, acquisition context, processing, metadata, or later review.
Buyers should test whether a system can trace one reported value back to the retained observation and forward into the comparison with the applicable standard. The demonstration should expose identifiers, versions, units and conversions, calculations, changes, timestamps, responsible people, and export. It should also show how the record handles a repeated or invalidated test without silently replacing the earlier data.
Method changes are separate controlled facts
Section 211.194 requires a statement of the method used and addresses the location of data supporting accuracy and reliability. When an established method is modified, the record must include the modification and the reason, and the modified method must be shown to be at least as accurate and reliable for the material. A method name alone cannot carry that context.
A LIMS or electronic laboratory notebook should distinguish the approved method, local instruction, executed version, authorized modification, justification, supporting qualification or suitability evidence, and the data set to which each applied. Configuration flexibility is not proof that a modified method is scientifically or procedurally acceptable. That conclusion belongs to the authorized quality and laboratory functions.
Second-person review needs more than an electronic sign-off
The regulation calls for review by a second person for accuracy, completeness, and compliance with established standards. An electronic signature can identify a reviewer and time, but the system should also make the reviewed population and state clear. If data, calculations, methods, or specifications change after review, the record needs an explicit path back to accountable review rather than preserving a detached approval icon.
Lab Systems Index uses this provision as a record-chain test, not a universal rule for every laboratory. It does not decide method suitability, specification adequacy, data integrity, validation, product quality, batch disposition, or compliance. A defensible assessment must identify the regulated context, procedures, system configuration, evidence reviewed, and authorized conclusion.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Lab Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.