Value Domain and Pick List Support in LexEVS 5.1 Sridhar Dwarkanath Mayo Clinic CaBIG Architecture/VCD Joint Workspace F2F.

Slides:



Advertisements
Similar presentations
Overview of LexEVS 5.0 LexEVS Architecture November, 2009.
Advertisements

LexEVS 5.0 Value Domain and Pick List November, 2009.
Chapter 10: Designing Databases
CACORE TOOLS FEATURES. caCORE SDK Features caCORE Workbench Plugin EA/ArgoUML Plug-in development Integrated support of semantic integration in the plugin.
CVRG Presenter Disclosure Information Tahsin Kurc, PhD Center for Comprehensive Informatics Emory University CardioVascular Research Grid Core Infrastructure.
Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.
Common Terminology Services 2 (CTS2)
LexBIG/EVS API Overview NCBO Seminar Series October 2008.
Netscape Application Server Application Server for Business-Critical Applications Presented By : Khalid Ahmed DS Fall 98.
LexGrid for cBIO Division of Biomedical Informatics Mayo Clinic Rochester, MN.
© Copyright 2008, Mayo Clinic College of Medicine Mayo Clinic Open Health Tools Application for Membership OHT Board Meeting, Birmingham, UK July 1, 2008.
CaBIG™ Terminology Services Path to Grid Enablement Thomas Johnson 1, Scott Bauer 1, Kevin Peterson 1, Christopher Chute 1, Johnita Beasley 2, Frank Hartel.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
CS CS 5150 Software Engineering Lecture 13 System Architecture and Design 1.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide
OpenMDR: Generating Semantically Annotated Grid Services Rakesh Dhaval Shannon Hastings.
OpenMDR: Alternative Methods for Generating Semantically Annotated Grid Services Rakesh Dhaval Shannon Hastings.
LexEVS 6.0 Overview Scott Bauer Mayo Clinic Rochester, Minnesota February 2011.
LexEVS 101 Craig Stancl Rick Kiefer February, 2010.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
1 LexEVS 5.0 Advanced Topics Configuration Options LexEVS Boot Camp November, 2009.
Deliverable Readiness Review LexEVS 5.1 December 17, 2009.
Data File Access API : Under the Hood Simon Horwith CTO Etrilogy Ltd.
CaBIG Semantic Infrastructure 2.0: Supporting TBPT Needs Dave Hau, M.D., M.S. Acting Director, Semantic Infrastructure NCI Center for Biomedical Informatics.
J2EE Structure & Definitions Catie Welsh CSE 432
LexEVS Overview Mayo Clinic Rochester, Minnesota June 2009.
Using the Open Metadata Registry (openMDR) to create Data Sharing Interfaces October 14 th, 2010 David Ervin & Rakesh Dhaval, Center for IT Innovations.
January 19, 2011 Sherri de Coronado, Semantic Services Center for Bioinformatics and Information Technology.
LexEVS in a caGrid Environment Interacting with LexEVS 5.0 November 2009.
XML Registries Source: Java TM API for XML Registries Specification.
H Using the Open Metadata Registry (OpenMDR) to generate semantically annotated grid services Rakesh Dhaval, MS, Calixto Melean,
LexBIG Release Overview Aug 21, LexBIG Context Project Goals for Sept –Incremental point release of LexBIG infrastructure to support EVS activities.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
NERC DataGrid NERC DataGrid Vocabulary Server Use Cases Vocabulary Workshop, RAL, February 25, 2009.
Value Set Resolution: Build generalizable data normalization pipeline using LexEVS infrastructure resources Explore UIMA framework for implementing semantic.
Open Terminology Portal (TOP) Frank Hartel, Ph.D. Associate Director, Enterprise Vocabulary Services National Cancer Institute, Center for Biomedical Informatics.
LexBIG/LexGrid Services for LexBIG 2.3 Model and API for the Grid.
Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
LexEVS Semantic Tooling Advancements Kevin Peterson Mayo Clinic Mayo 2009.
1/22/08 RTR Project Presentation to TPTF RTR Project Michael Daskalantonakis & Brian Cook.
LexGrid Philosophy, Model and Interfaces Harold R Solbrig Division of Biomedical Statistics and Informatics Mayo Clinic.
PHS / Department of General Practice Royal College of Surgeons in Ireland Coláiste Ríoga na Máinleá in Éirinn Knowledge representation in TRANSFoRm AMIA.
Overview of LexEVS 5.0 LexGrid 2009 Model November, 2009.
LexEVS Value Domains. LexGrid Definitions Value Domain Definition – the description of the contents Value Domain Resolution – the actual contents –The.
Scalable Hybrid Keyword Search on Distributed Database Jungkee Kim Florida State University Community Grids Laboratory, Indiana University Workshop on.
1 Service Creation, Advertisement and Discovery Including caCORE SDK and ISO21090 William Stephens Operations Manager caGrid Knowledge Center February.
1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL 17 December 2015.
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 JSP Application Models.
EVS 4.0 Feature Overview EVS API and User Interface pBIO Meeting March 20, 2007 Frank Hartel Gilberto Fragoso
1 Ontolog OOR-BioPortal Comparative Analysis Todd Schneider 15 October 2009.
Handling Semantic Data for Software Projects Data Management CSE G674 – SW Engineering Project.
Session 1 Module 1: Introduction to Data Integrity
Patterns in caBIG Baris E. Suzek 12/21/2009. What is a Pattern? Design pattern “A general reusable solution to a commonly occurring problem in software.
LexEVS 5.0 EVS to LexEVS: A Migration Guide November, 2009.
Design for a High Performance, Configurable caGrid Data Services Platform Peter Hussey LabKey Software, Inc, Seattle, WA USA Contact:
Steven Perry Dave Vieglais. W a s a b i Web Applications for the Semantic Architecture of Biodiversity Informatics Overview WASABI is a framework for.
CaBIG™ Terminology Services Path to Grid Enablement Thomas Johnson 1, Scott Bauer 1, Kevin Peterson 1, Christopher Chute 1, Johnita Beasley 2, Frank Hartel.
Java Programming: Advanced Topics 1 Building Web Applications Chapter 13.
WonderWeb. Ontology Infrastructure for the Semantic Web. IST Project Review Meeting, 11 th March, WP2: Tools Raphael Volz Universität.
National Cancer Institute 1 1 LexBIG integration caCORE Software User Meeting Aug 7, 2006.
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.
XML and Distributed Applications By Quddus Chong Presentation for CS551 – Fall 2001.
Extended Metadata Registries and Semantics (Part 2: Implementation) Karlo Berket Ecoterm IV Environmental Terminology Workshop April 18, 2007 Diplomatic.
Netscape Application Server
The Re3gistry software and the INSPIRE Registry
Lecture 1: Multi-tier Architecture Overview
ARCH-1: Application Architecture made Simple
AMGA Web Interface Vincenzo Milazzo
NIEM Tool Strategy Next Steps for Movement
Presentation transcript:

