Transcript Title

SIXTH FRAMEWORK
PROGRAMME
PRIORITY 2.3.1.11
e-Health
COCOON (FP6 507126)
Building knowledge driven & dynamically adaptive
networked communities
within European healthcare systems
Advanced Interoperability:
COCOON glue
Authors: E. Della Valle, D. Cerizza and S. Ceri
emails: {dellavalle},{cerizza}@cefriel.it and [email protected]
1st COCOON review – March 8th-9th , 2005
1
Advanced Interoperability: COCOON glue
the integration problem in COCOON?
End-users
• a seamless integration of many
complex technologies is needed
in COCOON
eHR
Mobile Portal
Knowledge Management Platform
Web-based Collaboration
EHR interface
tools
DSS
• all the interfaces must be exposed
as Web Services
Web Portal
Diagnosis DS
GP profiling
Glue
SIR
Semantic
Search
Conceptual
indexing
Treatment DS
patient-records
S-Navigation
K-cache
Regional services
content sources
• Moreover COCOON will only add a
new set of eHealth services to a
regional environment already
populated by thousand of
heterogeneous services (e.g.
SISS in Lombardy)
1st COCOON review – March 8th-9th , 2005
2
Advanced Interoperability: COCOON glue
a need for cataloguing and discovering services
If you have few services and you
want to support one simple
implementation strategy
Few services
B8
Lot of complex Services
A1
A1
A1 B3
A1
A1
A1
A1
A1 A4
A2
A1 A4
A2
A2
A1 A2A4 A1
A1 A2
B3
A1
B3
A1
B3 A1 A1
A1 A1
A4A1
A1
A1 A4 A1
A1
A1 A2
A4 A1 B3
A1
B3
A4 A1
A1 A1 A4 A1 A2
A1
A2
A1
A4 B3 A4
A1
A4 A1 A2
B3
A2
A1 A1
A1
A1
A1
A1A1
A4 A1
A1
A2
A2
A1
A1
B3
A4 A1 A2
A1
A1
A1 A2A2
A4 A1B3A2 A1 A1A2 A4A4
A2
A2
A4
A1
A1
A2 A4
A4
A4
A2 A1 A1
A4 A1 A1
A1
A1A1
A4
B3
A2
A1
B3
A4
A2
B3
A1
A2
B3 A4 A1
A1
A1
A4A4 A1A2 A4 A1
B3 B3A1
A1A1A1
A4 A2
A1 A1
A1A1
A1
A2
A2
A4
A4 A1 A1 A4
A1
A1 A1
A4A1
A4
A1
A1A1A2
A1
B3 A1A1 B3 B3 A1
A1
A4
B3
A1
B3
But, if you have lot of services and
you want to support multiple
complex implementation strategies
A4
A5A1 A2
A1
A4 A6
A2
Simple workflow
?
A
E
N1
C
N2
F
D
1st COCOON review – March 8th-9th , 2005
Complex Business Process
Inspired by: J. Cardoso, C. Bussler, A. Sheth1, D. Fensel, Semantic Web Services and Processes, October 2002
3
Advanced Interoperability: COCOON glue
Web Service Discovery
• Discovery service is an essential component in the abstract
idea of Service Oriented Architecture
Discovery
Agencies
Service
Descriptio
n
Discover
Service
requester
Publish
Interact
Service
provider
Service
Descriptio
n
source: http://www.w3.org/TR/2002/WD-ws-arch-20021114/
1st COCOON review – March 8th-9th , 2005
4
Advanced Interoperability: COCOON glue
Human processable semantics and discovery
• In concrete situation a strong agreement on semantics is
needed
Discover
Discovery
Agencies WSD
Provider Entity
Requester Entity
?
AGREE
Sem
Requester
Human
+
Service
requester
Publish
Sem
Provider
Human
WSD
Interact
1st COCOON review – March 8th-9th , 2005
+ Sem
Service
provider
5
Advance Interoperability: COCOON Glue
Machine processable semantics and discovery
• Machine processable semantics is needed for automating
discovery.
• Ontologies (
) are the enabling technology because they
interweave human understanding of symbols with their machine
processability
Discovery
Agencies
Discover
Ontology
Requester Entity
?
WSD
+ Sem
Publish
Provider Entity
Sem
Sem
Requester
Human
WSD
+ Sem
Service
requester
AGREE
Interact
1st COCOON review – March 8th-9th , 2005
Provider
Human
WSD
+ Sem
Service
provider
6
Advanced Interoperability: COCOON glue
Which approach to Semantic Web Services?
• In addition to a language for ontologies, semantic
interoperability requires a conceptual model and
formalization for services.
• OWL-S and WSMO are the two major initiatives that aim at
facilitating the automation of Web service tasks,
– OWL-S is an upper service ontology expressed in OWL.
• It supplies Web service providers with a core set of markup constructs
for describing the properties and capabilities of their Web services in
computer-interpretable form.
• OWL-S has been submitted to W3C in November 2004.
– WSMO, the Web Service Modeling Ontology,
• describes four different main elements: ontologies that provide the
terminology used by other elements, goals that describe aspects related
to user desires with respect to the requested functionality, Services
descriptions that define various aspects of a Web service, and mediators
which bypass interpretability problems.
• Preperations for the submission to the W3C are currently ongoing and
expected to be finished in March 2005.
1st COCOON review – March 8th-9th , 2005
7
Advanced Interoperability: COCOON glue
Which approach to Semantic Web Services?
Wide
Deployed
Technologies
COCOON aims at being a Wide
Deployed application
GAP
Most Recent SWS
developments
Standard
Industrial
Research
OWL-S
Academic
Research
IRS-III
WSMO
IRS-II
DAML-S
WSMF
Available Standard Technologies
(XML, SOAP, WSDL, UDDI, …)
• We choose WSMO because
– It is a strong conceptual model based on a sound separation between ontologies,
goals, web services and mediators
– It is founded on two clear principles of strong decoupling and strong mediation
1st COCOON review – March 8th-9th , 2005
8
Advanced Interoperability: COCOON glue
WSMO model
Source: WSMO D2v1.0.
• WSMO consists of four different main elements for describing semantic
web services:
–
–
–
–
ontologies (
) that provide the terminology used by other elements
goals ( G ) that define the problems that should be solved by web services
web services (
) descriptions that define various aspects of a web service
mediators (
) which bypass interpretability problems.
G
1st COCOON review – March 8th-9th , 2005
9
Advanced Interoperability: COCOON glue
WSMO at work: publishing time
Provider
entity
Requester
entity
WSD
Provider
entity
WSD
WS
WS
Execution Enviroment
Ontologies
1.
WS
Provider
entity
WSD
Mediators Web Services
2.
3.
WSD
+ WSD
+ WSD
+WSD
+
1. provider and requester entities
agree on the ontologies to use
2. If they cannot reach an agreement
on the terms to use (e.g. SNOMED,
IDC) mediators are required
3. Each provider entity formally
describe its services using the
agreed ontologies and (if
necessary) mediator
1st COCOON review – March 8th-9th , 2005
WS
Provider
entity
WSD
10
Advanced Interoperability: COCOON glue
WSMO at work: discovery time
Provider
entity
4.
WSD
Requester
entity
Invoke
Provider
entity
G
WS
3.
WSD
WS
1.
Execution Enviroment
{ ● ● } Discovery engine
Ontologies
2.
Mediators Web Services
WSD
+ WSD
+ WSD
+WSD
+
WS
Provider
entity
WSD
1. Requester entity formally describes its goal
using the agreed ontologies and (if necessary)
mediator
2. The discovery engine uses the specified
ontologies and mediators to match the goal
against the web service descriptions
3. The execution environment returns a list of
Web Services
COCOON reviewselects
– March 8 -9the
, 2005
4. The 1requester
most appropriate
Web Services and invokes it
st
th
th
WS
Provider
entity
WSD
11
Advanced Interoperability: COCOON glue
COCOON Ontology
Part of internal F-Logic syntax
…
disease[ affects=>>{bodyPart} ].
cancer::disease.
breastCancer::cancer[ affects=>>{breast} ].
hypertension::disease[ affects=>>{artery, heart} ].
…
medication[ controlsDiseases*=>>{disease} ].
hormonalTherapy::medication[ controlsDiseases*=>>{breastCancer} ].
blockers::medication.
alphaBlockers::blockers[ controlsDiseases*=>>{hypertension} ].
betaBlockers::blockers[ controlsDiseases*=>>{hypertension} ].
doxazosin::alphaBlockers.
atenolol::betaBlockers.
tenormine::atenolol.
metoprolol::betaBlockers.
Medications
lopressor::metoprolol.
seloken::metoprolol.
…
Hormonal
Blockers
Therapy
Alpha Blockers
Beta Blockers
Atenolol
Disease
Tenormine
Cancer
Breast Cancer
…
Hypertension
Metoprolol
Lopressor
Seloken
Skin Cancer
1st COCOON review – March 8th-9th , 2005
12
Advanced Interoperability: COCOON glue
WSMO at work: example of mediator
• Providers and requester entities
representation of date-time.
• For example:
may
disagree
on
the
– A provider entity may prefer to express service availability using a
Week-based calendar terminology (
)
• E.g. the service is available on Monday and Thursday morning and
Friday evening
– A requester entity may prefer to express user preferences using a
Gregorian-based calendar terminology (
)
• E.g. is the service available on March, 8th from 10 to 12
• An agreement is not necessary, a mediator can be used to
bypass the heterogeneity problem
March, 8th from 11 to 14
Thursday morning
1st COCOON review – March 8th-9th , 2005
13