CCDM Sample Questions Answers

Once theCase Report Form (CRF)has been finalized and database development has begun, thenext primary responsibility of the Data Manageris to prepare aData Validation Plan (DVP)for the clinical database.

According to theGCDMP (Chapter: Database Design and Build), the DVP documents all planned validation procedures — includingedit checks, cross-form validations, discrepancy management workflows, and system testing requirements. This ensures that data entry, processing, and cleaning are consistent with protocol requirements and that the database will produce reliable, auditable data for analysis.

Whilesystem requirement specifications (option B)are prepared before database development begins, andtimeline planning (option C)occurs during the study startup phase, theDVPis the critical next step post-CRF approval to define and validate system logic before user acceptance testing (UAT).

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Design and Build, Section 6.4 – Data Validation Plan (DVP) Development

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

FDA 21 CFR Part 11 – System Validation Requirements for Electronic Records

The best long-term corrective and preventive action (CAPA) in this situation is acombination of user re-training, communication, and routine monitoring— as described inOption B.

According to theGCDMP (Chapter: Electronic Data Capture Systems)andFDA 21 CFR Part 11, user credentials and electronic signatures in clinical systems arelegally bindingand must be used only by the assigned individual. Simultaneous log-ins under the same credentials often indicatecredential sharing, acompliance violationthat must be addressed through user education, reinforced security policies, and ongoing system oversight.

While technical controls (option A) may be considered, behavioral and procedural reinforcement are the first lines of defense. Options C and D are excessive and not aligned with proportional CAPA practices.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture (EDC) Systems, Section 7.1 – User Access, Authentication, and Training

FDA 21 CFR Part 11 – Electronic Records and Electronic Signatures, Sections 11.10(i) and 11.200(a)

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – Access Control and Audit Trail Requirements

This event qualifies as aSerious Adverse Event (SAE)because itresulted in a prolonged hospitalization, even though the episode itself was mild.

According toICH E2AandGCDMP (Chapter: Safety Data Handling and Reconciliation), an adverse event is considered“serious”if it results in any of the following outcomes:

Death,

Life-threatening situation,

Hospitalization or prolongation of existing hospitalization,

Persistent or significant disability/incapacity, or

Congenital anomaly/birth defect.

The severity (mild, moderate, severe) describesintensity, while seriousness describesregulatory significance and medical outcome. Thus, a mild tachycardia episode leading to extended hospital stay meets theregulatory definition of an SAE.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Safety Data Handling and Reconciliation, Section 5.2 – Definition and Classification of Serious Adverse Events

ICH E2A – Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, Section II – Seriousness Criteria

FDA 21 CFR 312.32 – IND Safety Reporting: Serious Adverse Event Definitions

InElectronic Data Capture (EDC)studies, proper user training and access management are essential for maintainingdata integrity, security, and regulatory compliance. According to theGood Clinical Data Management Practices (GCDMP)andFDA 21 CFR Part 11, EDC systems must ensure that only qualified and trained personnel can access study data, and that all access rights reflect current study responsibilities.

User training and access must therefore be reviewed and updated whenever:

Site staff leave the study(access revocation is required),

New site staff are added(training and credentialing are required), and

Study team members change roles(access levels must be modified accordingly).

However, if asoftware upgradeoccurs thatdoes not impact the functional roles, user permissions, or data handling processes, retraining or reauthorization isnot required. This is because such updates do not alter compliance-critical workflows or user interactions.

Therefore, the exception isC – when a software upgrade does not affect users.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture Systems, Section 7.1 – User Access and Training Controls

FDA 21 CFR Part 11 – Electronic Records; Electronic Signatures, Section 11.10(i) & (k)

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – System Security and User Training

When a company transitions from paper-based data capture toElectronic Data Capture (EDC)systems, one of the most critical areas requiring procedural updates is theData Review and Validation SOP. The introduction of EDC systems fundamentally changes how data is collected, reviewed, validated, and queried.

According to theGood Clinical Data Management Practices (GCDMP), the implementation of EDC introduces real-time data entry and review, automated edit checks, and electronic query management. These functionalities necessitate revised procedures to define how data validation, discrepancy management, and monitoring are conducted electronically. The SOP must specify roles, responsibilities, system access controls, and processes for electronic source verification (eSource), ensuring compliance with21 CFR Part 11andICH E6 (R2)requirements.

Other SOPs such asHandling External DataorData Backupmay require minor updates, but theData Review and Validation SOPundergoes the most extensive change because EDC technology shifts validation responsibilities from post-data entry review to real-time oversight within the system.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture (EDC) Systems, Section 6.3 – SOP Adaptation for EDC Implementation

FDA 21 CFR Part 11 – Electronic Records; Electronic Signatures

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

Providing the central laboratory vendor with acomplete subject demographic listingallowsongoing reconciliationbetween the sponsor’s EDC system and the vendor’s laboratory databaseduring study conduct.

