Pass the SCDM Clinical Data Management CCDM Questions and answers with ExamsMirror

Thesite-work dimension of site performanceevaluates how efficiently sites manage and resolve data-related tasks — particularly query resolution, data entry, and correction timelines. Among the given metrics, themedian and range of time from query generation to resolution (D)directly measures the site’s responsiveness and data management efficiency.

According to theGCDMP (Chapter on Metrics and Performance Measurement), this indicator helps identify sites that delay query resolution, which can impact overall study timelines and data quality. Tracking this metric allows the data management team to proactively provide additional training or communication to underperforming sites.

Other options measure different aspects of project progress:

Areflects overall database closure speed.

BandCrelate to study startup and enrollment readiness, not ongoing data work.

Thus,option Daccurately represents asite performance timeliness metric, aligning with CCDM principles for operational performance measurement.

Reference (CCDM-Verified Sources):

SCDM Good Clinical Data Management Practices (GCDMP), Chapter: Metrics and Performance Management, Section 5.4 – Site Query Resolution Metrics

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

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

In arelational database structure, each record in a table is uniquely identified by aprimary key. In this case, theVITAL_SIGNStable uses acomposite primary keyconsisting of:

Patient Identifier,

Visit Number, and

Vital Signs Parameter Name.

This means each record represents aunique measurement of a specific parameter (e.g., blood pressure, pulse)for a patient at a specific visit.

When joiningPATIENT_DEMOGRAPHYandVITAL_SIGNStables on thepatient identifier, the result set will includeone record for every combination of patient, visit, and parameter— i.e.,one record per patient per visit per vital sign parameter.

Therefore,option Ccorrectly describes the expected number of records.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 – Primary and Foreign Key Relationships in Relational Models

CDISC SDTM Implementation Guide, Section 5.3 – Observation-Level Data Structures

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

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

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