The
Specref |
---|
RefType | file |
---|
t | Relationship file |
---|
|
holds one
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationship |
---|
|
per row. Each
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationship |
---|
|
is of a particular type, and has a source
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | concept |
---|
|
and a destination
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | concept. |
---|
|
An example of a
Gloss |
---|
SpacePreSpace | truefalse |
---|
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 |
---|
SpacePreSpace | truefalse |
---|
t | relationship type |
---|
|
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | concept |
---|
|
and; Concept |
---|
t | 71388002|Procedure| |
---|
ShowFormat | inline |
---|
|
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 the
was or from the nominal release date specified by the effectiveTime field. ...
moduleId
...
SCTID
...
N
...
Identifies the
version's module. Set to a of Concept |
---|
t | 900000000000443000|Module| |
---|
ShowFormat | inline |
---|
|
within the metadata ...
sourceId
...
SCTID
...
Y
...
Identifies the source
of the version. That is the defined by this Set to the of a in the Concept File. ...
destinationId
...
SCTID
...
Y
...
Identifies the
that is the destination of the version. That is the
representing the value of the attribute represented by the typeId 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.
...
relationshipGroup
...
Integer
...
N
...
Groups together
versions that are part of a logically associated relationshipGroup. All records with the same relationshipGroup number and sourceId are grouped in this way. ...
typeId
...
SCTID
...
Y
...
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 typeId column. Set to the
of a in the Concept File. The concept identified must be either Concept |
---|
t | 116680003|Is a| |
---|
ShowFormat | inline |
---|
|
or a subtype of Concept |
---|
t | 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
...
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 Concept |
---|
t | 900000000000449001|Characteristic type| |
---|
ShowFormat | inline |
---|
|
in the metadata . ...
modifierId
...
SCTID
...
N
...
A
enumeration value that identifies the type of(DL) restriction (some, all, etc.). Set to aof Concept |
---|
t | 900000000000450001|Modifier| |
---|
ShowFormat | inline |
---|
|
in the metadata Note |
---|
Currently the only value used in this column is Concept |
---|
t | 900000000000451002|Some| |
---|
ShowFormat | inline |
---|
| and thus in practical terms this column can be ignored. For further clarification please see notes on modifierId. |
...
NO
Bookmarked content insert |
---|
Start | filespec |
---|
Page | REUSE:Relationship File |
---|
|
Only one
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
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | active |
---|
|
field of this record is false ('0'), then the
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationship |
---|
|
is
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | inactive |
---|
|
at that point in time. If the
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | active |
---|
|
field is true ('1'), then there is a
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationship |
---|
|
between the
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | SNOMED CT concepts |
---|
|
identified by
and
Specref |
---|
RefType | field |
---|
t | destinationId |
---|
|
.
The
,
Specref |
---|
RefType | field |
---|
t | destinationId |
---|
|
,
Specref |
---|
RefType | field |
---|
t | relationshipGroup |
---|
|
,
, 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
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | active |
---|
|
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 group
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationships |
---|
|
with the same
field into one or more logical sets. A
Gloss |
---|
SpacePreSpace | truefalse |
---|
t | relationship |
---|
|
with a
Specref |
---|
RefType | field |
---|
t | relationshipGroup |
---|
|
field value of '0' is considered not to be grouped. All
Gloss |
---|
SpacePreSpace | truefalse |
---|
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
...