NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Discussion PointsNotes
Who are the stakeholders and end users of value sets 
Define what end user interface is (Shell script, Rest Service, Browser based GUI) 

Define performance or other considerations that require a move to triple store or OWL API (For Example: Do value sets need full OWL expressivity)

 
Will non NCIt sourced value sets continue to use legacy value set definitions? (more a scope statement question) 
What considerations/requirements drive the development of an architecture that encompasses hierarchical value sets and new resolution mechanisms? 
Create OWL source for some/all values sets from LexEVS api or other source? (OWL export of value sets) 
What user needs around the report writer generate requirements for LexEVS or the LexEVS team 
Does Excel spread sheet generation fall into the scope of LexEVS value set resolution or otherwise generate requirements for the LexEVS team 
Do the users/stakeholders in the value set API have any new requirements beyond those already stated 

 

Open Questions

Questions that need further research or consideration.

Open Questions