Page History

The logical model ofbetween of

Gloss
Space true t associations

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
Space true t concept

is Eachis represented by a row in the Concept file 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 clinical

Gloss
t concept.

 

Each

Gloss
Space true t concept

has two or more

Gloss
Space true t descriptions

associated Eachhas two or moreassociated with it:

• At least oneandone

  Gloss
  Space true t Fully Specified Name;

  and

• At least one

  Gloss
  t synonym.

Each

Gloss
Space true t description

is Eachis represented by a row in the  Description file 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
Space true t relationship,

from a source

Gloss
Space true t concept

to a destination

Gloss
Space true t concept,

is Eachfrom a sourceto a destinationis represented by a row in the  Relationship file. 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 that to 

Gloss
Space true t concept,

that is also held within the Concept file. The only concepts that can be used as the relationship typeId are

Concept

scg-expression

t 116680003|is

a| ShowFormat inline

or concepts that are subtypes of nospace

Scg expression
ShowFormat

Concept
t 410662002

|Concept

model

attribute|

.

The most basic form ofis the  Scg expressionShowPartstermShowFormatnospaceof

Gloss
Space true t relationship

is the 

Concept
t 116680003|is

a| ShowFormat inline

relationship. This relationship states that oneis one

Gloss
Space true t concept

is a subtype of another

Gloss
t concept

. Each subtype concept is connected to its parent subtype(s) by relationships with the typeId

Concept

scg-expression

t 116680003|is

a| ShowFormat inline

and this form the main SNOMED CT In thisamay CT 

Gloss
Space true t hierarchy.

In this

Gloss
Space true t hierarchy,

a

Gloss
Space true t child

Gloss
Space true t concept

may have more than one parent

Gloss
t concept

. The root of theis the

Gloss
Space true t hierarchy

is 

Concept
t 138875005 |SNOMED CT

Scg expression

ShowFormat	nospace

138875005 |SNOMED CT

Concept|

, which has a set of top leveleach forming its ownwith level

Gloss
Space true t children,

each forming its own

Gloss
Space true t sub-hierarchy.

Gloss
Space true t Relationships

with typeid values that are subtypes of 

Scg expression

Concept
t

ShowPartsterm

410662002

|Concept

model

attribute| ShowFormat inline

are referred to as attribute relationship and contribute to the formal definition of the source concept.

...