The Role of Architecture and Ontology for Interoperability EFMI Special Topic Conference 2010 June 2-4. 2010 Reykjavik, Iceland Bernd Blobel eHealth Competence

The Role of Architecture and Ontology for Interoperability

EFMI Special Topic Conference 2010June 2-4. 2010

Reykjavik, Iceland

Bernd BlobeleHealth Competence CenterUniversity Hospital RegensburgeHCC


Bernd Blobel, Carolina Gonzalez, Frank Oemig, Diego M. Lopez, Pirkko Nykänen, Pekka Ruotsalainen



Reykjavik, Iceland


Observation

Interpretation Action

Data

Information

Observation

Diagnosis Therapy

Knowledge

Consent

HP or HCE Action Patient



Reykjavik, Iceland


Interoperability Level Instances

Technical interoperabilityTechnical plug&play, signal- & protocol compatibility

Structural interoperability Simple EDI, envelopes

Syntactic interoperabilityMessages, clinical documents, agreed vocabulary

Semantic interoperabilityAdvanced messaging, common information models and terminology

Organizations/Service interoperability

Common business process

Interoperability Levels



Reykjavik, Iceland


PervasiveComputing

Location-independentservice provision

Telematics,, Telemedicine

MobileComputingAccessabilityTele-consultation

AutonomicComputing

Self-organisationHealth information

systems

UbiquitousComputing

Technical Paradigms for pHealth



Reykjavik, Iceland


What would Gyro Gearloose like to do?



Reykjavik, Iceland




Reykjavik, Iceland




Reykjavik, Iceland




Reykjavik, Iceland


Domain n

Domain 2Domain 1

Ent

erpr

ise

Vie

w

Info

rmat

ion

Vie

w

Com

puta

tiona

l

Vie

w

Eng

inee

ring

Vie

w

Tec

hnol

ogy

Vie

w

Sys

tem

Com

pone

nt

Com

posi

tion

Syste

m D

omai

n

System Viewpoint

Sys

tem

’s A

rch

i-te

ctu

ral

Per

spec

tive

Development ProcessPerspective

Domain Perspective

Business Concepts

Relations Networks

Aggregations(Basic Services / Functions)

Details (Basic Concepts)

Generic Component Model (GCM)



Reykjavik, Iceland


Domain n

Domain 2Domain 1

Ent

erpr

ise

Vie

w

Info

rmat

ion

Vie

w

Com

puta

tiona

l

Vie

w

Eng

inee

ring

Vie

w

Tec

hnol

ogy

Vie

w

Sys

tem

Com

pone

nt

Com

posi

tion

Syste

m D

omai

n

System Viewpoint

Business Concepts

Relations Networks



Generic Component Model (GCM)

…

…

…



Reykjavik, Iceland


Domain n

Domain 2Domain 1

Ent

erpr

ise

Vie

w

Info

rmat

ion

Vie

w

Com

puta

tiona

l

Vie

w

Eng

inee

ring

Vie

w

Tec

hnol

ogy

Vie

w

Sys

tem

Com

pone

nt

Com

posi

tion

Syste

m D

omai

n

System Viewpoint

Sys

tem

’s A

rch

i-te

ctu

ral

Per

spec

tive


Domain Perspective

Business Concepts

Relations Networks



Security Services Granularity Levels at GCM

enabling/disenabling access, delegation, encoding/decoding

identification, authentication, integrity check, non-repudiation, security logging, digital signature

directory services, ID management, certification management, naming services

Information security management,



Reykjavik, Iceland


Conceptual Model of Architectural Descriptions after IEEE 1471:2000

Advanced EHR Architectures

Bernd BlobeleHealth Competence CenterUniversity of Regensburg Medical Center

eHCC

EHR Committee of HL7 Colombia2 J uly 2009



Reykjavik, Iceland




Reykjavik, Iceland


Modeling Business Concepts after McDavid

Advanced EHR Architectures

Bernd BlobeleHealth Competence CenterUniversity of Regensburg Medical Center

eHCC

EHR Committee of HL7 Colombia2 J uly 2009



Reykjavik, Iceland


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.



Reykjavik, Iceland


Ontology Hierarchy

• general ontologies

• upper level ontologies

• domain ontologies

• application ontologies

• ICT ontology



Reykjavik, Iceland


The Continuant Categories of BFO after Arp

and Smith

