2017.12 Proposed F2F Agenda Topics

Tuesday

9-11: EVS Status and Future Direction

• Discuss EVS current state, trends, and future directions
  
  • Larry to give brief overview of EVS infrastructure, resources, and services, to help frame
  • Group discussion of future possible directions and priorities.

User Group Discussion

• CTRP

Reschedule - conflicts with Tiger Team

Proposed topics for discussion:

• User Teams to share how they are using EVS and  discuss requirements/priorities for the future.
  • APIs: Java, REST (CTS2 or 3-store), SPARQL, FTP
  • Backwards compatibility of server/client/data releases
  • Incl: Java/jar file issues and future
  • Incl: New terminology server API/content/other needs.

CTRP - Tiger team (Brian)

User Group Discussion

• caDSR

Proposed topics for discussion:

• User Teams to share how they are using EVS and  requirements/priorities for the future.

• Services/updates for our customers - Discuss how to update LexEVS customers with jar files when updating LexEVS versions
  • Releases need to be backwards compatible

User Group Discussion

• FDA
• CDISC

Proposed topics for discussion:

• User Teams to share how they are using EVS and  requirements/priorities for the future.

• Services/updates for our customers - Discuss how to update LexEVS customers with jar files when updating LexEVS versions
  • Releases need to be backwards compatible

Editors

Wednesday

9-12: EVS Architecture

(10-11 Conflict: Data Commons Semantics meeting)

Discuss Potential of using a variety of architectures

Proposed topics for discussion:

• Micro services
  • Considerations:
    • 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. 
    • Determine the potential of a loader that relies on SPARQL queries (after SPARQL query load, kick off LexEVS loader)

• LexEVS integration with EVS Triple Store
  • Considerations:
    • Determine use of triple store calls in parallel with LexEVS DB
    • Determine performance improvements over LexEVS DB
    • Determine what calls could be made to the triple store instead of LexEVS.
    • Determine use of Stardog built in graph database.
    • Determine performance considerations for hierarchy traversal for graph resolution.
• Future implementation considerations
  • Java
  • Others?
    
    

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

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

Proposed topics for discussion:

• 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

Kim Ong

Tracy Safran

Rob Wynne

Editor's Representative/Margaret Haber

Larry Wright

Sherri De Coronado

NCI Systems Discussions

• CI and Docker Status/Roadmap
• Tech Stack Upgrades

Proposed topics for discussion:

• 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

Jacob and Systems team

Gilberto Fragoso

Rob Wynne

Tracy Safran

Kim Ong

Larry Wright

Margaret Haber

Sherri De Coronado

Q/A (Sana)

Thursday

API Services

Proposed topics for discussion:

• Overview of EVS REST API and future direction
  • Discuss what exists today.
  • Discuss future plans.

• Overview of LexEVS provided API services and future direction
  • LexEVS API
  • LexEVS Remote API
  • LexEVS REST API (CTS2-based)

• Discuss a new REST service
  • Discuss user requirements for a new REST API
    
    • Document the gaps from CTS2 REST API and user requirements.
    • Explore how simple searches and searches with an identifier and how this could replace most of the remote API.
  • Consider a new REST API to supplement CTS2 REST Services
    • Propose examination of current CTS2 REST API
    • Capture what doesn't work for the end users.
    • Review gap between Remote API and REST services.
  • Discuss surfacing terminology history in a REST service (NCIt and ULMS)
    • Determine what history information is required by the user to be returned.
      • Discuss surfacing history of value sets in a REST service
    • Discuss if this fits into LexEVS or is part of a new REST API

Kim Ong

Tracy Safran

Rob Wynne

End users such as CTRP, others

Larry Wright

Margaret Haber

Sherri De Coronado