When coding adverse events (AEs) using MedDRA (Medical Dictionary for Regulatory Activities) , valid AE terms must correspond to specific, medically meaningful concepts that match directly to a Preferred Term (PT) or Lowest Level Term (LLT) in the dictionary.

Among the options, “Elevated HDL” (High-Density Lipoprotein) represents a single, medically interpretable, and standard term that can directly match to a MedDRA LLT or PT. This makes it suitable for auto-coding , where the system automatically maps verbatim terms to MedDRA entries without manual intervention.

In contrast:

ALT (B) and Abnormal SGOT (C) are incomplete or nonspecific; they describe test names or qualitative interpretations rather than events.

Option D lists multiple findings, making it too complex for automatic mapping. Such compound entries would require manual coding review .

According to GCDMP (Chapter: Medical Coding and Dictionaries) , a valid AE term should be:

Clinically interpretable (not just a lab test name)

Unambiguous

Single-concept based , not a collection of results

Thus, option A (Elevated HDL) is correct, as it aligns with MedDRA’s single-concept, standard terminology structure suitable for auto-coding.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Medical Coding and Dictionaries, Section 5.3 – Auto-coding and Verbatim Term Management

ICH M1 MedDRA Term Selection: Points to Consider, Section 2.1 – Coding Principles

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

When laboratory data are missing from a paper-based clinical study, the Data Manager should direct data-entry personnel to issue a query to the investigative site for clarification or correction.

According to the Good Clinical Data Management Practices (GCDMP, Chapter: Data Validation and Cleaning) , every missing, inconsistent, or out-of-range data point must be reviewed and, if necessary, resolved through the formal query management process . This ensures that all discrepancies between the source documents and database entries are properly documented, traceable, and auditable.

Data-entry staff are not authorized to infer or fill in missing information. They must escalate such discrepancies to the site via query, preserving data integrity and regulatory compliance with ICH E6 (R2) and FDA 21 CFR Part 11 . Calling the patient directly (option B) would violate confidentiality and site communication protocol, while simply flagging or ignoring the issue (options A and D) would not meet GCDMP query resolution standards.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 5.2 – Query Management and Resolution

ICH E6 (R2) Good Clinical Practice, Section 5.18.4 – Communication of Data Discrepancies

FDA 21 CFR Part 11 – Electronic Records; Query Audit Trails Requirements

In a double-blind clinical trial , the randomization schedule must be generated by an independent biostatistician not directly involved in study operations or data management to preserve study blinding and integrity.

According to ICH E9 and the GCDMP (Chapter: Regulatory Requirements and Compliance) , randomization generation and blinding must be handled in a way that prevents bias or unintentional unblinding of study personnel. The sponsor’s biostatistician not assigned to the project (Option C) is the appropriate person because they have the necessary statistical expertise but remain operationally independent from study execution.

A project biostatistician (Option D) or programmer (Option A) directly involved in data analysis could inadvertently compromise blinding. The CRO biostatistician (Option B) should not perform this function if the sponsor retains randomization responsibility.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Regulatory Requirements and Compliance, Section 6.4 – Randomization and Blinding

ICH E9 – Statistical Principles for Clinical Trials, Section 5.4 – Randomization Procedures and Blinding

FDA Guidance for Industry: Adaptive Design Clinical Trials for Drugs and Biologics, Section 4.3 – Maintaining Blinding Integrity

RACI is a project management and governance framework used to define roles and responsibilities within a project. Each letter represents a distinct role type:

Responsible (R): The person(s) who perform the work or execute the task.

Accountable (A): The individual ultimately answerable for the task’s completion and success (only one per activity).

Consulted (C): Subject matter experts who provide input or guidance before decisions are made.

Informed (I): Individuals kept up to date on progress or outcomes but not directly involved in execution.

The RACI model ensures clarity in ownership and accountability , preventing duplication of effort or responsibility confusion. It is a key component of the GCDMP (Chapter: Project Management in Data Management) for ensuring clear delegation and communication within clinical data management teams.

Hence, option D is correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Project Management in Data Management, Section 5.1 – Roles, Responsibilities, and RACI Matrices

Project Management Institute (PMI) Framework – Responsibility Assignment Matrices (RACI)

ICH E6(R2) GCP, Section 5.1.1 – Defined Roles and Quality Oversight Responsibilities

When combining data from two datasets where one uses numeric codes (1 = Male, 2 = Female) and another uses text codes (M, F), each unique value in one dataset corresponds exactly to one unique value in the other.

This relationship is a one-to-one mapping , where each element in one dataset maps directly to a single corresponding element in the other.

1 → M

2 → F

Such mappings ensure consistent data harmonization during data integration and standardization phases, as outlined in the GCDMP (Chapter: Database Design and Integration) .

