NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (stanclcr2), last modified on Dec 09, 2015

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Document Information

Author:  Craig Stancl, Scott Bauer, Cory Endle
Email:  Stancl.craig@mayo.edu, bauer.scott@mayo.edu, endle.cory@mayo.edu
Team:  LexEVS
Contract:   S13-500 MOD4
Client:  NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Contents of this Page

The purpose of this document is to document the technical face to face meeting details between the NCI and Mayo for the National Cancer Institute Center for Biomedical Informatics and Information Technology (NCI CBIIT) LexEVS Release 6.3 and LexEVS Release 6.4 .

2015 December Face-to-Face Meeting Prioritization List

CategoryTopicNotes
Tech CatalogMigrate to centOS 76.5
Tech CatalogMigrate to Java 8

6.5

Tech CatalogMigrate to Spring 46.5
DevelopmentValue Set Performance - review compiled Value Set Definitions 
DevelopmentTree Performance - determine requirements and propose solution 
DevelopmentCTS2 Functionality - Expand to fully support browser 
DevelopmentCTS2 Functionality - CTRP Support - Determine specific requirements and propose solution (Partonomy, Disease Biomarker, and others)TBD (early 2016Q2?)
DevelopmentLexEVS Model - OWL and RRF Mapping use cases - Determine requirements and propose solution

This would include consulting with Harold Solbrig.

Considerations for backward compatibility with suggested changes.

DevelopmentMulti-namespace - determine requirements and propose solution 
DevelopmentQuery - Relationships - determine requirements and propose solution 
DevelopmentInferred Data - determine requirements and propose solution 
DevelopmentRemove caCORE 
DevelopmentRefactor Remote APISuggested inclusion with Spring migration
DevelopmentCTS2 Functionality - Ability to provide complete transitive closure 
DevelopmentCTS2 Functionality - Ability to restrict to association 
DevelopmentCTS2 Functionality - Ability to provide history API functionality 
DevelopmentCTS2 Functionality - Ability to group value sets together (FDA and SPL) 
DevelopmentCTS2 Functionality - Report to OMG the issue pertaining to return all results 
Support

Documentation Updates - review and clean up "LexEVS Code Examples"

 
SupportDocumentation Updates - Update CTS2 API documentation 
DevelopmentPresentation of Value Set and Mapping Data with Hierarchical structure - determine requirements and propose solution. 

 

  

 

  • No labels