NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...

Panel
titleDocument Information
Document Information

Author:

Traci St.Martin/

Craig Stancl
Email:

stmartin.traci@mayo.edu, stancl.

Stancl.craig@mayo.edu
Team: LexEVS
Contract:

CBIIT

CBITT BOA

Subcontract #29XS223

Subcontract# 29XS223
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Sign off

Date

Role

CBIIT or Stakeholder Organization

 

Larry Wright

5/6/2010

NCI PO & EVS Product Manager

CBIIT: NCI EVS & Semantic Infrastructure

Jason Lucas

5/6/2010

EVS Software Project Manager

 

   
    
    

Sherri de Coronado

5/7/2010

NCI PO

CBIIT: NCI EVS & Semantic Infrastructure

The purpose of this document is to collect, analyze, and define high-level needs and features of the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) caCORE LexEVS Release 6.01. This document focuses on the functionalities functions proposed by the product stakeholders and target users in order to make it a better product. The use-case and supplementary specifications document will detail how the framework will fulfill these needs.

...

The objective of this release of the LexEVS API is to design and construct a reference implementation of the CTS2 specification, leveraging LexEVS as the basis for the design and code base.

This release will address support for value sets, mappings between code sets, support for creation of local extensions to code sets and support related to content creation and editing.

Current Solution

LexEVS 5.1 currently supports much of the functionality called for by the CTS2 Specification.

Proposed Solutions

LexEVS 6.0 will provide the additional functionality to enhance LexEVS to meet the goals of a CTS2 Reference Implementation and requirements of the user communitiesprovide a CTS2 compliant REST API, Enhanced Performance and new loaders.

Functional Requirements

Each enhancement, modification or new feature is described in detail below.

...