What is it? Why is it important?
The study database and its electronic CRF can be developed once:
- An applicable access protected server is available
- A CDMS complying with regulatory requirements has been selected
- A final and approved study protocol is available, including its list of required variables
- Metadata and variable specifications are defined (e.g. by using a codebook)
Once the database is set-up, validation tests are performed to ensure that the eCRF works according to study specifications
Productive or real-life data entry is only possible:
- Upon successful testing of the database with dummy data
- The SP-INV has validated and requested the database to be released for productive data entry (the switch from test phase to productive phase must be approved by the SP-INV and documented)
- Study staff has been trained on data entry procedures and been given access through individualised passwords and logins
Changes to a productive database must be documented. In an electronic database the tracking can be done by the system itself.
Example of database version management
- Version tracking is documented using 3 digits
- The first release is given the number 1.0.0
- Small changes result in adaptations in the 3rd digit (e.g. 1.0.1, 1.0.2, 1.0.3)
- Medium changes result in adaptations in the 2nd digit. (e.g. 1.1.0, 1.2.0, 1.3.0)
- Major changes result in adaptations in the 1st digit (e.g. 1.0.0, 2.0.0, 3.0.0)
What do I need to do?
- Ensure requirements needed for the development of the study database are met (e.g. selection of CDMS, protected server location, qualified staff)
- Implement database according to specifications given in the study protocol (e.g. study design, variable selection, planned study visits)
- Perform functionality tests exclusively with dummy data:
- On the non-released database
- Include staff during test phase as they might more easily identify inconsistencies
- Once functionality tests are successfully completed:
- Release the database in order to allow for productive or real life data entry
- Provide secure logins to staff responsible for study data entry
- Ensure the database is provided with a release date and version number
Database validation tests should be performed diligently until data entry functions as intended without delays or problems. It will save time and resources later on during study conduct.
Planed changes to be implemented in a released database might initially require a substantial amendment (e.g. changes in inclusion/exclusion criteria, changes in study methods or data collection).
A substantial amendment will result in:
- An analysis including an applicable risk assessment in order to ensure that data quality is not jeopardised
- Submission and approval by EC and if applicable RA
- A delay in study conduct
- The potential need for additional resources (e.g. staff, infrastructure, partners)
- An increase in overall study cost
Where can I get help?
Your local CTU↧ can support you with experienced staff regarding this topic
Basel, Clinical Trials Unit, CTU, dkf.unibas.ch
Bellinzona, Clinical Trials Unit, CTU-EOC, www.ctueoc.ch
Bern, Clinical Trials Unit, CTU, www.ctu.unibe.ch
Geneva, Clinical Research Center, CRC, crc.hug.ch
Lausanne, Clinical Research Center, CRC, www.chuv.ch
St. Gallen, Clinical Trials Unit, CTU, www.kssg.ch
Zürich, Clinical Trials Center, CTC, www.ctc.usz.ch
Swissethics – see in particular
- Amendments – Definition of substantial and non-substantial amendments
ICH GCP E6(R2) – see in particular guidelines
- 5.5. Trial Management, data handling, and record-keeping