Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

This section describes how the SDTM will be implemented to represent relationships between records within a datasetdomain, between records in different datasets, domains,

Jira
showSummaryfalse
serverIssue Tracker (JIRA)
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyTOBA-797
and between datasets. 

When applicable, variables IDVAR and IDVARVAL will represent variables variable and values value pairs used as record-level keys to merge/join records between datasets.

Jira
showSummaryfalse
serverIssue Tracker (JIRA)
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyTOBA-798
In such cases, variables represented in IDVAR may have values that are unique for:

  • Unique values for each Each observation within a dataset.

...

  • domain
  • Groups of observations within a domain

The uniqueness of values by observation or groups of observations can be used to represent relationships efficiently. In cases where values are unique to observations

...

, the variable represented in IDVAR will have values from collected data (e.g., --SPID,

...

--

...

RECID)

...

In such cases, IDVAR and IDVARVAL the names of variables and specific variable values which relate records by acting as

 The following are examples of variables that could be used in IDVAR:

...

, when possible. When this is not possible, variables with derived values may also be used (e.g., --SEQ

...

  1. When possible, the variable represented in IDVAR will have values from collected data 

...

, LNKID, --LNKGRP).

Pagenav