Search



Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The logical model of

Gloss
Spacetrue
tassociations
between the components in the release files are depicted in the following diagram. The component class represents columns present in all three component files. The individual classes (description, concept and relationship) only show the additional columns present in those files. The colored lines between descriptions and concepts and between relationships and concepts represent the link between the foreign keys (shown in bold) and the id of the concept. These provide the functional connections between components described in this document. The grey lines indicate additional links between columns that are populated with concept identifiers that provide enumerated values.



Each

Gloss
Spacetrue
tconcept
is represented by a row in the
Specref
RefTypefile
tConcept
 and the concept is identified by the id column in that row. There can be more than one row with the same id but with different effectiveTime values, in which case each of these rows represents a version of that same concept. Thus each row represents a version of a clinical
Gloss
tconcept.
 

Each

Gloss
Spacetrue
tconcept
has two or more
Gloss
Spacetrue
tdescriptions
associated with it:

  • At least one

    Gloss
    Spacetrue
    tFully Specified Name;
    and

  • At least one

    Gloss
    tsynonym.

Each

Gloss
Spacetrue
tdescription
is represented by a row in the 
Specref
RefTypefile
tDescription
 and is identified by the id column in that row. There can be more than one row with the same id but with different effectiveTime values, in which case each of these rows represents a version of that same description. Thus each row represents a version of a description. Each description applies to one concept to which it is linked by the conceptId. All versions of a description must relate to exactly the same identified concept (i.e. the conceptId must not change between versions).

Each

Gloss
Spacetrue
trelationship,
from a source
Gloss
Spacetrue
tconcept
to a destination
Gloss
Spacetrue
tconcept,
is represented by a row in the 
Specref
RefTypefile
tRelationship
. There can be more than one row with the same id but with different effectiveTime values, in which case each of these rows represents a version of that same relationship. Thus each row represents a version of a relationship. The source, destination and type each relationship are identified respectively by the sourceId, destinationId and typeId columns. All versions of a relationship must have the same sourceId, destinationId and typeId.  The typeId refers to 
Gloss
Spacetrue
tconcept,
that is also held within the
Specref
RefTypefile
tConcept
. The only concepts that can be used as the relationship typeId are
Concept
t116680003|is a|
ShowFormatinline
or concepts that are subtypes of
Concept
t410662002 |Concept model attribute|
.

The most basic form of

Gloss
Spacetrue
trelationship
is the 
Concept
t116680003|is a|
ShowFormatinline
relationship. This relationship states that one
Gloss
Spacetrue
tconcept
is a subtype of another
Gloss
tconcept
. Each subtype concept is connected to its parent subtype(s) by relationships with the typeId
Concept
t116680003|is a|
ShowFormatinline
and this form the main SNOMED CT 
Gloss
Spacetrue
thierarchy.
In this
Gloss
Spacetrue
thierarchy,
a
Gloss
Spacetrue
tchild
Gloss
Spacetrue
tconcept
may have more than one parent
Gloss
tconcept
. The root of the
Gloss
Spacetrue
thierarchy
is 
Concept
t138875005 |SNOMED CT Concept|
, which has a set of top level
Gloss
Spacetrue
tchildren,
each forming its own
Gloss
Spacetrue
tsub-hierarchy.
Gloss
Spacetrue
tRelationships
with typeid values that are subtypes of 
Concept
t410662002 |Concept model attribute|
ShowFormatinline
are referred to as attribute relationship and contribute to the formal definition of the source concept.