Page History

User Group Discussion

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

CTRP, caDSR, GDC

RESTful API Discussion

• Discuss requirements for continued development of REST services. This will include both CTS2 and separate REST-ful API.
• Browser: Discuss requirements for remote API and CTS2 REST-ful API.

Triple store/RDF Discussion

• Discuss what Triple stores would be used for in parallel with LexEVS
• Text searching
• Searching on Roles (Gilberto, Kim)

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

• Discuss specialized search use cases

Value Set management and workflow

• Discuss requirements for value set version management and workflow management and supporting technology.
• Rob to give a demo of their current workflow and the scripts they use.

Value Set and Mapping Data with Hierarchical structure Discussion

• Determine requirements and propose options to hierarchical structure and mapping.
• Discuss how VS could retain their multiple hierarchical structure that it came from.
• Discuss what changes would be needed to CTS2 for this.

NCI Systems Discussions

• Nexus Deployment Discussion
  • Current status of LexEVS artifacts on NCI Nexus server
  • Discuss current technical challenges.
• CI and Docker Status/Roadmap
  
  • Discuss how to set up a DEV environment with CentOS 7
  • Does this require a complete recompile of the OS?
  • A separate DEV environment for Mayo Team
  • Discuss the current status of the Docker scripts used to build/test LexEVS components.
  • Discuss NCI's current status and future plans to use Docker.
  • Discuss security challenges associated with NCI's environment and Docker.
• Tech Stack Upgrades
  • Discuss DB upgrade: MySQL 5.6 vs. MariaDB (10.1 Supported 2017.01)

Sara, Shireesha, Phil

Jacob and Systems team

FHIR and terminology services (CTS2)

• Harold to provide update on CTS2 and FHIR.

OWL Restrictions in LexGrid Model

• Discuss approach and propose additional features.
• Discuss how to provide mapping into multiple coding schemes.
• Determine if there are lexevs model changes needed.
• Loader considerations.

LexEVS Admin

Discuss current and future requirements.

• GUI
  • Consider a web based tool.  A simple way to look at the data.
• Command Line

Future Architecture Discussion

• Discuss OWL2, RRF, LexEVS, CTS2, Browser, etc and propose a roadmap

Prioritization and Debrief (Continued)

• Prioritize
• Determine next steps/roadmap