> 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/map-development/8-revise-and-maintain.md).

# Revise and maintain

Maps developed for ongoing use may require maintenance.

When developing or evaluating a change management process, it is important to consider various factors. Some of these factors are introduced in the table below.

#### Change management considerations

{% columns %}
{% column width="25%" %}
**Request for change**
{% endcolumn %}

{% column width="75%" %}
**Where will the need for change come from?**

This could be any stakeholder involved in the development or use of the map.

**How will change requests be expressed and submitted?**

These may be submitted directly by users or may be collated and edited by suppliers. The maintainers of the subset may be proactive in seeking improvements or may wait for change requests to be submitted.

**What lead time is acceptable for the processing of a change request?**

What should users of the map do in the period between recognizing the need for a change and that need being met by a new release of the map? Options may include manual workarounds.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="25%" %}
**Revision cycle**
{% endcolumn %}

{% column width="75%" %}
**Will there be a predictable revision cycle with regular releases, or will changes be made on an as-needed basis?** 

Maintenance may be required when there are changes to

* source code system
* target code system
* use case/user and system requirements

Some use cases may also require maintaining retired/deprecated content alongside new content. Impact of changes need to be considered, as well as impact on delaying updates.
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="25%" %}
**Resources**
{% endcolumn %}

{% column width="75%" %}
What editorial and technical resources are needed?
{% endcolumn %}
{% endcolumns %}

{% columns %}
{% column width="25%" %}
**Documentation**
{% endcolumn %}

{% column width="75%" %}
Which associated documentation also requires updates with the map itself?
{% 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=Revise%20and%20maintain" 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/map-development/8-revise-and-maintain.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.