Implementing and Validating an Environmental and ... - IEEE Xplore

29 downloads 0 Views 948KB Size Report
Lawrence, Don Martin. Faculty of IT, University of Technology Sydney. PO box 123, Broadway 2007 NSW, Australia. E-mails: messina|[email protected].
Fifth International Conference on Information Technology: New Generations

Implementing and Validating an Environmental and Health Monitoring System Marco Messina, Yen Yang Lim, Elaine Lawrence, Don Martin Faculty of IT, University of Technology Sydney PO box 123, Broadway 2007 NSW, Australia E-mails: messina|[email protected] brian.lim\[email protected]

Frank Kargl Institute of Media Informatics, Ulm University, 89069 Ulm, Germany E-mail: [email protected]

integrated with the commonly used Mica2, MicaZ and Telos motes. In our architecture, we deploy MicaZ motes as wireless nodes, BCI pulse oximeters as medical sensor boards, the same used by the CodeBlue project, and MTS310 sensor boards as environmental sensors. These sensors collect the patients’ data and transmit them to local medical databases containing medical records or to a remote healthcare server. To address these requirements, the CodeBlue protocol and middleware framework implemented in TinyOS [13] offers protocols for device discovery, publish/subscribe multihop routing and an easy-to-use graphical user interface (GUI) which enables medical staff to request data from individuals or groups of patients. In this paper we describe the design and implementation of enhancements to the CodeBlue software and hardware. Our effort focused on two aspects: the wireless sensor network side by integrating environmental sensors that were previously not supported by the CodeBlue platform, in order to set up a combined environmental and medical monitoring system; and, on the backend side of the architecture, by implementing an SNMP-proxy connection in order to make the data easily available. The rest of this paper is structured as follows: the next section describes in detail the health monitoring system architecture. Section III reports on the series of scenarios tested on the system in the laboratory. In this section the system is evaluated and validated according to the analysis of the data collected during the laboratory testing. Finally, Section IV offers some concluding thoughts and future enhancements of the architecture.

Abstract In this paper the authors describe the implementation and validation of a prototype of an environmental and health monitoring system based on a Wireless Sensor Network (WSN). The solution proposed for our system combines environmental and medical sensors in order to monitor both the surrounding area of the patient and the patient’s health status simultaneously. This feature would allow a comprehensive understanding of the patient’s condition by the specialist caring for the subject. Another key feature of the system is the development of an architecture which provides an easy, viable, cheap and effective way for connecting our environmental and medical sensor network of MicaZ motes to the outside world using Simple Network Management Protocol (SNMP) version 3. A series of experimental scenarios were developed and implemented in a laboratory setting; firstly for evaluating the reactivity of the monitoring system to changes and secondly for understanding the reliability of the data obtained for benchmarking purposes. The conclusion considers the implementation of future improvements to the health monitoring network by introducing new sensors and location tracking capabilities, and by integrating alarm triggering algorithms and advanced security techniques.

Key words- Medical sensor networks, CodeBlue, SNMP, health monitoring.

1. Introduction The health sector is currently one of the most attractive targets for Wireless Sensor Network (WSN) applications. A health monitoring application, for example, allows health professionals (doctors, nurses, etc.) in a hospital or clinic to constantly monitor patients fitted with tiny, wearable sensors capable of collecting sensitive, vital health information in real-time. In this context, the most recent and perhaps the most promising complete proposal, is the CodeBlue prototype medical sensor network platform [8]. CodeBlue utilizes a range of medical sensors

978-0-7695-3099-4/08 $25.00 © 2008 IEEE DOI 10.1109/ITNG.2008.119

2. Architecture 2.1. Overview The architecture of the health monitoring system, as displayed in Figure 1, comprises the WSN connected via a gateway mote to the gateway PC. The motes are equipped with medical and/or environmental sensors. The sensor

995 994

network transmits gathered data via the CodeBlue protocol [4] to the gateway mote, which redirects the data to the local host for a first data analysis. On the Gateway-PC, the CodeBlue GUI displays the gathered data, the network topology and the Mote-equipped patients (see Figure 3). The data is stored in log files and made available to remote systems via an SNMP-proxy. Using only logfiles, we are even able to replay earlier experiments to SNMP clients in order to test our system when no patients are available.

