| Note |
|---|
| icon | false |
|---|
| title | Important Note |
|---|
|
Transitive Closure Files are not distributed in the SNOMED CT International Release
The two file structures documented here are intended as points of reference for those generating transitive closure table from the release data. SNOMED International provides a script file that can be used to generating the first of these structures generate the Snapshot Transitive Closure file from the snapshot version of the Relationship File.
|
The
| Gloss |
|---|
| SpacePreSpace | truefalse |
|---|
| t | Transitive Closure |
|---|
|
is the complete set of
| Gloss |
|---|
| SpacePreSpace | truefalse |
|---|
| t | relationships |
|---|
|
between every
| Gloss |
|---|
| SpacePreSpace | truefalse |
|---|
| t | concept |
|---|
|
and each of its super-type
, in other words both its parents and
.
A transitive closure table is one of the most efficient ways to test for subsumption between concepts.
Snapshot Transitive Closure File
SNOMED International provides an example of a Transitive Closure Perl script file (click to download) that can be used to generating a snapshot view of the transitive closure from the snapshot release of the . The output of this script conforms to the following following file structure. Note that the primary key for this table consists of both columns.bookmarker
...
...
Field
...
Data type
...
Purpose
...
subtypeId
...
...
Id of the
playing the role. Set to an of a ....
supertypeId
...
...
Id of the
playing the supertype role. Set to an of a ....
| CapId | transitive-closure-file-detailed-specification |
|---|
| CapType | Table |
|---|
|
Transitive Closure File - Detailed Specification |
| Bookmarked content insert |
|---|
| Start | filespec |
|---|
| Page | REUSE:Transitive Closure Snapshot File |
|---|
|
Versioned Transitive Closure
A versioned view of the
| Gloss |
|---|
| SpacePreSpace | truefalse |
|---|
| t | Transitive Closure |
|---|
|
can also be generated by combining the snapshot views for different effective times and removing redundant rows (e.g. where the transitive closure has not changed between release versions). The generated file could then be represented using the example specification below. Note that the unique key for this file would consist of the
subtypeId,
supertypeId and
effectiveTime.
...
Field
...
Data type
...
Purpose
...
subtypeId
...
...
Id of the
playing the role. Set to an of a ....
supertypeId
...
...
Id of the
playing the supertype role. Set to an of a ....
...
| Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
...
...
Specifies the inclusive date at which the
| Gloss |
|---|
| Space | true |
|---|
| t | transitive closure |
|---|
|
record was added or changed its active state....
...
| Specref |
|---|
| RefType | (data type) |
|---|
| t | Boolean |
|---|
|
...
Specifies whether at the
| Gloss |
|---|
| Space | true |
|---|
| t | transitive closure |
|---|
|
represented by the subtypeId and supertypeId became valid or invalid from the point in time specified by the | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
....
| Caption label |
|---|
| CapId | versioned-transitive-closure-file-example-specification |
|---|
| CapType | Table |
|---|
|
Versioned Transitive Closure File - Example Specification |
| Bookmarked content insert |
|---|
| Start | filespec |
|---|
| Page | REUSE:Transitive Closure File |
|---|
|
Related Links