1. SALUS Semantic Middleware SALUS Advisory Board Meeting - January 17, 2013

2. Semantic Interoperability  Formalization of more then ‘just’ terminology, but also the relations between concepts and the context  Constraining the semantics = limiting possible interpretations  People can interpret according to the context, computers don’t  This summer I travelled to Java  This software module is written in Java  My preferred brand of coffee is Java

3. Introduction The Semantic Interoperability Platform (SIP)  A simple thing (?)  Put a semantic layer on top if any resource  Define a common ontology (or a system to mediate between ontologies)  Query data as if everything behaves as one virtual system Information source Information source Information source Information source Information source Semantic layer Semantic Interoperability Platform Virtual and consolidated information source

4. Semantic Interoperability and Service Platform CD A Arch … …

5. central Integrating the different approaches X (HL7) X (HL7) Y (CEN) Y (CEN) Z Z Warehouse Semantic Mediator Sem. Resour ces Repositories detectionreportingSem. services… monitoringreportingportal local Formalize ASAP

7. From data to formal resources CIS: Clinical Information System CTMS: Clinical Trial Management System DDO: Data Definition Ontology DO: Domain Ontology DSQ: Domain SPARQL Query DSSQ: Data Set SPARQL Query GUI: Graphical User Interface SQL: Structured Query Language At development (deployment) time: creating "formal library" At any time: formalizing upfront (triple cache) At runtime: formalizing (via querying) and deducing (via reasoning with rules) Using formalisms declared in ontologies Fixed query link Formal world Operational world Step 1 Step 2 Local Operational world GUI Query SQL DO Analysis 3 1-1 mapping Portal Result 1-1 mapping Result in DO form 2 5 DSSQ 4 DDO Result in DDO form 3 Analysis result Global Analysis rules DSQ 7 8 Conversion rules 6 CIS* 1 CDA 2 1 1 1 3 2 4 5 6 7 8 9 1 2 3

8. 8 X X Y Y Z Z SALUS CBA … … …