NIH | National Cancer Institute | NCI Wiki  

  • Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
      .

Progress

Area of InterestDetails
LexEVSThe QA team received the final 6.3 CTS2 tag from Mayo today. 
Report Writer

 

Term Browser 

Continued work on the Value Set Tree.

Spoke with the Security Team about how to improve appscan times.  Was told that it does not look like there is an obvious step to improving performance.  Recommended utilizing HP Fortify but it is not currently available to EVS development team.

Produced new Neoplasm Core hierarchy based on the Neoplasm tree in the NCIt.

    • Downloaded Neoplasm Core value set from the NCI ftp site.
    • Downloaded NCI Thesaurus, version 16.04, OWL file from the NCI ftp site.
    • Loaded NCI Thesaurus, version 16.04, OWL to Jena-Fuseki triple store server.
    • Retrieved distance one parent-child relationships from NCI Thesaurus, version 16.04 using SPARQL.
    • Developed and implemented a flooding algorithm for retrieving the distance-1 parent-child relationships among Neoplasm Core concepts.
    • Generated the new Neoplasm Core hierarchy based on the parent-child relationships obtained above.
    • Produced a HTML representation of the tree.

Produced a mapping between Neoplasm Core concepts and all NCIm sources such as ICD10, ICD9CM, and ICD10CM, and ICD-O-3, using NCI Metathesaurus.

Term Suggestion Application

NCIm BrowserPutting together scope and schedule.  Only have a couple of items in scope so far.  Mainly the move to 6.4 API but also looking at removing some data fields from the details pages that has been deemed not useful by the EVS group.
Triple Store PrototypeContinuing work on the new Report Writer using triplestore.

JIRA Issues

Issue NumberDescriptionStatus
NCIM-223

Replace NCI_MetaThesaurus by NCI Metathesaurus in hyperlinks.

Implemented.

NCIM-225Suppress properties with at least one property qualifier STYLE=AUI, or STYLE=RUI.

Evaluated the code changes required to implement the feature request.

  • Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       

  •  Planned Activities

Area of InterestDetails
Term Browser 2.9 ReleaseStart development of the 2.9 Term Browser release.
  

  • Risks, Issues, Dependencies

  • Risks

# Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 09/10/2015  H H AppScan are taking long periods of time to complete.  For Term browser, the minimum has been 5 days.We are working on both the code base and configuration of the scan to try to improve performance.  We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required.
         

  • Issues

 #Opened DateDescriptionImpactAssignedStatus
 7/17/2014Deployment of software, even small upgrades, have been a lengthy process.This especially affects smaller releases in which there are security or bug fixes. The Agile practices migration have been put on hold for now.
 09/10/2014Getting the environment in place for the Mayo trip to NCI.Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd.  We are currently one week behind.  The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place. Currently we only have the DEV environment setup for the LexEVS API>
      

  • Dependencies

Opened DateDescriptionAssigned
 .
 
   
   
  • No labels