NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Made this page more 508-compliant, by replacing each JIRA macro with a link.

Page info
title
title

Panel
titleContents of this Page

Table of Contents
maxLevel3
minLevel2

LexEVS 6.4.1 CTS2 Overview of Changes

LexEVS 6.4.1 CTS2 release consisted of the following changes:

(red star)CTS2 API Documentation

Interactive CTS2 API Documentation has been updated and is available for LexEVS CTS2 6.3.

  • Note that issue LEXEVSCTS2-21 has been resolved and allows for value set names greater than 50 characters. 

Entities Active Flag

The previous version of the CTS2 service (LexEVS 6.2) was updated to accept an "active" flag for entities.  As a side effect of this change, the default behavior of LexEVS API was inadvertently changed.  In 6.3, the default behavior was changed to return "active" and "inactive" entities by default.  

  • Jira
    serverNCI Tracker
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-811
     
  • Jira
    serverNCI Tracker
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVSCTS2-29

The two options for the active flag are:

  • ACTIVE_ONLY - The inquiry only applies to ACTIVE entries.
  • ACTIVE_AND_INACTIVE - The inquiry applies to both ACTIVE and INACTIVE entries

Property Qualifier Support

Property Qualifiers (property to property relationships) are now being returned by the CTS2 RESTful service in XML and JSON formats.

 

http://<base url>/codesystem/Automobiles/version/1.0/entities?active=ACTIVE_AND_INACTIVE 
Code Block
titleExample Call
Code Block
titleEntities - Active Only
http://<base url>/codesystem/AutomobilesNCI_Thesaurus/version/114.005d/entity/entitiesC12435?activeformat=ACTIVE_ONLY
Code Block
titleEntities - Active and Inactive
json

Default URI Resolver

The default URI Resolver that CTS2 points to is now an internal URI Resolver at NCI.  This removed the dependency on an external URI Resolver being active.

Parameterize the URI Resolver service URL

Allow the end user to specify the URL of the URI Resolver service in a property file rather than hard coded in code.