SCDM Certified Clinical Data Manager CCDM Exam Questions

Answer : B

In a discrepancy management workflow, ''Received from site and not yet reviewed'' is not a resolution type --- it represents a status, not a final resolution outcome.

According to the GCDMP (Chapter: Data Validation and Cleaning), resolution types describe how a data discrepancy was finalized or addressed, such as:

Resolved with data correction,

Confirmed as correct (no change required),

Self-evident correction applied by data management, or

Unresolvable discrepancies documented.

In contrast, statuses describe the stage of the query (e.g., open, sent, answered, pending review, closed). ''Received from site and not yet reviewed'' indicates an intermediate workflow state where the response awaits validation by data management.

Proper classification of resolution types is essential for performance reporting, audit readiness, and ensuring the traceability of query management actions under ICH E6 (R2) and FDA 21 CFR Part 11.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 5.3 -- Discrepancy Resolution Lifecycle

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Data Handling and Record Management

FDA 21 CFR Part 11 -- Electronic Records; Audit Trails and Discrepancy Tracking Requirements

Answer : A

In paper-based clinical studies, front-end data checks (those performed during data entry) are intentionally kept minimal to ensure that data are entered exactly as recorded on the paper CRF. This principle ensures data integrity by maintaining fidelity between source and electronic records before any cleaning or edit validation occurs.

The GCDMP (Chapter: Data Validation and Cleaning) explains that data entry operators should input values as written, even if they appear incorrect or inconsistent, because the purpose of front-end checks is not to interpret but to capture data faithfully. The back-end edit checks---performed later by data managers---are designed to identify inconsistencies, out-of-range values, or logical errors that require clarification through queries.

This approach separates data capture from data cleaning, minimizing bias and preserving original investigator input. Hence, option A accurately states the rationale for keeping front-end checks minimal in paper-based studies.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 4.2 -- Data Entry, Edit Checks, and Query Process

ICH E6(R2) GCP, Section 5.5.3 -- Data Handling and System Controls

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.1 -- Data Entry and Verification Processes

Answer : A

When derived or calculated variables (like Body Mass Index) are created, it is essential to document the algorithm used and its version to ensure full data traceability and reproducibility.

According to GCDMP (Chapter: Database Design and Derived Data), every derived field must include metadata describing:

The derivation algorithm (e.g., BMI = weight [kg] / height [m])

The version of the algorithm (if updates or revisions occur)

Any associated data sources or transformation rules

This ensures consistent calculation across systems, prevents discrepancies during regulatory submissions, and aligns with FDA and CDISC documentation expectations.

Option B lacks version control, which is critical for traceability. Option C describes audit trail data (not derivation metadata), and option D refers to broader documentation, not specific algorithm traceability.

Hence, option A (Algorithm and algorithm version associated with the calculated value) is the correct and compliant answer.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Derived Data and Algorithms, Section 5.3 -- Documentation and Metadata Requirements

ICH E6(R2) GCP, Section 5.5.3 -- Derived Data and Validation Traceability

FDA Guidance for Industry: Providing Regulatory Submissions in Electronic Format -- Data Definitions (Define.xml)

Answer : D

When merging data from different clinical trials, the use of a common adverse event (AE) dictionary (such as MedDRA or WHO Drug) is essential to ensure consistency and comparability across datasets.

According to the GCDMP (Chapter: Standards and Data Mapping) and CDISC SDTM Implementation Guide, data integration across studies requires standardized terminology for adverse events, medications, and clinical outcomes. Using the same AE dictionary ensures that similar terms are coded consistently, allowing accurate cross-study analysis, pooled summaries, and safety reporting.

A shared software platform (option A) is not necessary if data are mapped to standard formats (e.g., CDISC SDTM). Patient population similarity (option B) affects interpretation but not technical data merging. Study design differences (option C) may influence statistical analysis but not data integration mechanics.

Therefore, Option D -- Use of a common adverse event dictionary -- is the correct and most critical action for consistent multi-study data integration.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Standards and Data Mapping, Section 5.1 -- Use of Standardized Coding Dictionaries

CDISC SDTM Implementation Guide, Section 4.3 -- Controlled Terminology and Cross-Study Integration

ICH E3 and E2B -- Clinical Data Standards and Safety Coding Requirements

Answer : C

When existing SDTM (Study Data Tabulation Model) domains do not cover specific efficacy data, the best practice is to first search for relevant data element standards that may be available through CDISC CDASH (Clinical Data Acquisition Standards Harmonization) or other recognized industry standards.

Per GCDMP (Chapter: Standards and Data Integration), Data Managers must ensure that new CRF elements are consistent with standardized definitions, controlled terminology, and data models to support interoperability, future analysis, and regulatory submission.

If no existing standards exist, only then should the Data Manager collaborate with the study team to define new elements --- but standard searches always come first.

Thus, option C is correct --- search for relevant data element standards ensures alignment with CDISC best practices and regulatory expectations.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Standards and Data Integration, Section 5.1 -- Use of CDISC Standards in CRF Design

CDISC CDASH Implementation Guide, Section 4.1 -- Standardization of Data Collection Fields

FDA Study Data Technical Conformance Guide (SDTCG), Section 2.4 -- Use of Standard and Custom Domains

Answer : C

Providing the central laboratory vendor with a complete subject demographic listing allows ongoing reconciliation between the sponsor's EDC system and the vendor's laboratory database during study conduct.

The GCDMP (Chapter: External Data Transfers and Integration) emphasizes that subject reconciliation ensures that all laboratory data correspond to valid enrolled subjects and visits. Regular reconciliation throughout the study prevents data mismatches, missing results, or misassigned lab reports.

This proactive measure supports timely query resolution and data integrity across systems. Waiting until after database lock (as in option A) would delay corrections and risk inconsistencies. Options B and D address secondary benefits but not the primary purpose---ongoing subject-level reconciliation.

Thus, option C is correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: External Data Transfers, Section 4.4 -- Reconciliation and Vendor Communication

ICH E6(R2) GCP, Section 5.5.3 -- Data Management, Reconciliation, and Integration

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.3 -- External Data Management

Answer : A

The primary purpose of maintaining an audit trail as required under 21 CFR Part 11 is to preserve data integrity. According to the U.S. FDA's regulation on electronic records and signatures, every change to electronic data must be traceable, including information about who made the change, when it was made, and what the change entailed.

The Good Clinical Data Management Practices (GCDMP) outlines that an audit trail provides a permanent, chronological record of all modifications to clinical data. This ensures transparency and allows the reconstruction of the course of data entry and modification. The regulation aims to prevent unauthorized or undocumented data manipulation, thereby maintaining the accuracy, reliability, and validity of electronic records.

The FDA 21 CFR Part 11, Section 11.10(e) explicitly mandates that systems must use secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records. This ensures the data remains trustworthy and defensible in regulatory reviews or inspections.

Therefore, the main reason for requiring an audit trail is to preserve data integrity --- ensuring that all data captured, modified, or transmitted is authentic, accurate, and complete throughout the study lifecycle.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Regulatory Compliance and Data Integrity

FDA 21 CFR Part 11 -- Electronic Records; Electronic Signatures, Section 11.10(e)

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Data Integrity and System Validation