Release File Specification

Search

SNOMED CT Document Library

    Loading...

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Purpose

The | Map correlation and origin type reference set|  is used to meet the requirements for representation of maps between codes in another code system  (other-codes) and 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.

Data Structure

Field

Data type

Purpose

id

UUID

A 128 bit unsigned integer, uniquely identifying the reference set member.

effectiveTime

Time

Specifies the inclusive date at which this addition or change becomes effective.

active

Boolean

Specifies whether the member's state was active or inactive from the nominal release date specified by the effectiveTime field.

moduleId

SCTID

Identifies the member version's module. Set to a child of | Module| within the metadata hierarchy.

refsetId

SCTID

Identifies the reference set and must be a subtype of | Map correlation and origin type reference set| which is located in the metadata hierarchy as shown below: 

referencedComponentId

SCTID

A reference to the SNOMED CT concept being mapped to/from the other-code.

mapTarget

String

The other-code to/from which the concept is mapped.

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 model1 , 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 | Concept model attribute| .

Footnotes
Ref Notes
1 For example a code representing 'procedure site index finger' could not be mapped accurately simply to | Index finger| but also needs to refer to the implied attribute | Procedure site| .

correlationId

SCTID

The correlation between the SNOMED CT concept and the other-code. Possible values are the following subtypes of 447247004 | SNOMED CT source code to target map code correlation value| :

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   705116007 | Original code system source for linked content value| .

Feedback
  • No labels