NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 1

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameRolePresent
Remennik, LyubovNIH/NCIx

De Coronado, Sherri    

NIH/NCI   x

Safran, Tracy

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

Kuntipuram, Kumar

NIH/NCI [C]
Mensah, JacobNIH/NCI [C]
Trong, TracyNIH/NCI [C]
Kondareddy, SwathiNIH/NCI [C]
Kisler, BronNIH/NCI [C]

...

EVS Weekly Tech Meeting (Systems focus)

Discussion Points:

  • Systems related topics:
    • LexEVS
      • MySQL on Data Dev - Waiting to hear from Yahia for making changes to the MySQL format to Barracuda.
        • Jacob suggested creating a ticket for making changes to the DB.  The Systems team will make the DB changes.
      • No one else is using the Data Dev system.  There is no concern if we remove/add terminologies for our testing.
    • Browser/Tools
    • Data
    • Systems
    • Triple Store/EVS API

Decision Points:

Roll Call

Sprint Status


Current Sprint -  Sprint 93 (October 11, 2018 – October 24, 2018)

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

Planned Activities

  • Data Dev performance testing
  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-4143
  • Post F2F activities
  • Start EVS Service and Architecture GroupEVS Architecture

Anticipated Releases

  • Release 6.5.2We will need to coordinate with QA to do testing on the resolved issues.
  • Release 6.5.1.2
Face2Face RecapLexEVS Wiki Updates

Discussion Points:

2018.10 Technical Face-To-Face Meetings
  • Tracy will plan on make the initial changes and the Mayo team will assist as needed.
Decision Points:
EVS Service and Architecture Group
  • Cancer data aggregator and other projects will create multiple requests for terminology information for NCIt, Meta as well as others.
  • LexEVS Strengths - We will need to list what services could be enhanced and provided.
    • Also need to explain how we plan to use these strengths.
  • Sherri suggested that they need to add use cases for us to help determine solutions.  This will help the architecture team determine the needs.
    • SEER - Map to RxNorm
    • CTRP - use case
    • API Use Case: Given a SNOMED concept code - find the ICD10 concept code.
  • Continued Docker implementation

    • Decision Points:

    Discussion Points:

    Decision Points:

    • If there is a process that isn't describe, we should list that.  Lyuba mentioned we may be able to get a technical writer to assist.
    Med-RT

    Discussion Points:

    • 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.
    Lucene Security Issue

    Discussion Points:

    • SOLR Query Parser - not exposed by LexEVS.
    Decision Points:
    LexEVS-4178 Issue

    Discussion Points:

    • Jira
      serverNCI Tracker
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId7954a81f-12da-3366-a0ef-97c806660e7c
      keyLEXEVS-4178
    • Metathasuarus search and restricting to Med-RT

    Decision Points:

    • This is a higher priority and it was requested that we look at it.  We will work on it in the next sprint.

    LexEVS External Users

    Discussion Points:

    Decision Points:

    LexEVS External Users

    Discussion Points: 

    • CIViC LexEVS API documentation request
      • Sherri commented that in the EVS wiki pages, it is difficult to find how wiki pages.
      • Also, we should change the branding from CTS2 to REST service.

    Decision Points:

    We should update the wiki pages to make the LexEVS REST services easier to use.
  • Lyuba suggested a simple page on how to use the LexEVS REST services.  Use language that a 6th grader can understand.
    • "LexEVS for dummies"
  • Explain how you query for NCIt (How to documentation). 
    • Users want to specifically see how to search on NCIt.
  • Look at the CIViC documentation.
  • LexEVS Code Examples is useful (search for this will bring up this page).
    • Tracy and the Mayo team will discuss possibilities and make changes.

    Team Absences

    Mayo Team

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

    NCI

    • Tracy -
    • Rob - 
    • Kim -

    JIRA Issues

    ...