 |
Page History
...
| Info |
|---|
| Standards for terminology service interoperability have long been a goal of standards organizations. With Common Terminology Services Release 2 -- Two standards organizations, Health Level 7 and the Object Management Group have jointly released both a comprehensive standard and a specification and done so under a structured operating agreement designed to provide workable standards to the community of users. At the same time, as a single Java API, LexEVS has perhaps become the most comprehensive terminology service API in the ontology world. This release of LexEVS focuses on wrapping a CTS2 compliant REST service over the LexEVS API. This CTS2 compliant wrapper provides core support of the Common Terminology Service - Release 2 functionality as described in the OMG CTS2 specification. |
CTS2 References on this Wiki
Additional Functionality
Also included in this package:
...
| Tip |
|---|
For help with a migration from previous releases, refer to the LexEVS 6.0 Migration Tips for 5.x Users. To see any of the previous releases, refer to the LexEVS Release Roadmap. |
CTS2 References on this Wiki
...
. |
...
LexEVS Summary
| Wiki Markup |
|---|
{multi-excerpt:name=LexEVSSummary}
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.1 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|https://wiki.nci.nih.gov/x/paSl] 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|http://ncicb.nci.nih.gov/download/evsportal.jsp] 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 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.
{multi-excerpt} |
...
