NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 17

changes.mady.by.user Bauer, Scott (NIH/NCI) [C]

Saved on

compared with

New Version 59

changes.mady.by.user Unknown User (stanclcr2)

Saved on

Key

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

 

 

Info

LexEVS and it's 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.0  featured a comprehensive Java implementation of the CTS2 Service Functional Model in it's preliminary form as a Draft Standard for Trial Use. 
  • The final specification of CTS2 was designed as a REST specific API and LexEVS 6.1 has implemented the specification core functionality.
  • 5.1 implementation updates internal framework to include asserted value sets when querying for resolved value sets.
Panel
titleContents of this Page
Table of Contents
minLevel2

(red star)CTS2 Rest Client Quick Start

Refer to LexEVS 6.

...

CTS2 may be implemented as  a service or as a client.  Clients can access terminology data with minimum implementation.

CTS2 Rest Client Quick Start

Plus a full x CTS2 API Quick Start for information and a set of examples for the CTS2 REST implementation over LexEVS: LexEVS 6.1 CTS2 API.

Current State of CTS2

 as implemented in LexEVS 6.1 is outlined in a CTS2 implementation resources site.

The CTS2 REST API in LexEVS 6.1

The OMG CTS2 1.1 Specification is written as a REST based architecture. It can be implemented as a minimal set of modules.

CTS2 design document

OMG CTS2 specification:

defined and hosted by the OMG group.

The HL7 CTS2 Service Functional Model

.

(red star)CTS2 API Documentation

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

LexEVS 6.5.1 CTS2

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

The URI Resolver

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)as normalized to the OMG group specification is hosted here.

Installing CTS2 as a Service

Instructions Refer to the instructions for installing your own CTS2 over LexEVS service

...

.

...

Warning
This implementation, while not CTS2 compliant, still has value as it includes a number of unique features including terminology authoring and version control in a Java API.

LexEVS 6.0 CTS2 Guide

 LexEVS 6.0 CTS2 API