1. LexEVS 6.0 Overview Scott Bauer Mayo Clinic Rochester, Minnesota February 2011

2. LexEVS 6.0 Overview LexEVS 6.0 Current Implementation Key Features Infrastructure Enhancements High Level Architecture 2

3. LexEVS 6.0 – Current Release LexEVS 6.0

4. LexEVS 6.0 – Key Features Implements the draft specification for HL7 Common Terminology Services 2 (CTS 2). Supports mapping associations between terminologies. Value set, pick list, and versioning support. Authoring API and loader enhancements. New OWL/RDF Exporter. 4

5. LexEVS 6.0 – CTS 2 Functionality 5 LexEVS 5.1 already supports much of the functionality detailed in CTS 2 Administration Search / Query LexEVS 6.0 adds comprehensive support for CTS 2 functionalities that are either partially supported or unsupported in LexEVS 5.1. LexEVS 6.0 is a preliminary reference implementation that: Provides expanded support for value sets Provides the ability to provide local extensions to code sets and maps among code sets. Develop other capabilities called for in the HL7 CTS 2 Specification (DSTU) Draft Standard for Trial Use.

6. LexEVS 6.0 - Infrastructure – CTS 2 Functionality Enhancements Administrative Functionality Content Dependency Notification Search / Query Functionality Value Set and Concept Domain Search / Query Authoring / Curation Functionality Code System Authoring / Curation Value Set Authoring / Curation Concept Domain and Usage Context Authoring / Curation Association/Mapping Functionality Association Administrative Functionality Association Search / Query Functionality Association Author / Curation Functionality

7. LexEVS 6.0 – Mapping Functionality Mapping functionality in LexEVS has been enhanced to provide the following functionality: Create Association - Relates a single specific coded concept within a specified code system (source) to a corresponding single specific coded concept (target) within the same or another code system, including identification of a specified association type. Update Association Status - Update the status of an association (active, inactive, canceled etc). This allows the ability to activate or inactivate a given association, thus changing its availability for access by other terminology service functions. Persist MRMAP data - Creates association and qualifier for the given concept as target establishing a "map entry" with unprocessed text string from MRMAP row as qualifier value. Other values for association predicate and source pulled from MRSAT as required. 7

8. LexEVS 6.0 – Mapping Functionality Mapping functionality in LexEVS has been enhanced to provide the following functionality: Enhanced query API to allow mapping to mapping graph traversal. LexEVS API can create maps in the form of: LexGrid java objects Load maps from XML file in LexGrid format. MRMAP data files 8

9. LexEVS 6.0 – Value Set Functionality The Value Set Definition of the LexGrid Model is the mechanism for describing the contents of Value Sets. Provides capability to represent a subset of Code System. Provides capability to combine contents from one or more Code Systems. The contents are concept codes defined in a referenced Code System. Value Set can contain concept codes from one or more Code Systems. 9

10. LexEVS 6.0 – Authoring Functionality LexEVS 6.0 API and LexGrid 2010 model have been designed to provide capabilities to make changes to the terminology elements. The LexEVS Authoring API implementation provides the following authoring functionality: Create / Maintain Code System Code System Supplement Concept Association Type Value Set Concept Domain Usage Context Association 10

11. LexEVS 6.0 – Authoring Functionality LexEVS Authoring API provides ability to query terminology content based on: Revision - This allows users to get the state of an entity like concept code, coding scheme, pick list, etc, at the given revision. Specific Date and Time - This allows users to get the state of an entity like concept code, coding scheme, pick list etc, at the given date and time. The LexEVS authoring tasks assume that there is an external authoring tool that persists partially formed content and performs the necessary validation and reasoning tasks prior to their being incrementally loaded into the LexEVS services. LexEVS Authoring API can accept changes to the terminology contents in the form of LexGrid java objects OR XML file in LexGrid format. 11

12. LexEVS 6.0 – OWL/RDF Exporter Content may be loaded into LexEVS from any of the LexEVS supported Load Formats. Once loaded, the content may be transformed and exported as OWL/RDF. The transformation uses the Jena API to produce an OWL/RDF representation of the LexGrid Model. Entity Entity Code : VegetarianPizza Entity Code Namespace : pizza isDefined : true Entity Description : PizzaVegetariana Exports to: true PizzaVegetariana 12

13. LexEVS 6.0 - Infrastructure – Additional Enhancements Additional enhancements included in LexEVS 6.0: Updated Data Access Layer Enables authoring capabilities Allows for diverse set of data sources (MySQL, DB2, Oracle, etc.). ISO 21090 data type support for grid analytical services Load Balancing Filtered Exporter 13

14. LexEVS 6.0 - High Level Architecture 14 Local Client Application LexEVS Local Runtime CTS 2 Distributed LexEVS Analytical Grid Distributed Client Application RMI LexEVS caCORE API’s Soap/ REST/ QBE Clients Grid Client Application LexEVS Model Objects Extended for CTS 2 LexGrid DB Lucene Index Files Clients Application Service Core API Indexes and Data Source DAO

15. LexEVS Resources LexEVS Project http://gforge.nci.nih.gov/projects/lexevs/ caBIG® Vocabulary Knowledge Center Wiki Comprehensive resource for LexEVS https://cabig-kc.nci.nih.gov/Vocab/KC/index.php/Main_Page caBIG® Vocabulary Knowledge Center Forums Provides ability to ask LexEVS questions and find answers https://cabig-kc.nci.nih.gov/Vocab/forums/ 15