CCDM Practice Questions

User training and access management are fundamental to maintaining data integrity, security, and regulatory compliance in clinical trials. Actions are required whenever a user's relationship with the study or system changes. This includes onboarding new staff, reassigning roles, or offboarding staff. However, a software upgrade that has no impact on the user interface, system functionality, or workflow for end-users does not necessitate re-training or modifications to access rights. Since the users' interaction with the system remains identical, their existing training and access permissions remain appropriate.

A. When site staff leaves a study, their system access must be promptly revoked to prevent unauthorized access and ensure data security.

B. New site staff must receive documented training on the protocol and EDC system and be granted role-appropriate access before they can perform study duties.

D. Reassigning a team member to a different role requires a review and update of their access permissions to align with the principle of least privilege for their new responsibilities.

1. Society for Clinical Data Management. (2023). Good Clinical Data Management Practices (GCDMP®).

Section 4.6, "User Access and Security," states that a process must be in place to manage user access throughout the study lifecycle, including additions, changes, and deactivations. This directly supports the need for action in options A, B, and D.

Section 4.7, "Training," mandates that training be provided and documented for individuals based on their roles and responsibilities. A change in role (D) or a new user (B) explicitly requires training. A system upgrade that does impact users would also require training, but the question specifies one that does not.

2. U.S. Food and Drug Administration. (May 2007). Guidance for Industry: Computerized Systems Used in Clinical Investigations.

Section IV.C, "Personnel," states, "Persons who develop, maintain, or use computerized systems should have the education, training, and experience to perform their assigned tasks." This implies that training is tied to the tasks performed. If a system change does not alter the tasks (as in option C), additional training is not required. The guidance also emphasizes controls for security and access, which are relevant to options A, B, and D.

3. Nahm, M., et al. (2022). The Society for Clinical Data Management’s Good Clinical Data Management Practices, Version 2: A summary of changes. Therapeutic Innovation & Regulatory Science, 56(4), 506-515. https://doi.org/10.1007/s43441-022-00403-z

This publication, which reviews the updates to the GCDMP, reinforces the importance of lifecycle management for user accounts (p. 511). It highlights that access should be based on role and that procedures must be in place for "granting, changing, and revoking access," directly addressing the scenarios in A, B, and D as necessary actions.

A standardized data collection element is defined by its semantic and technical properties to ensure consistency and interoperability. These properties include an unambiguous definition (what it means), a standard set of permissible values (how to answer), and unique metadata for storage (variable name, data type). However, the physical positioning of the element on a Case Report Form (CRF) is a matter of form design and usability, not a core attribute of the data element's standard itself. The same standardized element can be placed in different locations on various CRFs across different studies while retaining its standardized meaning and structure.

A. An unambiguous definition is a fundamental requirement for standardization, ensuring all users understand and collect the data element in the same way.

C. A standard set of values (controlled terminology) is crucial for ensuring that responses are consistent, comparable, and ready for analysis.

D. Standardized metadata (e.g., variable name, data type) is essential for technical interoperability and mapping data from collection to analysis datasets like SDTM.

1. Society for Clinical Data Management (SCDM). (2023). Good Clinical Data Management Practices (GCDMP).

Section 5.2.2 Data Standards: This section details the components of data standards, emphasizing metadata, definitions, and controlled vocabularies. It does not mandate a specific layout or position on a form, focusing instead on the content and structure of the data itself.

2. Clinical Data Interchange Standards Consortium (CDISC). (2022). Clinical Data Acquisition Standards Harmonization (CDASH) Model v2.2.

Section 2.1, Goals of CDASH: The document states a primary goal is to provide a "standard way to collect data... that improves data quality and streamlines processes." It focuses on standardizing the data collection fields (elements) but explicitly notes that "CDASH does not prescribe a specific layout for CRFs." This confirms that positioning is not a required characteristic of the standard.

3. Kush, R. D., et al. (2007). Implementing the CDISC clinical data acquisition standards harmonization (CDASH) standard. Drug Information Journal, 41(3), 303-313.

DOI: https://doi.org/10.1177/009286150704100305

