110 likes | 281 Views
. 2. Problem Domain. In distributed medical applications the following information is split into different administration domains (islands of information)The medical data (HC history of patients) The workflows (of the corresponding processes carried out to patients)The logs (recording meaningful
E N D
1. EU PROVENANCE project: an open provenance architecture for distributed applications Javier Vázquez-Salceda
4th Workshop on Agents Applied in Health Care
August 28, 2006
2. 2 Problem Domain In distributed medical applications the following information is split into different administration domains (islands of information)
The medical data (HC history of patients)
The workflows (of the corresponding processes carried out to patients)
The logs (recording meaningful events)
An integrated view, not only for data but also for workflows and logs is needed
To have an integrated view of a patient’s treatment across all institutions
To analyse the performance of distributed HC services to detect problems to solve
To carry out audits of the system, if requested by medical or legal authorities.
3. 3 Problem Domain Need: to trace back
The origins of (medical) decisions and processes
The (medical) information available a each step
The origins of such information
Idea: make the distributed medical system provenance_aware
Our def: “Provenance of a piece of data is the process that lead to the data”
Re-convert standard logs into provenance-based logging services capable to record information about the workflow execution and the data, and their provenance.
Adapt the medical systems to provide provenance information.
Have tools to properly reconstruct the full provenance of data
4. 4 Aims of EU PROVENANCE project Define core concepts pertaining to provenance
Specify functionality required to become “provenance-aware”
Define open data models and protocols that allow distributed systems to inter-operate
Standardise data models and protocols
Provide a reference implementation
Provide reasoning capabilities over provenance data (higher-level queries)
5. 5 Target: Service Oriented Architectures Covering not only Multiagent Systems but other SOA’s (Webservices, GRID)
Service Oriented Architectures approach
Broad definition of service as component that takes some inputs and produces some outputs.
Services are brought together to solve a given problem typically via a workflow definition that specifies their composition.
Every application is made up of actors
Every change that happens is an action by an actor
Actors communicate by sending messages
Every action is triggered by a message
The outputs of (messages sent by) an actor are caused by the inputs to (messages received by) the actor
6. 6 Use cases Aerospace engineering: maintain a historical record of design processes, up to 99 years.
7. 7
8. 8 An Example If actors are black boxes, these assertions are not very useful because
we do not know dependencies between messages
If actors are black boxes, these assertions are not very useful because
we do not know dependencies between messages
9. 9
10. 10 Conclusions Provenance may increase the quality of Agent-mediated Health Care services:
trace back the origin of (medical) decisions and actions
provide an integrated view of a patient’s treatment
Issues
Connect an electronic computational process with real world
Connect past electronic computational processes
Currently building a full demonstrator for the Catalan OTA as a use case for EU PROVENANCE
Evaluation is planned with some hospital and transplant coordinators in the Barcelona area.
11. 11