FDA says a printed chromatogram is not the complete electronic raw-data record

Define the source record before designing the export

FDA's example begins with computerized chromatography systems and the electronic records they create. The analytical result cannot be reduced to the plotted trace or reported value when the sequence, acquisition and processing methods, integration, metadata, and audit trail participate in how that result was produced and reviewed. Teams should identify those linked objects for each instrument and workflow before deciding what an archive or migration must preserve.

A defensible inventory names the instrument, software and version, data system, method, sequence, sample and preparation identity, acquired data, processing events, results, audit trail, user and role, review, approval, exception, retention rule, and authoritative storage location. It should also identify which objects are dynamic or relational and which export formats preserve or lose those relationships.

Separate readable output from an exact and complete copy

A printed chromatogram may be human-readable and useful in a review package. FDA's guidance nevertheless says it generally is not the full electronic raw-data record. Readability answers whether a person can inspect the presented content; completeness answers whether the retained copy contains the source data and associated context needed to reconstruct, evaluate, and audit the analysis.

Export testing should therefore compare more than page appearance. Teams need to verify data values, units, timestamps, identities, sequence order, methods and versions, processing and integration history, audit trail, signatures or approvals, attachments, links, and the ability to retrieve the record for the required period. An export that produces a clean PDF while dropping relational or event data should be recorded as a limited report, not a complete migration.

Keep custody and review attached through system changes

Laboratories often move records from instruments into chromatography data systems, scientific data platforms, SDMS repositories, LIMS references, document archives, or long-term storage. Each handoff can change format, identifiers, metadata, searchability, permissions, and review behavior. The receiving system should not inherit record authority merely because it stores a file from the source.

Migration and retirement evidence should connect source inventory, extraction, transformation, destination, validation or assurance activity, reconciliation, exceptions, approvals, access controls, retention, retrieval testing, and decommissioning. Sampling may support an approved method, but the population, selection logic, acceptance criteria, deviations, and residual gaps must remain visible. A vendor export claim does not establish buyer-specific completeness.

Apply the rule only within its regulatory and factual scope

The FDA Q&A addresses records subject to drug CGMP predicate rules and gives a chromatography example. It should not be presented as a universal answer for every research, clinical, environmental, forensic, food, or industrial laboratory. Other laws, standards, accreditation rules, contracts, methods, and institutional policies may define different records and retention duties.

Lab Systems Index treats the current FDA page as primary evidence for the agency's stated CGMP electronic-record and chromatogram boundary. It does not establish the record population, completeness, compliance, validation, data integrity, method suitability, or scientific validity of any laboratory or product. Those conclusions require the applicable authority, exact configured workflow, retained records, qualified review, and documented assurance.

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.