Page History
https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/LexEVS_Highlights
The following information was designed to give an overview of the functionality contained within the Lexical Grid Enterprise Vocabulary Services (LexEVS). As a beginner or experienced terminologist you will find this information useful when choosing if the LexEVS services are right for your institution or application.
Each area of LexEVS is broken down with its primary value proposition and additional items for you to consider.
Service Area | Main Functions | Additional Functional Qualification | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Model: The LexGrid model is Mayo Clinic's proposal for standard storage of controlled vocabularies and ontologies. These are the high-level objects incorporated into the model definition. |
|
| ||||||||
Authoring - The APIs provide the capability to author a Code System and its contents. |
|
| ||||||||
Versioning - An ordered collection of state changes that define the transformation of a set of resources from one consistent state to another. |
|
| ||||||||
CTS - Comprehensive support for Common Terminology Services. |
|
| ||||||||
Mapping - Concept, Instance, or Association mapping between two different ontologies. |
|
| ||||||||
Value Set - Value Set Definition within the LexGrid logical model defines the contents of a Value Set. The contents are coded entities defined in the referenced Code System. |
|
|
|
|
Panel | |
---|---|
LexEVS includes predefined exporters. | * LexGrid XML exporter with filter functionalities
|
OWL/RDF exporter | Supports the versioning of concepts, value sets, and terminologies.
Panel | |
---|---|
LexEVS provides a set of query services and APIs | * By Entity - Code Node Set.
|
Value Set Query API - provides capability to query Value Sets available in the LexEVS system and also to query the binding between Value Set and concept domain. | Provides answers to queries concerning the LexEVS system capabilities, terminologies supported, relationship types, search algorithms, and versions.
Panel | |
---|---|
LexEVS provides a couple of web services. | * SOAP |
REST | Prototype functionality provided prior to and including LexEVS 6.0.
Panel | |
---|---|
LexEVS provides extendability through a pluggable framework for use locally or as contributions to the community via open source. | * The LexEVS APIs, the core APIs, fall into three primary categories:
|
Preliminary CTS2 API: provides programmatic access to LexEVS 6.0 implementation of CTS 2 features and services. Developers can build custom applications, tools, and services that can make calls as per CTS 2 specification against LexEVS CTS 2 API. Visit Common Terminology Services 2 for services description, purpose and scope of CTS 2 specification. | LexEVS uses an open architecture supporting extensions created by external organizations.
Panel | |
---|---|
LexEVS supports the semantic web. | * OWL/RDF loader and API.
|
OWL/RDF exporter can export an ontology to a triple store, based on Jena 2.6.3. | Import and export functions can be executed via APIs, command line, or GUI. |
Panel | |
---|---|
Relevant non-functional attributes are typically covered by the underlying architecture. | * Security
|
License | Custom security implementation configurable per Coding System in a distributed environment.
Panel |
---|
- Install instructions contain recommended approaches for certain database management systems.
- Conforms to licensing needs. |