Medical devices are considered as data publishers. A topic is the device name and
for each device, a subscriber is created to listen to the published data and save it in a
local database with the required parameters. The main component of the gateway is an
embedded configuration service that provides medical staff with the ability to log into
and configure the data process behavior depending on patients’ situations. Medical staff
can configure publishers and subscribers by providing information such as the ID of the
devices, the references of the patients and the corresponding dates of hospitalization.
b) The virtual sensor
It is a software component that has three main roles. First, it saves the received data as
significant information in the local database. Second, it calculates the score of the data
depending on its type and using the predefined intervals of the NEWS2 approach. In
case of problem detection with the calculated score or data interruption, the virtual
sensor publishes a notification to the local broker. Added to that, each virtual sensor is
subscribed to a configuration topic in order to receive the requested interval of saving
data in the local database. To ensure the privacy of the patient information, the virtual
sensor does not store the patients’ details such as their names or their ages. It stores
only the references of patients associated with the devices’ numbers and the corresponding range time of data collection.
c) Scores manager
The scores manager is a software component that receive calculated scores from all the
virtual sensors. It calculates the global score of each patient and evaluates its risk level.
The calculated scores are saved in the local database and they are sent regularly to the
hospital server for long term storage. In case of high score detection, the scores
manager keep publishing significant notifications to the local broker until it receives a
validation of the medical staff intervention.
d) Configuration manager
The configuration manager is in an intermediate position between the hospital server
and the virtual sensors. It initializes each new virtual sensor with the corresponding
configuration. The configuration manager of each gateway is considered as a subscriber
to the corresponding configuration topic defined at the Hospital server.
3.3 Methods
The main objective of our solution is to provide intelligent methods of patient control.
Two types of configuration are supported by the configuration manager:
• Devices configuration
The medical staff can submit a configuration request using a web interface, the
server broker publish the received request as a configuration message to the concerned
gateway. If the request is about adding a new device, a new virtual sensor is created
after validation. In case that the medical staff choose to modify some parameters of an
existing device, the corresponding virtual sensor checks the different inserted parameters: device identifier, patient reference and the time range of saving data and save the
22
I. Ben Ida et al.
for each device, a subscriber is created to listen to the published data and save it in a
local database with the required parameters. The main component of the gateway is an
embedded configuration service that provides medical staff with the ability to log into
and configure the data process behavior depending on patients’ situations. Medical staff
can configure publishers and subscribers by providing information such as the ID of the
devices, the references of the patients and the corresponding dates of hospitalization.
b) The virtual sensor
It is a software component that has three main roles. First, it saves the received data as
significant information in the local database. Second, it calculates the score of the data
depending on its type and using the predefined intervals of the NEWS2 approach. In
case of problem detection with the calculated score or data interruption, the virtual
sensor publishes a notification to the local broker. Added to that, each virtual sensor is
subscribed to a configuration topic in order to receive the requested interval of saving
data in the local database. To ensure the privacy of the patient information, the virtual
sensor does not store the patients’ details such as their names or their ages. It stores
only the references of patients associated with the devices’ numbers and the corresponding range time of data collection.
c) Scores manager
The scores manager is a software component that receive calculated scores from all the
virtual sensors. It calculates the global score of each patient and evaluates its risk level.
The calculated scores are saved in the local database and they are sent regularly to the
hospital server for long term storage. In case of high score detection, the scores
manager keep publishing significant notifications to the local broker until it receives a
validation of the medical staff intervention.
d) Configuration manager
The configuration manager is in an intermediate position between the hospital server
and the virtual sensors. It initializes each new virtual sensor with the corresponding
configuration. The configuration manager of each gateway is considered as a subscriber
to the corresponding configuration topic defined at the Hospital server.
3.3 Methods
The main objective of our solution is to provide intelligent methods of patient control.
Two types of configuration are supported by the configuration manager:
• Devices configuration
The medical staff can submit a configuration request using a web interface, the
server broker publish the received request as a configuration message to the concerned
gateway. If the request is about adding a new device, a new virtual sensor is created
after validation. In case that the medical staff choose to modify some parameters of an
existing device, the corresponding virtual sensor checks the different inserted parameters: device identifier, patient reference and the time range of saving data and save the
22
I. Ben Ida et al.