BFO:entitycontinuant• 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



Reykjavik, Iceland


The Occurrent Categories of BFO after Arp

and Smith

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



Reykjavik, Iceland


First Version of the OBO Relation Ontology after Arp and Smith

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



Reykjavik, Iceland


V3 + GCM after Oemig

Application Roles

Pat. Admin.

Inter-action

sReference Information Model

Data Types

Vocabulary

(Domains)

Value Set

CMETs

Business Concepts

Relations Network

Aggre-gations

Details

RIM Classes

RIM Attribute

s

Data Types

Elements

als verschiedene Subdomänen

(Enterprise View)

Domain Models

R-MIMVocab. Binding

Vocab. Binding

Value SetValue Set

ADT Lab, Rad,

Pharm., ..

(Information View)



Reykjavik, Iceland


V2.x + GCM after Oemig

Application Roles

Pat. Admin.

Inter-action

s

Data Types

Tables (Domains

)

Table Values

Msg Struct

Business Concepts

Relations Network

Aggregations (Basic Services/ Functions)


Data Types

Elements

(Enterprise View)

Events

Segments

(Information View)

Data Elements



Reykjavik, Iceland


Ent

erpr

ise

Vie

w

Info

rmat

ion

Vie

w

Com

puta

tiona

l

Vie

w

Eng

inee

ring

Vie

w

Tec

hnol

ogy

Vie

w

Sys

tem

Com

pone

nt

Com

posi

tion

Syste

m D

omai

n

System Viewpoint

Sys

tem

’s A

rch

i-te

ctu

ral

Per

spec

tive


Business Concepts

Relations Networks



Designing Ontology Systems with the GCM

ApplicationOntology

DomainOntology

Top-LevelOntology

GeneralOntology

ICT O

ntolo

gy



Reykjavik, Iceland


Policypolicy_identifier : IIpolicy_name : CSpolicy_authority_ID : OIDpolicy_authority_name : STpolicy_domain_identifier : OIDpolicy_domain_name : ENpolicy_target_list : LIST <INT>

AuthorisationPolicy

Obligation Policyevent : CVexception : Exception

RefrainPolicyaction : CE

Delegation Policygrantee : OIDaccessRights : CE

Auth+action : CE

Auth-action : CE

Deleg+ Deleg-

MetaPolicymeta_expressionraised_action : CE

BasicPolicypolicy_subject_ID : OIDpolicy_subject_name : STtarget_identifier : IItarget_name : ENtarget_object : IIoperation_code : CEpermission_policy : CDconstraint : OCL

CompositePolicyevent : CVpolicy : CDmpolicy : CDpolicy_group : IIconstraint : OCL

Groupgroup_identifier : IIgroup_name : CSgroup_description : CD

ManagementStructureroles : Rolerels : Relmstructs : Mstruct

Relationshiproles : Role

RolesubjectDomain : OIDrole_identifier : IIrole_name : CSrole_description : CD



Reykjavik, Iceland


Policy-Driven, Role-Based Access Control

Principal

SR_Policy

Structural_Role

Role_Hierarchy

1..*

1

FR_Policy

Functional_Role0..*0..* 0..*0..*

User_Assignment1..*1

Process_PolicySession

1..*

0..*

1..*

0..*

User_Session

1

1..*

1

1..*

Session_Role

1..* 1

Target_Policy

Target_Component0..*0..* 0..*0..*

Permission_Assignment1..*

1

1..*

1

1 1..*

1..* 1

1

1..*



Reykjavik, Iceland


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, ijurolememberships(ri) urolememberships(rj) rjmutuallyexclusiveauthorisation (rj)



Reykjavik, Iceland


Types of ontologies



Reykjavik, Iceland


After Kamareddine et al.



Reykjavik, Iceland


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.



Reykjavik, Iceland


Thank you very much for your

attention!

Bernd Blobel, PhD, Associate ProfessoreHealth Competence CenterUniversity of Regensburg Medical CenterFranz-Josef-Strauss-Allee 11D-93042 Regensburg, GermanyEmail: [email protected]: +49-941-944 6769Fax: +49-941-944 6766http://www.ehealth-cc.de

Takk fyrir aheyrnina!

Documents

The Role of Architecture and Ontology for Interoperability EFMI Special Topic Conference 2010 June 2-4. 2010 Reykjavik, Iceland Bernd Blobel eHealth Competence