Self Sovereign Identity for Patient Controlled Health Records

39 concepts21 papers1 proposal

Traditional Electronic Health Record (EHR) systems treat medical data as institutional property. When you visit a clinic, your data is recorded inside that specific institution's database silo. Even within modern federated health networks, retrieving and sharing your own medical history remains convoluted and fragmented (John Robert Bautista et al., MediLinker: a blockchain-based decentralized health information management platform for patient-centric healthcare).

This centralization creates a fundamental imbalance of agency. Centralized identity providers possess excessive control over user data, making it difficult for patients to manage granular consent or prevent the oversharing of sensitive information (Mohammed Amine Bouras et al., Distributed Ledger Technology for eHealth Identity Privacy: State of The Art and Future Perspective). When patients lack direct control over their records, data continuity breaks down across different clinical settings, increasing the risk of medical errors (Sajid Hussain et al., Pervasive Health Care Services and Technologies).

To resolve these issues, a growing body of research proposes inverting the root of trust using Self-Sovereign Identity (SSI) and decentralized ledgers. This paradigm shifts data ownership from institutional databases directly to the individual patient.


Inverting the Root of Trust

In a traditional system, an institution acts as the identity provider. It authenticates who you are and decides who can view your records. SSI flips this architecture by making the individual the absolute root of their digital identity.

Traditional Model:
[Institution] ──> Authenticates Patient ──> Controls Access to [Database Silo]

Self-Sovereign Identity Model:
[Patient Wallet] ──> Holds Cryptographic Keys ──> Grants Access via [Decentralized Ledger]

Instead of storing raw, sensitive medical records directly on a public blockchain—which would violate privacy laws and fail to scale—the decentralized ledger is used to manage Decentralized Identifiers (DIDs) and cryptographic schemas (John Robert Bautista et al.). The blockchain serves as an immutable, shared registry of trust.

By using this decentralized ledger, fragmented medical records from disparate clinics can be aggregated into a single, unified, longitudinal history controlled by the individual (Wubing Chen et al., A Survey of Blockchain Applications in Different Domains). This client-centric design eliminates administrative barriers and preserves privacy across healthcare touchpoints, which is particularly vital for highly stigmatized care continuums (Daniel Toshio Harrell et al., Designing a blockchain technology platform for enhancing the pre-exposure prophylaxis care continuum). For vulnerable populations who lack stable physical documentation, a blockchain-based transaction identity provides a secure, immutable way to verify and manage essential health records independently (Ashish Gadnis, Using Blockchain to Create Transaction Identity for Persons Experiencing Homelessness in America: Policy Proposal).


The Cryptographic Handshake

How does a patient actually grant or revoke access to a medical provider without a central server enforcing the rules? The mechanism relies on user-controlled encryption keys and cryptographic handshakes.

Asymmetric Encryption Handshakes

Patrick Li et al. (DMMS: A Decentralized Blockchain Ledger for the Management of Medication Histories) design a framework where medical records are secured using asymmetric cryptography.

  1. Encryption: When a medical event occurs, the data is encrypted using the patient's public key.
  2. Storage: The encrypted payload is stored securely (e.g., in a decentralized cloud or distributed database).
  3. Authorization: To allow a third-party practitioner to view historical records, the patient executes an asymmetric encryption handshake, providing a temporary authorization key.

Because patients hold the master keys to their own data, they can independently grant or revoke permissions at will (Danan Thilakanathan et al., Facilitating Secure Sharing of Personal Health Data in the Cloud; Rongrong Zhu et al., Investigation of personal data protection mechanism based on blockchain technology).

Patient Tokenization via NFTs

To link disparate health records across multiple institutions without a centralized master patient index, researchers have turned to tokenization. Yan Zhuang et al. (Self-sovereign identity empowered non-fungible patient tokenization for health information exchange using blockchain technology) demonstrate how Non-Fungible Tokens (NFTs) can be repurposed as unique, patient-controlled identifiers.

Instead of representing digital art, the NFT acts as a secure pointer to a patient's distributed medical records. Using a mobile device, the patient authenticates via SSI principles and manages granular access permissions directly to their health NFT. This allows data from smart wearables, biosensors, and clinical examinations to continuously stream into a unified, encrypted database that securely follows the user across different medical service providers (the authors of Development of a personal health management system integrating digital twin technology and smart wearables in China).


Shifting Agency: Verification and Auditing

True data sovereignty means patients are active participants in data verification, rather than passive subjects of data collection.


Open Challenges

While decentralized architectures offer robust, privacy-preserving alternatives that can withstand institutional trust crises (N. Deepa et al., A survey on blockchain for big data: Approaches, opportunities, and future directions; Anjum Khurshid, Applying Blockchain Technology to Address the Crisis of Trust During the COVID-19 Pandemic), they introduce unique engineering and philosophical challenges.

  1. Emergency Access and Guardianship: Standard SSI models assume a fully conscious, capable user holding their own cryptographic keys. Imrana Abdullahi Yari (Security Engineering of Patient-Centered Health Care Information Systems in Peer-to-Peer Environments: Systematic Review) highlights that standard decentralized identity models do not adequately handle emergency access or guardianship for incapacitated users. Specialized authentication schemes are required to balance patient autonomy with delegated access during acute medical crises.
  2. Access Control vs. Content Control: A critical boundary exists between managing access and managing content. As Yan Zhuang et al. point out, while patients can control who views their records, they do not have direct control over modifying the clinical content once it has been generated and signed by a professional. This boundary ensures that the objective medical history remains accurate and tamper-resistant, even while the patient retains absolute sovereignty over who gets to see it.

Key Foundational Work

Pervasive Health Care Services and Technologies (2008) — contributed 2 concept elements to this direction.
Requirements and Design for an Extensible Toolkit for Analyzing EMR Audit Logs (2013) — contributed 1 concept elements to this direction.
History & citationVersion 1 · 2026-10-04

Current · Permanent link

View frozen version 1

Cite this direction

Latest version (a living page):

@misc{lacuna_patient_controlled_data_access_406b0cfc,
  title = {patient-controlled data access},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/patient-controlled-data-access/rdr_406b0cfc365b42a4bb1a154d6c68f3b8},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-19},
}

This exact version (version 1, frozen text):

@misc{lacuna_patient_controlled_data_access_406b0cfc_v1,
  title = {patient-controlled data access},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/patient-controlled-data-access/rdr_406b0cfc365b42a4bb1a154d6c68f3b8/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-19},
}
About

These directions overlap with this one through shared papers.

See something wrong? Report a mistake