This article discusses the implementation of CDASH, highlighting that the standard provides a consistent set of global data collection fields (elements) with harmonized names, definitions, and metadata. The focus is on the content of the CRF, not its visual presentation or the specific location of fields.

The most effective method to identify sites with high subject attrition is to use a normalized, site-level metric. Option A, the proportion of patients with multiple missed visits by site, is the best choice. Using a proportion (or percentage) normalizes the data, allowing for a fair and accurate comparison between sites with different enrollment numbers. A raw count would be misleading, as a larger site is expected to have more dropouts. The criterion of "two visit periods have passed without data" serves as a standard operational proxy for a subject who is likely lost to follow-up, directly indicating attrition.

B. Number of late visits per site: This measures visit delinquency, not subject attrition. A raw number is also a poor metric for comparing sites of different sizes.

C. Proportion of late visits by site: While a proportion is better than a raw number, this metric still measures visit lateness, not subjects permanently leaving the study (attrition).

D. Number of patients for which two visit periods have passed without data: This is a study-level metric, not a site-level one. It provides a total count for the entire study and cannot be used to identify which specific sites are problematic.

1. Prokscha, S. (2017). Practical Guide to Clinical Data Management (3rd ed.). CRC Press. In Chapter 13, "Metrics, Reporting, and Study Closeout," the text emphasizes the importance of using rates and proportions for site performance metrics to allow for meaningful comparisons. It discusses tracking subject status, including dropouts, at the site level (pp. 265-267).

2. Society for Clinical Data Management. (2023). Good Clinical Data Management Practices (GCDMP). Section 6.5, "Centralized Monitoring," discusses the use of Key Risk Indicators (KRIs) to monitor site performance. Subject dropout rate per site is a critical KRI used to detect potential issues with site conduct or patient retention.

3. TransCelerate BioPharma Inc. (2020). Risk-Based Quality Management (RBQM) – Key Risk Indicators (KRIs) Library. This industry guidance document lists "Subject Discontinuation Rate" as a core KRI. It is defined as the percentage of subjects who discontinued, calculated per site, to identify sites with abnormally high rates compared to their peers. (Section: KRI Library, KRI ID: SD-01).

When using an Electronic Data Capture (EDC) system with the medical record as the source, the primary task for site personnel is transcribing data from the source to the EDC. If the medical record is electronic (EMR/EHR), which is common, staff must first be able to access it. This requires specific training on the medical records system to ensure they can log in, navigate, and locate the correct data while adhering to institutional security and privacy policies (e.g., HIPAA). This competency is a fundamental prerequisite for performing the data entry task itself. Without the ability to access the source, no data can be entered into the EDC.

A. Screening study subjects is a clinical procedure that occurs before data entry and is not a competency related to the use of the EDC system.

B. Using ePRO (electronic Patient-Reported Outcome) devices is a separate data collection method; the question specifies the medical record as the source.

C. Resolving discrepant data is a standard data management activity in any study using EDC, not a competency uniquely necessary because the source is a medical record.

1. Society for Clinical Data Management. (2023). Good Clinical Data Management Practices (GCDMP). Section 4.3.2, "Training," specifies that site personnel must be trained on all electronic systems used in the conduct of a clinical trial. This includes both the EDC system and any electronic source data systems, such as an EMR/EHR.

2. U.S. Food and Drug Administration. (2018). Use of Electronic Health Record Data in Clinical Investigations: Guidance for Industry. Section IV.A, "Ensuring the Quality, Reliability, and Integrity of EHR Data," states that sponsors should ensure sites have "procedures to ensure that only authorized individuals can access, create, or modify EHRs," which necessitates training on system access.

3. Løvestam, E., et al. (2017). Sourcing clinical trial data from electronic health records: a qualitative study of the process and its implications. BMC Medical Informatics and Decision Making, 17(1), 14. https://doi.org/10.1186/s12911-017-0413-y. The study highlights that a key challenge is the "need for training and support for the research nurses in how to find the data in the EHR," confirming that system access and navigation is a critical competency.

