NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Contents of this Page

This page is for capturing the discussion around updating the workflow for value set definition creation.

Meeting Minutes

Value set requirements gathered through meetings with the NCI stakeholders.  Minutes from the meetings are here:

Discussion Points

  • LexEVS model and implementation are more complex than requirements of most NCI value sets
  • NCI Thesaurus may have enough assertions to adequately describe value sets without external modeling
  • User needs beyond the browser should be recorded
    • should include report writer
    • excel spread sheet file consumers
    • any users of value set definition and resolved value set XML files.
    • consumers of the value set api
    • Neoplasm value set types (containing self asserted hierarchy)

Proposed Support and Solutions

  • Provide concurrent value set loading capability.
  • Provide OWL export of value sets
  • Provide programmatic Access to value set definition expressed as XML
  • Provide examples for regular api level access of value set members
  • Provide support for Neoplasm like value sets. 

Requirements

Requirements for the new value set work flow architecture

RequirementPriority

Better logging to help determine if there were any failures for resolving the 760+ value sets.

 
Resolving all 760+ value sets should be able to finish over night (Rob). 

 

Proposed or Possible Requirements

RequirementPriority
Remove Dependency on Value Set Definitions for NCIt defined Value Sets 
Generate All Value Sets from NCIt source. 
Resolve discrepancies between value set definition file set and value sets defined in NCIt 
Provide acceptable substitutions for value set URI's and other metadata that is not defined in the source (List in other rows as necessary) 
Maintain Resolved Value Set Coding Scheme API as interface 
Create OWL source for some/all values sets from LexEVS api or other source? 
Define performance or other considerations that require a move to triple store or OWL API. 
Define what end user interface is (Shell script, Rest Service, Browser based GUI) 
Non NCIt sourced value sets continue to use legacy value set definitions 
What considerations/requirements drive the development of an architecture that encompasses hierarchical value sets and new resolution mechanisms 

 

 

  • No labels