Traceability from source to SDTM to ADaM
Synthetic data. Not submission-ready. Not a copy of official IG mapping tables. Licensed vocabularies are not republished here.
The problem
A reviewer, a medical monitor, or a future you will ask: “which source row produced this analysis value?” Official ADaM material puts weight on traceability back to SDTM, and SDTM in turn has to be reconcilable to the collected source (EDC, lab, FHIR, and so on). A warehouse that only keeps the latest derived table is not a clinical data pipeline.
A working example
For the synthetic study STUDY-SYN-001, a minimal identifier chain that survived the DuckDB examples:
| Layer | Identifier you can actually store | Example |
|---|---|---|
| Source / FHIR | resource or extract id | AE-001, Patient/SYN-001 |
| SDTM-shaped row | STUDYID, USUBJID, a domain, a sequence or source id | STUDY-SYN-001, SYN-001, AE, 1 |
| ADaM-shaped row | the subject key from ADSL plus a parameter or event key, plus a link back to the SDTM row(s) | SYN-001, a parameter, a reference to the AE / VS row |
Define-XML and reviewer guides are the official places a submission documents that chain. This site is not a Define-XML tutorial; official Define-XML materials live with CDISC data-exchange standards. If you never write a Define file, you can still keep the same joins in the warehouse: do not throw away source ids when you assign SDTM sequences.
A practical rule: every derived column has either (a) a source column it was copied from, or (b) a named derivation that lists its inputs. “We cleaned it in a notebook” is not (b).
The gotcha
Recomputing sequences on every load without a stored source id will retarget supplemental rows, query comments, and ADaM links. Sequences can be official, required, and still be a terrible only key.
Hashing a row and calling the hash “traceability” fails when two legitimate versions of the source exist (a query correction). Keep versions, or keep a load id, or both.
When not to use this
- Do not add fifty audit columns to every table without a consumer. Agree the chain with whoever has to defend the data.
- Do not claim “ADaM traceability” because a column happened to have the same name as an SDTM variable. Names can coincide while values were recalculated.
The identifier examples use the same synthetic subjects as the rest of this site. Traceability as a requirement is a public CDISC ADaM theme; official Define-XML and ADaM documents are linked, not quoted at length.