EVS Tools Meeting Minutes - 30 August 2017

Attendees

#	Assigned	Description	Date Identified	Due Date	Date Completed	Status
						.

Area of Interest	Details
LexEVS
Report Writer
Term Browser	DAP implementation patch for 2.11 is now on Production awaiting deployment of LexEVS 6.5.
NCIm Browser	DAP implementation patch for 2.11 is now on Production awaiting deployment of LexEVS 6.5.
Term Suggestion Application	DAP implementation patch for 2.11 is now on Production awaiting deployment of LexEVS 6.5.
EVS REST API	Added the following concepts to main types. Kidney Carcinoma (C9384) Malignant Eye Neoplasm (C4767) Malignant Bone Neoplasm (C4016) Paget Disease (C7073) Renal Pelvis and Ureter Carcinoma (C7515) Produced a new main type hierarchy file. Repair the MainTypeHierarchy isDisease method for two concepts: Disease, Disorder or Finding (Code C7057) Disease or Disorder (Code C2991)
Biomarkers Support
Neoplasm Core
Other Support

Issue Number

Description

Status

LEXEVS-1732

Coding scheme name and version of ResolvedConceptReference

Assessed a possible solution proposed by Mayo. The method will not work for all forms of resolved value set coding schemes.

Reported a possible error in Metathesaurus namespace returned by the CTS2 API.

#	Description	Due Date	Resources	Notes	Risks	Mitigation

Area of Interest	Details

Risks

#	Opened Date	Due Date	Description	Likelihood (H, M, L)	Impact	Assigned	Status	Mitigation 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.

Opened Date	Description	Impact	Status

09/10/2014	Getting 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>