# Revise and maintain

Maps developed for ongoing use may require maintenance.

When developing or evaluating a change management process it is important to take different factors into account. 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 of the stakeholders 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 looking for improvements, or may wait for requests for change 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 work arounds
{% 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 maintenance of retired/deprecated content, with addition of 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 require 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: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-mapping-guide/map-development/8-revise-and-maintain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.