Clinical trial databases change. Protocol amendments, clarified requirements, new edit checks, revised external-data specifications and operational findings may all require updates during the study.
The objective is not to avoid every change. It is to ensure that each change is justified, assessed, tested, approved and traceable.
Small changes can create wide consequences
A seemingly simple field change may affect data entry, edit checks, exports, mappings, listings, statistical programs, reconciliation and documentation. Change control should therefore consider the full chain rather than only the screen being modified.
- Reason and business need for the change
- Impact on existing and future data
- Impact on forms, checks, interfaces and exports
- Impact on SDTM, ADaM and statistical outputs
- Required regression testing and UAT
- Communication and training needs
- Approvals, implementation date and retained evidence
Database lock is a readiness decision
Database lock should confirm that predefined review and reconciliation activities are complete. It should not be the moment when the team first discovers unresolved study-wide problems.
A lock-readiness process may include:
- Completion of required data entry and source review
- Resolution or documented acceptance of critical queries
- Completion of coding and external-data reconciliation
- Review of protocol deviations and safety discrepancies
- Completion of programmed data checks and listings
- Confirmation of expected transfers and exports
- Documented approvals from responsible functions
- Controlled execution of freeze and lock activities
The decision should be based on defined criteria and visible evidence, not on general confidence that the study is probably ready.
Archiving protects the story of the data
Archiving is more than storing the final database. It preserves the evidence needed to understand how the data were collected, reviewed, changed and finalised.
- Final datasets and data extracts
- Data Management Plan and approved specifications
- CRFs, annotations and database documentation
- Validation, UAT and change-control evidence
- Query, coding and reconciliation records
- Lock approvals and completion records
- Audit trails and relevant review documentation
- Retention responsibilities and accessible formats
Conclusion
Controlled change, visible lock readiness and complete archiving protect both the final analysis and the credibility of the process that produced it.