NIH | National Cancer Institute | NCI Wiki  


Please be advised that NCI Wiki will be undergoing maintenance on Thursday, May 23rd between 1200 ET and 1300 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.


Haber, MargaretNIH/NCI
Fragoso, Gilberto NIH/NCI     

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x

Kuntipuram, Kumar

Mensah, JacobNIH/NCI [C]x
Trong, TracyNIH/NCI [C] 
Din, SanaNIH/NCI [C] 
Kisler, BronNIH/NCI [C]x
Remennik, LyubovNIH/CC/BTRISx

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • Systems team has DEV system configured to run Docker containers.
      • LexES team to start working with this setup.
    • CTS2 on-line documentation is running on NCI Dev system and Heroku.
      • Jenkins is set up to build/deploy on dev.
    • Lexevs-system-tests - have been updated and are running successfully.
    • MySQL timeout during value set load.
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

  • Cory to submit a ticket to install npm/node.js and deploy CTS2 API documentation artifacts to QA/PROD.
Roll Call 

Sprint Status


Current Sprint  Sprint 75 (February 1, 2018 – February 14, 2018)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint75
API Meeting/Discussion Update

Discussion Points:

  •  Meeting will be on Thursday this week.

Decision Points:

Resolved Value Set rework

Discussion Points:

  • Resolved value set API should continue to return what it was prior to this rework.
  • The search extension won't have value set coding schemes to search against.
  • The team will need to determine what impacts that these changes will have on existing applications that use this API.

Decision Points: 

  • Scott to send out email to document/describe the value set rework and what impacts this will have on resolved value sets and other services.
Source Asserted Value Sets

Discussion Points:

  • Scott mentioned that how we represent/structure value sets in NCIt is a new/interesting concept. 
  • He mentioned that this could be a good idea for a paper.

Decision Points: 

  • Scott and Rob to create an abstract and bring it back to the group to review.

LexEVS External Users

Discussion Points:

  • caDSR - LexEVS REST vs Java API discussion on Friday.
  • Mayo team gave some query/display examples using the LexEVS API and CTS2 REST API.
  • We did not have an EVS API example. 

Decision Points:

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig -


  • Tracy -
  • Rob - 2/13-3/6
  • Bron -
  • Sana -
  • Kim -

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.5 LexEVS Related Issues

Key Summary T Created Updated Due Assignee Reporter P Status Resolution

6.5 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