The Relationship file holds one relationshipper row. Each relationshipis of a particular type, and has a source conceptand a destination concept.An example of a relationshipis given below: 371883000 | Outpatient procedure| 116680003 | Is a| 71388002 | Procedure| where:
-
371883000 | Outpatient procedure| is the source concept;
-
116680003 | Is a| is the relationship type concept and;
-
71388002 | Procedure| is the destination concept.
|
Field |
Data type |
Immutable |
Purpose |
Part of Primary Key |
|---|---|---|---|---|
|
id |
Y |
Uniquely identifies the relationship. |
YES (Full/Snapshot) | |
|
N |
Specifies the inclusive date at which the component version's state became the then current valid state of the component |
YES (Full) Optional (Snapshot) |
||
|
N |
Specifies whether the state of the relationshipwas activeor inactivefrom the nominal release date specified by the effectiveTime field. |
NO | ||
|
N |
Identifies the relationshipversion's module. Set to a childof 900000000000443000 | Module| within the metadata hierarchy. |
NO | ||
|
Y |
Identifies the source conceptof the relationshipversion. That is the conceptdefined by this relationship.Set to the identifierof a concept.in the Concept File. |
NO | ||
|
Y |
Identifies the conceptthat is the destination of the relationshipversion. That is the conceptrepresenting the value of the attribute represented by the typeId column. Set to the identifierof a concept.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 | ||
|
N |
Groups together relationshipversions that are part of a logically associated relationshipGroup. All active Relationshiprecords with the same relationshipGroup number and sourceId are grouped in this way. |
NO | ||
|
Y |
Identifies the conceptthat represent the defining attribute (or relationship type) represented by this relationshipversion. That is the conceptrepresenting the value of the attribute represented by the typeId column. Set to the identifierof a conceptin the Concept File. The concept identified must be either 116680003 | Is a| or a subtype of 410662002 | Concept model attribute| . The concepts that can be used as in the typeId column 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 | ||
|
N |
A conceptenumeration value that identifies the characteristic type of the relationshipversion (i.e. whether the relationshipversion is defining, qualifying, etc.) This field is set to a descendantof 900000000000449001 | Characteristic type| in the metadata hierarchy. |
NO | ||
|
N |
Aconceptenumeration value that identifies the type ofDescription Logic(DL) restriction (some, all, etc.). Set to achildof 900000000000450001 | Modifier| in the metadatahierarchy. Currently the only value used in this column is 900000000000451002 | Some| and thus in practical terms this column can be ignored. For further clarification please see notes on modifierId. |
NO
|
Only one relationshiprecord 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 activefield of this record is false ('0'), then the relationshipis inactiveat that point in time. If the activefield is true ('1'), then there is a relationshipbetween the SNOMED CT conceptsidentified by sourceId and destinationId.
The sourceId, destinationId, relationshipGroup, typeId, characteristicTypeIdand modifierId 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 activefield set to false) and a new row with a new id will be appended.
The relationshipGroup field is used to group relationshipswith the same sourceId field into one or more logical sets. A relationshipwith a relationshipGroup field value of '0' is considered not to be grouped. All relationshipswith the same sourceId and non-zero relationshipGroup are considered to be logically grouped.
The relationshipGroup field will be an unsigned Integer, 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 concepts.
Related Links
Feedback
Overview
Content Tools
Apps