![]() |
Page History
...
Proposed or Possible Requirement | Priority | Notes | Is Requirement? (Yes/No) | ||||
---|---|---|---|---|---|---|---|
Remove Dependency on value set definition files for NCIt defined Value Sets | There are still some value sets that need to be approached with the old value set method. | yes | |||||
Generate All NCIt sourced value set coding schemes from NCIt source in LexEVS (DB) | There are still some value sets that need to be approached with the old value set method. | yesGenerate all | |||||
(Browser) Auto generate value set definitions | forfrom the NCIT source |
| yes | ||||
Resolve discrepancies between number of value set definition files and value sets defined in NCIt | This is not necessary | no | |||||
Provide acceptable substitutions for value set URI's and other metadata that is defined in the source (List in other rows as necessary) | yes | ||||||
Maintain Resolved Value Set Coding Scheme API as interface |
| yes | |||||
Provide concurrent value set loading capability | This was originally a suggestion on how to speed the load up. This could still be a possibility that we should look at going forward, | no | |||||
Provide programmatic access to value set definition XML files | We need efficient way to retrieve this day (Kim)
| no |
| ||||
Do we need to define A8 as an association each time | no | ||||||
(Browser) Provide efficient way to retrieve label (CS name) and version of all resolved value set coding schemes |
| yes | |||||
**** (Browser) Maintain the VS definition metadata around the source and description. |
| yes | |||||
(Browser) Auto generate value set definitions from the NCIT source | yes | ||||||
Reify relationship restrictions in the resolution of the value set members
| May need to discuss this with Larry/Gilberto | ? | |||||
(Browser) Efficient resolution of VS graphs as it pertains to hierarchies | Seconds | yes | |||||
(Browser) Efficient results to VS resolutions | sub second for most | yes | |||||
(Browser) Efficient retrieval VS definition metadata resolution calls | 1 second or less | yes | |||||
(Browser) Efficient search by code or name - query for value set that this concept matches | This needs further definition/discussion with Kim. | ? | |||||
(Browser) Source specific information - need to call lexevs LexEVS API for each vs Iterator without having to further query | Kim mentioned this when you click the value set button. | ? |
...