Skip to content

docs: add healthcare and mental wellness security considerations #1490

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add healthcare and mental wellness security considerations #1490

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions docs/regulated-domains/healthcare-security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Healthcare and Mental Wellness Security Considerations

## Context
Cloud-native and blockchain-based systems are increasingly used in healthcare and mental wellness. These systems must follow strict privacy and security practices due to the sensitivity of personal health information (PHI/PII).

## Principles
- **Data minimization:** Never place PHI/PII directly on public chains or in unencrypted logs.
- **Consent workflows:** Use Verifiable Credentials (VCs) and Decentralized Identifiers (DIDs) to manage patient consent off-chain, verifying proofs without exposing raw attributes.
- **Privacy-preserving analytics:** Apply commitments, zero-knowledge proofs, and aggregation to measure outcomes without leaking individual records.
- **Incident readiness:** Define break-glass procedures, rotation plans, and clear audit trails.
- **Mental wellness risk:** Misuse or leakage of mental health data has higher ethical stakes; systems must exceed baseline privacy standards.

## Checklist
- [ ] No PHI/PII in logs, storage, or transactions.
- [ ] Consent captured via VCs/DIDs with expiration + nonce.
- [ ] Cloud-native deployments include encryption at rest and in transit.
- [ ] Break-glass access is gated and logged.
- [ ] Testing covers reentrancy, replay, and denial-of-service threats in consent flows.

## References
- CNCF TAG-Security docs
- NIST Privacy Framework
- HIPAA Security Rule
- HL7 FHIR Security and SMART on FHIR
- W3C VC and DID Core
Loading