on or control another product. OR.NET [@ORNET] and ICE [@CIMIT] are two examples of projects whose objective is to provide a safe and interoperable network of medical devices. This will be later described in this paper.

For safety reasons, medical systems have traditionally been deployed in isolation. However, the proliferation of networking technology and distribution software and middleware has also reached eHealth in such a way that medical systems are becoming more open. 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 [@8029619]. To fulfill this goal, manufacturers have to use standards such as ICE (Integrated Clinical Environment) or other medical-device interoperability projects. Communication standards are beneficial for manufacturers, health care providers, and users: According to the west health organization [@WEST], the take up of functional interoperability in medical devices can save up to \$30 billion dollars.

Having said the above, this paper focuses on the impact of 