NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus

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 is still having an issue with the value set loader.  Mayo requested the load logs to see what is going on.  At this point we will have to wait for QA testing before getting performance results in value sets on the term browser.

Review MedDRA 15.0 data loaded by MedDRA Loader.

  • Assessed the MedDRA_history_english.asc data file. This file contains a field for the MedDRA code, the term name, what version (e.g., 10.1) the term was added, the type of term (e.g., PT, HLGT), its currency status if it is an LLT, and an action code. The action code can be either A (Add), U (Update), or D (Delete). It is possible for the MedDRA loader  to derive the PT_IN_VERSION data required by the FDA CTR team from this history file under a minimum assumption that all historical version number of MedDRA versions appear at least once in this file (i.e., at least one MedDRA term in each historical version has been either added, updated, or deleted). A longer term solution would be to extend the NCI History module to cover other applicable data sources.


Area of InterestDetails
LexEVS 6.1AntHillPro track has been completed.  The request to move to QA was suspended awaiting a re-format of the request.  Waiting for final approval.
Term Browser 2.3 Release

Waiting for the deployment of LexEVS 6.1 to QA to start testing.  Investigated the level of effort for migrating to java 1.7.

Meta Download Validation AppWaiting for the final decision on whether to use the EVS or CBIIT interface.  There will be a meeting on Aug 19th to finalize the decision.  Development is on hold until then.

JIRA/Gforge Issues

Issue NumberDescriptionStatus
GF#32871JAVA 1.7 Upgrade.
  • Assessed the impact of Java 1.7 upgrade. Currently, all EVSFocus applications are built and deployed using BDALite. Because that BDALite code was written based on the boss-5.1.0.GA architecture, and that the Java 1.7 is not compatible with boss-5.1.0.GA. So, the application server would need to be upgraded to either JBoss Enterprise Application Platform 6.1 (jboss-eap-6.1), or Apache Tomcat 7.0. The buck of the migration effort would be on modifying the BDALite software to accommodate the new target application server architecture.


#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.   
 Pushing back the start of the user evaluation7/22/2013 Having an issue with the exact match search.  Working with mayo to get it resolved but need it fixed before user can review.  
 Delay starting QA testing for Term Browser and NCIm Browser7/13/2013 We had to delay the start of the QA testing since a fully functioning API has not been established on the QA tier.  

 Planned Activities

Area of InterestDetails
Term Browser 2.3 ReleaseProvide any updates based on the user review/testing.
Term Browser 2.3 ReleaseMake any required fixes from QA testing.

Risks, Issues, Dependencies


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.


 #Opened DateDescriptionImpactAssignedStatus
 7/17/2013Removal of JAVA 1.6 from desktops.  The Term Browser deployments using AntHillPro require JAVA 1.6.  Putting in a request for a waiver until we can upgrade.This would affect the deployments and production environment for the EVS tools.  It sounds like this is going to be a future issue but we should have time to upgrade before it is part of the CBIIT tech stack. Provided a level of effort for migrating all of the EVS applications to Java 1.7 to the Technical Project Manager and government sponsor.
 7/31/2013We currently have an issue where the browsers are ready to move to the QA tier for testing but due to the dependency of LexEVS 6.1 cannot start the QA testing process.  LexEVS 6.1 does not currently have all the pre-QA qualification to proceed with the deployment to the QA tier.With a hard deadline of Sept. 30 for both the browsers and LexEVS API 6.1 there is concern that there will be time to finish all the testing and deployments on time. Received approval to proceed to QA tier with LexEVS 6.1.


Opened DateDescriptionAssigned
 Term Browser 2.3 release dependent on the LexEVS 6.1 release. See the Issue listed for 7/31/2013 for details on the status.
  • No labels