involved in developing tools or systems for patient monitoring based on WSNs. Examples include the Advanced Health and Disaster Aid Network (AID-N) from Johns Hopkins University for improving the way to provide emergency care in prehospital situations. Electronic triage tags with sensors continuously monitor the vital signs and locations of patients until they are admitted to a hospital (VitalMote Technology) [6]. The department of Computer Science, University of Virginia is developing AlarmNet, an architecture for smart healthcare, continuous monitoring of assisted-living and independent-living residents based on mote technology [1]. Other examples include BigNurse [2] or the Motecare system [9]. Finally, Harvard University has devleoped CodeBlue, a platform based on mote sensors network technology useful for a range of medical applications, including pre-hospital and in-hospital emergency care, disaster response, and stroke patient rehabilitation [10]. This is the platform we adopted for our prototype. The system is based on MicaZ motes. The medical sensors adopted were pulse oximeter sensors from BCI, Inc. (see Figure 2). The device consists of a standard finger or ear sensor, a pulse oximetry module (BCI Micro Power Oximeter board) and a mote. The pulse oximeter module has a serial interface that relays SpO2 (blood oxygen saturation), pulse, and plethysmogram waveform data to the MicaZ node. The pulse oximeter mote device periodically transmits packets containing the measured samples. For environment sensors we used the MTS310CA which is a flexible sensor board with a variety of sensing modalities. In our system we deployed light and temperature sensors, which were integrated into the CodeBlue system.

Figure 1. WSN Health Monitoring Architecture We argue that our design has two significant advantages: first, introducing environmental sensors that collect context information will help in analysis of the medical data. When, e.g., a patient is doing sports, medical parameters like heart rate or O2 saturation have to be interpreted differently compared to the same person sleeping in bed. Second, making available the data via SNMP allows us to use existing network management tools with only slight modifications for medical monitoring. In essence, patient monitoring and network monitoring is not too different. It is all about collecting period data samples (like link usage or heart rate) from a large number of entities (like switches or patients), interpreting this data, triggering alarms or predicting trends. Using SNMP, one monitoring and analysis station can supervise a large number of sensor networks from a central place.

Figure 2. Pulse oximeter device [1]

2.3. CodeBlue Enhancements

2.2. Wireless Sensor Network

We extended the CodeBlue system so that motes were able to collect light and temperature values and transmit them as additional channels to the CodeBlue GUI, where this data can be displayed in addition to the medical values. The screen shot in Figure 3 shows on the left hand side the improvements added to the basic version of the

Key WSN devices in the remote healthcare monitoring domain are tiny battery-powered sensors called Motes. There are a variety of mote designs, e.g. the Mica motes from University of California, Berkeley. Motes organize themselves into a wireless network, sharing data with one another and with computers, embedded devices, or PDAs. Already, a number of commercial and research groups are

995 996

CodeBlue GUI. Patient #102 is able to collect environmental data, namely light and temperature readings. On the right hand side of the GUI temperature and light graphs have been added. The topology on the center right side remains the same; it shows the base station with a red cross and the two patients sensors forming a wireless sensor network. The diagnostic panel at the bottom left is used mainly for debugging purposes.

SNMP allows for multiple agents (devices) to talk to multiple managers. This allowed us to have multiple managers polling the Gateway-PC for the required information without increasing the load on the WSN side. Besides, SNMPv3 supports encryption and provides endto-end point security [6, 3].

2.5. SNMP Clients Each agent in an SNMP-managed network maintains a local database of information relevant to network management, known as the management information base (MIB). An SNMP-compliant MIB contains definitions and information about the properties of managed resources and the services that the agents support. The manageable features of resources, as defined in an SNMP-compliant MIB, are called managed objects or management variables (or just objects or variables) [12]. Each object in the MIB has an object identifier (OID), which the management station uses to request the object's value from the agent. An OID is a sequence of integers that uniquely identifies a managed object by defining a path to that object through a tree-like structure called the OID tree or registration tree. When an SNMP agent needs to access a specific managed object, it traverses the OID tree to find the object [12]. We plan to define an own range of OIDs for representing medical values. A MIB browser is a simple SNMP client allowing viewing of the hierarchical tree of the SNMP MIB variables and displaying them as values or graphs. Figure 4 shows the graphical view of the light sensor.

Figure 3. Screen Shot of CodeBlue showing environmental data The sensor data collected by the network and shown in the GUI is stored continuously in log files. The log file stores records consisting of a time stamp, the patient and sensor ID, and the sensor value:

Suggest Documents