Version |
Development Focus |
Release Date |
LexEVS 6.5.5 This version is available and sup=
ported. |
Log4j Fixes
Update=
log4j to 2.17.1 Bug Fixes and API Updates |
February 2022 |
LexEVS 6.5.4 This version is available and sup=
ported. |
Loader Fixes Loader up=
dates. Bug Fixes and API Updates Graph DB and Gra=
ph Resolve REST API |
August, 2020 |
LexEVS 6.5.3 This version is deprecated. |
Loader Fixes Loader up=
dates. Bug Fixes and API Updates |
September, 2019 |
LexEVS 6.5.1.3 This version is deprecated.=
p> |
Loader Fixes Loader updat=
es. |
December, 2018 |
LexEVS 6.5.1.2 This version is retire=
d and unavailable.
|
Loader Fixes Loader up=
dates. |
November, 2018 |
LexEVS 6.5.1.1 This version is retire=
d and unavailable.
|
Loader/UI Patch
Lo=
ader and UI fixes. |
September, 2018 |
LexE=
VS 6.5.1 This version is retired and unavailable.=
|
NCIt Source Asserted Value Sets Allow the automated building of value sets based on keywords buil=
t into the NCI Thesaurus. There are currently over 1000 value sets in NCIt.=
|
August, 2018 |
LexE=
VS 6.5.0 This version is retired and unavaila=
ble.
|
Java 1.8 Update LexEVS=
to be built and run with CentOS 7, Java 1.8, Tomcat 8, MySQL 5.6 <=
br> |
June, 2017 |
Le=
xEVS 6.4.1.4 This version is retired and unavailable.=
|
Resolved Defects<=
/p>LexEVS 6.4.1.4 NCIT loader upgrade to load OWL2, Loader fixes a=
nd Admin script fixes. |
April, 2017 |
Le=
xEVS 6.4.1.3 This version is retired and unavailable.=
|
Resolved Defects and Enhancements=
strong> LexEVS 6.4.1.3 Loader fixes and Admin UI and C=
LI enhancements. |
March, 2017 |
Le=
xEVS 6.4.1.2 This version is retired and unavailable.=
|
Resolved Defects<=
/p>LexEVS 6.4.1.2 Fixes a codingSchemeReference defect: hashCode Method =
in CodingSchemeReference can fail. |
November, 2016 |
LexEVS 6.4.1.1 This version is retired and unavailable.
|
Resolved Defects
LexEVS 6.4.1.1 Fixes a search defect: Searching for the NCI=
Metathesaurus concept with source SRC and source-code V-NCI (or any source=
code of the form SRC-(source name) is failing. |
November, 2016 |
LexEVS 6.4.1 Thi=
s version is retired and unavailable. |
LexEVS Lucene upgrade, LexEVS=
Loader Enhancements, new HTT=
PS Requirements, Admin script updates, and Resolved Defects=
strong> LexEVS 6.4.1 provides an upgrade to Lucene, the unde=
rlying search engine, additional OWL2, HL7 and other loader enhanceme=
nts, ability to run services over HTTPS, and updates to existing admin scri=
pts.
- Lucene software upgrade to 5.2.1.
- OWL2 loader enhancements around restrictions and annotations.
- HL7 loader enhancement to account for a namespace.
- Enable LexEVS services to run on the HTTPs protocol.=
- Admin script updates around general usage.
|
October, 2016 |
LexEVS 6.3 This versio=
n is retired and unavailable.
|
LexEVS Loader Enhancements and Enhanced CTS2 API Documentation. Le=
xEVS 6.3 provides additional OWL and loader enhancements and an update to t=
he interactive CTS2 API documentation.
|
August, 2015 |
LexEVS 6.2 This version is retired and unavailable. |
CTS2 REST Implementation Enhancements=
, LexEVS software component upgrades, Implementation of a =
prototype Value Set Viewer, and Resolved Defects<=
br>
LexEVS 6.2 provides additional implementation of the CTS2 REST specificati=
on as well as upgrading LexEVS software components to new versions.
- CTS2 Implementation Enhancements=20
- Updated the CTS2 compliant REST service from the 1.0 to 1.1
- Implementation of the CTS2 Value Set Module
- Added the ability to filter for active only entities or active and inac=
tive entities
- Added the ability to adjust landing page in the LexEVS CTS2=
service application
- LexEVS Software Component Upgrades
- Java 1.7.x
- MySQL 5.5.x
- Apache Tomcat 7.0.x
- CentOS 6.0
- Additional Functionality
- Implemented a convenience method for identifying and retrie=
ving resolved value set coding schemes
- NCI CTS2 Value Set Viewer
|
October, 2014 |
LexEVS 6.=
1 This version is deprecated. It is=
supported until the end of 2016. |
CTS2 REST Specification Implementatio=
n, Content Loaders
LexEVS 6.1 provides support for the emerging CTS2 REST specification=
as developed in by the HL7 and OMG Standards organizations
|
May, 2014 |
LexEVS=
6.0 This version is retired and un=
available. |
Higher Standards
This release is primarily about alignment with standards. Other significan=
t functionality, especially in the authoring APIs, value sets, mappings, an=
d exporters makes a big difference.
- LexEVS 6.0 adds comprehensive support of the Common Terminology Service=
s - Release 2 functionality as described in the Health Level Seven (HL7) CT=
S 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 retired and un=
available. |
Enhancing Search and Sorting Performa=
nce
This is an enhancement version, based on the new architecture introduced i=
n LexEVS 5.0. 5.1 focuses on providing features that support the NCI Metath=
esaurus 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:=20
- Lucene 2.4 fast search engine with lazy document loading.
- Plug-in search framework that allows a text query string input and gene=
rates a Lucene query output.
- Plug-in sort framework that allows rapid creation of new sort algorithm=
s and techniques.
- SQL query optimaizations that increase database performance.
- LexEVS Value Domain Service - provides programmatic access to load valu=
e domain definitions using the domain objects that are available via the Le=
xGrid logical model.
- LexEVS Pick List Service - provides programmatic access to pick list de=
finitions using the pick list that are available via the LexGrid logical mo=
del.
- Loader framework enhancements - improved loading capability; allows loa=
ders to be modular and easily extendable; ability to load custom data.
- RRF loader enhancements - ability to fully load RRF data; support the N=
CI 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 un=
available. |
Next generation of NCI Enterprise Voc=
abulary Services
This version represents the next generation of NCI Enterprise Vocabulary S=
ervices. 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.=
p>
- Complete shift from the EVS Model and EVS API to the LexBIG API and Lex=
Grid Model. LexGrid Enterprise Vocabulary Services is now known as LexEVS.<=
/li>
- 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 rest=
rictions on a search request, which are automatically combined by the runti=
me 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 mu=
ltiple search restrictions based on association name or qualifier).
- Compared to the legacy EVS model, the LexGrid model is capable of repre=
senting additional ontology sources and/or semantics for some sources.
- Improved concept search (support of additional match algorithms, abilit=
y 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 analyti=
cal grid service .
|
May 14,2009 |
LexE=
VS 4.2.1 This version is retired an=
d 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 archit=
ectures with LexGrid/LexBIG technologies. This allows the same vocabularies=
to be served in terms of the older EVS model (via pre-existing EVS APIs) o=
r the LexGrid model (via the LexBIG API).
- The legacy EVS model and API have been formally deprecated in this rele=
ase.
- Fundamental goal for the release is to provide a migration path that al=
lows users to transition from the older/legacy EVS interfaces toward adopti=
on of newer LexEVS interfaces (based on the LexGrid model and LexBIG API).<=
/li>
- Many EVS and LexGrid/LexBIG components are individually packaged, versi=
oned, and installed. As the transition from the legacy EVS interfaces compl=
etes (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 <=
br class=3D"atl-forced-newline">
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 prioriti=
zed needs of the caBIG=C2=AE community.
- Provides a flexible implementation for vocabulary storage and persisten=
ce, allowing for alternative mechanisms without impacting client applicatio=
ns or end users. Initial development will focus on delivery of open source =
freely available solutions, though this does not preclude the ability to in=
troduce commercial solutions (e.g. Oracle).
- Provides standard tooling for load and distribution of vocabulary conte=
nt. This includes but is not limited to support of standardized representat=
ions 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 re=
trieved through the LexBIG system, and is rich enough to represent vocabula=
ries provided in numerous source formats including:=20
- Open Biomedical Ontologies (OBO)
- Web Ontology Language (OWL)
- Unified Medical Language System (UMLS) Rich Release Format (RRF)
|
October 10, 2008 |