You Are Here:

Community: Blogs

Arto Holopainen's Forum Nokia Blog

Connectivity with medical POC devices, background

ahoccc | 13 June, 2006 08:23

Bluetooth has finally found its way to medical devices as well (especially POC, Point-Of-Care). There are still lot of measurement devices out that just gives the measurement result to the device screen, no connections to outside world whatsoever. Then majority of devices that has output connections uses serial communication, either using RS-232 or serial-to-USB conversion. Minority of connectable devices uses Bluetooth, infrared or other wireless communication channel. However it seems that Bluetooth has got manufacturers’ interest since new medical measurement devices with Bluetooth are coming. Even Bluetooth SIG has special medical devices working group.

 

Even though medical devices are bound by very strict regulations it is quite surprising to notice the variations between Bluetooth implementations between devices. First of all what comes to my mind when talking about medical device and Bluetooth is security. Health care sector and medical industry have always been very straightforward with the security issues when it comes to dealing electronic patient records. So, personally I would take granted that medical devices uses the highest Bluetooth security level (level 3), but that’s not the real world case. For example, there are devices as follows:

 
  • devices without any kind of security
  • devices with fixed PINs like 0000 and 1234
  • devices that has PIN code hard coded to its friendly name like MEAS_DEVICE_123456
  • devices that blindly tries to find first available Bluetooth SPP service around and then tries to send information to that service

The common thing for all the above cases in my opinion is the attempt to ease the device users work e.g. by bypassing Bluetooth paring process so that the user does not have to input the actual PIN code.  This is very awkward when comparing to other health care security regulations regarding electronic patient data. For some cases this kind of solutions might be suitable, e.g. for cases where there is some kind of dedicated “black box” whose only job is to listen and collect data from specific devices. But when these measurement devices are used with Symbian, developers have to think twice before implementing working connectors.

 

Stay tuned for more…

 

Find more related topics in my blogs here.

RSSComments

Re: Connectivity with medical POC devices, background

coultonp | 14/06/2006, 13:07

coultonp Arto

Thanks for another very interesting blog. This is outside my area(seem to keep saying that lately) but isn’t there an argument to say that the measurement data only really becomes sensitive once it has been tied to a particular patient which I would assume would be post the Bluetooth connection. If the argument is that a potential backdoor is being left open could that not be solved by having a register of Bluetooth addresses.
As an aside what are the regulations with regard to the interference from wireless devices in hospitals?

Re: Connectivity with medical POC devices, background

kevinadmin | 15/06/2006, 00:20

Paul,

Like most things governmental and all things electromagnetic, "the regulations" that apply are less than clear cut. The good news is that, at least in the US, government regulations on electromagnetic compatibility in health care settings recognize that it's an engineering process that can't possibly be codified by a legislative body.

