EDC configuration for CNS assessments is the process of building scale-specific scoring logic, administration order enforcement, alternate form rotation, rater certification gating, and assessment-level deviation capture into an electronic data capture system before the first participant is enrolled – distinct from generic CRF construction, which applies completeness and range rules without accounting for the instrument-specific requirements of validated cognitive and motor scales.

Central review of ADAS-Cog 13, ADCS-ADL, CDR, and MMSE administrations across multiple Alzheimer’s disease trials found deviations from standard guidelines in 40 to 60% of administrations, according to Cogstate’s published rater performance analysis. The EDC build either catches those errors at entry or it does not. If the validation logic, administration order enforcement, scoring rules, and alternate form rotation are not configured correctly before the first participant is enrolled, the data quality consequence is not recoverable at lock.

Standard EDC builds apply completeness and range checks to form fields. CNS-specific EDC builds must enforce the validated administration sequence of each scale, lock the correct instrument version, auto-calculate derived scores from subtest entries using the version-specific algorithm, assign and enforce alternate form rotation by participant and visit, and capture assessment-level deviations with sufficient specificity to support SAP inclusion/exclusion decisions.

The ADAS-Cog uses alternate word lists, recognition lists, and number cancellation forms across successive visits to reduce practice effects. If a participant receives the same word list at Visit 2 and Visit 6, the repeat exposure inflates their score. A CNS-specific EDC build assigns alternate forms by participant and visit at enrollment and blocks reuse of a prior form – a function a generic form-based EDC cannot perform without custom configuration.

The ADAS-Cog uses alternate word lists, recognition lists, and number cancellation forms across successive visits to reduce practice effects. If a participant receives the same word list at Visit 2 and Visit 6, the repeat exposure inflates their score. A CNS-specific EDC build assigns alternate forms by participant and visit at enrollment and blocks reuse of a prior form, a function a generic form-based EDC cannot perform without custom configuration.

A version mismatch, such as an EDC configured for ADAS-Cog 11 while sites administer ADAS-Cog 13, produces a scoring inconsistency that cannot be fully resolved after the fact. The 11-item total score maximum is 70; the 13-item maximum is 85. Sites entering 13-item raw scores into an 11-item build produce a miscalculated derived total with an audit trail that does not match the instrument actually administered, potentially triggering partial data exclusion from the primary analysis.

“The assumption going into most CNS builds is that standard range checks and completeness rules are sufficient. Where that breaks down is alternate form rotation. On one ADAS-Cog program, we discovered mid-study that the EDC had no logic to block reuse of prior word lists; sites were selecting forms manually each visit. By the time it surfaced through a data review, roughly 30% of enrolled participants had received a repeated list at a follow-up visit, which triggered a deviation classification discussion that touched the primary endpoint dataset and delayed lock by six weeks.”

– Kyle Hanson, Director of Clinical Operations at Sitero

CNS EDC configuration should condition form access on current rater certification status: when a rater attempts to open an assessment, the system verifies their certification is current against protocol-defined requirements before granting access. Uncertified or lapsed raters cannot enter data. This creates a system-level enforcement layer that does not depend on CRA observation or site self-reporting to catch certification gaps.

Assessment-level deviation capture records deviations at the scale and subtest level, naming which rater, which subtest, which administration condition was out of compliance, and links that deviation record to the specific endpoint data it may affect. Generic EDC builds capture deviations at the visit level with a general description. Without assessment-level granularity, the SAP cannot determine whether a deviated assessment should be included or excluded from the primary analysis without a manual data review.

1. Is the scale version, ADAS-Cog 11, 12, or 13; MDS-UPDRS or legacy UPDRS; CDR Global or CDR-SB, locked in the database at study startup, and does the scoring algorithm in the EDC match that exact version?
2. Does the EDC calculate derived scores from raw subtest entries, or does it require the site to enter a pre-calculated total?
3. For scales with alternate forms, does the database assign and enforce form rotation by participant and visit, and does it block re-use of a prior form at subsequent visits?
4. Is the administration order of each multi-step scale enforced in form logic, or can site coordinators complete fields out of sequence?
5. Are assessment-level protocol deviations captured with sufficient specificity, scale name, subtest, rater, timing, to support inclusion/exclusion determinations in the SAP?
6. For programs with multiple scales in a single visit battery, does the EDC enforce the inter-scale administration sequence the protocol requires?
7. Does the EDC enforce rater certification status as a gate condition before a scale form can be opened, and how does it handle a rater whose certification lapses mid-study?
8. How does the build handle the ADAS-Cog word recall delay interval – is the required time gap between immediate recall and delayed recall enforced in the visit schedule?
9. For the C-SSRS or other safety-flagged scales, are specific response thresholds configured to trigger immediate alerts to the medical monitor, independent of the standard query workflow?
10. What is the change control process for a protocol amendment that changes scale version, administration sequence, or scoring methodology mid-study – and how are existing data and the new configuration reconciled in the audit trail?

