NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 18

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

Saved on

compared with

New Version 19

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

Saved on

Key

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

 

 

Info

LexEVS and it's 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.

  • 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.
Panel
titleContents of this Page
Table of Contents
minLevel2

LexEVS 6.1 CTS2

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

(red star) CTS2 Rest Client Quick Start

Plus a full 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

as normalized to the OMG group specification is hosted here.

Installing CTS2 as a Service

Instructions for installing your own CTS2 over LexEVS service

LexEVS 6.0 CTS2

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