Name | Role |
---|---|
# | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
---|---|---|---|---|---|---|
. |
Area of Interest | Details |
---|---|
LexEVS | |
Report Writer | |
Term Browser | DAP implementation patch for 2.11 passed appscan and awaiting deployment to stage. |
NCIm Browser | DAP implementation patch release for 2.8 has passed appscan and awaiting deployment to stage. |
Term Suggestion Application | DAP implementation patch has passed appscan and awaiting deployment to stage. |
EVS REST API | Modified the MainTypeHierarchy class
|
Biomarkers Support |
|
Neoplasm Core |
|
Other Support |
|
Issue Number | Description | Status |
---|---|---|
EVSREPORT-109 | Incorrect Pediatric Terminology report content. | Performed trouble shooting on an empty source combo-box issue reported by the Operations team. The results show that the LexEVSAPI CodingScheme getMappings().getSupportedSource() method returns nothing in NCIt version 17.07e, but the method returns expected sources in NCIt version 17.02d. The Operations team will work with the Mayo team to resolve the issue. |
# | Description | Due Date | Resources | Notes | Risks | Mitigation |
---|---|---|---|---|---|---|
Area of Interest | Details |
---|---|
Risks
# | Opened Date | Due Date | Description | Likelihood (H, M, L) | Impact | Assigned | Status | Mitigation Strategy |
---|---|---|---|---|---|---|---|---|
09/10/2015 | H | H | AppScan are taking long periods of time to complete. For Term browser, the minimum has been 5 days. | We are working on both the code base and configuration of the scan to try to improve performance. We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required. | ||||
# | Opened Date | Description | Impact | Assigned | Status |
---|---|---|---|---|---|
09/10/2014 | Getting the environment in place for the Mayo trip to NCI. | Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place. | Currently we only have the DEV environment setup for the LexEVS API> | ||
Opened Date | Description | Assigned |
---|---|---|
. | ||