NIH | National Cancer Institute | NCI Wiki  

LexEVS and its data model LexGrid comprise a full function terminology service meeting a wide range of requirements. The Common Terminology Service 2 is a comprehensive standard defined by a broad range of community interests.

  • The LexEVS 6.7.0 implementation updates code compatibility to Java 17 including use of Spring 6, Hibernate 6, updates to Ehcache and other dependencies.  CTS2 is deprecated and it's latest version v2.30 may not be deployed before end of life.  
Contents of this Page

(red star)CTS2 Rest Client Quick Start for 6.5.1 (CTS2 for 6.7.0 is not deployed)

Refer to LexEVS 6.x CTS2 API Quick Start for information and a set of examples for the CTS2 REST implementation over LexEVS.

(red star)CTS2 API Documentation for 6.5.1 (CTS2 for 6.7.0 is not deployed)

Interactive CTS2 API Documentation has been updated and is available for LexEVS CTS2 6.5.1 (Deprecated).  It is available here:

LexEVS 6.5.1 CTS2  (CTS2 for 6.7.0 is not deployed)

Refer to LexEVS 6.5.1 CTS2 documentation for information on changes made in LexEVS 6.5.1 CTS2.

The URI Resolver (Removed from Service)

Given the RESTful nature of CTS2 along with the possibility of distributed queries over multiple terminology nodes, the need for canonical naming conventions around URI, IRI or URL becomes paramount.  To serve this purpose a URI resolving service has been built for CTS2 over LexEVS.  This service attempts to provide a canonical name in the form of a URI based on curated convention and dependent upon the comprehensive storage of know other URIs known for a given terminology.   As such this service provides some securely robust resolution of a given resource despite it's possible use of an alternative URI.  

URI Design Statement

URI Architecture

URI Whitepaper (pdf download)

Installing CTS2 as a Service

Refer to the instructions for installing your own CTS2 over LexEVS service. (Deprecated.  6.7.0 will have streamlined installation.)



  • No labels