 |
Page History
...
- Java 8 update
- Expand the CTS2 REST interface to potentially include associations
- Loader issues with OWL2, MeDRA and HL7
- GUI updates
- RDF Triple Store or graph database LexEVS backing
- End-user Value Set editor
- Loader Tutorial/Education
- Model updates to support additional Value Set functionality
- Horizontal Coding Scheme searches
CTS2 discussion about one client should be able to connect to multiple instances of a service. Can one endpoint provide data to query against another? How can CTS2 be used in a manner that provides uri's that are not a part of the local resources.
Optional Tasks:
- LEXEVS API Performance and Usability Improvements
LEXEVS API performance and usability will be a major focus area for this effort. EVS and other users have hit a number of bugs and missing features that significantly affect the usability of the APIs, with special effort needed to improve value set, mapping, multi-namespace support as well as querying of relationship and inferred data.
Active LEXEVS support in all indicated areas is important to the quality and efficiency of ongoing EVS operations and services, and to the growing community of LEXEVS adopters for whom it provides a shared conceptual and technical terminology model supporting community standards and interoperability.
- LEXEVS Loader Improvements
The subcontractor shall address LEXEVS Loader Improvements. The LEXEVS Loaders are a set of Java programs and configuration files that transform and load terminology data from the various file formats and source terminology data structures into the unified LEXEVS server data model. They are crucial to data access and quality, and a top priority for the current effort. Key areas of effort are improving and extending loaders to better handle current and new sources and formats, and improved documentation and error handling.
- Enhancing the LEXEVS CTS2 REST Interface
The subcontractor shall address improvements to the CTS2 REST API and related resources. The previously existing REST API was created as a prototype to prove that such an interface will have value. It succeeded in that task. Unfortunately, that older API is tied very closely to the underlying structure of the data rather than being tied to the usage of the data. This effort will extend the new CTS2 API, tools and documentation to fill gaps in coverage of the CTS2 REST specification and focus on the user of the API, providing them with a clean, complete API that is easier to use than the current heavyweight solution.
- Cloud Support
The subcontractor will address the deployment, customization and maintenance of cloud-based LEXEVS services in order to address the challenges associated with the growth of biomedical research data, and the computational limitations currently experienced by biomedical researchers.
| Wiki Markup |
|---|
{scrollbar:icons=false} |
...
