1 / 29

The Role of Architecture and Ontology for Interoperability

The Role of Architecture and Ontology for Interoperability. Bernd Blobel, Carolina Gonzalez, Frank Oemig, Diego M. Lopez, Pirkko Nykänen, Pekka Ruotsalainen. Observation. Data. Observation. Knowledge. Interpretation. Information. Diagnosis. Therapy. Action. Interoperability Levels.

oshiro
Download Presentation

The Role of Architecture and Ontology for Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Role of Architecture and Ontology for Interoperability Bernd Blobel, Carolina Gonzalez, Frank Oemig, Diego M. Lopez, Pirkko Nykänen, Pekka Ruotsalainen

  2. Observation Data Observation Knowledge Interpretation Information Diagnosis Therapy Action

  3. Interoperability Levels

  4. Pervasive Computing Location-independent service provision Telematics,, Telemedicine Autonomic Computing Self-organisation Health informationsystems Mobile Computing Accessability Tele-consultation Technical Paradigms for pHealth Ubiquitous Computing

  5. What would Gyro Gearloose like to do?

  6. Generic Component Model (GCM) Domain n Domain 2 Domain 1 Domain Perspective System Component Composition Business Concepts Relations Networks Aggregations (Basic Services / Functions) Details (Basic Concepts) System’s Archi- tectural Perspective Development Process Perspective System Domain System Viewpoint Enterprise View Information View Computational View Engineering View Technology View

  7. Generic Component Model (GCM) Domain n Domain 2 Domain 1 System Component Composition Business Concepts Relations Networks Aggregations (Basic Services / Functions) Details (Basic Concepts) … … … System Domain System Viewpoint Enterprise View Information View Computational View Engineering View Technology View

  8. Security Services Granularity Levels at GCM Domain n Domain 2 Domain 1 Domain Perspective System Component Composition Information security management, Business Concepts Relations Networks Aggregations (Basic Services / Functions) Details (Basic Concepts) System’s Archi- tectural Perspective directory services, ID management, certification management, naming services Development Process Perspective identification, authentication, integrity check, non-repudiation, security logging, digital signature System Domain enabling/disenabling access, delegation, encoding/decoding System Viewpoint Enterprise View Information View Computational View Engineering View Technology View

  9. Conceptual Model of Architectural Descriptionsafter IEEE 1471:2000

  10. Modeling Business Concepts after McDavid

  11. Ontology Hierarchy Using a computation-independent approach, the domain knowledge for performing a specific business has to be represented defining Business Domain, Business Process, Location, Business Organization, Event, and Business Motivation regarding meta-models, concepts and relationships.

  12. Ontology Hierarchy general ontologies upper level ontologies domain ontologies application ontologies ICT ontology

  13. BFO:entity continuant independent continuant object object boundary object aggregate fiat object part site dependent continuant generically dependent continuant specifically dependent continuant quality realizable entity Function artifactual function biological function role disposition spatial region zero-dimensional region one-dimensional region two-dimensional region three-dimensional region The Continuant Categories of BFO after Arp and Smith

  14. BFO:entity occurrent processual entity process process boundary process aggregate fiat process part processual context spatiotemporal region scattered spatiotemporal region connected spatiotemporal region spatiotemporal instant spatiotemporal interval temporal region scattered temporal region connected temporal region temporal instant temporal interval The Occurrent Categories of BFO after Arp and Smith

  15. Foundational relations is_a part_of Spatial relations (connecting one entity to another in terms of relations between the spatial regions they occupy) located_in contained_in adjacent_to Temporal relations (connecting entities existing at different times) transformation_of derives_from preceded_by Participation relations (connecting processes to their bearers) has_participant has_agent First Version of the OBO Relation Ontology after Arp and Smith

  16. V3 + GCM after Oemig (Enterprise View) (Information View) Pat. Admin. Business Concepts Application Roles Inter-actions Reference Information Model CMETs Relations Network Domain Models Vocab. Binding Vocab. Binding R-MIM RIM Classes Data Types Vocabulary (Domains) Aggre-gations RIM Attributes Data Types Elements Value Set Value Set Value Set Details ADT Lab, Rad, Pharm., .. als verschiedene Subdomänen

  17. V2.x + GCM after Oemig (Enterprise View) (Information View) Pat. Admin. Business Concepts Application Roles Inter-actions Relations Network Msg Struct Events Aggregations (Basic Services/ Functions) Segments Tables (Domains) Data Types Data Elements Table Values Data Types Elements Details (Basic Concepts)

  18. Designing Ontology Systems with the GCM System Component Composition General Ontology Business Concepts Relations Networks Aggregations (Basic Services / Functions) Details (Basic Concepts) System’s Archi- tectural Perspective Top-Level Ontology Development Process Perspective ICT Ontology Domain Ontology System Domain Application Ontology System Viewpoint Enterprise View Information View Computational View Engineering View Technology View

  19. Policy-Driven, Role-Based Access Control

  20. Privilege Assignments canActivate(cli , Clinician(org, area)) ra.is-certified-NHS-clinician-cert(cli , org, area, start , end), is-registration-authority(ra, org), no-main-role-active(cli), Current-time() 2 [start , end] u:user, rij:roles, ij urolememberships(ri)  urolememberships(rj) rjmutuallyexclusiveauthorisation (rj)

  21. Types of ontologies

  22. After Kamareddine et al.

  23. Conclusions • Interoperability is not first a matter of the ICT domain, but a user domains‘ one. • Interoperability is a challenge to meeting business objectives. It requires sharing of knowledge, which should be built on a hierarchical system of ontologies. • Multi-disciplinary interoperability solutions require a system-theoretical, architecture-centric approach, enabling the formalization of systems representation including ontology mapping.

  24. Thank you very much for your attention! Takk fyrir aheyrnina! Bernd Blobel, PhD, Associate Professor eHealth Competence Center University of Regensburg Medical Center Franz-Josef-Strauss-Allee 11 D-93042 Regensburg, Germany Email: bernd.blobel@klinik.uni-regensburg.de Phone: +49-941-944 6769 Fax: +49-941-944 6766 http://www.ehealth-cc.de

More Related