...
Each
is 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
...
Each
is 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
from a source
to a destination
is 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 is also held within the
Concept file. The only concepts that can be used as the relationship typeId are
Concept |
---|
t | 116680003|is a| |
---|
ShowFormat | inline |
---|
|
or concepts that are subtypes of
Concept |
---|
t | 410662002 |Concept model attribute| |
---|
|
.
...