NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Document Information

Author:  Craig Stancl, Scott Bauer, Cory Endle
Email: craig.stancl2@nih.govscott.bauer@nih.govcory.endle@nih.gov
Team:  LexEVS
Contract:  16X237
Client:  NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services

Contents of this Page

The purpose of this document is to capture proposed agenda topics for the 2017 technical face to face meeting between NCI and Mayo.

 

Agenda ItemPurpose/GoalsProposed DurationParticipantsTime/Date RestrictionsRequested / Proposed ByAdded to Schedule
Year in review and Future Direction

Discuss the accomplishments of the past year and the future direction of EVS

 2 hours

Larry Wright

Margaret Haber

Sherri De Coronado

Gilberto Fragoso

 Tuesday 9:00 AM  

User Group Discussion

  • CTRP
  • caDSR
  • FDA
  • CDISC

Teams to share how they are using LexEVS and additional usage requirements they may have.

Services/updates for our customers - Discuss how to update LexEVS customers with jar files when updating LexEVS versions

  • Releases need to be backwards compatible

Discuss evolving to all REST services and possibility of retiring the Java API

  • What needs to be enhanced in the REST API need to support our Java API customers.
2 hours

caDSR contact

 

Tuesday 1:00 PMMayo Team 
EVS Architecture

Discuss Potential of using a variety of architectures

  • Discuss potential use of micro services
  • Need to determine how to synchronize data on the back-end
    • LexEVS DB and Triple Store need to be in sync when NCIt information (such as value sets) changes. 
  • Discuss the potential of a loader that relies on SPARQL queries
      • After SPARQL query load, kick off LexEVS loader

LexEVS integration with EVS Triple Store

  • Discuss using triple store calls in parallel with LexEVS DB
    • Explore if the EVS triple store offers performance improvements over LexEVS DB
    • Discuss what calls could be made to the triple store.
  • Discuss Stardog and its built in graph database. (Note that Stardog is proprietary and NCI may switch out at a future date.)
    • Performance considerations for hierarchy traversal for graph resolution.
3 hours

Gilberto Fragoso

Kim Ong

Tracy Safran

Rob Wynne

Larry Wright

Margaret Haber

Sherri De Coronado

Systems team

John Cambell /Ruth Monterio users of the SQARL

 

Wednesday 9:00 AMMayo Team/Larry 

EVS Project Group Discussion (During regular call-in time)

Discuss direct calls to NCIt for value sets

  • Performance
  • Workflow
  • API Implications

Discuss Mappings and cross-walking coding schemes

  •  SwissProt, ICD-0-3, and MED-RT as the successor of NDRFT
    • Associations from/to
    • Cross walking coding schemes
    • Loader considerations for Mesh, RxNorm
1 hour

Kim Ong

Tracy Safran

Rob Wynne

Editor's Representative/Margaret Haber

Larry Wright

Sherri De Coronado

Wednesday 1:00 PM  

NCI Systems Discussions

  • CI and Docker Status/Roadmap
  • Tech Stack Upgrades

Discuss CI and Docker Status/Roadmap

  • Discuss the current status of the Docker scripts used to build/test LexEVS components.
    • Discuss the current NCI Docker images used in LexEVS tests.
  • Discuss NCI's current status and future plans to use Docker.

Discuss Tech Stack Upgrades

  • Discuss DB upgrade: MySQL 5.6 vs. MariaDB

Discuss migrating from Anthill Pro to Jenkins

1 hour

Jacob and Systems team

Gilberto Fragoso

Rob Wynne

Tracy Safran

Kim Ong

Larry Wright

Margaret Haber

Sherri De Coronado

Q/A (Sana)

Wednesday 2:00 PMMayo Team 
API Services

Discuss a new REST API to supplement CTS2 REST Services

  • Examine current CTS2 REST API
    • Discuss what doesn't work for the end users.
    • Discuss gap between Remote API and REST services.
  • Discuss user requirements for a new REST API
    • Document the gaps from CTS2 REST API and user requirements.

Discuss surfacing terminology history in a REST service (NCIt and ULMS)

  • Determine what history information is required by the user to be returned.
  • Discuss if this fits into LexEVS or is part of a new REST API

Discuss surfacing history of value sets in a REST service

Discuss REST service - simple searches and searches with an identifier and how this could replace most of the remote API

3 hours

Kim Ong

Tracy Safran

Rob Wynne

End users such as CTRP, others

Larry Wright

Margaret Haber

Sherri De Coronado

Thursday 9:00 AMMayo Team/Larry 
Prioritization and debrief 1 hour Thursday 1:00 PM  

 

 

 

 

  • No labels