Database Lock (DBL) is a critical milestone in the clinical trial lifecycle. A final step of clinical data management, database lock indicates the completion of data collection, cleaning, and validation, readying the data for statistical analysis. This milestone typically occurs 4–6 weeks after Last Patient Last Visit (LPLV). However, if a more challenging timeline (like 1-3 weeks) for DBL is required — due perhaps to expedited regulatory submissions and pressing business or scientific requirements — it creates a high-pressure scenario for all stakeholders.

As gatekeepers of data integrity and quality in clinical trials, the Clinical Data Manager (CDM) plays an important role in ensuring DBL is achieved on time without sacrificing data quality.

Here, I share best practices for achieving accelerated database lock timelines.

Successful database lock depends on early planning

To ensure the database lock is successful, meticulous planning and key stakeholder involvement are vital from the start. Key stakeholders may include Clinical Data Managers (CDM), Clinical Research Associates (CRA), Medical Monitors, Site Staff (Investigators, Coordinators), and Biostatisticians.

Stakeholder involvement

Different domains have different perspectives when looking at data, although we share the same goal. Since the biostatisticians are the ones who process and analyze the data, it is important to involve them early on so that our perspectives are aligned.

Stakeholder expectations

It’s important to align expectations, responsibilities, and timelines with all key stakeholders early in the planning process, ensuring all parties are on the same page. This will help to identify potential risks, evaluate the likelihood and impact of risks to determine their severity, and allow for contingency planning.

Accelerate database lock with continuous data cleaning

Adopting a strategy of continuous data cleaning throughout the trial significantly accelerates DBL. This involves performing regular, structured data review and correction of accumulated trial data.

Locking data in groups

Locking data periodically throughout the trial reduces the volume of data that needs to be finalized at the end. Grouping data for locking, verification, and cleaning must be completed before locking can take place.

Timelines for each group of data locking

Collaborate with stakeholders on how data could be grouped together for locking and agree on realistic timelines for each group, having specific needs of each stakeholder in mind as some tasks are dependent on one another. These timelines could include last data entry, last query sent, last query resolved, investigator sign-off, and lock date.

For example, a grouping strategy includes:

1. Looking at the participant recruitment plan
2. Identifying the number of participants expected to complete the last visit or specific visit in a certain number of months
3. Grouping these data together to form a batch
4. Defining timelines for data cleaning activities before performing a lock on these data

When pre-defining timelines, it is important to take into consideration source data verification (SDV) intervals, and the feasible aspects to minimize data unlocking after the lock. For example, if the locking group contains a substantial volume of data, then the timeline for each activity typically needs to be longer. Aiming for a smaller volume of data when nearer to LPLV is essential to facilitate shorter data cleaning turnaround time.

Identify issues early with clinical data manager oversight

The CDM should closely monitor data and perform trend analyses to detect common data entry discrepancies, lagging query resolutions, unexpectedly high open queries, or pending SDVs, and alert stakeholders to address the issues promptly. This significantly helps to identify issues early and optimize data quality, which minimize costly delays. The CDM should also monitor the unlocking rates of previously locked data. If the unlocking rate is high, consider revising the data locking plan with more realistic timelines.

Delay in Investigator sign-off

Investigator sign-off of Electronic Case Report Forms (eCRFs) is a foundational regulatory requirement serving as documented evidence for the accuracy, completeness, and integrity of the data submitted. It is frequently delayed due to a combination of high investigator workloads, technical complexities, or cumbersome processes. Early discussion on this critical milestone and including the timeline in the Data Locking Plan contribute significantly to expedited DBL.

Avoid bottlenecks caused by data outside electronic data capture

External data that are not part of electronic data capture (EDC) often become the bottleneck in DBL due to complexity and time-intensive processes. Early proactive discussions with vendors regarding timelines for data delivery are critical to avoid jeopardizing an accelerated DBL timeline.

Final takeaways

Adopting continuous data cleaning approach is essential for organizations aiming to shorten the timeline between LPLV and DBL. With strong attention to planning, timelines, and ongoing stakeholders’ engagement, DBL can be achieved on an accelerated timeline.

Share Via