SCDM CCDM Exam Dumps

In an Electronic Data Capture (EDC) system, even after a data manager completes all manual queries and marks data as 'clean,' the data may later appear unclean if the site (study coordinator) makes subsequent updates in the system after re-reviewing the source documents.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Electronic Data Capture Systems), site users maintain the authority to modify data entries as long as the system remains open for data entry. The EDC system audit trail captures such changes, which can automatically invalidate prior data reviews, triggering new discrepancies or changing system edit-check statuses.

This situation commonly occurs when the site identifies corrections in the source (e.g., wrong date or lab result) and updates the EDC form accordingly. These post-cleaning changes require additional review cycles to ensure the database reflects accurate and verified information before final lock.

Options B, C, and D are incorrect --- CRAs and medical monitors cannot directly change EDC data; they can only raise queries or request updates.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture Systems, Section 6.3 -- Post-Cleaning Data Changes and Audit Trails

ICH E6 (R2) GCP, Section 5.5.3 -- Data Integrity and Change Control

FDA 21 CFR Part 11 -- Electronic Records: Change Documentation Requirements

Manual or visual data review is used to identify complex clinical relationships and contextual inconsistencies that cannot be detected by automated edit checks.

According to the GCDMP (Chapter: Data Validation and Cleaning), automated edit checks are ideal for structured validations, such as missing fields (option C), reference ranges (option D), or predefined value lists (option A). However, certain clinical cross-checks---such as verifying adverse event treatments against concomitant medication records---require clinical judgment and contextual understanding.

For example, if an adverse event of 'severe headache' was reported but no analgesic appears in the concomitant medication log, the data may warrant manual review and query generation. These context-based checks are best performed by trained data reviewers or medical data managers during manual data review cycles.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 6.3 -- Manual Review and Clinical Data Consistency Checks

ICH E6 (R2) Good Clinical Practice, Section 5.18.4 -- Clinical Data Review Responsibilities

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations -- Data Verification Principles

To synchronize data from electronic patient-reported outcomes (ePRO) and wearable activity-monitoring devices with site-entered visit data, both the study subject identifier and date/time are essential.

According to the GCDMP (Chapter: Data Management Planning and Study Start-up), each dataset must contain key identifiers that allow for accurate data integration and temporal alignment. In studies involving multiple digital data sources, time-stamped subject identifiers are necessary to ensure that the device-generated data correspond to the correct subject and study visit.

The subject identifier ensures data traceability and linkage to the appropriate participant, while date/time allows synchronization of device data (e.g., activity or physiological measurements) with the corresponding site-reported visit or event. Geo-spatial data (options C and D) are typically not relevant to study endpoints and pose unnecessary privacy risks under HIPAA and GDPR guidelines.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Integration and eSource Data, Section 5.2 -- Data Alignment and Synchronization Principles

FDA Guidance for Industry: Use of Electronic Health Record Data in Clinical Investigations, Section 4.2 -- Data Linking and Synchronization

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

Database audits are conducted to ensure ongoing data accuracy, completeness, and compliance throughout the lifecycle of a clinical trial. According to the Good Clinical Data Management Practices (GCDMP, Chapter: Data Quality Assurance and Control), quality audits are most effective when performed periodically 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 with risk-based quality management principles outlined in ICH 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

Let's calculate the workload:

200 patients 30 minutes = 6,000 minutes/week

6,000 minutes 60 = 100 hours/week

Over 6 months (~26 weeks): 100 26 = 2,600 hours total

Assuming a full-time Data Manager works approximately 160 hours/month, over 6 months (960 hours) per full-time equivalent (FTE):

2,600 960 2.7 FTEs total for the entire study period

To find the average per month, we divide evenly over 6 months:

2.7 6 0.45 FTE per month, or approximately 50% of a Data Manager per month.

Thus, the correct answer is B. Fifty percent of a Data Manager per month.

This estimate follows GCDMP best practices in resource planning, ensuring adequate data management capacity for ongoing external data handling activities.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Project Management, Section 5.3 -- Resource Estimation and Workload Planning

ICH E6(R2) GCP, Section 5.1.1 -- Quality Systems and Adequate Staffing