Pass the SCDM Clinical Data Management CCDM Questions and answers with CertsForce

Whenlaboratory dataare missing from a paper-based clinical study, theData Managershould directdata-entry personnel to issue a queryto the investigative site for clarification or correction.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Data Validation and Cleaning), every missing, inconsistent, or out-of-range data point must be reviewed and, if necessary, resolved through the formalquery management process. This ensures that all discrepancies between the source documents and database entries are properly documented, traceable, and auditable.

Data-entry staff arenot authorizedto infer or fill in missing information. They must escalate such discrepancies to the site via query, preservingdata integrityandregulatory compliancewithICH E6 (R2)andFDA 21 CFR Part 11. Calling the patient directly (option B) would violate confidentiality and site communication protocol, while simply flagging or ignoring the issue (options A and D) would not meet GCDMP query resolution standards.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 5.2 – Query Management and Resolution

ICH E6 (R2) Good Clinical Practice, Section 5.18.4 – Communication of Data Discrepancies

FDA 21 CFR Part 11 – Electronic Records; Query Audit Trails Requirements

The best metric to identifymalfunctioning or ineffective edit checksis thecount by edit check of the number of times the check fired. This allows data managers to assess whether specific edit checks are performing as intended.

According to theGCDMP, Chapter: Data Validation and Cleaning, edit checks are programmed logic conditions that identify data inconsistencies or potential errors during data entry. A properly functioning edit check should trigger only when data falls outside acceptable or logical limits. If an edit check fires too frequently or not at all, it may indicate alogic errorin the check’s programming or configuration.

By analyzing counts by individual edit checks, data managers can:

Identify checks that never trigger (potentially inactive or incorrectly written),

Detect overactive checks (poorly designed parameters causing excessive false positives), and

Optimize system performance and review efficiency.

This metric supports continuous improvement in data validation logic and contributes to cleaner, higher-quality clinical databases.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 6.2 – Edit Check Design and Performance Metrics

FDA Guidance: Computerized Systems Used in Clinical Investigations – Section on Validation of Electronic Data Systems

Database auditsare conducted to ensureongoing data accuracy, completeness, and compliancethroughout the lifecycle of a clinical trial. According to theGood Clinical Data Management Practices (GCDMP, Chapter: Data Quality Assurance and Control), quality audits are most effective when performedperiodically 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 withrisk-based quality management principlesoutlined inICH 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

When a clinical study usesblood pressure (BP)as anefficacy endpoint, the most reliable and standardized method of data collection is throughstudy-provisioned equipment.

According to theGCDMP (Chapter: CRF Design and Data Collection), data collected for primary efficacy endpoints must beconsistent, accurate, and standardized across all investigative sites. Usingstudy-provided calibrated equipmentensures that measurements are taken under uniform conditions, eliminating inter-site variability due to differences in devices, calibration, or measurement methods.

Collecting BP data from medical records (option A) risks inconsistent timing and techniques. Using each site’s own equipment (option B) introduces variability, while patient self-reports (option D) lack reliability and objectivity.

Thus, thebest practiceis to provision and standardize all equipment used to collect endpoint-related physiological data, ensuring regulatory-quality results suitable for analysis.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 5.1 – Standardization of Clinical Measurements

ICH E6 (R2) GCP, Section 5.5.3 – Data Accuracy and Equipment Standardization

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 4.3 – Data Capture and Standardization Requirements

During a regulatory inspection, inspectors expect to find documentedStandard Operating Procedures (SOPs)governing the use, validation, and maintenance ofcomputerized systems, includingdata backup and recovery procedures.

According to theGCDMP (Chapter: Computerized Systems and Compliance)andFDA 21 CFR Part 11, organizations must maintain an SOP that ensuresdata protection against loss, corruption, or unauthorized access. The SOP should describe backup frequency, secure storage, verification of backup integrity, and procedures for data restoration.

While theData Management Plan (A)andEdit Specifications (D)are study-level documents, and theStatistical Analysis Plan (C)focuses on analysis procedures,only a Data Backup Plan (B)constitutes a requiredsystem-level SOPensuring compliance and data continuity.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Computerized Systems and Compliance, Section 5.2 – Data Security, Backup, and Recovery SOPs

