Page History

9:00 AM - 11:00 AM

EVS Status and Future Direction

Discuss EVS current state, trends, and future directions

• Larry to give brief overview of EVS infrastructure, resources, and services.
• Review overall technical workflow and architecture.
• Group discussion of future possible directions and priorities.

EVS Project Architecture

(so far only LexEVS)

11:00 AM - 12:00 PM

EVS Technical Infrastructure, Issues, and Options

Flesh out architecture and workflow diagrams, identify key areas of discussion

• Review overall architecture and expand/update
• Identify areas where current infrastructure is changing or problematic

Primarily EVS technical team members

(several have conflicting clinical trials meeting)

1:00 PM - 2:00 PM

User Group Discussion - caDSR

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.

2:00 PM - 3:00 PM

User Group Discussion - FDA and CDISC

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.

Editors

Liz, Erin, Brenda

3:00 PM - 4:00 PM

User Group Discussion - CTRP / CTS-API

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.

EVS Architecture

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

Gilberto Fragoso

Kim Ong

Tracy Safran

Rob Wynne

Larry Wright

Margaret Haber

Sherri De Coronado

Bron Kisler

Systems team

John Cambell /Ruth Monterio users of the SQARL

MicroServiceProp.pptx

TripleStore.pptx

10:00-10:30

3-W-030

11:00-12:30

TE-420

(Can't fill gap 10:30-11:00)

EVS Architecture - Technical Discussion with Systems team

Discuss technical aspects of potentially using a variety of architectures

Proposed topics for discussion:

• Micro services
  • Considerations:
    • Embedded Tomcat implementations
    • Alternative web service platforms
    • Container/Port clashes

• LexEVS integration with EVS Triple Store
  • Considerations:
    • SPARQL clients
    • Docker options
• Future implementation considerations
  • Java
  • Python
  • Node.js/javascript
  • Others?

Systems team

1:00 PM - 2:00 PM

Kim Ong

Tracy Safran

Rob Wynne

Editor's Representative/Margaret Haber

Larry Wright

Sherri De Coronado

Gilberto Fragoso

NCI Systems Discussions

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

3:00 PM - 4:00 PM

(added meeting)

User Group Discussion - caDSR 

Continued discussion of current API

• APIs: Java, REST (CTS2 or 3-store), SPARQL
• https://github.com/CBIIT/cadsr-semantic-tools

caDSR - Philippa,

Vikram, Natalia, Rui

EVS REST API

• https://evsrestapi.nci.nih.gov/evsrestapi/swagger-ui.html#/evs-controller

CTS2 REST API

• https://lexevscts2.herokuapp.com/cts2

caDSR LexEVS API calls

• caDSR-EVS-Calls-NA.xlsx
• caDSR-EVS-Calls-VS.xlsx

1-E-030

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

Gilberto Fragoso

Prioritization and debrief

Determine strategic direction and priorities