NIH | National Cancer Institute | NCI Wiki  


Please be advised that NCI Wiki will be will be undergoing maintenance on Monday, June 24th between 1000 ET and 1100 ET.
Wiki will remain available, but users may experience screen refreshes or HTTP 502 errors during the maintenance period. If you encounter these errors, wait 1-2 minutes, then refresh your page.

If you have any questions or concerns, please contact the CBIIT Atlassian Management Team.


Wright, Larry NIH/NCI  x
Fragoso, Gilberto NIH/NCI    x

De Coronado, Sherri    


Safran, Tracy

Ong, Kim L
Lucas, Jason R
Bauer, Scott  Mayox
Stancl, Craig
Endle,  CoryMayox
Wynne, Robert    NIH/NCIx
Pan, JJ
Tran, Tin    NIH/NCI [C]  
Ahmed, Shamim
NIH/NC [C]  
Haber, Margaret (NIH/NCI) 
Roth, Laura (NIH/NLM)  
Ramani, Vivek (NIH/NCI) [C]  
Carlsen, Brian (NIH/NCI) [C] 
Wong, Joanne   

Kuntipuram, Kumar

Gavin Brennan x
Preston Wood x


Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
64ScottTo follow up on URI's on OWL2 with Harold.   on hold

Scott to work with Gilberto to determine what is needed for OWL 2 requirements


on hold

164CoryCory to add implementation to CTS2 implementations page.2014.04.30  on hold
170ScottUpdate the ARC dates to include range of dates for each tier.2014.05.14  on hold
185GilbertoCreate Jira for OWL 2 Annotation issue in the API.2014.05.28  on hold
197ScottDo a gap analysis on what the URI_Resolver logs and what NCI would like to know from these logs2014.6.18  on hold
200Larry/SherryQuery current LexEVS users about use of SOAP, REST or QBE services in the legacy caCORE api's2014.6.18  on hold
207CoryWrite issue against CTS2 OMG regarding the ability to return INACTIVE concepts only.2014.07.30  on hold
209Craig/LarryPlan Techical F2F/AMIA meetings.2014.07.30  

on hold

210Larry/GilbertoDetermine if there is a need to meet with the CTRP2014.07.30  on hold
212LarryInclude LexGrid XML Export as part of the 5.1 retirement notice. 2014.07.30  

on hold

224ScottURI Resolver - Provide overview of how to access the URI Resolver2014.09.03  

on hold

225ScottURI Resolver - Look at TLAMP and VSAC service to determine usage of URI Resolver2014.09.03  on hold
233CoryLet Tracy know when to re-Index after CTS2 fix is rolled up the tiers. 2014.10.02  


234Joanne and BrianProvide ICD10-CM issue details to Scott for evaluation.2014.10.02  done
235Mayo TeamIdentify additional value set JIRA items to be included in 6.3 release.2014.10.02  open
236CraigCreate MOD4 project plan.2014.10.02  open
237ScottFinal code deliverables posted to SFTP site and wiki pages updated.2014.10.02  open
238ScottCreate JIRA items for ICD10-CM issues (from Joanne)2014.10.08  done


Immediate Priorities and Problems (Mayo Team)

Scott: CTS2 deployment, SNOMED/ ICD10CM issues, Issues support

    • Support - 3 external users.  One from ASU, one from Spain, and one other.   Indications that we need to have improved documentation.   
      • Eric - Scott to follow up (from Gilberto) - looking to set up a federated set of CTS2 notes for German universities
      • Some of the issues - mismatches of GIT content being used; support of non-tested versions of tech stack.  
      • May want to consider "bootcamp" like education - was we did back during the caBIG days 

Cory: CTS2 issue and AMIA Poster

    • AMIA poster sent to authors
    • CTS2 search issues
    • JIRA issue

Craig: Project Plan, Project Startup, Poster

  • Plan on sending plan out this week
  • Initial product dev documentation section of wiki created.  Will add documents as required.


