Attendees
Name | Role |
---|---|
Action Items
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
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/13 | 6/25/13 | |||
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 | |||
Progress
Area of Interest | Details |
---|---|
LexEVS 6.1 | We 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 Release | First 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 Release | Continued 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. |
JIRA/Gforge Issues
Issue Number | Description | Status |
---|---|---|
GF#32772 | Improve value set accessibility. |
|
GF#32793 | Extend the advanced search capability. |
|
Project Plan Changes
# | Description | Due Date | Resources | Notes | Risks | Mitigation |
---|---|---|---|---|---|---|
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. | ||
Planned Activities
Area of Interest | Details |
---|---|
Term Browser 2.3 Release | Continue working on the migration of the Term Browser 2.3 release to LexEVS API 6.1. |
Term Browser 2.3 Release | Continue evaluating the new LexEVS search against user requirements. |
Risks, Issues, Dependencies
Risks
# | 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 is in parallel development with the Term Browser having a dependency on LexEVS release. Both of a hard deployment date by 9/30. 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 Date | Description | Impact | Assigned | Status |
---|---|---|---|---|---|
Dependencies
Opened Date | Description | Assigned |
---|---|---|
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. | ||