Skip to end of metadata
Go to start of metadata

The release file naming convention specified in this section applies to all SNOMED International release files starting with the January 2010 International release. The release package naming convention specified was added subsequently to provide additional clarity through a structured name applied to the folder (and zip archive name) containing a set of release files. This package naming convention first applied to releases by SNOMED International during 2017.

These naming specifications provides the following benefits:

  • A consistent naming convention across the International edition and each National edition.

  • Predictable file naming, providing a stable structure for naming over time between releases.
  • A standard way to identify the source country and namespace of the organization responsible for a release file .

  • A consistent mechanism for representing version of release files and packages of release files.
  • An human readable way to identify the content of a file, at a summary level.
  • A mechanism for identifying the type of information stored in a release file(e.g. documentation, tooling, etc.).

  • Guidance on file naming for release files in non-English extensions.

  • Assurance that file names will be unique across the International release and releases from individual National release centers and across separate releases from each center over time.

  • An upgrade path, to enabled use of the same naming convention to be applied to both release files using the current  release format( RF2), as well as the earlier release format ( RF1) while also enabling easy identification of which format is used in eavh file.

Quality Assurance checks, to ensure that this naming convention is enforced, will be performed as part of the International release process. Equivalent checks should be performed as part of each National Release Center's release process.


Prior to January 2010 other naming conventions were used. Implementers who need to review earlier releases should consult the documentation that accompanied the release that they need to review

  • No labels