21 CFR Part 58 separates quality assurance from study conduct

Scope begins with the nonclinical study

Part 58 does not apply to every experiment, laboratory file, or quality workflow. Its scope begins with nonclinical laboratory studies that support or are intended to support identified FDA research or marketing permit applications. The study purpose, sponsor, testing facility, protocol, test system, test and control articles, dates, and submission relationship therefore belong in the system boundary.

A LIMS, ELN, SDMS, CDS, or quality platform can support parts of that record without determining that a study is in scope or compliant. The configured intended use, connected systems, procedures, validation evidence, people, and complete study record remain necessary.

Independence is an authority rule, not a second approval button

The regulation gives the study director overall study responsibility and separately requires an independent quality assurance unit. Modeling both as interchangeable approvers can erase who directed the work, who inspected it, which problem was reported, when management was informed, and what corrective action followed.

A defensible informatics design should preserve role assignment, study status, protocol version, inspection phase, inspector, findings, notification, recommended and taken action, reinspection, final-report review, and signed quality-assurance statement. Access controls and workflow routing support the separation; they do not create independence if organizational responsibility conflicts.

The buyer test challenges both sequence and visibility

Ask a provider to run one study deviation from observation through study-director action and independent quality-assurance review. The record should show who could create, modify, review, acknowledge, and close each item, what earlier information remained visible, and how the final report and quality statement link back to inspection evidence.

Then test a conflict: an individual assigned to study conduct is also offered the quality-assurance action, or a protocol changes after an inspection. The system should enforce the approved role model, preserve the prior record, route the exception, and expose any customer-controlled configuration that could weaken the intended separation.

Software does not establish GLP compliance

Part 58 sets requirements for organizations, studies, personnel, facilities, equipment, operations, protocols, records, reports, and archives. An audit trail, electronic signature, validation package, or quality module does not establish that the complete study and laboratory practice comply. Nor does this article decide a study's regulatory scope.

Lab Systems Index treats the current eCFR as authoritative but unofficial and retains the displayed currency date as part of the evidence record. Laboratories should verify controlling official text, FDA guidance, study facts, procedures, roles, validation, and qualified quality and regulatory judgment.

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.