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

UnderICH E6 (R2) Good Clinical Practiceand21 CFR Part 312.52, when asponsor delegates or transfers obligationsfor a clinical trial to aContract Research Organization (CRO), there must be awritten description of each specific obligation being assumed by the CRO.

According to theGood Clinical Data Management Practices (GCDMP), while sponsors may outsource responsibilities such as data management, monitoring, or biostatistics,ultimate accountability remains with the sponsor. The documentation of the transfer of responsibilities ensures regulatory transparency and compliance.

This written agreement, often referred to as aTransfer of Obligations (TOO)document, defines exactly which duties the CRO is responsible for (e.g., CRF design, data cleaning, database lock), as well as any retained sponsor oversight. A general statement that "all obligations are transferred" (option D) is insufficient per regulatory expectations, as sponsors must retain traceability of responsibility.

Therefore,Option Bis correct — a detailed written description of transferred obligations is required.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Regulatory Compliance and Oversight, Section 5.2 – Sponsor and CRO Responsibilities

ICH E6 (R2) Good Clinical Practice, Section 5.2.1 – Transfer of Trial-Related Duties and Functions

FDA 21 CFR 312.52 – Transfer of Obligations to a Contract Research Organization

In Structured Query Language (SQL), theWHEREclause is used to filter records based on specified criteria. The query retrievesall columnsfrom thepatienttable (SELECT *) but onlythose rowswhere themedical_record_numbervalue is greater than 9000.

This means:

Thenumber of columns (fields)remains the same as the original table.

Thenumber of rows (records)will beequal to or less thanthe number of rows in thepatienttable, depending on how many patients meet the filter condition.

Hence, the result set can only beshorter or equal in lengthcompared to the original table. It cannot be longer, wider, or narrower, since no new rows or columns are created.

Therefore,option B—“Shorter or of equal length than the patient table”— is correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 – Relational Database Queries and Filtering Logic

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

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.4 – Query Logic and Record Subsetting

When adverse events (AEs) are discovered after adatabase lock, the appropriate first step is toevaluate the impactof the missing data on theintegrity, safety analysis, and regulatory validityof the study results.

According toGCDMP (Chapter: Data Quality Assurance and Control), any post-lock data discovery requires aroot cause assessment and impact analysisbefore deciding whether to unlock the database. The key question is whether the missing AEs:

Affectprimary safety endpoints,

Introducebiasin safety reporting, or

Alterefficacy conclusions.

Based on the assessment, the Data Management and Biostatistics teams determine if unlocking and correction are justified. Simply entering data immediately (A) or repeating checks (D) without analysis may violate data control procedures.

Hence,option Bis correct — the first step is to assess theimpact on data validity and analysis.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Quality Assurance and Control, Section 5.5 – Post-Lock Findings and Impact Assessment

ICH E6(R2) GCP, Section 5.1.1 – Quality Management and Risk Assessment

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 – Post-Lock Data Management

In a relational database system used in clinical data management, performance refers to how efficiently the system processes transactions, retrieves data, and handles large volumes of information without delay or data integrity issues. Among the listed options, loading a large lab data file into the database (Option B) has the most significant impact on database performance.

According to theGood Clinical Data Management Practices (GCDMP, Chapter on Database Design and Build), the bulk data load process — such as importing large external datasets (e.g., central lab data, ECG results, or imaging metadata) — can be computationally intensive. This process engages the database’s input/output (I/O) subsystem, indexing mechanisms, and transaction logs simultaneously, often locking tables temporarily and consuming significant memory and processing resources.

Unlike standard CRF data entry (Option A) or record updates (Option D), which are incremental and typically processed in smaller transactional batches, bulk loading operations handle thousands or millions of rows at once. If not optimized (e.g., via staging tables, indexing strategies, or commit frequency control), such operations can degrade system performance, slow down concurrent user access, and increase the risk of transaction failure.

Executing a properly designed query (Option C) can also be resource-intensive depending on data volume and join complexity, but when queries are properly optimized (using indexed keys, efficient SQL joins, and selective retrieval), their impact is generally controlled and transient compared to large data imports.

Therefore, as outlined in theGCDMP Database Design and BuildandFDA Computerized Systems Guidance, the most performance-impacting activity in a relational database is bulk loading large external datasets, making Option B the correct answer.

Reference (CCDM-Verified Sources):

Society for Clinical Data Management (SCDM), Good Clinical Data Management Practices (GCDMP), Chapter: Database Design and Build, Section 6.7 – Database Performance and Optimization

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6 – System Performance and Data Handling Efficiency

