LexEVS 5.0: Migrating from EVS 3.x API to LexEVS API Craig R. Stancl, Kevin J. Peterson, H. Scott Bauer, Traci V. St.Martin, Christopher G. Chute, MD PhD Department of Biomedical Statistics and Informatics Mayo Clinic, Rochester, MN What’s New in LexEVS 5.0 OWL Loader Data Services New caCORE SDK REST Interface Based on LexGrid Model Query-By-Example (QBE) queries in LexEVS 4.2 utilized the EVS model and referenced DescLogicConcept as represented in the following URL: In LexEVS 5.0, QBE queries now utilize the LexGrid 2009 model and reference Entity as represented in the following URL: LexEVS Architecture LexEVS 5.0 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 the EVS 3.2 model. LexGrid Model/DB LexEVS caCORE SDK LexEVS Java LexEVS Distributed Java LexEVS caGrid LexGrid Model/DB LexBIG Java API LexBIG Distributed Java API Adapter Legacy caCORE SDK Services Legacy EVS caGrid Services LexEVS caGrid Services (New) Release 4.2.1Release 5.0 Design Convergence LexEVS 5.0 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 the EVS 3.2 model. The convergence of LexEVS 5.0 components has introduced new naming of components: Design ComponentsRelease 4.2.1Release 5.0 EVS Model Version3.2No Longer Available EVS API Version3.2No Longer Available LexGrid Model Version2008/012009/01 LexBIG API Version The supported programming interfaces are now all provided by LexEVS: Supported Programming InterfacesRelease 4.2.1Release 5.0 Direct JavaLexBIGLexEVS Distributed Java (RMI)LexBIGLexEVS caCORE SDK ServicesEVSLexEVS caGRID ServiceEVS, LexEVSLexEVS LexEVS Resources caBIG® Vocabulary Knowledge Center Wiki - Comprehensive resource for LexEVS caBIG® Vocabulary Knowledge Center Forums – Ask LexEVS questions and find answers LexEVS 5.0 Migration Guide - Documentation to assist adopters to migrate to LexEVS /01 LexGrid Model The 2009 LexGrid Model incorporates the following major changes: Entity replaces Concept and provides name neutral terminology elements (e.g. Entity can represent a concept, association, instance, property, value domain…) Versioning – entities and properties are versionable Revised value domain and picklist OWL Loader Unified in 5.0. NCI specific adaptations are eliminated and OWL-DL is employed for all OWL loads. Generic OWL NCI OWL Unified OWL Loader Memory based loads of large OWL sources can strain the resources of memory constrained hardware systems. A new option using a temporary Protégé Data Base provides an alternative to direct to Data Base Streaming. Users may still use the option of memory based loads on high end hardware. Option 1: Model is loaded into memory and streamed into the LexGrid Data Base Option 2: Temporary Protégé Data Base helps prevent heap allocation errors. Source LexGrid Db Source Protégé Db Memory LexGrid Db Unified OWL loader (Migration from the NCI OWL loader and a generic OWL loader to a single loader) Updated to work with caCORE SDK 4.1 LexEVS 5.0 introduces LexGrid-based Query-By-Example (QBE) services LexEVS 5.0 is the first release to completely shift from the EVS Model and EVS API to LexEVS API and LexGrid Model The 2008/01 model is updated to the 2009/01 LexGrid Model New Data Services are now provided for the Grid and web service interfaces XSL transformations are provided for legacy LexGrid data To query the LexEVS 5.0 Data Grid Service, use the standard caGrid CQL query method to compose queries.  For Example: Query for a Concept with a specific Code ( Example: Concept: C12345) \ LexBIG Model Extension Users may still access ConceptReference objects, but name neutral CodedNodeReference objects are also included in the 2009 model