NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The purpose of this document is to capture proposed agenda topics for the 2018 technical face to face meeting with NCI EVS Teams. 

Proposed Agenda

Broad cross-EVS participation
Agenda ItemPurpose/GoalsProposed DurationParticipantsTime/Date RestrictionsTechnical Discussion/PresentationAdded to Schedule

Tuesday, December 5

9:00-11:00

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 discussion

  • Group discussion of future possible directions and priorities.
  •  

     2 hours x hours


     Tuesday 9:00 AM

    Slide of technical components

    Full EVS view of all the technical components.

    EVS Project Architecture

     

    11:00-12:00

    EVS Project Architecture

    Proposed topics for discussion:

    • EVS Project Architecture Review and Update
      • Review overall architecture and provide updates.
      • Describe and record full EVS architechture
    1 hour

    Broad cross-EVS participation


     

    Tuesday 11:00 AM EVS Project Architecture  

    1:00-2:00

    User Group Discussion

    • caDSR

    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.
    1 hourcaDSR contact - Denise, Philippa, developersTuesday 1:00 PM  

    2:00-3:00

    User Group Discussion

    • FDA
    • CDISC

    Proposed topics for discussion:

    • User Teams to share how they are using EVS and  discuss requirements/priorities for the future.
      • Value set curation in the context of sourcing value sets directly from NCIt
      • Desired output structure
      • 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.
    1 hour

    Editors

    Liz, Erin, Brenda

    Tuesday 2:00 PM  
    3:00-4:00 ?

    User Group Discussion

    • CTRP / CTS-API

    Reschedule - conflicts with Tiger Team (was at 11-12)

    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.
    1 hour

    CTRP / CTS-API - developers, managers,  Tiger team (Brian, Peter, Tracy, Jason, others)

     

    Tuesday 3:00 PM  
    Wednesday, December 6

    9:00-10:00

    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)
        • MicroServices and LexEVS
        • MicroServices and deployment options
    • 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
    1 hour

    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

     

    Wednesday 9:00 AM

    Micro service proposals

    LexEVS and Triple Store - Would be useful to have slides for suggested integration

    • Umbrella REST API that would connect to LexEVS REST API and Triple Store
     

    10:00-12: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?
    2 hours

    Systems team

     

     

    Wednesday 10:00 AM  

    1:00-2:00

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

    Proposed topics for discussion:

    • (High Level Overview) 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
        • Configuring LexEVS xml to allow load against source not in the service
    1 hour

    Kim Ong

    Tracy Safran

    Rob Wynne

    Editor's Representative/Margaret Haber

    Larry Wright

    Sherri De Coronado

    Wednesday 1:00 PM  

    2:00-3:00

    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
    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 PM  

    Thursday, December 7

    9:00-12:00

    API Services

    (10-12 Conflicts: Data Commons & GDC meetings)

    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

     

    3 hours

    Kim Ong

    Tracy Safran

    Rob Wynne

    End users such as CTRP, others

    Larry Wright

    Margaret Haber

    Sherri De Coronado

    Thursday 9:00 AM  

    1:00-3:00

    Prioritization and debrief

    Determine strategic direction and priorities1-2 hours Thursday 1:00 PM