23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Communications in Medical Applications 30-7<br />

30.4.4 Bluetooth<br />

Although requiring more power than IEEE 802.15.4-based <strong>communication</strong>s, Bluetooth has found<br />

applications in ambulatory medical monitoring [23], mobile care alert <strong>systems</strong> [24], and in physiological<br />

monitoring [25]. The ambulatory monitoring solution presented by Zhang and Liu addresses the<br />

replacement of traditional holter <strong>systems</strong> by real-time ones. Traditional holter <strong>systems</strong> store physiological<br />

data in a local memory that is later downloaded onto a PC for diagnosis. This approach endorses the<br />

occurrence of a wide range of errors that can only be detected after downloading the holter data (e.g.,<br />

lead malfunction). As such, the authors propose a monitoring architecture where several patients can<br />

be monitored through the use of Bluetooth-enabled sensors communicating with a PC using Bluetooth<br />

asynchronous connectionless (ACL) links.<br />

Lee et al. put forward a mobile care alert system allowing the monitoring of hypertension and<br />

arrhythmia patients, triggering early warning notifications when abnormal parameters are detected.<br />

This system encompasses a front-end personal mobile device and a back-end care center server. The first<br />

comprises a physiological (blood pressure, pulse, and ECG) parameter extraction Bluetooth-enabled<br />

device and a mobile phone. The second consists of a GSM/GPRS module (able to transmit/receive short<br />

messages) and a PC-based care center host with an Internet connection. The system operates by periodically<br />

sampling physiological signals performing its transmission to a Bluetooth-enabled mobile phone<br />

(device) using the RFCOMM transport protocol, which emulates RS232 serial ports over the (Bluetooth)<br />

L2CAP protocol. Besides uploading the physiological data to a database in the healthcare center server,<br />

the mobile phone uses a simple algorithm to identify abnormal conditions, which result in the transmission<br />

of short messages to the physicians or the other healthcare providers. Abnormal conditions (identified<br />

by professional judgment of the stored information in the healthcare center server) trigger an alarm<br />

to the related personnel, for example, local officers can be instantly informed or an ambulance can be<br />

immediately dispatched to the location of the patient for rescue.<br />

Stojanovic et al. proposed a physiological monitoring system with an architecture comprising<br />

Bluetooth-enabled sensors worn by patients, a Bluetooth access point, and a local server. The major<br />

difference from the system proposed by Lee et al. is that the patient-worn integration device is here<br />

replaced by an access point. As such, if the patient wears multiple Bluetooth-enabled sensors, there will<br />

be multiple RFCOMM links to the access point, which acts as a wireless multiserial server that receives<br />

serial data over the Bluetooth RFCOMM links and packs it in TCP/IP frames that are sent to the local<br />

server and to other remote locations (e.g., hospital), using the Internet, if required.<br />

As suggested by the aforementioned examples, Bluetooth has been identified as a feasible PAN technology<br />

to support medical sensor-based applications. In consequence, the Bluetooth Special Interest<br />

Group (SIG) developed a specific Medical Device Profile (MDP) [26] aimed at expanding the use of the<br />

technology into the medical, health, and fitness markets. The MDP addresses a wide variety of medical<br />

devices (blood pressure meters, weight scales, pulse oximeters, glucose monitors, pulse/heart rate monitors,<br />

etc.), supports multiple data transfer modes (real-time streaming, periodic, episodic, and batch<br />

transfer), and is able to cope with tight synchronization requirements (1.ms). Data <strong>communication</strong>s use<br />

the exchange specifications and the data structures defined by the IEEE 11073 [53] protocol on top of the<br />

MDP layer, thus enabling data sharing between applications and improving interoperability between<br />

medical data endpoints.<br />

30.4.5 IEEE 802.11<br />

The IEEE 802.11 protocol has been widely adopted in wireless LANs addressing home and business<br />

application scenarios. Given its target application domain (power consumption characteristics), it is not<br />

commonly used for supporting small form factor monitoring devices requiring a high level of autonomy.<br />

Nevertheless, there are reported results of using IEEE 802.11 for physiological data collection [27].<br />

However, due to its pervasiveness, it is frequently adopted as the enabling technology for gateways in<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!