A Data Transfer Agreement (DTA), also known as a Data Transfer Specification (DTS), is the formal document created specifically to govern the transfer of data from an external vendor to the sponsor or CRO. This document precisely defines the operational details, including the transfer schedule and frequency (when), the recipients and contact points (to whom), and the technical specifications such as file format, transfer method, and security measures (in what manner). Its purpose is to ensure data is received in a consistent, timely, and usable format, making it the correct document for these details.

A. Project Plan: This document outlines the overall project scope, timelines, and resources, but lacks the granular, technical specifications of a data transfer.

B. Communication Plan: This governs the communication strategy among human stakeholders (e.g., meeting schedules, reporting lines), not the technical transfer of data files.

D. Data Management Plan (DMP): The DMP is a high-level document describing all data management activities. While it will state that vendor data will be transferred, it references the DTA/DTS for the specific operational details.

1. Society for Clinical Data Management (SCDM). (2023). Good Clinical Data Management Practices (GCDMP v2). Section 7.6, External Data Management, states, "Specifications for external data transfers should be documented. This documentation may be referred to as a Data Transfer Agreement (DTA), Data Transfer Specification (DTS), or External Data Vendor Specification... The specifications should include... data structure and format... transfer schedule... [and] method of data transfer."

2. Prokscha, S. (2012). Practical Guide to Clinical Data Management (3rd ed.). CRC Press. In Chapter 12, "External Data," the text explains that a "data transfer specification" or "data transfer agreement" is required to define "the file layout, the transfer frequency, the transfer medium, and the contacts for both the sending and the receiving party" (p. 215).

3. Rondel, R. K., Varley, S. A., & Webb, C. F. (Eds.). (2000). Clinical Data Management. John Wiley & Sons. Chapter 10, "External Data," emphasizes the need for a Data Transfer Specification that details the "frequency of data transfers," "data format," and "transfer mechanism" (pp. 133-134).

The most important reason for a data manager to review data before a monitor is to enhance the efficiency and effectiveness of the overall data cleaning and verification process. By performing a central review first, the data manager can use programmed edit checks and manual review to identify inconsistencies, outliers, and missing data across the entire study database. This allows discrepancies to be flagged (queried) in the system before the monitor conducts an on-site visit. The monitor can then focus their valuable on-site time on resolving these pre-identified issues with site staff and performing Source Data Verification (SDV), rather than discovering basic data entry errors that could have been caught centrally.

A. Data managers write the Data Management Plan that specifies the data cleaning workflow.

This is a statement of responsibility. While true, it describes what a data manager does (planning), not the strategic reason for the specific timing of the review.

C. Data managers have access to programming tools to identify discrepancies.

This describes a capability or tool used by data managers. It enables the pre-review but is not the fundamental reason why the pre-review is important for the workflow.

D. The GCDMP recommends that data managers review data prior to a monitor's review.

While this workflow aligns with the principles of Good Clinical Data Management Practices (GCDMP), the recommendation exists because of the operational benefit described in option B. Option B is the underlying reason for the best practice.

1. Society for Clinical Data Management (SCDM). (2019). Good Clinical Data Management Practices (GCDMP v2).

Section 5.5, Data Review and Query Management: This section details the ongoing process of data review performed by the data management team, which includes both automated and manual checks. It states, "Data review is an ongoing process that occurs from the first data received until database lock." This central, ongoing review logically precedes a monitor's periodic, on-site review to ensure efficiency. The central review identifies issues for the monitor to address during site visits.

2. Krishnankutty, B., Bellary, S., Kumar, N. B. R., & Moodahadu, L. S. (2012). Data management in clinical research: An overview. Indian journal of pharmacology, 44(2), 168–172.

Page 170, "Data validation" section: The article describes the process where "validation procedures... check the data for its completeness, consistency and accuracy." This is a core data management function. The text distinguishes this from the Clinical Research Associate's (monitor's) role of source data verification. A central data validation before the monitor's visit makes the monitor's subsequent verification more targeted and efficient.

DOI: https://doi.org/10.4103/0253-7613.93842

3. Gassman, J. J., et al. (2019). A guide to data management for clinical trials. In Clinical and translational science, 12(4), 326–333.

