A secure and flexible e-Health access control system with provisions for emergency access overrides and delegation of access privileges

Khan, M. Fahim Ferdous; Satoh, Ken

doi:10.1109/icact.2016.7423463

Cited by 3 publications

(4 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some papers addressed the need for emergency access and/or access delegation features in addition to RBAC. The Khan and Sakamura [ 14 , 16 , 17 ] work describes an RBAC adaptation based on access context. The scenario described is emergency access needed for EHR system information that is currently common on ambulatory but mostly at hospital facilities.…”

Section: Literature Review Classificationmentioning

confidence: 99%

“…The Chen and Hoang [ 20 ] approach is also concerned with the interdomain and cross-border issues related to the use of cloud-based solutions. Similar to [ 14 , 17 ], they propose a context-based access decision that adds the “Role Roaming” and the “Active Auditing” to the scheme. Also using an information segmentation approach to store EHR securely in the cloud environment, Premarathne et al [ 21 ] suggest the use of steganography-cryptography to index protected information.…”

Section: Literature Review Classificationmentioning

confidence: 99%

“…Although some articles focused only at describing the need of an additional security layer or different access control model combination [ 26 , 29 , 31 ], we can summarize RBAC current adaptation needs as follows: Conditional or emergency access and authorization are delegated. Context- and situation access-based solutions are advocated to be adapted over original RBAC features [ 14 , 16 – 18 , 32 ] requiring additional user's obligation. Access segmentation and interdomain/federation scenarios are needed.…”

Section: Rbac Current Security Trends and Limitations Mapped On Himentioning

confidence: 99%

“…Context- and situation access-based solutions are advocated to be adapted over original RBAC features [ 14 , 16 – 18 , 32 ] requiring additional user's obligation.…”

Section: Rbac Current Security Trends and Limitations Mapped On Himentioning

confidence: 99%

See 3 more Smart Citations

Health Information System Role-Based Access Control Current Security Trends and Challenges

Carvalho

Bandiera-Paiva

2018

Journal of Healthcare Engineering

View full text Add to dashboard Cite

Objective This article objective is to highlight implementation characteristics, concerns, or limitations over role-based access control (RBAC) use on health information system (HIS) using industry-focused literature review of current publishing for that purpose. Based on the findings, assessment for indication of RBAC is obsolete considering HIS authorization control needs. Method We have selected articles related to our investigation theme “RBAC trends and limitations” in 4 different sources related to health informatics or to the engineering technical field. To do so, we have applied the following search query string: “Role-Based Access Control” OR “RBAC” AND “Health information System” OR “EHR” AND “Trends” OR “Challenges” OR “Security” OR “Authorization” OR “Attacks” OR “Permission Assignment” OR “Permission Relation” OR “Permission Mapping” OR “Constraint”. We followed PRISMA applicable flow and general methodology used on software engineering for systematic review. Results 20 articles were selected after applying inclusion and exclusion criteria resulting contributions from 10 different countries. 17 articles advocate RBAC adaptations. The main security trends and limitations mapped were related to emergency access, grant delegation, and interdomain access control. Conclusion Several publishing proposed RBAC adaptations and enhancements in order to cope current HIS use characteristics. Most of the existent RBAC studies are not related to health informatics industry though. There is no clear indication of RBAC obsolescence for HIS use.

show abstract

Section: Literature Review Classificationmentioning

confidence: 99%

Section: Literature Review Classificationmentioning

confidence: 99%

Section: Rbac Current Security Trends and Limitations Mapped On Himentioning

confidence: 99%

“…Context- and situation access-based solutions are advocated to be adapted over original RBAC features [ 14 , 16 – 18 , 32 ] requiring additional user's obligation.…”

Section: Rbac Current Security Trends and Limitations Mapped On Himentioning

confidence: 99%

See 2 more Smart Citations