Release File Specification

Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 4

changes.mady.by.user Jon Zammit

Saved on

compared with

New Version Current

changes.mady.by.user Peter G. Williams

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Table width manager
Col140px,1*
Sizefs8


ValueUsage
Concept

The file conforms to the 4.2.1 Concept File Specification and contains data related to a set of

Gloss
PreSpacefalse
tconcepts
.

Relationship

The file conforms to the 4.2.3 Relationship File Specification and contains

Gloss
PreSpacefalse
trelationships
that represent the
Gloss
PreSpacefalse
tdistribution normal form
Gloss
PreSpacefalse
tinferred view
of a set of concept definitions.

sRefset

The file conform to the single string reference set format. This only applies to the OWL Expression Reference Set and followed by the content sub-element _OWLExpression which contains stated

Gloss
tconcept definitions
represented as
Gloss
tOWL axioms
and additional
Gloss
tOWL ontology
information.

Description

The file conforms to the 4.2.2. Description File Specification and contains at set of

Gloss
PreSpacefalse
tdescriptions
with description types
Concept
ShowPartsterm
t900000000000013009 Synonym
and
Concept
ShowPartsterm
t900000000000003001 Fully specified name
.

Note that both these description types have a maximum

Specref
PreSpacefalse
tterm
length of 255 characters.

TextDefinition

The file conforms to the 4.2.2. Description File Specification and contains at set of

Gloss
PreSpacefalse
tdescriptions
with description type .

Note: This description type has a maximum

Specref
PreSpacefalse
tterm
length of 4096 characters.

StatedRelationship

The file conforms to the 4.2.3 Relationship File Specification and contains

Gloss
PreSpacefalse
trelationships
that represent the
Gloss
PreSpacefalse
tstated view
of a set of concept definitions.

Note: It is likely this file will be phased out and replaced with a reference set containing a richer OWL representation of stated concept definition.

Identifier

The file conforms to the 4.2.4 Identifier File Specification.

Note: This file does not contain any data rows in the International Edition.


...

Table width manager
Col140px,1*
Sizefs8


ValueDescription
RefsetThe file conforms to the 5.2.1.1 Simple Reference Set specification and contains the members of one or more simple reference sets.
<pattern>Refset

The file conforms to the 5.1.1 Basic Reference Set Member File Format and include one or more additional columns, The number and order of the columns and their basic data types are specified by the <pattern> which precedes Refset.

The <pattern> consists of a sequence of lowercase letters each of which represent an additional column with a datatype specified by the letter as listed below

Pattern letter


c

A SNOMED CT component identifier (

Gloss
PreSpacefalse
tSCTID
) referring to a concept, description or relationship.

iA signed integer.
s

A UTF-8 text string.

Examples


Table width manager
Col140px,1*
Sizefs8


FileTypeValue and Description
doc

The title of the document in CamelCase, abbridges if necessary to fit within the length constraint.

Note: Abbreviations should not be used unless they are essential to fit the title within the available length.

Examples of ContentType for Documents

  • doc_SnomedDecisionSupport_Current-en-US_INT_20170331.pdf (Title: Decision Support with SNOMED CT)
  • doc_SearchDataEntryGuide_Current-en-US_INT_20171122 (Title: SNOMED CT Search and Data Entry Guide) 

res

tls

The value of the ContentType element may be determined on a case-by-case basis but, in conjunction with the ContentSubType element, should be adequate to identify the content and purpose of the file.


...

Table width manager
Col140px,140px,1*
Sizefs8


Sub-elementsValuesDescription
Summary


An optional short camel case summary of the usage of the file. The value of this sub-element may be determined on a case-by-case basis but, in conjunction with the ContentType element, should be adequate to identify the content and purpose of the file.

Examples:

  • For references sets a brief indication about the type or purpose the reference set(s) in the file.

Note: If there is a summary the ReleaseType or DocStatus follows this Summary sub-element immediately without a space or other separator.

ReleaseTypeFullThe file contains the Full view of the components or refset members within its scope (i.e. every version ever released).
SnapshotThe file contains the Snapshot view of the components or refset members within its scope (i.e. only the most recent version released).
DeltaThe file contains the Delta view of the components or refset members within its scope (i.e. only additions/changes since previous release).
LanguageCode


Where it is necessary to specify the language or dialect used in a file, the appropriate language code must be included as the final sub-element of the ContentSubType. If a Summary or DocStatus sub-element is also included, the LanguageCode must be added after the last of those sub-elements and must be separated from it by a hyphen.

Representation of the LanguageCode

The language is specified with a 2 character ISO 639-1 language code (e.g. es = Spanish, fr = French, da = Danish). If necessary, a dialect code is added after the langauge language code and seperated separated from it by a hyphen.

Depending on the specificity required the dialect code comes from one of two sources:

  • If the dialect is general to an entire country, the two-letter ISO-3166 alpha-2 country code is used to specify the dialect (e.g. en-US = US English, en-GB British English)

  • If dialect is less common or not country specific, the IANA language subtag should be used. Note this code consists strings of lower case letres letters. IANA is the Internet Assigned Numbers Authority.

This approach follows Internet conventions.


...