Built from the specification, not around it
Screens follow the eCRF/aCRF specification directly, so nothing gets reinterpreted between design and build.
What's included
What goes into the build
- Screen-by-screen build in TrialKit, one field at a time, against the locked eCRF/aCRF specification
- CDASH-aligned field structures so collection maps cleanly to SDTM without rework later
- Conditional logic, skip patterns, and visit/form scheduling configured to match the protocol's visit schedule
- Field-level annotations prepared for edit check and SAS check programming to build against
- A build package handed to UAT with traceability back to every specification line item
Tested before it's trusted
Every screen goes through data entry screen UAT before site users ever see it.
← Back to Data Management
More in Database Build