Please use this identifier to cite or link to this item: http://hdl.handle.net/20.500.11889/4235
DC FieldValueLanguage
dc.contributor.authorCurcin, Vasa-
dc.contributor.authorMiles, Simon-
dc.contributor.authorDanger, Richard-
dc.contributor.authorChen, Yuhui-
dc.contributor.authorBache, Richard-
dc.contributor.authorTaweel, Adel-
dc.date.accessioned2017-02-13T13:38:10Z
dc.date.available2017-02-13T13:38:10Z
dc.date.issued2014-
dc.identifier.urihttp://hdl.handle.net/20.500.11889/4235-
dc.description.abstractThe provenance of a piece of data refers to knowledge about its origin, in terms of the entities and actors involved in its creation, e.g. data sources used, operations carried out on them, and users enacting those operations. Provenance is used to better understand the data and the context of its production, and to assess its reliability, by asserting whether correct procedures were followed. Providing evidence for validating research is of particular importance in the biomedical domain, where the strength of the results depends on the data sources and processes used. In recent times, previously manual processes have become fully or semi-automated, e.g. clinical trial recruitment, epidemiological studies, diagnosis making. The latter is typically achieved through interactions of heterogeneous software systems in multiple settings (hospitals, clinics, academic and industrial research organisations). Provenance traces of these software need to be integrated in a consistent and meaningful manner, but since these software systems rarely share a common platform, the provenance interoperability between them has to be achieved on the level of conceptual models. It is a non-trivial matter to determine where to start in making a biomedical software system provenance-aware. In this paper, we specify recommendations to developers on how to approach provenance modelling, capture, security, storage and querying, based on our experiences with two large-scale biomedical research projects: Translational Research and Patient Safety in Europe (TRANSFoRm) and Electronic Health Records for Clinical Research (EHR4CR). While illustrated with concrete issues encountered, the recommendations are of a sufficiently high level so as to be reusable across the biomedical domainen_US
dc.language.isoen_USen_US
dc.subjectMedical informaticsen_US
dc.subjectMedicine—Researchen_US
dc.subjectBiology - Researchen_US
dc.subjectMedical records—Data processingen_US
dc.subjectInformation technology - Managementen_US
dc.subjectVirtual storage (Computer science)en_US
dc.subjectInformation storage and retrieval systems - Medicineen_US
dc.titleImplementing interoperable provenance in biomedical researchen_US
dc.typeArticleen_US
newfileds.departmentEngineering and Technologyen_US
newfileds.item-access-typeopen_accessen_US
newfileds.thesis-prognoneen_US
newfileds.general-subjectnoneen_US
item.fulltextWith Fulltext-
item.grantfulltextopen-
item.languageiso639-1other-
Appears in Collections:Fulltext Publications
Files in This Item:
File Description SizeFormat
1-s2.0-S0167739X13002653-main.pdf1.53 MBAdobe PDFView/Open
Show simple item record

Page view(s)

134
Last Week
0
Last month
5
checked on Apr 14, 2024

Download(s)

90
checked on Apr 14, 2024

Google ScholarTM

Check


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.