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

DSR Knowledge Library

Research prototype · Native Open Knowledge Format

LibraryChatImprintPrivacyEvaluation survey ↗
Library/DR1 - Privacy

Design Requirement

DR1 - Privacy

Patient consent self-management must support patients' privacy preferences, since the exposure of protected health information to unauthorized entities can be detrimental to patients and healthcare organizations are federally mandated to secure PHI privacy under HIPAA.

OverviewLinked conceptsRelationshipsGraphRaw metadata

01

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/consent-self-management-hie-dr1
Open concept record
Producer label
DR1
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-dr1.md
consent-managementconsent-self-management-hiedesign-requirementhealthcareinteroperabilityprivacy

Design requirement DR1: Privacy

Patient consent self-management must support patients' privacy preferences, since the exposure of protected health information to unauthorized entities can be detrimental to patients and healthcare organizations are federally mandated to secure PHI privacy under HIPAA.

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.

1 Design Principle

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

DP1 - Authorization-restricted consent visibility

Only HIEs and providers with authorization can view a patient's consent status, maintaining confidentiality.

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
    DR1 - Privacy
    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

2
  • ←

    Blockchain innovation for consent self-management in health information exchanges

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

    Derived heading context: Design knowledge

  • ←

    DP1 - Authorization-restricted consent visibility

    Design Principle
    Source
    DP1 - Authorization-restricted consent visibility
    Target
    DR1 - Privacy
    Link label
    Design requirement DR1: Privacy
    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

3 of 3 concepts · 5 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

Privacy

Concept identity

Concept ID
design-knowledge/consent-self-management-hie-dr1
Producer label
DR1
Native type
design-requirement

Description

Patient consent self-management must support patients' privacy preferences, since the exposure of protected health information to unauthorized entities can be detrimental to patients and healthcare organizations are federally mandated to secure PHI privacy under HIPAA.

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": "DR1 - Privacy",
  "description": "Patient consent self-management must support patients' privacy preferences, since the exposure of protected health information to unauthorized entities can be detrimental to patients and healthcare organizations are federally mandated to secure PHI privacy under HIPAA.",
  "resource": "https://doi.org/10.1016/j.dss.2023.114021",
  "source_paper": "Blockchain innovation for consent self-management in health information exchanges",
  "label": "DR1",
  "tags": [
    "consent-self-management-hie",
    "design-requirement",
    "healthcare",
    "consent-management",
    "privacy",
    "interoperability"
  ]
}