This section includes information about covers several general topics related to SNOMED CT release file
and including:
The following two sections provide detailed specification specifications of release file is provided in the two section that follow this one: the release files.
- Section 4 3. Component Release Files SpecificationFiles contains details of release files that represent the main SNOMED CT components:
Concepts
Descriptions
- Relationships
4. - Section 5 Reference Set Release Files Specification
Files that can be used to contains details of release files that customize and enhance SNOMED CT by representing:- Subsets of concepts and descriptions
- Maps to other code systems
- Language and dialect preferences for different terms
- Annotation of components
- Associations between components
- Other forms of configuration and extensibility
...
Info |
---|
title | Historical Note on Current and Previous Release File Formats |
---|
|
The standard format in which Gloss |
---|
SpacePreSpace | truefalse |
---|
t | SNOMED CT |
---|
| has been distributed since 2012 is known as Gloss |
---|
PreSpace | false |
---|
t | Release Format 2 |
---|
| (RF2). It was developed in response to extensive feedback on the original release file format, now known as Gloss |
---|
PreSpace | false |
---|
t | Release Format 1 |
---|
| (RF1), in which Gloss |
---|
SpacePreSpace | truefalse |
---|
t | SNOMED CT |
---|
| was distributed between its first release in 2002 and 2012. The SNOMED CT International Edition RF1 format is now deprecated and no longer supported or distributed in RF1. However, a conversion tool to general RF1 style files from the RF2 release files is available. The key enhancements in were: - More robust and consistent version representation;
- Inclusion of a moduleId and module dependency mechanism, which together enable modularization of releases while representing dependencies between modules;
- to provide an extensible and versionable way to configure Including support for subsets, maps, annotations, alternative hierarchies, etc.;
Use of an added to represent metadata about the structure of itself.
In common with the earlier release format specifies files that: Represent the components of : Provide standard representations for subsets, language preferences and maps to other codes and classifications. Are distributed as tab-delimited text files - which represent character content in accordance with the Unicode UTF-8 specification; Use Gloss |
---|
Space | true |
---|
t | SNOMED CT Identifiers |
---|
| as the permanent of released core components; Support to the Gloss |
---|
Space | true |
---|
t | International Release |
---|
| using allocated to licensees to denote the provenance of added components and to ensure uniqueness. . |