SNOMED Documentation Search


 Other Documents
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Current Version - Under Revision

The

$gterm

files to be imported should all be selected from the set of files representing a single

$gterm

for a chosen version of the

$gterm

.

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

$gterm

and metadata about

$gterm

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...

$gterm

The primary

$gterm

of

$gterm

. Essential for all implementations.

sct2_description_ [rt] _INT...

$gterm

 

sct2_relationship_ [rt] _INT...

$gterm

 

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

Language

$gterm

(s)

At least one Language

$gterm

must be imported. The English Language

$gterm

should be imported unless another Language

$gterm

covering the full content is available and imported.

Table 8. Highly recommended import files

 

 

 

File type

Content

Notes

der2_cRefset_AttributeValue [rt] _...

$gterm

Inactivation

$gterm

Provides information about the status of

$gterm

.

 

$gterm

Inactivation

$gterm

Provides information about the status of

$gterm

.

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

$gterm

$gterm

codes, other

$gterm

to

$gterm

Only required if the server needs to be able to lookup

$gterm

based on a

$gterm

$gterm

or

$gterm

.

 

Maps from legacy

$gterm

3 codes to

$gterm

Only required if the server needs to be able to lookup

$gterm

based on a legacy

$gterm

3 code.

WordEquivalents

 

 

StatedRelationships

 

 

Table 10. Supplementary import files

 

 

 

File type

Content

Notes

DescWordKey

 

 

DescDualKey

 

 

ExcludedWords

 

 

TransitiveClosure

 

Generated from the

$gterm

. Needs to be regenerated or updated if

$gterm

are imported.

If

$gterm

are required to support an implementation, the

$gterm

to be imported should be selected from the set of files for a single

$gterm

for a chosen version of that

$gterm

. It is important to ensure that the

$gterm

version(s) on which all the imported

$gterm

are based has also been imported. The files that need to be imported from a chosen

$gterm

may vary depending on the scope of the

$gterm

.

Note: Advice should be sought from the

$gterm

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


Feedback
  • No labels