Page 329, "Data Cleaning" section: The authors describe data cleaning as an iterative process involving query generation. "Queries are typically generated by the data management/coordinating center and sent to the clinical sites for resolution." This central generation of queries by data management is the process that occurs before a monitor might visit the site to help resolve them and perform SDV.

DOI: https://doi.org/10.1111/cts.12635

To facilitate communication with clinical sites about pending work, the most effective tool is a clear, actionable list of what is outstanding. A list of outstanding (late/missing) data and unresolved queries provides site personnel with a specific "to-do" list. This allows them to efficiently locate and address the exact data points and queries requiring attention, which is a fundamental practice for ensuring data timeliness and quality in a clinical trial. This type of report is a standard component of site management and monitoring activities within clinical data management.

A. A list of entered and clean data shows completed work, not what is pending. It is a measure of progress, not an action list for outstanding issues.

B. A list of screened and enrolled subjects tracks recruitment metrics, not the status of clinical data entry or queries for those subjects.

C. A list of user account activity is used for auditing system access and security, not for identifying specific missing data or unresolved clinical queries.

1. Society for Clinical Data Management (SCDM). (2023). Good Clinical Data Management Practices (GCDMP). Section 6.6, "Query Management," outlines the process which includes tracking, managing, and resolving data discrepancies. Reporting on the status of queries (i.e., which are outstanding) is an integral part of this process for communication with sites.

2. Prokscha, S. (2011). Practical Guide to Clinical Data Management. CRC Press. Chapter 12, "Managing the Data Flow," discusses the use of status reports, such as missing pages reports and query status reports, which are provided to sites to monitor and prompt action on outstanding items (pp. 165-167).

3. Krishnankutty, B., Bellary, S., Kumar, N. B. R., & Moodahadu, L. S. (2012). Data management in clinical research: An overview. Indian Journal of Pharmacology, 44(2), 168–172. This article describes the data validation process, stating, "Discrepancy management is the process of resolving the errors... A list of discrepancies is generated and sent to the investigator for clarification." (p. 171). This directly supports providing lists of outstanding items. https://doi.org/10.4103/0253-7613.93842

To minimize transcription errors, data entry should be as direct as possible from the source document, eliminating the need for manual calculations by site personnel. Allowing staff to enter the lab value and select the corresponding unit as recorded in the source (Option B) achieves this. This method transfers the responsibility of unit conversion to a centralized, programmable, and verifiable system within the clinical database. This systematic approach is significantly less error-prone than relying on manual conversions performed at multiple international sites, which can introduce inconsistencies and calculation mistakes.

A. Deriving units from the value's magnitude is speculative and unreliable, as different units can have overlapping numerical ranges, leading to incorrect assumptions.

C. Forcing data entry into a standard unit requires site staff to perform manual conversions if the source unit differs, which is a primary source of error.

D. This is functionally the same as option C; mandating manual conversion by site staff before data entry significantly increases the risk of calculation errors.

1. Prokscha, S. (2011). Practical Guide to Clinical Data Management (3rd ed.). CRC Press. In Chapter 5, "Case Report Form Design," it is emphasized that CRFs should be designed to be clear and easy to complete. A key principle stated is, "Avoid asking the site to perform calculations, such as calculating a patient’s age from the date of birth or converting pounds to kilograms" (p. 68). This directly supports capturing the original value and unit without on-site conversion.

2. Society for Clinical Data Management (SCDM). (2023). Good Clinical Data Management Practices (GCDMP). The principles of quality data collection emphasize capturing data accurately as it appears in the source. Section 4.6, "CRF/eCRF Design," highlights the need for "clear and unambiguous" forms. Forcing on-site conversion (Options C and D) introduces ambiguity and potential for error, while allowing entry of the original value and unit (Option B) is a clearer, more direct method of transcription.

3. Clinical Data Interchange Standards Consortium (CDISC). (2023). Study Data Tabulation Model Implementation Guide for Human Clinical Trials (SDTMIG) v4.0. The SDTM model design inherently supports this best practice. It specifies variables for the original result and unit (--ORRES, --ORRESU) and separate variables for the standardized result and unit (--STRESC, --STRESU). This structure is built on the premise that original data is collected first and then standardized centrally (p. 118, Section 4.1.5.3, Standard Test Results).

