# Design and Evaluation of Large-Scale IoT-Enabled Healthcare Architecture
## 5 Results and Discussion
The x- and y-axes represent the simulation time (minutes) and packet loss ratios over the simulation time, respectively. The packet loss percentage for the proposed IoT-enabled healthcare architecture is less than that of the traditional architecture because the congestion rate increases in the traditional healthcare architecture due to using only Internet as a coverage tool, increasing the packet loss ratio. Moreover, for the traditional healthcare architecture, increasing of transmission and processing data leads to increasing of packet loss ratio. The small hesitations, which are found in the two plots, are explained by sudden changing in the available bandwidth values due to bottleneck occurrence. Figure 11 displays the employment of coverage tools. It is measured by the percentage of users that have benefited from each coverage tool as first, second, or third priority within a simulation time. This performance metric is selected to ensure that each device can easily exchange between different coverage tools in the proposed IoT-enabled healthcare architecture. The x- and y-axes represent the coverage tool (first, second, and third priority) and usage percentages, respectively. The Internet coverage tool has the largest values. The  
Figure 10: Packet loss ratio. Figure 9: Energy consumption average. HAP coverage tool follows the Internet, and the satellite coverage tool has the least usage percentage. This is because the Internet has first priority to cover things in the proposed IoT-enabled healthcare architecture. In addition, in some situations the satellite and HAP are used for the things that loss the Internet signal, which means that both of them may have first or second priority (according to their coverage areas). Figure 12 illustrates the average throughput for the two healthcare architectures. The x- and y-axes represent the simulation time and average throughput divided by 10E6, respectively. The average throughput for the proposed IoT-enabled healthcare architecture is greater than that of the traditional architecture over the simulation time. This is explained for the traditional healthcare architecture by increasing packet loss and delay values causing a negative effect for the size of data that is correctly received and a decrease in the average throughput. The fluctuations in the two plots come from the network bottlenecks and numerous dynamic joining and leaving in the architectures that cause sudden changes in the size of the transmitted data. Figure 11: Usage of coverage tools. Figure 12: Average of throughput. Figure 13 presents the percentage of served users in the two healthcare architectures. The x- and y-axes represent the number of users per simulation time and the servicing percentage, respectively. The red points represent the proposed IoT-enabled healthcare architecture and are between approximately 90% and 100%, and the black points represent the traditional healthcare architecture and are between approximately 80% and 91%. Therefore, the servicing percentages over the simulation time for the proposed IoT-enabled healthcare architecture are larger than those of the traditional healthcare architecture. This outcome is because of the availability of multiple coverage tools, such as satellites and HAPs, in addition to Internet. In addition, the selection flexibility of computing resources, which are connected to the proposed IoT-enabled healthcare architecture, increases the number of benefited users. Most of healthcare things, such as doctors, patients, managers, employees, pharmacists, and the vast majority of medical and non-medical devices, use text data to complete the cooperation between each other. In addition, many medical devices use other types of data such as multimedia (video and audio) in addition to images. Hence, this performance metric is measured to ensure that the proposed IoT-enabled healthcare architecture can transmit the different data types required by medical fields to achieve its functions.