TheGCDMP (Chapter: External Data Transfers and Integration)emphasizes thatsubject reconciliationensures that all laboratory data correspond to valid enrolled subjects and visits. Regular reconciliation throughout the study prevents data mismatches, missing results, or misassigned lab reports.

This proactive measure supports timely query resolution and data integrity across systems. Waiting until after database lock (as in option A) would delay corrections and risk inconsistencies. Options B and D address secondary benefits but not theprimary purpose—ongoing subject-level reconciliation.

Thus,option Cis correct.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: External Data Transfers, Section 4.4 – Reconciliation and Vendor Communication

ICH E6(R2) GCP, Section 5.5.3 – Data Management, Reconciliation, and Integration

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.3 – External Data Management

In anElectronic Data Capture (EDC)system, even after a data manager completes all manual queries and marks data as "clean," the data may later appearuncleanifthe site (study coordinator)makes subsequent updates in the system after re-reviewing thesource documents.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Electronic Data Capture Systems), site users maintain the authority to modify data entries as long as the system remains open for data entry. TheEDC system audit trailcaptures such changes, which can automatically invalidate prior data reviews, triggering new discrepancies or changing system edit-check statuses.

This situation commonly occurs when the site identifies corrections in the source (e.g., wrong date or lab result) and updates the EDC form accordingly. These post-cleaning changes require additional review cycles to ensure the database reflects accurate and verified information before final lock.

Options B, C, and D are incorrect — CRAs and medical monitors cannot directly change EDC data; they can only raise queries or request updates.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture Systems, Section 6.3 – Post-Cleaning Data Changes and Audit Trails

ICH E6 (R2) GCP, Section 5.5.3 – Data Integrity and Change Control

FDA 21 CFR Part 11 – Electronic Records: Change Documentation Requirements

If a clinical site continues to provideinconsistent or illogical dataafter multiple queries, the correct course of action is toescalate the issue to the appropriate site contact personnel, typically theClinical Research Associate (CRA)orSite Monitor.

According to theGood Clinical Data Management Practices (GCDMP), persistent data discrepancies often indicate a misunderstanding of the protocol, CRF instructions, or data entry procedures at the site level. Repeatedly re-querying the same data without escalation wastes time and risks introducing bias or error. By escalating through formal communication channels, the issue can be clarified through re-training, documentation review, or site monitoring visits.

The GCDMP emphasizes that escalation ensuresdata accuracy, site accountability, and protocol adherence, maintaining both data quality and regulatory compliance. Data managers must document the escalation process in the Data Management Plan (DMP) and ensure proper follow-up resolution is achieved.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Communication and Issue Escalation, Section 4.2 – Handling Persistent Data Discrepancies

ICH E6 (R2) Good Clinical Practice, Section 5.18 – Monitoring and Site Communication

FDA Guidance for Industry: Oversight of Clinical Investigations – Risk-Based Monitoring, Section on Issue Escalation

During a regulatory inspection, inspectors expect to find documentedStandard Operating Procedures (SOPs)governing the use, validation, and maintenance ofcomputerized systems, includingdata backup and recovery procedures.

According to theGCDMP (Chapter: Computerized Systems and Compliance)andFDA 21 CFR Part 11, organizations must maintain an SOP that ensuresdata protection against loss, corruption, or unauthorized access. The SOP should describe backup frequency, secure storage, verification of backup integrity, and procedures for data restoration.

While theData Management Plan (A)andEdit Specifications (D)are study-level documents, and theStatistical Analysis Plan (C)focuses on analysis procedures,only a Data Backup Plan (B)constitutes a requiredsystem-level SOPensuring compliance and data continuity.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Computerized Systems and Compliance, Section 5.2 – Data Security, Backup, and Recovery SOPs

FDA 21 CFR Part 11 – Subpart B, Controls for Closed Systems

ICH E6(R2) GCP, Section 5.5.3 – System Security, Data Backup, and Recovery Requirements

In theEDC database build process, the first logical specifications that require approval are theelectronic Case Report Form (eCRF) fields.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Database Design and Build), eCRF field specifications define what data elements are collected, their data types, permitted values, field lengths, and any associated metadata. Approval of these specifications forms the foundation for subsequent design components such asedit check programming,query management rules, anddata validation logic.

Edit checks (B)are developed only after fields and structures are finalized.

Metric reports (C)andeCRF guidelines (D)are downstream documentation or tools, not logical specifications required at the build start.

Therefore,option A (eCRF fields)is correct, as their approval marks the first formal milestone in the EDC system development life cycle.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 4.2 – Logical Design and eCRF Field Specifications

ICH E6(R2) GCP, Section 5.5.3 – System Design and Validation Documentation

FDA 21 CFR Part 11 – System Validation and Documentation Controls

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

