| Literature DB >> 34813494 |
Kerstin Gierend1, Frank Krüger2, Dagmar Waltemath3, Maximilian Fünfgeld1, Thomas Ganslandt1, Atinkut Alamirrew Zeleke3.
Abstract
BACKGROUND: Provenance supports the understanding of data genesis, and it is a key factor to ensure the trustworthiness of digital objects containing (sensitive) scientific data. Provenance information contributes to a better understanding of scientific results and fosters collaboration on existing data as well as data sharing. This encompasses defining comprehensive concepts and standards for transparency and traceability, reproducibility, validity, and quality assurance during clinical and scientific data workflows and research.Entities:
Keywords: biomedical; data genesis; data sharing; digital objects; healthcare data; lineage; provenance; scientific data; scoping review; workflow
Year: 2021 PMID: 34813494 PMCID: PMC8663663 DOI: 10.2196/31750
Source DB: PubMed Journal: JMIR Res Protoc ISSN: 1929-0748
Concepts and matching keywords (eligibility criteria).
| Concepts | Matching keywords (inclusion criteria) |
| Target domain | biomed*a, EHR, electronic health record, healthcare, clinical, scientificb |
| Provenance | provenance, prov, lineage |
| Provenance properties | interop*, (data NEAR/2 [flow, quality, transformation]), metadata, workflow, semantic, framework, annotat*, ontolog*, management, document*, (model NEAR/2 provenance) |
| Objective | audit*, decision support, ETL, Extract-Transform-Load, FHIR, record linking, machine learning, reproducib*, transparen*, track*, implement* |
aThe * symbol (wildcard character) replaces or represents one or more characters.
bWill be used in a domain-independent context only.
Data charting template for key information from eligible papers.
| Metadata publication | Characteristic extraction and specification |
| Titlea | Title |
| Citation detailsa | Author (1st), journal, DOI |
| Year of publicationa | For example, YYYY |
| Publication typea | Journal or website or conference, etc |
| Study typea | Use case or development or evaluation |
| Continent of study | For example, Australia |
| Institutea | Contributing institute (corresponding author or—if not provided—1st author) |
| Corresponding author’s discipline | For example, data architect |
| Funding source | Public or industry or none or missing |
| Objectivea | Aim of the publication |
| Methods | Strategies, processes, or techniques utilized in the collection or analyzing of data, how is the validity of the study judged |
| Summary resultsa | Short description of results |
| Conclusion | Short description of conclusion |
| Target domaina | Name specific domain or domain independent |
| Keywords | List keywords from abstract |
| Metadata to key findings related to research questions | Characteristic extraction and specification |
| Research question 1: Approaches for classification and tracking of provenance criteria and methods in biomedical or domain-independent context | Provide description in the domain for data suitability or data availability and other requirements or factors on data or systems regarding the trace of the data history (eg, role of provenance in terms of domain standards, ie, interoperability standards, FAIR [findable-accessible-interoperable-reusable] data, relation to metadata and model use, representation formalisms, etc), check definition of provenance |
| Research question 2: Potential value of provenance information | Provide possible use case description and types of data sources included, usability including effect on target domain and by whom it can be used and who will be the stakeholders; |
| Research question 3: Potential problems or bottlenecks for the accomplishment of provenance | Describe any challenges (eg, legal, organizational, or technical conditions) or problems that occurred during implementation phase of provenance |
| Research question 4: Guidelines or demands for the consideration of provenance to be adhered to | Describe any valid domain standard requirement, for example, legal, guidelines, rules |
| Research question 5: Completeness of provenance information during data management process or data life cycle | Describe any measurement or outcome available for completeness of provenance information |
aObligatory input.