An ICE Compliant Component Model for Medical Systems Development

Touahria, Imad Eddine; García-Valls, Marisol; Khababa, Abdellah

doi:10.1109/compsac.2017.55

Cited by 6 publications

(7 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The most common ports are RS 232 port (DB-9, DB-15, and DB-25), RJ 45, wireless LAN, Bluetooth, USB, or some proprietary data connection systems developed by suppliers for using data by their own IT systems. The following are the most common hardware connections used by suppliers to input data into the device: PS/2 (for supporting keyboard or a mouse inputs), USB, RS 232, and digital data input [71]. Figure 2 shows how medical devices are integrated in a clinical situation and the way how medical devices are connected to the patient body, to each other and to networking devices.…”

Section: Medical Devices and Medical Communication Standardsmentioning

confidence: 99%

“…To support such interconnection in a safe way, medical systems actors convened on the need of a common environment to facilitate interoperability and safety. The Integrated Clinical Environment (ICE) is a new solution that includes many stakeholders where the final goal is to realize an interoperable network of medical device in a safe way [71], to achieve this medical devices manufacturers must rely to standards defined by ICE and/or other interoperability projects. Communication standards in medical devices are away to be used by manufacturers even in the same company and for devices that are from the same range, as a result, devices that have the same communication standards may not be able to communicate.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Medical systems, the role of middleware and survey on middleware design

Touahria

2018

Preprint

Self Cite

View full text Add to dashboard Cite

The integration of medical devices in the patient treatment process becomes increasingly important due to the efficiency of the technology. On the one hand, medical devices hardware is more powerful and its integration with the software platforms is improved. These devices are able to transfer accurate data to the clinician and offer the possibility of sharing data with other devices or computational servers for advanced analysis. On the other hand, medical software platforms are appearing to provide advanced functionality on top of these medical hardware devices. In this context, the role of the software is essential, not only at the highest abstraction level that provides the application business logic; the role of the underlying connecting software (the communication middleware or distribution software) is essential. These are capable of providing advanced connectivity functions, very efficiently, and within appropriate time bounds. This paper reviews the state of the art on middleware as facilitator for interconnection among devices and also describes a number of initiatives (such as the Integrated Clinical Environment -ICE) and projects that further extend the underlying distribution software towards the clinical domain as device interconnection facilitators.

show abstract

Section: Medical Devices and Medical Communication Standardsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Medical systems, the role of middleware and survey on middleware design

Touahria

2018

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

“…To support such interconnection in a safe way, the involved actor agreed on the necessity of a common environment to facilitate interoperability and safety. The most accepted one is the Integrated Clinical Environment (ICE), that is a new solution involving a number of stakeholders where the final goal is to realize an interoperable network of medical devices in a safe way [105]. To fulfill this goal, manufacturers have to use standards such as ICE (Integrated Clinical Environment) or other medical-device interoperability projects.…”

Section: Introductionmentioning

confidence: 99%

An incomplete and biased survey on selected resource management for distributed applications as basis for interoperability of medical devices

Touahria

2018

Preprint

Self Cite

View full text Add to dashboard Cite

The popularity and wide spread of IoT technology has brought about a rich hardware infrastructure over which it is possible to run powerful applications that were not previously imagined. Among this infrastructure, there are the medical hardware that is progressively advancing but at a slower pace. Nevertheless, medical devices are more powerful now to run more sophisticated functions and applications and exchange big data with external systems in a secure and safe fashion. Towards the design of an architecture for interoperability of medical devices, this paper initially focuses on the background work that is taken by the author for this objective. The paper briefly describes the role of the software in the advances of medical systems and their possibilities for interoperability. It focuses attention on the distribution software layer that is responsible for connectivity, efficiency, and time-sensitivity in the basic operation of medical systems such as exchange of information and commands across devices and systems. The paper analyses a number of previous work on middleware (mostly performed at his research group and also in a broader research community), and pay especial attention to the middleware for web-based systems and how they relate to the development of distributed medical systems.

show abstract

“…[ 28 ] that discusses security aspects on eHealth; Ref. [ 29 ] that provides a framework for integration of medical systems and distributed technology; in [ 30 ], a component model is described that allows developing medical systems for ICE-compliant applications. However, none of these contributions focuses on provisioning the ICE standard with reconfiguration and on line service composition facilities.…”

Section: Introductionmentioning

confidence: 99%

On Line Service Composition in the Integrated Clinical Environment for eHealth and Medical Systems

García-Valls

Touahria

2017

Sensors

View full text Add to dashboard Cite

Medical and eHealth systems are progressively realized in the context of standardized architectures that support safety and ease the integration of the heterogeneous (and often proprietary) medical devices and sensors. The Integrated Clinical Environment (ICE) architecture appeared recently with the goal of becoming a common framework for defining the structure of the medical applications as concerns the safe integration of medical devices and sensors. ICE is simply a high level architecture that defines the functional blocks that should be part of a medical system to support interoperability. As a result, the underlying communication backbone is broadly undefined as concerns the enabling software technology (including the middleware) and associated algorithms that meet the ICE requirements of the flexible integration of medical devices and services. Supporting the on line composition of services in a medical system is also not part of ICE; however, supporting this behavior would enable flexible orchestration of functions (e.g., addition and/or removal of services and medical equipment) on the fly. iLandis one of the few software technologies that supports on line service composition and reconfiguration, ensuring time-bounded transitions across different service orchestrations; it supports the design, deployment and on line reconfiguration of applications, which this paper applies to service-based eHealth domains. This paper designs the integration between ICE architecture and iLand middleware to enhance the capabilities of ICE with on line service composition and the time-bounded reconfiguration of medical systems based on distributed services. A prototype implementation of a service-based eHealth system for the remote monitoring of patients is described; it validates the enhanced capacity of ICE to support dynamic reconfiguration of the application services. Results show that the temporal cost of the on line reconfiguration of the eHealth application is bounded, achieving a low overhead resulting from the addition of ICE compliance.

show abstract

An ICE Compliant Component Model for Medical Systems Development

Cited by 6 publications

References 14 publications

Medical systems, the role of middleware and survey on middleware design

Medical systems, the role of middleware and survey on middleware design

An incomplete and biased survey on selected resource management for distributed applications as basis for interoperability of medical devices

On Line Service Composition in the Integrated Clinical Environment for eHealth and Medical Systems

Contact Info

Product

Resources

About