The best choice for managingStandard Operating Procedures (SOPs)in a compliant and auditable manner is aDocument Management System (DMS).

According to theGCDMP (Chapter: Regulatory Requirements and Compliance)andICH E6 (R2), SOPs must beversion-controlled, securely stored, retrievable, and auditable. Avalidated DMSsupports controlled access, document lifecycle management (draft, review, approval, and archival), and electronic audit trails, ensuring full compliance withFDA 21 CFR Part 11andGood Documentation Practices (GDP).

WhileLearning Management Systems (C)track training, they are not intended for document control.Spreadsheets (B)andpaper systems (D)cannot provide adequate version tracking, access security, or audit capability required for regulatory inspection readiness.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Regulatory Requirements and Compliance, Section 5.2 – SOP Management and Document Control

ICH E6 (R2) GCP, Section 5.5.3 – Document and Record Management

FDA 21 CFR Part 11 – Electronic Records and Signatures, Section 11.10 – System Validation and Document Controls

To monitorsite variability in eligibility screening, you must analyzethe number of subjects screenedversusthe number of subjects enrolledat each site. This allows identification of sites that are over- or under-screening relative to their enrollment yield.

TheGCDMP (Chapter: Data Quality Assurance and Metrics)emphasizes thatscreening-to-enrollment ratiosare critical indicators of protocol compliance and data quality. Sites with unusually low conversion rates may have unclear understanding of inclusion/exclusion criteria, requiring targeted training or monitoring.

Other options (A, C, D) provide enrollment metrics but do not revealscreening efficiency or variability, which depend on bothscreening and enrollment data.

Thus,option Bcorrectly identifies the data necessary for monitoring eligibility screening performance across sites.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Quality Assurance and Metrics, Section 5.4 – Site Performance Metrics

ICH E6(R2) GCP, Section 5.18 – Monitoring and Site Oversight Requirements

The section of theClinical Study Report (CSR)most useful for aData Manageris thedescription of how data were processed.

According to theGCDMP (Chapter: Data Quality Assurance and Control), this section details thedata handling methodology— includingdata cleaning, coding, transformation, and derivation procedures— all of which are core responsibilities of data management. Reviewing this section ensures that the data processing methods documented in the CSR align with theData Management Plan (DMP),Data Validation Plan (DVP), anddatabase specifications.

Thestatistical methods section (option A)is primarily for biostatistics, and therationale for study design (option B)pertains to clinical and regulatory affairs.Clinical narratives (option D)are used by medical reviewers, not data managers.

By reviewing how data were processed, the Data Manager verifies that the study data lifecycle—from collection to analysis—was conducted in compliance with regulatory and GCDMP standards.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Quality Assurance and Control, Section 6.3 – Documentation of Data Processing in Clinical Study Reports

ICH E3 – Structure and Content of Clinical Study Reports, Section 11.3 – Data Handling and Processing

FDA Guidance for Industry: Clinical Study Reports and Data Submission – Data Traceability and Handling Documentation

TheInformed Consent Form (ICF)is the document that explicitly describes what study subjects can expect regardingdata disclosure, privacy, and confidentialityduring and after participation in a clinical trial. According toICH E6 (R2) Good Clinical PracticeandFDA Human Subject Protection Regulations (21 CFR Parts 50 and 56), participants must be fully informed about how their personal and clinical data will be collected, used, stored, and shared — both during the study and in any subsequent data-sharing or publication activities.

TheGCDMPreiterates that clinical data managers must ensure that all data handling practices align with the privacy commitments made in the ICF. This includes compliance withdata protection regulationssuch as HIPAA (in the U.S.) and GDPR (in the EU). The ICF defines the permissible scope of data use, ensuring ethical management and subject protection.

Documents like theprotocolordata sharing planmay outline procedures and responsibilities but do not directly inform participants of their rights and data use expectations. Only theICFis designed for that ethical communication purpose.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Ethics, Privacy, and Data Security

ICH E6 (R2) Good Clinical Practice, Sections 4.8.10 & 4.8.12

FDA 21 CFR Part 50 – Protection of Human Subjects, Informed Consent Requirements

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)

TheIndividual Case Safety Report (ICSR)is the standard format used globally for the exchange ofSerious Adverse Event (SAE)data between clinical data management systems (EDC) and safety management systems.

According toICH E2B(R3)andGood Clinical Data Management Practices (GCDMP, Chapter: Safety Data Management and SAE Reconciliation), the ICSR provides thedata structure and content standardsfor electronic transmission of safety data, including patient demographics, event details, outcomes, and product information. It ensures interoperability between systems by defining standardized message elements and controlled terminologies.

Other options are not applicable:

A. Medical Document for Regulatory Activities (MDRA)is not a recognized standard.

B. Biomedical Research Domain Model (BRIDG)provides conceptual modeling but not data exchange guidance.

D. SDTMis used for regulatory submission datasets, not real-time SAE exchange.

