Database Lock Readiness with Outstanding Issues
A Phase III study is scheduled for database lock in 10 days. The data manager runs a readiness report and finds: 12 open queries (8 for missing lab dates, 4 for inconsistent AE terms), 3 subjects with missing primary endpoint data, 2 SAE reconciliation discrepancies, and 5 protocol deviations not yet coded. The sponsor is pressing for lock to meet a regulatory submission deadline. The data manager knows that the missing primary endpoint data could affect the primary analysis. The CRA suggests locking with the missing data and noting it in the clinical study report.
1. What should the data manager recommend regarding database lock?
Read the worked answer
The data manager should not recommend locking the database with unresolved critical issues. Missing primary endpoint data for 3 subjects is a significant issue that could bias the analysis. The data manager should prioritize resolving the missing data by contacting the sites immediately to determine if the data can be obtained (e.g., from source documents or repeat tests). If the data cannot be obtained, the data manager should document the reason and assess the impact on the analysis. The data manager should also resolve the open queries, particularly those related to safety (AE terms) and the SAE reconciliation discrepancies. Protocol deviations should be coded and reviewed. The data manager should present a risk assessment to the sponsor: locking now risks an incomplete or inaccurate analysis, which could lead to regulatory rejection or post-marketing issues. The data manager should propose a revised timeline with a clear plan to resolve each item, and if the sponsor insists on locking, the data manager should document the decision and the outstanding issues in the database lock checklist and the clinical study report.
2. How should the data manager handle the pressure from the sponsor?
Read the worked answer
The data manager should communicate clearly and factually about the risks. They should provide a detailed list of outstanding issues, their impact, and the estimated time to resolve. The data manager should escalate to the study director or quality assurance if necessary. They should also remind the sponsor of regulatory requirements for data integrity and completeness. If the sponsor decides to lock with outstanding issues, the data manager should ensure that the decision is documented, that the issues are described in the clinical study report, and that a post-lock plan exists for any data that becomes available later. The data manager should also consider whether a partial lock (e.g., locking certain domains) is feasible. Ultimately, the data manager's responsibility is to ensure that the database is fit for purpose and that the analysis is reliable.