 |
Page History
...
| 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 |
|---|
...
| 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 |
| Discussion Points | Notes |
|---|---|
| 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? |