Thus,option C (Individual Case Safety Report)is correct, as it defines the internationally accepted electronic format for SAE data exchange between safety and clinical databases.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Safety Data Management and SAE Reconciliation, Section 4.3 – SAE Data Exchange and Standards

ICH E2B(R3): Electronic Transmission of Individual Case Safety Reports

FDA Guidance for Industry: Providing Regulatory Submissions in Electronic Format — Postmarketing ICSRs (2014)

Case Report Form Completion Guidelines (CCGs)are essential study documents that instruct site staff on how to complete each field of the CRF correctly. Aminimum requirementfor CCGs, according toGood Clinical Data Management Practices (GCDMP, Chapter: CRF Design and Data Collection), is that they must includeversion control.

Version control ensures that all updates or revisions to the CCG—arising from protocol amendments or clarification of data entry rules—are documented, dated, and traceable. This guarantees that site personnel are always using the most current version and supports audit readiness.

Option A describes an important design consideration but not a minimum compliance requirement. Option B is inaccurate, as CCGs must be approved and implementedbefore data collection begins, not after. Option D includes an irrelevant stakeholder (Marketing).

Therefore,option C—“CCGs must include a version control on the updated document”—is correct and compliant with CCDM and GCP standards.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: CRF Design and Data Collection, Section 4.3 – Development and Maintenance of CRF Completion Guidelines

ICH E6(R2) GCP, Section 8.2.1 – Essential Documents and Version Control Requirements

The section of theClinical Study Report (CSR)that is most useful for a Data Manager is the one that includes theenumeration and explanation of data errors. This section provides a summary of thedata quality control findings, including error rates, missing data summaries, and any issues identified during data review, validation, or database lock.

According to theGCDMP (Chapter: Data Quality Assurance and Control), post-study reviews of data errors and quality findings are essential for evaluating process performance, identifying recurring issues, and informing continuous improvement in future studies.

Other sections, such as clinical narratives (A) or statistical methods (C), are outside the core scope of data management responsibilities. Thedata error enumeration sectiondirectly reflects the quality and integrity of the data management process and is therefore the most relevant for review.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Quality Assurance and Control, Section 6.4 – Quality Reporting and Error Analysis

ICH E3 – Structure and Content of Clinical Study Reports, Section 14.3 – Data Quality Evaluation

Beforedatabase lock, the Data Manager must confirm that all collected data are complete, validated, and reconciled across systems. This includes:

Ensuring data completeness (B)— confirming all expected forms and data files have been received.

Verifying coded data (A)— ensuring no pending terms remain in coding dictionaries like MedDRA or WHO Drug.

Performing SAE reconciliation (C)— cross-checking the clinical database against the safety system for accuracy.

However,ensuring study close-out visits (D)isnot a data management function; it falls underclinical operationsandmonitoring responsibilities. While data management may review confirmation of site close-outs, the activity itself is not part of pre-database lock procedures.

Therefore,option Dcorrectly identifies the exception—an activity outside the data manager’s direct scope of responsibility before database closure.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Lock and Archiving, Section 5.3 – Pre-Lock Validation and Reconciliation Activities

ICH E6(R2) GCP, Section 5.5.3 – Data Handling and Quality Control Prior to Lock

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.1 – Database Management and Lock Procedures

When efficacy data arenot covered by existing CDISC SDTM domains, thefirst resourcethe Data Manager should consult is theCDISC Therapeutic Area Implementation Guide (TAIG)for that therapeutic field.

According to theGCDMP (Chapter: Standards and Data Mapping), CDISC’s Therapeutic Area User Guides (TAUGs) and Implementation Guides providestandardized data structures, variable definitions, controlled terminology, and implementation examplesfor 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 Dis correct—CDISC TA Implementation Guidesare 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

Thebest practicefor developingelectronic Case Report Forms (eCRFs)is to involvecross-functional team membersthroughout the design process.

According to theGCDMP (Chapter: CRF Design and Data Collection), eCRFs should be collaboratively developed bydata management, clinical operations, biostatistics, medical, and regulatory teams. Each function provides a unique perspective — data managers focus on data capture and validation; statisticians ensure alignment with analysis requirements; clinicians ensure medical relevance and protocol compliance.

Collaborative development ensures that the eCRFs arefit-for-purpose, capturing all required data accurately, minimizing redundancy, and supporting downstream data analysis.

Options A and B violate good data management practice because sites should not directly access coded terms (to prevent bias), and fields shouldnever auto-populate without explicit source verification. Option D is outdated; while paper CRFs may inform structure,EDC-optimized eCRFsshould leverage system functionality rather than mimic paper.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 4.2 – Collaborative CRF Development

ICH E6 (R2) GCP, Section 5.5.3 – Data Collection and System Validation

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 3.4 – CRF Design Considerations

