NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 5

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

Saved on

compared with

New Version 6

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

Saved on

Key

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

...

EVS Weekly Tech Meeting

Discussion Points:

  • LexEVS
    • Nothing new to report this week
  • Browser/Tools
  • Data
  • Systems
  • Triple Store/EVS API

Decision Points:

Sprint Status

 

Current Sprint -  Sprint 66 (September 28, 2017 – October 11, 2017)


16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint66
Tier Deployment - Update
  • Tier Deployment
    • Data deployment

Discussion Points:

Decision Points:

Face2Face Discussion

Discussion Points:

  • Possible Travel Dates
    • November
      • 6 - 10
      • 13 - 17
    • December
      • 4 - 8 - This looks like the best week as of now.
      • 11 - 15 (Rob out)
  • F2F discussion and content to include in LexEVS 7.0
    • REST APIs/Triple Stores and their trade offs
    • Stardog and its built in graph database
    • Surfacing history in a REST service
      • Ability to time travel the history - NCIt and ULMS
    • Surfacing history of value sets in a REST service
    • Direct calls to NCIt for value sets

Decision Points:

Value Set Updates
  • Hierarchy prioritization

Discussion Points: 

  •  
    Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-2969
  • Some value sets have structure (like neoplasm).  Should this be implemented in LexEVS so the structure can be viewed in the browser? 
  • ICBO 3 map representation -
  • It was suggested that it would be nice to load a set of mappings to a set of URLs instead of a source/target coding scheme. (possibly for LexEVS 7.0)

Decision Points:

  • Larry suggested that overall, this is not a high priority.
  • The highest  highest is the relationship of value set to value set that Kim is doing.
    • Then the next priority would be ICBO 3 map.
Compiled Value sets

Discussion Points: 

  • Jira
    serverNCI Tracker
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId7954a81f-12da-3366-a0ef-97c806660e7c
    keyLEXEVS-3334
  • We should consider removing them
    • These are loaded at value set. resolve time.  The problem is they are persisted, but don't get updated.  They need to be updated when the value set. changes.
  • How would we test performance without them?
    • We can remove them all and then resolve a large value set., once (which will create the compiled value set.), and then again (which will use the compiled value set.) and see what the performance difference is.

Decision Points:

  • We should do some initial testing to see what the performance difference is with and without using the compiled value set.
Errors during the History load

Discussion Points: 

Decision Points:

NCIt load of the published value set version - errors during load

Discussion Points: 

Decision Points:

Backlog grooming - plan meeting

Discussion Points: 

  • We will plan a grooming session in the near future.

Decision Points:

LexEVS External Users

Discussion Points: 

Decision Points:

Team Absences

Mayo Team

  • Cory -
  • Scott -
  • Craig -

NCI

  • Tracy -
  • Rob - 12/11 - 12/18, 2/13 – 3/6
  • Kim -
  • Larry -

...