SCDM Updated CCDM Exam Questions and Answers by leilani

The described process isBlind Verification, also known asdouble data entry with blind verification. In this method, two independent operators enter the same data. The second operator isblindedto the first entry to avoid bias. When discrepancies arise, the system flags them for review, and the second entry (or an adjudicated value) is retained as the correct one.

According toGCDMP (Chapter: Data Entry and Data Tracking), blind double data entry is used primarily inpaper-based studiesto minimize transcription errors and ensure data accuracy.

Single entry (D):Only one operator enters data.

Manual review (B):Involves post-entry checking, not during entry.

Third-party compare (C):Used for reconciling external data sources, not CRF data.

Hence,option A (Blind verification)is the correct and CCDM-defined process.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Entry and Data Tracking, Section 5.1 – Double Data Entry and Verification Methods

ICH E6(R2) GCP, Section 5.5.3 – Data Entry and Verification Controls

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.2 – Data Accuracy and Verification

In theEDC database build process, the first logical specifications that require approval are theelectronic Case Report Form (eCRF) fields.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Database Design and Build), eCRF field specifications define what data elements are collected, their data types, permitted values, field lengths, and any associated metadata. Approval of these specifications forms the foundation for subsequent design components such asedit check programming,query management rules, anddata validation logic.

Edit checks (B)are developed only after fields and structures are finalized.

Metric reports (C)andeCRF guidelines (D)are downstream documentation or tools, not logical specifications required at the build start.

Therefore,option A (eCRF fields)is correct, as their approval marks the first formal milestone in the EDC system development life cycle.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 4.2 – Logical Design and eCRF Field Specifications

ICH E6(R2) GCP, Section 5.5.3 – System Design and Validation Documentation

FDA 21 CFR Part 11 – System Validation and Documentation Controls

Thebest practicefor developingelectronic Case Report Forms (eCRFs)is to involvecross-functional team membersthroughout the design process.

According to theGCDMP (Chapter: CRF Design and Data Collection), eCRFs should be collaboratively developed bydata management, clinical operations, biostatistics, medical, and regulatory teams. Each function provides a unique perspective — data managers focus on data capture and validation; statisticians ensure alignment with analysis requirements; clinicians ensure medical relevance and protocol compliance.

Collaborative development ensures that the eCRFs arefit-for-purpose, capturing all required data accurately, minimizing redundancy, and supporting downstream data analysis.

Options A and B violate good data management practice because sites should not directly access coded terms (to prevent bias), and fields shouldnever auto-populate without explicit source verification. Option D is outdated; while paper CRFs may inform structure,EDC-optimized eCRFsshould leverage system functionality rather than mimic paper.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 4.2 – Collaborative CRF Development

ICH E6 (R2) GCP, Section 5.5.3 – Data Collection and System Validation

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 3.4 – CRF Design Considerations

TheIndividual Case Safety Report (ICSR)is the standard format used globally for the exchange ofSerious Adverse Event (SAE)data between clinical data management systems (EDC) and safety management systems.

According toICH E2B(R3)andGood Clinical Data Management Practices (GCDMP, Chapter: Safety Data Management and SAE Reconciliation), the ICSR provides thedata structure and content standardsfor electronic transmission of safety data, including patient demographics, event details, outcomes, and product information. It ensures interoperability between systems by defining standardized message elements and controlled terminologies.

Other options are not applicable:

A. Medical Document for Regulatory Activities (MDRA)is not a recognized standard.

B. Biomedical Research Domain Model (BRIDG)provides conceptual modeling but not data exchange guidance.

D. SDTMis used for regulatory submission datasets, not real-time SAE exchange.

Thus,option C (Individual Case Safety Report)is correct, as it defines the internationally accepted electronic format for SAE data exchange between safety and clinical databases.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Safety Data Management and SAE Reconciliation, Section 4.3 – SAE Data Exchange and Standards

ICH E2B(R3): Electronic Transmission of Individual Case Safety Reports

FDA Guidance for Industry: Providing Regulatory Submissions in Electronic Format — Postmarketing ICSRs (2014)