OR.NET RT: how service-oriented medical device architecture meets real-time communication.

Today's landscape of medical devices is dominated by stand-alone systems and proprietary interfaces lacking cross-vendor interoperability. This complicates or even impedes the innovation of novel, intelligent assistance systems relying on the collaboration of medical devices. Emerging approaches use the service-oriented architecture (SOA) paradigm based on Internet protocol (IP) to enable communication between medical devices. While this works well for scenarios with no or only soft timing constraints, the underlying best-effort communication scheme is insufficient for time critical data. Real-time (RT) networks are able to reliably guarantee fixed latency boundaries, for example, by using time division multiple access (TDMA) communication patterns. However, deterministic RT networks come with their own limitations such as tedious, inflexible configuration and a more restricted bandwidth allocation. In this contribution we overcome the drawbacks of both approaches by describing and implementing mechanisms that allow the two networks to interact. We introduce the first implementation of a medical device network that offers hard RT guarantees for control and sensor data and integrates into SOA networks. Based on two application examples we show how the flexibility of SOA networks and the reliability of RT networks can be combined to achieve an open network infrastructure for medical devices in the operating room (OR).

Software design and implementation concepts for an interoperable medical communication framework.

The new IEEE 11073 service-oriented device connectivity (SDC) standard proposals for networked point-of-care and surgical devices constitutes the basis for improved interoperability due to its independence of vendors. To accelerate the distribution of the standard a reference implementation is indispensable. However, the implementation of such a framework has to overcome several non-trivial challenges. First, the high level of complexity of the underlying standard must be reflected in the software design. An efficient implementation has to consider the limited resources of the underlying hardware. Moreover, the frameworks purpose of realizing a distributed system demands a high degree of reliability of the framework itself and its internal mechanisms. Additionally, a framework must provide an easy-to-use and fail-safe application programming interface (API). In this work, we address these challenges by discussing suitable software engineering principles and practical coding guidelines. A descriptive model is developed that identifies key strategies. General feasibility is shown by outlining environments in which our implementation has been utilized.