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. | * Coding System - each vocabulary is modeled as an individual Code System, which could be seen as a container for concepts, relationships, properties and meta data.
Pick List Definition - defines an ordered list of entity codes and preferred designations drawn from a resolved Value Set Definition. | Supports synonyms. |
Authoring |
The APIs provide the capability to author a Code System and its contents. | * Create new Code System, Code System Property, Concept, Concept Property, Association (add Qualifiers to the Association), and supplement.
New mapping for an existing mapping scheme. | The LexEVS user interface supports efficient manual use for query and test operations even when operating on large data sets. |
Versioning |
An ordered collection of state changes that define the transformation of a set of resources from one consistent state to another. | * Provides release information about content loaded into the LexEVS system.
Versionable Entities are the resources that can undergo change over time while maintaining its identity. All the LexGrid elements that can undergo changes such as Entity, CodingScheme, ValueSetDefinition, property, etc. are Versionable Entities. | The version of loaded content can be checked via APIs, command line, or GUI. | |
CTS |
Comprehensive support for Common Terminology Services. | * CTS defines the functional requirements of a set of service interfaces to allow the representation, access, and maintenance of terminology content either locally, or across a federation of terminology service nodes. | * Fully compliant with CTS 1 and soon CTS 2.
Mapping |
Concept, Instance, or Association mapping between two different ontologies. | * LexEVS provides inter-terminology relationship support, authoring, and loading. | * Mapping scheme is loaded independent of the mapped 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. | * Administration - ability to load, export, and remove a Value Set Definition.
Resolve - ability to resolve a Value Set Definition dynamically against selected Code System version and return all Concepts belonging to the Value Set. | Value Sets can contain coded entities from one or more Code Systems. |
Pick List |
Pick List Definition within the LexGrid logical model defines an ordered list of entity codes and corresponding presentations drawn from a resolved Value Set Definition. | * Administration - ability to load, export and remove Pick List Definitions.
Resolve - ability to resolve Pick List Definition dynamically against a selected Code System version and return all concepts or selected concepts belonging to the Pick List. | Pick Lists can be defined using exclusion or inclusion criteria. |
Loaders |
LexEVS includes the loaders listed in this document. | * NCI MetaThesaurus Loader
ICD general equivalence mapping loader | Create custom loaders using the Loader Framework extension. | |
Exporters |
LexEVS includes predefined exporters. | * LexGrid XML exporter with filter functionalities
OWL/RDF exporter | Supports the versioning of concepts, value sets, and terminologies. |
Query |
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. |
Web services |
LexEVS provides a couple of web services. | * SOAP
REST | Prototype functionality provided prior to and including LexEVS 6.0. |
Extensibility |
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. |
Semantic Web |
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. | |
Other |
Relevant non-functional attributes are typically covered by the underlying architecture. | * Security
License | Custom security implementation configurable per Coding System in a distributed environment. |