> 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-user-guides/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.1-workflow/3.1.4-maintenance-workflow.md).

# Maintenance workflow

Snap2SNOMED supports maintenance of maps that have been created within the tool and also allows upload of simple maps in a defined format for maintenance.

Maintenance is supported through the following workflows

<table data-full-width="true"><thead><tr><th width="308.36798095703125">Action</th><th>Description</th></tr></thead><tbody><tr><td>Create new version of an existing map, update source scope (code system), target scope (code system) and migrate existing map rows</td><td><p>A new version of an existing map in the tool can be created through the project list by selecting the version to be copied and then creating a new version.</p><ul><li><p>For map rows that are copied, the tool will migrate</p><ul><li>source</li><li>target</li><li>relationship</li><li>status (e.g. DRAFT, MAPPED, ACCEPTED, etc.)</li><li>last author/reviewer data</li></ul></li></ul></td></tr><tr><td>Identify changes in map due to change in source scope</td><td><p>Removed or retired codes in the source</p><ul><li>tool will remove the rows from the map</li></ul><p>New codes in the source</p><ul><li>tool will create rows for the new source codes, with an empty target</li><li>Owners or members can filter empty target fields to create a task to complete mapping process</li></ul></td></tr><tr><td>Identify changes in map due to change in target scope</td><td><p>Out of scope or retired codes in the target</p><ul><li>Owners can use VALIDATE function in tool to identify out of scope codes</li><li>Owners or members can filter identified rows to create a task to update map targets and complete mapping process<br></li></ul><p>New target codes in code system</p><ul><li>Owners or members can filter relationship type for any type except for equivalent to create a task to review and update map targets and complete mapping process</li></ul></td></tr><tr><td>Upload existing map</td><td>An existing map can be uploaded into the tool to then be updated.</td></tr></tbody></table>

<div data-full-width="true"><figure><img src="https://4073150387-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhhAMcxzclQGXKlrJY7Lj%2Fuploads%2Fgit-blob-5cfded12c709f599060896f6e2471b163bd92b1d%2F137247299.png?alt=media" alt=""><figcaption></figcaption></figure></div>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=snap2snomed+User+Guide&#x26;entry.670899847=Maintenance%20workflow" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-ct-user-guides/snap2snomed-user-guide/how-to-.../3-mapping-with-snap2snomed/3.1-workflow/3.1.4-maintenance-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.