NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column
width35%
Panel
titleContents of this Page
Table of Contents
maxLevel2
minLevel2
Column

Include Page
VKC:VKC Quick Links to Include
VKC:VKC Quick Links to Include

Multiexcerpt
MultiExcerptNameLexEVSAtaGlance
Panel
titleAt a Glance Details
  • Version Number and Release Date: v6.0.4 April, 2012
  • Primary audience: System administrators (Server); Developers (API)
  • Installation Level: Intermediate - technical assistance may be required, download may require supporting infrastructure or software
  • System Requirements: Refer to Prerequisite Software and Supported Platforms.

 

 

Tool Overview

Multiexcerpt
MultiExcerptNameLexEVSSummary

 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 and grid environments. The LexEVS API serves users who want programmatic access to the data made available by LexEVS.

LexEVS 6.0 is the current embodiment of work started under the LexBIG project (LexGrid Vocabulary Services for caBIG®). This technology has been 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. 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 either controlled terminologies available from the NCI EVS Project or their own 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 for their own organization. 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.

...