SCDM CCDM Exam Questions

In Electronic Data Capture (EDC) systems, free text fields should be used only when a predefined list of acceptable responses cannot accommodate the full variability of input data --- most notably for Adverse Event (AE) verbatim terms.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: CRF Design and Data Collection), AE verbatim terms are initially entered as free text by site staff to accurately capture the investigator's exact medical description of the event. These verbatim terms are later coded using standardized dictionaries such as MedDRA during medical coding, ensuring both flexibility and standardization in reporting.

Conversely, fields such as urine sedimentation rate (A), date of birth (C), and Body Mass Index (D) require structured numeric or date formats to enable validation, range checks, and consistency across datasets. Free text would compromise data integrity, accuracy, and validation efficiency for these structured data elements.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 4.3 -- Use of Free Text and Coded Fields

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 -- Data Structure and Validation

MedDRA Introductory Guide, Section 2.3 -- Verbatim Entry and Coding Requirements

In a relational database structure, each record in a table is uniquely identified by a primary key. In this case, the VITAL_SIGNS table uses a composite primary key consisting of:

Patient Identifier,

Visit Number, and

Vital Signs Parameter Name.

This means each record represents a unique measurement of a specific parameter (e.g., blood pressure, pulse) for a patient at a specific visit.

When joining PATIENT_DEMOGRAPHY and VITAL_SIGNS tables on the patient identifier, the result set will include one record for every combination of patient, visit, and parameter --- i.e., one record per patient per visit per vital sign parameter.

Therefore, option C correctly describes the expected number of records.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 -- Primary and Foreign Key Relationships in Relational Models

CDISC SDTM Implementation Guide, Section 5.3 -- Observation-Level Data Structures

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

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