Table 1 Research on the scalability of blockchain-based healthcare systems.
No. | Research | Method | Advantages | Disadvantages |
|---|---|---|---|---|
1 | 14, 2017 | An index is created on a web platform using a URL for each healthcare data entry, alongside access control permissions managed through smart contracts, which are stored on the blockchain. | Reduction of computational resources per node; increased scalability. | The growing volume of healthcare data is not adequately addressed, particularly regarding the integrity of data stored on the web. |
2 | 25, 2018 | Task allocation among different nodes, where each node is responsible for a specific task. | Reduction of computational resources per node; increased scalability. | Although more nodes are participating in the network, they lack the computational resources needed to store the complete chain of blocks, which diminishes the overall trustworthiness of the blockchain. |
3 | 23, 2021 | New blocks are replicated more frequently than old blocks across full nodes. | Reduction of computational resources per node; increased scalability. | This approach reduces the trustworthiness of the blockchain and increases retrieval time for older blocks. |
4 | 13, 2021 | Utilizing two separate chains, with healthcare data stored on-chain and access control policies stored off-chain. | Reduction of computational resources per node; increased scalability. | The data integrity stored on the off-chain is not ensured. |
5 | 12, 2022 | The data and its hash are initially stored off-chain, with only the hash placed on the blockchain. | Reduction of computational resources per node; increased scalability. | The integrity of off-chain data is not addressed. |
6 | 28, 2024 | Raw data is stored on IPFS servers, with a single hash value created for all the data and included in the block. | Reduction of computational resources per node; increased scalability. | The integrity of off-chain data remains a concern. |
7 | 21,2025 | User data is clustered, with each cluster containing only its users’ data in its designated chain of blocks, while maintaining hashes of blocks created from other clusters. | Reduction of computational resources per node; increased scalability. | Global data retrieval times are not considered. |
