Database Lock definition

Database Lock means the database lock of the Study Data after Study Completion.

Database Lock means, with respect to each Combined Therapy Trial, such actions as are taken with approval of the JDC to prevent any modification to the database of Study Data generated in the course of such Combined Therapy Trial.

Database Lock means when the clinical trial database for the [***] is locked to further modifications (including additions, deletions or alterations of data).

Examples of Database Lock in a sentence

• In that case, hard copies with original signatures may be sent to: Shannon Sprague, B–WET Program Manager, NOAA Chesapeake Bay Office, 410 Severn Avenue, Suite 107A, Annapolis, MD 21403Information Contacts: Please visit theB–WET Web site for further information at: http://noaa.chesapeakebay.net/ educationgrants.aspx or contact the NOAA Chesapeake Bay Office, 410 Severn Avenue, Suite 107A, Annapolis, MD 21403, or by phone at 410–267– 5660.

• The projected timeline for this Project is as follows: PROJECT TIMELINE Commencement of Work (Start Date) **** Protocol Finalised **** First Patient Enrolled **** Last Patient Enrolled **** Last Patient End of Treatment **** Last CRF to Data Management **** Database Lock **** Statistical Analysis **** Study End **** Study Completion — End Omnicare Involvement **** A detailed timeline and milestones will be developed based on the different assumptions of how the project is conducted.

• Corvus shall provide the Final Study Report to Genentech within [***] after Database Lock.

• Database services and support will be delivered through a contract signed by Sealed Envelope and UCL.PRIMENT SOPs Validating Sealed Envelope Systems and Change Control for Sealed Envelope Systems will be followed to set up and manage changes to the trial database.At the end of the trial, prior to analysis, PRIMENT SOP Database Lock, Unlock and Closure will be followed.

• Any changes from the analyses planned in SAP will be detailed in the Clinical Study Report (CSR).Prior to Database Lock, a Final Review of Data and TLFs Meeting will be held to allow a review of the clinical trial data and to verify the data that will be used for analysis set classification.

More Definitions of Database Lock

Database Lock means, with respect to each Collaboration Study, such actions as are taken with approval of the JDC to prevent any modification to the database of Study Data generated in the course of such Collaboration Study.

Database Lock means the locking of a Study database maintained by Sponsor that includes the data from the Case Report Forms, whereby no further changes are allowed thereafter.

Database Lock means that all Clinical Data has been received and processed, all queries have been resolved, all external data (e.g. lab results) have been integrated into the main database for the Study, the completion of the final quality audit ensuring that all Clinical Data is present, correspondent and accurate and that the edit access of the database has been removed.

Database Lock means after data collection has been completed in a clinical trial, including follow up of all participants as described in the clinical trial protocol, data quality and validation exercises are undertaken. After this, the database is “locked” so no further changes can be made to clinical trial data and the data are then able to be extracted from the database for analysis.

Database Lock means, with respect to any Clinical Trial, the date on which the database(s) containing the applicable clinical trial data is determined to be complete and locked in order to permit the analysis of the primary and secondary endpoints of such Clinical Trial. ActiveUS 144208420v.18

Database Lock means, with respect to the Next Trial, the stage in which the clinical trial database is ready for code opening and analysis of the trial results, as described in Schedule 1.64(a).

Database Lock means that all Sub-Study data has been received and processed, all queries have been resolved, all external data (for example, lab results) have been integrated into the main Sub-Study database, the completion of the final quality audit ensuring that all Sub-Study data is present, correspondent and accurate and that the edit access of the Sub-Study database has been removed.