Here is the guideline from the US Food and Drug Administration/Center for Devices and Radiological Health (no kidding -- that's their name): http://www.fda.gov/cdrh/emc/emc-in-hcf.html

The Mobile Health Care Alliance has an interesting overview of international standards here.: http://www.mohca.org/presentations/JimConrad.ppt

Re: Connectivity with medical POC devices, background

ahoccc | 15/06/2006, 00:22

ahoccc Paul,

Your argument is correct that most likely there is no patient data stored in measurement device. And if someone gets somehow the information, it cannot be tied to certain person just by looking the values. Information stealing gets even more difficult when measurement devices have Bluetooth active only when ready to transfer. Also the use of proprietary communication protocol is effective way to block unwanted data collection. Perhaps I’m little paranoid about this but I’ll still emphasize that if there is an easy backdoor like this, someone can and will use it. Perhaps this is not a big problem today but when Bluetooth medical devices, especially those that people are carrying along, will become more common this will pop up.

This kind of backdoor could be easily blocked as you mentioned by storing paired device to the medical device memory and allow connections only with that device. I totally agree with you but reality is that this is not used. Why? Perhaps because the most of current medical measurement device Bluetooth implementations are just serial cable replacements to existing devices and nobody has paid any attention how Bluetooth device should actually work.

About interference inside hospitals, it could be summarised as in study done in 2001 (www.chatterboxsoftware.com/MedReport.htm):

“Until recently (1/9/2001), the standard for EMC, IEC 60601-1-2 (8), was only specified for electromagnetic waves up to 1 GHz. This means that no electronic medical devices used in hospitals today are tested for disturbances of higher electromagnetic frequencies. It is therefore necessary to do clinical studies of new wireless communications technologies using higher frequencies than 1 GHz, such as General Packet Radio Service (GPRS), Bluetooth, Wireless Local Area Network (WLAN), and Universal Mobile Telecommunications System.”

In that study no interference were found. Surely there might be still some medical devices that take disturbance with higher frequency communication like Bluetooth. Anyway nowadays Bluetooth is quite well approved inside hospital. There are even some cases where Bluetooth hotspots are used to relay connections for longer distances (quite similarly as WiFi hotspots works).

I hope you get something out of my reasoning... Keep up commenting!

Re: Connectivity with medical POC devices, background

coultonp | 15/06/2006, 04:15

coultonp Arto

Thanks for the information its all very interesting and as you say gratifying that the process in being viewed from the engineering perspective. I am interested to see Bluetooth Hotspots are being used I have always though that there was an obvious potential there and did some work in this are but was disappointed when the PAN profile disappeared of a lot of the phones.

Re: Connectivity with medical POC devices, background

adebam | 23/06/2006, 20:15

Hi Arto

I share your view that not much attention has been paid to how Bluetooth medical devices should work in practice.

Part of the problem is that Bluetooth in medical devices implies a mass market for personal use medical devices - eHealth for the masses. Here, we need to consider a wide range of use case scenarios that meet the needs of patients, health care service providers and carers. I am pretty sure that issues relating to device management, device sharing amongst patients and ease with which devices can be linked to other communication protocols and devices will rank along side device paring and securty of data as the issues that need to be solved before Bluetooth medical devices enjoys mass market acceptance.

So whilst the new Bluetooth Medical Device SIG will help focus and clarify the technical standards as far as Bluetooth implementation in devices goes, business process, workflows and technology integration are still the issues that need to be solved.

Ade Bamgboye, Wireless Matters, UK
You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fartoE2dholopainensE2dforumE2dnokiaE2dblogE2f2006E2f06E2f16E2fconnectivityE2dwithE2dmedicalE2dpocE2ddevicesE2dbluejackingX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxArtoE20HolopainenE27sE20ForumE20NokiaE20BlogE20E7cE20ConnectivityE20withE20medicalE20POCE20devicesE2cE20bluejackingE3fX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUqfnTopicZconnectivityQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZcppQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZenterpriseQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZupdatedQDx2006E2d06E2d16X qfnZuserE5ftagQSxconnectivityX qfnZuserE5ftagQSxenterpriseX qfnZuserE5ftagQSxsymbianE2dcE2bE2bX qmarsZdescriptionQSxSpecialistE20withE20healthcareE20andE20mobileE20workforceE20E28enterpriseE29E20relatedE20mobileE20solutionsE2eE20ahocccE20E7cE2016E20JuneE2cE202006E2000E3a52E20WhatE20doesE20bluejackingE20toE20doE20withE20medicalE20measurementE20devicesE3fE20Ea0E20E4cetE92sE20takeE20closerE20lookE20forE20theE20caseE20whereE20measurementE20deviceE20isE20activeE20inE20creatingE20connectionE20toE20otherE20deviceE20toE20deliverE20measurementE20resultsE2eE20InE20thisE20caseE20deviceE20functioningE20isE20asE20followsE3aAfterE20personE20hasE20takenE20measurementE20deviceE20activatesE20BluetoothE20communicationE20automaticallyE20E28personE20canE20notE20affectE20toE20thisE29E2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