Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Close issue 

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

Current Sprint -  Sprint 28 (April 14, 2016 – April 27, 2016)

LexEVS 6.4 S13-500 Agile Development - Sprint Status

LexEVS Compatibility

• Remote service and client jar migration

LexEVS 6.4 Remote Service and Client Updates

caCore legacy code was mentioned and it was suggested that we should remove any caCore code.

Mayo will need to prioritize this work to determine where it will fit into our schedule. 

TODO:  Craig to create a JIRA item to track the removal of the caCore code.

PTE for CI and DEV environment discussion

• CI Server
• DEV Server

CI server - it was discussed that we may use an in-memory DB (HSQL) instead of MySQL DB.  This is being investigated by Mayo to see if we can get this working locally.

Scott noted that our Mayo Jenkins server is running on a system that has 8 cores with 32 GB of memory.

DEV server - Rob has installed LexEVS 6.4 runtime on DEV and generated the indexes.

There is a new 6.4 DEV container that Jacob is working on getting deployed.

NCI testing - NCI will build the 2.8 browser with the new LexEVS 6.4 jars and see if that runs without any code changes.

NCI will also test the runtime API and Tin will look at performance to compare 6.3 and 6.4.

Jason asked when the remote API will be available.  We suggested that it should be delivered by the end of sprint 29.  We will need to verify performance is still acceptable prior to releasing it to NCI.

Status#SprintStatus-Sprint28

The plan is to finish LexEVS Remote API in sprint 29 and test performance and deliver the LexEVS Remote API in Sprint 30.

If development finishes earlier, it is possible to deliver the LexEVS Remote API at the end of Sprint 29.

NCI DEV Deployment and Status

• Mayo/NCI DEV utilization

NCI is in agreement that Mayo can develop and test on NCI DEV in parallel with NCI using the DEV instance for their testing.

Rob mentioned there is an issue that the current NCI DEV instance cannot find the indexes.  Scott will investigate this problem. 

Rob and Scott will webEx to review the issue.

Rxnorm batch loader extension

• Verify removal of loader

• Jira
  server NCI Tracker columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-1430

Lexevs remote API

• Automation of unit testing

There is a need to automate LexEVS remote API to make the testing more generic and easier to run.

Craig to set up meeting to discuss.  This should include: Scott and Kevin, Tin, Rob, and Tracy.

Search Extension Discussion

• Kim to describe issue

Kim mentioned that the search extension returns different results than the standard (codedNodeSet) search.

Kim noted that the difference in the searches has been there for a long time. 

Larry suggested that the development team should address this issue.

Scott will look into the differences and review that with the team.

CTCAE Discussion

• Hierarchy issue

Scott explained how namespace should be set up to get the hierarchy set up correctly.

Scott requested more information from Kim in order to understand the issue. 

Kim and Scott will investigate further offline.

LexEVS External Users

• Jorge
• Supported databases

The Mayo dev team has worked with Jorge to get his installation working.  Jorge originally attempted to use PostgreSQL and it failed.

We recommended the Jorge use MySQL as that is the most widely used/tested DB.

Craig asked what databases should LexEVS support going forward.

Larry suggested that we update our wiki documentation to reflect what DBs are supported now.

Going forward we will officially support MySQL

.