CCDM Exam Questions & Answers

In managing site data timeliness, the most actionable and effective tool is a report listing all outstanding (missing or incomplete) CRFs.

According to GCDMP (Chapter: Communication and Study Reporting), Data Managers must provide site-level performance reports highlighting:

Outstanding CRFs not yet entered,

Unresolved queries, and

Pending data corrections.

Such reports help sites prioritize and address data gaps efficiently.

Option A and D are historical metrics without actionable context.

Option B gives a general overview but lacks specific site-level actionability.

Hence, option C (List of outstanding forms) provides the clearest and most motivating feedback to sites for timely data entry and query resolution.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Communication and Study Reporting, Section 5.3 -- Data Timeliness and Reporting Metrics

ICH E6(R2) GCP, Section 5.1.1 -- Sponsor Oversight and Data Communication Requirements

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 -- Site-Level Data Timeliness Reporting

For a well-maintained 100-subject study with ongoing data cleaning and completed reconciliations, the database lock process typically takes a few days after the Last Patient Last Visit (LPLV).

According to the GCDMP (Chapter: Database Lock and Archiving), the duration of the lock process depends on the level of data cleanliness at LPLV. If the study team has conducted continuous data cleaning, query resolution, and external data reconciliation throughout the trial, then the final lock steps (e.g., final data review, documentation, and approvals) can be completed in 2--5 days.

However, if significant cleaning or reconciliation remains outstanding, lock may take several weeks. Since the question states that data are ''maintained almost all clean,'' Option B -- a few days -- is the appropriate estimate.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Lock and Archiving, Section 6.2 -- Database Lock Preparation and Timelines

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

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations -- Data Lock and Archiving Procedures

Regulatory agencies such as the FDA and ICH require that electronic data be retained in a format that preserves audit trails and traceability.

While PDF images (option C) provide a static representation of data, they do not preserve the underlying audit trail (i.e., who changed what, when, and why). The ASCII data files with corresponding audit trails (option D) provide complete transparency and comply with 21 CFR Part 11 and GCDMP archival standards.

Option A (storing computers) is unnecessary and impractical, and Option B (paper source documents) are site records, not system archives.

Hence, option D is correct --- ASCII data files with audit trails meet traceability and compliance standards.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Lock and Archiving, Section 5.4 -- Archival Formats and Audit Trail Retention

ICH E6(R2) GCP, Section 5.5.3 -- Data Integrity, Audit Trails, and Record Retention

FDA 21 CFR Part 11 -- Electronic Records; Audit Trail and Retention Requirements

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

When the primary efficacy endpoint in a clinical trial is 3-month survival, the key data element required is the death date. This is because the survival endpoint is determined by calculating whether the subject lived or died within a defined time frame from study enrollment or randomization.

According to the GCDMP (Chapter: Data Management Planning and Study Start-up), the Clinical Data Manager (CDM) must identify and ensure the capture of all critical data elements necessary to evaluate the study endpoints. For time-to-event analyses (e.g., survival studies), accurate event dates (death date) are essential for endpoint derivation and statistical analysis.

Other data elements such as cause of death or date of autopsy (options B and C) may support secondary analyses or safety reviews but are not necessary to determine the survival endpoint itself. Similarly, birth date (option D) contributes to demographic data but is unrelated to the primary efficacy outcome.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Planning and Study Start-up, Section 4.4 -- Critical Data Identification for Endpoints

ICH E9 -- Statistical Principles for Clinical Trials, Section 2.2.3 -- Time-to-Event Data Considerations

FDA Guidance for Industry: Clinical Trial Endpoints for Drug Development