SCDM Certified Clinical Data Manager CCDM Exam Questions

Answer : C

The Scope of Work (SOW) is a contractual document that outlines the specific deliverables, responsibilities, timelines, and budgetary details for a given project between the sponsor and the contract research organization (CRO).

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Project Management and Communication), the SOW defines what work will be performed, how many resources are allocated, and the expected deliverables. This includes detailed information such as:

The number of database builds or migrations,

Timelines for deliverables (e.g., database lock),

Responsibility distribution between sponsor and CRO, and

Budget parameters for defined activities.

Therefore, if a Data Manager needs to determine how many database migrations are budgeted for a project, the SOW is the correct document to reference.

Information such as PK sample scheduling (option A), site monitoring dates (option B), or staff contact details (option D) would be found in operational plans or contact lists, not in the SOW.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Project Management and Communication, Section 6.2 -- Scope of Work Definition and Deliverables

ICH E6 (R2) GCP, Section 5.5.3 -- Documentation and Responsibilities for Data Management Tasks

FDA Guidance for Industry: Oversight of Clinical Investigations -- Sponsor and CRO Agreements

Answer : D

A self-evident correction (SEC) refers to a data correction that is obvious, logical, and unambiguous --- such as correcting an impossible date (e.g., 31-APR-2024) or standardizing a known abbreviation (e.g., ''BP'' to ''Blood Pressure''). According to the Good Clinical Data Management Practices (GCDMP), SECs can be applied by data management staff following pre-approved conventions defined in the Data Management Plan (DMP).

The DMP should explicitly describe the criteria for SECs, including the types of errors eligible for this correction method, the required documentation, and the communication procedure to inform the investigative site. The process must maintain audit trail transparency and ensure that all changes are traceable and justified.

Options A and B suggest unauthorized or informal change procedures, which violate audit and compliance standards. Option C is too restrictive, as it prevents the efficient correction of non-clinical transcription or formatting errors.

Therefore, option D is correct: ''Self-evident changes may be made per the listed conventions and documented to the investigative site.'' This approach aligns with CCDM expectations for balancing efficiency, accuracy, and regulatory compliance.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 6.2 -- Self-Evident Corrections

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

Answer : D

When combining data from two datasets where one uses numeric codes (1 = Male, 2 = Female) and another uses text codes (M, F), each unique value in one dataset corresponds exactly to one unique value in the other.

This relationship is a one-to-one mapping, where each element in one dataset maps directly to a single corresponding element in the other.

1 M

2 F

Such mappings ensure consistent data harmonization during data integration and standardization phases, as outlined in the GCDMP (Chapter: Database Design and Integration).

Many-to-one (C) mapping would occur if multiple values (e.g., ''Male,'' ''M,'' ''Man'') mapped to a single standardized value, which isn't the case here.

Thus, the mapping is one-to-one, ensuring precise correspondence between both representations of gender data.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.4 -- Data Mapping and Harmonization

CDISC SDTM Implementation Guide, Section 5.2 -- Controlled Terminology and Mapping Rules

ICH E6(R2) GCP, Section 5.5.3 -- Data Integrity and Integration Principles

Answer : C

When a CRF modification leads to a sudden increase in EDC queries, the most likely cause is an error or misconfiguration in the edit checks introduced during or after the change. Therefore, the first step should be to review the edit checks for correctness.

The GCDMP (Chapter: Database Design and Validation) emphasizes that any database or CRF modification should trigger retesting of affected validation rules. Incorrect logic, thresholds, or missing conditional statements in automated edit checks can cause false or redundant queries, leading to unnecessary data management burden and site frustration.

Manually handling edit checks (option A) or adding SDV (option B) does not address the root cause. Having monitors close queries (option D) would mask the problem rather than resolve it.

Thus, the correct corrective measure is Option C --- review and validate the edit checks to ensure proper functionality.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Design and Validation, Section 5.5 -- Edit Check Testing and Review

ICH E6 (R2) GCP, Section 5.5.3 -- Validation and Change Control for Electronic Systems

FDA 21 CFR Part 11 -- System Validation and Change Documentation

Answer : D

Database audits are conducted to ensure ongoing data accuracy, completeness, and compliance throughout the lifecycle of a clinical trial. According to the Good Clinical Data Management Practices (GCDMP, Chapter: Data Quality Assurance and Control), quality audits are most effective when performed periodically during study conduct, rather than waiting until study completion.

Performing audits periodically allows early detection of data entry errors, protocol deviations, and system inconsistencies, thereby reducing the risk of large-scale data issues before database lock. This proactive approach aligns with risk-based quality management principles outlined in ICH E6(R2) and ensures corrective actions are implemented in real time.

Options A and B represent reactive quality control, which occurs too late to prevent data issues. Option C (after first few cases) provides initial validation but does not ensure continuous oversight.

Therefore, option D --- ''Periodically throughout the study'' --- represents the optimal and compliant timing for quality audits of the database.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Quality Assurance and Control, Section 5.3 -- Ongoing Quality Control and Auditing

ICH E6(R2) GCP, Section 5.1.1 -- Quality Management System and Risk-Based Monitoring

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 -- Data Review and Auditing Practices

Answer : A

In an Electronic Data Capture (EDC) system, even after a data manager completes all manual queries and marks data as 'clean,' the data may later appear unclean if the site (study coordinator) makes subsequent updates in the system after re-reviewing the source documents.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Electronic Data Capture Systems), site users maintain the authority to modify data entries as long as the system remains open for data entry. The EDC system audit trail captures such changes, which can automatically invalidate prior data reviews, triggering new discrepancies or changing system edit-check statuses.

This situation commonly occurs when the site identifies corrections in the source (e.g., wrong date or lab result) and updates the EDC form accordingly. These post-cleaning changes require additional review cycles to ensure the database reflects accurate and verified information before final lock.

Options B, C, and D are incorrect --- CRAs and medical monitors cannot directly change EDC data; they can only raise queries or request updates.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture Systems, Section 6.3 -- Post-Cleaning Data Changes and Audit Trails

ICH E6 (R2) GCP, Section 5.5.3 -- Data Integrity and Change Control

FDA 21 CFR Part 11 -- Electronic Records: Change Documentation Requirements

Answer : C

The best practice for developing electronic Case Report Forms (eCRFs) is to involve cross-functional team members throughout the design process.

According to the GCDMP (Chapter: CRF Design and Data Collection), eCRFs should be collaboratively developed by data 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 are fit-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 should never auto-populate without explicit source verification. Option D is outdated; while paper CRFs may inform structure, EDC-optimized eCRFs should 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