Attribute Value Reference Set

Purpose

An 900000000000480006 | Attribute value type reference set| allows a value from a specified range to be associated with a component. This type of reference set can be used for a range of purposes where there is a requirement to provide additional information about particular concepts, descriptions or relationships. For example, an |Attribute value type reference set| is used to indicate the reason why a concept has been inactivated.

Data Structure

An Attribute value reference set is a component reference set used to apply a tagged value to a SNOMED CT component. Its structure is shown in the following table.

Attribute Value Reference Set - Data Structure

Field

Data type

Purpose

Mutable

PK*

UUID

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.

YES (Full/Snapshot)

effectiveTime

Time

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 (YYYYMM DD) 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)

active

Boolean

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

moduleId

SCTID

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

refsetId

SCTID

Identifies the reference set to which this reference set member belongs.

In this case, a subtype descendant of: 900000000000480006 |Attribute value type reference set|

referencedComponentId

SCTID

A reference to the SNOMED CT component to be included in the reference set.

valueId

SCTID

The tagged value applied to the referencedComponentId. A subtype of 900000000000491004 | Attribute value| .

YES

PK* indicates if the attribute is part of the primary key for that file/table.

Metadata

The metadata concepts shown below are examples of concepts that identify attribute value reference sets.

Attribute Value Reference Sets in the Metadata Hierarchy

900000000000454005 |Foundation metadata concept| 900000000000455006 |Reference set| 900000000000480006 |Attribute value type| 900000000000489007 |Concept inactivation indicator reference set| 900000000000490003 |Description inactivation indicator reference set| 900000000000547002 |Relationship inactivation indicator reference set| ^{_{< Not currently used}}

Note. Other attribute value reference sets exist but are not used to track component inactivation

Concept Inactivation Values (with usage notes referring to the International Release)

900000000001043018 |Concept inactivation value| 723277005 |Nonconformance to editorial policy component| ^{_{< New introduced 2017-07-31}} 900000000000482003 |Duplicate| 900000000000483008 |Outdated| 900000000000484002 |Ambiguous| 900000000000485001 |Erroneous| 900000000000486000 |Limited| 900000000000487009 |Moved elsewhere| 900000000000492006 |Pending move| ^{_{< NEVER used for descriptions in the International Release - may have been used in extensions}}

Description Inactivation Values (with usage notes referring to the International Release)

900000000001077011 |Description inactivation value| 723277005 |Nonconformance to editorial policy component| ^{_{< New introduced 2017-07-31}} 723278000 |Not semantically equivalent component| ^{_{< New introduced 2017-07-31}} 900000000000483008 |Outdated| 900000000000485001 |Erroneous| 900000000000495008 |Concept non-current| 900000000000486000 |Limited| ^{_{< NOT used for description inactivations after 2010-07-31}} 900000000000487009 |Moved elsewhere| ^_<^{_{NOT used for description inactivations before 2016-07-31 or after 2017-07-31}} 900000000000482003 |Duplicate| ^_<^{_{NOT used for description inactivations before 2016-07-31 or after 2017-07-31}} 900000000000494007 |Inappropriate| ^{_{< NOT used for description inactivations before 2008-07-31 or after 2017-07-31}} 900000000000492006 |Pending move| ^{_{< NEVER used for descriptions in the International Release - may have been used in extensions}}

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.