Design Requirement
The solution must have the flexibility to comply with the variable body of federal and state regulatory rules governing patient consent for PHI sharing, since healthcare providers must comply with these regulations for the patient data they manage.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/consent-self-management-hie-dr4design-knowledge/consent-self-management-hie-dr4.mdThe solution must have the flexibility to comply with the variable body of federal and state regulatory rules governing patient consent for PHI sharing, since healthcare providers must comply with these regulations for the patient data they manage.
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
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
Derived heading context: Design knowledge
Derived heading context: Addresses
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
3 of 3 concepts · 5 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "DR4 - Compliance",
"description": "The solution must have the flexibility to comply with the variable body of federal and state regulatory rules governing patient consent for PHI sharing, since healthcare providers must comply with these regulations for the patient data they manage.",
"resource": "https://doi.org/10.1016/j.dss.2023.114021",
"source_paper": "Blockchain innovation for consent self-management in health information exchanges",
"label": "DR4",
"tags": [
"consent-self-management-hie",
"design-requirement",
"healthcare",
"consent-management",
"privacy",
"interoperability"
]
}