Research Article
[Retracted] Systematic Assessment of the Interoperability Requirements and Challenges of Secure Blockchain-Based Electronic Health Records
Table 6
Approaches for blockchain-based EHR interoperability challenges.
| | Ref. | Blockchain-based EHR framework | | Technique used | RE | AD | DP | SC | SCA | AC | AUTN | AUTR | ANON | RB | COFD | IMMU | Standard used/rule | Suggested standard |
| | [43] | 1.Ciphertext-based attribute encryption | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | No | No | Yes | Yes | No | — |
| | [44] | 1. Zero-knowledge proofs
2. Proxy re-encryption | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No | Yes | HIPAA | FHIR |
| | [45] | 1. Distributed ledger technology
2. Smart contract
3. Hashing algorithm | No | No | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | — |
| | [46] | 1.SHA-256 algorithm
2. RSA encryption | No | No | Yes | Yes | No | Yes | Yes | Yes | No | No | Yes | Yes | No | HL7, FHIR |
| | [45] | 1. Public key infrastructure-based asymmetric encryption
2. Digital signatures to secure shared EHR data | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | Yes | HIPAA | HL7, FHIR |
| | [47] | 1. Smart contract
2. AWS | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | HITECH, HL7 | FHIR |
| | [48] | 1. Smart contract | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes | No | No | Yes | HIPAA | — | | | 2. Hashing method-SHA-256 | | | | | | | | | | | | | | |
| | [49] | 1. Proxy re-encryption technology
2. DPoS consensus mechanism | Yes | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No | No | Yes | No | Unified standard |
| | [50] | 1. Blockchain base lattice cryptography
2. Deep learning as a service | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | Yes | HIPAA | FHIR |
| | [51] | 1. Cryptographic hash key
2. Genetic algorithm | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | No | Standard regulations |
| | [52] | 1. Smart contract
2. Cryptographic techniques | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | HIPAA | HL7 |
| | [53] | 1. Cryptographic techniques (encryption and digital signatures) | No | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | Yes | No | — |
| | [54] | 1. Smart contract. | No | No | Yes | Yes | No | Yes | Yes | Yes | Yes | No | Yes | Yes | No | — |
| | [55] | 1. Public key cryptography
2. Proof of work algorithm
3. Smart contract | No | No | Yes | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | Yes | HIPAA | HL7, FHIR |
| | [56] | 1. Multi-authority attribute-based encryption
2. Smart contract | No | No | Yes | Yes | No | Yes | Yes | Yes | No | No | Yes | Yes | HIPAA | — |
| | [42] | 1. Smart contract
2. Digital identities | Yes | No | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No | Yes | ONC, FHIR, Hl7 | New versions of HL7 to support semantic interoperability |
| | [57] | 1. Off-chain storage and on-chain verification | No | No | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | Yes | No | — |
|
|
