SCDM Certified Clinical Data Manager CCDM Exam Questions

Answer : D

The most critical consideration is that data cleaning is an iterative process, and completing all necessary steps --- including query generation, site resolution, and second-pass validation --- cannot realistically be accomplished within two weeks after study close.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Data Validation and Cleaning), data cleaning must occur continuously throughout the study, not only at the end. Post-database lock activities typically include running final validation checks, resolving outstanding queries, performing reconciliation (e.g., SAEs, labs, coding), and conducting final quality review.

Even in small studies, query turnaround and response cycles from sites take time --- typically 2--4 weeks per iteration --- making a two-week total cleaning period unrealistic.

Therefore, Option D is correct: it would take more than two weeks to handle second-round (follow-up) queries and confirm final resolutions prior to database lock.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 5.4 -- Ongoing vs. End-of-Study Data Cleaning

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Data Quality and Timeliness

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations -- Data Management and Cleaning

Answer : D

To identify site variability in eligibility screening, the most effective approach is to plot eligibility rate by site. This allows visual detection of differences in how well each site screens subjects according to protocol-defined inclusion and exclusion criteria.

The GCDMP (Chapter: Data Quality Assurance and Metrics) emphasizes the importance of graphical analysis for identifying anomalies and site-level performance variability. By plotting the eligibility rate by site, data managers and clinical operations teams can quickly identify outliers---sites that screen too many or too few eligible subjects---indicating potential training issues, misunderstanding of inclusion/exclusion criteria, or even possible protocol deviations.

While summarizing screening rate (B) provides useful numeric data, it lacks visual comparability. Listing waivers (A) or enrollment counts (C) provide limited insights into eligibility consistency.

Therefore, option D---Plot eligibility rate by site---is the best analytic and visualization practice to assess site variability in screening outcomes.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Quality Assurance and Control, Section 6.1 -- Use of Metrics and Graphical Review for Site Performance

ICH E6(R2) GCP, Section 5.18.4 -- Identification of Systematic or Site-Specific Issues

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

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

This event qualifies as a Serious Adverse Event (SAE) because it resulted in a prolonged hospitalization, even though the episode itself was mild.

According to ICH E2A and GCDMP (Chapter: Safety Data Handling and Reconciliation), an adverse event is considered ''serious'' if it results in any of the following outcomes:

Death,

Life-threatening situation,

Hospitalization or prolongation of existing hospitalization,

Persistent or significant disability/incapacity, or

Congenital anomaly/birth defect.

The severity (mild, moderate, severe) describes intensity, while seriousness describes regulatory significance and medical outcome. Thus, a mild tachycardia episode leading to extended hospital stay meets the regulatory definition of an SAE.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Safety Data Handling and Reconciliation, Section 5.2 -- Definition and Classification of Serious Adverse Events

ICH E2A -- Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, Section II -- Seriousness Criteria

FDA 21 CFR 312.32 -- IND Safety Reporting: Serious Adverse Event Definitions

Answer : A

The main issue with this approach is that no time has been allocated for ongoing maintenance and updates of the Data Management Plan (DMP) throughout the study lifecycle.

According to the GCDMP (Chapter: Data Management Planning and Study Start-up), the DMP is a living document --- it must be continuously maintained and updated as study procedures evolve, particularly after protocol amendments, database modifications, or changes in data validation or reconciliation procedures.

Budgeting only for initial creation (forty hours) over three months ignores the substantial effort required for DMP version control, stakeholder communication, and mid-study updates. These updates are mandatory to maintain compliance with ICH E6 (R2) GCP Section 5.5.3, which requires that all procedural documentation accurately reflect current practices.

Thus, the problem is not the time allocated for creation but the lack of planning for ongoing maintenance.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Plan (DMP), Section 5.3 -- DMP Maintenance and Version Control

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Documentation of Data Handling Procedures

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations -- Section on Documentation Updates

Answer : A

When an audit identifies missing or undocumented training, the most appropriate and compliant response is to identify the root cause of the issue and implement corrective and preventive actions (CAPA) to ensure that similar findings do not recur.

According to Good Clinical Data Management Practices (GCDMP, Chapter: Quality Management and Auditing), effective quality systems require root cause analysis (RCA) for all audit findings. The process involves:

Investigating why the documentation gap occurred (e.g., poor tracking, outdated SOP, or lack of oversight).

Correcting the immediate issue (e.g., ensuring the developers complete or document training).

Updating processes, training systems, or oversight mechanisms to prevent recurrence.

While sending the two developers to training (D) addresses the symptom, it does not resolve the systemic issue identified by the audit. Options B and C are non-compliant and do not address quality system improvement.

Therefore, option A (Identify the root cause and improve the process) is the best and CCDM-compliant response.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Quality Management and Auditing, Section 6.2 -- Corrective and Preventive Actions (CAPA)

ICH E6(R2) GCP, Section 5.1.1 -- Quality Management and Continuous Process Improvement

FDA 21 CFR Part 820.100 -- Corrective and Preventive Action (CAPA) Requirements