Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Common Data Elements

  • All relevant common data elements (CDEs) are added to the study

  • CDEs are the most recent version(s)

  • No changes have been made to the original

  • No CDE variable names were used for another eCRF

  • The Informed Consent Form (ICF) contains a SQL consent field

  • ICF contains a Brain-CODE subject ID naming checker

Electronic Case Report Forms (eCRFs) and Patient-Reported Outcomes (ePROs)

  • Consistent formatting

  • Fonts (type, colour, size) are consistent throughout and are legible

  • No spelling errors

  • All units are included (time, temperature, height, etc)

  • Option coding matches paper versions

Validation

  • Limited number of free text fields

  • Numeric fields only allow for integers or double numbers

  • Email address fields have email validation

  • When applicable ontology validation is used

  • Tested all fields with validation checks to ensure that they were functioning

eCRF/ePRO Variables

  • Consistent naming (eCRF has a prefix for all variables)

  • Numbers in variables have leading zeroes

  • No spelling errors

  • Naming is as intuitive as possible

  • Consistent abbreviations

  • Field labels are accurate

  • Fields have accurate descriptions and notes

Branching Logic

  • No errors due to branching logic

  • Branching logic is designed to mimic paper CRF

  • All branching logic has been tested for logic and correctness

Calculated Fields, Range Checks and Automated Queries

  • All calculated fields were manually calculated to ensure accuracy of the equation used

  • When applicable add range checks

    • For example - if the study is for participants older than 18, may have a range validation for age

  • Automated queries were tested for accuracy

    • Ensured no false positives

    • Ensured no false negatives

  • Range checks were tested for accuracy

Required Fields

  • All fields that are required are marked wherever possible

  • Fields are not inappropriately marked as required – causing errors in saving forms

  • Fields are properly designated as required – as to not prevent survey respondents from properly filling out ePROs

Survey Formatting

  • Autonumbering is turned off when ePROs are already labelled with custom numbering

  • If required, proper “STOP” actions are included

  • If required, hidden fields/read-only fields are included and properly formatted

  • Survey is appropriately formatted for its length

    • For example - one page for short ePROs, multiple pages for long ePROs

  • Font of Survey is legible and uses default OBI color scheme

  • Instructions for survey are available

  • Survey administration matches protocol

Study Design

  • Correct Data Access Groups for sites

  • Each eCRF has been assigned to at least one event in the Event Schedule Grid

  • Event grid matches study protocol

  • Arms are appropriately labeled and w/o spelling errors

  • Each arm has at least one event

  • Data entry workflow intuitive and as simple as possible

  • No labels