All pages
Powered by GitBook
1 of 9

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Map Reference Sets

  • Simple Map from SNOMED CT Reference Set

  • Simple Map to SNOMED CT Reference Set

  • Complex and Extended Map from SNOMED CT Reference Sets

  • Map to SNOMED CT with Correlation and Origin Reference Set

Code to Expression Reference Set
Simple map with correlation from SNOMED CT type reference set
Simple map with correlation to SNOMED CT type reference set
Simple map with correlation from SNOMED CT to SNOMED CT type reference set
Provide Feedback

Simple map with correlation from SNOMED CT to SNOMED CT type Reference Set

Purpose

A 1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set (foundation metadata concept)| supports the representation of simple maps from SNOMED CT concepts to SNOMED CT concepts. No constraints are put on the number of SNOMED CT concepts to which each SNOMED CT concept is mapped.

Data structure

A |Simple map with correlation from SNOMED CT to SNOMED CT type reference set (foundation metadata concept)| is a Component - Component reference set used to represent maps from SNOMED CT concepts to SNOMED CT concepts. Its structure is shown in the following table.

Simple map with correlation from SNOMED CT to SNOMED CT type reference set - Data structure

Field
Data type
Purpose
Mutable
PK*

The following metadata hierarchy supports this reference set:

Simple map with correlation to |SNOMED CT type reference set (foundation metadata concept)| in the Metadata Hierarchy


The tables below show the descriptors that define examples of reference sets that follow the pattern.

Refset Descriptor rows for Simple Map with correlation from SNOMED CT to SNOMED CT Reference Set

refsetId
referencedComponentId (Referenced component)
attributeDescription (Attribute description)
attributeType (Attribute type)
attributeOrder (Attribute order)

Sample Content from a Simple Map with correlation from SNOMED CT to SNOMED CT Reference Set

refsetId
referencedComponentId (mapSource)
mapTarget

Simple map with correlation to SNOMED CT type Reference Set

Purpose

A 1193543008 |Simple map with correlation to SNOMED CT type reference set (foundation metadata concept)| 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 to which a particular code is mapped.

Data structure

A 1193543008 |Simple map with correlation to SNOMED CT type reference set (foundation metadata concept)| is a String - Component 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 with correlation to SNOMED CT type reference set - Data structure

Field
Data type
Purpose
Mutable
PK*

The following metadata hierarchy supports this reference set:

Simple map with correlation to SNOMED CT type reference set (foundation metadata concept)| in the Metadata Hierarchy


The tables below show the descriptors that define examples of reference sets that follow the pattern.

Refset Descriptor rows for Simple map with correlation to SNOMED CT type reference set

refsetId
referencedComponentId (Referenced component)
attributeDescription (Attribute description)
attributeType (Attribute type)
attributeOrder (Attribute order)

Sample Content from a Simple Map to SNOMED CT Reference Set

refsetId
referencedComponentId (mapSource)
mapSource

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 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:

NO

NO

referencedComponentId

SCTID

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

The SNOMED CT concept (mapSource) that is mapped to another SNOMED CT concept.

NO

NO

mapTarget

String

The SNOMED CT concept to which the referencedComponentId is mapped.

NO

NO

correlationId

SCTID

The correlation between the referencedComponentId (mapSource) and the mapTarget. Possible values are the following subtypes of :

YES

NO

0

1

2

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)

900000000000456007 |Reference set descriptor|

1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set|

900000000000500006 |Map source|

281000036105 |SNOMED CT-AU to INT substance mapping reference set|

1799011000036105 |amoxicillin (AU substance)|

372687004 |Amoxicillin (substance)|

281000036105 |SNOMED CT-AU to INT substance mapping reference set|

2442011000036104 |paracetamol (AU substance)|

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

Metadata

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 and examples

Refset Examples

900000000000454005 |Foundation metadata concept|
900000000000455006 |Reference set|
1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set
(foundation metadata concept)|
1187636009 |Simple map to SNOMED CT type reference set (foundation metadata concept)|
Provide Feedback

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 within the metadata hierarchy.

YES

NO

refsetId

SCTID

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

In this case, a subtype descendant of:

NO

NO

referencedComponentId

SCTID

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

The SNOMED CT concept to which the code in the other terminology or code system is mapped.

NO

NO

mapSource

String

The other-code which maps to the SNOMED CT concept.

NO

NO

correlationId

SCTID

The correlation from the other-code to the SNOMED CT concept. Possible values are the following subtypes of :

YES

NO

0

1

2

11205000

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)

900000000000456007 |Reference set descriptor|

