Applying Provenance in Distributed Organ Transplant Management

Álvarez, Sergio; Vázquez-Salceda, Javier; Kifor, Tamás; Varga, László Zsolt; Willmott, Steven

doi:10.1007/11890850_4

Cited by 26 publications

(12 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, the provenance of a hospital patient, the process which led to that patient being in a particular state [1], would be different for the patient up to an operation starting and up to the operation finishing, because after the latter event the provenance includes data about the operation. An event that an assertion provides documentation about need not be instantaneous, but entities documented in the assertion must not change over the course of the event (else the provenance would be ambiguous).…”

Section: Assertions and Temporalitymentioning

confidence: 99%

Electronically Querying for the Provenance of Entities

Miles

2006

Provenance and Annotation of Data

View full text Add to dashboard Cite

Abstract. The provenance of entities, whether electronic data or physical artefacts, is crucial information in practically all domains, including science, business and art. The increased use of software in automating activities provides the opportunity to add greatly to the amount we can know about an entity's history and the process by which it came to be as it is. However, it also presents difficulties: querying for the provenance of an entity could potentially return detailed information stretching back to the beginning of time, and most of it irrelevant to the querier. In this paper, we define the concept of provenance query and describe techniques that allow us to perform scoped provenance queries.

show abstract

Section: Assertions and Temporalitymentioning

confidence: 99%

Electronically Querying for the Provenance of Entities

Miles

2006

Provenance and Annotation of Data

View full text Add to dashboard Cite

show abstract

“…Today, human activity is becoming increasingly automated with the aid of computational systems, which perform part or, in some cases, all of processes previously undertaken solely by humans. Interestingly, this means that activities in scientific [2], governmental [4] and commercial [12] settings are increasingly represented in computational systems, which presents an opportunity: it becomes possible to capture what happens in these settings both accurately and comprehensively.…”

Section: Motivationmentioning

confidence: 99%

Principles of High Quality Documentation for Provenance: A Philosophical Discussion

Groth

Miles

Munroe

2006

Provenance and Annotation of Data

View full text Add to dashboard Cite

Abstract.Computer technology enables the creation of detailed documentation about the processes that create or affect entities (data, objects, etc.). Such documentation of the past can be used to answer various kinds of questions regarding the processes that led to the creation or modification of a particular entity. The answer to such questions are known as an entity's provenance. In this paper, we derive a number of principles for documenting the past, grounded in work from philosophy and history, which allow for provenance questions to be answered within a computational context. These principles lead us to argue that an interaction-based model is particularly suited for representing high quality documentation of the past.History is important: in order to make progress in the future, it is important to learn the lessons of the past. History, therefore, becomes a vital resource for progressive societies. History is based on evidence or documentation of events that occurred in the past. Computer technology enables documentation to be produced that is more accurate and comprehensive than previously possible. Given the quantity of documentation that can be generated by computer systems (for example those running e-Science applications), what kind of documentation should be created that enables historians and users to most effectively answer questions they have about the past. To answer these questions, we argue for two principles for the creation of, what we term, high quality documentation of the past. One principle guarantees that users of documentation of the past have a precise semantics for it. The other principle guarantees that there exists a link between documentation and its creators. Together these principles are the first contribution of this paper.A question that is often posed by historians and users regards the provenance of an entity (object, data item, etc..): what was the process that led to the entity in question? To enable the answering of provenance questions in a manner that conforms with the aforementioned principles, we introduce a model of documentation based on the exchange of messages between actors. The justification of this model is the second contribution of this paper.The rest of this paper is organised as follows. We begin with a more detailed motivation of our work. After which, three assumptions about the world are

show abstract

“…It records the processes that produce the data and relationship between the processes. A simple example of the provenance is the documentation about how to produce a patient record in a hospital [2,6,12,13]. The patient record contains the data about the medical treatment or medical test of the patient which is produced by the physicians and laboratory staffs in the hospital.…”

Section: Introductionmentioning

confidence: 99%

Supporting Secure Provenance Update by Keeping “Provenance” of the Provenance

Syalim

Nishide

Sakurai

2013

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Provenance of data is a documentation of the origin and processes that produce the data. Many researchers argue that the provenance should be immutable: once a provenance is submitted, it should not be changed or updated. A main reason is that the provenance represents the history of data, and the history should not be altered or changed because it represents the fact in the past. Provenance can be represented by a graph, where each node represents the process executed by a party and an edge represents the relationship between two nodes (i.e. a child node uses the outputs of the parent nodes). A method to ensure that the provenance has not been updated is by using signature chain, where the signatures of the parent nodes are recorded in the children nodes so that any changes to the parent nodes will raise inconsistencies between the parent and the children. However, sticking to the requirement that the provenance should be immutable requires unlimited data storage and also we have problems whenever we need to update the provenance for an accidental error. In this paper, we propose a method that allows updates in the signature chain-based secure provenance, while keeping the signature consistent. The main idea is by keeping the "provenance" of the provenance itself, that is the history of update of the provenance, in the form of the signatures of the previous versions of the nodes. We implement the idea by keeping the signatures of the previous version in a signature tree similar to the Merkle-tree, where the a parent node in tree is the aggregate signature of the children. Using this method, the storage requirement to store signatures is always smaller than the number of updates.

show abstract

Applying Provenance in Distributed Organ Transplant Management

Cited by 26 publications

References 8 publications

Electronically Querying for the Provenance of Entities

Electronically Querying for the Provenance of Entities

Principles of High Quality Documentation for Provenance: A Philosophical Discussion

Supporting Secure Provenance Update by Keeping “Provenance” of the Provenance

Contact Info

Product

Resources

About