 |
Page History
...
| Feature | Summary | Type |
|---|---|---|
| LEXEVS-3509 | I would like to add a value set to the VS hierarchy implementation from an outside source | Improvement |
| LEXEVS-3694 | Change the coding scheme name in ResolvedConceptReference returned by both search and resolution API. | Improvement |
| LEXEVS-3781 | Increase memory on LoadMetaBatch script | Improvement |
| LEXEVS-3640 | Place value set nodes in value set hierarchy using contributing source. | New Feature |
| LEXEVS-3406 | I would like to have a value set service that runs directly against the NCIt | New Feature |
| LEXEVS-3524 | Allow VS Hiearchy to be resolved from Source Asserted VS API | New Feature |
| LEXEVS-3475 | Write controller/business logic layer for Source Asserted VS API | New Feature |
| LEXEVS-3476 | Implement Source Asserted Value Set API | New Feature |
| LEXEVS-3540 | Implement Resolved Value Set Style API for Asserted Value Sets | New Feature |
| LEXEVS-3545 | Update the Resolved Value Set API to include access to Asserted Value Sets | New Feature |
| LEXEVS-3565 | Update and Verify Asserted Value Set Service API for Remote API | New Feature |
| LEXEVS-3564 | Update and Verify Asserted Value Set Search Service for Remote API | New Feature |
| LEXEVS-3639 | Change the URI in ResolvedConceptReference returned by Value Set Search and Resolution methods. | New Feature |
| LEXEVS-3642 | Support search against a specific value set or any collection of value sets. | New Feature |
| LEXEVS-3301 | I would like LexEVSTreeItem attributes to be made public or publicly accessible | New Feature |
| LEXEVS-2961 | VS Workflow: Remove Dependency on value set definition files for NCIt defined Value Sets | New Feature |
| LEXEVS-2962 | VS Workflow: Generate all NCIt sourced resolved value set coding schemes from NCIt source in LexEVS | New Feature |
| LEXEVS-3058 | Value Set: Value Set Hierarchy will be defined from that in the NCIt and returned in a performant manner | New Feature |
| LEXEVS-2967 | Value Set - (Browser) Efficient search by code or name - query for value set that this concept matches | New Feature |
| LEXEVS-2966 | Value Set - (Browser) Efficient retrieval VS definition metadata resolution calls. Faster queries against the definitions themselves. | New Feature |
| LEXEVS-3170 | Provide ability to add Non-NCIt value sets to asserted vs hierarchy | New Feature |
| LEXEVS-3057 | Value Set - Definition for LexEVS Value Set Definition Asserted Source Task | New Feature |
| LEXEVS-3074 | Value Set: Create User Defined property name parameter for Concept Domain | New Feature |
| LEXEVS-3063 | Implement Value Set Tree Integration for Browser API | New Feature |
| LEXEVS-3165 | Implement simpler approach to resolving a list of all value sets | New Feature |
| LEXEVS-3203 | Value Set - Update Resolved Value Set Query Mechanism for Optimized Search | New Feature |
| LEXEVS-3220 | Determine if a NCIt Asserted Value Set has changed | New Feature |
| LEXEVS-3494 | Follow up code cleanup test expansion for Asserted Value Set Indexing | New Feature |
| LEXEVS-3474 | I would like an index access layer to be written for the source asserted value set search | New Feature |
| LEXEVS-3339 | Modularize the full system test to allow individual modules to be run | New Feature |
| LEXEVS-3473 | I would like an Index creation layer to be written for Source Asserted Value Sets | New Feature |
| LEXEVS-3477 | Create Full Unit test suite for the API | New Feature |
| LEXEVS-3547 | Create and support a value set iterator that pages from the data base | New Feature |
| LEXEVS-3603 | Iterators for Assserted Value Sets need to be adjusted for RMI | New Feature |
| LEXEVS-3617 | Update AssertedValueSet Search Extension to work with RMI | New Feature |
| LEXEVS-3518 | I would like to include external value sets in NCIt asserted value set index | New Feature |
| LEXEVS-3517 | I would like to include Neoplasm Tree value set entities in asserted VS index | |
| LEXEVS-3445 | Create prioritization list from F2F activities | |
| LEXEVS-3413 | I would like to be able to load mapping schemes as stand alone entities | |
| LEXEVS-3636 | Update links to the CTS2 on-line documentation to NCI's URL and remove external instance | |
| LEXEVS-3146 | Investigate HistoryService getDescendants failure | |
| New Feature | ||
| LEXEVS-LEXEVS-3135 | Default page for lexevsapi6 needs to be updated | |
| LEXEVS-3189 | Code review and merge of high performance resolved value set | |
| LEXEVS-3032 | Investigate options to pull from different Docker repositories | |
| LEXEVS-3040 | Investigate LexEVS API for creating/updating entities | |
| LEXEVS-3105 | Hierarchy design/Investigation | User Story |
| LEXEVS-3171 | Investigate options for returning value sets with a non-NCIt default coding scheme (e.g., NDF-RT) | |
| LEXEVS-3278 | Investigate coding scheme name and versions for value sets | |
| LEXEVS-3597 | Update LexEVS version to 6.5.1.SNAPSHOT.6 | |
| LEXEVS-3703 | Expand Iterator Tests for Asserted Value Sets | |
| LEXEVS-3786 | LEXEVS-3783 Code review/Test and Merge | |
| LEXEVS-3749 | Update lexgrid.org to be local | |
| LEXEVS-3789 | Services don't start up when asserted value sets are not present. | |
| LEXEVS-3743 | Update Asserted Value Set default version to the PRODUCTION tag | |
| LEXEVS-3223 | Create LexEVS Dev Snapshot | |
| LEXEVS-2517 | Value Set Loader: Investigate ability to update as needed (not have to load all 700 at the same time). | |
| LEXEVS-3338 | I would like to know what the performance values of running with and without compiled value sets | |
| LEXEVS-3587 | Update Lexevs value set loader to work for CTS2 in memory tests | |
| LEXEVS-3655 | Update to support CTS2 asserted resolved value set read | |
| LEXEVS-3750 | Admin: Provide continued Product Maintenance Support (Sprint 82) | |
| LEXEVS-3739 | Add ability to determine if Asserted Value Sets exist before requesting them | |
| LEXEVS-3760 | Updated LexEVS Interface Javadoc |
...