1193543008 |Simple map with correlation to SNOMED CT type reference set|

900000000000505001 |Map target|

|EDQM to SNOMED CT pharmaceutical dose forms map with correlation|

66076007 |Conventional release chewable tablet (dose form)|

10228000

|EDQM to SNOMED CT pharmaceutical dose forms map with correlation|

385060002 |Prolonged-release oral tablet (dose form)|

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

Metadata

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 and examples

Simple Map Refset Examples

900000000000454005 |Foundation metadata concept|
900000000000455006 |Reference set|
1193543008 |Simple map with correlation to SNOMED CT type reference set (foundation
metadata concept)|
1187636009 |Simple map to SNOMED CT type reference set (foundation metadata concept)|
Provide Feedback

active

10226000

1193549007 |Narrow map source to broad map target|
  • 1193548004 |Exact match between map source and map target|

  • 1193547009 |Broad map source to narrow map target|

  • 900000000000443000 |Module (core metadata concept)|
    1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set (foundation metadata concept)|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    1193552004 |Map source to map target correlation not specified|
    1193551006 |Map source not mappable to map target|
    1193550007 |Partial overlap between map source and target|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set|
    900000000000505001 |Map target|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    1193544002 |Simple map with correlation from SNOMED CT to SNOMED CT type reference set|
    1193546000 |Map source to map target correlation|
    900000000000461009 |Concept type component|
    387517004 |Paracetamol (substance)|
    281000036105 |SNOMED CT-AU to INT substance mapping reference set|
    2571011000036104 |salbutamol (AU substance)|
    372897005 |Salbutamol (substance)|
    1193549007 |Narrow map source to broad map target|
  • 1193548004 |Exact match between map source and map target|

  • 1193547009 |Broad map source to narrow map target|

  • 900000000000443000 |Module (core metadata concept)|
    1193543008 |Simple map with correlation to SNOMED CT type reference set (foundation metadata concept)|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    1193552004 |Map source to map target correlation not specified|
    1193551006 |Map source not mappable to map target|
    1193550007 |Partial overlap between map source and target|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    1193543008 |Simple map with correlation to SNOMED CT type reference set|
    900000000000500006 |Map source|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    119354
    1193543008 |Simple map with correlation to SNOMED CT type reference set|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    900000000000461009 |Concept type component (foundation metadata concept)|
    |EDQM to SNOMED CT pharmaceutical dose forms map with correlation|
    385223009 |Powder for conventional release solution for injection (dose form)|

    Simple Map from SNOMED CT Reference Set

    Purpose

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

    Data structure

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

    Table: Simple map from SNOMED CT reference set - Data structure

    Field
    Data type
    Purpose
    Mutable
    PK*

    The following metadata hierarchy supports this reference set:

    Simple Map from SNOMED CT Reference Sets in the Metadata Hierarchy


    The tables below show the descriptors that define examples of reference sets that follow the pattern.

    Refset Descriptor rows

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from a Simple Map From SNOMED CT Reference Set

    refsetId
    referencedComponentId (mapSource)
    mapTarget

    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 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:

    NO

    NO

    referencedComponentId

    SCTID

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

    Refers to the SNOMED CT concept from which the mapTarget is mapped (i.e. the map source).

    NO

    NO

    mapTarget

    String

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

    YES

    NO

    0

    1

    L-55535

    F-D5972

    L-37904

    P1-18376

    DD-82950

    T-D8602

    T-F1102

    T-49723

    D9-12000

    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)

    900000000000456007 |Reference set descriptor|

    900000000000496009 |Simple map from SNOMED CT type reference set|

    900000000000500006 |Map source|

    900000000000498005 |SNOMED RT ID simple map|

    100005 |SNOMED RT Concept|

    G-3000

    900000000000498005 |SNOMED RT ID simple map|

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

    Metadata

    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 and examples

    Refset Examples

    900000000000454005
    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    900000000000496009 |Simple map from SNOMED CT|
    900000000000496009 |Simple map from SNOMED CT reference set|
    Provide Feedback

    active

    900000000000443000 |Module (core metadata concept)|
    900000000000496009 |Simple map from SNOMED CT type reference set|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    900000000000496009 |Simple map from SNOMED CT type reference set|
    900000000000505001 |Map target|
    900000000000465000 |String|
    101009 |Quilonia ethiopica|
    900000000000498005 |SNOMED RT ID simple map|
    102002 |Hemoglobin Okaloosa|
    900000000000498005 |SNOMED RT ID simple map|
    103007 |Squirrel fibroma virus|
    900000000000498005 |SNOMED RT ID simple map|
    104001 |Excision of lesion of patella|
    900000000000498005 |SNOMED RT ID simple map|
    105000 |Poisoning by pharmaceutical excipient|
    900000000000498005 |SNOMED RT ID simple map|
    106004 |Structure of posterior carpal region|
    900000000000498005 |SNOMED RT ID simple map|
    107008 |Structure of fetal part of placenta|
    900000000000498005 |SNOMED RT ID simple map|
    108003 |Entire condylar emissary vein|
    900000000000498005 |SNOMED RT ID simple map|
    109006 |Anxiety disorder of childhood OR adolescence|

    Simple map with correlation from SNOMED CT type Reference Set

    Purpose

    A 1193542003 |Simple map with correlation from SNOMED CT type reference set| supports the representation of simple maps from SNOMED CT concepts to values in other code systems. No constraints are put on the number of codes mapped from a single SNOMED CT concept.

    Data structure

    A 1193542003 |Simple map with correlation from SNOMED CT type reference set| is a String - Component reference set used to represent maps from SNOMED CT concepts to codes in another terminology, classification or code system, with the correlation between these codes. Its structure is shown in the following table.

    Simple map with correlation from SNOMED CT type reference set - Data structure

    Field
    Data type
    Purpose
    Mutable
    PK*

    The following metadata hierarchy supports this reference set:

    Simple map with correlation from SNOMED CT type reference sets in the Metadata Hierarchy


    The tables below show the descriptors that define examples of reference sets that follow the pattern.

    Refset Descriptor rows for Simple map with correlation from SNOMED CT type reference set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from a Simple map with correlation from SNOMED CT type reference set

    refsetId
    referencedComponentId (mapSource)
    mapTarget

    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 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:

    NO

    NO

    referencedComponentId

    SCTID

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

    The SNOMED CT concept that is mapped to the code in the other terminology or code system.

    NO

    NO

    mapTarget

    String

    The other-code to which the SNOMED CT concept is mapped.

    NO

    NO

    correlationId

    SCTID

    The correlation between the SNOMED CT concept and the other-code. Possible values are the following subtypes of :

    YES

    NO

    0

    1

    2

    11205000

    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)

    900000000000456007 |Reference set descriptor|

    1193542003 |Simple map with correlation from SNOMED CT type reference set|

    900000000000500006 |Map source|

    |SNOMED CT to EDQM pharmaceutical dose forms map with correlation|

    66076007 |Conventional release chewable tablet (dose form)|

    10228000

    |SNOMED CT to EDQM pharmaceutical dose forms map with correlation|

    385060002 |Prolonged-release oral tablet (dose form)|

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

    Metadata

    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 and examples

    Simple Map with Correlation Refset Examples

    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    1193542003 |Simple map with correlation from SNOMED CT type reference set|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    Provide Feedback

    active

    10226000

  • <

  • 900000000000443000 |Module (core metadata concept)|
    |Simple map with correlation from SNOMED CT type reference set (foundation metadata concept)|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    1193552004 |Map source to map target correlation not specified|
    1193551006 |Map source not mappable to map target|
    1193550007 |Partial overlap between map source and target|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    1193542003 |Simple map with correlation from SNOMED CT type reference set|
    900000000000505001 |Map target|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    1193542003 |Simple map with correlation from SNOMED CT type reference set|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    900000000000461009 |Concept type component (foundation metadata concept)|
    |SNOMED CT to EDQM pharmaceutical dose forms map with correlation|
    385223009 |Powder for conventional release solution for injection (dose form)|
    1193549007 |Narrow map source to broad map target|
    1193548004 |Exact match between map source and map target|
    1193547009 |Broad map source to narrow map target|
    447247004 |SNOMED CT source code to target map code correlation value|

    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*

    The following metadata hierarchy supports this reference set:

    Simple Map to SNOMED CT Reference Sets in the Metadata Hierarchy


    The tables below show the descriptors that define examples of reference sets that follow the pattern.

    Refset Descriptor rows for Simple map to SNOMED CT type reference set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from a Simple Map to SNOMED CT Reference Set

    refsetId
    referencedComponentId (mapTarget)
    mapSource

    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 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:

    NO

    NO

    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).

    NO

    NO

    mapSource

    String

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

    YES

    NO

    0

    1

    10058683

    10036000

    10068719

    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)

    900000000000456007 |Reference set descriptor|

    1187636009 |Simple map to SNOMED CT type reference set|

    900000000000505001 |Map target|

    1193497006 |MedDRA to SNOMED CT simple map reference set|

    131114008 |Decreased vitamin D|

    10078111

    1193497006 |MedDRA to SNOMED CT simple map reference set|

    702809001 |Drug reaction with eosinophilia and systemic symptoms|

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

    Metadata

    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 and examples

    Refset Examples

    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    1187636009 |Simple map to SNOMED CT type reference set|
    1187636009 |Simple map to SNOMED CT type reference set (foundation metadata concept)|
    Provide Feedback

    active

    10058899

    900000000000443000 |Module (core metadata concept)|
    1187636009 |Simple map to SNOMED CT type reference set|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    1187636009 |Simple map to SNOMED CT type reference set|
    900000000000500006 |Map source|
    900000000000465000 |String|
    1193497006 |MedDRA to SNOMED CT simple map reference set|
    95388000 |Injection site pain|
    1193497006 |MedDRA to SNOMED CT simple map reference set|
    410061008 |Intentional poisoning|
    1193497006 |MedDRA to SNOMED CT simple map reference set|
    55680006 |Drug overdose|

    Map to SNOMED CT with Correlation and Origin Reference Set

    Purpose

    The 705111002 |Map to SNOMED CT with correlation and origin type reference set| is used to meet the requirements for representation of maps from codes in another code system (other-codes) to a SNOMED CT concept, where the following requirements apply.

    1. A requirement to indicate the degree of correlation between the SNOMED CT concept and the other-codes.

    2. A requirement to indicate whether a concept or code was added to either code system as a result of the mapping process and, in this case, to indicate in which code system the concept or code originated.

    3. A requirement to represent the SNOMED CT attribute to which the other-code should be applied in order to capture the full specificity of the value represented by the other-code.

    4. No requirements for mapping rules or advice to be included with each map.

    Map to SNOMED CT with Correlation and Origin Reference Set - Data structure

    Field
    Data type
    Purpose
    Mutable
    PK*

    The following metadata hierarchy supports this reference set:

    Map to SNOMED CT with correlation and origin type reference set in the Metadata Hierarchy


    The tables below show the descriptors that define examples of reference sets that follow the pattern.

    Refset Descriptor rows for Map to SNOMED CT with correlation and origin type reference set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from a Map to SNOMED CT with correlation and origin type reference set

    refsetId
    referencedComponentId (mapTarget)
    mapSource
    attributeId
    correlationId
    contentOriginId

    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 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:

    NO

    NO

    referencedComponentId

    SCTID

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

    The SNOMED CT concept to which the code in the other terminology or code system is mapped.

    NO

    NO

    mapSource

    String

    The other-code which maps to the SNOMED CT concept specified as the referencedComponentId.

    NO

    NO

    attributeId

    SCTID

    A reference to the SNOMED CT concept representing the attribute to which the referencedComponentId (other-code) applies. In some cases, other-codes may be overloaded with a meaning that combines the meaning of a specific attribute with a value applied to it in the SNOMED CT concept model , in these cases accurate mapping needs to specify both aspects of the meaning. The attributeId provides effective disambiguation in these cases. Values of attributeId are restricted to subtypes of .

    YES

    NO

    correlationId

    SCTID

    The correlation from the other-code to the SNOMED CT concept. Possible values are the following subtypes of :

    YES

    NO

    contentOriginId

    SCTID

    An indication of whether the concept was initially in one of the terminologies (SNOMED CT or other-codes) and added to the other as part of mapping or was in both terminologies at the outset. Values are subtypes of .

    YES

    NO

    0

    1

    2

    3

    4

    TBC

    LP16246-8

    TBC

    LP148077-3

    TBC

    LP15149-5

    TBC

    LP14492-0

    TBC

    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

    900000000000456007 |Reference set descriptor|

    705111002 |Map to SNOMED CT with correlation and origin type reference set|

    900000000000505001 |Map target|

    705112009 | LOINC part to SNOMED CT map reference set|

    96257008 |Cathine (substance)|

    LP16063-7

    Data Structure

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

    Metadata

    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 and examples

    Refset Examples

    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    705111002 |Map to SNOMED CT with correlation and origin type reference set|
    1187636009 |Simple map to SNOMED CT type reference set (foundation metadata concept)|
    Provide Feedback

    YES (Full /Snapshot)

    Code to Expression Reference Set

    Purpose

    The 705109006 |Code to expression type reference set| is designed to enable associations between codes in another code system (other-codes) and SNOMED CT concepts, where the following constraints apply:

    1. Some of the other-codes cannot be mapped to an individual SNOMED CT concept.

    2. Licensing conditions (or other considerations) prevent addition of new SNOMED CT concepts to represent the same meaning as the other-codes.

    3. The other-codes can be logically defined using the SNOMED concept model to represent the same meaning (sufficiently defined) or a similar though less specific meaning (primitive).

    4. Other requirements similar for those applicable to mapping may also apply including:

      1. An indication of the degree of correlation between the other-code and the SNOMED CT expression.

      2. An indication of whether the other-code was created before any single concept representation of that meaning in SNOMED CT or whether the single concept representation in SNOMED CT predated the creation of the association.

    The general approach to the above requirements is to associate each of the other-codes with a representation of the same logic based definition as would have been applied to a SNOMED CT concept with that meaning. However, since the other-code are not identified by an SCTID, the logical definition cannot be represented using defining relationships. There are two potential approaches to this, one would be to use a general purpose description logic language (e.g. OWL) and the other is to use a SNOMED CT expression to represent each definition. The is designed to support the expression-based approach.

    Code to Expression Reference Set - Data structure

    Field
    Data type
    Purpose
    Mutable
    PK*

    The following metadata hierarchy supports this reference set:

    Code to Expression Reference Set in the Metadata Hierarchy


    The tables below show the descriptors that define examples of reference sets that follow the pattern.

    Refset Descriptor rows for a Code to Expression Reference Set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from a Code to Expression Type Reference Set

    refsetId
    referencedComponentId
    mapSource
    expression
    definitionStatusId
    correlationId
    contentOriginId

    900000000000443000 |Module (core metadata concept)|
    705111002 |Map to SNOMED CT with correlation and origin type reference set (foundation metadata concept)|
    1
    |Concept model attribute|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    1193552004 |Map source to map target correlation not specified|
    1193551006 |Map source not mappable to map target|
    1193550007 |Partial overlap between map source and target|
    1193549007 |Narrow map source to broad map target|
    1193548004 |Exact match between map source and map target|
    1193547009 |Broad map source to narrow map target|
    705116007 |Original code system source for linked content value|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705111002 |Map to SNOMED CT with correlation and origin type reference set|
    900000000000500006 |Map source|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    705111002 |Map to SNOMED CT with correlation and origin type reference set|
    734866006 |Concept attribute|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705111002 |Map to SNOMED CT with correlation and origin type reference set|
    1193546000 |Map source to map target correlation|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705111002 |Map to SNOMED CT with correlation and origin type reference set|
    705116007 |Original code system source for linked content value|
    900000000000461009 |Concept type component|
    704324001 |Process output|
    705119000 |Originally in both LOINC and SNOMED CT|
    705112009 | LOINC part to SNOMED CT map reference set|
    373500002 |Pheniramine (substance)|
    246093002 |Component|
    705119000 |Originally in both LOINC and SNOMED CT|
    705112009 | LOINC part to SNOMED CT map reference set|
    388067000 |Lactuca sativa specific immunoglobulin E|
    246093002 |Component|
    705119000 |Originally in both LOINC and SNOMED CT|
    705112009 | LOINC part to SNOMED CT map reference set|
    30326004 |Atrial natriuretic factor|
    246093002 |Component|
    705119000 |Originally in both LOINC and SNOMED CT|
    705112009 | LOINC part to SNOMED CT map reference set|
    95971004 |Urea nitrogen (substance)|
    246093002 |Component|
    705119000 |Originally in both LOINC and SNOMED CT|

    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 within the metadata hierarchy.

    YES

    NO

    refsetId

    SCTID

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

    In this case, a subtype descendant of:

    NO

    NO

    referencedComponentId

    SCTID

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

    A subtype of identifying the code system from which the code in the field is derived.

    • For example: .

    NO

    NO

    mapSource

    String

    The other-code which is mapped to the SNOMED CT expression.

    NO

    NO

    expression

    String

    A SNOMED CT expression that represents the meaning of the other-code. This expression may be a stated or inferred view of the definition provided that documentation of each identified reference set specifies the view provided.

    The expression must conform to the syntax defined in the .

    YES

    NO

    definitionStatusId

    SCTID

    Indicates whether or not the expression contains a sufficient definition of the other-code in the mapSource field. Possible values are the following subtypes of :

    YES

    NO

    correlationId

    SCTID

    The correlation between the other-code and the SNOMED CT expression. Possible values are the following subtypes of :

    YES

    NO

    contentOriginId

    SCTID

    Indication of whether the concept was initially in one of the terminologies (SNOMED CT or other-codes) and added to the other as part of mapping or was in both terminologies at the outset. Values are subtypes of .

    YES

    NO

    0

    1

    2

    3

    4

    5

    363787002:246093002=720113009,370134009=123029007,246501002=702675006,704327008=122592007,370132008=117363000,704319004=50863008,704318007=705057003

    51406-7

    363787002:704323007=123027009,704321009=718500008,704327008=122575003,704322002=64033007,704318007=118544000,370132008=30766002,704324001=706939009

    51406-7

    363787002:370134009=123029007,704327008=122592007,704318007=118556004,370132008=30766002,704319004=50863008,246093002=4546008

    59878-9

    363787002:370134009=123029007,704327008=258459007,704318007=118556004,246093002=273948005,370132008=30766002,704319004=31773000

    51921-5

    363787002:704318007=118539007,370134009=123029007,704326004=703765007,704327008=122592007,370132008=30766002,704319004=50863008,246093002=387067003

    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

    900000000000456007 |Reference set descriptor|

    705109006 |Code to expression type reference set|

    449608002 |Referenced component|

    705110001 |LOINC Term to Expression reference set|

    705114005 |LOINC Code System|

    Data Structure

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

    Metadata

    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 and examples

    Refset Examples

    |Code to expression type reference set|
    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    705109006 |Code to expression type reference set|
    705109006 |Code to expression type reference set (foundation metadata concept)|
    Provide Feedback

    YES (Full /Snapshot)

    48023-6

  • When these values are applied to this reference set type, the phrase "map source" refers to the other-code. and the "map target" refers to the SNOMED CT expression.

    900000000000443000 |Module (core metadata concept)|
    705109006 |Code to expression type reference set|
    705113004 |Terminology system|
    mapTarget
    705114005 |LOINC Code System|
    SNOMED CT Compositional Grammar - Specification and Guide
    900000000000444006 |Definition status|
    900000000000074008 |Not sufficiently defined by necessary conditions definition status|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    1193552004 |Map source to map target correlation not specified|
    1193551006 |Map source not mappable to map target|
    1193550007 |Partial overlap between map source and target|
    705116007 |Original code system source for linked content value|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705109006 |Code to expression type reference set|
    900000000000505001 |Map target|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    705109006 |Code to expression type reference set|
    706999006 |Expression|
    706999006 |Expression|
    900000000000456007 |Reference set descriptor|
    705109006 |Code to expression type reference set|
    734867002 |Expression definition status|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705109006 |Code to expression type reference set|
    447247004 |SNOMED CT source code to target map code correlation value|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    705109006 |Code to expression type reference set|
    705116007 |Original code system source for linked content value|
    900000000000461009 |Concept type component|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    447557004 |Exact match map from SNOMED CT source code to target code|
    705117003 |Originally in LOINC|
    705110001 |LOINC Term to Expression reference set|
    705114005 |LOINC Code System|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    447557004 |Exact match map from SNOMED CT source code to target code|
    705117003 |Originally in LOINC|
    705110001 |LOINC Term to Expression reference set|
    705114005 |LOINC Code System|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    447557004 |Exact match map from SNOMED CT source code to target code|
    705117003 |Originally in LOINC|
    705110001 |LOINC Term to Expression reference set|
    705114005 |LOINC Code System|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    447557004 |Exact match map from SNOMED CT source code to target code|
    705117003 |Originally in LOINC|
    705110001 |LOINC Term to Expression reference set|
    705114005 |LOINC Code System|
    900000000000073002 |Sufficiently defined by necessary conditions definition status|
    447557004 |Exact match map from SNOMED CT source code to target code|
    705117003 |Originally in LOINC|
    1193549007 |Narrow map source to broad map target|
    1193548004 |Exact match between map source and map target|
    1193547009 |Broad map source to narrow map target|

    Complex and Extended Map from SNOMED CT Reference Sets

    Purpose

    A 447250001 |Complex map from SNOMED CT type reference set| supports the representation of maps where each SNOMED CT concept may map to one or more codes in a target scheme. This type of reference set supports the general set of mapping data required to enable a target code to be selected at run-time from a number of alternate codes. It supports target code selection by accommodating the inclusion of machine readable rules and/or human readable advice. An 609331003 |Extended map from SNOMED CT type reference set| adds an additional field to allow the categorization of maps.

    Data structure

    A 447250001 |Complex map from SNOMED CT type reference set| is an Integer - Integer - String - String - String - Component reference set. The pattern is currently used for the map to ICD-9-CM. Its structure is as shown in the following table, with one exception - the table below includes an additional field (mapCategoryId) which is not used for this type of map.

    An 609331003 |Extended map type reference set (foundation metadata concept)| follows the same pattern but adds one additional column. It is an Integer - Integer - String - String - String - Component - Component reference set and this pattern is currently used for maps to ICD-10. Its structure is shown in the following table, and includes the mapCategoryId.

    Table: Complex and Extended map from SNOMED CT type reference sets - Data structures

    Field
    Data type
    Purpose
    Mutable
    PK*

    Values for are allocated on a sequential basis (for each refsetId and referencedComponentId combination) during authoring starting at 1. However, distributed mapGroup are not necessarily sequential, as some mapGroup may be created and removed during a mapping process between releases. For maps where each SNOMED CT concept only maps to at most one of a group of alternate target codes, the mapGroup field are usually be set to '1'.

    Values for will be allocated on a sequential basis (within each map group) starting from '1'. For maps that do not require run - time alternatives, the mapPriority field is set to '1'.

    The and fields enable run-time selection (within vendor's software) from a number of alternative map records within a mapGroup. Where there are no alternatives maps these columns of the release files will be empty (zero length string). Where alternative maps exist one or both of columns will be populated where relevant information is available.

    Where both fields are populated, and a vendor's system is capable of processing a machine readable rule, this should take priority over the human readable advice. Where neither field is populated, a vendor's system should allow the end-user to select the appropriate target code from the alternates.

    For more details on this topic in relation to the ICD-10 maps released as part of the SNOMED CT International Edition please see the .

    The specific grammar and content of the rules for resolving complex mapping cases depends on the nature of the target code system or classification. In general, each map is accompanied by a rule which is tested against other data and can be evaluated to return one of the following values:

    • True - in which case the map target applies;

    • False - in which case the map target does not apply;

    • Indeterminate - in cases where there is insufficient accessible data to determine whether the map target applies. In this case manual resolution of the map using the map advice provided will be required.

    The mapping rules assume access to a number of variables, that can be bound to appropriate attributes in the vendor's system information model. These include the age and gender of the patient and information about coexisting situations (e.g. records of other disorders, procedures or events in the same patient record).

    Detailed definitions of the mapping rules used forms part of individual specifications for maps to particular target code systems and classifications. This will initially be provided separately and will accompany the release of the relevant mapping files. For example, the set of rules used for mapping to ICD-10 are included in the .

    The following metadata supports this reference set:

    List: Complex and Extended Map from SNOMED CT References Sets in the Metadata Hierarchy


    The tables below examples of the descriptors for specific reference sets that follow the and patterns.

    Table: Refset Descriptor Rows for a Complex Map from SNOMED CT Reference Set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Refset Descriptor Rows for an Extended Map from SNOMED CT type Reference Set

    refsetId
    referencedComponentId (Referenced component)
    attributeDescription (Attribute description)
    attributeType (Attribute type)
    attributeOrder (Attribute order)

    Sample Content from an Extended Map from SNOMED CT Reference Set

    refSetId
    referencedComponentId (Map source concept)
    mapGroup (Map group)
    mapPriority (Map priority)
    mapRule (Map rule)
    mapAdvice (Map advice)
    mapTarget (Map target)
    correlationId (SNOMED CT source code to target map code correlation value)
    mapCategoryId (Map category value)

    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 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: or

    NO

    NO

    referencedComponentId

    SCTID

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

    Refers to the SNOMED CT concept that is mapped to the other terminology or code system (i.e. the map source).

    NO

    NO

    mapGroup

    Integer

    An Integer, grouping a set of complex map records from which one may be selected as a target code. Where a SNOMED CT concept maps onto 'n' target codes, there will be 'n' groups, each containing one or more complex map records.

    YES

    NO

    mapPriority

    Integer

    Within a mapGroup, the mapPriority specifies the order in which complex map records should be checked. Only the first map record meeting the run - time selection criteria will be taken as the target code within the group of alternate codes.

    YES

    NO

    mapRule

    String

    A machine-readable rule, (evaluating to either 'true' or 'false' at run-time) that indicates whether this map record should be selected within its mapGroup.

    YES

    NO

    mapAdvice

    String

    Human-readable advice, that may be employed by the software vendor to give an end-user advice on selection of the appropriate target code from the alternatives presented to him within the group.

    YES

    NO

    mapTarget

    String

    The target code in the target terminology, classification or code system.

    YES

    NO

    correlationId

    SCTID

    A child of in the metadata hierarchy, identifying the correlation between the SNOMED CT concept and the target code.

    YES

    NO

    The following additional field only applies to

    mapCategoryId

    SCTID

    Identifies the SNOMED CT concept in the metadata hierarchy which represents the MapCategory for the associated map member. The categories vary for different target code systems, each set of categories is represented by a subtype of .

    In the case of ICD-10 the individual category values are of: .

    YES

    NO

    0

    1

    2

    3

    4

    5

    6

    0

    1

    2

    3

    4

    5

    6

    7

    1

    1

    TRUE

    ALWAYS O03.8

    O03.8

    2

    1

    TRUE

    ALWAYS O08.6

    O08.6

    1

    1

    IFA 90979004 |Chronic tonsillitis (disorder)|

    IF CHRONIC TONSILLITIS CHOOSE J35.0 MAP OF SOURCE CONCEPT IS CONTEXT DEPENDENT

    J35.0

    1

    2

    IFA 232406009 |Chronic pharyngeal candidiasis (disorder)|

    IF CHRONIC PHARYNGEAL CANDIDIASIS CHOOSE B37.8 MAP OF SOURCE CONCEPT IS CONTEXT DEPENDENT

    B37.8

    1

    3

    OTHERWISE TRUE

    ALWAYS J31.2

    J31.2

    1

    1

    TRUE

    ALWAYS F31.1

    F31.1

    1

    1

    TRUE

    ALWAYS T63.4

    T63.4

    2

    1

    TRUE

    ALWAYS X25

    X25

    1

    1

    TRUE

    ALWAYS J18.0

    J18.0

    1

    1

    TRUE

    ALWAYS D61.8

    D61.8

    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)

    900000000000456007 |Reference set descriptor|

    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|

    900000000000500006 |Map source concept|

    900000000000456007 |Reference set descriptor|

    447562003 |SNOMED CT to ICD-10 complex map reference set

    900000000000500006 |Map source concept|

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

    Map Group, Priority and Rules

    Mapping Rule Specifications

    Metadata

    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 Templates

    Example Data

    Related Links

    mapGroup
    mapPriority
    mapRule
    mapAdvice
    ICD-10 Mapping Technical Guide
    ICD-10 Mapping Technical Guide
    900000000000454005 |Foundation metadata concept|
    900000000000455006 |Reference set|
    447250001 |Complex map from SNOMED CT type reference set|
    609331003 |Extended map from SNOMED CT type reference set|
    447250001 |Complex map type reference set|
    609331003 |Extended map type reference set|
    ICD-10 Mapping Technical Guide
    Provide Feedback

    effectiveTime

    900000000000443000 |Module (core metadata concept)|
    447250001 |Complex map from SNOMED CT type reference set|
    609331003 |Extended map from SNOMED CT type reference set|
    1193546000 |Map source to map target correlation (foundation metadata concept)|
    609331003 |Extended map type reference set|
    609330002 |Map category value|
    subtypes
    447634004 |ICD-10 map category value|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    900000000000501005 |Map group|
    900000000000478000 |Unsigned integer|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    900000000000502003 |Map priority|
    00000000000478000 |Unsigned integer|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    900000000000503008 |Map rule|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    900000000000504002 |Map advice|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    900000000000505001 |Map target|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447563008 |SNOMED CT to ICD-9-CM equivalence complex map reference set|
    1193546000 |Map source to map target correlation|
    900000000000461009 |Concept type component|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    900000000000501005 |Map group|
    900000000000478000 |Unsigned integer|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    900000000000502003 |Map priority|
    900000000000478000 |Unsigned integer|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    900000000000503008 |Map rule|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    900000000000504002 |Map advice|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    900000000000505001 |Map target|
    900000000000465000 |String|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    1193546000 |Map source to map target correlation|
    900000000000461009 |Concept type component|
    900000000000456007 |Reference set descriptor|
    447562003 |SNOMED CT to ICD-10 complex map reference set
    609330002 |Map category value|
    461009 |Concept type component|
    447562003 |ICD-10 complex map reference set|
    127009 |Miscarriage with laceration of cervix|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    127009 |Miscarriage with laceration of cervix|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    140004 |Chronic pharyngitis|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447639009 |Map of source concept is context dependent|
    447562003 |ICD-10 complex map reference set|
    140004 |Chronic pharyngitis|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447639009 |Map of source concept is context dependent|
    447562003 |ICD-10 complex map reference set|
    140004 |Chronic pharyngitis|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    162004 |Severe manic bipolar I disorder without psychotic features|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    177007 |Poisoning by sawfly larvae|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    177007 |Poisoning by sawfly larvae|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    181007 |Hemorrhagic bronchopneumonia|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|
    447562003 |ICD-10 complex map reference set|
    183005 |Autoimmune pancytopenia|
    447561005 |SNOMED CT source code to target map code correlation not specified|
    447637006 |Map source concept is properly classified|