User Tools

Site Tools


documentation:athena:import_snomed

This is an old revision of the document!


Import data from SNOMED vocabulary.

The source SNOMED vocabulary can be acquired from SNOMED. Also, SNOMED is included in UMLS. Both of this resources are suggested to be used in the import process.

Local copy of the vocabulary will be used to extract the concepts, and the UMLS web API will be used for additional concept analysis. The advantages of this approach are:

  • If the SNOMED vocabulary has been updated, we can process it, and we do not have to wait the next UMLS update.
  • Less load on web API.
  • Still we can use UMLS knowledge about the SNOMED vocabulary, especially in cross-vocabulary relations.

We'll start from the basic import process, which will give additional knowledge about the process itself.

The import process

Each concept in the source dictionary can be:

  • Identified
  • Validated

In current scope, identification means that OMOP and UMLS already have info about current context. When the Concept is identified, it can be validated. Each Concept is described by its type, set of attributes and relations with other Concepts. During the validation process, we must compare the Source and UMLS Concepts description to OMOP. If the translation can be performed to both directions, without data integrity and validity violation, we can say that the Concept is valid.

Identification

To identify the Concept we must:

  1. Search OMOP by the “CONCEPT_CODE”
  2. Query the UMLS by web API.
documentation/athena/import_snomed.1427877957.txt.gz · Last modified: 2015/04/01 08:45 by gleb_malikov