Communication patterns

This project explores various clinical scenarios on top of various middleware using a basic set of communication patterns.  This project is composed of the following components. 

• Simple Communication Patterns abstract low-level details of communication between medical devices and applications.  All of the four patterns support properties to capture QoS requirements.  The supported properties enable modular reasoning (via local control) about devices and applications. A prototype Java implementation of the patterns is available on top of RTI Connext and Vert.x via a common API/SPI and general mechanism to notify clients about the violation of QoS requirements.
• Clinical Scenarios demonstrate the use of both the native API of communication substrates (such as DDS) and simple communication patterns to realize various clinical scenarios involving communicating medical devices and applications. [Work in progress]

While the effort is being pursued in the space of communicating medical devices and applications, the patterns are applicable to other domains that involve heterogeneous communicating entities.   

This effort is being pursued in the context of Medical Device Coordination Framework (MDCF), a project exploring techniques to enable Medical Application Platforms (MAP).  MDCF provides a prototype implementation of Integrated Clinical Environment (ICE), an architecture to realize MAP.

In aircraft industry, after labour and fuel costs, maintenance costs are the third largest expense item for both regional and national carriers. By implementing IVHM technologies not only the maintenance costs can be reduced, also it can provide more specific scheduled maintenance, on-board diagnostics and prognostics services. Maintenance department can be notified about the fault in advance and can arrange for components while aircraft is in mid-air. IVHM technologies minimize the physical diagnostics costs and provide more realistic condition based maintenance (CBM). The aim of this project is to investigate, using simulation and optimization, how IVHM network architecture can be built and implemented in aircraft (or IVHM applications), to support interoperability between multiple vendors’ IVHM components and insertion of new IVHM capabilities. IVHM consists of subsystems, sensors, model based reasoning systems for subsystem and system level managers, diagnostic and prognostics software for subsystems. In IVHM systems, usually there is large amount of data (collected from sensors), which needs to be delivered to right places at the right time so communication paradigm is the first and very essential design consideration which impacts many key properties such as scalability, reliability, availability, timeliness and configuration of overall system. The OSA-CBM (Open System Architecture for Condition Based Maintenance) defines an open architecture for moving information in a condition-based maintenance system. Typically, companies developing condition-based maintenance systems must develop software and hardware components, in addition a framework for these components to integrate. OSA-CBM is a standard architecture and framework for implementing condition-based maintenance systems. It not only describes the six functional blocks of condition based maintenance systems but also the interfaces to establish communication.