NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
 Mayo

Provide example code to assist us with the understanding of the handling of value sets as coding schemes.  This understanding will assist in our development of a Value Set Entity Search (GF#32794) which is part of the Term Browser 2.3 scope.

Provide a convenience method for resolving value sets from a resolved concept reference.

6/19/136/25/1310/26/13Kim received the example code as part of the new release of LexEVS 6.1 to DEV.
 OperationsLoading resolved value sets to test the performance to make sure additional work is not needed for the resolving value set performance.6/19/136/21/13 Operations team was able to load 5 of the resolved value sets but it requires loading one at a time.  Mayo is going to look at the possibility of providing a batch loader.
       

Progress

Area of InterestDetails
LexEVS 6.1We have been working with the Mayo team to get the deployment of LexEVS 6.1 onto the DEV environment.  This was successfully completed and we are currently evaluating the effects on the EVS tools
Term Browser 2.3 ReleaseFirst glance of the new LexEVS 6.1 shows that there might be more work than first thought with migrating to the new release of the LexEVS API for Term Browser.  The changes made to the value sets breaks the Term Browser code.  We are requesting more specific details on the changes made by the Mayo team.  With the LexEVS 6.3 release value sets are treated as coding schemes but at they do not appear to behave exactly the same.  More investigation is needed.
Term Browser 2.3 ReleaseContinued reviewing the new simplified search capability provided in LexEVS to see how it will fit the searching needs required in the browser.  The goal is to use the new search to replace the current quick search in the browser.  If that is not possible, make it an additional search in the Advanced Search page.
Term Browser 2.3 ReleaseWe believe we know how the LexEVS methods we need to start working on the Value Set Entity Search.  This is the highest priority for development right now.

JIRA/Gforge Issues

Issue NumberDescriptionStatus
GF#32772Improve value set accessibility.
  • Continued to test the new value set tree implementation.
GF#32793Extend the advanced search capabilities
  • Added a new CTS2 Lucene search option to the advanced search page.
  • Assessed code changes required to integrate with the new search extension.
GF#32779Enhancement to Contains Search Functionality.
  • Tested Mayo’s CTS2 contains search function using the web application CTS2.war available at  http://ncias-d488-v.nci.nih.gov:8000/. It was observed that, the contains search failed to find concepts that match the user-specified search criteria in some test cases. For example, the NCI Thesaurus concept, Induction of Cell Senescence (Code C40779), has a synonym called "Positive Regulation of Cell Aging". But, the contains search using the search string “cell AND aging” failed to find this concept. Also, some input strings containing special characters can cause the application to hang. The Mayo team will investigate these issues.
  • The Mayo team deployed lexevsapi61 on NCI DEV at:

http://ncias-d499-v.nci.nih.gov:29780/lexevsapi61. Successfully tested the 6.1 server using the new client package.  

GF#32793Extend the advanced search capability.
  • Added a new CTS2 Lucene search option to the advanced search page.
  • Assessed code changes required to integrate with the new search extension.
GF#32794Implement value set entity search.
  • Discussed with the Mayo team on the possibility of developing convenience methods for retrieving coding scheme name and version for entities belonging to a resolved value set coding scheme.
GF#32816Migrate to LexEVSAPI 6.1.
  • Identified difference between the lexevsapi6.0 and lexevsapi6.1 client packages. 
  • Updated the lib folder in the term browser application.
GF#32811Tagging of value sets.
  • Identified the method for distinguish resolved value set coding schemes from regular coding schemes. A resolved value set coding scheme has a property called RESOLVED_AGAINST_CODING_SCHEME_VERSION. But, a regular coding scheme does not have this property. In addition, a resolved value set coding scheme has a 32-bit represents version.

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation
GF#32816Migrate to LexEVS API 6.1. 6/28/20131 DeveloperWe are still reviewing the new deployment of LexEVS 6.1 on DEV.  This date is dependent on the value sets issues describe previously.  
 Moving up Development Time7/17/2013 We are pushing to get the coding done for a July 17th review by the EVS users.  This will give the users a chance to provide input on the implementation before we completely freeze the code.   
       

 Planned Activities

Area of InterestDetails
Term Browser 2.3 ReleaseContinue working on the migration of the Term Browser 2.3 release to LexEVS API 6.1.
Term Browser 2.3 ReleaseContinue evaluating the new LexEVS search against user requirements.
  

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 6/19/139/30/13Term Browser 2.3 and LexEVS 6.1 are in parallel development with the Term Browser having a dependency on LexEVS release.  Both have a hard deployment date of 9/30/2013.  Anticipating some QA resource limitations with both schedules being in parallel.M Jason Monitoring both schedules and will provide status to QA to make sure resources are available.
         
         

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
 Term Browser 2.3 release dependent on the LexEVS 6.1 release. Mayo team says that they will start deployment through the tiers the second week in July pending any additional work needed on the Value Set resolution performance.  Operations team is loading the value sets into DEV through this week and we can then evaluate the performance.
 
   
   
  • No labels