Blockchain in E-Health: trust and data architecture

Blockchain in E-Health Infrastructure: A Trust Architecture for Medical Data

Blockchain addresses a fundamental healthcare challenge: lack of trust in data. Medical records are stored in isolated systems, changes go untracked, and patients lose control over access. The cost of data breaches in the industry reaches $10.93 million per incident—double that of the financial sector. FHIR standards enable format exchange but do not guarantee immutability or access control. Blockchain introduces a cryptographic ledger of hashes and metadata, where verification occurs without a central authority.

Technical Foundations of Blockchain in E-Health

Medical data is not stored directly on the blockchain due to volume and regulations like GDPR/HIPAA. A hybrid model is used: off-chain storage for encrypted documents, on-chain for hashes, timestamps, and access events.

Verification process:

• The patient controls access to the off-chain storage (IPFS or a secure database).
• The blockchain records the SHA-256 hash of the document.
• During verification: compute the file's hash and compare it with the on-chain record. A mismatch indicates alteration.

Smart contracts automate processes: verifying an insurance event triggers a payout without intermediaries. SSI (Self-Sovereign Identity) gives patients keys for selective data disclosure.

Types of blockchains for E-Health:

• Public (Ethereum): Transparency for certificates, low throughput.
• Permissioned (Hyperledger Fabric, Quorum): Verified nodes, confidentiality, high performance.
• Specialized (KSI Guardtime): Merkle hash trees without keys for long-term verification.

This architecture turns blockchain into a trust ledger, not a storage solution.

Development Timeline: From Concept to Standard

Development began in 2008 with the Bitcoin whitepaper, which introduced the idea of a distributed ledger. In 2012, Estonia implemented KSI to protect data for 1.3 million citizens. Ethereum (2015) added smart contracts, and MIT introduced MedRec. By 2017–2018, pharmaceutical logistics (MediLedger) and Hyperledger became standards. The pandemic accelerated adoption: Singapore and the WHO standardized certificates. By 2024, MediLedger covers 95% of prescription drugs in the U.S., and EHDS regulates the EU.

Implementation Clusters: Real-World Cases

Implementations are grouped by task, revealing mature areas (registries, verification) and experimental ones (logistics).

Cluster A: Registries and Access Management

• Estonia (KSI, 2012): Merkle hash trees protect population data. Patients see real-time access audits via e-Estonia. Off-chain—clinic records, on-chain—event hashes.
• MedRec (MIT, 2016): Ethereum smart contracts manage rights over EHRs. Pattern: blockchain as an overlay for legacy systems.
• Medibloc (Korea, 2017): Proprietary Panacea blockchain aggregates records. Patients delegate access via MED tokens; data is transferred P2P with encryption.

Cluster B: Document Verification

• Singapore OpenAttestation (2020): Ethereum for COVID certificates. JSON → hash in smart contract → verification without a central database. Extended to diplomas and licenses.
• WHO Smart Vaccination (2021): Framework for cross-border verification without bilateral agreements.
• IBM Digital Health Pass (2021): Tool for health verification without data disclosure.

Other clusters include pharmaceutical supply chains (MediLedger), insurance, and research—all relying on permissioned blockchains for scale.

Architectural Patterns

• Hash Ledger: On-chain metadata, off-chain data.
• Smart Access: Contracts for roles (doctor/insurer).
• SSI Identity: DID (Decentralized Identifiers) for patients.
• Task-Based Consensus: PBFT in permissioned networks for TPS >1000.
• FHIR Integration: Blockchain as a trust layer over exchange standards.

These patterns are scalable and compatible with existing EHRs.

Key Takeaways

• Blockchain does not store data but guarantees immutability through hashes—key to trust without an arbitrator.
• Permissioned networks (Hyperledger) dominate in E-Health due to performance and confidentiality.
• Patient control via SSI shifts the paradigm: data is decentralized by rights.
• Real-world scale: Estonia (population), U.S. (95% of pharmaceuticals), Singapore (global certificates).
• Breach costs decrease: mathematical verification minimizes risks.

— Editorial Team