【正文】 rchitecture consists of a Wireless Personal Area Network (WPAN) and a Local Area Network. The WPAN implemented as a Zigbee work municates with the LAN via a gateway. This gateway also serves as the WPAN coordinator which is responsible for forming the work. Each medical device has a Zigbee node attached(MDI) which enables data to be transmitted wirelessly to the Gateway and then onto a Server existing on the LAN. See Fig. 1 below for a graphical representation of this. When an MDI is powered on it automatically joins the work and makes itself known to the Server. A user can then associate this device with a patient using a GUI client. Once an association has been pleted the MDI will be notified to begin transmitting data. Data received by the server will be stored in the Electronic Health Record (EHR) for that patient and displayed on any GUI Client that is subscribed. Figure 1. HighLevel Architecture B. Medical Device Interface The diagram in Fig. 2 below shows the key ponents of the MDI. The hardware prises of a Zigbee module, a microcontroller and an RS 232 Interface. The microcontroller is responsible for interfacing with both the RS232 Interface and the Zigbee module. Figure 2. MDI Block Diagram When the MDI is powered on, the Zigbee stack will automatically join a Zigbee work within range. Next the MDI will announce an ID which is also visible on the external surface of the device. This is done using a protocol we designed for this project. The protocol supports these types of status messages in addition to supporting the actual real data we are interested in. At this point it is possible to make an association with the MDI. To achieve this, the administrator selects the ID from an automatically generated list on screen, a patient demographic and a type of medical device which is supported in the system. This process results in the server sending the correct RS232 settings to the MDI for the medical device that it is connected to. Now that the system can municate directly with the medical device the server will send any necessary mands to initiate a data stream from the device. C. Server Functionality The server is responsible for decoding specific medical device data. This functionality is implemented in a DLL (Dynamic Link Library) that is run on the server. There is one DLL for each type of medical device the system supports which allows for future medical devices to be supported without upgrading the server software. Any future device can easily be supported within the DLL framework by simply inheriting from the appropriate class for that particular type of device. These DLLs are loaded at runtime and have a standard interface that each designer must adhere to in order to interoperate with the system. A designer must also plete an XML file from a template to indicate which features the new medical device supports. The DLL only handles device specific information。 在這樣的背景下，我們討論怎樣使“紫蜂”技術(shù)滿足我們對于寬帶，能源，安全性和移動性的要求。這些設(shè)備 還可以共享無線電資源，通過其他形式正在開發(fā)的傳感器，來結(jié)合到此項(xiàng)目，例如無線電心電圖和脈沖血氧測定傳感器。這樣就會使整合這些設(shè)備到一個信號網(wǎng)絡(luò)變得困難。一旦這些設(shè)備是可以聯(lián)網(wǎng)的，他們也能夠在同一環(huán)境中使用其他的基礎(chǔ)設(shè)施類似無線電傳感器。類似的固件可以保持通用而且任何特定的設(shè)備通信協(xié)議能夠在服務(wù)器上網(wǎng)絡(luò)上的后端得到執(zhí)行。目前正在進(jìn)行的有關(guān)病人監(jiān)護(hù)儀的工作，例如使用無線傳感器如“ CodeBlue ”項(xiàng)目在哈佛大學(xué) [ 3 ] 開展。使用無線傳感器網(wǎng)絡(luò)在醫(yī)院進(jìn)行了廣泛的審查。 ZigBee 的自我形成和自我調(diào)整的網(wǎng)絡(luò)架構(gòu)讓數(shù)據(jù)和控制信息從一個節(jié)點(diǎn)傳輸?shù)搅硪粋€多個路徑。離線節(jié)點(diǎn)可以連接到一個網(wǎng)絡(luò)中的大約 30 毫秒。這一點(diǎn)尤其重要，在醫(yī)療環(huán)境中，病人往往是在輪椅上移動的時候仍然被連接到醫(yī)療設(shè)備。 D 器件參數(shù) 可以在呼吸機(jī)進(jìn)行典型的讀數(shù)如吸氣潮氣量，呼氣潮氣量，氧氣濃度， 呼吸速率，峰值壓力，過期每分通氣量和平均氣道壓。這些都是呼吸速率，無創(chuàng)血壓，血氧飽和度和溫度。 E 帶寬 我們分析了支持所有上述呼吸參數(shù)的 Maquet ServoI，發(fā)現(xiàn)已達(dá)到完善的目的。 F 可測量性 通風(fēng)設(shè)備，擁有最多的裝置參數(shù)研究，需要最多帶寬。所有這些設(shè)備都自己建造的報警機(jī)制 。 A1 分鐘的間隔是一個典型的價值，然而即使他們被需要的數(shù)據(jù)每隔幾秒鐘，很明顯網(wǎng)絡(luò)仍可以支持大量的設(shè)備。每個醫(yī)療設(shè)備有一個附加的ZigBee 節(jié)點(diǎn)（磁航向指示器），使數(shù)據(jù)傳送無線網(wǎng)關(guān)，然后到一個服務(wù)器上的現(xiàn)有局域網(wǎng)。一旦協(xié)會已經(jīng)被完成 MDI 將通知開始傳輸數(shù)據(jù)。微 控制器負(fù)責(zé)為 RS232 接口和 ZigBee 模塊接口。該協(xié)議支持這些狀態(tài)消息的類型除了支持我們感興趣的實(shí)際的真實(shí)數(shù)據(jù)?，F(xiàn)在，該系統(tǒng)能直接與醫(yī)療設(shè)備通信服務(wù)器將發(fā)出任何必要的命令，以從裝置中啟動一個數(shù)據(jù)流。今后的任何設(shè)備可以很容易被支持在 DLL 框架內(nèi)通過簡單繼承相應(yīng)的類為特定類型的設(shè)備。主要的服務(wù)器應(yīng)用程序從我們的項(xiàng)目協(xié)議解碼本信息。圖 3 段顯示的動態(tài)圖代表一個事件序列圍繞這一計時器到期的 DLL 中的呼吸機(jī)。 當(dāng)醫(yī)療設(shè)備返回一個響應(yīng)服務(wù)器應(yīng)用這些數(shù)據(jù)傳遞到 DLL 上所示。最后 DLL 會提高另一種情況，本次說明該圖形數(shù)據(jù)是可用的。為此目的我們連接 MDI 到 PC 模擬器設(shè)計作為 Maquet 伺服系統(tǒng)呼吸器。圖 6 顯示在運(yùn)行時間模擬器處理這些命令 圖 6 呼吸機(jī)模擬器 像架構(gòu)中描述的服務(wù)器 DLL 保持一種狀態(tài)為每個終 端設(shè)備，以便它知道什么信息預(yù)期的回報。這些結(jié)果是非常確切的先于在醫(yī)院用實(shí)際呼吸機(jī)的可用性測試之前。初步結(jié)果 是確切的，但進(jìn)一步深入測試是需要在醫(yī)院的環(huán)境中進(jìn)行的。此外，我們有基礎(chǔ)設(shè)施使我們能夠很容易地提供新的設(shè)備系統(tǒng)內(nèi)的需