Purpose

The  is designed to enable associations between codes in another code system  and , where the following constraints apply:

  1. Some of the  cannot be mapped to an individual SNOMED CT .
  2. Licensing conditions (or other considerations) prevent addition of new SNOMED CT concepts to represent the same meaning as the .
  3. The  can be logically defined using the  to represent the same meaning  or a similar though less specific meaning .
  4. Other requirements similar for those applicable to mapping may also apply including:
    1. An indication of the degree of correlation between the   and the SNOMED CT expression.
    2. An indication of whether the  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.

Data Structure

The general approach to the above requirements is to associate each of the  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   are not identified by an  , the logical definition cannot be represented using  . There are two potential approaches to this, one would be to use a general purpose description logic language (e.g.  ) and the other is to use a  to represent each definition. The  is designed to support the expression-based approach.

Code to Expression Reference Set - Data structure


Metadata

The following metadata supports this :

Code to Expression Reference Set in the Metadata Hierarchy


  900000000000454005 |Foundation metadata concept|
		900000000000455006 |Reference set|
				705109006 |Code to expression type reference set|



Descriptor template and examples

The tables below show the descriptors that define examples of 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)

0



1

2

3

4


5

Refset Examples


Sample Content from a Code to Expression Type Reference Set


refsetId

referencedComponentId 

mapSource

expressiondefinitionStatusIdcorrelationIdcontentOriginId

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

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

51406-7363787002:370134009=123029007,704327008=122592007,704318007=118556004,370132008=30766002,704319004=50863008,246093002=4546008


59878-9363787002:370134009=123029007,704327008=258459007,704318007=118556004,246093002=273948005,370132008=30766002,704319004=31773000


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

Related Links