The
| Specref |
|---|
| RefType | file |
|---|
| t | Relationship file |
|---|
|
holds oneper row. Eachis holds one | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
per row. Each | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
is of a particular type, and has a
sourceand a destinationAn example of ais given below:| Scg expression |
|---|
|
371883000|Outpatient procedure| |
| Scg expression |
|---|
|
116680003|Is a| |
| Scg expression |
|---|
|
71388002|Procedure| |
where:| Scg expression |
|---|
|
371883000|Outpatient procedure| |
is the source| Scg expression |
|---|
|
116680003|Is a| |
is theand;| Scg expression |
|---|
| ShowParts | term |
|---|
| ShowFormat | inline |
|---|
|
71388002|Procedure| |
is the destination
...
Field
...
Data type
...
Immutable
...
Purpose
...
id
...
SCTID
...
Y
...
...
effectiveTime
...
Time
...
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)
...
active
...
Boolean
...
N
...
Specifies whether the state of thewasorfrom the nominal release date specified by the effectiveTime field.
...
moduleId
...
SCTID
...
N
...
Identifies theversion's module. Set to aof
| Scg expression |
|---|
|
900000000000443000|Module| |
within the metadata...
sourceId
...
SCTID
...
Y
...
Identifies the sourceof theversion. That is thedefined by thisSet to theof ain the Concept File.
...
destinationId
...
SCTID
...
Y
...
Identifies thethat is the destination of theversion.
That is therepresenting the value of the attribute represented by the typeId column.
Set to theof ain 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 .
...
relationshipGroup
...
Integer
...
N
...
Groups togetherversions that are part of a logically associated relationshipGroup. Allrecords with the same relationshipGroup number and sourceId are grouped in this way.
...
typeId
...
SCTID
...
Y
...
Identifies thethat represent the defining attribute (or relationship type) represented by thisversion.
That is therepresenting the value of the attribute represented by the typeId column.
Set to theof ain the Concept File. The concept identified must be either
| Scg expression |
|---|
|
116680003|Is a| |
or a subtype of| Scg expression |
|---|
|
410662002|Concept model attribute| |
. The concepts that can be used as in the typeId column are formally defined as follows:| Scg expression |
|---|
| Border | ridge |
|---|
| ShowFormat | block |
|---|
|
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....
characteristicTypeId
...
SCTID
...
N
...
Aenumeration value that identifies the characteristic type of theversion (i.e. whether theversion is defining, qualifying, etc.) This field is set to aof
| Scg expression |
|---|
|
900000000000449001|Characteristic type| |
in the metadata....
modifierId
...
SCTID
...
N
...
Aenumeration value that identifies the type of(DL) restriction (some, all, etc.). Set to aof
| Scg expression |
|---|
|
900000000000450001|Modifier| |
in the metadata| Note |
|---|
Currently the only value used in this column is | Scg expression |
|---|
| 900000000000451002|Some| |
and thus in practical terms this column can be ignored. For further clarification please see notes on modifierId . |
...
NO
source
and a destination An example of a | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
is given below: | Concept |
|---|
| t | 371883000|Outpatient procedure| |
|---|
| ShowFormat | inline |
|---|
|
| Concept |
|---|
| t | 116680003|Is a| |
|---|
| ShowFormat | inline |
|---|
|
| Concept |
|---|
| t | 71388002|Procedure| |
|---|
| ShowFormat | inline |
|---|
|
where:| Concept |
|---|
| t | 371883000|Outpatient procedure| |
|---|
| ShowFormat | inline |
|---|
|
is the source | Concept |
|---|
| t | 116680003|Is a| |
|---|
| ShowFormat | inline |
|---|
|
is the | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship type |
|---|
|
and;| Concept |
|---|
| t | 71388002|Procedure| |
|---|
| ShowFormat | inline |
|---|
|
is the destination
| Bookmarked content insert |
|---|
| Start | filespec |
|---|
| Page | REUSE:Relationship File |
|---|
|
Only one
| Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
record Only onerecord 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 thefield the
field of this record is false ('0'), then
theisat the | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
is at that point in time. If
thefield the field is true ('1'), then there is
abetween theidentified by sourceId and destinationId.a | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
between the | Gloss |
|---|
| PreSpace | false |
|---|
| t | SNOMED CT concepts |
|---|
|
identified by and | Specref |
|---|
| RefType | field |
|---|
| t | destinationId |
|---|
|
.The
, | Specref |
|---|
| RefType | field |
|---|
| t | destinationId |
|---|
|
, | Specref |
|---|
| RefType | field |
|---|
| t | relationshipGroup |
|---|
|
, , characteristicTypeIdand 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
thefield the field set to false) and a new row with a new id will be appended.
The
| Specref |
|---|
| RefType | field |
|---|
| t | relationshipGroup |
|---|
|
field is used to
groupwith the same sourceId group | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationships |
|---|
|
with the same field into one or more logical sets.
Awith a relationshipGroup A | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationship |
|---|
|
with a | Specref |
|---|
| RefType | field |
|---|
| t | relationshipGroup |
|---|
|
field value of '0' is considered not to be grouped.
Allwith the same sourceId All | Gloss |
|---|
| PreSpace | false |
|---|
| t | relationships |
|---|
|
with the same and non-zero
| Specref |
|---|
| RefType | field |
|---|
| t | relationshipGroup |
|---|
|
are considered to be logically grouped.
The
| Specref |
|---|
| RefType | field |
|---|
| t | relationshipGroup |
|---|
|
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
Related Links