Value Domain and Pick List Support in LexEVS 5.1 Sridhar Dwarkanath Mayo Clinic CaBIG Architecture/VCD Joint Workspace F2F Atlanta, GA USA October 2009

Session Goal Familiarize with Value Domain Definition and Pick List Definition part of LexGrid model and Their functions supported in LexEVS 5.1 release.

LexEVS – Lexical Enterprise Vocabulary Services LexEVS Developed to allow federated, open source system for delivering vocabulary content. Strategic EVS interface, replacing the legacy EVS API and the EVS 3.2 model. Key infrastructure tool for caBIG ®. Available through caCORE distribution. Represents the next generation of NCI Enterprise Vocabulary Services.

LexEVS – Lexical Enterprise Vocabulary Services LexEVS combines LexGrid and LexEVS Java API LexGrid : A standard model of controlled vocabularies and ontologies. Defines how vocabularies should be formatted and represented programmatically. Rich enough to represent vocabularies provided in numerous source formats including: Open Biomedical Ontologies (OBO) Web Ontology Language (OWL), e.g., NCI Thesaurus Unified Medical Language System (UMLS) Rich Release Format (RRF), e.g., NCI MetaThesaurus LexEVS Java API : Applies LexGrid vision and technologies to requirements of the caBIG® community. Provide a flexible implementation for vocabulary storage and persistence. Provide standard tooling for load and distribution of vocabulary content.

LexEVS – Lexical Enterprise Vocabulary Services LexEVS includes the following components: Java API - A Java interface based on the LexGrid Object Model Distributed LexBIG (DLB) API - A Java interface based on the LexGrid data model and relies on a LexEVS Proxy and Distributed LexEVS Adapter to provide remote clients access to the native LexEVS API REST/HTTP Interface - Offers an HTTP based query mechanism. Results are returned in either XML or HTML formats SOAP/Web Services Interface - Provides a programming language neutral Service- Oriented Architecture (SOA) LexEVS 5.0 Grid Service - An interface which uses the caGRID infrastructure to provide access to the native LexEVS API via the caGRID Services

