# Release Package Naming Conventions

## Overall Package Naming Pattern

<sub><mark style="color:blue;">SnomedCT<mark style="color:blue;"></sub><sub>\_\[</sub><sub><mark style="color:blue;">Product<mark style="color:blue;"></sub><sub>]\[</sub><sub><mark style="color:blue;">Scope<mark style="color:blue;"></sub><sub>(optional)]\[</sub><sub><mark style="color:blue;">Format<mark style="color:blue;"></sub><sub>(optional)]\_\[</sub><sub><mark style="color:blue;">ReleaseStatus<mark style="color:blue;"></sub><sub>]\_\[</sub><sub><mark style="color:blue;">ReleaseDate<mark style="color:blue;"></sub><sub>]T\[</sub><sub><mark style="color:blue;">ReleaseTime<mark style="color:blue;"></sub><sub>]\[</sub><sub><mark style="color:blue;">TimeZone<mark style="color:blue;"></sub><sub>]</sub>

<sub>*e.g. SnomedCT\_InternationalRF2\_PRODUCTION\_20250701T120000Z.zip*</sub>

## Package Name Elements

<table data-header-hidden data-full-width="true"><thead><tr><th width="154.46484375"></th><th width="135.8046875"></th><th></th></tr></thead><tbody><tr><td><strong>Element</strong></td><td><strong>Values</strong></td><td><strong>Description</strong></td></tr><tr><td>Product</td><td>&#x3C;any></td><td>Camel case short title sufficient to identify the product.</td></tr><tr><td>Scope (optional)</td><td>Edition</td><td>The release files included in the package fully resolve all dependencies of all modules included in the package.</td></tr><tr><td>Scope (optional)</td><td>Extension</td><td>The release files included in the package needs to be combined with the International Edition release package and any other packages required to resolve the dependencies declared by the Module Dependency Reference Set.</td></tr><tr><td>Format (optional)</td><td>RF1</td><td>Required for any release packages containing Release Format 1 files.</td></tr><tr><td>Format (optional)</td><td>RF2</td><td>Current value for all release packages.</td></tr><tr><td>Format (optional)</td><td>&#x3C;other></td><td>Other values may be specified in future.</td></tr><tr><td>ReleaseStatus</td><td>ALPHA</td><td><p>The package is an alpha release package, which is defined as a SNOMED CT release package made available only for initial review and testing by implementers and other stakeholders.</p><p><strong>Notes</strong></p><ul><li>An <em>alpha release package</em> must not be used in production clinical systems or in clinical settings. This includes Affiliate Licensees or any third parties, except those who have formally committed to test it.</li><li>An <em>alpha release</em> is used to test the format and content of the SNOMED CT release. Feedback is elicited and changes are made prior to publication of the beta release.</li><li><em>Alpha releases</em> were formerly known as a technology preview releases.</li></ul></td></tr><tr><td>ReleaseStatus</td><td>BETA</td><td><p>The package is a beta release package, which is defined as a SNOMED CT release package made available for review and testing only.</p><p><strong>Notes</strong></p><ul><li>Implementers and other stakeholders review and test the <em>beta release</em>.</li><li>The <em>beta release package</em> is made available prior to the production release. It must not be used in production clinical systems or in clinical settings. This includes Affiliate Licensees or any third parties, except those who have formally committed to test it.</li><li>The <em>beta release</em> status indicates it is expected to subsequently be confirmed as a production release. If there is significant issue in format or content, it may be withdrawn, or replaced with an updated <em>beta release package</em>. Whether or not it becomes a production release is decided shortly before the due date for the next release. If a <em>beta release</em> is subsequently confirmed as a production release, all updates are fully version-tracked from the date of the <em>beta release</em>.</li><li>Beta releases were formerly known as candidate baseline releases.</li></ul></td></tr><tr><td>ReleaseStatus</td><td>PRODUCTION</td><td><p>The package is a production release package, which is defined as a final, formally endorsed SNOMED CT release package intended for live use in appropriately licensed operational systems.</p><p><strong>Notes</strong></p><ul><li>A <em>production release package</em> represents the authoritative release of the product. Implementers can use it in operational clinical systems.</li><li>The <em>production release</em> status indicates that the releasing party (SNOMED International or the owner of the extension) commits to maintain the release history. Thus the historical audit trail is maintained through the product's lifetime.</li></ul></td></tr><tr><td>ReleaseDate</td><td>YYYYMMDD</td><td>The package release date formatted in accordance with ISO-8601.</td></tr><tr><td>ReleaseTime</td><td>HHMMSS</td><td>The package release time formatted in accordance with ISO-8601.</td></tr><tr><td>TimeZone</td><td>Z</td><td>The package timezone formatted in accordance with ISO-8601.</td></tr></tbody></table>

<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%20Package%20Naming%20Conventions" 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.3-naming-conventions-for-release-packages-and-files/3.3.1-release-package-naming-conventions.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.