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.
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
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
Refset Descriptor Rows for an Extended Map from SNOMED CT type Reference Set
Sample Content from an Extended Map from SNOMED CT Reference Set
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)
effectiveTime