ICH E6 (R2) Good Clinical Practice, Section 5.5 – Data Handling and Record Integrity

CDISC Operational Data Model (ODM) Implementation Guide – Bulk Data Transfer and Validation Considerations

Adding multiple new sites late in the enrollment period creates aconcentrated influx of new datanear the end of the study. These sites typically start enrolling patients later, resulting in a“bolus” of Case Report Forms (CRFs)that must be entered, validated, and cleaned within a shorter timeframe to meet database lock deadlines.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Project Management and Data Flow), late site activation compresses the timeline for data management tasks, necessitating increased resources fordata entry, query management, and cleaning. Data management teams must anticipate this surge and plan accordingly—either by increasing staffing or revising timelines to prevent bottlenecks and maintain quality.

Whileoption D(increased query rates) can occur, it is a secondary effect. Themost direct and consistent impactis the surge in data volume requiring expedited processing near study end.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Project Management, Section 5.3 – Managing Changes in Site Activation and Data Flow

ICH E6(R2) GCP, Section 5.1 – Quality Management and Oversight

Manual or visual data reviewis used to identifycomplex clinical relationships and contextual inconsistenciesthat cannot be detected by automated edit checks.

According to theGCDMP (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 verifyingadverse event treatments against concomitant medication records—requireclinical judgmentandcontextual 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

According toICH E6(R2) Good Clinical Practice (GCP), Section 5.18.1, theSponsoris ultimatelyresponsible for developing and implementing the Monitoring Plan.

The Monitoring Plan defines:

Theextent and nature of monitoring(e.g., on-site, remote, risk-based).

Theresponsibilities of monitors.

Thecommunication and escalation proceduresfor data quality and protocol compliance.

While theCRO (B)orMonitor (D)may perform monitoring activities under delegation, theSponsorretains legal accountability for ensuring a compliant and effective plan is developed and maintained. TheData Manager (C)may contribute by outlining data review workflows, but is not responsible for authoring or owning the plan.

Therefore,option A (Sponsor)is the correct answer.

Reference (CCDM-Verified Sources):

ICH E6(R2) GCP, Section 5.18.1 – Purpose and Responsibilities for Monitoring

SCDM GCDMP, Chapter: Regulatory Compliance and Oversight, Section 5.3 – Sponsor Responsibilities in Monitoring and Quality Assurance

FDA Guidance for Industry: Oversight of Clinical Investigations – Sponsor Responsibilities (2013)

In managingsite data timeliness, the most actionable and effective tool is areport listing all outstanding (missing or incomplete) CRFs.

According toGCDMP (Chapter: Communication and Study Reporting), Data Managers must providesite-level performance reportshighlighting:

Outstanding CRFs not yet entered,

Unresolved queries, and

Pending data corrections.

Such reports help sites prioritize and address data gaps efficiently.

Option AandDare historical metrics without actionable context.

Option Bgives a general overview but lacks specific site-level actionability.

Hence,option C (List of outstanding forms)provides the clearest and most motivating feedback to sites for timely data entry and query resolution.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Communication and Study Reporting, Section 5.3 – Data Timeliness and Reporting Metrics

ICH E6(R2) GCP, Section 5.1.1 – Sponsor Oversight and Data Communication Requirements

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 – Site-Level Data Timeliness Reporting

In studies where themedical record serves as the source document, theElectronic Data Capture (EDC)system users (typically study coordinators or site personnel) must have appropriatetraining on how to access and log into the medical record system. This competency ensures that data abstracted from the electronic medical record (EMR) are complete, accurate, and verifiable in compliance with Good Clinical Practice (GCP) andGood Clinical Data Management Practices (GCDMP).

According to theGCDMP (Chapter: EDC Systems and Data Capture)andICH E6(R2), all personnel involved in data entry and verification must be trained in both the EDC and the primary source systems (e.g., EMR). This ensures that the integrity of data flow—from source to EDC—is maintained, and that personnel understand system access controls, audit trails, and proper documentation of source verification.

Whileresolving discrepant data (C)andscreening subjects (A)are part of study operations, thecompetency directly related to EDC system use in EMR-based studiesis the ability to properly log into and navigate the medical records system to extract source data.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Electronic Data Capture (EDC), Section 5.1 – Source Data and System Access Requirements

ICH E6(R2) Good Clinical Practice, Section 4.9 – Source Documents and Data Handling

FDA Guidance: Use of Electronic Health Record Data in Clinical Investigations, Section 3 – Investigator 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