[24], and are summarised in Section four. The following actions had been utilised by
[24], and are summarised in Section 4. The following measures had been utilised by the lead author of this paper to conduct the literature review:Appl. Syst. Innov. 2021, 4,7 ofConduct a search on PHA-543613 In Vitro IEEEXplore, ScienceDirect and Google scholar applying the search string; “healthcare AND (security OR privacy) AND (typical OR regulation OR compliance) AND (barrier OR challenges OR difficulties)”. Set inclusion criteria as follows: (1) presented the challenges for assuring security and privacy of healthcare applications that comply with regulations; (two) publication year: 2010020; (three) language is English and complete text accessible. The initial search resulted inside a total of 320 study papers. Inside the first screening every paper was analyzed by reviewing the abstract and conclusion. In the event the paper addressed any challenges, then it was selected for the second screening. A total of 125 papers out of 320 were chosen for the second screening. Within the second screening each and every paper was analyzed by reading the complete text and checking no matter if the paper presented any challenges for assuring safety and privacy of healthcare applications that comply with regulations. The second screening resulted inside a total of 19 papers out of 125. Lastly, a list of challenges was recorded from these papers which is presented in Section 4.3.four. Create the Proposed Safety and Privacy Framework The following measures were employed to develop the safety and privacy danger management framework:Determine the possible threats and vulnerabilities of a WBAN primarily based healthcare application by conducting threat modeling. Overview the report from threat modeling to recognize the respective control(s) for each and every threat and vulnerability. Create the implementation PK 11195 In Vitro specifics for these controls (presented in Section 5.two.). Validate the effectiveness from the controls by implementation in an industrial setting. This is outlined in Section six. Gather suggestions and ideas for improvement towards the alpha version from the organization who performed the implementation. That is outlined in Section six.five.Every single in the recommendations were then reviewed by the authors of this paper. All the suggestions were regarded, and acceptable action was taken throughout development from the beta version. By way of example, the developer recommended to identify the threats and vulnerabilities at the requirement evaluation phase to produce the security and privacy specifications. To address this suggestion a security threat assessment step was designed to be conducted in both the requirement evaluation along with the technique architecture phases (presented in Section 8.three). Sections 70 present the detailed measures and implementation course of action of the beta version of the framework. four. Challenges The list of challenges from both the literature overview and interview is presented in Table 1. The second column indicates no matter whether the challenges were identified by literature critique or by interview, or certainly by both literature critique and interview.Table 1. List of challenges. Challenges Lack of educated staff, responsibilities, budget, and management help The existing requirements are as well complex and complicated to implement Restricted knowledge about market-specific regulatory specifications, security requirements, and policies Sources Literature [254] Literature [27,30,357] Literature Interview [32,36,380]Appl. Syst. Innov. 2021, four,8 ofTable 1. Cont. Challenges Lack of extensive understanding of the architecture for WBAN safety and privacy Understanding the data flow about the sys.