Page History

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Discussion Points:

• Systems related topics:

• • LexEVS
    • Data Dev
    • System Tests - Jenkins build failing
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

Sprint Status

Discussion Points:

• No significant changes to mention.
• The Mayo team is available to assist Tracy, if she needs it.
• Tracy mentioned that she will have a preliminary outline of changes by this Friday.
  
• Sherri mentioned that QDC (user) is waiting for this updated documentationTracy will plan on make the initial changes and the Mayo team will assist as needed.
  

Decision Points:

• Lyuba suggested that we provide a timeline to complete the wiki updates.

Discussion Points:

• Workgroup Meeting Logistics
  • Led by Tracy
  • Documents/Agenda/Minutes: EVS Services and Architecture Workgroup
  • Weekly - Tuesday at 10:00 AM
• Meeting Minutes: 2018-10-23 Meeting notes
  • EVS Architecture: https://wiki.nci.nih.gov/pages/viewpage.action?spaceKey=EVSproj&title=EVS+Architecture
• EVS Evaluation Timeline?
  • Sherri doesn't have a timeline yet.
• Next Steps
  • https://wiki.nci.nih.gov/display/LexEVS/EVS+Services+and+Architecture+Roadmap

Decision Points:

• Team will meet next week.

Decision Points:

Discussion Points:

• The long term priority is to create a LexEVS loader for MED-RT.
• Short term priority is the single source extraction - This is on Dev.
• There is also a MED-RT browser issue that the LexEVS team needs to look at
• Med-RT is loaded as a single source on DEV. 
  
• Stephanie is reviewing it currently
• The hierarchy is there.
• Anything that belongs to Med-RT is there.
• This is a new hybrid reference terminology.
• It was requested that we create a LexEVS Med-RT loader.
• It would be helpful to LexEVS if MESH and RX-NORM are their own separate terminology loads.
  

Decision Points:

• Mayo team to create a JIRA item to create this loader.

Discussion Points:

• SOLR Query Parser - not exposed by LexEVS.
  

• LexEVS Security issues
  • The team reviewed the security issues and discussed how to proceed.
  • We discussed the usage of AppScans for LexEVS and assumed they should be revealing any real security issues.
• LexEVS users
  • caDSR Tools use LexEVS Remote client

Decision Points:

• We agreed that we need to discuss possible actions with the Systems team.
  • Kumar will set up a meeting to discuss with the Systems team (Phil).
    • We should include the LexEVS team and caDSR (Natalia) in this meeting.

Discussion Points:

• December 8 power outage.
• We will need to test our services when the power is back on (December 9/10).
  

Decision Points:

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

• Metathasuarus search and restricting to Med-RT
  

Decision Points:

LexEVS External Users

Discussion Points:

Decision Points:

Mayo Team

• Cory -
• Scott - 11/6 (PM), 11/7 (AM)
• Craig - 11/2 - 11/8

NCI

• Tracy -
  
• Rob - 
• Kim -