It is rumored that some day Philips (on-going), will be coming out with a 802.11 (based), b/a or maybe n telemetry system. Where does this place WMTS? Legacy. When I go to the Philips web site and read about IntelliVue Telemetry and 802.11 Infrastructure, I scratch my head a bit.
– IntelliVue 802.11 Infrastructure. "It is not designed for use with or near other 802.11 networks that use the same spectrum. For example, enterprise 802.11b/g networks can be used in the same space when the Philips infrastructure is set to use 80211a (5 GHz)" – This simply means that you have to install a "separate" infrastructure just for bedside and transport monitoring..yes? Why cannot you use 802.1q trunking and make this a part of the enterprise and save costs?
Philips is offering now it seems 1.4 Ghz (higher band), of WMTS and 2.4 GHz (ISM), however this is proprietary "smart hopping" technology. But it seems that you could by their statement run both telemetry and portable monitoring patient monitoring on this network too. I guess the only reason you would want 2.4GHz "Smart Hopping" is if you desire to expand telemetry coverage up to 1,028 patients. But this totally different than the previous 802.11a infrastructure. (Note they mentioned 2.4GHz (ISM), but not the 802.11b/g/n, IEEE protocol)
In today's healthcare economic climate it seems that Philips is saying no to "any" ability to share an enterprise network. This simply means "dedicated" switches and 802.11 infrastructure for portable monitoring and dedicated either WMTS or proprietary 2.4GHz infrastructure additionally for telemetry.
The way I read this is as follows:
1. 802.11a/b/g/n for enteprise data and voice over IP, video etc.
2. Entirely separate 802.11a network for portable monitoring
3. Entirely separate 1.4Ghz or 2.4Ghz infrastructure for telemetry monitoring
In 2010 hospitals are desiring house wide coverage for telemetry and portable monitoring. This allows for flexibility in monitoring patients from the ER, dialysis, orthopedics you name it. The "traditional' step-down unit for "telemetry", is now pretty much house wide. Having multiple infrastructure(s), to accomplish this gets "very expensive"
I guess as the market leader they can convince customers that they have all this "separate" infrastructure, however in 2010 with proper network design and enterprise grade components, "proprietary networks" are really no longer needed. John Chambers CEO of Cisco Systems even commented in 2006 at HIMSS in his key note, that "proprietary networks are history".
Would like to see people chime in here and give their opinions.
Do you know of any hospitals that are currently using the philips intellivue m4841a trx telemetry transceivers but want to get rid of them or are in the process of getting rid of them (ie: sell their unwanted equipment)?
Yes