Search



Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

All SNOMED CT release file are named in accordance with the 3.3.2 Release File Naming Convention. The naming conventions result in names that can be decomposed into parts as illustrated by examples with color coding in .in

Caption reference
CapRefIdillustrations-of-the-release-file-naming-conventions
CapRefTypeTable
.

Caption label
CapIdillustrations-of-the-release-file-naming-conventions
CapTypeTable
Illustrations of the Release File Naming Conventions


Description of the pattern or file illustratedExample release file names

General pattern

Footnote Macro

Pattern elements in square brackets [ ] are optional depending on file type.


prefix_[refsetPattern]componentType_[refsetType][extensionName]releaseType[-language]_country_releaseDate.txt
International edition full release concepts file for 2019-07-31sct2_Concept_Full_INT_20190731.txt
International edition snapshot release english descriptions file

sct2_Description_Snapshot-en_INT_20190731.txt

Spanish extension full release spanish descriptions filesct2_Description_SpanishExtensionFull-es_INT_20190430.txt
International edition snapshot release extended maps reference set fileder2_iisssccRefset_ExtendedMapSnapshot_INT_20190731.txt
Spanish extension full release spanish language reference set fileder2_cRefset_LanguageSpanishExtensionFull-es_INT_20190430.txt
International edition snapshot release english language reference set fileder2_cRefset_LanguageSnapshot-en_INT_20190731.txt

File Name Element Relevance to Table Names

Caption reference
CapRefIdrelevance-of-file-name-pattern-elements-to-database-table-names
CapRefTypeTable
 identifies the elements of the release file naming pattern that are relevant to the naming of the database tables containing content from those files. It also outlines the reasons why some elements that form an important part of the release file names can or should be omitted from the relevant database table names. 

Caption label
CapIdrelevance-of-file-name-pattern-elements-to-database-table-names
CapTypeTable
Relevance of File Name Pattern Elements to Database Table Names


Filename ElementRelevant to Table NameExplanation
prefixNoThe prefix sct2 or der2 distinguishes components from derivatives (refsets). This information is present in the componentType and refsetType.
refsetPatternNoThis information relates to the datatypes of additional columns in the file and the table. The table structure includes the required columns so there is no reason to include this in the table name.
componentTypeYesThis is essential as it indicates either the type of components represented in the table or that this is a reference set
refsetTypeYesThis is essential to distinguish the tables representing different reference set types (and not present in other file names).
extensionNameNoThis is not required as data from extensions files should be included in the same tables as the equivalent data from the international release. Individual records maintained in extensions can be distinguished by moduleId
releaseTypeYesThis is essential if importing data from both the full and snapshot release. However, since this is a fundamental grouping, it is probably sensible for this to be a prefix to the table name. Otherwise with long table names this key distinction may be easier to miss. A short prefix denoting release types with a convention that also allows database views to be named in a similar consistent manner is recommended.
languageNoThis is not applicable to the description table name. All descriptions should be accommodated in a single table with the languageCode column indicating the language of the associated term. Similarly it is not applicated to a language reference set table name. All language reference sets should be accommodated in a single table with the refsetId column indicating the language and dialect of each language preference.
countryNoThis is not required in the table name as the country or other point of origin of the components and reference set members is indicated by the moduleId.
releaseDateNoThis is not required as data from many releases is included in the full release file tables. In the case of the snapshot it would be possible to include the date of the snapshot in the table name. However this is not recommended because, as noted in 4.2. Release Type Options multiple sets of tables representing different snapshot releases multiply the required storage capacity required.


Deriving Table Names from Release File Names

The analysis in 

Caption reference
CapRefIdrelevance-of-file-name-pattern-elements-to-database-table-names
CapRefTypeTable
, identifies three elements in the release file name that are relevant to table names. There are various ways in which table names could be derived by combining these elements and one of these is shown in 
Caption reference
CapRefIdrules-applied-to-release-file-names-to-generate-table-name-for-the-example-database
CapRefTypeTable
. The end result (shown in 
Caption reference
CapRefIdresults-of-mapping-release-file-names-to-example-database-table-names
CapRefTypeTable
) is a set of table names that:

...

Note
titleNote

The rules shown here are those applied to the example SNOMED CT database. Alternative table naming patterns may be preferred by those developing their own SNOMED CT database. However, is important is to ensure that the table naming pattern should be consistently applicable to all release files. Furthermore, it also should be readily applicable to any additional reference set types that may be added to future releases of the International Edition (or included in other SNOMED CT editions and or extensions).


Caption label
CapIdrules-applied-to-release-file-names-to-generate-table-name-for-the-example-database
CapTypeTable
Rules Applied to Release File Names to Generate Table Name for the Example Database


Start with file name patternprefix_[refsetPattern]componentType_[refsetType][extensionName]releaseType[-language]_country_releaseDate.txt
Remove element that are not requiredcomponentType[_refsetType]releaseType
Make release type the prefixreleaseType_componentType[_refsetType]

Abbreviate the prefix to 4 characters

(full or snap)

rtyp_componentType[_refsetType]

...


Caption label
CapIdresults-of-mapping-release-file-names-to-example-database-table-names
CapTypeTable
Results of Mapping Release File Names to Example Database Table Names



List of Release File NameList of Corresponding Table Names in the Example Database
sct2_Concept_Full_INT_20190731.txt

Image Modified

sct2_Description_Full-en_INT_20190731.txt
der2_cRefset_AssociationFull_INT_20190731.txt
der2_cRefset_AttributeValueFull_INT_20190731.txt
der2_ciRefset_DescriptionTypeFull_INT_20190731.txt
der2_iisssccRefset_ExtendedMapFull_INT_20190731.txt
der2_cRefset_LanguageFull-en_INT_20190731.txt
der2_ssRefset_ModuleDependencyFull_INT_20190731.txt
der2_cissccRefset_MRCMAttributeDomainFull_INT_20190731.txt
der2_ssccRefset_MRCMAttributeRangeFull_INT_20190731.txt
der2_sssssssRefset_MRCMDomainFull_INT_20190731.txt
der2_cRefset_MRCMModuleScopeFull_INT_20190731.txt
sct2_sRefset_OWLExpressionFull_INT_20190731.txt
der2_cciRefset_RefsetDescriptorFull_INT_20190731.txt
der2_Refset_SimpleFull_INT_20190731.txt
der2_sRefset_SimpleMapFull_INT_20190731.txt
sct2_Relationship_Full_INT_20190731.txt
sct2_StatedRelationship_Full_INT_20190731.txt
sct2_TextDefinition_Full-en_INT_20190731.txt
sct2_Concept_Snapshot_INT_20190731.txt
sct2_Description_Snapshot-en_INT_20190731.txt
... list continues for all Snapshot release files... list continues for all the snap_ tables

...

Display Footnotes Macro