Provenance in Distr Organ Transplant Management EU PROVENANCE

Provenance in Distr. Organ Transplant Management EU PROVENANCE project: an open provenance architecture for distributed applications Javier Vázquez-Salceda 4 th Workshop on Agents Applied in Health Care August 28, 2006 http: //www. lsi. upc. es/~webia/KEMLG EU PROVENANCE project

Problem Domain l In distributed medical applications the following information is split into different administration domains (islands of information) n n n EU PROVENANCE l 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 n n n 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. 2

Problem Domain l Need: to trace back n n n l Idea: make the distributed medical system provenance_aware n EU PROVENANCE The origins of (medical) decisions and processes The (medical) information available a each step The origins of such information n 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 3

EU PROVENANCE Aims of EU PROVENANCE project l Define core concepts pertaining to provenance l Specify functionality required to become “provenanceaware” l Define open data models and protocols that allow distributed systems to inter-operate l Standardise data models and protocols l Provide a reference implementation l Provide reasoning capabilities over provenance data (higher-level queries) 4

Target: Service Oriented Architectures l Covering not only Multiagent Systems but other SOA’s (Webservices, GRID) l Service Oriented Architectures approach n EU PROVENANCE n 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. l Every application is made up of actors l Every change that happens is an action by an actor l Actors communicate by sending messages l Every action is triggered by a message l The outputs of (messages sent by) an actor are caused by the inputs to (messages received by) the actor Direct application to multiagent systems 5

Use cases EU PROVENANCE Aerospace engineering: maintain a historical record of design processes, up to 99 years. Organ transplant management: tracking of previous decisions, crucial to maximise the efficiency in matching and recovery rate of patients 6

OTA General Practice Center Hospital C WL Transplant Unit EHCR WL Hospital A (donor side) Hospital B (recipient side) Transplant Unit WL EU PROVENANCE WL Lab_A EHCR Lab_B General Practice Center Hospital D Lab_1 Lab_2 Lab_3 EHCR 7

An Example 1. Agent messages are recorded as interactions, either by the agents or by the agent platform PROVENANCE Store 2. Agents record the internal relationships between inputs and outputs, plus extra meaningful information. TU. 1 Data Collection request OTM. 1 Donor Data request HC. 1 Patient Data request TU. 2 Serology Test request OTM. 2 Donor Data EHCR HC. 2 Patient Hospital A Hospital B Data Transplant TU. 3 Brain Death Notification Interface + report EU PROVENANCE Unit Agent OTM Donor Data Collector TU. 4 Decision request TU. 5 Decision + report Agent OTM. 3 Serology test request OTM. 4 Serology test result + report Test Lab. Interface Agent 8

Patient response Which is the basis for Data to Request Hospital B donation decision D? HC. 2 contains caused by HC. 1 parts of Data Donor response caused Donor Collection Data to by Data Request based is logged in OTM. 2 OTM. 1 TU. 1 on User Z User X is logged in Brain based Decision response Donation Death justified Death on by to Request Decision report Notification TU. 5 TU. 4 TU. 3 User Y caused Author B justified by is logged in authored by by based Decision on report Serology caused response Test by to Result Request TU. 5 justified by OTM. 4 TU. 2 OTM. 3 Author A User X authored by caused User W is logged in is logged by Serology in report EU PROVENANCE • OTM. 4 Author C authored by 9

Conclusions l Provenance may increase the quality of Agent-mediated Health Care services: n n l Issues n n EU PROVENANCE trace back the origin of (medical) decisions and actions provide an integrated view of a patient’s treatment Connect an electronic computational process with real world Connect past electronic computational processes l Currently building a full demonstrator for the Catalan OTA as a use case for EU PROVENANCE l Evaluation is planned with some hospital and transplant coordinators in the Barcelona area. 10

EU PROVENANCE project IBM United Kingdom Limited EU PROVENANCE University of Southampton University of Wales, Cardiff Deutsches Zentrum fur Luft- und Raumfahrt s. V Universitat Politècnica de Catalunya MTA SZTAKI 11