NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

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

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

Compare with Current View Page History

« Previous Version 13 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

All issues are considered after 6.4 related development.


Priority

(1-high, 3-low)

CategoryTopicNotes
1.5Tech CatalogMigrate to centOS 7

6.5

Required for better Docker support.

1Tech CatalogMigrate to Java 8

6.5

1.5Tech CatalogMigrate to Spring 46.5
2DevelopmentTree Performance - determine requirements and propose solutionLinked to the triple store discussions.
2DevelopmentCTS2 Functionality - Expand to fully support browser 
1DevelopmentCTS2 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
1DevelopmentCTS2 Functionality - Ability to provide complete transitive closureWill support CTRP requirement.
 DevelopmentCTS2 Functionality - Ability to restrict to association 
 DevelopmentCTS2 Functionality - Ability to provide history API functionalityMay be required for CTRP
 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. 
 DevelopmentLucene Implementation - Document query result differences and share with group to decide on solution. 
 LoaderOWL2 - LEXEVS-586 - Getting issue details... STATUS Gilberto to provide requirements.
 LoaderOWL2 - LEXEVS-1160 - Getting issue details... STATUS Included as part of OWL2 implementation.
 LoaderMedDRA - Provide comparison of MedDRA loaders to identify differences - determine requirements and propose a solution. 
 LoaderHL7 - LEXEVS-1037 - Getting issue details... STATUS  
 LoaderMedDRA - Close LEXEVS-339 - Getting issue details... STATUS  
 LoaderHL7 - Close LEXEVS-584 - Getting issue details... STATUS  
 LoaderHL7 - Review HL7 website rendering of brach/hierarchy to determine requirements and to propose solution to support HL7 structure. 
 LoaderLoad Process Automation - determine requirements and propose a solution. 
 LoaderReview all loader related JIRA issues and remove those that are no longer valid. 
 LoaderMySQL 5.5 Table Locking issue - propose a solution. 
 LoaderSNOMED - LEXEVS-234 - Getting issue details... STATUS  
 LoaderOWL2 - LEXEVS-347 - Getting issue details... STATUS  
 Loader

Value Set - LEXEVS-459 - Getting issue details... STATUS

 
 LoaderCLAML - Close - LEXEVS-535 - Getting issue details... STATUS  
 LoaderCreate an OWL2 to LexGrid Model spreadsheet (mapping). 
2DevelopmentTriple Store / SPARQL- Clarify the strengths and weaknesses in the tools (Blazegraph, Virtuoso, Stardog) to determine how to best address the browser and LexEVS needs.This will be led by Kim and Jason. They will share their evaluation with the group to help determine the best approach.
2Development

Review of value set workflow (including resolution) to determine requirements and proposed changes.  

 
 DevelopmentReview of admin workflow to determine requirements and proposed admin script changes and additions. 
 DevelopmentlbGUI - Provide viewing additional metadata in the GUI. 

 

  

 

  • No labels