CCDM Exam Dumps : Certified Clinical Data Manager

Theinner joinoperation retrievesonly the records that exist in both tables, which is theintersectionof two datasets.

In clinical data management, relational databases often store related data in multiple tables—for example, demographic data in one table and lab results in another. When a Data Manager needs to extract records that exist in both (e.g., subjects appearing in both demographics and labs), aninner joinis used.

According to theGCDMP (Chapter: Database Design and Build), joins are fundamental relational operations ensuring data consistency and integrity across multiple data domains.

Inner join:Returns matching records from both tables (intersection).

Left/right outer joins:Return all records from one table and matching records from the other (preserving nonmatches).

Full outer join:Returns all records from both tables, whether matched or not.

Therefore, to select only the50 records commonto both tables, the correct operation is aninner join.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Design and Build, Section 4.3 – Relational Database Concepts and Joins

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – Data Processing and Validation

In aSQL (Structured Query Language)database, theSELECTstatement specifies which columns to display from a table. In this query, only three columns —Pt_ID,MRN, andSSN— are being selected from thepatienttable.

This means the resulting dataset will contain:

The same number ofrows (records)as the original table (assuming noWHEREfilter), and

Fewer columnsthan the full table.

In database terminology:

“Wider” refers to more columns (fields).

“Narrower” refers to fewer columns (fields).

Since this query retrieves only 3 columns (out of potentially many in the original table), the result set isnarrower than the patient table, makingoption Dcorrect.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.1 – Relational Databases and Query Logic

ICH E6(R2) GCP, Section 5.5.3 – Data Retrieval and Integrity Principles

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.4 – Database Query Controls

The correct and compliant sequence forEDC system setup and implementationbegins onlyafter the study protocol is finalized, as all case report form (CRF) designs, database structures, and validation rules derive directly from the finalized protocol.

According toGCDMP (Chapter: EDC Systems Implementation), the proper order is:

Protocol finalized– defines endpoints and data requirements.

Database created– built according to the protocol and CRFs.

Edit checks created– programmed to validate data entry accuracy.

Database tested (UAT)– ensures functionality, integrity, and compliance.

Sites trained and system released– only then can data entry begin.

Option B follows this logical and regulatory-compliant sequence. Other options (A, C, D) are eitherpaper-based workflowsor violateGCP-compliant timelines(e.g., enrolling subjects before database validation).

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Electronic Data Capture (EDC) Systems, Section 5.2 – System Setup and Implementation Flow

ICH E6(R2) GCP, Section 5.5.3 – Computerized Systems Validation and User Training Before Use

FDA 21 CFR Part 11 – Validation and System Release Requirements