Future

• Implementation of CTS 2 (preliminary) aligned API:
  • Java API (update and deprecate 6.0)
  • REST API (new)
  • SOAP API (new)
• Provide support for OWL 2 (Import/Export)

LexEVS 6.0
This version is available and supported.

Higher Standards
This release is primarily about alignment with standards. Other significant functionality, especially in the authoring APIs, value sets, mappings, and exporters makes a big difference.

• LexEVS 6.0 adds comprehensive support of the Common Terminology Services - Release 2 functionality as described in the Health Level Seven (HL7) CTS 2 Draft Standard for Trial Use (DSTU).
• LexGrid Model and database updates to support CTS 2
• Loader and data access layer changes to support CTS 2 functions
• Additional versioning and value set / picklist functionality to support CTS 2 functions
• New OWL/RDF Exporter
• XML exporter enhancements to provide filtered export of code system
• New Authoring API services to support CTS 2 functions
• New Query API services to support CTS 2 functions
• Associations/Mappings enhancements to support CTS 2 functions and user requirements

February 2, 2011

LexEVS 5.1
This version is deprecated. It is supported until at least the end of 2012.

Enhancing Search and Sorting Performance
This is an enhancement version, based on the new architecture introduced in LexEVS 5.0. 5.1 focuses on providing features that support the NCI Metathesaurus Browser in the areas of performance and loading. Value Domain, Pick List Services and the loader framework had significant changes as well.

• Enhanced query performance and behavior:
  • Lucene 2.4 fast search engine with lazy document loading.
  • Plug-in search framework that allows a text query string input and generates a Lucene query output.
  • Plug-in sort framework that allows rapid creation of new sort algorithms and techniques.
  • SQL query optimaizations that increase database performance.
• LexEVS Value Domain Service - provides programmatic access to load value domain definitions using the domain objects that are available via the LexGrid logical model.
• LexEVS Pick List Service - provides programmatic access to pick list definitions using the pick list that are available via the LexGrid logical model.
• Loader framework enhancements - improved loading capability; allows loaders to be modular and easily extendable; ability to load custom data.
• RRF loader enhancements - ability to fully load RRF data; support the NCI Metathesaurus Browser.
• BDA (Build and Deployment Automation) support - build and deployment of LexEVS project artifacts to remote servers.

January 5, 2010

LexEVS 5.0
This version is retired and unavailable.

Next generation of NCI Enterprise Vocabulary Services
This version represents the next generation of NCI Enterprise Vocabulary Services. In this release, the LexBIG Java API and LexGrid model become the strategic EVS interfaces, replacing the legacy EVS API and EVS 3.2 model.

• Complete shift from the EVS Model and EVS API to the LexBIG API and LexGrid Model. LexGrid Enterprise Vocabulary Services is now known as LexEVS.
• Introduces LexGrid-based QBE services.
• Consistent naming and release numbers for API and services.
• Unified OWL loader (Migration from the NCI OWL loader and a generic OWL loader to a single loader).
• The 2008/01 model is updated to the 2009/01 LexGrid Model.
• Optimized query execution (ability to place an arbitrary number of restrictions on a search request, which are automatically combined by the runtime when on node or graph resolution).
• Improved graph navigation (navigation of arbitrary relationships within a specific distance, uni or bi-directional navigation, ability to place multiple search restrictions based on association name or qualifier).
• Compared to the legacy EVS model, the LexGrid model is capable of representing additional ontology sources and/or semantics for some sources.
• Improved concept search (support of additional match algorithms, ability to place multiple search restrictions based on properties by type, name, value, or qualifier).
• LexEVS now offers a LexEVS data grid service in addition to the analytical grid service .

May 14,2009

LexEVS 4.2.1
This version is retired and unavailable.

Migration Path
This version supports the EVS adapters through LexBIG but also introduces LexEVS API.

• Represents a hybrid design, integrating components of legacy EVS architectures with LexGrid/LexBIG technologies. This allows the same vocabularies to be served in terms of the older EVS model (via pre-existing EVS APIs) or the LexGrid model (via the LexBIG API).
• The legacy EVS model and API have been formally deprecated in this release.
• Fundamental goal for the release is to provide a migration path that allows users to transition from the older/legacy EVS interfaces toward adoption of newer LexEVS interfaces (based on the LexGrid model and LexBIG API).
• Many EVS and LexGrid/LexBIG components are individually packaged, versioned, and installed. As the transition from the legacy EVS interfaces completes (in version 5.0), all packages will begin to carry the LexEVS name and abide by the same conventions for version numbering

February 6, 2009

LexBIG 2.3
This version is retired and unavailable.

Robust vocabulary services
This release provides a robust and scalable open source implementation of EVS-compliant vocabulary services.

• The API specification is based on but not limited to fulfillment of the caCORE EVS API - The input/output parameters used by EVS API adapters. The specification also accommodates changes and requirements based on prioritized needs of the caBIG® community.
• Provides a flexible implementation for vocabulary storage and persistence, allowing for alternative mechanisms without impacting client applications or end users. Initial development will focus on delivery of open source freely available solutions, though this does not preclude the ability to introduce commercial solutions (e.g. Oracle).
• Provides standard tooling for load and distribution of vocabulary content. This includes but is not limited to support of standardized representations such as UMLS Rich Release Format (RRF), the OWL web ontology language, and Open Biomedical Ontologies (OBO).
• This model provides the core representation for all data managed and retrieved through the LexBIG system, and is rich enough to represent vocabularies provided in numerous source formats including:
  • Open Biomedical Ontologies (OBO)
  • Web Ontology Language (OWL)
  • Unified Medical Language System (UMLS) Rich Release Format (RRF)

October 10, 2008