Purpose
An 733619002 | Ordered component type reference set (foundation metadata concept)| allows a collection of componentsto be defined with a specified order. This type of reference retis therefore useful for creating ordered lists and to specify groups where the components that belong to the same group share the same order.
Data structure
An Ordered component reference setis an IntegerComponentreference setis used to represent ordered lists and alternative hierarchies. Its structure is shown in the following table.
Field | Data type | Purpose | Part of Primary Key | |
id | A 128 bit unsigned Integer, uniquely identifying this reference set member. Different versions of a reference set member share the same id but have different effectiveTime. This allows a reference set member to be modified or made inactive (i.e. removed from the active set) at a specified time.
| NO | YES (Full /Snapshot) | |
The inclusive date or time at which this version of the identified reference set member became the current version. Note: In distribution files the effectiveTime should follow the short ISO date format (YYYYMMDD) and should not include the hours, minutes, seconds or timezone indicator. The current version of this reference set member at time T is the version with the most recent effectiveTime prior to or equal to time T .
| YES | YES (Full) Optional (Snapshot) | ||
The state of the identified reference set member as at the specified effectiveTime . If active = 1 (true) the reference set member is part of the current version of the set, if active = 0 (false) the reference set member is not part of the current version of the set.
| YES | NO | ||
Identifies the SNOMED CT module that contains this reference set member as at the specified effectiveTime . The value must be a subtype of 900000000000443000 | Module (core metadata concept)| within the metadata hierarchy.
| YES | NO | ||
Identifies the reference set to which this reference set member belongs.
In this case, a subtype descendant of: 733619002 | Ordered component type reference set (foundation metadata concept)|
| NO | NO | ||
A reference to the SNOMED CT component to be included in the reference set.
| NO | NO | ||
Specifies the sort order of the list. The list is ordered by applying an ascending sort of the order value. The value of order =1 represents the highest priority. A value of '0' is not allowed. Duplicate values are permitted and the sort order between two members with the same order value is not defined. Note: The name "order" is a reserved word in some database environments. Please consider this when using this column. | YES | NO |
Metadata
The following metadata in the "Foundation metadata concept" hierarchysupports this reference set:
Reference Set Descriptor and Example Data
Notes on the tables used to show descriptors and examples
The reference set example tables on this page have been revised as follows to aid clarity and understanding:
- The first four columns which are present in all release files are not shown. The omitted columns (id, effectiveTime, active, moduleId) are used in the same way in all referenced sets to support identification, versioning and packaging. They do not directly affect the specific features of a particular reference set or reference set type.
- Reference set columns that contain SNOMED CT identifiers are expanded to show details of the concept or description referenced by that identifier. In some cases, the term is shown in the same column using the expression syntax, in other cases an additional column with a name suffix '_term' has been added. In the standard reference set files only the identifier is present in the column and there is no added column for the term. When using reference sets, the term and other details of the component are looked up from the relevant component release files.
Descriptor Template
The tables below show the descriptor that defines the structure of the
733619002
|
Ordered component type reference set|
pattern and an example of descriptor for a specific reference setthat follows this pattern.
refsetId | referencedComponentId | attributeDescription | attributeType | attributeOrder |
|---|---|---|---|---|
0 | ||||
1 |
Note: The table above omits 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 table above also shows the termfrom one of the descriptionsassociated with each of the identified concept. The release file only contains the identifier.
Ordered reference set example
refsetId | referencedComponentId (Referenced component) | order (Attribute order) |
|---|---|---|
| 733619002 | Fingers ordered component reference set | | 127053016 127053016 |Thumb| | 1 |
733619002 | Fingers ordered component reference set | |
| 2 |
733619002 | Fingers ordered component reference set | |
| 3 |
733619002 | Fingers ordered component reference set | |
| 4 |
733619002 | Fingers ordered component reference set | |
| 5 |
Feedback
Overview
Content Tools
Apps