> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-mapping-guide/evaluating-mapping-as-a-solution/4.5-intended-or-unintended-consequences-of-mapping.md).
# Intended or unintended consequences of mapping
Even a dual-authored, dual-reviewed, clinically assured equivalence map may not provide a comprehensive and long-term solution in every case.
The table below shows a well-formed map.
| Source ID | Source term | Relationship type | Target ID | Target term |
| --------- | -------------------- | ----------------- | --------- | -------------------- |
| A01 | Asthma | equivalent | 195967001 | Asthma |
| C11 | Common cold | equivalent | 82272006 | Common cold |
| D58 | Dislocation of joint | equivalent | 108367008 | Dislocation of joint |
| E123 | Ear infection | equivalent | 129127001 | Ear infection |
The consequence here is that the new SNOMED CT content reflects only what was pre-existing, with no change in scope or range of clinical content, and with the features of the legacy source system maintained.
{% hint style="info" %}
These may be 'convenience' terms or handpicked favourites with no or some internal structure, or they may be disjoint. Sometimes these source code sets are arbitrary or idiosyncratic.
{% endhint %}
Despite investing effort in producing a well-formed map, we achieve only what we already have, with merely a change in codes/identifiers. There is no improvement in clinical utility, standardisation, interoperability with other standard SNOMED CT-enabled systems, or analytics that might exploit the logical definitions of SNOMED CT, which are not readily performed using subsumption or ECL queries.
In this scenario, the SNOMED CT map target concepts can be regarded as the minimum viable 'mapset' of concepts that will support migration or longitudinal data analyses. But to provide future utility, for integration, interoperability among and between systems and settings, and to support SNOMED CT-aware analytics, this mapset would need to be expanded to form a more comprehensive and sustainable ValueSet. Mapping is a great first step, but it is not the whole journey.
Map products that contain broader or narrower relationships may influence how data is analysed and interpreted. Reports of patient data that are formulated using such maps will likely reflect at least some of those map features.
This may result in some slippage in understanding or direct comparability between reports generated directly using the old source code set and mapped data reports, and/or between mapped data reports and reports formulated using SNOMED CT-encoded data directly. It may appear that data analyses are 'skewed' when a map product is in use. It is recommended that map performance be evaluated and compared across retrospective and prospective analyses to determine the impact of the map product.
Again, all of these consequences, intended or not, are choice points that jurisdictions and users might consider when embarking on and designing a roadmap for their mapping strategies.
Provide Feedback
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-mapping-guide/evaluating-mapping-as-a-solution/4.5-intended-or-unintended-consequences-of-mapping.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.