NIH | National Cancer Institute | NCI Wiki  


Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Sharma, DeepakMayox
Wynne, Robert    NIH/NCI [C]x
Tran, Tin    NIH/NCI [C] x
Carlsen, Brian NIH/NCI [C] 
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar


Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus

Close issue 

  LEXEVS-1516 - Getting issue details... STATUS

2016.02.092016.04.10 Open

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

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open
ScottSend F2F presentation to Tracy2016.04.272016.04.30 Open
ScottReview differences between search extension and the regular search and discuss with the team2016.04.27  Open
ScottDiscuss CTCAE hierarchy issue with Kim.2016.04.27  Open
CoryUpdate wiki to describe what DBs are supported/tested going forwared2016.04.272016.04.30 Open
CraigSet up meeting for LexEVS remote API automation discussion.  Include: Scott, Kevin, Tin , Rob and Tracy2016.04.272016.04.30 Open


  • Sprint 28
  • Sprint 29 Planning
  • On going Support
  • Sprint 28
  • Sprint 29 Planning
  • On going Support
  • Sprint 28
  • Sprint 29 Planning
  • Sprint 28
  • Sprint 29 Planning
  • Agile Admin


Sprint Status

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

LexEVS S13-500 Agile Development - Sprint 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
  • LEXEVS-1430 - Getting issue details... STATUS
Tracy and Rob confirmed that this loader is not used by NCI and we can remove this.

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.

JIRA Issues

Recent LexEVS Related Bugs and Features (within last week)

Key Summary T Created Reporter P Status Affected Version/s Fix Version/s

Recent CTS2 Service Related Issues (within last week)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.4 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.4 CTS2 Service Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned


Action Item Backlog

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold
164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
244CraigPlan meeting with Tracy to discuss collaborative LexEVS development process2014.12.03  on hold
281ScottTry to replicate what CTRP did to break our service (retrieve a tree through CTS2).2015.03.25  on hold
282Mayo TeamLook into implementing graph node in CTS2 for the path to root method (and path to leaf).2015.03.25  on hold




  • No labels