> 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.2-change-requests.md).

# Change Requests

Updating the extension to accommodate user requests for additions or changes is an important aspect of the overall extension maintenance process. Consumers of extensions need to be able to submit requests for changes, and the extension producer is responsible for providing a mechanism to collect and process these change requests. This process in turn supports the continued relevance and quality of the extension itself.

National Release Centers (NRCs) are responsible for collecting requests for changes detected by Affiliates. Organizations in Member countries or territories should therefore submit their content requests to the relevant NRC. The NRC will subsequently make a decision as to the relevance of the content for the International or National Edition, as described in [Assessing Requests](/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.3-assessing-requests.md).

The type of service implemented to support change requests will depend on the scope and size of the extension, the anticipated number of extension consumers, and a range of other factors. In situations in which a small number of extension consumers are expected, a simple email service may be sufficient to enable consumers to request content changes. Extension producers with a greater number of anticipated consumers may decide to implement a dedicated system to support the tracking and management of change requests. SNOMED International has a formal procedure for submitting change requests, as described in the [CRS User Guide](https://confluence.ihtsdotools.org/display/SCTCR/CRS+User+Guide).

<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.2%20Change%20Requests" 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.2-change-requests.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.