When efficacy data are not covered by existing CDISC SDTM domains , the first resource the Data Manager should consult is the CDISC Therapeutic Area Implementation Guide (TAIG) for that therapeutic field.

According to the GCDMP (Chapter: Standards and Data Mapping) , CDISC’s Therapeutic Area User Guides (TAUGs) and Implementation Guides provide standardized data structures, variable definitions, controlled terminology, and implementation examples for specific diseases or therapeutic areas. These guides ensure consistency across studies, promote interoperability, and align data collection with regulatory submission expectations.

Consulting other sponsors’ forms or external registries (options A and C) can be informative but do not provide authoritative CDISC-compliant standards. SNOMED terms (option B) address medical terminology, not structural data domain definitions.

Therefore, Option D is correct— CDISC TA Implementation Guides are the recognized primary reference when extending or designing SDTM-compliant CRFs.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Standards and Data Mapping, Section 4.2 – Use of CDISC Standards

CDISC Therapeutic Area User Guides (TAUGs) – Implementation Guidance for Domain Extension

FDA Data Standards Catalog – CDISC Therapeutic Area Standards

When an investigator retires mid-study and the replacement refuses to use the Electronic Data Capture (EDC) system, the data manager must not take unilateral action but rather collaborate with the study team to explore acceptable solutions.

