Page History

The following rules apply to all 

• Gloss
  t SNOMED CT Release Files

   are

In RF2, release files will be named predictably and in such a way as to avoid naming clashed between files in the International release and National releases.The basic pattern for SNOMED CT release file names consists of five elements, separated by an underscore ("_"), followed by a full stop (".") and a file extension :
Full details of the file naming convention can be found in the " SNOMED CT File Naming Convention" document(see associated documentation).All release files :

• are UTF-8 encoded, tab delimited text files.
• contain a column header row, providing field names for each column within the file. Lower camel case is used for the field names (e.g. moduleId, effectiveTime ).
• use DOS style line termination. Each line is terminated Each line, including the final line, ends with a carriage return character (hex 0D) followed by a line feed character (hex 0A).Should have a last line that ends with a line terminator (CR/LF) before the end of file
• The first line of each file, contains the names of each column (also know more generally as a field).
• Field names are represented using lower-camel-case
  • First letter of name is lower case
  • First letter of each words apart from the first word in the name is upper case
  • All other letters are lower case.
  • For example:
    • id
    • term
    • typeId
    • relationshipGroup
    • definitionStatusId
• The name, datatype and usage of the fields in each file are specified in the following sections of this guide
  • 4.2 File Format Specifications
  • 5.2 Reference Set Types.