Purpose
An 900000000000521006 | Association type reference set| represents a set of unordered associations of a particular type between components.
Data structure
An Association reference setis a Component reference setused to represent associations between component. Its structure is shown in the following table.
|
Field |
Data type |
Purpose |
|---|---|---|
|
A 128 bit unsigned Integer (data type), uniquely identifying this reference set member. Different versions of a reference set member share the same id (field) but have different effectiveTime (field). This allows a reference set member to be modified or made active (field) (i.e. removed from the active set) at a specified time. |
||
|
The inclusive date or time at which this version of the identified reference set memberbecame the current version. The current version of this reference set memberat time T is the version with the most recent effectiveTime (field) prior to or equal to time T . |
||
|
The state of the identified reference set memberas at the specified effectiveTime (field) . If active (field) = 1 (true) the reference set memberis part of the current version of the set, if active (field) = 0 (false) the reference set memberis not part of the current version of the set. |
||
|
Identifies the SNOMED CT modulethat contains this reference set memberas at the specified effectiveTime (field) . The value must be a subtypeof 900000000000443000 | Module (core metadata concept)| within the metadata hierarchy. |
||
|
Identifies the reference setto which this reference set memberbelongs. In this case, set to a subtypeof 900000000000521006 | Association type reference set| . This indicates the nature of the association between the source and target components. |
||
|
The identifier of the source componentof the association. |
||
|
The identifier of the target componentof the association. |
Metadata
The following metadata in the "Foundation metadata concept" hierarchysupports this reference set:
Notes on usage
Each member of a 900000000000522004 | Historical association| reference setrepresents a Reference from an inactive componentto other equivalent or related componentsthat were current in the Release Versionin which that componentwas inactivated.
Each 900000000000522004 | Historical association| reference setholds Relationshipsof a different nature between the components. The 900000000000522004 | Historical association| reference setcontains associations:
-
from each inactive descriptionto one or more other Descriptionsthat are current in the release Versionin which the descriptionwas inactivated;
-
from each inactive reference setfor which there is a current replacement to the replacement reference set;
-
from an inactive descriptionto a conceptthat is current in the Release Versionin which the descriptionwas inactivated, and which is correctly described by the Term of the inactive description;
-
From each inactive conceptto one or more conceptsthat replace it.
The componentidentified by the targetComponentId (field) must be an instance of the same class of componentas the componentidentified by the referencedComponentIdfor all |Historical association| reference setsapart from the |REFERS TO conceptassociation reference set|.
Within the |REFERS TO conceptassociation reference set|, the referenced ComponentId field must be a descriptionand the targetComponentIdmust be a concept.
The targetComponentId (field) is used differently in the |MOVED TO association reference set|. In this case, the targetComponentId (field) does not refer directly to a replacement component, but rather to the namespace to which the componentwas moved to. The targetComponentId (field) actually refers to the conceptthat represents the namespace. This approach is used since the organization sourcing the componentmay 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.
See also more further information about 4.2.3 Historical Association Reference Sets.
Descriptor template and examples
The tables below show examples of the descriptors for specific reference setsthat follow the 900000000000521006 | Association type reference set| pattern.
|
refsetId |
referencedComponentId (Referenced component) |
attributeDescription (Attribute description) |
attributeType (Attribute type) |
attributeOrder (Attribute order) |
|
|---|---|---|---|---|---|
|
0 |
|
||||
|
1 |
|
||||
|
|
|
|
|
|
|
|
refsetId |
referencedComponentId (Referenced component) |
attributeDescription (Attribute description) |
attributeType (Attribute type) |
attributeOrder (Attribute order) |
|
|
0 |
|
||||
|
1 |
|
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active (field), active (field). Additionally, to aid understanding, the tables above also show the termfrom one of the descriptionsassociated with each of the identified concept. The release file only contains the identifier.
Association reference set example
The following table holds example entries for the 370124000 | Replaced by| reference set.
|
refsetId |
referencedComponentId (Association source component) |
targetComponentId (Association target component) |
|---|---|---|
Note: The tables above omit the initial four columns of data present in the release file. These follow the standards versioning pattern id (field), effectiveTime (field), active (field), active (field). Additionally, to aid understanding, the tables above also show the termfrom one of the descriptionsassociated with each of the identified concept. The release file only contains the identifier.
Feedback
Overview
Content Tools
Apps