tectures for where the blockchain can be used. A blockchain can be placed on the cloud, the edge, or between devices in an IoT network or a combination of all of these. Guo et al. [11] suggested using blockchain on edge for authentication while the transaction recording is done on a blockchain on the cloud. Permission management can be placed instead in the cloud, as the case with MedRec [12]. Seng et al. [13] suggested a blockchain that connects end devices and MEC servers altogether. The blockchain was used for sharing offloading tasks to other devices and the MEC server to decide where best to place the task in a decentralized manner. Results showed that their solution reached a better offloading success rate and less energy consumption compared to centralized offloading techniques. However, there is no analysis for the latency of their framework compared to the centralized approach. EdgeBot [14] uses a 4-layer architecture, namely, the sensor, edge, fog, and cloud layers. The blockchain and smart contracts are hosted at the fog layer, which manages several edge gateways. Edge gateways collect and analyze data and send it to the fog layer. The fog layer acts as a data gatekeeper between data from sensors and the cloud applications requesting the data. This way, only authorized 5G Wireless Communication System in Healthcare Informatics entities can send or receive data. EdgeMediChain [15] breaks down the blockchain into two parts for more efficiency. The first part is the local edge-mining layer which manages the authentication of IoT devices within their geolocation without downloading information about users outside their range. Local edge-mining layers reach consensus about their state through proof-of-authority (PoA), which does not require computationally intensive work. The second part is the global blockchain, based on Ethereum, which contains hashes of transactions done on the EMR of all patients. The EMR itself is stored on InterPlanetary File System (IPFS). To decrease the global blockchain burden, th