Member Annotation String Value Reference Set

Purpose

A Member Annotation Refset will be created to support annotations on members of any reference set(s).

The SNOMED CT International Release contains Annotations content in two reference sets:

  • The Member Annotation String Value reference set, in which annotations are held on members of any reference set(s).

  • The Component Annotation String Value reference set, in which annotations are assigned to any SNOMED CT component.

Note

These reference sets replace the previous Annotation Type reference set, which has now been deprecated:

Data Structure

A Member Annotation String Value reference set is structured as shown in the following table:

Field
Data type
Purpose
Mutable
PK

id

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.

NO

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

NO

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

NO

refsetId

SCTID

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

In this case, a subtype descendant of: 1292995002 |Member annotation with string value reference set (foundation metadata concept)|.

NO

NO

referencedComponentId

SCTID

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

The SNOMED CT component to which the Annotation applies.

NO

NO

referencedMemberId

UUID

The UUID of the relevant member of the reference set in SNOMED CT.

NO

NO

languageDialectCode

String

Specifies the language of the Annotation text using the two character ISO-639-1 code. Note that this specifies a language level only, not a country code. However, a dialect can also be included by following the standard RFC 5646, although this is an optional inclusion. The new concept 1304275002 |Language or dialect code (foundation metadata concept)| has been added for the metadata for this refset.

NOTE: This field should be blank wherever a language code is not applicable, but never NULL.

YES

NO

typeId

SCTID

Any descendant of 1295447006 |Annotation attribute (attribute)| minus 1295449009 |Additional relationship attribute (attribute)| and its descendant in the attribute hierarchy.

NO

NO

value

String

The Annotation text itself, with a maximum size of 32Kb, represented in UTF-8 encoding.

YES

NO

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


RF2 File naming convention

A Component Annotation String Value reference set should be named along the lines of the following convention:

  • der2_sscsRefset_MemberAnnotationStringValueSnapshot__[Product]_ __[date]_.txt

For example, for an International Release on 1st December 2023:

  • der2_sscsRefset_MemberAnnotationStringValueSnapshot_INT_20231201.txt

Descriptor Template 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) 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 table below shows the descriptors that define the structure of the 1292995002 |Member annotation with string value reference set (foundation metadata concept) | pattern and examples of the descriptors for specific reference sets that follow this pattern.

Descriptor templates for Member Annotation String Value reference sets

refsetId
referencedComponentId
attributeDescription
attributeType
attributeOrder

1292995002 |Member annotation with string value reference set (foundation metadata concept) |

900000000000460005 |Component type (foundation metadata concept)|

excluding the postcoordinated expression and rerfset member type components

0

1292995002 |Member annotation with string value reference set (foundation metadata concept) |

1296891007 |Annotated member (foundation metadata concept)|

900000000000464001 |Reference set member type component|

1

1292995002 |Member annotation with string value reference set (foundation metadata concept) |

1304275002 |Language or dialect code (foundation metadata concept)|

900000000000465000 |String (foundation metadata concept)|

2

1292995002 |Member annotation with string value reference set (foundation metadata concept) |

1296892000 |Annotation type (foundation metadata concept)|

900000000000461009 |Concept type component|

3

1292995002 |Member annotation with string value reference set (foundation metadata concept) |

900000000000519001 |Annotation value|

900000000000465000 |String (foundation metadata concept)|

4


Member Annotation String Value Reference Set Example

The same value of the referencedComponentId from an annotated refset is assigned in the annotation refset. For example, this OWL axiom has a referencedComponentId 91302008 |Sepsis (disorder)| in the OWL expression refset. The annotated text could indicate the intended annotation target is the OWL axiom though it is not referenced in referencedComponentId. This simplifies the query of annotations by referencedComponent.

id
effectiveTime
active
moduleId
refsetId
referencedComponentId
referencedMemberId
languageDiaiectCode
annotationTypeId
Annotation

00000000-1111-2222-3333-444444444444

20240131

1

1292995002 | Member annotation with string value reference set (foundation metadata concept) |

91302008 |Sepsis (disorder)|

3ddfb6d2-0874-4916-8767-8d48c781d435

en

|Change note (attribute)| (to be released)

In the third International Consensus Definitions for Sepsis and Septic Shock (Sepsis-3) published in 2016, the new definition eliminated the requirement for the presence of systemic inflammatory response syndrome (SIRS) to define sepsis. The sepsis is now logically defined as Organ dysfunction syndrome (disorder) with pathological process of disregulated host response due to infectious disease.


Last updated