Page History
...
The following are expectations for how values in these variables will group records given their hierarchy. Jira
showSummary | false |
---|---|
server | Issue Tracker (JIRA) |
serverId | 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 |
key | TOBA-621 |
Metadataspec | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The optional grouping identifier variable --GRPID may be used in all domains based on the general observation classes. --GRPID identifies relationships between records within a USUBJID within a single domain and has no inherent meaning across subjects or across domains. Relationships between observations are defined by assigning the same unique character value to the --GRPID variable for sets of related observations. The values used for --GRPID can be any values the applicant chooses; however, if the applicant uses values with some embedded meaning (rather than arbitrary numbers), those values will be consistent. Jira
Using --GRPID in the general-observation class domains can reduce the number of records in the RELREC, SUPP--, and CO datasets, when those datasets represent relationships/associations for records or values to a "group" of general observation class records.
...