A study is collecting ePRO assessments as well as activity-monitoring data from a wearable device. Which data should be collected from the ePRO and activity-monitoring devices to synchronize the device data with the visit data entered by the site?
Answer(s): B
To synchronize data from electronic patient-reported outcomes (ePRO) and wearable activity- monitoring devices with site-entered visit data, both the study subject identifier and date/time are essential.According to the GCDMP (Chapter: Data Management Planning and Study Start-up), each dataset must contain key identifiers that allow for accurate data integration and temporal alignment. In studies involving multiple digital data sources, time-stamped subject identifiers are necessary to ensure that the device-generated data correspond to the correct subject and study visit. The subject identifier ensures data traceability and linkage to the appropriate participant, while date/time allows synchronization of device data (e.g., activity or physiological measurements) with the corresponding site-reported visit or event. Geo-spatial data (options C and D) are typically not relevant to study endpoints and pose unnecessary privacy risks under HIPAA and GDPR guidelines.
(CCDM-Verified Sources)SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Integration and eSource Data, Section 5.2 Data Alignment and Synchronization Principles FDA Guidance for Industry: Use of Electronic Health Record Data in Clinical Investigations, Section 4.2 Data Linking and SynchronizationICH E6 (R2) GCP, Section 5.5.3 Data Traceability and Integrity
During testing of an ePRO system, a test fails. Which information should be found in the validation documentation?
When a system validation test fails during Electronic Patient-Reported Outcome (ePRO) system testing, the validation documentation must record the expected results (what should have occurred) and the actual results (what occurred).According to the GCDMP (Chapter: Database Validation and Testing), proper system validation documentation ensures traceability, reproducibility, and compliance with FDA 21 CFR Part 11 and ICH E6 (R2). Each test case must include:Test objective,Preconditions,Test steps,Expected results,Actual results, andPass/fail status.If a test fails, this documentation provides the objective evidence necessary for deviation handling, issue resolution, and re-testing. While a separate root cause analysis may be performed later (option D), the validation record itself must focus on verifying outcomes against predefined expectations. Therefore, the correct answer is B Expected and actual results.
(CCDM-Verified Sources)SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Database Validation and Testing, Section 4.4 Documentation of Test ResultsFDA 21 CFR Part 11 Validation Requirements (Section 11.10(a)) ICH E6 (R2) GCP, Section 5.5.3 Computer System Validation and Documentation
Which of the following laboratory findings is a valid adverse event reported term that facilitates auto coding?
Answer(s): A
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)UnambiguousSingle-concept based, not a collection of resultsThus, option A (Elevated HDL) is correct, as it aligns with MedDRA's single-concept, standard terminology structure suitable for auto-coding.
(CCDM-Verified Sources)SCDM GCDMP, Chapter: Medical Coding and Dictionaries, Section 5.3 Auto-coding and Verbatim Term ManagementICH 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
To ensure data quality and efficient integration of data, which of the following best describes the main topic that should be covered in initial discussions with a vendor providing the external data?
Answer(s): C
In initial vendor discussions for external data integration (e.g., central lab, ECG, imaging vendors), the most critical and foundational topic is defining the acceptable record, field, and file formats. According to the GCDMP (Chapter: External Data Transfers and Integration), establishing the Data Transfer Specifications (DTS) early in the process ensures consistent structure, proper mapping, and compatibility between the vendor's system and the sponsor's database. These specifications define:Data structure (variable names, formats, delimiters)File naming conventionsFrequency of transfersMethods of secure data transmissionDiscussing formats first allows later alignment on data validation, quality metrics, and dictionary standards (which occur in subsequent stages). Without format agreement, all downstream processes risk misalignment, resulting in data incompatibility and rework.Thus, option C (Acceptable record, field, and file formats) correctly represents the foundational focus of initial vendor discussions for ensuring data quality and integration efficiency.
(CCDM-Verified Sources)SCDM GCDMP, Chapter: External Data Transfers and Integration, Section 4.1 Data Transfer Planning and Specification DevelopmentICH E6(R2) GCP, Section 5.5.3 Data Handling and System Validation FDA Guidance: Computerized Systems Used in Clinical Investigations, Section 6.3 Data Import and Format Control
Which of the following SOPs are required for management of an EDC system?
Answer(s): D
The most essential Standard Operating Procedure (SOP) for management of an Electronic Data Capture (EDC) system is Change Control.Per GCDMP (Chapter: Computerized Systems and Compliance) and FDA 21 CFR Part 11, any changes made to an EDC system--whether to software configuration, study database design, or system functionality--must follow a documented, validated, and auditable change control process. This ensures that:Modifications are properly authorized, tested, and approved before implementation.System validation remains intact.Data integrity, traceability, and regulatory compliance are maintained. While vendor management (A) and coding maintenance (C) have supporting SOPs, change control (D) is mandatory for any system handling regulated clinical data. Measurement of data quality (B) is important but not specifically tied to system management procedures.Thus, option D (Change control) is the correct answer.
(CCDM-Verified Sources)SCDM GCDMP, Chapter: Computerized Systems and Compliance, Section 5.3 Change Control and System MaintenanceFDA 21 CFR Part 11 Electronic Records and Electronic Signatures, Section 11.10(ak) ICH E6(R2) GCP, Section 5.5.3 Computerized Systems Validation and Change Documentation
Post your Comments and Discuss SCDM CCDM exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CCDM content, but please register or login to continue.