Blood pressure is aquantitative physiological measurement, typically consisting oftwo continuous numeric values: systolic and diastolic pressure. Therefore, the most appropriate and scientifically valid method of data collection is to usetwo continuous variables(e.g., systolic = 120 mmHg, diastolic = 80 mmHg).

According to theGCDMP (Chapter: CRF Design and Data Collection), data fields must be designed to capture the mostprecise, accurate, and analyzableform of clinical data. Numeric data should be collected using numeric data types to allow for range checks, calculations (e.g., mean arterial pressure), and statistical analysis.

Options such as categorical representations (radio buttons or check boxes) introduce rounding, data loss, and analytic limitations. Coding a verbatim diagnosis (option A) is inappropriate for numeric vital sign data and violates the principle of capturing data at the most granular level.

Thus, the correct and validated method per CCDM standards istwo continuous variables, ensuring accuracy, traceability, and analytical flexibility.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 4.2 – Best Practices for Quantitative Data Capture

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – Data Accuracy and Collection Standards

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 4.3 – Data Format and Structure Requirements

TheStatisticianis responsible for assessing theoverall impact of data errors on the analysis and study results.

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Data Quality Assurance and Control)andICH E9 (Statistical Principles for Clinical Trials), while theData Managerensures data accuracy and completeness through cleaning and validation, theStatisticiandetermines whether the observed data discrepancies are statistically significant or if they may affect thevalidity, power, or interpretabilityof the study’s outcomes.

TheQuality Auditor (C)identifies and reports issues but does not quantify analytical impact. TheInvestigator (D)is responsible for clinical oversight, not statistical assessment. Thus, after a database audit, theStatistician (B)performs a formal evaluation to determine whether the magnitude and nature of the errors could bias results or require reanalysis.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Quality Assurance and Control, Section 7.3 – Data Audit and Impact Assessment

ICH E9 – Statistical Principles for Clinical Trials, Section 3.2 – Data Quality and Analysis Impact Assessment

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations – Data Validation and Analysis Review

During amajor system upgrade, it is critical to verify thatarchived data remain accessible, readable, and intactfollowing the implementation.

According to theGCDMP (Chapter: Database Lock and Archiving), regulatory requirements such as21 CFR Part 11andICH E6(R2)mandate that archived data must remain retrievable in ahuman-readable formatfor the duration of retention (often years after study completion).

Therefore, as part ofvalidation and verification testing, organizations must confirm that existing archives can still be accessed using the upgraded system or compatible tools.

Option A:Updating archive formats could alter original data integrity (noncompliant).

Option C:Migration offsite is an IT infrastructure task, not directly tied to the upgrade process.

Option D:Comparing CRFs to archives is unnecessary unless data corruption is suspected.

Hence,option B (testing archive accessibility)is the correct and compliant approach.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Lock and Archiving, Section 5.4 – System Upgrades and Archive Validation

ICH E6(R2) GCP, Section 5.5.3 – System Validation and Data Retention

FDA 21 CFR Part 11 – Data Archiving, Retention, and Retrieval Requirements

In international or multicenter clinical studies,laboratory dataoften originate from different laboratories that use varying measurement units (e.g., mg/dL vs. mmol/L). TheGood Clinical Data Management Practices (GCDMP, Chapter on CRF Design and Data Collection)provides clear guidance on managing this variability to ensuredata consistency,traceability, andminimized transcription errors.

The approach that results infewer transcription errorsis toallow sites to enter lab values exactly as recorded in the source document (original lab report)and to requireexplicit selection of the corresponding unitfrom a predefined list on the data collection form or within the electronic data capture (EDC) system. This method (Option B) preserves the original source data integrity while enabling centralized or automated unit conversion later during data cleaning or statistical processing.

Option B also supports compliance withICH E6 (R2) Good Clinical Practice (GCP), which mandates that transcribed data must remain consistent with the source documents. Attempting to derive units automatically (Option A) can lead to logical errors, while forcing sites to manually convert units (Option D) introduces unnecessary complexity and increases the risk of miscalculation or inconsistent conversions. Printing only standard units on the CRF (Option C) ignores local lab practices and can lead to discrepancies between CRF entries and source records, triggering numerous data queries.

TheGCDMPemphasizes that CRF design must account for local variations in measurement systems and ensure thatunit selection is structured (dropdowns, controlled lists)rather than free-text to prevent typographical errors and facilitate standardization during data transformation.

Therefore, OptionB—“Allow values to be entered as they are in the source and the selection of units on the data collection form”—is the most compliant, accurate, and efficient strategy for minimizing transcription errors in international lab data collection.

Reference (CCDM-Verified Sources):

Society for Clinical Data Management (SCDM), Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 5.4 – Laboratory Data Management and Unit Handling

ICH E6 (R2) Good Clinical Practice, Section 5.18 – Data Handling and Record Retention

