Simple Map to SNOMED CT Reference Set

Purpose

A 1187636009 |Simple map to SNOMED CT type reference set| supports the representation of simple maps from values in other code systems to SNOMED CT concepts. No constraints are put on the number of SNOMED CT concepts mapping to by a particular code. However, this type of reference set is usually only appropriate where there is a close "one-to-one" mapping between the coded values in another code system and SNOMED CT concepts.

Data structure

A 1187636009 | Simple map to SNOMED CT type reference set| is a String Reference Set used to represent maps from codes in another terminology, classification or code system to SNOMED CT concepts. Its structure is shown in the following table.

Simple map to SNOMED CT 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 (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)

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: 1187636009 |Simple map to SNOMED CT type reference set|

referencedComponentId

SCTID

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

Refers to the SNOMED CT concept to which the mapSource is mapped (i.e. the map target).

mapSource

String

The equivalent code in the other terminology, classification or code system, from which the referencedComponentId is mapped.

YES

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

Metadata

The following metadata hierarchy supports this reference set:

Simple Map to SNOMED CT Reference Sets in the Metadata Hierarchy

900000000000454005 |Foundation metadata concept| 900000000000455006 |Reference set| 1187636009 |Simple map to SNOMED CT type 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.