# Get Mapping Data

## Overview

Mapping is the process of converting data from one code system, classification, or terminology to another code system, classification, or terminology.

#### Notes

* The _mapping_ process includes the preparation and maintenance of resources used for converting data.
* SNOMED CT _mapping_ resources are distributed as mapping reference sets.

The SNOMED CT reference set design provides a common foundation on which mapping resources that meet different requirements can be built. The guidance in this section relates to the general approaches to accessing data in a mapping reference set. The table below provides reference to specific mapping reference set types and supporting documentation related to the use of those reference sets.

#### Map Reference Sets and Documentation

<table data-full-width="true"><thead><tr><th>Map type</th><th>Description</th><th>Reference Set File Format</th></tr></thead><tbody><tr><td><strong>Simple map</strong></td><td>Supports one to one maps to or from another code system</td><td>Simple Map Reference Set</td></tr><tr><td><strong>ICD classification maps</strong></td><td>Supports maps from SNOMED CT to ICD-10 classifications. Enables mapping to different codes based on rules and priorities. Also allows maps from a single code to combinations of codes.</td><td>Complex and Extended Map from SNOMED CT Reference Sets</td></tr><tr><td><strong>Maps including additional data to represent attribute-value combinations, correlation and source of original code</strong></td><td>Supports maps where some codes in the other code system represent a combination of and attribute with a value (e.g. finding site appendix). Also supports maps where the correlation between source and target needs to be specified and where there are intellectual property reasons for recording that either the SNOMED CT or other code were the original representations of the mapped meaning.</td><td>Map to SNOMED CT with Correlation and Origin Reference Set</td></tr><tr><td><strong>Maps to SNOMED CT expressions</strong></td><td>Supports maps from another code systems where the use of a SNOMED CT expression may capture the meaning of that code more accurately than can be achieved with a single concept.</td><td>Code to Expression Reference Set</td></tr></tbody></table>

## Requirements and Options

Terminology services should be able to provide access to sets of maps based either on the SNOMED CT concept or a code from the other code system.

* The concept involved in the map is represented by the referencedComponentId. As noted in [Get Data from a Reference Set](4.10-get-data-from-a-reference-set), access to reference set data using a combination of refsetId and referencedComponentId is a general requirement.
* The other code is generally in a column referred to as mapTarget1. Support for access to maps using a combination of refsetId and mapTarget is therefore also required.

The required services are listed in the table below. Additional requirements should be considered for cases where the map refers to an expression rather than a single concept.

The services described in this section are limited to accessing the relevant map data. In simple cases, this may be sufficient to enable mapping. However, in other cases the services will provide client applications with options to display to the user and/or processable rules to be tested against other data to determine the appropriate map.

### Required Services

<table data-full-width="true"><thead><tr><th>Service Name and Status</th><th>Input</th><th>Output</th></tr></thead><tbody><tr><td><strong>Get maps based on combinations of refsetId and referencedComponentId</strong></td><td><ul><li>Identifier of concept to be mapped to target scheme </li><li>Edition and version Reference set identifier </li><li>Optional: Language/dialect2</li></ul></td><td><p>All map data associated with maps in the specified reference set in which the referencedComponentId matches the specified concept identifier. </p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Gets maps from SNOMED CT to another code system, if the map data supports mapping in that direction.</p></div></td></tr><tr><td><strong>Get maps based on combinations of refsetId and mapTarget</strong></td><td><ul><li>Other code to be mapped to SNOMED CT. </li><li>Edition and version </li><li>Reference set identifier </li><li>Optional: Language/dialect2</li></ul></td><td><p>All map data associated with maps in the specified reference set in which the mapTarget matches the specified other code. </p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Gets maps from SNOMED CT to another code system, if the map data supports mapping in that direction.</p></div></td></tr><tr><td><strong>Get maps based on combinations of refsetId,referencedComponentIdand mapTarget</strong></td><td><ul><li>Identifier of concept </li><li>Other code </li><li>Edition and version </li><li>Reference set identifier </li><li>Optional: Language/dialect2</li></ul></td><td><p>All map data associated with maps in the specified reference set in which the referencedComponentId matches the specified concept identifier and the mapTarget matches the other code.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>There are two situations in which this can be useful:</p><ul><li>To test whether a map exists between a concept and a specific code in the other code system.</li><li>To access information about maps between a concept and a specific code in another code system.</li></ul></div></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

## Interdependencies

### Required By

* Use Cases
  * [Mapping Data to or from or from Another Code System](../3-terminology-service-use-cases/apply-mapping-reference-sets)

