> 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/developing-use-case-and-requirements/5.1-map-documentation.md).

# Map documentation

Documentation of mapping methodology and decisions made is important:

* to allow reproduction of the mapping process for updates
* as evidence of the mapping process undertaken and the rules applied for compliance assessment

A map is not necessarily static; future versions of a map may require changes to decisions or rules, which will need to be clearly defined and consistently applied.

Clear documentation will allow the correct usage of the map and allow users to identify when the meaning of the results of the map has changed

Documentation should include:

{% columns %}
{% column %}

* identification of source and target code systems (include versioning)
* the purpose and use case of the map
* intended users of the map
* the scope and rules of the map
* pre-processing undertaken
* processes undertaken to modify data
* rules and reasons for changes
  {% endcolumn %}

{% column %}

* personnel involved
* tools used
* the mapping process used
* issues resolution process
* validation process
* risk assessment
* risk management process
  {% endcolumn %}
  {% endcolumns %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Mapping+Guide&#x26;entry.670899847=Map%20documentation" 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/developing-use-case-and-requirements/5.1-map-documentation.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.