Study of Middleware for IoHT and Their Applications
227
to interact with a changing set of wireless nodes in a medical environment. The
proposed middleware has the ability to multiplex the received data from the
various sensors in order to fit multiple applications simultaneously.
The contribution has been applied in three applications. The first is the
fitness support in which the user’s physical activity is tracked by dedicated
sensors: a wearable accelerometer to track the user’s status (walking, sitting,
standing etc.) and a chest strap and two embedded sensors in the weightlifting
gloves to figure out the user’s body exercise. This application motivates the
user and helps him to track his sports activities. The second application is the
telemonitoring. The main objective of this application is to monitor remotely
the patient’s status. To this end, the middleware collects information about the
patient’s weight, pressure, heart rate, ECG, etc. When the heart rate of the
patient is not suitable (abnormal) to his activities, an alarm is sent. The third
application is elderly care that monitors the elderly daily activities and reminds
him whenever he forgets an important task.
2.6 Message Oriented Middleware (MoM)
Message oriented middleware have the ability to exchange important number of
messages between distributed applications. A MoM in [21] is proposed to unify
the access to all the medical devices in order to ease the data collection from
the patients to the doctors. To this end, “Advanced Message Queuing Protocol
(AMQP)” is employed to ensure data transfer according predefined standards
with the required interoperability. To increase the security of the middleware,
a RESTful application has been added to verify which manager is allowed to
access which data.
2.7 Real Time Publish Subscribe Based Middleware
The Real-Time Publish Subscribe (RTPS) middleware is well suited for the
real-time distributed applications. That’s why authors in [19] decided to port
this middleware to healthcare. In this middleware, each medical device such
as temperature probe, Capnometer, ElectroCardiogram, has the function of a
publisher. It collects and publishes the patient’s measurements via fast Ethernet
LAN. The published information is sent to the corresponding subscribers.
3 Discussion
As we have stated in the previous sections, the middleware for healthcare of
things have covered lot of healthcare domains. Table 1 gives an overview of these
middleware, their applications and their required medical devices (NM means
not mentioned in the related paper). We notice that a same application can be
ensured in many cases by different middleware belonging to different classes. For
example, patients monitoring applications are implemented using SOA-based or
Event-driven or Web of things or Publish/subscribe middleware. There are also
227
to interact with a changing set of wireless nodes in a medical environment. The
proposed middleware has the ability to multiplex the received data from the
various sensors in order to fit multiple applications simultaneously.
The contribution has been applied in three applications. The first is the
fitness support in which the user’s physical activity is tracked by dedicated
sensors: a wearable accelerometer to track the user’s status (walking, sitting,
standing etc.) and a chest strap and two embedded sensors in the weightlifting
gloves to figure out the user’s body exercise. This application motivates the
user and helps him to track his sports activities. The second application is the
telemonitoring. The main objective of this application is to monitor remotely
the patient’s status. To this end, the middleware collects information about the
patient’s weight, pressure, heart rate, ECG, etc. When the heart rate of the
patient is not suitable (abnormal) to his activities, an alarm is sent. The third
application is elderly care that monitors the elderly daily activities and reminds
him whenever he forgets an important task.
2.6 Message Oriented Middleware (MoM)
Message oriented middleware have the ability to exchange important number of
messages between distributed applications. A MoM in [21] is proposed to unify
the access to all the medical devices in order to ease the data collection from
the patients to the doctors. To this end, “Advanced Message Queuing Protocol
(AMQP)” is employed to ensure data transfer according predefined standards
with the required interoperability. To increase the security of the middleware,
a RESTful application has been added to verify which manager is allowed to
access which data.
2.7 Real Time Publish Subscribe Based Middleware
The Real-Time Publish Subscribe (RTPS) middleware is well suited for the
real-time distributed applications. That’s why authors in [19] decided to port
this middleware to healthcare. In this middleware, each medical device such
as temperature probe, Capnometer, ElectroCardiogram, has the function of a
publisher. It collects and publishes the patient’s measurements via fast Ethernet
LAN. The published information is sent to the corresponding subscribers.
3 Discussion
As we have stated in the previous sections, the middleware for healthcare of
things have covered lot of healthcare domains. Table 1 gives an overview of these
middleware, their applications and their required medical devices (NM means
not mentioned in the related paper). We notice that a same application can be
ensured in many cases by different middleware belonging to different classes. For
example, patients monitoring applications are implemented using SOA-based or
Event-driven or Web of things or Publish/subscribe middleware. There are also