> 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-extension-guide/5-key-steps/5.7-maintenance/5.7.1-change-management.md).

# Change Management

Each new release of the SNOMED CT International Edition introduces some changes to the content in SNOMED CT. Many of these changes are additions to the breadth and depth of clinical coverage. Other changes may include new descriptions, corrections to concept definitions, and enhancements to the expressivity of the concept model. These changes are an essential characteristic of an evolving clinical terminology which seeks to support current requirements. However, each change made to the International Edition may have an impact on the content in an extension. It is therefore important to evaluate and manage these changes when reconciling an extension with a new version of the SNOMED CT International Edition (or another extension on which it depends).

The change management process can be divided into three distinct phases:

1. **Identify changes**
2. **Assess change impact**
3. **Update extension**

After change management has been performed, it is important that thorough [review and validation](/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.5-review-and-validation.md) of the resulting extension is performed.

In the following sections we discuss the three phases of change management.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=5.7.1%20Change%20Management" 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-extension-guide/5-key-steps/5.7-maintenance/5.7.1-change-management.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.