Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. A VD may have these properties
    1. An Administrative record
    2. A definition
    3. A data type
    4. A relationship to another VD
    5. A unit of measure, especially quantitative results
    6. A Format template e.g., CDASH's dates, ADaM's SAS format, etc.
    7. A length descriptor, for character data type
  2. A VD may be either enumerated, described, or continuous
    1. Enumerated VD contains discrete values, e.g., {MILD, MODERATE, SEVERE}
    2. Described VD contains a description of what data values are permissible, e.g., LLT from MedDRA by MSSO
    3. Continuous VD contains awhose PV may be free text, with or without any nomenclature.
  3. A PV may belong to 1..n VD
    1. A Permissible Value may have a Value Meaning
      1. Representation of its value meaning is independent of, and shall not be constrained by, the representation of its corresponding value
    2. A Value Meaning may have 1:n representations, hence taking a unique form of PV
    3. For a Permissible Value to become a member of VD, use a start date
    4. To retire a Permissible Value from a VD, use an end date

Gliffy Diagram
bordertrue
displayNamecd-vd-pv-semantic
namecd-vd-pv-semantic
pagePin35

Gliffy Diagram
bordertrue
namevd-classes
pagePin1

...

  1. Does ADaM's parameter VLM have any relevance here?
  2. Is EVS onboard with managing subsets? In other words, must subsets need to have a unique identifier?
    However, for the BC Height the valid units of measure may only include two units, cm and in . CDISC 360 requires the instantiation of a codelist subset so that th e BC can reference a codelist , which includes only the Height BC units . This subs et will have an identifier such as a concept code.
  3. Do we treat different components of an external dictionary as separate described value domains? For example, MedDRA's LLT, HLGT, etc as separate DVD in the repository?
  4. The use case of SDTM variables having partially controlled values is weird. Any good suggestions?
  5. PV-to-PV relationship will be useful for VD with VD-to-VD relationship. Example: Mapping of RACEC to RACE, ADaM's variable pairs of numeric & text variables with values such as {0, 1} and {Y, N}. Does it make sense?