Consistency across a portfolio
Sites and monitors who've worked a sponsor's other studies see familiar forms, reducing training time and entry errors.
What's included
What adaptation covers
- Field-by-field comparison of the sponsor's standard template against this protocol's visit schedule and assessments
- Retirement of fields the current protocol doesn't require, so testers and site users aren't presented with dead form logic
- Addition of protocol-specific fields in a style and layout consistent with the sponsor's existing library
- Confirmation that inherited controlled terminology and coding conventions still match this study's CDASH-aligned structures
- A change log documenting every deviation from the standard template, for the sponsor's own portfolio records
Adapted, not just copied
Every inherited field is checked against the current protocol during eCRF/aCRF specification before it's carried forward.
← Back to Data Management
More in Database Build