An effective documentation framework for chromatography integration-review exception records supports traceability, reproducible decision-making, and defensible records. This article outlines practical record elements and a stepwise workflow that laboratory analysts and reviewers can adopt to capture integration changes and exception reviews in a consistent, auditable manner.
Key record elements for integration-review exceptions
Each exception record should include a concise set of metadata fields to enable rapid review and long-term traceability. Minimum fields include system identifier, sequence or injection ID, chromatogram filename or unique reference, timestamp of the integration change, user ID making the change, and a clear rationale for the action. Capture the original integration result and the revised result, with linked images or file snapshots where possible. Use an explicit field for whether the change was automated by the CDS or manually altered, and note applicable SOP references or deviation identifiers.
Design record templates to reference audit-trail entries rather than replace them. Many guidance documents and industry reviews emphasize preserving native audit-trail records while adding contextual explanatory notes; see the FDA guidance on data integrity for regulatory expectations on audit trail preservation and record completeness.
Workflow for documenting integration changes
Implement a linear workflow: detection, annotation, justification, reviewer assignment, and closure. When an integration anomaly is detected, the analyst logs an exception record immediately and attaches the raw chromatogram plus a snapshot of the original integration. The analyst documents the proposed change, the rationale (for example, baseline correction or peak merge justification), and any calculations used to derive revised quantitative values.
Assign a reviewer with required authority and include a defined review timeline. The reviewer should verify the audit-trail entries in the chromatography data system (CDS), confirm that the proposed change follows SOP criteria, and either approve, request additional information, or reject the change with reasons. For practical guidance on integration interpretation and reviewer considerations, consult industry discussions on integration and interpretation practices available from chromatography subject-matter resources.
Audit trail review and traceability
Audit trails are primary evidence of who changed what and when. Ensure exception records explicitly reference audit-trail IDs or timestamps so reviewers can cross-check entries within the CDS. Where possible, include direct links or exported audit-trail extracts that show the event sequence. Guidance on audit-trail content and review expectations can be found in resources covering CDS audit trails and data integrity practices; for example, see the chromatography data system audit trail guide and detailed articles on integration and interpretation review practices.
When automated integration algorithms are tuned, document algorithm version, parameter sets, and the rationale for retuning in a change-control record that links to affected exception records. This preserves context for future reviewers assessing historical datasets processed under different algorithm settings.
Retention, version control, and training
Define retention periods and storage locations for exception records, raw chromatograms, and audit-trail exports in laboratory documentation procedures. Use version-controlled templates for exception records and enforce mandatory fields to reduce incomplete entries. Maintain a simple naming convention and index to enable quick retrieval by injection ID, date, or project tag.
Provide targeted training for analysts and reviewers that covers template use, acceptable justification language, and how to cross-reference audit trails. Periodic reviews of exception record samples help identify recurring integration issues and opportunities to refine SOP criteria, without making claims about outcomes.
Adopting a consistent documentation structure improves traceability and reviewer efficiency. For practical implementation details, review guidance on CDS audit trails and integration interpretation from established industry sources such as chromatography system audit-trail guidelines and integration-review best practices.
Chromatography Online article on integration and interpretation and CASRAI guide on CDS audit trails provide additional technical context and examples for recordkeeping and review.
Not for human consumption. For laboratory research use only.