|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
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/13||6/25/13||10/26/13||Kim received the example code as part of the new release of LexEVS 6.1 to DEV.|
|Operations||Loading resolved value sets to test the performance to make sure additional work is not needed for the resolving value set performance.||6/19/13||6/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.
|Area of Interest||Details|
|LexEVS 6.1||AntHillPro 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 App||Waiting 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.|
|GF#32871||JAVA 1.7 Upgrade.|
|GF#32816||Migrate to LexEVS API 6.1.||6/28/2013||1 Developer||We 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 Time||7/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 evaluation||7/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 Browser||7/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.|
|Area of Interest||Details|
|Term Browser 2.3 Release||Provide any updates based on the user review/testing.|
|Term Browser 2.3 Release||Make any required fixes from QA testing.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|6/19/13||9/30/13||Term 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.|
|7/17/2013||Removal 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/2013||We 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.|
|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.|