> 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.4-data-quality.md).

# Data quality

Mapping cannot mitigate data quality issues.

## Poor data quality

Poor-quality source data or insufficient information for the map development team to understand the source code and identify an appropriate target code will result in poor or low-quality maps, with many source codes remaining unmapped.

Also, "dirty" data, e.g., abbreviations, shorthand, use of symbols, or free-text sentences, can be expensive to process and map. "Dirty" data is difficult to process, and incorrect maps can be created if the author's true intent is unclear.

## Unknown, unfamiliar or undocumented source code sets

Often, legacy code sets have existed for some time, have been developed locally, and may not be well documented. The original intent of the source code set may be vague, not well understood, or not agreed upon. There may only be informal documentation, or the documentation may have aged. Understanding both the source and target vocabularies is essential; guessing at the intended meaning of either the source or the target will result in a less robust, less safe map product.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Mapping+Guide&#x26;entry.670899847=Data%20quality" class="button primary">Provide Feedback</a>


---

# 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.4-data-quality.md?ask=<question>&goal=<endgoal>
```

`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.
