NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 2

changes.mady.by.user Unknown User (endlecm)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

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

...

NameRolePresent
Remennik, LyubovNIH/NCIx

De Coronado, Sherri    

NIH/NCI   

Safran, Tracy

NIH/NCI [C]x
Ong, Kim L
IS
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCI [C]x

Kuntipuram, Kumar

NIH/NCI [C]x
Mensah, JacobNIH/NCI [C]x
Trong, TracyNIH/NCI [C]
Kondareddy, SwathiNIH/NCI [C]
Kisler, BronNIH/NCI [C]

...

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus






Agenda

EVS Weekly Tech Meeting (Systems focus)

Discussion Points:

  • Systems related topics:
    • LexEVS
Data Dev - upgrade DB to Barracuda
      • Appscan/Nessus Scan?
        • There are no current scans being done.
        • These scans will not pickup any of the additional security issues that we got from the git scan.
    • Browser/Tools
    • Data
    • Systems
    • Triple Store/EVS API

Decision Points:

Roll Call

Sprint Status


Current Sprint -  Sprint 95 (November 8, 2018 – November 21, 2018)

16X237 Agile Development - Sprint Status#16X237AgileDevelopment-SprintStatus-Sprint95

Planned Activities

Review Security issues

  • Data Dev performance testing
  • EVS Service and Architecture Group

Anticipated Releases

  • Release 6.5.2
  • Release 6.5.1.2
Value Set Definitions - REST services not working

Discussion Points:

  • 6.5.1.1 issue?: LEXEVS-4056
  • Scott will contact Jacob and confirm the server DNS/redirects are working properly.
  • We will need to make sure all valuesets are being returned.

Decision Points:

LexEVS Wiki Updates (Tracy)

Discussion Points:

  • Tracy
has done
  • did some
LexEVS wiki
  • reorganization
at the top level
  • .
  • We suggested that the "community code contribution" could probable be archived.
  • Tracy will continue working on updating the wiki pages.
  • A quick start page was originally suggested for the NCIt access.
    • She will be adding some text around some of the links.

    Decision Points:

    • We will review the wiki changes next week

    Decision Points:

    Lyuba suggested that we can provide additional feedback at the next meeting
    • .
    EVS Service and Architecture Group (Tracy)

    Discussion Points:

  • Lyuba would like a timeline for us to come up with a valuation of the EVS services

    • Decision Points:

    Med-RTDiscussion Points:
    • .
    • Mapping - there is not an RFI for this yet.
    • Mapping should be included in the overall architecture/timeline.
    • Lyuba asked about creating usecases (ICD9, ICD10, etc)
      • How do we map from one terminology to the NCIt?

    Decision Points:

    LexEVS Security Issue
    Value Set deployment workflow triage

    Discussion Points:

    • Reviewed issues
    • Prototyped fixes in branches for CTS2, URI Resolver, LexEVS Service
    • Created partial updates to LexEVS to gauge the scope of spring updates in LEXEVS-4192
    • Alternately removed project with pom file LEXEVS-4199
    • Waiting for Kumar to set up a meeting with security, systems, and development teams
    • Kumar mentioned that there has been turn over in the security division and it will take time to get everyone together.
    • Jacob suggested that we could update/fix our security issues and then they can perform an appscan and nexus scan to see what ports are open and any other security users.
    • Tracy mentioned that the remote client users (caDSR) would need to update their client jars if/when we do security upgrades.
    • Jacob mentioned in the past, the security team considered issues fixed only when the spring version was upgraded to a version that fixes the vulnerability.

    Decision Points:

    • Jacob will look into what was last done by Phil before he left.
    • The LexEVS team will work on security issues and request an appscan and nexus scan on the services.
    • Has CTS migrated off from 6.4?  Kumar will ask Tony.  If they have, the 6.4 service will be retired.

    Decision Points:

    LexEVS External Users

    Discussion Points:

    • Tracy talked to Natalie (caDSR)about re-writing their code (data layer) using LexEVS REST service.
      • We will need to review their list API calls and convert it use LexEVS REST service.
    • Tracy mentioned CTS is still on 6.4.  There is no current work on this project.

    Decision Points:

    • Lyuba suggested that we start working on converting caDSR code (data layer) using the LexEVS REST service.
    LexEVS Meeting - week of Thanksgiving

    Discussion Points:

    Decision Points:

    • We decided we will try to schedule to next Tuesday. 
      • Jason will reschedule.
    Value Set deployment issuesDiscussion Points:
    • We need to meet with NCI development team to discuss how to move more quickly on diagnoses and fixes.

    Decision Points:

    • Scott will come up with a workflow plan on how to diagnose these issues in the future. 
      • Provide a task list of things to look at before considering this is a coding issue.
    Power outage

    Discussion Points:

    • December 8 power outage.
    • We will need to test our services when the power is back on (December 9/10).
    • This testing will be done by NCI.

    Decision Points:

    LexEVS External Users

    Discussion Points:Decision Points:
    Team Absences

    Mayo Team

    • Cory - 11/22, 11/23
    • Scott - 11/21-11/23
    • Craig - 11/21-11/23

    NCI

    • Tracy -
    • Rob - 
    • Kim -

    JIRA Issues

    Recent LexEVS Related Bugs and Features (within last week)

    ...