DSR Knowledge LibraryReusable design knowledge and grounded research support
HomeLibraryChatGive feedback ↗

DSR Knowledge Library

Research prototype · Native Open Knowledge Format

LibraryChatImprintPrivacyEvaluation survey ↗
Library/DR3 - Trust

Design Requirement

DR3 - Trust

The solution must build and maintain patient trust in health information exchange by giving patients control over and visibility into their consent relationships, since patient trust is critical to the rights patients have to control the sharing of their protected health information.

OverviewLinked conceptsRelationshipsGraphRaw metadata

01

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/consent-self-management-hie-dr3
Open concept record
Producer label
DR3
Source paper
Blockchain innovation for consent self-management in health information exchanges
Timestamp
2026-08-05T00:00:00+00:00
Bundle path
design-knowledge/consent-self-management-hie-dr3.md
consent-managementconsent-self-management-hiedesign-requirementhealthcareinteroperabilityprivacy

Design requirement DR3: Trust

The solution must build and maintain patient trust in health information exchange by giving patients control over and visibility into their consent relationships, since patient trust is critical to the rights patients have to control the sharing of their protected health information.

Source paper

This design requirement is proposed by Blockchain innovation for consent self-management in health information exchanges (Chad Anderson, Arthur Carvalho, Mala Kaul, Jeffrey W. Merhout, 2023).

02

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

2 Design Principles

design-knowledge/consent-self-management-hie-dp2

DP2 - Patient-only consent changes

Only the patient can change their consent status, supporting self-management and engendering patient trust.

consent-managementconsent-self-management-hiedesign-principlehealthcare+2
design-knowledge/consent-self-management-hie-dp3

DP3 - Auditable consent history

The history of consent transactions between patients and the HIE must be auditable so that compliance with consent laws can be verified for all transactions.

consent-managementconsent-self-management-hiedesign-principlehealthcare+2

1 Paper

papers/consent-self-management-hie

Blockchain innovation for consent self-management in health information exchanges

Having established patients' desire to self-manage consent, the paper proposes a permissioned-blockchain solution enabling seamless sharing of patient consent across providers and HIEs, formalized through five design requirements, five design principles and five design features, and evaluated with a prototype.

blockchainconsent-managementconsent-self-management-hiedesign-science-research+3

03

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

1
  • →

    Blockchain innovation for consent self-management in health information exchanges

    Paper
    Source
    DR3 - Trust
    Target
    Blockchain innovation for consent self-management in health information exchanges
    Link label
    Blockchain innovation for consent self-management in health information exchanges
    Status
    Resolved

    Derived heading context: Source paper

Incoming backlinks

3
  • ←

    Blockchain innovation for consent self-management in health information exchanges

    Paper
    Source
    Blockchain innovation for consent self-management in health information exchanges
    Target
    DR3 - Trust
    Link label
    Design requirement DR3: Trust
    Status
    Resolved

    Derived heading context: Design knowledge

  • ←

    DP2 - Patient-only consent changes

    Design Principle
    Source
    DP2 - Patient-only consent changes
    Target
    DR3 - Trust
    Link label
    Design requirement DR3: Trust
    Status
    Resolved

    Derived heading context: Addresses

  • ←

    DP3 - Auditable consent history

    Design Principle
    Source
    DP3 - Auditable consent history
    Target
    DR3 - Trust
    Link label
    Design requirement DR3: Trust
    Status
    Resolved

    Derived heading context: Addresses

04

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

4 of 4 concepts · 8 directed relationships

Concept types
Press enter or space to select a node.You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Design RequirementSeed

Trust

Concept identity

Concept ID
design-knowledge/consent-self-management-hie-dr3
Producer label
DR3
Native type
design-requirement

Description

The solution must build and maintain patient trust in health information exchange by giving patients control over and visibility into their consent relationships, since patient trust is critical to the rights patients have to control the sharing of their protected health information.

DOI

https://doi.org/10.1016/j.dss.2023.114021

Tags

  • consent-management
  • consent-self-management-hie
  • design-requirement
  • healthcare
  • interoperability
  • privacy
Description and publication link from the library record.

05

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter+
{
  "type": "design-requirement",
  "title": "DR3 - Trust",
  "description": "The solution must build and maintain patient trust in health information exchange by giving patients control over and visibility into their consent relationships, since patient trust is critical to the rights patients have to control the sharing of their protected health information.",
  "resource": "https://doi.org/10.1016/j.dss.2023.114021",
  "source_paper": "Blockchain innovation for consent self-management in health information exchanges",
  "label": "DR3",
  "tags": [
    "consent-self-management-hie",
    "design-requirement",
    "healthcare",
    "consent-management",
    "privacy",
    "interoperability"
  ]
}