Adaptation and application of the IEEE 2413-2019 standard security mechanisms to IoMT systems
Healthcare information systems are evolving from traditional centralised architectures towards highly-mobile distributed environments within the connected health context. The IoMT paradigm is at the forefront of this technological revolution underlying the development of communication infrastructure...
| Autores: | , , |
|---|---|
| Tipo de recurso: | artículo |
| Estado: | Versión publicada |
| Fecha de publicación: | 2022 |
| País: | España |
| Institución: | Universidad de Sevilla (US) |
| Repositorio: | idUS. Depósito de Investigación de la Universidad de Sevilla |
| OAI Identifier: | oai:idus.us.es:11441/139177 |
| Acceso en línea: | https://hdl.handle.net/11441/139177 https://doi.org/10.1016/j.measen.2022.100375 |
| Access Level: | acceso abierto |
| Palabra clave: | Internet of medical things (IoMT) Interoperability Security Smart sensor device IEEE 2413-2019 Connected health |
| Sumario: | Healthcare information systems are evolving from traditional centralised architectures towards highly-mobile distributed environments within the connected health context. The IoMT paradigm is at the forefront of this technological revolution underlying the development of communication infrastructures connecting smart medical devices, healthcare information systems and services. The IEEE 2413 standard, a promising general architectural framework for the design and implementation of IoT systems, has recently been announced. This standard proposes a general description for different types of domains, including healthcare, but it does not contain an extension developed for the IoMT systems domain. This paper presents a first approach to adapt the IEEE 2413 standard to the design of IoMT systems from a security perspective, considering the most relevant aspects of the standard for the construction of this type of systems. The application to an IoMT system for monitoring patients with chronic obstructive pulmonary disease is presented as a use case. |
|---|