Many-to-one (C) mapping would occur if multiple values (e.g., “Male,” “M,” “Man”) mapped to a single standardized value, which isn’t the case here.

Thus, the mapping is one-to-one , ensuring precise correspondence between both representations of gender data.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.4 – Data Mapping and Harmonization

CDISC SDTM Implementation Guide, Section 5.2 – Controlled Terminology and Mapping Rules

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

In managing site data timeliness , the most actionable and effective tool is a report listing all outstanding (missing or incomplete) CRFs .

According to GCDMP (Chapter: Communication and Study Reporting) , Data Managers must provide site-level performance reports highlighting:

Outstanding CRFs not yet entered,

Unresolved queries, and

Pending data corrections.

Such reports help sites prioritize and address data gaps efficiently.

Option A and D are historical metrics without actionable context.

Option B gives 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

A front-end check is a type of real-time validation performed at the point of data entry—typically within an Electronic Data Capture (EDC) system or data entry interface—designed to ensure that the data entered in a text box (or any input field) is valid, logically correct, and within expected parameters before the user can proceed or save the record.

According to the Good Clinical Data Management Practices (GCDMP, Chapter on Data Validation and Cleaning) , edit checks are essential components of data validation that ensure data accuracy, consistency, and completeness. Front-end checks are implemented within the data collection interface and are triggered immediately when data are entered. They prevent invalid entries (such as letters in numeric fields, out-of-range values, or improper date formats) from being accepted by the system.

Examples of front-end checks include:

Ensuring a numeric field accepts only numbers (e.g., weight cannot include text characters).

Validating that a date is within an allowable range (e.g., not before the subject’s date of birth).

Requiring mandatory fields to be completed before moving forward.

This differs from back-end checks or programmed checks , which are typically run later in batch processes to identify data inconsistencies after entry. Manual checks are human-performed reviews, often for context or data that cannot be validated automatically (e.g., narrative assessments).

Front-end edit checks are preferred wherever possible because they prevent errors at the source , reducing the number of downstream data queries and cleaning cycles. They contribute significantly to data quality assurance , regulatory compliance , and efficiency in data management operations .

Reference (CCDM-Verified Sources):

Society for Clinical Data Management (SCDM), Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 6.2 – Edit Checks and Real-Time Data Validation

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

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

CDISC Operational Data Model (ODM) Specification – Edit Check Implementation Standards

The best response is that diary data to be source data verified should be selected using a risk-based approach .

According to the GCDMP (Chapter: Data Quality Assurance and Control) and FDA Guidance on Risk-Based Monitoring (RBM) , not all data require full SDV. Electronic patient-reported outcome (ePRO) or mobile diary data are typically direct electronic source data (eSource) captured at the time of entry, which already ensures authenticity and traceability.

A risk-based SDV approach focuses verification efforts on data critical to subject safety and primary efficacy endpoints , as defined in the study’s Risk Assessment Plan or Monitoring Plan . Random or full verification of low-risk data (like diary compliance metrics) adds unnecessary effort and cost.

Thus, Option C aligns with current regulatory expectations and data management best practices.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Quality Assurance and Control, Section 7.3 – Risk-Based Monitoring and SDV

ICH E6 (R2) Good Clinical Practice, Section 5.18 – Risk-Based Quality Management

FDA Guidance for Industry: Oversight of Clinical Investigations — A Risk-Based Approach to Monitoring (2013)

When an audit identifies missing or undocumented training , the most appropriate and compliant response is to identify the root cause of the issue and implement corrective and preventive actions (CAPA) to ensure that similar findings do not recur.

According to Good Clinical Data Management Practices (GCDMP, Chapter: Quality Management and Auditing) , effective quality systems require root cause analysis (RCA) for all audit findings. The process involves:

Investigating why the documentation gap occurred (e.g., poor tracking, outdated SOP, or lack of oversight).

Correcting the immediate issue (e.g., ensuring the developers complete or document training).

Updating processes, training systems, or oversight mechanisms to prevent recurrence.

While sending the two developers to training (D) addresses the symptom , it does not resolve the systemic issue identified by the audit. Options B and C are non-compliant and do not address quality system improvement.

Therefore, option A (Identify the root cause and improve the process) is the best and CCDM-compliant response.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Quality Management and Auditing, Section 6.2 – Corrective and Preventive Actions (CAPA)

ICH E6(R2) GCP, Section 5.1.1 – Quality Management and Continuous Process Improvement

FDA 21 CFR Part 820.100 – Corrective and Preventive Action (CAPA) Requirements

Under ICH E6 (R2) Good Clinical Practice and 21 CFR Part 312.52 , when a sponsor delegates or transfers obligations for a clinical trial to a Contract Research Organization (CRO) , there must be a written description of each specific obligation being assumed by the CRO .

According to the Good 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 a Transfer 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 B is 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