SCDM Updated CCDM Exam Questions and Answers by aviraj

RACIis aproject management and governance frameworkused to defineroles and responsibilitieswithin a project. Each letter represents a distinct role type:

Responsible (R):The person(s) who perform the work or execute the task.

Accountable (A):The individual ultimately answerable for the task’s completion and success (only one per activity).

Consulted (C):Subject matter experts who provide input or guidance before decisions are made.

Informed (I):Individuals kept up to date on progress or outcomes but not directly involved in execution.

The RACI model ensuresclarity in ownership and accountability, preventing duplication of effort or responsibility confusion. It is a key component of theGCDMP (Chapter: Project Management in Data Management)for ensuring clear delegation and communication within clinical data management teams.

Hence,option Dis correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Project Management in Data Management, Section 5.1 – Roles, Responsibilities, and RACI Matrices

Project Management Institute (PMI) Framework – Responsibility Assignment Matrices (RACI)

ICH E6(R2) GCP, Section 5.1.1 – Defined Roles and Quality Oversight Responsibilities

Theprimary reasondata managers review data before a monitor’s review is toidentify and flag discrepancies or inconsistenciesso that site monitors can focus their efforts more efficiently during on-site or remote source data verification (SDV).

According to theGood 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 emphasizesprocess purpose, not prescriptive order. Thus,option Bcorrectly 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

In a relational clinical database, themost efficient and normalized structurefor data collected repeatedly over time—such asvital signs—isone record per patient per visit.

Each patient will have multiple records, one for each visit when vital signs are assessed. This structure supports:

Time-based analysis (e.g., trends across visits),

Accurate data linkage with visit-level metadata, and

Efficient querying for longitudinal data.

According to theGCDMP (Chapter: Database Design and Build), the relational design principle dictates that data should be stored at thelowest unique level of observation. Since vital signs vary by both patient and visit, the combination ofpatient ID + visit IDforms a unique key for each record.

Option A (per visit) lacks patient identification, while options B and D aggregate data too broadly, losing temporal detail.

Thus,option C (One record per patient per visit)correctly represents the normalized design structure.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 4.2 – Normalization and Table Structure

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

ICH E6(R2) GCP, Section 5.5.3 – Data Handling Principles

TheQuery frequency counts per data element(Option D) is the best metric for identifyingdata trends and potential systemic data issuesin clinical trials.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Data Quality Assurance and Control),trend analysisinvolves identifying recurring data issues across subjects, sites, or variables to detect training gaps, protocol misinterpretation, or CRF design flaws. A high number of queries generated for specific fields (e.g., visit date, lab values, or dosing information) may indicate systemic problems such as unclear CRF instructions or site-level misunderstandings.

While metrics such aspercent of data cleaned (A)andtime to database lock (B)reflect overall progress and efficiency, they do not identifyspecific data pattern issues. Thenumber of subjects screened/enrolled (C)pertains to recruitment rather than data quality.

Therefore,query frequency per data elementprovides actionable insights for quality improvement, process refinement, and early identification of potential risks.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Quality Assurance and Control, Section 6.3 – Metrics and Trend Analysis

ICH E6 (R2) Good Clinical Practice, Section 5.18.4 – Risk-Based Quality Review and Data Trends

FDA Guidance for Industry: Oversight of Clinical Investigations – Risk-Based Monitoring, Section 6 – Data Metrics and Trend Evaluation