EVS 3.x Retirement
Overview of EVS
NCI Enterprise Vocabulary Services (EVS) provides controlled vocabulary that is the semantic base for caCORE, CORE infrastructure, and caBIG® tools and collaborations. Activities include terminology development, terminology licensing, software development and licensing, and operations support. Projects center on development and maintenance of vocabulary and servers. EVS is a collaborative effort of the NCI Center for Biomedical Informatics and Information Technology (CBIIT) and the NCI Office of Communications.
EVS develops and provides operations support for two broadly used vocablary sources for cancer research: the NCI Thesaurus (NCIt), a cancer-focused terminology, and the NCI Metathesaurus (Meta), a mapping of concepts to terms in multiple vocabularies.
EVS also conducts the Biomedical Grid Terminology (BiomedGT) project to enlist participation in developing an open, federated ontology covering translational research. EVS has developed tools to support collaborative community-based ontology development, and is actively seeking subject matter experts from across biomedicine as contributors to BiomedGT.
In addition, EVS licenses and serves third party terminology as needed to meet NCI and caBIG requirements; hosts and contributes to other standards; and works with vendors to create and improve tools for vocabulary development, curation and deployment. EVS from its beginning has sought to address the broad spectrum of terminology needs at NCI.
Architecturally the EVS terminology service is a component of caCORE. The LexEVS 4.2 service is the current release, and LexEVS 5.0 is under development. With that release, the caCORE 3.x APIs and EVS 3.x Grid services will be retired. Refer to the retirement announcement for details.
The EVS/caCORE 4.x service supports the new distributed LexBIG API as well as the older caCORE 3.2 EVS API. Both are supported by the LexBIG server. Because adoption of the LexBIG terminology server is a major change for EVS users, we are continuing to operate the original caCORE 3.2 server as well as the newer EVS/caCORE 4.x server. For both, the caCORE client side APIs provide an open, publicly available, unified interface to EVS services. Effective with caCORE 4.1 EVS surfaced a terminology service node based on the caCORE 3.2 EVS API on caGrid 1.1.
The underlying software code, object model, use cases, and user documentation are available for use under an open-source license. Developers are encouraged visit the EVS download page for the relevant files and licensing information.
The following Enterprise Architect example files are available.
- Enterprise Architect generated HTML version
- EVS Enterprise Architect EAP File
- EVS XMI Model File
Availability of earlier releases
Files from caCORE EVS version 4.1.x, 4.0, 3.2.1, 3.1, 22.214.171.124, 126.96.36.199, 3.0.1, 3.0 are made available for download from the EVS Archives. Note that the 4.x license terms still apply.
The EVS Grid Service 1.0 (pointing to the caCORE 3.1 EVS Services) is still available. It will be decommissioned with next major release of the LexEVS (v5.0). Therefore, the EVS Team encourages migration to the current release of the LexEVS Grid Service (v4.2). As of the 4.1 Release of the EVS Grid Service, the service is no longer part of the caGrid infrastructure and has been deployed as a separate unit. For access to the EVS 4.1 Grid Service, visit the EVS Archives. Note that the 4.x license terms still apply.
Semantics of NCI Terminology (NCIt)
NCIt provides four features which together provide proven sufficient basis for the semantic integration of the caCORE. These four features are:
- Permanent, non-semantic concept codes
- NCI preferred terms for each concept
- English language definitions
More complete description of the semantics of NCIt has been posted. A document briefly describing the editorial policies governing change to NCIt content is included with the semantics information.
Using the EVS Wiki
This is the wiki home page for the EVS products. EVS developers may edit this page and any user may add a comment.