The first and most fundamental step when importing external data is to verify that the incoming files are conformant to the pre-agreed Data Transfer Specification (DTS) or Data Transfer Agreement (DTA). This structural check ensures the file format, naming convention, column headers, data types, and overall layout are correct. If a file fails this initial validation, it cannot be processed correctly, rendering subsequent checks on its content (such as record counts or data consistency) meaningless. This step acts as a gateway for all further data validation and integration activities.

A. Incoming files have the expected number of records: This is a content validity check that occurs only after the file's structure has been successfully verified and parsed.

C. Data in incoming files are consistent with existing data in the study database: This reconciliation step happens much later in the process, after the incoming file has passed both structural and internal validation checks.

D. Data in the incoming files are internally consistent: Running internal edit checks requires the system to first successfully read and understand the file, which is only possible if it conforms to the specification.

---

1. Society for Clinical Data Management. (2023). Good Clinical Data Management Practices (GCDMP). Section 7.4, "Data Transfer." This section emphasizes that a DTS must be established and that upon receipt, data files are checked for conformity to this specification as an initial step.

2. Prokscha, L. A. K. (2011). Practical Guide to Clinical Data Management. CRC Press. In Chapter 11, "Managing Laboratory Data," the process for handling external data is described as beginning with a check to ensure the received file "meets the specifications for file format and content" before it is loaded for further validation (p. 169).

3. Krishnankutty, B., Bellary, S., Kumar, N. B. R., & Moodahadu, L. S. (2012). Data management in clinical research: An overview. Indian journal of pharmacology, 44(2), 168–172. The article describes the data validation process, which logically begins with verifying the structure and format of data sources before proceeding to content-level checks. https://doi.org/10.4103/0253-7613.93842 (See section on "Data Validation").

A Data Management Plan (DMP) must prospectively define all data handling procedures to ensure consistency and quality. The best practice for managing self-evident corrections involves two key principles outlined in Good Clinical Data Management Practices (GCDMP). First, the specific types of changes that are permissible must be pre-defined in a set of conventions within the DMP. This prevents subjective or arbitrary changes. Second, because the Principal Investigator is ultimately responsible for all site data, any changes made centrally—even obvious ones—must be documented and communicated to the investigative site. This ensures transparency and maintains the investigator's oversight.

A. Making changes "without further documentation" violates core principles of traceability, transparency, and investigator oversight required by GCDMP.

B. Internal review is a good quality control step, but this statement omits the essential requirements of pre-defined conventions and communication to the site.

C. This negates the efficiency and purpose of a self-evident correction process, which is designed to handle obvious errors without unnecessarily burdening the site.

1. Society for Clinical Data Management. (2023). Good Clinical Data Management Practices (GCDMP v2).

Section 4.6.10, Data Review and Cleaning Procedures: This section specifies that the DMP must describe the procedures for data review, query generation, and management, including "any pre-approved data corrections that may be applied by the data manager." This supports the need for "listed conventions."

Section 5.4.4, Discrepancy Management: This section emphasizes that "Any changes made to the clinical data by the CDM team should be documented and communicated to the investigator," which supports the requirement to document changes to the investigative site.

2. Krishnankutty, B., Bellary, S., Kumar, N. B. R., & Moodahadu, L. S. (2012). Data management in clinical research: An overview. Indian journal of pharmacology, 44(2), 168–172.

Page 170, "Data validation/Data cleaning": The article states, "The data management plan or a separate data validation plan should describe the data validation activities in a clinical trial... Any discrepancies generated are resolved with the investigator." This highlights the principle of resolving data issues, including corrections, in communication with the investigator. https://doi.org/10.4103/0253-7613.93842

3. Tudur Smith, C., et al. (2012). The data management plan: a practical guide to documenting the management of data in a clinical study. Trials, 13(1), 1-7.

Section "Data checking, validation and error handling": The paper notes the importance of documenting procedures for handling data errors, stating, "The DMP should describe the procedures for checking and validating data... and the process for resolving any inconsistencies." This reinforces the need for a pre-specified process as described in option D. https://doi.org/10.1186/1745-6215-13-78