The

International Release
files to be imported should all be selected from the set of files representing a single
Release Type
for a chosen version of the
SNOMED CT International Release
.

Within the chosen file set the files identified in must be imported. The files listed in should also be imported as these provide important information about

inactive concepts
and metadata about
Description
types. The decision on whether to import the files listed in depends on whether the additional features identified in that table are required for the planned implementation. Finally the supplementary files listed in may be used to assist implementation but are not essential as the data they contain can be generated from the other files and/or replaced by alternative approaches to provide similar functionality.

Table 7. Mandatory import files

 

 

 

File type

Content

Notes

sct2_concept_ [rt] _INT...

concepts

The primary

components
of
SNOMED CT
. Essential for all implementations.

sct2_description_ [rt] _INT...

Descriptions

 

sct2_relationship_ [rt] _INT...

Relationships

 

sct2_cRefset_Language [rt] - [lang] _INT...

Language

Refset
(s)

At least one Language

Refset
must be imported. The English Language
refset
should be imported unless another Language
refset
covering the full content is available and imported.

Table 8. Highly recommended import files

 

 

 

File type

Content

Notes

der2_cRefset_AttributeValue [rt] _...

concept
Inactivation
refset

Provides information about the status of

inactive concepts
.

 

Description
Inactivation
Refset

Provides information about the status of

inactive descriptions
.

der2_cRefset_DescriptionType [rt] _INT...

 

 

der2_cRefset_AssociationReference [rt] _INT...

 

 

Table 9. Optional import files

 

 

 

File type

Content

Notes

der2_sRefset_SimpleMap [rt] _INT...

Maps from

NHS
Clinical Terms Version 3
codes, other
Read Codes
to
SNOMED CT

Only required if the server needs to be able to lookup

SNOMED CT concepts
based on a
CTV3
Identifier
or
Read Code
.

 

Maps from legacy

SNOMED CT
3 codes to
SNOMED CT

Only required if the server needs to be able to lookup

SNOMED CT concepts
based on a legacy
SNOMED CT
3 code.

WordEquivalents

 

 

StatedRelationships

 

 

Table 10. Supplementary import files

 

 

 

File type

Content

Notes

DescWordKey

 

 

DescDualKey

 

 

ExcludedWords

 

 

TransitiveClosure

 

Generated from the

Relationships
. Needs to be regenerated or updated if
Extensions
are imported.

If

Extensions
are required to support an implementation, the
release files
to be imported should be selected from the set of files for a single
Release Type
for a chosen version of that
Extension
. It is important to ensure that the
International Release
version(s) on which all the imported
Extensions
are based has also been imported. The files that need to be imported from a chosen
Extension
may vary depending on the scope of the
Extension
.

Note: Advice should be sought from the

Extension
provider on the essential and recommended requirements of files to be imported and supported.