Q1: What is EDC configuration for CNS assessments?

EDC configuration for CNS assessments is the process of building instrument-specific scoring logic, administration order enforcement, alternate form rotation, rater certification gating, and assessment-level deviation capture into an electronic data capture system for a clinical trial using validated cognitive or motor scales. It is distinct from generic CRF construction because CNS scales like the ADAS-Cog, MDS-UPDRS, PANSS, and MMSE require version-locked scoring algorithms, validated administration sequences, and compliance enforcement that standard form-based EDC builds do not provide. Incorrect configuration is not recoverable at database lock.

Q2: Why does the ADAS-Cog require more complex EDC configuration than most clinical scales?

The ADAS-Cog combines multiple assessment modalities, each with distinct administration instructions, scoring criteria, and a derived total score that changes depending on which version is in use. More than 30 modified versions of the ADAS-Cog exist across the literature, so a global Phase 3 program must lock its version precisely. The limited number of alternate word list forms requires rotation management across visits, and the highest-error subitems, Number Cancellation (23.38% error rate) and Constructional Praxis (20.48%) per Cogstate’s published analysis, require administration-specific validation logic that a standard entry field cannot supply.

Q3: What is the consequence of a scale version mismatch in a Phase 3 CNS EDC build?

A scale version mismatch produces a scoring inconsistency that cannot be fully resolved after the fact. The ADAS-Cog 11-item total score maximum is 70; the 13-item maximum is 85. If a site enters raw scores for 13 items into an EDC configured for 11 items, the derived total is miscalculated and the audit trail does not match the instrument actually administered. Depending on the magnitude of the mismatch across sites and visits, this can result in partial data exclusion from the primary analysis, protocol deviation classifications, and a regulatory question at submission about whether the primary endpoint dataset is consistent.

Q4: How does EDC configuration interact with rater training oversight in a CNS program?

The EDC is the enforcement point for the rater program’s certification requirements. If the EDC does not condition form access on current certification status, a site can have a lapsed or uncertified rater complete a primary endpoint assessment without any system-level record of the compliance gap. A CNS EDC build that integrates rater certification status provides a real-time gate: uncertified raters cannot open the scale form. This eliminates the documentation gap between a lapsed certification and the data record it would otherwise affect, without relying on CRA observation to catch the compliance failure.

Q5: What should a CNS EDC build include that a standard clinical trial EDC build does not?

A CNS EDC build should include: version-locked scale configurations with auto-calculated derived scores using the version-specific algorithm; administration order enforcement that prevents fields from being completed out of the validated sequence; alternate form rotation assigned by participant and visit at enrollment with system-level blocking of form reuse; assessment-level deviation capture linking each deviation to the specific scale, subtest, rater, and endpoint data affected; inter-scale sequencing enforcement across multi-scale visit batteries; and rater certification gating that conditions form access on current certification status. None of these are standard features of a generic EDC build.

Sitero has supported more than 230 CNS, neurology, psychiatry, and behavioral health studies across 67 countries. The EDC configuration decisions made before a CNS study goes into UAT shape the data quality, query volume, and inspection readiness of every assessment visit that follows. For programs running ADAS-Cog, UPDRS, PANSS, EDSS, or other complex CNS scale batteries, that configuration work needs to happen at protocol finalization, not after first patient in.

Talk to a neurology trial expert to discuss your protocol, or use the button below to learn more about Sitero’s Mentor EDC capabilities:

1. CNS/Neurology Program Operational Data. Internal dataset.
2. Hanson K. Director of Clinical Operations, Sitero. Expert interview conducted for this article. September 2026.
3. Primwhere B. Senior Director, Product Management and Strategy, Sitero. Expert interview conducted for this article. September 2026.
4. Cogstate. (n.d.). Adas-Cog, ADCS-adl, CDR, and MMSE rater performance analysis data. Cogstate. https://www.cogstate.com/blog/adas-cog-adcs-adl-cdr-and-mmse/
5. Sink, K., & Wacker, S. (n.d.). The alzheimer’s disease assessment scale cognitive subscale (Adas-cog): Advantages, challenges, and considerations. Cogstate. https://www.cogstate.com/blog/the-adas-cog-advantages-challenges-and-considerations/
6. Montano, O., Pestronk, M., Johnson, D., Muthanna, M., Redkar-Brown, D., Russo, R., Eade, D. & Zozus, M. N., (2021) “Electronic Data Capture-Study Conduct, Maintenance and Closeout”, Journal of the Society for Clinical Data Management 4. doi: https://doi.org/10.47912/jscdm.31