> 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-ehr-requirements-guide/5-maintenance.md).

# Maintenance

The ability to incorporate changes from International and National editions of SNOMED CT is key to a successful, long-term implementation. SNOMED International provides release twice a year and national release centers may provide the same or more. These updates contain important changes that may be due to changes in medical knowledge or patches on feedback from the community, and it is important that vendors are able to process these updates.

1. Ensure that the version of the given SNOMED CT edition being used within the solution is no more than 2 versions (n-2) behind the most current version. Components that may change between versions may include:
   * Concepts: new concepts added, concepts made inactive.
   * Descriptions (with terms): new terms added, terms made inactive, terms changed (minor typing mistakes may have been corrected).
   * Relationships: new relationships, relationships made inactive, additional inferred relationships from classifying the terminology.
   * Refsets: new refsets, new members to a refset, members made inactive within a refset, a refset made inactive.
2. Ensure all subsets and maps used in user interfaces, reports, queries, etc. are maintained with each new version of SNOMED CT to ensure continued clinical validity.
3. If the vendor is required to create a SNOMED CT extension, they must follow the general principles of SNOMED CT, including allocating globally unique identifiers, concept permanence (i.e. never reusing the same concept id for a different concept), and maintaining a robust audit trail for all inactivation’s (including when the code was inactivated and what codes have replaced it).

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=EHR+Requirements+Guide&#x26;entry.670899847=5.%20Maintenance" 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-practical-guides/snomed-ct-ehr-requirements-guide/5-maintenance.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.
