Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails


Report Writer


Term Browser 

508 compliance reports came back for the browser and term suggestion and all appeared to pass at 100%.

ICD-O-3.1 Sort Order - Developed and implemented an algorithm for sorting both Topography and Morphology mapping entries by ICD-O-3.1 codes.

Scheduling a meeting in the new year to discuss the Value Set hierarchy design.  This is the item to work out until we can deploy to 2.12.

NCIm Browser

Scheduled to meet with user group in January to discuss future search options including searching by specific sources.

508 scan came back at 100% compliant.

Term Suggestion Application

508 scan came back at 100% compliant.

Biomarkers Support


SPARQL Report Writer

Continued development of the UI.  Completed the majority of the UI pages.  Should complete development by mid January.

Other Support


JIRA Issues

Issue NumberDescriptionStatus

Missing coding scheme version in value set search result.

Performed trouble-shooting on a related issue reported by the Operations team.

NCIM-241508 All layout tables must be labeled as presentation.


NCITERM-776Replace the existing CDISC code list and caDSR source combo-box by editable combo-box.Implemented

Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
Area of InterestDetails

Risks, Issues, Dependencies


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.


 #Opened DateDescriptionImpactAssignedStatus
 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>


Opened DateDescriptionAssigned