JP2015512175A - Medical device remote monitoring system and method - Google Patents

Abstract

A remote monitoring system that monitors multiple medical devices in patient or home care facilities. The system includes a device integration server in communication with the wireless relay module for receiving data packets sent from the medical device, including identifiers and data for each medical device. The system also includes an outbound web server. The web server is configured to provide a web page containing medical device data for display on the first and second remote monitoring devices, subject to authentication of the associated data request sent from the monitoring device. . [Selection] Figure 1

Description

  The present application relates to a remote monitoring system for monitoring a medical device that communicates with a wireless communication network, and more particularly, monitors a medical device that communicates with the wireless communication network via one or more wireless relay modules and the wireless relay network. The present invention relates to a remote monitoring system having a plurality of monitoring devices.

  In emergency medical centers such as hospitals, clinics, and life support centers, and home health care service centers, the time required for interaction between treatment personnel and patients is valuable. Also, the response time of the caregiver for serious health conditions and development may be important. Centralized monitoring systems have been developed to better manage the caregivers' time and patient interactions. In such a system, physiological data from each patient is transmitted to a centralized location. In this concentrated location, one or a few technicians monitor all of this patient information to determine the patient's condition. Information indicating the patient's alarm status can be immediately communicated by the technician and / or system with the on-site treatment personnel, for example via a wireless pager and / or mobile phone and / or by making a voice call throughout the facility. Causes a situation to alert the patient.

  Implementation of such a centralized monitoring system using a wireless network presents many difficulties. In order to effectively monitor patient status using information provided by various medical devices that may be dynamically assigned to patients in many rooms and on many floors in the facility, for example, IEEE 802.11 It would be desirable to establish communication between a medical device and a centralized location using a local area network, such as a standards-based “Wi-Fi” network. However, such networks are usually already deployed in equipment to assist a variety of other functions (eg, physician access to electronic medical records (EMR), equipment management systems, and other functions). As such, it is often undesirable to ensure sufficient local area network access for the purpose of providing centralized monitoring. Also, when a patient is away from a critical care health service center (eg, at home), access to traditional local area network equipment such as a Wi-Fi network is unavailable or assists in the application of critical care monitoring. May not be reliable enough.

  To improve efficiency in centralized monitoring of life-saving emergency centers and home care health service centers, providing one “off-site” centralized monitoring point to monitor several geographically dispersed life-saving emergency health service centers May be desirable.

  As an alternative to traditional Wi-Fi or IEEE 801.11 based local area networks, ZIGBEE networks based on the IEEE 802.15.4 standard for wireless personal area networks have been developed at treatment locations such as pulse oximeters, sphygmomanometers, pulse monitors It has been used to collect information from a variety of medical devices compliant with the IEEE 11073 device specialization for communication of medical devices including scales and blood glucose meters. For example, see ZIGBEE Wireless Sensor Applications for Health, Wellness and Fitness, ZIGBEE Alliance, March 2009. This document is incorporated herein by reference in its entirety. Compared to the current IEEE 802.15.1 Bluetooth® wireless personal area network, for example, a ZIGBEE network can be dynamically configured, for example in a “self-healing” mesh configuration, and low power requirements Provides the advantage of operating on (eg, allowing ZIGBEE transceivers to be connected to a medical device integrally with battery power). However, the transmission range between individual ZIGBEE transceivers is usually limited to a few hundred feet or less. As a result, such networks are suitable for on-site communication with medical devices, but cannot be used for centralized monitoring locations installed off-site.

  Therefore, one or more wireless personal area networks are configured to facilitate on-site communication between the medical device and the one or more wireless relay modules, the one or more wireless relay modules being Off-site centralized monitoring systems and radios such as cellular telephone data networks based on, for example, Pan-European Digital Mobile Telephone (GSM) or Code Division Multiple Access (CDMA) cellular networks or associated wireless data channels A hybrid system may be employed that is further configured to communicate (such as through a wide area network (WWAN)). Such a relay module and system are described in U.S. Patent Application No. 13 / 006,769 entitled “Wireless Relay Module for Remote Monitoring Systems” filed on January 14, 2011, respectively, and January 14, 2011. It is described in related patent applications, such as US patent application Ser. No. 13 / 006,784, entitled “Medical Device Wireless Network Architectures” filed on a daily basis. These documents are hereby incorporated by reference in their entirety.

  In accordance with the applicable patient data privacy provisions of the 1996 Health Insurance Interoperability and Accountability Act (HIPAA), information communication between monitored medical devices and centralized monitoring locations must be secure. Rather, patient information associated with a medical device must be available only to individuals who have the appropriate access authorization and access the centralized monitoring system. To make this feasible, the centralized monitoring system is also able to recognize medical device information indicating alarm conditions that require response by on-site or other professional personnel and to report them in a timely manner. These must be delivered to onsite or professional personnel.

  Accordingly, at each site, communicate with one or more life-saving emergency centers and / or home care health service centers via one or more wireless relay modules through a wide range of wireless networks (eg, wireless wide area networks). It would be desirable to provide a remote, centralized medical information monitoring system. In this communication, a wireless relay module relays communication provided by an on-site medical device through a wireless local area network or a wireless personal area network. It would be further desirable to have a centralized medical information monitoring system that can also configure medical devices according to individual site and patient relevance. The system logs communications from medical devices, displays medical device data to users of a centralized medical information monitoring system that can provide sufficient qualification, recognizes alarm status of medical devices, and identifies these statuses. It is possible to report to responsible personnel in a timely manner.

  The present invention is directed to a remote monitoring system and method for monitoring the status of a plurality of medical devices located remotely from a monitoring system in a patient or home care facility. According to one embodiment of the present invention, one or more medical devices (including but not limited to ventilators, enteral feeding devices, pulse oximeters, sphygmomanometers, pulse meters, scales, blood glucose meters) Are provided in patient care or home care facilities. An interface circuit is connected to each medical device and configured to communicate with one of the plurality of wireless relay modules via the wireless relay network. The wireless relay module may be connected to an internet-accessible wireless communication network, and preferably (eg, Pan-European Digital Mobile Telephone (GSM)) or Code Division Multiple Access (CDMA) cellular network or associated wireless data channel. Further configured to communicate with the remote monitoring device through a wireless wide area network (WWAN) such as a cellular data network. For example, in order to comply with HIPAA regulations, it is desirable to perform communication safely through each of the wireless networks.

  The remote monitoring system and method includes a device integration server in communication with the wireless relay module for receiving data packets sent from the wireless relay module, including information provided by the medical device. This information includes the identification of the associated medical device, may include medical device data, and is preferably transmitted in an encrypted or other secure manner, eg, in compliance with HIPAA's patient data privacy provisions . The information may also include patient identification information that is encrypted or transmitted in some other secure manner. This information may also preferably be encoded in its unencrypted state to avoid any reference to the patient's identity.

  The remote monitoring system includes a data management system including a secure device web server and a device control database and an outbound web server. The data management system is configured to log information provided to the device integration server regarding the medical device. An outbound web server (also referred to herein as a “web server”) is a medical device for display on the first and second remote monitoring devices, subject to authentication of the associated data request generated by the monitoring device. Configured to provide web pages containing data. The second monitoring device may conveniently be for the patient's relatives, caregivers or nurses, such as parents, who may be located close to the patient or remotely to the patient.

  According to further aspects of the concepts described herein, a system that enables remote monitoring of at least one medical device is configured to transmit a data packet containing information provided by at least one medical device. In addition, an apparatus integration server that communicates with at least one wireless relay apparatus is included. Each data packet includes medical device data and at least one medical device identifier or patient identifier. The system further includes a web server remote from the device integration server. The web server is configured to provide a web page and receive at least medical data.

  According to one embodiment, the web server is connected to the first remote monitoring device via a secure internet connection, configured to receive medical device data and send the medical device data to the first remote monitoring device. Is done. According to one embodiment, the first remote monitoring device displays medical device data.

  According to one embodiment, the web server further transmits at least a portion of the medical device data to the second remote monitoring device, and the second remote monitoring device displays the portion of the medical device data.

  According to one embodiment, the system further includes a data management system connected to the device integration server. The data management system includes at least a device control database.

  According to one embodiment, the web server is configured to verify the patient identifier and the medical device identifier before sending the medical device data to the first remote monitoring device over a secure internet connection.

  According to one embodiment, the web server is configured to transmit a portion of the medical device data to a second remote monitoring device through a path that includes a wireless data link.

  According to one embodiment, the wireless data link is on a wireless mobile data network.

  According to one embodiment, the second remote monitoring device is at least one portable communication device of a mobile phone, a tablet computer, or a portable computer.

  According to one embodiment, the web server is configured to send status information regarding the wireless relay network associated with the wireless relay device to at least one of the first and second remote monitoring devices.

  According to further aspects of the concepts described herein, a system that enables remote monitoring of at least one medical device is configured to transmit a data packet containing information provided by at least one medical device. In addition, an apparatus integration server that communicates with at least one wireless relay apparatus is included. The respective data packet includes data identifying medical device data, and at least one of a medical device identifier and a patient identifier, and a web server configured to provide a web page that receives at least the medical device data is And medical device data is transmitted to the first and second remote monitoring devices via a secure internet connection to display the medical device data at the first and remote monitoring devices, subject to verification of the medical device identifier.

  According to one embodiment, the system further includes a data management system connected to the device integration server. The data management system includes at least a device control database.

  According to one embodiment, the system further includes a network status server configured to send status information regarding the radio relay network associated with the radio relay device to at least one of the first or second remote monitoring devices. .

  According to one embodiment, the network status server is located at a different geographical location than the web server.

  According to a further aspect of the concepts described herein, a method for displaying medical device data by a medical device monitoring system includes a qualification sent from a user of a first monitoring device, and medical device information about the patient being monitored. Receiving a request sent from the user in response to checking for whether the user is authorized to receive medical device information. Responding to the achievement of the match, then (a) identifying the address of the secure patient database having information about the patient based at least on the qualifications and requests.

  According to one embodiment, the method includes (b) obtaining patient data and associated medical device identification data with a web server from a patient database over a secure communication link, and (c) according to the obtained medical device identification data, Obtaining medical device data for at least one medical device from the device control database.

  According to one embodiment, the method includes (d) transmitting the acquired medical device data by a web server for display on the first monitoring device; and (e) at least a portion of the medical device data. Transmitting to the second remote monitoring device for display on the second remote monitoring device.

  According to one embodiment, the portion of the medical device data transmitted to the second remote monitoring device includes status information regarding the wireless relay network associated with the wireless relay device.

  According to one embodiment, the method further includes receiving status information regarding a wireless relay network associated with the wireless relay device from the wireless relay module.

  According to one embodiment, the status information regarding the wireless relay network includes signal strength, data transfer rate, specific transmission timestamp, number of active relay modules in the wireless relay network, and a unique identifier corresponding to the specific relay module. Relates to at least one of the numbers.

  According to one embodiment, transmitting the portion of medical device data to the second remote monitoring device includes encrypting a portion of the medical device data.

  According to one embodiment, transmitting the acquired medical device data for display on the first monitoring device further includes encrypting the medical device data using a first encryption technique. Transmission of the portion of the medical device data to the second remote monitoring device includes encrypting the portion of the medical device data using a second encryption technique, the first encryption technique being the second encryption technique. Different from the encryption technology.

  According to further aspects of the concepts described herein, a system that enables remote monitoring of at least one medical device includes an access point that communicates with at least one wireless relay device, and an individual patient care database node . The access point includes a device integration server connected to a database in which medical device data is stored. The access point further includes a secure device server connected to the device integration server. The patient care database node includes a secure patient server connected to a patient database in which patient data is stored. The secure patient server is connected to the secure device server of the access node through a secure link.

  Each secure patient care database node to classify stored medical device data and patient data, respectively, and manage by access point and patient care database node, and to ensure control of privacy and related patient data By configuring access points to assist in many different patient care facilities that each maintain, certain scale benefits can be achieved.

  The invention will become more readily apparent from the detailed description of the invention which proceeds with reference to the following figures.