LexEVS – Lexical Enterprise Vocabulary Services LexEVS Environment Architecture Diagram showing architecture of LexEVS. At the bottom, as Data Source, we have lexGrid MySQL database. Core API layer on top of data source layer contains LexGrid Model Objects, Java APU and the Lucene Index Files. Application Service layer on top of Core API, contain Distributed Java API and LexEVS CaGrid API. And at the top, we have Client layer, with Client Application which could include Java QBE (Query By Example), Web/Grid Service (Soap/HTTP/Rest) and Java RMI. Model Objects LexEVS caCORE SDK APIs Java API LexGrid MySQL DB Lucene Index Files Distributed Java LexEVS caGrid API Java (QBE) Application Service Client Web/Grid Service (Soap/HTTP/Rest) Java (RMI) ( Distributed) Client Application Core API Data Source RMI

LexGrid Model : Value Domain Definition Diagram containing Value Domain part of LexGrid Logical Model. Value Domain Definition : URI should be unique Versionable DefinitionEntry 0 or more definitionEntry Each definitionEntry can reference either code system or value domain or can contain entityReference Multiple definitionEntries can be combined using local operators ‘OR’, ‘SUBTRACT’ or ‘AND’ entityReference entityCode is the start concept and a required field. Other fields are for rules. URI should be unique Versionable 0 or more definitionEntry Each definitionEntry can reference either code system or value domain or can contain entityReference entityCode is start concept referenceAssociation Applicable rules : leafOnly targetToSource transitiveClosure DefinitionEntries can be combined using logical operators ‘OR’, ‘SUBTRACT’, or ‘AND’

Value Domain Definitions Possible Forms Code system/concept code + relationship + additional rules (leaf only, immediate children,...) Code system – all concept codes in the code system Other Value Domain – all resolved concept codes returned by referencing Value Domain Code system/concept code – individual code Combination of any of the above with or/and/difference operators

Value Domain Definition Resolution A value domain definition has to be made against a specific version of a code system. But it doesn’t have to be resolved against the same version. Even a simple list (a, b, c, d) needs to be resolved as, at some future date, “c” might be retired. Resolution does not create static artifact.

LexGrid Model : Pick List Definition Diagram showing Pick List part of LexGrid Logical Model. PickListId unique Value Domain URI required completeDomain – True/False True – Dynamic, ignores pickListEntryNode False – Static, default 0 or More pickListEntryNode Each pickListEntryNode can contain either have pickListEntry or pickListEntryExclusion PickListEntry : pickText and entityCode are required fields. PickListId unique Value domain URI required completeDomain – True/False True – Dynamic, ignores pickListEntryNode. False – Static, default versionable 0 or more pickListEntryNode Each pickListEntryNode can contain either pickListEntry or pickListEntryExclustion versionable pickText and entityCode are required fields.

Pick List Definitions Possible Forms Value Domain Definition – all concept codes in the value domain completeDomain = true Dynamic form Code system/concept code – individual code (inclusion and exclusion) completeDomain = false Subset of Value Domain Static form

Pick List Resolution A Pick List definition has to be made against a specific value domain. Even a simple list (a, b, c, d) needs to be resolved as, at some future date, “c” might be retired. Resolution does not create static artifact.

LexEVS Value Domain Services Admin Services loadValueDomain(InputStream, boolean) - Loads value domain using inputStream. loadValueDomain(String, boolean) - Loads value domain by reading XML file. loadValueDomain(ValueDomainDefinition, String) - Loads supplied valueDomainDefinition object. removeAllValueDomains() - Removes all value domain definitions from the system. removeValueDomain(URI) - Removes supplied value domain definition from the system. validate(URI, int) - Perform validation of the value domain definition without loading data. dropValueDomainTables() - Drops value domain tables only if there are no value domain and pick list entries.

