Page History
...
The remaining steps to do in the MDR are as follows:
- Proceed with building the remaining two permissible values
- Ensure each permissible value is part of the same concept
- Associate them to their respective codelists
- Assign the variables these codelists represent
The picture after stitching all these steps looks like this:
Notice, to the right on the picture, how the AESEV (C66769) codelist is associated to variables from 2 foundational standards? Therefore, at the physical layer, there are no ambiguations these variables in 2 datasets share the same semantic content, underscoring reusability.
In conclusion, ISO 11179 Part 3's concept region outlines a relationship that unifies concepts, terms, codelists, and semantics in a MDR. Though, in CDISC standards, it is rare to see multiple value domain sets having the same value meanings. This scenario is much more likely to exist in a pharma company. The ISO 3166 country code is a good example, which has multiple value domains. E.g., the long name for site management using a CTMS, the alpha-3 code for submission data specifically SDTM.DM.COUNTRY, etc.
References
| Anchor | ||||
|---|---|---|---|---|
|
...
Overview
Content Tools