Intelligent Ontology Alignment Tool for Complex Mismatches

Intelligent Ontology Alignment Tool for Complex Mismatches
Slide Note
Embed
Share

Dealing with ontology mismatches is crucial in aligning diverse healthcare entities and data sources. Learn about an intelligent ontology alignment tool presented at the ICCS/NTUA workshop in December 2014 in Berlin, focusing on managing conceptual, explication, and classification mismatches using mapping rules and ontology patterns. Explore functionalities, system architecture, and interaction components for effective ontology alignment in healthcare settings.

  • Ontology Alignment
  • Healthcare Entities
  • Data Sources
  • ICCS Workshop
  • Ontology Tools

Uploaded on Feb 16, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. An Intelligent Ontology Alignment Tool Dealing with Complicated Mismatches Efthymios Chondrogiannis ICCS / NTUA Greece Workshop 10, December 2014, Berlin

  2. Introduction Ontologies A specification of a conceptualization (Gruber, 1993) Design: Subjective Depends on the purpose they serve, the aspect(s) they cover Ontologies Mismatches Different Types: Conceptualization (e.g., scope, granularity, coverage) Explication (e.g., data structure, paradigm) Especially in the case of healthcare entities and their data sources: Different Classification Systems (e.g., vocabularies for laboratory examinations) Different Schemas (e.g., different parameters to represent hematological examination outcomes) Workshop 10, December 2014, Berlin 2

  3. Ontology-based DB Access SQL SPARQL SPARQL D2R Server Mediator XML/RDF XML/RDF Tuples User / System Query & Results Rewriting Query Translation HealthEntity EHR Schema Global EHR Ontology Local EHR Ontology EDOAL File D2RQ File Domain DB Syntactic Heterogeneity Structural & Semantic Heterogeneity Healthcare Entity Mapping Tool D2RQ Platform Workshop 10, December 2014, Berlin 3

  4. Mapping Rules & Ontology Patterns Mapping Rule Data Entities 1 and 2 Ontology Pattern Instances An existing element (e.g., an OWL class) An element with narrower meaning (e.g., a Property with Restricted Domain) A combinations of existing elements (e.g., union of OWL classes) Relation (e.g., Equivalent Terms) Data Transformation (if required) Direction (e.g., From Ontology 1 to Ontology 2) Mapping Rule Metadata Origin ( Manually / Automatically ) Confidence Value Comments Workshop 10, December 2014, Berlin 4

  5. Functionality provided by OAT Explore Ontological Elements Handle Candidate Mapping Rules LOAD LOAD ONTOLOGY A ONTOLOGY B Specify Mapping Rules missing Save/Export Mapping Rules Workshop 10, December 2014, Berlin 5

  6. System Architecture CLIENT SIDE SERVER SIDE Upload Ontologies Ontologies Handler Web Interface Requests Handler Get Available Terms Get Element Definition Get Suggestions Upload Mappings Mappings Handler Export Mappings Workshop 10, December 2014, Berlin 6

  7. Interaction among Components (1/2) Web Interface Requests Handler Ontologies Handler Mappings Handler Upload Ontology (File|URL) Store Onto File (File|URL) PROVIDE ONTOLOGY Store Read Imports ID & Imports Json Data Upload (List<URL,File|URL>) Store Onto File (File|URL) Store RESOLVE DEPENDENCIES Read Imports Json Data Get Elements (Onto, Type) OntoJson & Type get Elements Tree (ID, Type) Load Ontology (first time) Get Elements GET ONTOLOGICAL ELEMENTS Json Data Update Panel Workshop 10, December 2014, Berlin 7

  8. Interaction among Components (2/2) Web Interface Requests Handler Ontologies Handler Mappings Handler get Element Def (Onto, URI)get Element File (Onto, File) OntoJson & ElemURI GET ELEMENT DEFINITION UI Json Data Update Update Panel get Suggestions (Ontos,Maps)find Suggestions ( ) Ontos & Mappings GET SUGGESTIONS UI Json Data Update Update Panel EXPORT MAPPINGS Export (Ontos, Maps, Format) OntoJson & Mappings create Mappings File ( ) Workshop 10, December 2014, Berlin 8

  9. Interaction with the End Users (1/4) Examine Ontological Elements Quickly Define 1:1 Correspondences Workshop 10, December 2014, Berlin 9

  10. Interaction with the End Users (2/4) Handle Suggestions Accept / Reject Massively Accept / Reject based on the Confidence Value Reload or Export Suggestions Workshop 10, December 2014, Berlin 10

  11. Interaction with the End Users (3/4) Manually Specify Mapping Rules Ontology Pattern Instantiations Workshop 10, December 2014, Berlin 11

  12. Interaction with the End Users (4/4) Load Mapping Rules JSON Format Save/Export Mapping Rules JSON / XML (EDOAL) / HTML Workshop 10, December 2014, Berlin 12

  13. Live Demo Use the Ontologies Alignment Tool for specifying the mappings between: Global EHR Ontology Designed in close collaboration with clinical experts Healthcare Entity EHR Ontology Automatically generated based on DB schema Goal Precisely determine correspondence among them Intend to use mappings for SPARQL query rewriting Workshop 10, December 2014, Berlin 13

  14. Conclusion and Next Steps The Ontologies Alignment Tool covers all process driven requirements Weaknesses: Improve the quality of suggested mapping rules Visualization of suggestions and mapping rules Next Steps: Update Site Tool Architecture Source Code Update The Ontologies Alignment Tool Fix errors/weaknesses Workshop 10, December 2014, Berlin 14

  15. Thank you ! Questions ? Workshop 10, December 2014, Berlin 15

  16. Backup Slides Workshop 10, December 2014, Berlin 16

  17. Manually specifying a Mapping Rule Web Interface Requests Handler Ontologies Handler Mappings Handler Mapping Rules Repository and Panel Initialize / Update HANDLE MAPPING RULES Rules specified are stored on client side. Mapping Rule Change ... MANUALLY SPECIFYA MAPPING RULE Accept / Reject Tab 2 ... For manually specifying a mapping rule, none server side component is being used. Update Panel Json Mapping Rules Parameters MANUALLY SPECIFYA MAPPING RULE Tab 3 ... Ontology Pattern(s) Instantiation ( in the current version of OAT ) Json Workshop 10, December 2014, Berlin 17

  18. Example: Examination Outcome Workshop 10, December 2014, Berlin 18

Related


More Related Content