 |
Page History
...
Special Case | How to handle | ||||||||
|---|---|---|---|---|---|---|---|---|---|
The NCI Thesaurus differs from other OWL formatted resources and as a result you should follow this documentation. | |||||||||
OWL terminologies do not normally require special handling, but LexEVS offers some advanced loading options users may take advantage of. | |||||||||
Terminologies in RRF format typically come from the National Library of Medicine's (NLM) Unified Medical Language System (UMLS). Many terminologies are a subset of the UMLS such as LOINC, SNOMED, MedDRA, HUGO, GO, and ICD to name a few. The terminology you're interested in is a subset of the UMLS if:
| |||||||||
| Loading Asserted Value Set Definitions and Indexes | Source Asserted Value Set Loads require that value set definitions based on source asserted value sets be loaded. Supporting Indexes for searches on these value sets also need a separate load from the source terminology load (At the moment this is focused on the NCI Thesaurus.) | ||||||||
| Loading the Graph Database into ArangoDb for a Given Terminology | LexEVS supports use of a graphing database, ArangoDb for high speed graph resolution of its relationships. These can be loaded from any terminology in the current LexEVS terminology service. The graphs are loaded from the table of associations persisted into the LexGrid data model in MySQL and can be accessed from either a REST graph service or a client service the NodeGraphResolutionService. It is meant to supplement, but not replace, the LexEVS CodedNodeGraph API. | ||||||||
None of the above match and you cannot find a suitable source format. | Many terminology providers produce more than one source format that can be downloaded. Source formats such as text only, CSV, tab delimited, and spreadsheets are not acceptable source formats for LexEVS. If you can not find an acceptable source format for a terminology to load into LexEVS then one option is to download versions that have been placed on BioPortal
|
...
