Table: Concrete Value file - Detailed specification
Field | Data type | Purpose | Part of Primary Key | |
id | Uniquely identifies the relationship. | NO | YES (Full/ Snapshot) | |
Specifies the inclusive date at which the component version's state became the then current valid state of the component. Note: In distribution files the effectiveTime should follow the short ISO date format (YYYYMMDD) and should not include the hours, minutes, seconds or timezone indicator. | YES | YES (Full) Optional (Snapshot) | ||
Specifies whether the state of the relationship was active or inactive from the nominal release date specified by the effectiveTime field. | YES | NO | ||
Identifies the relationship version's module. Set to a child of 900000000000443000 | Module| within the metadata hierarchy. | YES | NO | ||
Identifies the source concept of the relationship version. That is the concept defined by this relationship. Set to the identifier of a concept. | NO | NO | ||
| String | Identifies the concrete value that is related to the relationship version. This could be an Integer, Decimal or String. Numbers are prefixed with a # (hash) symbol. Strings are surrounded with " (double quote) with double quotes inside the string escaped using \ (backslash). Note that the values that can be applied to particular attributes are formally defined by the SNOMED CT Machine Readable Concept Model. | NO | NO | |
Groups together relationship versions that are part of a logically associated relationshipGroup. All active Relationship records with the same relationshipGroup number and sourceId are grouped in this way. | YES | NO | ||
Identifies the concept that represent the defining attribute (or relationship type) represented by this relationship version. That is the concept representing the value of the attribute represented by the typeId column. Set to the identifier of a concept. The concept identified must be a subtype of 4762706009 | Concept model data attribute (attribute)| . The concepts that can be used as in the typeId column of the Concrete Value file are formally defined as follows: Note that the attributes that can be applied to particular concepts are formally defined by the SNOMED CT Machine Readable Concept Model. | NO | NO | ||
A concept enumeration value that identifies the characteristic type of the relationship version (i.e. whether the relationship version is defining, qualifying, etc.) This field is set to a descendant of 900000000000449001 | Characteristic type| in the metadata hierarchy. | YES | NO | ||
A concept enumeration value that identifies the type of Description Logic (DL) restriction (some, all, etc.). Set to a child of 900000000000450001 | Modifier| in the metadata hierarchy. | YES | NO |