> 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/4-logical-design/4.5-release-packages.md).

# Release Packages

A SNOMED CT release package is a set of SNOMED CT components, reference set members and other related items that are distributed in a set of release files as a single archived unit by SNOMED International, a National Release Center or another organization authorized to maintain and distribute a SNOMED CT extension. A release package may include one or more complete SNOMED CT Editions (in which all dependencies are resolved) or a supplementary extension module that depends on separately packaged modules. While a SNOMED CT edition is a logical construct consisting of the contents of a focus module and the modules on which it depends, release packages are the physical unit in which some or all of an edition is distributed. A release package, which is distributed at a given point in time, is referred to as a release package version or a versioned release package. For more information on release packages, please refer to [Packaging and File Naming](/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.6-distribution/5.6.1-preparing-for-distribution/5.6.1.2-packaging-and-file-naming.md).

For example, as illustrated in the image below, SNOMED International distributes the two modules of the International Edition plus the [| SNOMED CT to ICD-10 rule-based mapping module|](http://snomed.info/id/449080006) extension in a single release package, and distributes a range of other extensions (such as the 'International Classification of Nursing Practice (ICNP) to SNOMED CT' extension) as separate release packages. The National Library of Medicine (NLM) publishes the US Edition as a single release package, while NHS England (UK) currently publishes the UK Clinical Edition and the UK Drug Extension as separate release packages.

<figure><img src="https://3979592733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3RKZIWpWFT0ocCgNT16E%2Fuploads%2Fgit-blob-180a8f9def1bc7bfaadc047e7febb35985f4cf98%2F57815194.png?alt=media" alt=""><figcaption><p> Release packages published by SNOMED International</p></figcaption></figure>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=4.5%20Release%20Packages" 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-extension-guide/4-logical-design/4.5-release-packages.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.