Introduction to Clinical Data Management (CDM)

A: Governing principle: functional controls are verified by demonstrating intended behavior before downstream processes rely on them. In this scenario, UAT is meant to show that edit checks actually trigger as designed when data are entered. Reviewing documents or lock behavior happens after basic functionality is shown. Option B traps engineers who know documentation matters but misplace it ahead of functional verification.

A: Governing principle: derived data must be fully supported by collected source fields and consistent units. Here, the CRF design doesn’t provide the metric inputs required for the derivation shown. Assuming height exists elsewhere ignores form-level traceability. Option D catches engineers who expect cross-form reuse without checking design intent.

A: Governing principle: data integrity erodes primarily through unmanaged change, not physical wear. In CDM, schema changes without full impact assessment break traceability and reconstruction. Hardware environment matters, but it’s not the main driver here. Option D appeals to human factors but misses system-level degradation.

A: Governing principle: audit trails record change, they don’t judge correctness. If wrong data are entered and left untouched, the audit trail stays silent. The safeguard prevents hidden modification, not poor initial quality. Option B tempts engineers who confuse audit trail with backup controls.