FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W3015732378> ?p ?o ?g. }

• W3015732378 endingPage "e18175" @default.
• W3015732378 startingPage "e18175" @default.
• W3015732378 abstract "Background As familiarity with and convenience of using personal devices in hospitals help improve the productivity, efficiency, and workflow of hospital staff, the health care bring-your-own-device (BYOD) market is growing consistently. However, security concerns owing to the lack of control over the personal mobile devices of staff, which may contain sensitive data such as personal health information of patients, make it one of the biggest health care information technology (IT) challenges for hospital administrations. Objective Given that the hospital BYOD security has not been adequately addressed in peer-reviewed literature, the aim of this paper was to identify key security challenges associated with hospital BYOD usage as well as relevant solutions that can cater to the identified issues by reviewing gray literature. Therefore, this research will provide additional practical insights from current BYOD practices. Methods A comprehensive gray literature review was conducted, which followed the stepwise guidelines and quality assessment criteria set out by Garousi et al. The searched literature included tier 1 sources such as health care cybersecurity market reports, white papers, guidelines, policies, and frameworks as well as tier 2 sources such as credible and reputed health IT magazines, databases, and news articles. Moreover, a deductive thematic analysis was conducted to organize the findings based on Schlarman’s People Policy Technology model, promoting a holistic understanding of hospitals’ BYOD security issues and solutions. Results A total of 51 sources were found to match the designed eligibility criteria. From these studies, several sociotechnical issues were identified. The major challenges identified were the use of devices with insufficient security controls by hospital staff, lack of control or visibility for the management to maintain security requirements, lack of awareness among hospital staff, lack of direction or guidance for BYOD usage, poor user experience, maintenance of legal requirements, shortage of cybersecurity skills, and loss of devices. Although technologies such as mobile device management, unified endpoint management, containerization, and virtual private network allow better BYOD security management in hospitals, policies and people management measures such as strong security culture and staff awareness and training improve staff commitment in protecting hospital data. Conclusions The findings suggest that to optimize BYOD security management in hospitals, all 3 dimensions of the security process (people, policy, and technology) need to be given equal emphasis. As the nature of cybersecurity attacks is becoming more complex, all dimensions should work in close alignment with each other. This means that with the modernization of BYOD technology, BYOD strategy, governance, education, and relevant policies and procedures also need to adapt accordingly." @default.
• W3015732378 created "2020-04-17" @default.
• W3015732378 creator A5006392412 @default.
• W3015732378 creator A5052253938 @default.
• W3015732378 creator A5077798762 @default.
• W3015732378 date "2020-06-18" @default.
• W3015732378 modified "2023-09-27" @default.
• W3015732378 title "Hospital Bring-Your-Own-Device Security Challenges and Solutions: Systematic Review of Gray Literature" @default.
• W3015732378 cites W1028229730 @default.
• W3015732378 cites W1975592151 @default.
• W3015732378 cites W1995851560 @default.
• W3015732378 cites W2025476516 @default.
• W3015732378 cites W2048172235 @default.
• W3015732378 cites W2057703873 @default.
• W3015732378 cites W2073990477 @default.
• W3015732378 cites W2084203262 @default.
• W3015732378 cites W2133674686 @default.
• W3015732378 cites W2168459847 @default.
• W3015732378 cites W2174850379 @default.
• W3015732378 cites W2299804167 @default.
• W3015732378 cites W2336383631 @default.
• W3015732378 cites W2387564118 @default.
• W3015732378 cites W2560352887 @default.
• W3015732378 cites W2735864825 @default.
• W3015732378 cites W2788456181 @default.
• W3015732378 cites W2800111293 @default.
• W3015732378 cites W2910070300 @default.
• W3015732378 cites W2912172640 @default.
• W3015732378 cites W4294215472 @default.
• W3015732378 doi "https://doi.org/10.2196/18175" @default.
• W3015732378 hasPubMedCentralId "https://www.ncbi.nlm.nih.gov/pmc/articles/7333072" @default.
• W3015732378 hasPubMedId "https://pubmed.ncbi.nlm.nih.gov/32554388" @default.
• W3015732378 hasPublicationYear "2020" @default.
• W3015732378 type Work @default.
• W3015732378 sameAs 3015732378 @default.
• W3015732378 citedByCount "25" @default.
• W3015732378 countsByYear W30157323782020 @default.
• W3015732378 countsByYear W30157323782021 @default.
• W3015732378 countsByYear W30157323782022 @default.
• W3015732378 countsByYear W30157323782023 @default.
• W3015732378 crossrefType "journal-article" @default.
• W3015732378 hasAuthorship W3015732378A5006392412 @default.
• W3015732378 hasAuthorship W3015732378A5052253938 @default.
• W3015732378 hasAuthorship W3015732378A5077798762 @default.
• W3015732378 hasBestOaLocation W30157323781 @default.
• W3015732378 hasConcept C127627568 @default.
• W3015732378 hasConcept C136764020 @default.
• W3015732378 hasConcept C144024400 @default.
• W3015732378 hasConcept C144133560 @default.
• W3015732378 hasConcept C160735492 @default.
• W3015732378 hasConcept C177212765 @default.
• W3015732378 hasConcept C17744445 @default.
• W3015732378 hasConcept C184356942 @default.
• W3015732378 hasConcept C186967261 @default.
• W3015732378 hasConcept C190248442 @default.
• W3015732378 hasConcept C199360897 @default.
• W3015732378 hasConcept C199539241 @default.
• W3015732378 hasConcept C2778282719 @default.
• W3015732378 hasConcept C2779473830 @default.
• W3015732378 hasConcept C36289849 @default.
• W3015732378 hasConcept C39549134 @default.
• W3015732378 hasConcept C41008148 @default.
• W3015732378 hasConcept C56666940 @default.
• W3015732378 hasConcept C56739046 @default.
• W3015732378 hasConcept C61904560 @default.
• W3015732378 hasConcept C71924100 @default.
• W3015732378 hasConcept C74196892 @default.
• W3015732378 hasConcept C77088390 @default.
• W3015732378 hasConceptScore W3015732378C127627568 @default.
• W3015732378 hasConceptScore W3015732378C136764020 @default.
• W3015732378 hasConceptScore W3015732378C144024400 @default.
• W3015732378 hasConceptScore W3015732378C144133560 @default.
• W3015732378 hasConceptScore W3015732378C160735492 @default.
• W3015732378 hasConceptScore W3015732378C177212765 @default.
• W3015732378 hasConceptScore W3015732378C17744445 @default.
• W3015732378 hasConceptScore W3015732378C184356942 @default.
• W3015732378 hasConceptScore W3015732378C186967261 @default.
• W3015732378 hasConceptScore W3015732378C190248442 @default.
• W3015732378 hasConceptScore W3015732378C199360897 @default.
• W3015732378 hasConceptScore W3015732378C199539241 @default.
• W3015732378 hasConceptScore W3015732378C2778282719 @default.
• W3015732378 hasConceptScore W3015732378C2779473830 @default.
• W3015732378 hasConceptScore W3015732378C36289849 @default.
• W3015732378 hasConceptScore W3015732378C39549134 @default.
• W3015732378 hasConceptScore W3015732378C41008148 @default.
• W3015732378 hasConceptScore W3015732378C56666940 @default.
• W3015732378 hasConceptScore W3015732378C56739046 @default.
• W3015732378 hasConceptScore W3015732378C61904560 @default.
• W3015732378 hasConceptScore W3015732378C71924100 @default.
• W3015732378 hasConceptScore W3015732378C74196892 @default.
• W3015732378 hasConceptScore W3015732378C77088390 @default.
• W3015732378 hasIssue "6" @default.
• W3015732378 hasLocation W30157323781 @default.
• W3015732378 hasLocation W30157323782 @default.
• W3015732378 hasLocation W30157323783 @default.
• W3015732378 hasLocation W30157323784 @default.
• W3015732378 hasLocation W30157323785 @default.
• W3015732378 hasOpenAccess W3015732378 @default.

• next