View Source

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:

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)

Requirements for the new value set work flow architecture

Requirement	Priority
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, Issues, Definitions

Requirement	Priority
Remove Dependency on Value Set Definitions for NCIt defined Value Sets
Generate All NCIt sourced 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
Define what end user interface is (Shell script, Rest Service, Browser based GUI)
Non NCIt sourced value sets will continue to use legacy value set definitions (more a scope statement)
What considerations/requirements drive the development of an architecture that encompasses hierarchical value sets and new resolution mechanisms
Define performance or other considerations that require a move to triple store or OWL API
Create OWL source for some/all values sets from LexEVS api or other source?