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. Table 5.2.3.4-1: Map to SNOMED CT with Correlation and Origin Reference Set - Data structure
Field Data type Purpose id 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.
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 (Full) Optional (Snapshot) 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.
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.
Identifies the reference set to which this reference set member belongs.
In this case, a subtype descendant of:
705111002
|
Map to SNOMED CT with correlation and origin type reference set (foundation metadata concept)|
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. The other-code which maps to the SNOMED CT conceptspecified as the referencedComponentId. 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|
. The correlation from the other-code to the SNOMED CT concept. Possible values are the following subtypes of
1193546000
|
Map source to map target correlation (foundation metadata concept)|
:
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
705116007
|
Original code system source for linked content value|
.Purpose
Data Structure
Part of Primary Key NO YES (Full /Snapshot) YES YES NO YES NO NO NO NO NO NO NO YES NO
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|
YES NO YES NO
Metadata
The following metadata hierarchy supports this reference set:
Table 5.2.3.4-2: Map to SNOMED CT with correlation and origin type reference set in the Metadata Hierarchy
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
The tables below show the descriptors that define examples of reference sets that follow the 1187636009 | Simple map to SNOMED CT type reference set (foundation metadata concept)| pattern.
Table 5.2.3.4-3: 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) |
|---|---|---|---|---|
0 | ||||
1 | ||||
| 2 | ||||
| 3 | ||||
| 4 |
Refset Examples
Table 5.2.3.4-4: Sample Content from a Map to SNOMED CT with correlation and origin type reference set
refsetId | referencedComponentId (mapTarget) | mapSource | attributeId | correlationId | contentOriginId |
|---|---|---|---|---|---|
| LP16063-7 | TBC | ||||
| LP16246-8 | TBC | ||||
| LP148077-3 | TBC | ||||
| LP15149-5 | TBC | ||||
| LP14492-0 | TBC |
Related Links
- For further information see Using LOINC with SNOMED CT: 4.2.1 LOINC Part Map Reference Set.
Feedback
Overview
Content Tools
Apps