## 7 Architectural Challenges in Designing Any Smart Healthcare Application
### IoT Data Handling in Smart Healthcare  
Smart healthcare uses different communication technologies and standards, which results in difficulties in data aggregation [91]. A tremendous amount of medical data is generated by sensors. It is extremely difficult for doctors to manage, which ultimately affects the quality of decision-making. This will eventually lead to patient safety issues [86]. A generic architecture for IoT data handling is presented in Figure 16. Physical devices, such as sensors and RFID tags, generate vast amounts of data that should be stored and processed efficiently and effectively. Many big data and analytic data techniques are employed to handle this data, but there are still some challenges in managing and utilizing massive volumes of data [92]. Traditional database management systems cannot take IoT data, as unstructured and heterogeneous massive data are produced. IoT IWF Reference Architecture layers, including the edge computing layer, data accumulation layer, and data abstraction layer, are responsible for handling IoT systems' data. Service discovery protocols such as m-DNS and DNS-SD operate at the fog level and send the patterns to the cloud. The frontend is a communication-centric and online-based platform that collects, filters, aggregates, and delivers the patterns to the back end, which is offline based. This storage-centric backend is responsible for preprocessing, storing, and analyzing the familiar patterns of the applications/service layer that result from historical and global queries. The edge computing layer is responsible for producing, processing, storing, updating, and delivering the processed patterns to the application/service layer. This application layer supports query retrieval, which can again be given to the edge computing framework for reporting the data to the interested parties. This reporting can produce real-time and localized queries [5]. Traditional database management techniques cannot be applied for IoT data management. Table 4 provides the fundamental differences between both [5].  
The data management layer in the above architecture includes the middle three layers of IoT IWF Architecture, and Table 5 presents the responsibilities of these layers.  
\begin{table}
\begin{tabular}{c c} \hline \hline
**IoT Protocols** & **Respective IoT Application** \\ \hline NFC & Payments and loyalty points, Identity \\ NFC & Validation, Access Control, Attendance \\ tracking, and record-keeping \\ \hline BLE & Fitness trackers, Smart watches, Beacons, \\ Medical devices, Home automation devices \\ \hline Zigbee & Security systems, Light control systems, \\ Gaming consoles, Wireless control, Industrial \\ automation, Health care, Fire extinguishers \\ \hline Wi-Fi & Mobile applications, Business applications, \\ Smart home, Computerized applications, \\ Automotive segment \\ \hline
6 LoWPAN & Automation, Industrial monitoring, Smart grid, \\ Smart home \\ \hline IPV6 & Net utilities (ping, ipconfig), FTP, TELNET, \\ SMTP \\ \hline LoRa WAN & Smart city, Industrial applications, Smart home \\ applications, Smart health, Smart applications \\ \hline LTE-M & Smart city services, Asset tracking, Wearable, \\ E-Health solutions \\ \hline NB-IoT & Smart metering, Facility management services, \\ Intruder and fire alarms, Appliances measuring \\ health parameters, Object tracking, Smart city \\ infrastructure, Connected Industrial appliances \\ \hline MQTT & Gathering sensor data, Synchronization of \\ sensors, Monitoring health parameters via \\ sensors, Alert messages, Facebook Messenger \\ \hline CoAP & Smart energy, Building automation \\ \hline \hline \end{tabular}
\end{table}
Table 4: IoT protocols and respective applications.  
Figure 16: IoT data handling architecture.  
Scalability and security are the significant challenges of IoT data handling. Processing and extracting the patterns based on client requirements will simplify data handling. The secured protocols must be implemented for data integrity and access control.