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
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
CoryAdd link to Maven Opts for end users2016.12.21  



Sprint Status


Current Sprint  Sprint 50 (February 16, 2017 – March 1, 2017)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint50

  • Report writer team may need to test with Java8

DEV Server Configurations

  • Planning and usage discussion

Discussion Points:

  • Dev VM (Mayo) is set up and we confirmed we can log in
  • Dev Blade - Jacob is waiting for the Mayo Dev team to let him know if tomcat 8 will work.

Decision Points:

  • Cory to confirm with Jacob what version of tomcat 8.x NCI is going to run. FINAL build update

  • Creating

Discussion Points:

Decision Points:

Value Set Loading Enhancements

  • Update

Discussion Points:

Decision Points:

LexEVS Version/Naming Discussion


Discussion Points:

  • LexEVS Software Release Versioning
  • Larry suggested if the release has a major impact on the end user (consumers), then we would increment the major version number.
  • If the user created their own instance of LexEVS, then the versioning would affect them more than just being a consumer of the API. 

Decision Points:

  • The team will think about this and discuss again next week.
CTS2 REST API Discussion

Discussion Points:

  • End users are not familiar with the CTS2 model and REST API.
  • This doesn't fit well with end LexEVS users as they are not familiar with the CTS2 model.
  • It was suggested that it may make sense to have a REST API that represents the LexEVS Model.
  • Example scenarios:
    • For a given regime concept, give me the associated drugs. (the user knows the relationship)
    • This was available under caCore.
  • Users of CTS2:
    • Bob Kline (CTL), CTRP, Brian Bazilla
  • Tracy created multiple JIRA issues capturing the issues:
    • LEXEVSCTS2-138-144
      • Most of these issues were possible under caCore data services.
  • Larry suggested looking at the UMLS REST interface

Decision Points:

  • Mayo Dev team will discuss and come up with some possible solutions and report back to the team.

LexEVS Logical Role Relationship

  • Discussion with Kim

Discussion Points:

  •   LEXEVS-2764 - Getting issue details... STATUS
  • Kim is questioning the difference between inferred and asserted versions.
  • DEV vs PROD browser - inferred versions for neoplasm are different.

Decision Points:

  • Kim to provide some screen shots/examples of this issue.
LexEVS External Users

Discussion Points:

  • Nothing noted.

Decision Points:

Proposed Backlog Review Items

Discussion Points:

Decision Points:

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig - March 6-13


  • Tracy
    • March 9-17
  • Rob
    • March 20-24

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




  • No labels