Loads at NCI are acting differently than our loads here at Mayo.

Plan on reload transitive table (after DB restart).  Then look at SQL settings/variables in configuration to determine if there are differences. 

ICD10 CM - comments from Joanne and Stephanie.   It was decided that LexEVS is now doing what is needed, but Stephanie needs to work out some content issues.  

CTS2 Issue

Cory and Scott investigated and determined that index is missing in the DB - need to have indexes built on QA to reflect the database on QA.  Rob working on getting the indexes on Dev - going to bounce the DB and then reload.  If successful, then move the indexes to QA.  

Production Tier Server Configuration (Gavin @ 2:30-3PM)

Stage currently not avaible to outside users for testing.  Want to move Stage to the same segment as Production. 

Separate STAGE server in the production network segment.   (1 production blade and 1 stage blade)

Would prefer to have a fail-over blade. 

This is a security policy in that the servers that are on an external segment need to be APP scanned.   There cannot be a non-app scan server on the network with external accessible servers (PROD).

There are 2 blades provisioned in the production environment (Blade A is primary and Blade B is fail over)

There is a need to isolate tiers from other tiers.

Suggested to use the second Blade (with option to use the blade if primary blade goes down).

Need to consider I/O contention, lucene indexes, paths, etc, if 2 instances.   There is sufficient DB storage.  100GB was planned in the arch document.  (2 instances (STAGE and PROD) on the same blade server)

There are currently 4/socket and 4 sockets per blade server.  

LexEVS was first to be deployed in this new environment.  

Blade A is running production (like Stage on lower tier).  Blade B is running differently than production. 

It was suggested to start with the 2 Blades in production as A - Production and B - Stage.

As procurement processes get better, then consider additional servers.  

Lucene on SAN-based (8 GB fiber, not internal drive) - would this work?  Would normally try this in QA.  

Collaborators are testing software outside the firewall. 

Diagrams to be created to visual the environment. 


POST AMIA Discussion

Possible discussion on Wednesday PM or Thursday AM/PM.  

Thursday could work.  Need to come up with agenda/topics.  




JIRA Issues

LEXEVS-570 - Getting issue details... STATUS
LEXEVS-573 - Getting issue details... STATUS
LEXEVS-579 - Getting issue details... STATUS
LEXEVS-586 - Getting issue details... STATUS
LEXEVS-594 - Getting issue details... STATUS
LEXEVS-597 - Getting issue details... STATUS
LEXEVS-598 - Getting issue details... STATUS
LEXEVS-599 - Getting issue details... STATUS
LEXEVS-605 - Getting issue details... STATUS
LEXEVS-606 - Getting issue details... STATUS
LEXEVS-607 - Getting issue details... STATUS
LEXEVS-608 - Getting issue details... STATUS
LEXEVS-609 - Getting issue details... STATUS
LEXEVS-612 - Getting issue details... STATUS
LEXEVS-613 - Getting issue details... STATUS
LEXEVS-615 - Getting issue details... STATUS
LEXEVS-616 - Getting issue details... STATUS
LEXEVS-617 - Getting issue details... STATUS
LEXEVS-618 - Getting issue details... STATUS
LEXEVS-619 - Getting issue details... STATUS
LEXEVS-620 - Getting issue details... STATUS
LEXEVS-621 - Getting issue details... STATUS
LEXEVS-622 - Getting issue details... STATUS
LEXEVS-623 - Getting issue details... STATUS
LEXEVSCTS2-2 - Getting issue details... STATUS
LEXEVSCTS2-3 - Getting issue details... STATUS

Project Plan Changes

#DescriptionDue DateResourcesNotesRisksMitigation

 Planned Activities

Area of InterestDetails

Risks, Issues, Dependencies


Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy


 #Opened DateDescriptionImpactAssignedStatus


Opened DateDescriptionAssigned





  • No labels