Page History
...
LexEVS 6.5.1 - Features Implemented
Feature | Summary | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
LEXEVS-2961 | VS Workflow: Remove Dependency on value set definition files for NCIt defined Value Sets | ||||||||||||
| VS Workflow: Generate all NCIt sourced resolved value set coding schemes from NCIt source in LexEVS | ||||||||||||
| Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves. | ||||||||||||
LEXEVS-2967 | Value Set - (Browser) Efficient search by code or name - query for value set that this concept matches | ||||||||||||
LEXEVS-3057 | Value Set - Definition for LexEVS Value Set Definition Asserted Source Task | ||||||||||||
LEXEVS-3058 | Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant manner | ||||||||||||
LEXEVS-3063 | Implement Value Set Tree Integration for Browser API | ||||||||||||
LEXEVS-3074 | Value Set: Create User Defined property name parameter for Concept Domain | ||||||||||||
LEXEVS-3165 | Implement simpler approach to resolving a list of all value sets | ||||||||||||
LEXEVS-3170 | Provide ability to add Non-NCIt value sets to asserted vs hierarchy | ||||||||||||
LEXEVS-3203 | Value Set - Update Resolved Value Set Query Mechanism for Optimized Search | ||||||||||||
LEXEVS-3220 | Determine if a NCIt Asserted Value Set has changed | ||||||||||||
LEXEVS-3301 | I would like LexEVSTreeItem attributes to be made public or publicly accessible | ||||||||||||
LEXEVS-3406 | I would like to have a value set service that runs directly against the NCIt |
LexEVS 6.5.1 - Defects Fixed
...