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:
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.01.06
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.01.09
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.01.19
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.02.21
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.03.02
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.03.27
- LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.04.17
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
| 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). |