LexEVS Value Domain Services Query Services getCodingSchemesInValueDomain(URI) - Returns list of coding scheme summary that is referenced by the supplied value domain. getValueDomainDefinition(URI) - Returns value domain definition for supplied value domain URI. getValueDomainEntitiesForTerm(String, URI, String) - Resolves the value domain supplied and restricts to the term and matchAlgorith supplied. listValueDomains(String) - Return the URI's for the value domain definition(s) for the supplied domain name. If the name is null, returns everything. If the name is not null, returns the value domain(s) that have the assigned name. resolveValueDomain(URI, AbsoluteCodingSchemeVersionReferenceList) - Resolve a value domain using the supplied set of coding scheme versions.

LexEVS Value Domain Services Query Services (Cont…) isConceptInDomain(String, URI) - Determine if the supplied entity code is a valid result for the supplied value domain and, if it is, return the particular codingSchemeVersion that was used. isConceptInDomain(String, URI, CodingSchemeVersionOrTag, URI) - Determine if the supplied entity code is a valid result for the supplied domain. isDomain(String, String, CodingSchemeVersionOrTag) - Determine if the supplied entity code is of type valueDomain in supplied coding scheme and, if it is, return the true, otherwise return false. isSubDomain(URI, URI) - Check whether childValueDomainURI is a child of parentValueDomainURI.

LexEVS Pick List Services Admin Services loadPickList(InputStream, boolean) - Loads pick list using inputStream. loadPickList(PickListDefinition, URI) - Loads supplied PickListDefinition object. loadPickList(String, boolean) - Loads pick list by reading XML file location supplied. removePickList(String) - Removes pick list definition from the system that matches supplied pickListId. validate(URI, int) - Perform validation of the picklist definition without loading data.

LexEVS Pick List Services Query Services getPickListDefinitionById(String) - Returns pickList definition for supplied pickListId getPickListDefinitionsForDomain(URI) - Returns all the pickList definitions that represents supplied valueDomain URI. getPickListValueDomain(String) - Returns an URI of the represented valueDomain of the pickList. listPickListIds() - Returns list of pickListIds that are available in the system. resolvePickList(String, boolean) - Resolves pickList definition for supplied pickListId. resolvePickListForTerm(String, String, String, String, String[], boolean) - Resolves pickList definition for supplied arguments - Term to restrict, match algorithm to use, language to restrict, list of context to restrict, sort flag (If True, will be sorted by text in ascending order.)

LexEVS 5.0 vs LexEVS 5.1 LexEVS 5.0 Release Current Release Value Domain and Pick List services available as an extension LexEVS 5.1 Release November 2009 Integrated within LexEVS API

Value Domain and Pick List Services in LexEVS Both Value Domain and Pick List Services will be available in following components of LexEVS 5.1 : Java API - A Java interface based on the LexGrid 5.0 Object Model Distributed LexBIG (DLB) API - A Java interface based on the LexGrid 2009/01 data model and relies on a LexEVS Proxy and Distributed LexEVS Adapter to provide remote clients access to the native LexEVS API

Value Domain and Pick List Services in LexEVS Value Domain and Pick List Services available in LexEVS Environment Diagram showing architecture of LexEVS. At the bottom, as Data Source, we have lexGrid MySQL database. Core API layer on top of data source layer contains LexGrid Model Objects, Java APU and the Lucene Index Files. Application Service layer on top of Core API, contain Distributed Java API and LexEVS CaGrid API. And at the top, we have Client layer, with Client Application which could include Java QBE (Query By Example), Web/Grid Service (Soap/HTTP/Rest) and Java RMI. Model Objects LexEVS caCORE SDK APIs Java API LexGrid MySQL DB Lucene Index Files Distributed Java LexEVS caGrid API Java (QBE) Application Service Client Web/Grid Service (Soap/HTTP/Rest) Java (RMI) ( Distributed) Client Application Core API Data Source RMI

Future Plans Future plans for Value Domain and Pick List in LexEVS Persist resolved data. Include Value Domain and Pick List as part of following LexEVS components : REST/HTTP Interface - Offers an HTTP based query mechanism. Results are returned in either XML or HTML formats SOAP/Web Services Interface - Provides a programming language neutral Service- Oriented Architecture (SOA) LexEVS Grid Service - An interface which uses the caGRID infrastructure to provide access to the native LexEVS API via the caGRID Services

More Information caBIG® Vocabulary Knowledge Center : Download Software Documentation and Training Presentations and Demos LexGrid and LexBIG UML Diagram LexGrid and LexBIG XML Schema Sample Database caBIG LexEVS Developer Boot Camp : November 17 th, 18 th, and 19 th, 2009

Questions ?