NIH | National Cancer Institute | NCI Wiki  

  • Created by Unknown User (stanclcr2), last modified on Sep 19, 2014

LexEVS 6.2

Contents of this Page

Application Overview

LexEVS is the central EVS terminology server, developed by the Mayo Clinic with NCI and other support. LexEVS provides a common terminology model and open access to a wide range of terminologies, terminology value sets, and cross-terminology mappings needed by NCI and its partners. For users wanting to install and run a local instance of LexEVS, the LexEVS server package provides a comprehensive set of software and services to load, publish, and deploy vocabulary in a variety of web-enabled environments. The LexEVS API serves users who want programmatic access to the data made available by LexEVS.

LexEVS 6.3 is the current embodiment of work started under the LexBIG project (LexGrid Vocabulary Services for caBIG®). This technology was adopted as the strategic infrastructure for the caBIG® community and NCI's Enterprise Vocabulary Services (EVS).

NCI's EVS is a big user of the LexEVS services, but there are many others (see EVS Use and Collaborations). You can consume controlled terminologies hosted by NCI's EVS without setting up your own servers to do so. Seeing what NCI has done with EVS is a good way to learn about what LexEVS can do. Refer to the EVS Wiki for further information.

LexEVS provides a collection of programmable interfaces, affording users and developers open access to both controlled terminologies available from the NCI EVS Downloads page and other supported terminologies. NCI's installation of LexEVS is not only a tool for the community to use, but also an example of what developers can build at their own sites. By building an installation of LexEVS, an organization can control the content and have any set or subset of terminologies and mappings. One installation can be used by multiple applications in an enterprise.

LexEVS includes the following components:

  • Terminology Server - An enterprise level terminology server
  • Java API - A Java interface based on the LexGrid Object Model
  • CTS2 1.1 compliant REST interface
  • Distributed API - A Java interface based on the LexGrid data model and relies on a LexEVS Proxy and Distributed LexEVS Adapter to provide remote clients access to the native LexEVS API
  • Developers GUIs - Server administration, query testing, and value set development can be performed by a developer

The name LexEVS highlights the merging of LexGrid, LexBIG, and EVS technologies and designates an entire suite of applications. In this suite, LexGrid is the underlying model for standard storage of controlled vocabularies and ontologies. The LexBIG API is the set of services that EVS adapters use to store and retrieve terminology metadata. LexEVS APIs are a combination of convenience methods and the LexBIG API (combining LexBIG and the EVS adapters into one set of services). For detailed information, refer to the LexEVS architecture overview.

After you have a chance to get familiar with the LexEVS suite, consider looking through the LexEVS 6.2 Functionality Overview. This lays out everything that can be done from a developer's or ontologist's point of view.

Installation and Downloads

The installation overview provides an introduction to the different environments that can be installed. Refer to the LexEVS 6.x Installation Guide for more information.

The LexEVS 6.2 Installation Options identify the download files for each LexEVS environment that can be installed (Local Runtime, Distributed, and Grid Services).

The LexEVS Widget Library lists many widgets that have been developed for use by particular customers. These widgets have been found to be potentially useful to a wider audience. Each widget has a description for you to use in deciding if you'd like to dig deeper and find out the usefulness of the widget in your application.

Unable to render {include} The included page could not be found.

Forum and Support

LexEVS Issues and Discussion  Exit Disclaimer logo
Users and developers can report and discuss issues regarding the LexEVS application on its GitHub site.

What's New in LexEVS 6.2

Updated CTS2 Service to conform to CTS2 1.1

This release of LexEVS focuses updating the CTS2 compliant REST service from the 1.0 to 1.1 version of the CTS2 specification. This updated CTS2 compliant service provides core support of the Common Terminology Services 2 (CTS2) 1.1 Exit Disclaimer logo functionality as described in the OMG CTS2 specification 1.1 Exit Disclaimer logo .

CTS2 References on this Wiki

LexEVS 6.x REST CTS2 Service

LexEVS 6.2 CTS2

Additional Functionality

Also included in this package (refer to LexEVS 6.2 Release Notes):

  • Software component upgrades
  • Implementation of a prototype value set viewer
  • Bug fixes

Simplified Service URL

The service URL for LexEVS has been simplified and will resolve to the latest production service:

http://lexevsapi6.nci.nih.gov/

Contributions

The contribution process is described in LexEVS Community Code Contribution. LexEVS source code is in the NCIP channel of Github Exit Disclaimer logo

Presentations, Demos, and Other Materials

Presentations

Refer to LexEVS Presentations.

Examples

  • Query Service with Program Examples, included in the LexEVS base installation. Both Lexical Set Operations and Graph Operations are included for common vocabulary functions using a sample vocabulary and CodedNodeSet. This is described in the LexEVS 6.x Installation Guide.
  • Example Programs and Verification Test Suite, included in the LexEVS base installation. The Example Programs provide a limited interactive demonstration of LexEVS capabilities. Both are explained in the LexEVS 6.x Installation Guide.
  • LexEVS Example Code zip file. These are code examples for subjects of frequently asked questions such as creating a coded node graph using the LexBIG convenience methods.

Documentation and Training

Related Applications

  • No labels