Per the GCDMP (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 with ICH E6 (R2) GCP and FDA 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 this scenario, the site has deviated from the approved study protocol by using a different formulation (nebulized albuterol instead of inhaler) . This is considered a protocol deviation or violation , depending on study definitions.

Per GCDMP (Chapter: Data Validation and Cleaning) and ICH E6(R2) , Data Managers are responsible for ensuring that all protocol deviations affecting data integrity or subject safety are accurately captured and documented within the clinical database. The appropriate action is to issue a data query prompting the site to record the deviation in the designated section (e.g., “Protocol Deviations” CRF).

Option A: Incorrect — it affects data comparability.

Option B: Escalation to the Ethics Committee is handled by the sponsor, not the Data Manager.

Option C: Updating the CRF guidelines is premature; first, the deviation must be logged and assessed.

Therefore, option D (Query the site to enter a Protocol Violation) is the correct and compliant action.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 6.2 – Query Management and Protocol Deviations

ICH E6(R2) GCP, Section 4.5 – Compliance with Protocol

FDA Guidance for Industry: Oversight of Clinical Investigations — Compliance and Protocol Deviation Reporting

The primary reason data managers review data before a monitor’s review is to identify and flag discrepancies or inconsistencies so that site monitors can focus their efforts more efficiently during on-site or remote source data verification (SDV).

According to the Good 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 emphasizes process purpose , not prescriptive order. Thus, option B correctly 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

When adverse events (AEs) are discovered after a database lock , the appropriate first step is to evaluate the impact of the missing data on the integrity, safety analysis, and regulatory validity of the study results.

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

Affect primary safety endpoints ,

Introduce bias in safety reporting, or

Alter efficacy 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 B is correct — the first step is to assess the impact 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

Maintaining traceability of external data imports (such as laboratory results) is a fundamental principle of clinical data management. According to the GCDMP (Chapter: External Data Transfers and Integration) , Data Managers must retain an unaltered copy of the raw data exactly as received from the vendor .

This archived version serves as a reference for:

Data provenance verification,

Audit trail review, and

Discrepancy resolution between vendor and study database.

Since the central lab maintains its own audit trail, the Data Manager’s responsibility is to preserve the original data transmission file before applying transformations, merges, or validations.

Options A, C, and D describe procedural safeguards but do not meet the regulatory requirement of traceable data lineage . Only option B (Maintaining a copy of the data as received) ensures compliance with ICH E6(R2) and FDA 21 CFR Part 11 standards for data traceability and integrity.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: External Data Transfers and Integration, Section 5.2 – Data Traceability and Version Control

ICH E6(R2) GCP, Section 5.5.3 – Data Integrity and Source Data Verification

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.4 – Source Data Traceability and Archiving

The correct action is to consult the CRO’s Lead Data Manager and CRO’s Project Leader (Option C) to ensure the issue is addressed through the appropriate oversight and escalation process.

According to the GCDMP (Chapter: Project Management and Communication) , when a sponsor Data Manager identifies significant data management issues under CRO oversight — such as aging queries or site performance disparities — communication must follow the established governance and escalation pathway defined in the Scope of Work (SOW) and Data Management Plan (DMP).

Directly contacting the site (Option B) bypasses the CRO’s chain of command and violates communication protocols. Notifying only the Clinical Leader (Option A) is insufficient, and ignoring the issue (Option D) jeopardizes the Data Safety Monitoring Board (DSMB) review timeline.

Therefore, Option C ensures a documented, collaborative approach to problem resolution within the contractual oversight structure.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Project Management and Communication, Section 7.1 – Oversight of CRO Data Management Activities

ICH E6 (R2) GCP, Section 5.2 – Contract Research Organization Responsibilities

FDA Guidance for Industry: Oversight of Clinical Investigations – Sponsor and CRO Roles and Communication Pathways

Testing query rules with test data inputs to confirm expected outputs without examining the underlying program logic is an example of black box testing .

According to the GCDMP (Chapter: Data Validation and System Testing) , black box testing is a functional testing approach used to verify that the system performs correctly from the end-user’s perspective. In this method, testers input various conditions and observe outputs to ensure the system behaves as intended — for instance, that edit checks trigger correctly when data fall outside predefined limits.

In contrast, white box testing involves examining internal logic, code, and algorithm structures. Because data managers typically validate edit checks through data-driven test cases rather than code inspection, black box testing is the appropriate and industry-standard method. This ensures compliance with validation documentation standards as outlined in FDA 21 CFR Part 11, Section 11.10(a) and ICH E6 (R2) system validation expectations.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Validation and Testing, Section 4.1 – Testing Approaches (Black Box and White Box)

FDA 21 CFR Part 11 – System Validation Requirements

ICH E6 (R2) GCP, Section 5.5.3 – Computerized Systems Validation

In paper-based clinical studies , front-end data checks (those performed during data entry) are intentionally kept minimal to ensure that data are entered exactly as recorded on the paper CRF . This principle ensures data integrity by maintaining fidelity between source and electronic records before any cleaning or edit validation occurs.

The GCDMP (Chapter: Data Validation and Cleaning) explains that data entry operators should input values as written, even if they appear incorrect or inconsistent, because the purpose of front-end checks is not to interpret but to capture data faithfully. The back-end edit checks —performed later by data managers—are designed to identify inconsistencies, out-of-range values, or logical errors that require clarification through queries.

This approach separates data capture from data cleaning , minimizing bias and preserving original investigator input. Hence, option A accurately states the rationale for keeping front-end checks minimal in paper-based studies.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 4.2 – Data Entry, Edit Checks, and Query Process

ICH E6(R2) GCP, Section 5.5.3 – Data Handling and System Controls

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.1 – Data Entry and Verification Processes

The Investigator holds the primary responsibility for ensuring the accuracy, completeness, and timeliness of Case Report Form (CRF) entries. This responsibility is mandated by regulatory requirements under ICH E6(R2) Good Clinical Practice (GCP) .

The investigator may delegate CRF completion to a qualified designee (e.g., site coordinator) , but the ultimate accountability remains with the investigator. The investigator’s signature (electronic or manual) on the CRF serves as certification that the data accurately reflect the source documents and the patient’s participation.

The GCDMP (Chapter: CRF Design and Data Collection) reinforces this by stating that while data managers ensure design quality and CRAs verify consistency with source data, the investigator is legally responsible for CRF accuracy .

Thus, option D (Investigator) is correct, as it aligns with both GCP and CCDM standards.

Reference (CCDM-Verified Sources):

ICH E6(R2) GCP, Section 4.9 – Records and Reports (Investigator Responsibilities)

SCDM GCDMP, Chapter: CRF Design and Data Collection, Section 5.1 – Investigator’s Role in Data Accuracy

FDA 21 CFR Part 312.62 – Investigator Recordkeeping and Record Retention