Laboratory Units: Preserve Original Results Before Standardizing
A clinical trial laboratory crosswalk for converting units, preserving source results and ranges, and separating missing metadata from assay comparability.

Category
Data integrity, system validation, interoperability, and operational controls.
A clinical trial laboratory crosswalk for converting units, preserving source results and ranges, and separating missing metadata from assay comparability.

Decide whether to accept or quarantine an ODM transfer by checking its version, schema, header, metadata dependencies and required audit information.

Map clinical outcome assessments to CDISC QRS domains, track SDTM version dependencies, pin controlled terminology packages, and separate supplement publication from usage rights.

How FDA's May 2026 CGM technical specifications link SDTM LB epochs, ADCGM phantom rows and ADCGMEN completeness variables, and what the SAP must lock first.

How clinical trial teams choose wearable non-wear rules, define valid days, and distinguish missing observations from intercurrent events.

Which endpoint data must be reconciled and evidenced before a clinical database lock, who signs each row, and how unlock and unblinding stay controlled.

How trial teams timestamp a withdrawal boundary, keep endpoint data already collected in an FDA-regulated database, and stop only the collection the participant has refused.

How data management teams query an endpoint discrepancy without supplying the answer, and what to do when the site confirms the original value.

Resolve eCOA and EDC participant, visit, and timestamp conflicts using prespecified cross-reference keys, visit-window rules, and originator change controls under ICH E6(R3) and EMA guidelines.

A practical framework for clinical development and quality teams to validate computerized systems capturing trial endpoints—distinguishing platform qualification from protocol configuration under FDA 2024 and EMA 2023 guidelines.