FDA 21 CFR Part 11 – Subpart B, Controls for Closed Systems

ICH E6(R2) GCP, Section 5.5.3 – System Security, Data Backup, and Recovery Requirements

A completedata element definitionin clinical data management should include:

Nameandclear descriptionof the data element,

Data type(e.g., numeric, text, date),

Precisionor scale (if numeric), and

Unit or dimensionalityof measure (e.g., centimeters, inches).

In this example, while the data type (“measured physical quantity”) and precision (0.1) are defined, theunit of measurement(e.g., centimeters or inches) is missing. This omission leads to ambiguity and could cause serious discrepancies when comparing or analyzing measurements.

TheGCDMP (Chapter: Database Design and Build)emphasizes that units and dimensionality must be explicitly defined and consistently applied in all CRFs, metadata dictionaries, and data transformations.

Thus,option D (Unit or dimensionality of measure)is correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 – Metadata and Data Element Definitions

CDISC CDASH Implementation Guide, Section 3.3 – Data Element Metadata Requirements

ICH E6(R2) GCP, Section 5.5.3 – Data Accuracy and Standardized Definitions

When an investigator retires mid-study and the replacement refuses to use theElectronic Data Capture (EDC)system, thedata managermust not take unilateral action but rathercollaborate with the study teamto explore acceptable solutions.

Per theGCDMP (Chapter: Project Management in Data Management), any deviation from the established data capture method — particularly a change that affects regulatory compliance, data consistency, or site operations — requires a cross-functional assessment. The study team, which includes clinical operations, project management, regulatory affairs, and data management, should evaluate feasible alternatives such as:

Allowing paper CRF entry followed by centralized data transcription,

Retraining site staff on EDC use, or

Temporarily suspending data entry until compliance can be restored.

Immediate site closure (option A) or unilateral decisions by data management (options C and D) violate escalation and communication protocols. Collaborative decision-making ensures continuity, compliance, and data integrity, in line withICH E6 (R2) GCPandFDA 21 CFR Part 11.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Project Management and Communication, Section 5.2 – Handling Site and Investigator Changes

ICH E6 (R2) Good Clinical Practice, Section 4.1 – Investigator Responsibilities

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations – Section on EDC Operations and Site Management

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

TheData Manager (DM)plays a critical role in maintaining transparent communication with the clinical study team regardingdata quality and study progress. One of the most essential metrics regularly reported by the DM is thepercentage of data entered and cleaned.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Communication and Study Reporting), these metrics provide insight into study status, data readiness for interim analysis, and timeline predictability for database lock. Regular communication includes:

Percent of CRFs entered and verified

Percent of queries resolved

Outstanding data issues or missing pages

Other options fall outside the Data Manager’s direct responsibility:

A (Enrollment)is typically reported by clinical operations.

B (Staffing changes)are handled by site management.

D (Safety events)are communicated by the safety/pharmacovigilance team.

Thus,option Ccorrectly reflects the Data Manager’s responsibility for ongoing study communication.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Communication and Study Reporting, Section 5.3 – Study Metrics and Status Updates

ICH E6(R2) GCP, Section 5.1.1 – Communication and Oversight in Quality Management

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 – Data Status Reporting

Before implementing anEDC system upgrade, thefirst taskof the Data Manager is toassess the impact on the data.

According to theGCDMP (Chapter: Electronic Data Capture Systems)andFDA 21 CFR Part 11, any system upgrade must undergoimpact assessmentto determine how the change might affectdata integrity, functionality, validation, and ongoing study operations. This assessment ensures that no data are lost, corrupted, or rendered inconsistent during or after the upgrade.

The Data Manager should evaluate:

Potential effects on existing data, edit checks, and reports,

System functionality impacting current workflows, and

Any revalidation requirements.

Only after the impact is understood should the Data Manager proceed to communicate with sites (option A), update documentation (option B), or modify CRFs if required (option D).

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture Systems, Section 7.3 – System Upgrades and Change Control

FDA 21 CFR Part 11 – Change Control and Validation Requirements

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – Change Impact on Data Integrity and System Validation