Most Recent SCDM CCDM Exam Dumps

When importing external data (e.g., laboratory or imaging results) into a clinical database, the first step in data import quality control is to verify that incoming files conform to the pre-specified data transfer specifications (DTS).

According to the GCDMP (Chapter: External Data Transfers and Integration), the Data Transfer Specification defines file structure, variable names, data types, delimiters, record counts, and validation rules. The initial import check confirms that the received file matches the technical and structural requirements before content or record consistency is evaluated.

Subsequent checks---such as record counts (A), data consistency with existing database (C), and internal logical consistency (D)---are performed only after the file structure is validated and confirmed to match the specifications. Failure to perform this first check may cause import errors or corrupted data loads.

Thus, the first and most critical verification step is ensuring file conformity to the agreed data transfer specifications, making option B correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: External Data Transfers, Section 4.2 -- Data Transfer File Validation and Import Checks

ICH E6(R2) GCP, Section 5.5.3 -- Validation of Computerized Systems and Data Imports

To submit study data to the FDA in CDISC SDTM format, the sponsor must map and transform the collected data from the study's operational database (e.g., EDC) into SDTM-compliant domains.

According to GCDMP (Chapter: Standards and Data Integration) and CDISC SDTM Implementation Guide, this process includes:

Mapping raw data elements from the clinical database to SDTM domains (e.g., DM, AE, VS).

Transforming data to comply with SDTM structural and naming conventions.

Validating the output using CDISC compliance tools (e.g., Pinnacle 21).

Re-entering data (B) is unnecessary, and a letter of intent (C) is not required. SDTM is explicitly accepted by FDA for both retrospective and prospective submissions, so (D) is incorrect.

Thus, option A is correct --- map and transform existing data to SDTM format for regulatory submission.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Standards and Data Integration, Section 5.3 -- Data Transformation and CDISC Mapping

CDISC SDTM Implementation Guide, Version 3.4 -- Data Conversion and Submission Requirements

FDA Study Data Technical Conformance Guide, Section 2.2 -- SDTM Mapping and Validation

The most essential Standard Operating Procedure (SOP) for management of an Electronic Data Capture (EDC) system is Change Control.

Per GCDMP (Chapter: Computerized Systems and Compliance) and FDA 21 CFR Part 11, any changes made to an EDC system---whether to software configuration, study database design, or system functionality---must follow a documented, validated, and auditable change control process. This ensures that:

Modifications are properly authorized, tested, and approved before implementation.

System validation remains intact.

Data integrity, traceability, and regulatory compliance are maintained.

While vendor management (A) and coding maintenance (C) have supporting SOPs, change control (D) is mandatory for any system handling regulated clinical data. Measurement of data quality (B) is important but not specifically tied to system management procedures.

Thus, option D (Change control) is the correct answer.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Computerized Systems and Compliance, Section 5.3 -- Change Control and System Maintenance

FDA 21 CFR Part 11 -- Electronic Records and Electronic Signatures, Section 11.10(a--k)

ICH E6(R2) GCP, Section 5.5.3 -- Computerized Systems Validation and Change Documentation

Once a clinical database is locked, it becomes read-only --- no further data modifications can be made by any users, including site personnel. This ensures that the data are finalized, consistent, and auditable for statistical analysis and regulatory submission.

According to the GCDMP (Chapter: Database Lock and Archiving), the lock process involves freezing the database to prevent accidental or unauthorized changes. After lock, access permissions are restricted, and all edit and update functions are disabled. If any corrections are required post-lock, the database must be unlocked under controlled procedures (with full audit trail documentation).

Thus, option C --- The site study coordinator is not able to make the change --- correctly reflects standard EDC functionality and regulatory compliance.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Lock and Archiving, Section 5.2 -- Database Lock Procedures and Controls

ICH E6(R2) GCP, Section 5.5.3 -- Data Integrity and Audit Trail Requirements

FDA 21 CFR Part 11 -- Controls for Electronic Records and System Lock Functions

When a new version of MedDRA (Medical Dictionary for Regulatory Activities) is released, the correct action is to evaluate the extent and impact of the changes before implementation.

According to the GCDMP (Chapter: Medical Coding and Dictionaries), MedDRA updates are published twice yearly (March and September). Each release may introduce new terms, modify hierarchies, or retire old ones. Prior to adopting a new version, the Data Manager and Medical Coder must:

Assess the number and type of term changes,

Determine the potential effect on ongoing coding consistency, and

Decide whether migration to the new version is warranted mid-study or deferred until database lock.

Immediate recoding (option C) without evaluation may cause inconsistencies and require additional validation. Continuing with the existing version (option B) may be acceptable short-term but must be justified. Using an alternative dictionary (option D) is noncompliant, as MedDRA is the regulatory standard for safety reporting.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Medical Coding and Dictionaries, Section 6.3 -- Version Control and Impact Assessment

MedDRA Term Selection: Points to Consider (MSSO, Latest Version), Section 3 -- Versioning and Maintenance

ICH E2B(R3) -- Clinical Safety Data Management: Data Elements for Transmission of Individual Case Safety Reports