SCDM CCDM Exam Questions

Blood pressure is a quantitative physiological measurement, typically consisting of two continuous numeric values: systolic and diastolic pressure. Therefore, the most appropriate and scientifically valid method of data collection is to use two continuous variables (e.g., systolic = 120 mmHg, diastolic = 80 mmHg).

According to the GCDMP (Chapter: CRF Design and Data Collection), data fields must be designed to capture the most precise, accurate, and analyzable form of clinical data. Numeric data should be collected using numeric data types to allow for range checks, calculations (e.g., mean arterial pressure), and statistical analysis.

Options such as categorical representations (radio buttons or check boxes) introduce rounding, data loss, and analytic limitations. Coding a verbatim diagnosis (option A) is inappropriate for numeric vital sign data and violates the principle of capturing data at the most granular level.

Thus, the correct and validated method per CCDM standards is two continuous variables, ensuring accuracy, traceability, and analytical flexibility.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 4.2 -- Best Practices for Quantitative Data Capture

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Data Accuracy and Collection Standards

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 4.3 -- Data Format and Structure Requirements

Maintaining traceability of external data imports (such as laboratory results) is a fundamental principle of clinical data management. According to the GCDMP (Chapter: External Data Transfers and Integration), Data Managers must retain an unaltered copy of the raw data exactly as received from the vendor.

This archived version serves as a reference for:

Data provenance verification,

Audit trail review, and

Discrepancy resolution between vendor and study database.

Since the central lab maintains its own audit trail, the Data Manager's responsibility is to preserve the original data transmission file before applying transformations, merges, or validations.

Options A, C, and D describe procedural safeguards but do not meet the regulatory requirement of traceable data lineage. Only option B (Maintaining a copy of the data as received) ensures compliance with ICH E6(R2) and FDA 21 CFR Part 11 standards for data traceability and integrity.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: External Data Transfers and Integration, Section 5.2 -- Data Traceability and Version Control

ICH E6(R2) GCP, Section 5.5.3 -- Data Integrity and Source Data Verification

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.4 -- Source Data Traceability and Archiving

The Study Schedule of Events (SoE) section in the protocol is the most concise and comprehensive representation of the timing of data collection throughout a study.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Data Management Planning and Study Start-up) and ICH E6 (R2) GCP, the SoE outlines what assessments, procedures, and data collections occur at each study visit (e.g., screening, baseline, treatment visits, follow-up). This table is a foundational tool for CRF design, database structure, and edit-check development, ensuring alignment between the protocol and data management systems.

While the study endpoints section (A) defines what is measured, and the protocol synopsis (C) summarizes the design, only the schedule of events (B) specifies when data collection occurs for each parameter. The ICH essential documents (D) pertain to regulatory documentation, not study visit timing.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Planning and Study Start-up, Section 4.1 -- Using the Schedule of Events for Database Design

ICH E6 (R2) GCP, Section 6.3 -- Trial Design and Schedule of Assessments

FDA Guidance for Industry: Protocol Design and Data Collection Standards

When a protocol is amended mid-study, resulting in additional data collection requirements, the Data Management Plan (DMP) must be updated accordingly and all relevant stakeholders must be notified.

According to the GCDMP (Chapter: Data Management Planning and Study Start-up), the DMP is a living document that defines all data management processes for a clinical study. It must accurately reflect the current data flow, CRF design, validation procedures, and reporting structure. Any protocol amendments affecting data capture, structure, or analysis require immediate DMP revision and distribution to ensure alignment across data management, clinical, and biostatistics teams.

Failure to update and communicate DMP changes can lead to misalignment in data handling and introduce compliance risks during audits or inspections. Therefore, Option B is correct: the DMP must be updated and the change communicated to all stakeholders (e.g., sponsor, CRO, clinical operations, biostatistics).

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Plan (DMP), Section 5.3 -- Maintaining and Updating the DMP

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

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

The primary reason data managers review data before a monitor's review is to identify and flag discrepancies or inconsistencies so that site monitors can focus their efforts more efficiently during on-site or remote source data verification (SDV).

According to the Good Clinical Data Management Practices (GCDMP, Chapter on Data Validation and Cleaning), proactive data review by data management staff ensures data completeness and accuracy by identifying missing, inconsistent, or out-of-range values. This pre-review helps streamline the monitoring process, reduces the volume of open queries, and enhances data quality.

Option A is true but not the main reason for pre-monitor review. Option C highlights a capability rather than a rationale. Option D is partially correct, but the GCDMP emphasizes process purpose, not prescriptive order. Thus, option B correctly captures the practical and process-oriented reason for early data review---to ensure data are ready and accurate for the monitor's review phase.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 5.3 -- Data Review Timing and Purpose

ICH E6(R2) GCP, Section 5.18 -- Monitoring and Data Verification Requirements