Page History

User Group Discussion

• Team to share how they are using LexEVS and additional usage requirements they may have.
• What components of LexEVS do you currently use?

  • LexEVS API

  • LexEVS Remote API

  • CTS2 RESTful services

• Are there LexEVS services that you would like to use, but they don't meet your requirements?

• Are there any other road blocks preventing you from using LexEVS?

• What version of LexEVS are you currently using?

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 and in conjunction with LexEVS
• Text searching
• NCBO SPARQL white paper and it's implications
• Searching on Roles (Gilberto, Kim)

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

• User/content priorities for value set, mapping, and other services.
• Specialized search and other capabilities for complex chemical names and genetic names.
• Current capabilities and browser implementation
• Possible expert system extension

LexEVS Mapping Discussion

Determine requirements and propose solution for mapping.

• User requirement: One terminology to many terminologies mapping.
• Other topics:  Current, conditional, external relationships

Lucene Discussion

Propose additional features of Lucene to be used within LexEVS.

• Discuss specialized search use cases.
• Possible Lucene enhancements for coding scheme categorizations, auto complete aids, Lucene services.

Overflow/Additional Topics

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.
• Discuss latest issues on PROD.

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

• • 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.
• Discuss a separate DEV environment for CI server deployment
• Tech Stack Upgrades
  • Discuss DB upgrade:
    
    • MySQL 5.6 vs. MariaDB (10.1 Supported 2017.01)

• • Discuss CentOS 7 upgrade
• Tier Deployment testing responsibilities
  • Mayo development team responsibilities
  • NCI development team responsibilities

FHIR and terminology services (CTS2)

• Harold to provide update on CTS2 and FHIR.

OWL Restrictions in LexGrid Model

• Discuss approach and propose additional features.
• Determine if there are LexEVS model changes needed.
• Loader considerations.
• Additional problems and solutions

Overflow/Additional Topics

LexEVS Admin Tooling

Discuss current and future requirements.

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

Prioritization and Debrief

• Discuss OWL2, RRF, LexEVS, CTS2, Browser,

• and all previous topics
  • Discuss future architecture
• Determine next steps/road map and priorities

Prioritization and Debrief (Continued if needed)