Release Package Naming Conventions

Overall Package Naming Pattern

_{SnomedCT_[Product][Scope(optional)][Format(optional)]_[ReleaseStatus]_[ReleaseDate]T[ReleaseTime][TimeZone]}

_{e.g. SnomedCT_InternationalRF2_PRODUCTION_20250701T120000Z.zip}

Package Name Elements

Element	Values	Description
Product	<any>	Camel case short title sufficient to identify the product.
Scope (optional)	Edition	The release files included in the package fully resolve all dependencies of all modules included in the package.
Scope (optional)	Extension	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.
Format (optional)	RF1	Required for any release packages containing Release Format 1 files.
Format (optional)	RF2	Current value for all release packages.
Format (optional)	<other>	Other values may be specified in future.
ReleaseStatus	ALPHA	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. Notes An alpha release package 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. An alpha release 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. Alpha releases were formerly known as a technology preview releases.
ReleaseStatus	BETA	The package is a beta release package, which is defined as a SNOMED CT release package made available for review and testing only. Notes Implementers and other stakeholders review and test the beta release. The beta release package 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. The beta release 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 beta release package. Whether or not it becomes a production release is decided shortly before the due date for the next release. If a beta release is subsequently confirmed as a production release, all updates are fully version-tracked from the date of the beta release. Beta releases were formerly known as candidate baseline releases.
ReleaseStatus	PRODUCTION	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. Notes A production release package represents the authoritative release of the product. Implementers can use it in operational clinical systems. The production release 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.
ReleaseDate	YYYYMMDD	The package release date formatted in accordance with ISO-8601.
ReleaseTime	HHMMSS	The package release time formatted in accordance with ISO-8601.
TimeZone	Z	The package timezone formatted in accordance with ISO-8601.