1 represents a block diagram of an exemplary remote monitoring system for remotely monitoring a medical device according to the present invention. FIG. 2 represents a flow chart illustrating an exemplary method of registering a medical device with the remote monitoring system according to FIG. 2 represents a flow chart illustrating an exemplary method for acquiring and viewing medical data via a remote monitoring system according to FIG. FIG. 4 shows an exemplary screen display for acquiring and viewing medical data by the method of FIG. FIG. 4 shows an exemplary screen display for acquiring and viewing medical data by the method of FIG. FIG. 4 shows an exemplary screen display for acquiring and viewing medical data by the method of FIG. 2 represents a flowchart illustrating an exemplary method for issuing a command to be sent to a medical device via the remote monitoring system according to FIG. Fig. 5 shows an exemplary screen display commanding the medical device by the method of Fig. 4 (a). Fig. 5 shows an exemplary screen display commanding the medical device by the method of Fig. 4 (a). 2 represents a flowchart illustrating an exemplary method for recognizing and reporting an alarm situation with medical data logged via the remote monitoring system according to FIG. FIG. 6 shows an exemplary screen display for selecting a recipient to receive a warning message by the method of FIG. 2 represents a block diagram of an exemplary computer or server device suitable for use in the remote monitoring system according to FIG.

  Reference will now be made in detail to exemplary embodiments of the invention, including what the inventors regard as the best mode for carrying out the invention. Examples of these exemplary embodiments are shown in the accompanying figures. While the invention will be described in conjunction with these embodiments, it will be understood that it is not intended to limit the invention to the described embodiments. Rather, the present invention is also intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the present invention as defined in the appended claims.

  In the following description, specific details are set forth in order to provide a thorough understanding of the present invention. The present invention may be practiced without some or all of these specific details. In other instances, well-known aspects have not been described in detail so as not to unnecessarily obscure the present invention.

  In order to illustrate the present invention, exemplary embodiments will be described with reference to FIGS.

  In this specification and the appended claims, the singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise. Except as otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

  A diagram of an exemplary system 100 for monitoring a medical device according to the present invention is shown in FIG. For example, one or more medical devices 10 are provided in a patient facility 20 for monitoring medical conditions and / or medical treatment of one or more patients. Patient equipment 20 may be a life-saving emergency health service center (eg, including hospitals, clinics, life support centers, etc.) that serves a large number of patients, or household equipment that serves one or more patients, or A personal housing (eg, backpack) that may be worn or worn by an outpatient may be included. Examples of medical devices include, but are not limited to, ventilators, urine devices, energy delivery devices, pulse oximeters, predictive thermometers, tympanic thermometers, patient electrodes, and nutrient pumps.

  Associated with each medical device 10 is an interface circuit 15, which may be another low-speed personal area network or “LR-WPAN”, ZIGBEE network or other low power Bluetooth® network, such as a network. A transceiver having one or more transmitters and / or receivers for transmitting and receiving signals within a low power personal area network, an existing or currently developing or under consideration facility oriented wireless network 17, respectively. Including. See, for example, Houda Labet et al. , Wi-Fi, Bluetooth (registered trademark), Zigbee (registered trademark) and WiMax, Springer 2010. This document is also incorporated herein by reference in its entirety. It should be understood that the interface circuit 15 may be housed or disposed externally within the medical device 10 according to the present invention.

  One or more relay modules 30 are also provided within the patient facility 20. Each relay module 30 includes a first transceiver for receiving signals from the interface circuit 15 and transmitting signals to the interface circuit 15 in the equipment-oriented wireless network 17, and further includes a wireless wide area network “WWAN” 52. A second transceiver for wirelessly transmitting signals to and receiving signals from the access point 40. Suitable WWANs for use in the present invention are, for example, networks based on the Pan-European Digital Mobile Telephone System (GSM) or Code Division Multiple Access (CDMA) cellular network, or 2G, 3G, 3G long term evolution, 4G, including networks related to the WiMAX cellular radio standard of the International Telecommunication Union Telecommunication Standardization Sector (ITU-R). See, for example, Vijay Garg, Wireless Communications & Networking, Morgan Kaufmann 2007. This document is incorporated herein by reference in its entirety. In order to comply with HIPAA regulations, communication over each of the equipment-oriented wireless network and the WWAN is secure using, for example, a secure socket layer (SSL) protocol or a transport layer security (TLS) protocol, or other cryptographic protocols. It is desirable to do.

  As shown in FIG. 1, an access point 40 usable with the present invention incorporates or has access to a transceiver for communication with a relay module 30 on the WWAN (“device integration server”). ]) 41 is included. Medical device data, medical device identifiers and / or patient identifiers received through the WWAN by the device integration server 41 are forwarded to the secure device web server 42, which is associated with the associated device control database 44, for example. It is configured to log received data regarding the identification information of the medical device. “Medical device data” as generally used herein refers to data sent from or related to a medical device. This data may include, for example, medical device identification, medical device software, medical device settings or status information (including alarm information and / or alarm priority), patient identification information, patient personal identification number “PIN”, patient prescription, In addition to patient medical and / or physiological data collected, created and / or generated by at least one of a medical device and / or patient identification device, wireless relay network information such as location or status information is also included.

  The outbound web server 43 is provided by one or more first remote monitoring devices 62, for example through the broadband network 50 (eg, through the Internet), and / or by the second remote monitoring devices 70, 75 through a wired or wireless wide area network. Configured to receive and identify the received data acquisition request. It is beneficial to make such a request in an encrypted format. A suitable encryption format that can be used for such a request includes, for example, a format that complies with the above-mentioned HIPAA regulations. For each identified request, the outbound web server 43 requests the associated medical device data or a portion thereof obtained from the device control database 44 via the secure device web server 42, and includes metadata and applications. Associations that are requested from the patient database 66 provided in the patient care database node 60 through the secure link 54 via the secure patient web server 64, requesting relevant program data to construct the display page from the database 46. Request patient data. The secure link 54 can be implemented as another WWAN using, for example, the SSL protocol or the TLS protocol. Each secure patient care is assured by classifying the stored medical device data and patient data, respectively, and managing them by the access point 40 and patient care database node 60, and ensuring control of privacy and related patient data. By configuring the access point 40 to assist in many different patient care facilities each maintaining a database node 60, certain scale benefits can be achieved.

  In this case, for example, a third party service provider may host the access point 40 to assist many different patients and / or home care facilities simultaneously. This eliminates the need for each of these facilities to configure and maintain their own private access point facilities, perhaps much less than the cost of configuring and maintaining dedicated access point facilities by their respective care facility providers. , Provide hosting services for each facility. However, consistent with the principles of the present invention, the access point 40 and patient care database node 60 may still have one access (eg, by the provider of a very large facility that monitors hundreds or thousands of patients). Note that it can be integrated into points or nodes. In any case, as further described herein, the outbound web server 43 is convenient so that details of the configuration and operation of the access point 40 and patient care database node 60 do not affect the clinician or other monitor. An interface for an authenticated clinician or other monitor to obtain patient and medical device data from each of the patient care database node 60 and access point 40 in a transparent manner.

  The first remote monitoring device 62 is intended to be used by health care providers such as clinicians, physicians, technicians, nurses, and other health consultants who monitor patients associated with the medical device 10. The A suitable first remote monitoring device 62 may include, for example, a desktop or laptop computer, a tablet computer, a smartphone or other mobile phone, or other fixed or portable display device. The second remote monitoring device 70, 75 is advantageously a patient relative such as a caregiver and / or parent, a person close to the patient, such as in a home healthcare environment or small health care facility, or larger health care. It is intended to be used by nurses in a facility, such as a hospital. A suitable second remote monitoring device 70, 75 may also include, for example, a desktop or laptop computer, a tablet computer, a smartphone or other mobile phone, or other fixed or other portable communication device.

  The outbound web server 43 is also shown to connect to a network status server 80 that monitors the status of the equipment-oriented wireless network 17 and the associated medical device 10. The network status server 80 is intended to provide status information regarding the equipment-oriented wireless network 17 and the associated medical device 10 to the outbound web server 43. Exemplary status information regarding the equipment-oriented wireless network 17 includes, for example, signal strength, data transfer rate, a specific transmission time stamp between modules comprising the network 17, the number of active relay modules in the network 17, and a specific network 17 Contains a unique identifier number corresponding to the relay module.

  The network status server 80 may be implemented in hardware or software running on an application specific or general purpose processor or computer that is part of or separate from the outbound web server 43. Also, the network status server 80 is shown connected to the outbound web server 43 for ease of presentation and for discussion purposes only. The network status server 80 may be connected to any component or network of the access point 40 or the equipment-oriented wireless network 17 according to the present invention.

  In FIG. 1, upon obtaining the requested medical device data and patient data from the patient care database node 60, the outbound web server 43 then responds to the corresponding first and second remote monitoring devices 62, 70 according to the obtained program data. , 75 format and transmit the acquired medical device data and patient data as respective web pages or other formats displayed by (and / or provide status information about the equipment-oriented wireless network 17 and associated medical device 10 To do). The web page or other formatted information for display can include the same or different content and format for the intended remote monitoring device user, depending on the acquired program data. For example, detailed medical device data provided and displayed on the first remote monitoring device 62 for the clinician may be monitored by a parent, visiting nurse or other health care professional in a home care environment. It may differ from the less detailed information provided and displayed on the remote monitoring device 70. Status information regarding the facility-oriented wireless network 17 and associated medical device 10 is conveniently provided to the first and / or second remote monitoring devices 62, 70 and 75 in the same or different encryption formats that may be considered appropriate. Can be provided.

  As further described herein, the device integration server 41 of FIG. 1 is configured to transmit information and commands to the relay module 30. For example, medical devices or alert messages to other WWAN reachable nodes (eg emergency attendant's mobile phone) and / or operational commands and / or software or firmware updates, interface circuit 15 and equipment oriented radio The data is transmitted to the medical device 10 via the network 17.

  Further, in addition to monitoring medical devices and sending commands to them, the device integration server 41 can route through the outbound web server 43 and the secure device web server 42 to prevent dangerous medical device usage based on patient metric information. Or by an alternative and direct secure data link with secure patient web server 64 may also be configured to receive and analyze patient metric information from secure patient web server 64. For example, a database (not shown) accessible by device integration server 41 and / or device web server 42 can store various safe and dangerous operating parameters and situations for performing such analysis. It is. In this way, the device integration server 41 will function as an additional failsafe to prevent operational errors that may harm the patient.

  For example, in the case where the patient metric information indicates that the enteral feeding pump is associated with a newborn, the device integration server 41 may, for example, (1) remotely program large rapid IV and overfeeding that may be harmful to the infant. The monitoring command may be discarded and (2) a possibly dangerous usage warning message or other notification that may occur is provided to the user by execution of such a comment. Alternatively, if the patient metric information indicates that a specific nutritional supplement or rapid intravenous infusion has been prescribed by a physician or clinician, the device integration server will program the amount out of prescription or the rapid intravenous infusion. Can function to discard monitoring commands.

  FIG. 2 shows a flowchart of one exemplary method 200 according to the present invention for registering the medical device 10 with the system 100 of FIG. Method 200 allows an authorized technician or other individual having access to one of remote monitoring devices 62, 70, 75 to provide authentication credentials (eg, recognized login and password) to outbound web server 43. The web server then begins at step 202 where it responds by sending a device settings screen to the remote monitoring device 62, 70, 75 requesting medical device identification information and associated patient identification information.

  At step 204, the outbound web server 43 preferably connects to the associated patient care database node 60 by querying the metadata and application database 46 according to one or more of the technician identification information and / or patient identification information. A plurality of patient care database nodes for the patient are identified, and the destination address of the associated patient care database node 60 is recorded in the metadata and application database 46 along with the medical device 10 identification data and / or patient identification information. The patient identification information is preferably generated anonymously (eg, as a random number) and transmitted to the patient care database node 60 in step 206 in association with the securely stored patient identification information. In step 208 of the method 200 of FIG. 2, the outbound web server 43 causes the secure device web server 42 to log the associated medical device data for the medical device 10 as received by the device integration server 41. Requests that an area of the control database 44 be allocated. This can later be acquired by the outbound web server 43 upon receiving an authorized request from an authenticated user operating one of the remote monitoring devices 62, 70, 75.

  It will be appreciated by those skilled in the art that if one patient care database node is utilized in the system 100 of FIG. 1, step 204 of the method 200 for identifying and storing the address of the patient care database node 60 can be omitted by the present invention. Should be easily understood.

  FIG. 3 (a) illustrates one exemplary method 300 according to the present invention for obtaining and viewing medical device data for registered medical devices 10 according to the system of FIG. 1 at remote monitoring devices 62, 70, 75. FIG. A flowchart is shown. The method 300 includes a step 302 where a first authorized user with access to one of the first remote monitoring devices 62 provides authentication credentials (eg, recognized login and password) to the outbound web server 43. Be started. Similarly, in step 302, a second authorized user having access to one of the second remote monitoring devices 70, 75 provides respective authentication credentials to the outbound web server 43.

  At step 304, based on the verification of the authentication credentials of the first and second authorized users, the outbound web server 43 queries the metadata and application database 46 to determine the respective first and second authorizations. Identify the address of the patient care database node (s) 60 to which the user has been granted the right to gain access. Then, in step 306, the first and second users request data from the patient care database node 60 for at least one identified patient each authorized to view the medical device data. This data includes, for example, a list of medical devices 10 currently associated with the identified patient and / or status information of the facility-oriented network 17. It should be readily understood that various authenticated users probably have various levels of skills and skills that the corresponding access level can be associated with their authentication account or situation. These can be further used, for example, to limit or expand the type and / or extent of medical device data that can be transmitted to a remote monitoring device for such authenticated users.

  In step 308 of the method 300 of FIG. 3 (a), the outbound web server 43 queries the device control database 44 for status information via the secure device web server 42, thereby logging data from the device control database 44. To determine which listed medical devices are currently active. One or more medical devices 10, their associated interface device 15, associated wireless relay module 30, and / or device integration server 41 may receive data from medical device 10 at a predetermined preset interval or other interval. It should be noted that the data can be programmed to be provided to the device integration server 41 and then to the server 43 in response to an inquiry from the server 43.

  Upon obtaining the situation information, the outbound web server 43 creates each display page having encrypted medical device data according to the display of information acquired from, for example, the metadata and the application database 46, and each authorized user Displays a list of medical devices 10 that can be used for monitoring on the remote monitoring devices 62, 70, 75. FIG. 3 (b) represents a first exemplary screen display 320 on a remote monitoring device 62, 70, 75 that provides an array of medical devices 10 that can be used for monitoring according to device type. For example, in the screen display 320 of FIG. 3B, usable device types are a ventilator 321, a urinary device 322, an energy supply device 323, a pulse oximeter 324, a predictive thermometer 325, a tympanic thermometer 326, and a nutrition pump. 327. Each of the device types 321 to 327 in FIG. 3B is represented by an identification label (for example, label 321A) and an identification image (for example, image 321B) for easy recognition.

  When the device type is selected by the user (e.g., in response to an associated mouse pointer movement or mouse click performed by an authorized user), a second example as shown in FIG. A screen display 330 is preferably transmitted by the outbound web server 43 for display on the remote monitoring device 62, 70 or 75. In display 330, a label 337A is provided along with image 337B (eg, by the patient and / or depending on the logical or physical location) to identify individual feeding pumps. The unavailable medical device 10 may, for example, desirably include a label 337A ′ (“offline”) and an image 337B ′ (an oblique line or crosshair on the image) that distinguish the unavailable medical device 10 from the available medical device 10. Holding, or indicating a shaded or shaded device).

  When an individual device is selected by the first or second user (eg, again in response to an associated mouse pointer movement or mouse click performed by an authorized user), FIG. 3 (d) A third exemplary screen display 340 as shown may be desirably transmitted by the outbound web server 43 for display on the corresponding remote monitoring device 62, 70, 75. In the display 340, for example, device information of the medical device 10 (in this case, a nutrition pump) is displayed on a screen 347A that desirably reproduces the latest screen generated and displayed by the medical device 10. Also, the screen display 340 is an alternative to the panel 347B that provides identification information (in this case, pump position) regarding the medical device 10, a panel 347C that displays a message indicating the latest error status of the pump, and the screen display 340. One of the icon buttons 347D for selecting the “status” mode is included. Screen display 340 also includes a control icon button 347E for selecting a system setup screen display and a control icon button 347F for enabling device control from remote monitoring device 62. For example, when the control icon 347F is selected, the screen display 340 may desirably be refreshed to include the medical device screen 347A and one or more operable buttons that mimic the appearance of the control buttons on the medical device. The features of the control buttons are described in more detail below with respect to FIGS. 4 (b) and 4 (c).

  The exemplary computer screen images 320, 330, and 340, and the corresponding operations shown in FIGS. 3 (b), 3 (c), and 3 (d) are merely exemplary and many other user screens. Easily that image display and interface tools can be utilized in the practice of the present invention including a computer screen showing a medical device accessible by other means different from the device type, eg, as shown in FIG. Should be understood. For example, a display that provides information from a plurality of medical devices can be realized as an appropriate alternative to the screen image 340 of FIG. 3D that transmits information from one medical device. Also, outbound web server 43 is desirable and includes any variety (including, for example, tablet devices including workstations, personal computers, tablet computers, and display-based mobile devices including personal digital assistants, smart phones, portable game systems, etc.) It should be readily understood that it is operable to create a display page with encrypted medical device data for display on a display device.

  Whether the computer screen images available to the first and second users of the first and second remote monitoring devices are such clinicians, nurses, patient relatives, or other caregivers It should also be readily understood that it may vary depending on the qualification level, i.e. depending on the qualification level of a user having a particular authority. For example, the display to the clinician on the first remote monitoring device 62 allows the clinician to adjust the settings of the medical device 10 under control. This is in contrast to the display on the second remote monitoring device 70, 75 used by the patient's body, which shows only basic information from the medical device data. The option to adjust medical device settings is not given to the patient's body. Similarly, various encryption schemes or formats may be employed for medical device data transmitted to the first remote monitoring device 62 rather than the second remote monitoring device 70, 75.

  FIG. 4 (a) represents a flowchart illustrating an exemplary method 400 according to the present invention for issuing commands to be sent to the medical device 10 via the system 100 according to FIG. The method 400 logs the outbound web server 43 using the first remote monitoring device 62 and FIG. 3 (eg, as described above with reference to FIGS. 3 (a) -3 (d)). d) an authorized user, such as a clinician (also referred to herein as an “authorized clinician” or “user”), manipulating the screen display 340 of the device of d) begins at step 402 where the operating parameters are adjusted. Is done. At step 404, the clinician selects the “Enable Full Control” button 347F of FIG. 3 (d) to activate an operational command for the medical device 10 and is particularly relevant to the patient associated with the medical device 10. A request for authentication is provided. In step 406, the patient authentication information provided by the clinician is forwarded by the outbound web server 43 to the patient care database node 60 according to the metadata associated with the clinician and the patient care database node address stored in the application database 46. Is done. The clinician is authenticated to the patient by the outbound web server 43 upon receipt of the authentication confirmed message from the patient care database node 60.

  When the patient authentication is received, the control request is transferred to the secure device web server 42 by the outbound web server 43 in step 408. This is logged in the information record of the device control database 44 associated with the medical device 10 (as appropriate using the patient's anonymous ID). In step 410, the secure device web server transfers a control request, such as an encrypted control request, to the device integration server 41. In step 412, the device integration server 41 transmits the related device control command through the secure WWAN 52 to be received by the related wireless relay module 30. The wireless relay module 30 wirelessly communicates a command to the medical device 10 via the associated device interface 15 and waits for a response confirming execution of the command transmitted by the device interface 15.

  In step 414, the device integration server 41 receives an update message confirming that the command has been executed by the medical device 10 from the wireless relay module 30 via the secure WWAN 52. In step 416, the device integration server 41 forwards the update message to the secure device web server 42 for logging in the information record of the device control database 44 associated with the medical device 10. As appropriate and desirable, secure device web server 42 forwards information regarding the update message to outbound web server 43. The outbound web server 43 creates an updated display screen that is securely transmitted to the remote monitoring device 62 to indicate that the command has been executed.

  Alternatively, at step 404, the authenticated clinician may select the “System Settings” control icon button 347E to execute a command other than an operational command for the medical device 10. FIG. 4B shows a display screen 450 shown to the clinician in selecting the control icon button 347E. Display screen 450 includes a number of icon buttons that can be selected by the clinician (eg, as a result of a mouse pointer movement or mouse click initiated by the clinician) to select a particular configuration command. For example, the icon button 451 can be selected to activate a command that provides identification information for the medical device 10. Icon button 452 may be selected to provide a text call in response to an alarm condition, as further described herein. Icon button 453 may be selected to launch a software or firmware download for updating medical device 10.

  Icon button 454 may be selected to activate a diagnostic test of medical device 10. FIG. 4 (c) shows an exemplary display screen 460 that may be displayed to the clinician upon selection of the icon button 454. Via the display screen 460 of FIG. 4 (C), the clinician proceeds through a series of diagnostic tests 461 on medical device components (eg, including power components, memory components, alarm components, etc.). One or more of (including tests) can be selected. Alternatively and / or additionally, the clinician may include a series of performance statistics 462 that are collected and displayed (eg, including various device error statistics such as feeding pump feeding errors, rotational errors and flow error rates). One or more can be selected. Also, perhaps as most useful prior to issuing a software and / or firmware download command, the clinician is concerned with software and / or firmware (desirably including, for example, software and / or firmware download history). A version number test 463 for obtaining version identification information can be selected. Where appropriate, processes for running diagnostic tests 461, creating performance statistics 462, and identifying software and / or firmware version number 463 are automatically launched and not displayed on the display screen without being specifically selected by the clinician. A complete report of all results can be shown.

  It is possible to issue a bandwidth priority command or instruction and send it to a relay module such as the relay module 30 of FIG. 1 in a manner similar to the execution by the method of FIG. The relay module is given priority to relay information received from a particular medical device to other medical devices that can transmit or receive communications via the relay module. For example, it would be beneficial to provide greater bandwidth priority to a life-saving first aid device such as a ventilator that assists the patient's respiratory function with respect to a scale or thermometer. For example, based on the critical nature of the data or functionality provided by such devices, each medical device may be assigned a number of bandwidth priority levels.

  Referring again to FIG. 4 (b), the icon button 455 can be selected to allow the clinician to specify data transfer rate, priority, and other parameters related to the wireless transceiver of the interface device associated with the medical device. . Icon button 456 may be selected to provide the clinician with an alarm history, an onset history, and other information, such as logged on a medical device in device control database 44 of FIG.

  The reason that the method 400 for remotely issuing commands to be sent to the medical device 10 is described for the user of the first remote monitoring device 62 and not for the user of the second remote monitoring 70, 75 is for example this application. While the user of the first remote monitoring device 62 is a clinician, technician, or other highly skilled health care professional, the user of the second remote monitoring device 70, 75 as described throughout However, it should be readily understood that it is assumed that it may be the relative of a lower-skilled patient or a caregiver. Nevertheless, the method 400 can be used as well so that the user of the second monitoring device 70, 75 can also control certain settings of the medical device 10.

  FIG. 5 (a) shows one exemplary method according to the present invention for recognizing and reporting alarm conditions by medical device data (including the situation of the facility-oriented network 17) logged via the system 100 according to FIG. 5 is a flowchart illustrating 500. The method 500 begins at step 502 where a warning message is sent to the device integration server 41 by the wireless relay module 30 through the secure WAN 52. In this case, the wireless relay module 30 analyzes the message type of the message sent by the associated medical device 10 (e.g., detects flag or status information or stores information in a database associated with the message data). Are determined to determine whether the message is a warning message, and if the message is determined to be a warning message, the message is configured to be transmitted to the device integration server 41 (for example, as a priority message). Instead, the wireless relay module 30 simply queues all messages to be sent to the device integration server 41 in the order received and analyzes the associated message type to determine if the message is a warning message. It can depend on the device integration server 41.

  If it is determined that the transmitted message is a warning message, the device integration server 41 logs the message in the device control database 44 at step 503 and calls the text message application at step 504. This text message application obtains a text message number associated with the identification information and / or anonymous patient identification information of the medical device 10. The determination of whether the transmitted message is a warning message can be performed, for example, by detecting an alarm flag or trigger identifier in the message, or by scanning a message for other information indicating an alarm condition. The text messaging application preferably queries to identify the address of the patient care database node 60 associated with the metadata and application database 46, and makes a direct request to the outbound web server 43 to the associated patient care database node. By instructing to request a text message number from 60, the text message number can be obtained.

  In step 506, the device integration server 41 transmits one or more messages including the acquired text message number and text message information to the one or more wireless relay modules 30 through the secure WWAN 52 according to the warning message. At step 508, the one or more wireless relay modules 30 transmit the text message information addressed to the text message number through one or more of the secure WWAN 52 and / or the equipment-oriented wireless network 17, and the method 500 is Complete.

  FIG. 5 (b) shows a screen display 550 of a “text call” 452 that may be invoked using, for example, the method 400 of FIG. 4 (a) for issuing a command to be sent to the medical device 10. Specifically, with particular reference to FIGS. 3 (d) and 4 (b), the text call screen 550 is authenticated based on the clinician's selection of the “System Settings” icon button 347 e on the screen display 340. Displayed on the physician's first remote monitoring device 62 and then proceeds to the “call text” icon button on the screen display 450 as the clinician selects. Similarly, the call screen 550 of FIG. 5 (b) can be displayed on the second remote monitoring device 70, 75 for completion by an authorized user such as the patient's relative or other caregiver. It is. As shown in FIG. 5 (b), the “text call” screen display 550 includes a list of one or more names 551 of individuals responsible for responding to at least two types of warning messages. As these two types of warning messages, an “error message” 553 may indicate, for example, a failure of the medical device 10 and / or an “information message” 554 may include, for example, a serious patient health condition (eg, patient breathing). The number may be equal to or less than a preset minimum speed specified for the ventilator 321 of FIG.

  The information obtained by the outbound web server 43 to create this display desirably provides one or more of identification information and / or anonymous patient identification information about the medical device 10 stored in the device control database 44. Is obtained from the patient care database node 60. When the warning message regarding the medical device 10 is recognized, the information provided on the “text call” screen display can be acquired by the device integration server 41. This acquisition involves querying the metadata and application server 46 to obtain address information relating to the patient care database node 60, requesting text call information, identification information relating to the medical device 10 stored in the device control database 44, and This is done by forwarding to the patient care database node 60 based on one or more of the anonymous patient identification information. Recognition of whether the message received from the medical device 10 is a warning message is performed, for example, by detecting an alarm flag or trigger identifier in the message, or by scanning a message for other information indicating an alarm condition. sell.

  The use of warning message communication using the text messages of FIGS. 5 (a) and 5 (b) is merely to illustrate the purpose, and such alarms are communicated in other ways according to the present invention. It should be readily understood that this is possible. This method can be used in addition to voice messages by email, telephone calls, as well as any other wired and / or wireless text, voice, multimedia that can be received by, for example, a smartphone or computer tablet software application, or “app” Includes base communications services.

  FIG. 6 illustrates an exemplary computer system 600 (eg, including device integration server 41, secure device web server 42, outbound web server 43, and secure patient web server 64) suitable for execution of the server and computer components of the present invention. Indicates. The computer system 600 described herein may be, for example, a personal computer that boots a WINDOWS® operating system, or a WINDOWS® server, LINUX®, or other UNIX®-based operating system. A server computer for starting the system may be included. Instead, the computer system 600 described herein can be a mobile device, tablet device or computer, or, for example, Symbian, Android, Apple ios, Blackberry, Microsoft Windows®, Linux®, Palm®, Palm / Information home appliances that start operating systems in groups including HP WebOS, BADA, MAEMO, and MEEGO may also be included. The foregoing methods executed by the server and computer components of the present invention may be executed in computer system 600 as stored program control instructions directed to control application software.

  Computer system 600 includes a processor 610, a memory 620, a storage device 630, and an input / output device 640. One of the input / output devices 640 may desirably include a display 645. Some or all of the components 610, 620, 630, and 640 may be interconnected by a system bus 650. The processor 610 may be single or multi-threaded and may include one or more cores. The processor 610 executes instructions that are the steps described in one or more of, for example, FIG. 2, FIG. 3 (a), FIG. 4 (a), or FIG. 5 (a) in the disclosed embodiments of the invention. To do. These instructions may be stored in one or more memories 620 or storage device 630. Information may be received and output using one or input / output device 640. Memory 620 stores information and may include computer readable media such as volatile or non-volatile memory. Storage device 630 provides the storage device of system 600, including, for example, the aforementioned database, and may be a computer-readable medium. In various aspects, the storage device 630 may be one or more of a flash memory device, a floppy disk drive, a hard disk device and an optical disk device, and / or a tape device.

  Input device 640 may provide input / output operations for system 600. Input / output device 640 may include one or more of a keyboard, pointing device, and / or microphone. Input / output device 640 may further include a display unit that displays a graphical user interface, speakers and printers, and any number of other serial devices (eg, configured as a universal serial bus (USB) -based device). Good.

  While the invention has been described with reference to the disclosed embodiments, it should be understood that many variations are possible without departing from the spirit and scope of the invention as defined in the claims. .

The scope of the invention is also intended to include all other predictable equivalents of the components and structures described herein and with reference to the drawing figures. Therefore, the present invention should be limited only by the scope of the claims and their equivalents.
For example, the present invention provides the following items.
(Item 1)
A system enabling remote monitoring of at least one medical device,
An apparatus integration server that communicates with at least one wireless relay device, wherein the wireless relay device is configured to transmit a data packet containing information provided by at least one medical device, each of the data packets being identified A device integration server comprising medical device data and at least a medical device identifier or patient identifier;
A data management system connected to the device integration server and comprising at least a device control database;
Providing at least a web page for receiving the medical data, transmitting the medical device data to a first remote monitoring device for displaying the medical device data via a secure internet connection, and at least a portion of the medical device data And a web server configured to transmit to a second remote monitoring device that displays a portion of the medical device data.
(Item 2)
The system of claim 1, wherein the web server is configured to verify the patient identifier and the medical device identifier before sending the medical device data to the first remote monitoring device.
(Item 3)
The system of claim 1, wherein the web server is configured to transmit a portion of the medical device data to the second remote monitoring device over at least a wireless data link.
(Item 4)
4. The system of item 3, wherein the wireless data link is on a wireless mobile data network.
(Item 5)
The system of item 1, wherein the second remote monitoring device is at least one portable communication device of a mobile phone, a tablet computer, and a portable computer.
(Item 6)
The system of item 1, wherein the web server is configured to send status information regarding a wireless relay network associated with the wireless relay device to at least one of the first and second remote monitoring devices.
(Item 7)
A system enabling remote monitoring of at least one medical device,
A device integration server that communicates with at least one wireless relay device, wherein the wireless relay device is configured to transmit a data packet containing information provided by at least one medical device, each data packet being a medical device A device integration server comprising data identifying device data and at least one of a medical device identifier and a patient identifier;
A data management system connected to the device integration server and comprising at least a device control database;
Providing at least a web page for receiving the medical device data, and displaying the medical device data on a first and remote monitoring device, subject to a match of the patient identifier and the medical device identifier, A web server configured to transmit to the first and second remote monitoring devices via a secure internet connection;
A system comprising: a network status server configured to transmit status information regarding a radio relay network associated with the radio relay device to at least one of the first or second remote monitoring devices.
(Item 8)
8. The system of item 7, wherein the network status server is located at a different geographical location than the web server.
(Item 9)
A method of displaying medical device data by a medical device monitoring system comprising:
Receiving a qualification sent from a user of the first monitoring device and a request from said user for medical device information regarding the patient to be monitored;
Checking if the user has the authority to receive the medical device information and if verification is obtained,
(A) identifying an address of a secure patient database having information about the patient based at least on the qualification and the request;
(B) obtaining patient data and associated medical device identification data from the patient database via a secure communication link by a web server;
(C) acquiring medical device data relating to at least one medical device from the device control database according to the acquired medical device identification data;
(D) transmitting the acquired medical device data by the web server for display on the first monitoring device;
(E) transmitting at least a portion of the medical device data to the second remote monitoring device for display on the second remote monitoring device.
(Item 10)
Transmitting at least a portion of the medical device data to a second remote monitoring device includes transmitting at least status information regarding a wireless relay network associated with the wireless relay device to the second remote monitoring device. 9. The method according to 9.
(Item 11)
10. The method of item 9, further comprising receiving status information regarding a wireless relay network associated with the wireless relay device from the wireless relay module.
(Item 12)
The status information regarding the wireless relay network is at least one of signal strength, data transfer rate, specific transmission time stamp, number of active relay modules in the wireless relay network, and a unique identifier number corresponding to the specific relay module 10. The method according to item 9, wherein
(Item 13)
10. The method of item 9, wherein transmitting the portion of the medical device data to the second remote monitoring device includes encrypting the portion of the medical device data.
(Item 14)
The step of transmitting the acquired medical device data for display on the first monitoring device further comprises encrypting the medical device data using a first encryption technique; Transmitting the portion of the medical device data to the second remote monitoring device using a second encryption technique different from the first encryption technique. The method according to item 9, comprising.
(Item 15)
A system enabling remote monitoring of at least one medical device,
At least one wireless relay device configured to communicate with the at least one medical device;
An access point that communicates with the at least one wireless relay device, the access point including a device integration server connected to a database in which medical device data is stored, and a secure device server connected to the device integration server Point and
A patient care database node including a secure patient server connected to a patient database in which patient data is stored, separate from the access point;
A system comprising a secure link connected between the secure patient server and the secure device server of the access node.

Claims (18)

A system enabling remote monitoring of at least one medical device,
An apparatus integration server that communicates with at least one wireless relay device, wherein the wireless relay device is configured to transmit a data packet containing information provided by at least one medical device, each of the data packets being identified A device integration server comprising medical device data and at least a medical device identifier or patient identifier;
A data management system connected to the device integration server and comprising at least a device control database;
Providing at least a web page for receiving the medical data, transmitting the medical device data to a first remote monitoring device for displaying the medical device data via a secure internet connection, and at least a portion of the medical device data A web server configured to transmit to a second remote monitoring device that displays a portion of the medical device data;
A system wherein a portion of the medical device data displayed by the second remote monitoring device is different from the data displayed by the first remote monitoring device.   The system of claim 1, wherein the web server is configured to verify the patient identifier and the medical device identifier before sending the medical device data to the first remote monitoring device.   The system of claim 1, wherein the web server is configured to transmit a portion of the medical device data to the second remote monitoring device over at least a wireless data link.   The system of claim 3, wherein the wireless data link is on a wireless mobile data network.   The system of claim 1, wherein the second remote monitoring device is at least one portable communication device of a mobile phone, a tablet computer, and a portable computer.   The system of claim 1, wherein the web server is configured to send status information regarding a wireless relay network associated with the wireless relay device to at least one of the first and second remote monitoring devices. A system enabling remote monitoring of at least one medical device,
A device integration server that communicates with at least one wireless relay device, wherein the wireless relay device is configured to transmit a data packet containing information provided by at least one medical device, each data packet being a medical device A device integration server comprising data identifying device data and at least one of a medical device identifier and a patient identifier;
A data management system connected to the device integration server and comprising at least a device control database;
Providing a web page for receiving at least the medical device data and displaying the medical device data on a first and a second remote monitoring device subject to verification of the patient identifier and the medical device identifier A web server configured to transmit data to the first monitoring device and the second remote monitoring device via a secure internet connection, wherein the second monitoring device is configured by the first monitoring device. A web server configured to display a portion of the medical device data different from the data to be displayed;
A system comprising: a network status server configured to transmit status information regarding a radio relay network associated with the radio relay device to at least one of the first or second remote monitoring devices.   The system of claim 7, wherein the network status server is located at a different geographical location than the web server. A method of displaying medical device data by a medical device monitoring system comprising:
Receiving a qualification sent from a user of the first monitoring device and a request from said user for medical device information regarding the patient to be monitored;
Verifying that the user is authorized to receive the medical device information;
If a match is obtained,
Identifying an address of a secure patient database having information about the patient based at least on the qualification and the request;
Obtaining patient data and associated medical device identification data by a web server from the patient database through a secure communication link;
Acquiring medical device data relating to at least one medical device from the device control database according to the acquired medical device identification data;
Transmitting the acquired medical device data by the web server for display on the first monitoring device;
Transmitting at least a portion of the medical device data to the second remote monitoring device for display on the second remote monitoring device;
Displaying a portion of the medical data different from the data displayed on the first monitoring device in the second remote monitoring device.   Transmitting at least a portion of the medical device data to a second remote monitoring device comprises transmitting to the second remote monitoring device at least status information regarding a wireless relay network associated with the wireless relay device. Item 10. The method according to Item 9.   The method of claim 9, further comprising receiving status information regarding a wireless relay network associated with the wireless relay device from the wireless relay module.   The status information regarding the wireless relay network is at least one of signal strength, data transfer rate, specific transmission time stamp, number of active relay modules in the wireless relay network, and a unique identifier number corresponding to the specific relay module The method according to claim 9.   The method of claim 9, wherein transmitting the portion of the medical device data to the second remote monitoring device includes encrypting the portion of the medical device data.   The step of transmitting the acquired medical device data for display on the first monitoring device further comprises encrypting the medical device data using a first encryption technique; Transmitting the portion of the medical device data to the second remote monitoring device using a second encryption technique different from the first encryption technique. 10. The method of claim 9, comprising. A system enabling remote monitoring of at least one medical device,
At least one wireless relay device configured to communicate with at least one medical device;
An access point that communicates with the at least one wireless relay device, the access point including a device integration server connected to a database in which medical device data is stored, and a secure device server connected to the device integration server Point and
A patient care database node including a secure patient server connected to a patient database in which patient data is stored, separate from the access point;
A first monitoring device configured to receive and display data provided by the at least one medical device;
A second monitoring device configured to receive and display at least a portion of the data provided by the at least one medical device different from the data displayed by the first monitoring device;
A system comprising a secure link connected between the secure patient server and the secure device server of the access node.   The system of claim 1, wherein the data displayed by the second monitoring device is not as detailed as the data displayed by the first monitoring device.   The system of claim 16, wherein the second remote monitoring device is located in a home medical environment and the data displayed by the second monitoring device is designed for viewing in a home medical environment.   The system of claim 17, wherein the device integration server is further configured to send a device control command to the at least medical device.

Images