# Release Types

A SNOMED CT International Release includes three distinct release types. Table 3.2-1 describes the release types and the differences between them.

***

**SNOMED CT Release Types**

<table data-header-hidden data-full-width="true"><thead><tr><th width="123.296875"></th><th></th></tr></thead><tbody><tr><td><strong>Release type</strong></td><td><strong>Description</strong></td></tr><tr><td>Full</td><td>A full release is a release type in which the release files contain every version of every component and reference set member ever released.</td></tr><tr><td>Snapshot</td><td>A snapshot release is a release type in which the release files contain only the most recent version of every component and reference set member released, as at the release date.</td></tr><tr><td>Delta</td><td><p>A delta release is a release type in which the release files contain only rows that represent component versions and reference set member versions created since the previous release date.</p><p><strong>Notes</strong></p><ul><li>Each <em>row</em> in a <em>delta release</em> file represents either a new component or reference set member, or a change to an existing component or reference set member since the previous release date.</li><li>A <em>delta release</em> identifies differences between two versions of the same release package.</li><li>A <em>delta release</em> added to the previous full release is identical to the full release of the new version.</li><li>The previous <em>release date</em>, on which a <em>delta release</em> is based, is usually the date of the most recent previous release. However, that may not always be the case. For example, where interim releases are made between two major releases there may be a combined <em>delta release</em> covering a period since a previous major release<em>.</em></li><li>Delta files have been <strong>removed</strong> from the SNOMED International release package, Managed Service Extensions and Derivative packages. However a Delta Generation Tool is available for those who need it. The Delta Generation Tool allows users to create their own Delta between two fixed release dates - you can find it here: <a href="https://github.com/IHTSDO/delta-generator-tool/releases">https://github.com/IHTSDO/delta-generator-tool/releases.</a></li></ul></td></tr></tbody></table>

***

There are practical use cases for each Release Type.

* The full release allows access to all versions of the release. This is valuable for reviewing data entered using earlier versions and more generally supporting change management.
* The snapshot release only includes the latest version of each component. This can be useful to optimize access to the current version but does not provide access to earlier versions.
* The delta release only includes changes made between one version and the next. This provides a simple way to identify new and changed components to support change management and can also be used to update the previous version of the full release to the new version of the full release. However, the delta release cannot be used as a stand alone resource.

When considering which release type to use, it is worth noting that delta and snapshot views can be readily generated from the full release type. For this reason organizations that maintain SNOMED CT extensions are required to provide the full release type, while distribution of the other release types are optional.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Release+File+Specification&#x26;entry.670899847=Release%20Types" class="button primary">Provide Feedback</a>


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-specifications/snomed-ct-release-file-specification/release-types-packages-and-files/3.2-release-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.