CDISC SDTM Implementation Guide, Section 6.3 – Handling of Laboratory Data and Standardized Units

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6 – Source Data and Accuracy of Data Entry

Aprotocol compliance edit checkis designed to ensure that the data collected adheres to thespecific requirements defined in the study protocol, such as visit timing, procedure windows, and eligibility criteria.

The example inoption A— an edit check that triggers when a visit date falls outside the protocol-specified window — directly verifies compliance with the study design. This type of check supports real-time monitoring of protocol adherence, a critical quality and regulatory requirement underGCDMPandICH E6(R2).

Other options are examples of generaldata validation checks, not protocol compliance:

B:Ensures clinical plausibility (data range check).

C:Ensures completeness (missing data check).

D:Ensures format correctness (system validation check).

Thus,option Abest represents aprotocol compliance edit check, confirming that collected data conform to the visit schedule defined in the protocol.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Data Validation and Cleaning, Section 5.4 – Protocol Compliance Edit Checks

ICH E6(R2) GCP, Section 5.1.1 – Quality Management and Compliance Controls

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.3 – Edit Check Design and Validation

Maintainingtraceabilityof external data imports (such as laboratory results) is a fundamental principle of clinical data management. According to theGCDMP (Chapter: External Data Transfers and Integration), Data Managers mustretain 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 theoriginal data transmission filebefore applying transformations, merges, or validations.

Options A, C, and D describe procedural safeguards but do not meet the regulatory requirement oftraceable data lineage. Onlyoption B (Maintaining a copy of the data as received)ensures compliance withICH E6(R2)andFDA 21 CFR Part 11standards 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 efficacy endpoint ofall-cause mortality at one yeardirectly depends on thedate of deathfor each subject, makingOption D – Date of deaththe required data element.

According to theGCDMP (Chapter: Clinical Trial Protocols and Data Planning)andICH E3/E9 Guidelines, the primary efficacy analysis must be based on time-to-event data, particularly when the endpoint involvesmortality or survival. Thedate of deathallows accurate calculation oftime from randomization to event, essential for survival analysis (e.g., Kaplan-Meier curves).

Whilecause of death (C)may be collected for safety or secondary analyses,all-cause mortalityspecifically includes any death regardless of cause.Drug levels (A)andcoagulation times (B)may serve as pharmacodynamic or exploratory endpoints but do not directly measure mortality.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Planning and Protocol Review, Section 5.4 – Defining Data Required for Endpoints

ICH E9 – Statistical Principles for Clinical Trials, Section 2.3 – Time-to-Event Endpoints

FDA Guidance for Industry: Clinical Trial Endpoints for Drug Development and Approval

When aprotocol is amended mid-study, resulting in additional data collection requirements, theData Management Plan (DMP)must beupdated accordinglyand all relevant stakeholders must benotified.

According to theGCDMP (Chapter: Data Management Planning and Study Start-up), the DMP is aliving documentthat defines all data management processes for a clinical study. It must accurately reflect thecurrent data flow, CRF design, validation procedures, and reporting structure. Any protocol amendments affecting data capture, structure, or analysis require immediate DMP revision and distribution to ensure alignment across data management, clinical, and biostatistics teams.

Failure to update and communicate DMP changes can lead to misalignment in data handling and introduce compliance risks during audits or inspections. Therefore,Option Bis correct: the DMP must be updated and the change communicated to all stakeholders (e.g., sponsor, CRO, clinical operations, biostatistics).

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Plan (DMP), Section 5.3 – Maintaining and Updating the DMP

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – Documentation of Protocol Changes and Data Handling Procedures

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations – Section on Data Management Documentation

