doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 1 Communication requirements from IEEE 1073 Bin Zhen, Huan-band Li and Ryuji Kohno National Institute of Information and Communications Technology (NICT)

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 2 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [Communication requirements from IEEE 1073] Date Submitted: [May, 2007] Source: [Bin Zhen, Huan-Bang Li and Ryuji Kohno] Company [National Institute of Information and Communications Technology (NICT)] Contact: Bin Zhen Voice:[ , Abstract: [Introduction to IEEE 1073] Purpose: [To provide medical requirements for BAN] Notice:This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 3 Motivations Better understand medical applications Medical requirements from upper layers

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 4 Needs for IEEE 1073 Point-of-care medical device communication standards To make sure the connectivity among medical devices –Otherwise, it may leave open to question the accuracy and completeness of a patient record Better diagnosis, care and treatment –Without electronic capture of data and events associated with an episode of care, trending and other sophisticated data analyses are effectively impossible. Less medical error IEEE 802.x standards are inadequate to fully address the needs at the patient bedside

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 5 IEEE 1073 Medical Information Bus (MIB) –between bedside medical device associated with a patient –between bedside environment and a patient care information system

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 6 Medical device communication model Medical device system Medical device data language Patient care system Device communications controller Bedside communications controller BCC DCC MDS BCC MDS DCC PCS

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 7 Layer model of IEEE 1073 Application presentation Session Transport Network Data link Physical base – layer standard Medical device data language Device application profile Transport profile ISO model P P x P x P x

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 8 Approved 1073 standards Health informatics - Point-of-care medical device communication –Nomenclature (2004) –Domain information model (2004) –Application profile - base standards (2004) –Transport profile - cable connected (2004) –Transport profile – infrared wireless (2004) Only wired connections has standardized

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 9 Unapproved drafts Health informatics - Point-of-care medical device communication –Guidelines for the use of RF wireless technology –Medical Device Data Language (MDDL) Virtual Medical Device, Specialized Capnometer and cardiac Output Some withdrawn standards

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 10 Communication requirements For use in a clinical environment, the transport must be robust, reliable and adaptable to changing conditions Be suitable for a small single-bed systems with a local host at bedside to a lager multi-bed system with hosts and instrument throughout clinical facility A MDS shall be unambiguously associated with a patient Ease of use (“plug it in and walk away”)

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 11 Transport profile: connection mode Data rate –2.4kbps, 9.6kbps, 1000kbps Connection sensing –Link maintenance (?) Interrupt –to allow service request prior to next schedule polling time Flow control –to regulate data communication to insure no data is lost in the case of limited resources Data integrity check Physical layer event Single hop point-point communication (?)

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 12 PHY interfaces Cable connection –RS-232 –irDA

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 13 Summary information IEEE 1073 guarantees the plug-and-play interoperability in upper layers –Until now point-point cable connections have been defined Wireless works are still behind the scene –Data rate required by IEEE 1073 is pretty low –QoS is provided by point-point connection

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 14 IEEE 1073 and SG-MBAN IEEE11073 (ISO TC215 WG7) No wireless connection PHYs –Draft guideline –No power consumption requirement IEEE 1073 profiles are on the upper layer of SG-MBAN standard Enemies of wireless technology in medical bedside environment –Biological effect of long-tern exposure to wireless signal –Coexistence among wireless technologies

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 15 Medical requirement QoS requirement for critical applications –Delay < 300ms Determined by human response time It is not as critical as some real time applications –FER<10 -6 Determined by auto-detection algorithm –Sometimes, data cannot be lost in any condition –Mobility Patient can be in moving Doctors and nurses can walk around patient Part of body can be in moving

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 16 Interference analysis Channel fading –Mobility of device –Environment change Burst background noise –Microwave oven –Other wireless technologies Malicious nodes occupy the channel

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 17 Possible solutions Possible solution in the framework of –Interference and QoS sensing mechanism –Backup channel lists ISM and UWB band Fast switch signaling Dual channel mode –Frequency hopping system + adaptive frequency selection An extreme case SOP and multihop –Fast handover –New QoS mechanism TDMA based superframe? Move to WMTS band Better coexistence framework in UWB –UWB band is in its early phase

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 18 New issues QoS is the first priority –New FEC algorithm –Lack of QoS mechanism in Multi-hop QoS –Battery life and maintenance might be the second one Scalability –GTS and data rate Location ID –Patient is the center role Security –Any new attack? –Any insufficiency in legacy methods?

doc: IEEE ban May/2007 Zhen, Li and KohnoSlide 19 Conclusions Introduction to IEEE 1073 –Medical information bus Communication requirements from IEEE 1073 Possible solutions within IEEE 802 framework