SCDM Certified Clinical Data Manager CCDM Exam Questions

Answer : D

SAE reconciliation must be completed before database lock or closure to ensure all safety data are consistent between the clinical database and the pharmacovigilance (safety) database.

According to the GCDMP (Chapter: Safety Data Handling and Reconciliation), SAE reconciliation involves verifying that all adverse events reported in the clinical trial database are also captured and accurately recorded in the safety system (and vice versa). This is essential to confirm that no SAE is missing, misclassified, or inconsistently dated or coded between the two systems.

Performing this reconciliation before database lock ensures that any discrepancies are corrected, and both databases reflect consistent, verified information for regulatory submission. Conducting this after closure (or only at audit time) would risk data inconsistencies in the final submission datasets.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: SAE Reconciliation, Section 6.1 -- Timing and Procedures for Reconciliation

ICH E2A/E2F -- Clinical Safety Data Management: Definitions and Standards

FDA Guidance for Industry: E2A -- Clinical Safety Data Management: Processing Standards for Safety Reports

Answer : D

The efficacy endpoint of all-cause mortality at one year directly depends on the date of death for each subject, making Option D -- Date of death the required data element.

According to the GCDMP (Chapter: Clinical Trial Protocols and Data Planning) and ICH E3/E9 Guidelines, the primary efficacy analysis must be based on time-to-event data, particularly when the endpoint involves mortality or survival. The date of death allows accurate calculation of time from randomization to event, essential for survival analysis (e.g., Kaplan-Meier curves).

While cause of death (C) may be collected for safety or secondary analyses, all-cause mortality specifically includes any death regardless of cause. Drug levels (A) and coagulation times (B) may serve as pharmacodynamic or exploratory endpoints but do not directly measure mortality.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Planning and Protocol Review, Section 5.4 -- Defining Data Required for Endpoints

ICH E9 -- Statistical Principles for Clinical Trials, Section 2.3 -- Time-to-Event Endpoints

FDA Guidance for Industry: Clinical Trial Endpoints for Drug Development and Approval

Answer : D

The MedDRA (Medical Dictionary for Regulatory Activities) is a standardized medical terminology used for coding and analyzing adverse event (AE) and medical history data in clinical trials. Its hierarchical structure supports aggregation, analysis, and reporting across varying levels of medical specificity.

From most specific to least specific, the hierarchy is as follows:

Lowest Level Term (LLT): The most granular term, often reflecting the verbatim text reported by the investigator.

Preferred Term (PT): The standardized medical concept representing one or more LLTs describing the same condition.

High Level Term (HLT): A grouping of related PTs describing similar medical conditions.

High Level Group Term (HLGT): A broader grouping of related HLTs.

System Organ Class (SOC): The highest level of classification, grouping HLGTs by body system or etiology (e.g., cardiac disorders, infections).

Thus, the correct order --- from most specific to least specific --- is:

LLT PT HLT HLGT SOC, which corresponds to option D.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Medical Coding and Dictionaries, Section 5.2 -- MedDRA Hierarchical Structure

ICH M1 MedDRA Terminology Guide, Version 26.0 -- Hierarchy Overview

ICH E2B(R3) Guidelines -- Clinical Safety Data Management

Answer : A

A protocol compliance edit check is designed to ensure that the data collected adheres to the specific requirements defined in the study protocol, such as visit timing, procedure windows, and eligibility criteria.

The example in option A --- an edit check that triggers when a visit date falls outside the protocol-specified window --- directly verifies compliance with the study design. This type of check supports real-time monitoring of protocol adherence, a critical quality and regulatory requirement under GCDMP and ICH E6(R2).

Other options are examples of general data validation checks, not protocol compliance:

B: Ensures clinical plausibility (data range check).

C: Ensures completeness (missing data check).

D: Ensures format correctness (system validation check).

Thus, option A best represents a protocol compliance edit check, confirming that collected data conform to the visit schedule defined in the protocol.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 5.4 -- Protocol Compliance Edit Checks

ICH E6(R2) GCP, Section 5.1.1 -- Quality Management and Compliance Controls

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.3 -- Edit Check Design and Validation

Answer : B

When designing or configuring data entry screens within an Electronic Data Capture (EDC) system, three critical components are required for each field:

Data Type -- Defines the nature of the data (e.g., text, numeric, date).

Prompt -- The label or question displayed to the user.

Response Format -- Specifies how the user enters or selects data (e.g., free text, drop-down, checkbox).

According to the GCDMP (Chapter: EDC Systems and Database Design), these three attributes form the logical data structure required to build and validate data entry interfaces. They ensure consistency in how information is captured, displayed, and validated during data entry.

While user roles (A) and help text (D) are system-level configurations, not field-level specifications, page numbers (C) relate to printed CRFs rather than digital data screens.

Therefore, option B (Data type, prompt, and response format) correctly identifies the essential information needed to define data entry screens.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: EDC Systems and Database Design, Section 4.3 -- Screen Design Specifications

CDISC CDASH Implementation Guide, Section 3.2 -- Data Field Attributes

ICH E6(R2) GCP, Section 5.5.3 -- Data Capture and Input Standards

Answer : D

The optimal method for collecting frequent patient-reported pain data is through electronic Patient-Reported Outcomes (ePRO) with built-in reminder functionality.

According to the GCDMP (Chapter: Electronic Data Capture Systems), ePRO systems provide a validated, real-time, and user-friendly interface for subjects to record time-sensitive data accurately. The use of automated reminders ensures compliance with protocol-specified data collection times, improving data completeness and accuracy.

Paper diaries (option A) are prone to recall bias and backfilling, while daily site calls (option B) are resource-intensive and introduce human error. IVRS systems (option C) are acceptable but less efficient and user-friendly than modern ePRO applications, which can integrate timestamp validation, compliance monitoring, and real-time alerts.

ePRO systems also comply with FDA 21 CFR Part 11 and ICH E6 (R2) for audit trails, authentication, and validation, making them the preferred solution for repeated PRO data collection.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture (EDC) Systems, Section 6.1 -- Use of ePRO for Repeated Measures

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 5 -- ePRO Compliance and Validation

ICH E6 (R2) GCP, Section 5.5.3 -- Electronic Data Systems and Recordkeeping

Answer : D

RACI is a project management and governance framework used to define roles and responsibilities within a project. Each letter represents a distinct role type:

Responsible (R): The person(s) who perform the work or execute the task.

Accountable (A): The individual ultimately answerable for the task's completion and success (only one per activity).

Consulted (C): Subject matter experts who provide input or guidance before decisions are made.

Informed (I): Individuals kept up to date on progress or outcomes but not directly involved in execution.

The RACI model ensures clarity in ownership and accountability, preventing duplication of effort or responsibility confusion. It is a key component of the GCDMP (Chapter: Project Management in Data Management) for ensuring clear delegation and communication within clinical data management teams.

Hence, option D is correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Project Management in Data Management, Section 5.1 -- Roles, Responsibilities, and RACI Matrices

Project Management Institute (PMI) Framework -- Responsibility Assignment Matrices (RACI)

ICH E6(R2) GCP, Section 5.1.1 -- Defined Roles and Quality Oversight Responsibilities