...
An
| Gloss |
|---|
| Space | true |
|---|
| t | Association reference set |
|---|
|
is a
used to represent associations between
. Its structure is shown in the following table.
Field | Data type | Purpose |
|---|
id | UUID | A 128 bit unsigned Integer | Specref |
|---|
| RefType | (data type) |
|---|
| t | Integer |
|---|
|
, uniquely identifying this . Different versions of a reference set member share the same id but have different effectiveTime | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
. This allows a reference set member to be modified or made active (i.e. removed from the active set) at a specified time. |
effectiveTime | Time | The inclusive date or time at which this version of the identified | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
became the current version. The current version of this | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
at time T is the version with the most recent effectiveTime | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
prior to or equal to time T . |
| active | Boolean | The state of the identified | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
as at the specified effectiveTime | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
. If active = 1 (true) the | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
is part of the current version of the set, if active = 0 (false) the | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
is not part of the current version of the set. |
| moduleId | SCTID | Identifies the | Gloss |
|---|
| Space | true |
|---|
| t | SNOMED CT module |
|---|
|
that contains this | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
as at the specified effectiveTime | Specref |
|---|
| RefType | (field) |
|---|
| t | effectiveTime |
|---|
|
. The value must be a of | Concept |
|---|
| t | 900000000000443000|Module (core metadata concept)| |
|---|
| ShowFormat | inline |
|---|
|
within the metadata . |
| refsetId | SCTID | Identifies the to which this | Gloss |
|---|
| Space | true |
|---|
| t | reference set member |
|---|
|
belongs. In this case, set to a of | Concept |
|---|
| t | 900000000000521006|Association type reference set| |
|---|
|
. This indicates the nature of the association between the source and target . |
referencedComponentId | SCTID | The identifier of the source of the association. |
targetComponentId | SCTID | The identifier of the target of the association. |
...
The
identified by the
targetComponentId | Specref |
|---|
| RefType | (field) |
|---|
| t | targetComponentId |
|---|
|
must be an instance of the same class of
as the
identified by the referencedComponentIdfor all |Historical association|
apart from the |REFERS TO
association
|.
Within the |REFERS TO
association
|, the referenced ComponentId field must be a
and the targetComponentIdmust be a
.
The targetComponentId
| Specref |
|---|
| RefType | (field) |
|---|
| t | targetComponentId |
|---|
|
is used differently in the |MOVED TO association
|. In this case, the
targetComponentId | Specref |
|---|
| RefType | (field) |
|---|
| t | targetComponentId |
|---|
|
does not refer directly to a replacement
, but rather to the namespace to which the
was moved to. The
targetComponentId | Specref |
|---|
| RefType | (field) |
|---|
| t | targetComponentId |
|---|
|
actually refers to the
that represents the namespace. This approach is used since the organization sourcing the
may not always be able to determine the precise reference that is applicable in the receiving organization (namespace). Thus the responsibility for these references lies with the new responsible (receiving) organization.
...
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id
, effectiveTime , , active , , active , . Additionally, to aid understanding, the tables above also show the
from one of the
associated with each of the identified
. The release file only contains the
.
...
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id
, effectiveTime , , active , , active , . Additionally, to aid understanding, the tables above also show the
from one of the
associated with each of the identified
. The release file only contains the
.