### Depends On

* [Select Edition and Version](4.1-select-edition-and-version)
* [Get Data from a Reference Set](4.10-get-data-from-a-reference-set)

## Service Examples

{% hint style="info" %}
The Snowstorm and FHIR examples are presented in plain text and URL encoded versions. Always use the "Encoded URL" when testing the example service requests. The plain text version is included to aid readability but using this version in a service request may result in errors. These errors result from characters that have to be encoded as they are not permitted in a URL (see [IETF RFC1738](https://www.ietf.org/rfc/rfc1738.txt)).
{% endhint %}

#### Snowstorm API

<table data-full-width="true"><thead><tr><th width="159.74609375">Service Name</th><th>API Call</th><th>Result</th></tr></thead><tbody><tr><td><strong>Get maps based on combinations of refsetId and referencedComponentId</strong></td><td><pre data-overflow="wrap"><code>GET [snowstorm]/[branchPath]/members?referenceSet=[refsetid]&#x26;referencedComponentId=[conceptId]&#x26;active=true
</code></pre><p>Example 1. ICD-O Map for <a href="http://snomed.info/id/1338007">1338007 | Basal cell carcinoma (morphologic abnormality)|</a></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=446608001&#x26;referencedComponentId=1338007&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=446608001&#x26;amp;amp;referencedComponentId=1338007&#x26;amp;active=true
</code></pre><p>Example 2. ICD-10 Map for <a href="http://snomed.info/id/74400008">74400008 | Appendicitis|</a></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=447562003&#x26;referencedComponentId=74400008&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=447562003&#x26;amp;amp;referencedComponentId=74400008&#x26;amp;active=true
</code></pre><p>Example 3. ICD-10 Map for <a href="http://snomed.info/id/196607008">196607008 | Esophageal ulcer due to aspirin|</a></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=447562003&#x26;referencedComponentId=196607008&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=447562003&#x26;amp;amp;referencedComponentId=196607008&#x26;amp;active=true
</code></pre><p>Example 4. ICD-10 Map for <a href="http://snomed.info/id/32398004">32398004 | Bronchitis|</a></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=447562003&#x26;referencedComponentId=32398004&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=447562003&#x26;amp;amp;referencedComponentId=32398004&#x26;amp;active=true
</code></pre><p><br>Example 5. ICD-10 Map for <a href="http://snomed.info/id/111613008">111613008 | Closed skull fracture with intracranial injury|</a></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=447562003&#x26;referencedComponentId=111613008&#x26;active=true
</code></pre></td><td><p>Returns a JSON representation of the data in active rows in the specified mapping reference set with a referencedComponentId that matches the specified conceptId.</p><p><strong>The examples illustrate the following points</strong> <br><br><strong>Example</strong> 1. A concept that maps to a single ICD-O code in a simple map refset.<br><br><strong>Example 2</strong>. A concept that maps to a single ICD-10 classification code in a complex/extended map refset.<br><br><strong>Example 3</strong>. A concept that maps to a combination of two classification codes (there are two map groups and each contains a single map row with priority 1)<br><br><strong>Example 4</strong>. A concept that has a single map group containing two rows. The row with priority 1 has a rule that requires the patient age to be less than or equal to 15 years. If that rule is not matched the row with map priority 2 applies as it contains the rule "OTHERWISE".<br><br><strong>Example 5</strong>. A concept that, like example 2, contains two map groups. However, in the case it each of those maps also include specific human readable advice "... MAPPED FOLLOWING WHO GUIDANCE | POSSIBLE REQUIREMENT FOR AN EXTERNAL CAUSE CODE"</p><p>The data returned for each refset member of an extended map (e.g. as used in examples 2-5) includes the following mapping data as subproperties of the additionalFields property:</p><table data-header-hidden><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Property</strong></td><td><strong>Description</strong></td></tr><tr><td><strong>mapGroup</strong></td><td>An integer grouping a set of maps. One map should be chosen from each group.</td></tr><tr><td><strong>mapPriority</strong></td><td>The order in which map within a group should be checked.</td></tr><tr><td><strong>mapRule</strong></td><td>A machine-readable rule, that determines if a map applies.</td></tr><tr><td><strong>mapAdvice</strong></td><td>Advice to assist manual selection map from a group.</td></tr><tr><td><strong>mapTarget</strong></td><td>The target code from the other coding scheme (if this map is chosen based on the rule or advice).</td></tr><tr><td><strong>correlationId</strong></td><td>|Representing the correlation between the concept and the target code.</td></tr><tr><td><strong>mapCategoryId</strong></td><td>Represents the map category that applies to this map.</td></tr></tbody></table></td></tr><tr><td><strong>Get maps based on combinations of refsetId and mapTarget</strong><br></td><td><pre data-overflow="wrap"><code>GET [snowstorm]/[branchPath]/members?referenceSet=[refsetid]&#x26;mapTarget=[otherCode]&#x26;active=true
</code></pre><p>Example 6. Map from ICD-O code "8090/3" to SNOMED CT concepts</p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=446608001&#x26;mapTarget=8090/3&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=446608001&#x26;amp;amp;mapTarget=8090%2F3&#x26;amp;active=true
</code></pre><p>Example 7. Maps from NHS Clinical Terms to a SNOMED CT concept</p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=900000000000497000&#x26;mapTarget=Xa9C4&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=900000000000497000&#x26;amp;amp;mapTarget=Xa9C4&#x26;amp;active=true
</code></pre></td><td><p>Returns a JSON representation of the data in active rows in the specified mapping reference set with a mapTarget that matches the specified otherCode. This returns the same data as noted above.<br></p><p><strong>Example 6</strong>. Reverses the map shown in example 1. In this case it returns records showing several concepts that map to the this ICD-O code. As these are simple map with no rules, this result indicates that all these concepts map to the same less specific ICD-O code.</p><p><br><strong>Example 7</strong> . Maps from NHS CTV3 codes (previously used in the UK) to SNOMED CT concepts. In this case the map returns a single map from any specified CTV3 code to the closes matching SNOMED CT concept.<br></p><p>Warning</p><p>The ICD-10 map is a unidirectional map from SNOMED CT concept to ICD-10 codes. The mapGroup, mapPriority, mapRule, mapAdvice and mapCategoryId properties of complex and extended apply to the set of maps <strong>from</strong> a SNOMED CT concept to a mapTarget. These rules cannot be interpreted if maps are accessed for specified targetCode. Therefore, this service should not be used to access maps of this type.</p></td></tr><tr><td><strong>Get maps</strong> <strong>based on combinations of refsetId, referencedComponentId and mapTarget</strong></td><td><pre data-overflow="wrap"><code>GET [snowstorm]/[branchPath]/members?referenceSet=[refsetid]&#x26;referencedComponentId=[conceptId]&#x26;mapTarget=[otherCode]&#x26;active=true
</code></pre><p>Example 8. Finds any maps from <a href="http://snomed.info/id/111613008">111613008 | Closed skull fracture with intracranial injury|</a> to ICD-10 code S06.90</p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN/2020-01-31/members?referenceSet=447562003&#x26;referencedComponentId=111613008&#x26;mapTarget=S06.90&#x26;active=true
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [snowstorm]/MAIN%2F2020-01-31/members?referenceSet=447562003&#x26;amp;amp;amp;referencedComponentId=111613008&#x26;amp;amp;mapTarget=S06.90&#x26;amp;active=true
</code></pre></td><td><p>Returns a JSON representation of the data in active rows in the specified mapping reference set with a referencedComponentId that matches the specified conceptId and a mapTarget that matches the specified code from the other code system.<br></p><p><strong>Example 8</strong> . Could be used either or both of the following:</p><ol><li>Test if there is a map between the SNOMED CT concept "Closed skull fracture with intracranial injury" and the ICD-10 code S06.9 "Unspecified intracranial injury".</li><li>Provide access to the associated mapping rule, advice and correlation data for any maps between these two codes.</li></ol></td></tr></tbody></table>

#### FHIR API

<table><thead><tr><th width="168.15625">Service Name</th><th>API Call</th><th>Result</th></tr></thead><tbody><tr><td><strong>Get maps based on combinations of refsetId and referencedComponentId</strong></td><td><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=[componentId] &#x26;system=http://snomed.info/sct&#x26;source=[sourceCodeSystem]?fhir_vs&#x26;target=[sourceCodeSystem]&#x26;url=[version]?fhir_cm=[refesetId]
</code></pre><p>Example 1. ICD-O Map for <a href="http://snomed.info/id/1338007">1338007 | Basal cell carcinoma (morphologic abnormality)|</a></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=1338007&#x26;system=http://snomed.info/sct &#x26;source=http://snomed.info/sct?fhir_vs &#x26;target=http://snomed.info/sct?fhir_vs &#x26;url=http://snomed.info/sct/900000000000207008/version/20200131?fhir_cm=446608001
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=1338007&#x26;amp;amp;amp;amp;system=http%3A%2F%2Fsnomed.info%2Fsct+&#x26;amp;amp;amp;source=http%3A%2F%2Fsnomed.info%2Fsct%3Ffhir_vs+&#x26;amp;amp;target=http%3A%2F%2Fsnomed.info%2Fsct%3Ffhir_vs+&#x26;amp;url=http%3A%2F%2Fsnomed.info%2Fsct%2F900000000000207008%2Fversion%2F20200131%3Ffhir_cm%3D446608001%0A
</code></pre><p>Example 2. ICD-10 Map for <a href="http://snomed.info/id/74400008">74400008 | Appendicitis|</a></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=74400008&#x26;system=http://snomed.info/sct&#x26;source=http://snomed.info/sct?fhir_vs &#x26;target=http://hl7.org/fhir/sid/icd-10&#x26;url=http://snomed.info/sct/900000000000207008/version/20200131?fhir_cm=447562003
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=74400008&#x26;system=http://snomed.info/sct&#x26;source=http://snomed.info/sct?fhir_vs &#x26;target=http://hl7.org/fhir/sid/icd-10&#x26;url=http://snomed.info/sct/900000000000207008/version/20200131?fhir_cm=447562003
</code></pre><p>Example 3. ICD-10 Map for <a href="http://snomed.info/id/196607008">196607008 | Esophageal ulcer due to aspirin|</a></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=196607008&#x26;system=http://snomed.info/sct&#x26;source=http://snomed.info/sct?fhir_vs &#x26;target=http://hl7.org/fhir/sid/icd-10&#x26;url=http://snomed.info/sct/900000000000207008/version/20200131?fhir_cm=447562003
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=196607008&#x26;amp;amp;amp;amp;system=http%3A%2F%2Fsnomed.info%2Fsct&#x26;amp;amp;amp;source=http%3A%2F%2Fsnomed.info%2Fsct%3Ffhir_vs+&#x26;amp;amp;target=http%3A%2F%2Fhl7.org%2Ffhir%2Fsid%2Ficd-10&#x26;amp;url=http%3A%2F%2Fsnomed.info%2Fsct%2F900000000000207008%2Fversion%2F20200131%3Ffhir_cm%3D447562003
</code></pre><p><br>Example 4. ICD-10 Map for <a href="http://snomed.info/id/32398004">32398004 | Bronchitis|</a></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=32398004&#x26;system=http://snomed.info/sct&#x26;source=http://snomed.info/sct?fhir_vs &#x26;target=http://hl7.org/fhir/sid/icd-10&#x26;url=http://snomed.info/sct/900000000000207008/version/20200131?fhir_cm=447562003
</code></pre><hr><p><em>Encoded URL</em></p><pre data-overflow="wrap"><code>GET [fhir]/ConceptMap/$translate?code=32398004&#x26;amp;amp;amp;amp;system=http%3A%2F%2Fsnomed.info%2Fsct&#x26;amp;amp;amp;source=http%3A%2F%2Fsnomed.info%2Fsct%3Ffhir_vs+&#x26;amp;amp;target=http%3A%2F%2Fhl7.org%2Ffhir%2Fsid%2Ficd-10&#x26;amp;url=http%3A%2F%2Fsnomed.info%2Fsct%2F900000000000207008%2Fversion%2F20200131%3Ffhir_cm%3D447562003
</code></pre></td><td><p>Returns a JSON representation of data about each of the target components.</p><p>The data returned for each concept includes:</p><ul><li><strong>boolean:</strong> True if the concept could be translated successfully. The value can only be true if at least one returned match</li><li><strong>match:</strong> Each match represents data for the map or associated target. Note that there may be multiple matches, where each element represents a mapTarget. For each mapTarget, following data is provided</li><li><strong>system</strong>: the codesystem of the mapTarget</li><li><strong>code:</strong> The identifier of the mapTarget</li></ul><p>Request response</p><p>Be aware that the FHIR TS API only provides information about the mapTarget. However, no additional map data represented in the map reference set is provided. This service is therefore sufficient to represent simple maps, but data required to interpret complex maps is not made available.<br></p><p><strong>Example</strong> <strong>1</strong>. A concept that maps to a single ICD-O code in a simple map refset.</p><p><br><strong>Example 2</strong>. A concept that maps to a single ICD-10 classification code in a complex/extended map refset.</p><p><br><strong>Example 3</strong>. A concept that maps to a combination of two classification codes (there are two map groups and each contains a single map row with priority 1)</p><p><br><strong>Example 4</strong>. A concept that has a single map group containing two rows. For this map, a rule will determine which target should be chosen. Please note that the response does <strong>not</strong> show the rules as they are stated in the map reference set.</p><p><br></p></td></tr><tr><td><strong>Get maps based on combinations of refsetId and mapTarget</strong></td><td>N/A</td><td>The FHIR TS API does not support retrieval of map data based on a specific mapTarget</td></tr></tbody></table>

#### MySQL Example Database

<table data-full-width="true"><thead><tr><th>Service Name</th><th>SQL Query</th><th>Result</th></tr></thead><tbody><tr><td><strong>Get maps based on combinations of refsetId and referencedComponentId</strong></td><td><p></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap WHERE active=1 AND refsetId=[refsetId] AND referencedComponentId=[conceptId];
</code></pre><p>Example 1. ICD-O Map for <a href="http://snomed.info/id/1338007">1338007 | Basal cell carcinoma (morphologic abnormality)|</a></p><p></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_simplemap    WHERE active=1 AND refsetId=446608001 AND referencedComponentId=1338007
</code></pre><p>Example 2. ICD-10 Map for <a href="http://snomed.info/id/74400008">74400008 | Appendicitis|</a></p><p></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap WHERE active=1 AND refsetId=447562003 AND referencedComponentId=74400008
</code></pre><p>Example 3. ICD-10 Map for <a href="http://snomed.info/id/196607008">196607008 | Esophageal ulcer due to aspirin|</a></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap WHERE active=1 AND refsetId=447562003 AND referencedComponentId=196607008
</code></pre><p>Example 4. ICD-10 Map for <a href="http://snomed.info/id/32398004">32398004 | Bronchitis|</a></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap WHERE active=1 AND refsetId=447562003 AND referencedComponentId=32398004;
</code></pre><p>Example 5. ICD-10 Map for <a href="http://snomed.info/id/111613008">111613008 | Closed skull fracture with intracranial injury|</a></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap WHERE active=1 AND refsetId=447562003 AND referencedComponentId=111613008;
</code></pre><p>Alternative approach using a stored procedure. This does not require the specific map reference set type to be identified.</p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql"><strong>-- Alternative that also shows the terms associated-- with identifiers in the map records
</strong>
CALL snap_members([refsetId],[conceptId]);
</code></pre></td><td>Returns rows of data from the specified mapping reference set with a referencedComponentId that matches the specified conceptId.</td></tr><tr><td><strong>Get maps based on combinations of refsetId and mapTarget</strong></td><td><p></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=[refsetId] AND mapTarget=[otherCode];
</code></pre><p>Example 6. Map from ICD-O code "8090/3" to SNOMED CT concepts</p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=446608001 AND mapTarget="8090/3";
</code></pre><p>Example 7. Maps from NHS Clinical Terms to a SNOMED CT concept</p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=900000000000497000    AND mapTarget="Xa9C4";
</code></pre></td><td>Returns rows of data from the specified mapping reference set with a mapTarget that matches the specified code in the other code system.</td></tr><tr><td><strong>Get maps based on combinations of refsetId, referencedComponentId and mapTarget</strong></td><td><p></p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=[refsetId] AND referencedComponentId=[conceptId] AND mapTarget=[otherCode]
</code></pre><p>Example 8. Finds any maps from <a href="http://snomed.info/id/111613008">111613008 | Closed skull fracture with intracranial injury|</a> to ICD-10 code S06.90</p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql"><strong>SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=447562003 AND referencedComponentId=111613008 AND mapTarget="S06.90"
</strong></code></pre><p>Example 9. Finds any maps from <a href="http://snomed.info/id/111613008">111613008 | Closed skull fracture with intracranial injury|</a> to ICD-10 codes in the S06 chapter</p><pre class="language-sql" data-overflow="wrap"><code class="lang-sql">SELECT * FROM snap_refset_extendedmap    WHERE active=1 AND refsetId=447562003    AND referencedComponentId=111613008 AND mapTarget like "S06.%"
</code></pre></td><td><p>Returns rows of data from the specified mapping reference set with a referencedComponentId that matches the specified conceptId and a mapTarget that matches the specified code in the other code system.</p><p></p><p>Example 9. provides an additional option, which may be useful code systems such as ICD-10 in which part of the code represents represent chapters or subdivision. It allows a search for a map from a concept to any code in a specified chapter.</p></td></tr></tbody></table>