The correct action is toconsult 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 theGCDMP (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 followthe established governance and escalation pathwaydefined 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 theData Safety Monitoring Board (DSMB)review timeline.

Therefore,Option Censures 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

This question tests workload estimation and resource planning, which are fundamental competencies outlined in the Good Clinical Data Management Practices (GCDMP, Chapter on Project Management in Data Management). The task is to determine the Data Manager effort required based on the frequency and duration of data collection and processing activities.

Let’s calculate step by step:

Number of patients: 100

Frequency: Weekly (once per week)

Duration: 6 months ≈ 26 weeks

Time per file: 20 minutes

Total time per week:

100 patients × 20 minutes = 2,000 minutes per week

= 2,000 ÷ 60 = 33.3 hours per week

Total hours over 6 months:

33.3 hours/week × 26 weeks = 866 hours total

A full-time Data Manager typically works ~160 hours per month, so over six months:

160 × 6 = 960 hours total full-time capacity.

Therefore, the workload of 866 hours is approximately equivalent to one full-time Data Manager working across the six-month period:

866 ÷ 960 ≈ 0.9 FTE (Full-Time Equivalent).

This aligns most closely with Option D: One Data Manager per month (i.e., a full-time resource is required throughout the duration of the trial).

According to the GCDMP Project Management chapter, accurate resource estimation is critical in ensuring data management timelines are met without overloading staff or compromising data quality. The estimation process must consider not just the raw data download time but also associated data processing, verification, and upload into the clinical database.

Other options underestimate the effort significantly:

A (10%) and B (50%) do not account for cumulative weekly workload across multiple patients.

C (Two Data Managers) overestimates, as one Data Manager working full-time can manage the load efficiently.

Therefore, Option D is correct — approximately one full-time Data Manager (1.0 FTE) is required for the activity data alone during the six-month trial.

Reference (CCDM-Verified Sources):

Society for Clinical Data Management (SCDM), Good Clinical Data Management Practices (GCDMP), Chapter: Project Management in Data Management, Section 5.3 – Workload Estimation and Resource Allocation

SCDM GCDMP, Chapter: Data Handling and Processing – Effort Estimation for Repetitive Data Tasks

ICH E6 (R2) Good Clinical Practice, Section 5.1 – Quality Management and Resource Planning

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 4.3 – Operational Considerations for Data Management Activities

Thekey deliverables for User Acceptance Testing (UAT)are theTest Plan, Test Scripts, and Test Results.

According to theGCDMP (Chapter: Database Design and Validation), UAT is the final validation step before a clinical database is released for production. It confirms that the system performs according to user requirements and protocol specifications.

The deliverables include:

UAT Test Plan:Defines testing objectives, scope, acceptance criteria, and responsibilities.

UAT Test Scripts:Provide step-by-step instructions for testing database functionality, edit checks, and workflows.

UAT Test Results:Document actual test outcomes versus expected outcomes, including any deviations and their resolutions.

These deliverables form part of the system validation documentation required underFDA 21 CFR Part 11andICH E6 (R2)to demonstrate that the database has been properly validated.

Project Plans (option A) and Training (option B) occur in earlier phases, while eCRF Completion Guidelines (option D) support site data entry, not system validation.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Design and Validation, Section 5.3 – User Acceptance Testing Deliverables

FDA 21 CFR Part 11 – Validation Documentation Requirements

ICH E6 (R2) Good Clinical Practice, Section 5.5.3 – System Validation Records

When coding adverse events (AEs) usingMedDRA (Medical Dictionary for Regulatory Activities), valid AE terms must correspond to specific, medically meaningful concepts thatmatch directly to a Preferred Term (PT)orLowest 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 forauto-coding, where the system automatically maps verbatim terms to MedDRA entries without manual intervention.

In contrast:

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

Option Dlists multiple findings, making it too complex for automatic mapping. Such compound entries would requiremanual coding review.

According toGCDMP (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

Afront-end checkis a type ofreal-time validationperformed at the point of data entry—typically within anElectronic Data Capture (EDC)system or data entry interface—designed to ensure that the data entered in a text box (or any input field) isvalid, logically correct, and within expected parametersbefore the user can proceed or save the record.

According to theGood Clinical Data Management Practices (GCDMP, Chapter on Data Validation and Cleaning),edit checksare 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 fromback-end checksorprogrammed checks, which are typically run later in batch processes to identify data inconsistencies after entry.Manual checksare 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 theyprevent errors at the source, reducing the number of downstream data queries and cleaning cycles. They contribute significantly todata quality assurance,regulatory compliance, andefficiency 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 optimal method for collectingfrequent patient-reported pain datais throughelectronic Patient-Reported Outcomes (ePRO)with built-inreminder functionality.

According to theGCDMP (Chapter: Electronic Data Capture Systems), ePRO systems provide avalidated, real-time, and user-friendly interfacefor subjects to record time-sensitive data accurately. The use ofautomated remindersensures compliance with protocol-specified data collection times, improving data completeness and accuracy.

Paper diaries (option A) are prone torecall bias and backfilling, while daily site calls (option B) areresource-intensiveand introduce human error. IVRS systems (option C) are acceptable but less efficient and user-friendly than modern ePRO applications, which can integrate timestamp validation, compliance monitoring, and real-time alerts.

ePRO systems also comply withFDA 21 CFR Part 11andICH E6 (R2)for audit trails, authentication, and validation, making them the preferred solution for repeated PRO data collection.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture (EDC) Systems, Section 6.1 – Use of ePRO for Repeated Measures

FDA Guidance for Industry: Electronic Source Data in Clinical Investigations, Section 5 – ePRO Compliance and Validation

ICH E6 (R2) GCP, Section 5.5.3 – Electronic Data Systems and Recordkeeping

When adata inconsistencyarises — such as a record of “worsening of migraine” without prior documentation of a migraine episode — the Data Manager shouldquery the site for clarification(Option D).

According to theGCDMP (Chapter: Data Validation and Cleaning), data managers must raise aclarification querywhenever data appear incomplete, inconsistent, or ambiguous. The site must confirm whether “worsening of migraine” refers to anew eventor anexacerbation of a preexisting condition. This clarification ensures accurate safety reporting and appropriate medical coding (e.g., MedDRA classification).

Checking the medical history (Option C) may help but does not resolve the inconsistency. Assuming a relationship (Option A or B) without verification would violateGood Clinical Data Management Practiceand potentially misrepresent the adverse event.

Reference (CCDM-Verified Sources):

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

ICH E2A – Clinical Safety Data Management: Definitions and Standards for Expedited Reporting, Section II – Data Clarification Requirements

FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations – Data Query Management

The most significant difference in theData Manager’s rolewhen using anElectronic Data Capture (EDC)system is thatdata updates are implemented directly by site personnel(Option A).

According to theGCDMP (Chapter: Electronic Data Capture Systems), EDC technology shifts responsibility for data entry and correction from the sponsor or CRO to the investigator site, enabling real-time data entry and validation. This eliminates the need for double entry or remote data transcription, allowing Data Managers to focus onsystem validation, query management, and data quality oversightrather than physical data handling.

However, the EDC system still requires full validation (contrary to Option B). Metrics generation (Option C) and CRF tracking (Option D) are important but not unique to EDC-based workflows.

Thus, the correct answer isOption A – Data updates are implemented by the sites, reflecting the most fundamental operational shift introduced by EDC systems.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Electronic Data Capture (EDC) Systems, Section 4.1 – Role of the Data Manager in EDC

ICH E6 (R2) GCP, Section 5.5.3 – Electronic Data Entry and Responsibilities

FDA 21 CFR Part 11 – Electronic Records and Signatures: Data Entry Responsibilities

To improve efficiency and ensure consistency across multiple studies, the most effective infrastructure solution is tomaintain a centralized library of standardized forms or screen modules(e.g., CRF/eCRF templates).

According to theGood Clinical Data Management Practices (GCDMP, Chapter: Database Design and Build), using aform libraryallows reuse of validated data collection modules for commonly collected domains such as demographics, adverse events, and vital signs. This reduces database setup time, enhances uniformity in data definitions, and ensures alignment with standards such asCDISC CDASH and SDTM.

While adoptingODM (A)provides standardized data exchange and interoperability, it does not inherently reduce setup workload.Improving design processes (C)enhances efficiency but doesn’t guarantee consistency, andimplementing controlled terminology (D)helps with coding standardization, not database structure.

Therefore,option B—maintaining a library of form or screen modules— provides the most direct and sustainable improvement for scalability and quality.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.3 – Use of Standard Libraries and Templates

CDISC CDASH Implementation Guide, Section 3.2 – Reusable CRF Modules and Standardization

ICH E6(R2) GCP, Section 5.5.3 – Standardization and Reuse in Data Collection Systems

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

The best metric to identifymalfunctioning or ineffective edit checksis thecount by edit check of the number of times the check fired. This allows data managers to assess whether specific edit checks are performing as intended.

According to theGCDMP, Chapter: Data Validation and Cleaning, edit checks are programmed logic conditions that identify data inconsistencies or potential errors during data entry. A properly functioning edit check should trigger only when data falls outside acceptable or logical limits. If an edit check fires too frequently or not at all, it may indicate alogic errorin the check’s programming or configuration.

By analyzing counts by individual edit checks, data managers can:

Identify checks that never trigger (potentially inactive or incorrectly written),

Detect overactive checks (poorly designed parameters causing excessive false positives), and

Optimize system performance and review efficiency.

This metric supports continuous improvement in data validation logic and contributes to cleaner, higher-quality clinical databases.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Validation and Cleaning, Section 6.2 – Edit Check Design and Performance Metrics

FDA Guidance: Computerized Systems Used in Clinical Investigations – Section on Validation of Electronic Data Systems

When using acopyrighted or validated rating scale(e.g., Hamilton Depression Scale, Visual Analog Pain Scale), anymodification to the original instrument, including preprinting database codes on the CRF, must beapproved by the instrument’s owner or licensing authorityto ensure thevalidity and reliabilityof the instrument are not compromised.

According to theGCDMP (Chapter: CRF Design and Data Collection), validated rating scales are psychometrically tested tools. Any visual or structural modification (such as adding codes, changing layout, or rewording questions) can invalidate prior validation results. Therefore, the CRF designer mustconsult the independent source (copyright holder)for approval anddocument that the validity of the tool remains intact.

Merely consulting statisticians (option B) or verifying database alignment (option D) does not ensure compliance. Thus,Option Censures scientific and regulatory integrity.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: CRF Design and Data Collection, Section 6.1 – Use of Validated Instruments and Rating Scales

ICH E6 (R2) GCP, Section 5.5.3 – Validation of Instruments and Data Capture Tools

FDA Guidance for Industry: Patient-Reported Outcome Measures – Use in Medical Product Development to Support Labeling Claims, Section 4 – Instrument Modification and Validation