...

LexEVS 6.3 CTS2 Overview of Changes

LexEVS 6.2 3 CTS2 release consisted of the following changes:

• Interactive CTS2 API DocumentationValue Set Services
• Entities Active Flag
• LexEVS 6.2 CTS2 Alternate Landing Page
• Upgrade to CTS2 1.1 framework
• Updated LexEVS CTS2 Service to the CTS2 1.1 specification as implemented in the CTS2 Development Framework

Additionally, the LexEVS 6.0 CTS2 API code base has been removed in this release.

 CTS2 API Documentation

...

• Note that issue LEXEVSCTS2-21 will affect value set resolution REST calls with value set names greater than 50 characters.  This will be fixed in the next release.

Entities Active Flag

The previous version of the CTS2 service (LexEVS 6.2 CTS2 service accepts ) was updated to accept an "active" flag for entities.   If no flag is present, the LexEVS 6.2 CTS2 service will return only active 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
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-811

   

• Jira
  server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVSCTS2-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

...

http://<base url>/codesystem/Automobiles/version/1.0/entities?active=ACTIVE_AND_INACTIVE

...

INACTIVE