Updated Dec-2025 Exam Engine or PDF for the CCDM Tests Free Updated Today!
Ultimate Guide to Prepare CCDM with Accurate PDF Questions
SCDM CCDM Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 17
An organization conducts over fifty studies per year. Currently each study is specified and set-up from scratch. Which of the following organizational infrastructure options would streamline database set-up and study-to-study consistency?
- A. Implementing controlled terminology for adverse events
- B. Maintaining a library of form or screen modules
- C. Adopting an ODM compliant database system
- D. Improving the form or screen design process
Answer: B
Explanation:
To improve efficiency and ensure consistency across multiple studies, the most effective infrastructure solution is to maintain a centralized library of standardized forms or screen modules (e.g., CRF/eCRF templates).
According to the Good Clinical Data Management Practices (GCDMP, Chapter: Database Design and Build), using a form library allows 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 as CDISC CDASH and SDTM.
While adopting ODM (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, and implementing 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
NEW QUESTION # 18
Which document contains the details of when, to whom, and in what manner the vendor data will be sent?
- A. Data Management Plan
- B. Data Transfer Agreement
- C. Project Plan
- D. Communication Plan
Answer: B
Explanation:
A Data Transfer Agreement (DTA) defines the operational and technical details for transferring data between a sponsor and an external vendor (e.g., central lab, ECG vendor). It is a formalized, controlled document specifying what data will be sent, when transfers will occur, the transfer method, file structure, encryption or security protocols, and the recipients of the data.
The DTA is developed jointly by the sponsor and vendor before production data transfers begin. According to the GCDMP, Chapter on External Data Transfers, this agreement ensures both parties share a clear understanding of timing, responsibility, and data content to minimize errors and ensure regulatory compliance.
The Data Management Plan (DMP) outlines general data handling processes but does not capture the technical specifics of vendor data transfer logistics. The Project Plan (A) and Communication Plan (B) are broader operational tools and not specific to data transfer protocols.
Hence, option C (Data Transfer Agreement) is the correct answer, as it precisely governs the procedural and technical framework of vendor data exchange.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: External Data Transfers, Section 4.1 - Data Transfer Agreements and Specifications ICH E6(R2) Good Clinical Practice, Section 5.5 - Trial Management, Data Handling, and Record Keeping
NEW QUESTION # 19
Query rules were tested with test data for each logic condition within each rule. Which of the following types of testing was conducted?
- A. Black box testing
- B. User box testing
- C. White box testing
- D. T box testing
Answer: A
Explanation:
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
NEW QUESTION # 20
Electronic submission standards require that an individual subject's complete CRF should be provided as what type of file:
- A. Rich Text Format (.rtf)
- B. Portable Document Format (.pdf)
- C. Microsoft Word (.docx)
- D. Statistical Analysis System (.sas)
Answer: B
Explanation:
Electronic submission standards, as established by FDA, CDISC, and ICH, require that an individual subject's complete Case Report Form (CRF) be submitted as a Portable Document Format (.pdf) file. The PDF format is universally recognized and accepted because it ensures that the structure, format, and visual fidelity of the CRF are preserved exactly as originally designed, regardless of software or hardware environment.
According to the FDA Guidance for Industry: Providing Regulatory Submissions in Electronic Format (2006) and CDISC SDTM standards, sponsors must include a subject-level CRF in PDF form for each participant in the submission dataset. This requirement ensures that reviewers can trace data points from analysis datasets back to their source entries in the CRF, fulfilling the principles of data traceability and transparency.
The Good Clinical Data Management Practices (GCDMP) also support this requirement, emphasizing that CRF archiving should maintain readability and regulatory accessibility. Formats like RTF, DOCX, or SAS datasets are not acceptable substitutes for regulatory CRF submission because they may alter formatting, structure, or introduce modifiable content, violating FDA data integrity principles.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Archiving and Submission FDA Guidance for Industry: Providing Regulatory Submissions in Electronic Format, April 2006 CDISC SDTM Implementation Guide, Section 5.3 - CRF Representation and Traceability
NEW QUESTION # 21
In a study conducted using paper CRFs, a discrepancy is discovered in a CRF to database QC audit. What is the reason why this discrepancy would be considered an audit finding?
- A. Discrepancy not explained by the data quality control audit plan
- B. Discrepancy not explained by the protocol
- C. Discrepancy not explained by the data handling conventions
- D. Discrepancy not explained by the CRF completion guidelines
Answer: C
Explanation:
In a CRF-to-database quality control (QC) audit, auditors compare data recorded on the paper Case Report Form (CRF) with data entered in the electronic database. If discrepancies exist that cannot be explained by documented data handling conventions, they are classified as audit findings.
Per GCDMP (Chapter: Data Quality Assurance and Control), data handling conventions define acceptable data entry practices, transcription rules, and allowable transformations. These conventions ensure that CRF data are consistently interpreted and entered.
If a discrepancy deviates from these established rules, it indicates a process gap or error in data entry, validation, or training. Discrepancies justified by protocol design or CRF guidelines would not constitute findings.
Therefore, option C (Discrepancy not explained by the data handling conventions) correctly identifies the criterion for a true QC audit finding.
Reference (CCDM-Verified Sources):
SCDM GCDMP, Chapter: Data Quality Assurance and Control, Section 6.1 - Data Handling Conventions and QC Auditing ICH E6(R2) GCP, Section 5.1 - Quality Management and Documentation of Deviations FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.5 - Data Verification and Audit Findings
NEW QUESTION # 22
According to ICH E6, developing a Monitoring Plan is the responsibility of whom?
- A. Sponsor
- B. Data Manager
- C. Monitor
- D. CRO
Answer: A
Explanation:
According to ICH E6(R2) Good Clinical Practice (GCP), Section 5.18.1, the Sponsor is ultimately responsible for developing and implementing the Monitoring Plan.
The Monitoring Plan defines:
The extent and nature of monitoring (e.g., on-site, remote, risk-based).
The responsibilities of monitors.
The communication and escalation procedures for data quality and protocol compliance.
While the CRO (B) or Monitor (D) may perform monitoring activities under delegation, the Sponsor retains legal accountability for ensuring a compliant and effective plan is developed and maintained. The Data 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)
NEW QUESTION # 23
The result set from the query below would be which of the following?
SELECT * FROM patient WHERE medical_record_number > 9000
- A. Shorter or of equal length than the patient table
- B. Longer than the patient table
- C. Narrower than the patient table
- D. Wider than the patient table
Answer: A
Explanation:
In Structured Query Language (SQL), the WHERE clause is used to filter records based on specified criteria. The query retrieves all columns from the patient table (SELECT *) but only those rows where the medical_record_number value is greater than 9000.
This means:
The number of columns (fields) remains the same as the original table.
The number of rows (records) will be equal to or less than the number of rows in the patient table, depending on how many patients meet the filter condition.
Hence, the result set can only be shorter or equal in length compared to the original table. It cannot be longer, wider, or narrower, since no new rows or columns are created.
Therefore, option B - "Shorter or of equal length than the patient table" - is correct.
Reference (CCDM-Verified Sources):
SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 - Relational Database Queries and Filtering Logic ICH E6(R2) GCP, Section 5.5.3 - Data Retrieval, Filtering, and Storage Principles FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations, Section 6.4 - Query Logic and Record Subsetting
NEW QUESTION # 24
Which is the MOST appropriate flow for EDC set-up and implementation?
- A. Protocol finalized, Database created, Edit Checks created, Database tested, Sites trained
- B. Database created, Subjects enrolled, Database tested, Sites trained, Database released
- C. Database created, Database tested, Sites trained, Protocol finalized, Database released
- D. CRF "wire-frames" created, CRFs reviewed, CRFs printed, CRFs distributed to sites
Answer: A
Explanation:
The correct and compliant sequence for EDC system setup and implementation begins only after the study protocol is finalized, as all case report form (CRF) designs, database structures, and validation rules derive directly from the finalized protocol.
According to GCDMP (Chapter: EDC Systems Implementation), the proper order is:
Protocol finalized - defines endpoints and data requirements.
Database created - built according to the protocol and CRFs.
Edit checks created - programmed to validate data entry accuracy.
Database tested (UAT) - ensures functionality, integrity, and compliance.
Sites trained and system released - only then can data entry begin.
Option B follows this logical and regulatory-compliant sequence. Other options (A, C, D) are either paper-based workflows or violate GCP-compliant timelines (e.g., enrolling subjects before database validation).
Reference (CCDM-Verified Sources):
SCDM GCDMP, Chapter: Electronic Data Capture (EDC) Systems, Section 5.2 - System Setup and Implementation Flow ICH E6(R2) GCP, Section 5.5.3 - Computerized Systems Validation and User Training Before Use FDA 21 CFR Part 11 - Validation and System Release Requirements
NEW QUESTION # 25
A study budgeted forty hours allocated over the three months following first protocol draft for Data Management Plan (DMP) creation. If there is a problem with this approach, what is it?
- A. No time was allocated for maintenance of the DMP
- B. Forty hours is too little time to budget for DMP creation
- C. There is no problem with the approach
- D. Forty hours is too much time to budget for DMP creation
Answer: A
Explanation:
The main issue with this approach is that no time has been allocated for ongoing maintenance and updates of the Data Management Plan (DMP) throughout the study lifecycle.
According to the GCDMP (Chapter: Data Management Planning and Study Start-up), the DMP is a living document - it must be continuously maintained and updated as study procedures evolve, particularly after protocol amendments, database modifications, or changes in data validation or reconciliation procedures.
Budgeting only for initial creation (forty hours) over three months ignores the substantial effort required for DMP version control, stakeholder communication, and mid-study updates. These updates are mandatory to maintain compliance with ICH E6 (R2) GCP Section 5.5.3, which requires that all procedural documentation accurately reflect current practices.
Thus, the problem is not the time allocated for creation but the lack of planning for ongoing maintenance.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Data Management Plan (DMP), Section 5.3 - DMP Maintenance and Version Control ICH E6 (R2) Good Clinical Practice, Section 5.5.3 - Documentation of Data Handling Procedures FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations - Section on Documentation Updates
NEW QUESTION # 26
A protocol is updated mid-study to add an additional procedure about which data needs to be collected. Which of these statements applies?
- A. The DMP does not need to be updated until the end of the trial and all updates are included in the DMP to indicate what happened in the trial
- B. The DMP does not need to be updated as it represents the data at the beginning of the trial only
- C. The DMP should be updated to reflect the changes to the protocol and stakeholders notified
- D. The DMP should be updated to reflect the changes to the protocol, but this update does not need to be communicated
Answer: C
Explanation:
When a protocol is amended mid-study, resulting in additional data collection requirements, the Data Management Plan (DMP) must be updated accordingly and all relevant stakeholders must be notified.
According to the GCDMP (Chapter: Data Management Planning and Study Start-up), the DMP is a living document that defines all data management processes for a clinical study. It must accurately reflect the current 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 B is 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
NEW QUESTION # 27
Which is a minimum prerequisite that should be in place before choosing an EDC system?
- A. Knowledge of functional requirements
- B. Completed installation qualification
- C. Updated governance documentation
- D. Draft validation plan
Answer: A
Explanation:
Before selecting an Electronic Data Capture (EDC) system for a clinical trial, it is essential to have a clear understanding of the functional requirements. This serves as the minimum prerequisite to guide system selection, ensuring that the EDC solution aligns with the protocol needs, data workflow, security requirements, and regulatory compliance.
According to the Good Clinical Data Management Practices (GCDMP, Chapter: Computerized Systems and Compliance), functional requirements describe what the system must do-such as data entry capabilities, edit checks, query management, user roles, audit trails, and integration with external systems (e.g., labs, ePRO). This understanding allows sponsors and CROs to evaluate vendor systems effectively during the selection and qualification phase.
Other options:
B . Installation qualification and D. Validation plan occur after system selection.
C . Governance documentation supports operations but is not required before choosing the system.
Hence, option A is correct - the first and most essential prerequisite before EDC selection is a solid understanding of the functional requirements.
Reference (CCDM-Verified Sources):
SCDM GCDMP, Chapter: Computerized Systems and Compliance, Section 4.2 - Requirements Gathering and System Selection FDA 21 CFR Part 11 - System Validation and Intended Use Requirements ICH E6(R2) GCP, Section 5.5.3 - Computerized System Selection and Qualification
NEW QUESTION # 28
In a cross-functional team meeting, a monitor mentions performing source data verification (SDV) on daily diary data entered by patients on mobile devices. Which of the following is the best response?
- A. Diary data to be source data verified should be randomly selected
- B. Diary data to be source data verified should be selected using a risk-based approach
- C. All diary data should be source data verified
- D. The diary data should not be source data verified
Answer: B
Explanation:
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)
NEW QUESTION # 29
What are the key deliverables for User Acceptance Testing?
- A. eCRF Completion Guidelines
- B. Project Plan
- C. Training
- D. Test Plan/Script/Results
Answer: D
Explanation:
The key deliverables for User Acceptance Testing (UAT) are the Test Plan, Test Scripts, and Test Results.
According to the GCDMP (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 under FDA 21 CFR Part 11 and ICH 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
NEW QUESTION # 30
Which information is most useful in working with sites to catch up a backlog of unresolved queries at sites?
- A. Graph and summary table of clean cases by site
- B. List of late queries by site and summary table
- C. Graph of expected versus actual enrollment
- D. Table of outstanding queries counts by site
Answer: B
Explanation:
The most effective information for addressing a backlog of unresolved queries at investigative sites is a list of late queries by site combined with a summary table.
According to the GCDMP (Chapter: Communication and Issue Escalation), timely and structured feedback to sites is critical for efficient query resolution. A detailed list of late or overdue queries, accompanied by summary statistics (e.g., counts, durations, status), enables data managers and monitors to prioritize follow-up actions, target problem areas, and provide focused support or retraining to underperforming sites.
While query count summaries (option B) are helpful for overview metrics, they lack the specific information (query ID, date, field, status) required for targeted follow-up. Graphs of enrollment or clean cases (options A and C) are unrelated to discrepancy resolution performance.
Thus, the combination of detailed lists and summarized performance metrics offers both granularity and a high-level overview - the optimal tool for query management communication.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Communication and Issue Escalation, Section 5.1 - Site Query Management Reports ICH E6 (R2) GCP, Section 5.18.4 - Communication Between Monitors and Sites FDA Guidance for Industry: Oversight of Clinical Investigations - Risk-Based Monitoring, Section on Query Metrics and Site Performance Review
NEW QUESTION # 31
The Medical Dictionary for Regulatory Activities (MedDRA) structure is in which of the following hierarchical orders, from most specific to least specific?
- A. LLT, PT, HLT, HLGT, SOC
- B. LLT, HLGT, PT, HLT, SOC
- C. LLT, PT, HLGT, HLT, SOC
- D. LLT, HLGT, HLT, PT, SOC
Answer: A
Explanation:
The MedDRA (Medical Dictionary for Regulatory Activities) is a standardized medical terminology used for coding and analyzing adverse event (AE) and medical history data in clinical trials. Its hierarchical structure supports aggregation, analysis, and reporting across varying levels of medical specificity.
From most specific to least specific, the hierarchy is as follows:
Lowest Level Term (LLT): The most granular term, often reflecting the verbatim text reported by the investigator.
Preferred Term (PT): The standardized medical concept representing one or more LLTs describing the same condition.
High Level Term (HLT): A grouping of related PTs describing similar medical conditions.
High Level Group Term (HLGT): A broader grouping of related HLTs.
System Organ Class (SOC): The highest level of classification, grouping HLGTs by body system or etiology (e.g., cardiac disorders, infections).
Thus, the correct order - from most specific to least specific - is:
LLT → PT → HLT → HLGT → SOC, which corresponds to option D.
Reference (CCDM-Verified Sources):
SCDM GCDMP, Chapter: Medical Coding and Dictionaries, Section 5.2 - MedDRA Hierarchical Structure ICH M1 MedDRA Terminology Guide, Version 26.0 - Hierarchy Overview ICH E2B(R3) Guidelines - Clinical Safety Data Management
NEW QUESTION # 32
Which information should an auditee expect prior to an audit?
- A. Standard operating procedures
- B. Auditor's credentials and certification number
- C. Audit plan or agenda
- D. Corrective action requests
Answer: C
Explanation:
Prior to an audit, the auditee should expect to receive an audit plan or agenda, which outlines the scope, objectives, schedule, and logistics of the audit.
According to the GCDMP (Chapter: Quality Assurance and Audits), an audit plan ensures transparency, preparation, and efficient execution. It typically includes details such as:
The audit scope and objectives,
The audit team members,
Documents or processes to be reviewed, and
The audit schedule and timeframe.
This allows the auditee to prepare the necessary records, staff, and facilities. While the auditor's credentials (option A) may be shared informally, they are not a regulatory requirement. Corrective actions (option B) are outcomes of the audit, not pre-audit materials. Standard Operating Procedures (option C) may be requested during the audit but are not provided in advance.
Thus, Option D - Audit Plan or Agenda - is the correct and compliant answer.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Quality Assurance and Audits, Section 6.1 - Pre-Audit Planning and Communication ICH E6 (R2) Good Clinical Practice, Section 5.19.3 - Audit Procedures and Responsibilities FDA Guidance for Industry: Computerized Systems Used in Clinical Investigations - Section 8.1 - Audit Preparation and Planning
NEW QUESTION # 33
The serious adverse event (SAE) database should be reconciled against the clinical trial database prior to which occasion?
- A. Expedited safety reporting
- B. Database closure or locking
- C. Case report form data entry
- D. Database quality audit
Answer: B
Explanation:
SAE reconciliation must be completed before database lock or closure to ensure all safety data are consistent between the clinical database and the pharmacovigilance (safety) database.
According to the GCDMP (Chapter: Safety Data Handling and Reconciliation), SAE reconciliation involves verifying that all adverse events reported in the clinical trial database are also captured and accurately recorded in the safety system (and vice versa). This is essential to confirm that no SAE is missing, misclassified, or inconsistently dated or coded between the two systems.
Performing this reconciliation before database lock ensures that any discrepancies are corrected, and both databases reflect consistent, verified information for regulatory submission. Conducting this after closure (or only at audit time) would risk data inconsistencies in the final submission datasets.
Reference (CCDM-Verified Sources):
SCDM Good Clinical Data Management Practices (GCDMP), Chapter: SAE Reconciliation, Section 6.1 - Timing and Procedures for Reconciliation ICH E2A/E2F - Clinical Safety Data Management: Definitions and Standards FDA Guidance for Industry: E2A - Clinical Safety Data Management: Processing Standards for Safety Reports
NEW QUESTION # 34
A Data Manager receives an audit finding of three different instances of simultaneous log-ins to the EDC system by the same site user. This was observed at three different sites. Which of the following is the best long-term response to the audit finding?
- A. Requesting that the sites fire the offending users for a HIPAA violation and increasing the monitoring for the offending sites
- B. Refresher training for the offending users, re-communication of the binding nature of e-signatures to all users, routine monitoring for simultaneous log-ins from the same user
- C. Acquiring technical controls from the same or a different system vendor that prevent simultaneous log-ins from the same user
- D. Removing all access to the system until the situation is resolved
Answer: B
Explanation:
The best long-term corrective and preventive action (CAPA) in this situation is a combination of user re-training, communication, and routine monitoring - as described in Option B.
According to the GCDMP (Chapter: Electronic Data Capture Systems) and FDA 21 CFR Part 11, user credentials and electronic signatures in clinical systems are legally binding and must be used only by the assigned individual. Simultaneous log-ins under the same credentials often indicate credential sharing, a compliance violation that 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
NEW QUESTION # 35
A CRF was approved by the Sponsor and development of a clinical database has been started according to the data management plan. What is the next responsibility of the Data Manager?
- A. Prepare system requirements specification
- B. Plan the timelines to ensure a clinical database is ready before the first screening
- C. Prepare a data validation plan for the clinical database
- D. Prepare a communications plan
Answer: C
Explanation:
Once the Case Report Form (CRF) has been finalized and database development has begun, the next primary responsibility of the Data Manager is to prepare a Data Validation Plan (DVP) for the clinical database.
According to the GCDMP (Chapter: Database Design and Build), the DVP documents all planned validation procedures - including edit 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.
While system requirement specifications (option B) are prepared before database development begins, and timeline planning (option C) occurs during the study startup phase, the DVP is 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
NEW QUESTION # 36
An external organization has been hired to manage SAE follow-up for a large study. Which of the following would be used as guidance for exchange of the SAE data between the EDC system and the vendor's safety management system?
- A. Medical Document for Regulatory Activities
- B. Submission Data Tabulation Model
- C. Biomedical Research Domain Model
- D. Individual Case Safety Report
Answer: D
Explanation:
The Individual Case Safety Report (ICSR) is the standard format used globally for the exchange of Serious Adverse Event (SAE) data between clinical data management systems (EDC) and safety management systems.
According to ICH E2B(R3) and Good Clinical Data Management Practices (GCDMP, Chapter: Safety Data Management and SAE Reconciliation), the ICSR provides the data structure and content standards for 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 . SDTM is 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)
NEW QUESTION # 37
The best example of a protocol compliance edit check is:
- A. An edit check that fires when a visit date is outside the specified window
- B. An edit check that fires when a field is left blank
- C. An edit check that fires when a value is outside of the normal range for vital signs
- D. An edit check that fires when an invalid date is entered
Answer: A
Explanation:
A protocol compliance edit check is designed to ensure that the data collected adheres to the specific requirements defined in the study protocol, such as visit timing, procedure windows, and eligibility criteria.
The example in option 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 under GCDMP and ICH E6(R2).
Other options are examples of general data 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 A best represents a protocol 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
NEW QUESTION # 38
......
Pass SCDM With Actual4Cert Exam Dumps: https://pass4sure.actual4cert.com/CCDM-pass4sure-vce.html