NIH | National Cancer Institute | NCI Wiki  

 Attendees

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

De Coronado, Sherri    

NIH/NCI    

Safran, Tracy

NIH/NCI   x
Ong, Kim L
ISx
Lucas, Jason R
ISx
Bauer, Scott  Mayox
Stancl, Craig
Mayox
Endle,  CoryMayox
Wynne, Robert    NIH/NCIx
Pan, JJ
NIH/NCI [E]x
Tran, Tin    NIH/NCI [C] x
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

  

 

Action Items

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

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

2014.04.30  

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  

done

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  open

Progress

Immediate Priorities and Problems (Mayo Team)

Scott: URI Changes, SNOMED load, Kim's Issue, CTS2 Issues

    • CTS2 Service issues have been resolved and anticipate things to work once re-indexed. 
    • URI Resolver - AppScan identified some risks.  Scott updated the code in the resolver - using prepared statements to elimiate the possiblity of SQL injection.  Latest Appscan didn't identify any continued issues.  URI resolver is ready to be deployed.
      • There is a new tag and PTE updated.
    • SNOMED - recent loads on new system. 

Cory: CTS2 issue and AMIA Poster

    • Confirmed issue with CTS2 with Scott
    • AMIA poster draft to be send by next Wednesday. 

Craig: Project Plan, Project Startup, Poster

    • Will create a new plan with ongoing support issues.
    • Project documents being created on WIKI.
 

 

 

SNOMED Load

Continued review of SNOMED issue.  Determined there is no transitivity table built.   This would possibly be why hierarchy isn't displayed in the term browser.  Scott to continue to investigate and identify if hierarchy was ever present - or merely using the qualifiers to determine hierarchy (CHD Relation). 

Need to know how this is being done in the term browser (Kim to provide??).   

    • Using API to dyamically create the hierarchy and uses getHierarchyRoots.
  
AMIA PosterPlan on having a draft to show next week to get feedback.  
ICD10-CM Loading Issue with 6.1

Scott did get the information from Joanne.  Hasn't had time to review.   There may be todos for the loader based on feedback - will create JIRA item to capture these requests.   Should be less priority than SNOMED as Joanne has a work around. 

Determined that we are not showing hierarchy - no "@" or "@@" rows being created. 

  
CTS2 Issue

Re-indexing is expected to solve problems.

There are DRT tickets that need to be resolved for DEV (too many files).

  

 

 

 

JIRA Issues

Description
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
 None     
       
       

 Planned Activities

Area of InterestDetails
  
  
  

Risks, Issues, Dependencies

Risks

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

Issues

 #Opened DateDescriptionImpactAssignedStatus
      
      
      

Dependencies

Opened DateDescriptionAssigned
   
   

 

 

 

 

  • No labels