The holds one per row. Each is of a particular type, and has a source and a destination An example of a is given below: where:


Field

Data type

Purpose

Part of Primary Key

id

Uniquely identifies the

NO

YES (Full/ Snapshot) 

Specifies the inclusive date at which the component version's state became the then current valid state of the component

YES

YES (Full)

Optional (Snapshot) 

Specifies whether the state of the was or from the nominal release date specified by the field.

YES

NO

Identifies the version's module. Set to a of within the metadata

YES

NO

Identifies the source of the version. That is the defined by this Set to the of a in the Concept File.

NO

NO

Identifies the that is the destination of the version.

That is the representing the value of the attribute represented by the column.

Set to the of a in the Concept File.

Note that the values that can be applied to particular attributes are formally defined by the   SNOMED CT Machine Readable Concept Model .

NO

NO

Integer

Groups together versions that are part of a logically associated . All records with the same number and are grouped in this way.

YES

NO

Identifies the that represent the defining attribute (or relationship type) represented by this version.

That is the representing the value of the attribute represented by the column.

Set to the of a in the Concept File. The concept identified must be either or a subtype of . The concepts that can be used as in the typeId column are formally defined as follows:

116680003|is a| OR <410662002|concept model attribute|
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 enumeration value that identifies the characteristic type of the version (i.e. whether the version is defining, qualifying, etc.) This field is set to a of in the metadata .

YES

NO

A enumeration value that identifies the type of (DL) restriction (some, all, etc.). Set to a of in the metadata

Currently the only value used in this column is and thus in practical terms this column can be ignored. For further clarification please see notes on modifierId .


YES

NO

 

Only one record with the same id field will be current at any point in time. The current record will be the one with the most recent effectiveTime before or equal to the point in time under consideration.

If the field of this record is false ('0'), then the is at that point in time. If the field is true ('1'), then there is a between the identified by and .

The , , , , characteristicTypeIdand will not change between two rows with the same id, in other words they are immutable. Where a change is required to one of these fields, then the current row will be de-activated (by appending a row with the same id and the field set to false) and a new row with a new id will be appended.

The field is used to group with the same field into one or more logical sets. A with a field value of '0' is considered not to be grouped. All with the same and non-zero are considered to be logically grouped.

The field will be an unsigned , and will not be limited to a single digit value. There is no guarantee that they will be assigned sequentially, and the values will not be unique across

Related Links