Database Lock, SDTM, and ADaM: The Last Mile of Clinical Data Management

Database lock is not a button. It is soft lock, SAE reconciliation, medical coding freeze, outstanding queries at zero or waived, a study reference listing, a data validation summary, and a lock memo QA will file. Then SDTM, ADaM, define.xml, cSDRG / ADRG, Pinnacle 21, and the statistical analysis plan. A failed lock is a missed filing metaphor even when the calendar has another name.

Where the last mile breaks

• MedDRA / WHODrug upversion mid-study with no impact assessment
• SDTM that cannot be traced to the annotated CRF
• ADaM that does not match the SAP
• Pinnacle 21 issues treated as “just warnings”
• Interim analysis cuts nobody can reproduce
• Unlock without a documented reason and a re-lock plan

We staff CDM + statistical programmer as one vendor motion. The DVS owner sits next to SDTM.IG. We do not let a CRO toss a define.xml over the wall a week before CSR. When the same enterprise runs S/4 for supply and an EDC for the trial, we staff the kit / IRT / expiry seam so CDM is not surprised by a manufacturing hold.

Soft lock is a state. Hard lock is a legal act.

Soft-lock criteria published before LPLV. SAE recon complete. Coding freeze with dictionary version. Queries zero or waived with signatures. SRL and DVS reviewed. Then hard lock: access pulled, memo filed. Unlock is a controlled process, not a favor. SDTM traces to aCRF. ADaM traces to SAP. Pinnacle 21 “warnings” are either justified or fixed. Define.xml is not a gift from the CRO the week of CSR.

We staff CDM + statistical programmer as one motion. Interim cuts are versioned. When S/4 supply and EDC share a kit, we staff that seam so a manufacturing hold does not surprise lock.