De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Open

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.

Value Set Loading Enhancements

• Update

Discussion Points:

• LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.02.21
• There are individual value set loads that are failing.  Scott will look into them first before looking at the issues in the multiple value set definition load script.
  
• Tracy mentioned that the run she started on DEV appears to still be running.
  

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.

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
  • https://documentation.uts.nlm.nih.gov/rest/home.html

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:

• Nothing noted.

Decision Points:

Mayo Team

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

NCI

• Tracy
  • March 9-17
• Rob
  

  • March 20-24