System for paring medical monitoring with network controller by using dongle
A centralized medical monitoring hub addresses the fragmentation of patient monitoring devices by integrating and translating data from multiple sources, enhancing data management and patient safety through unified displays and streamlined caregiver workflows.
Patent Information
- Application Number
- JP2024113523
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2017-07-21
- Filing Date
- 2024-07-16
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2038-05-04
AI Technical Summary
The existing patient monitoring environment is fragmented with multiple devices from different manufacturers that do not communicate with each other, leading to inconsistent data entry, chaotic displays and alarms, and potential patient distraction or confusion, especially in critical care settings.
A medical monitoring hub that centralizes patient data from various devices, providing a configurable medical port for communication, translating data formats, and integrating with a portable monitor to present unified displays, including anatomical graphics, while allowing seamless integration with hospital systems.
The hub simplifies data management, reduces caregiver workload, and enhances patient safety by providing a unified display of patient information, reducing distractions and improving care coordination across different medical devices.
Smart Images

Figure 2024161364000001_ABST
Abstract
Description
[Technical field]
[0001] Related Applications This application is related to the following U.S. patent applications, the disclosures of which are incorporated herein by reference in their entireties: Application Number Application Date name Reference number 62 / 463,452 February 24, 2017 Patient Monitor Communication Platform MAS.1126PR 62 / 463,297 February 24, 2017 Modular Multi-Parameter Patient Monitoring Device MAS.1130PR 62 / 463,517 February 24, 2017 System for displaying and controlling medical monitoring data - Patents.com MAS.1132PR1 62 / 503,109 May 8, 2017 System for displaying and controlling medical monitoring data - Patents.com MAS.1170PR1 62 / 535,757 July 21, 2017 System for displaying and controlling medical monitoring data - Patents.com MAS.1170PR2 62 / 463,614 February 25, 2017 Patient Monitor Communication Platform MAS.1133PR
[0002] Many of the embodiments described herein are compatible with the embodiments described in the related applications referenced above. Furthermore, some or all of the features described herein may be used or otherwise combined with many of the features described in the applications listed above.
[0003] FIELD OF THE DISCLOSURE The present disclosure relates generally to patient monitoring devices, and more particularly to patient monitors and medical data communication hubs. [Background technology]
[0004] Today's patient monitoring environment is bustling with sophisticated, often electronic, medical devices that provide a wide variety of monitoring and treatment activities for a given patient. Typically, many, if not all, of these devices are from different manufacturers, and many may be portable devices. These devices may not communicate with each other, and each may have its own dedicated controls, displays, alarms, configurations, and the like. Complicating the issue is that caregivers often want to associate all kinds of measurement and usage data from these devices with a specific patient. Thus, patient information entry is often done on a device-by-device basis. Sometimes, inconsistencies within devices necessitate simply printing out a paper from each device and filing it in the patient's chart for review by the caregiver.
[0005] Such differences in devices often result in a caregiver's environment being cluttered with multiple displays and alarms, creating a potentially chaotic experience that can be harmful to the patient in many situations, including surgical environments where caregiver distraction is undesirable, and recovery or monitoring environments where patient distraction or confusion may be undesirable.
[0006] Various manufacturers produce multi-monitor devices or devices that expand in a modular manner to increase the variety of monitoring or therapeutic activities that a particular system can accomplish. However, as medical device technology expands, such multi-monitor devices begin to become obsolete the moment they are installed. [Prior art documents] [Patent documents]
[0007] [Patent Document 1] U.S. Patent Application Serial No. 13 / 269,296 [Patent Document 2] U.S. Patent Application Serial No. 13 / 371,767 [Patent Document 3] U.S. Patent Application Serial No. 12 / 904,925 [Patent Document 4] U.S. Patent Publication No. 2002 / 0140675 [Patent Document 5] U.S. Patent Publication No. 2010 / 0274099 [Patent Document 6] U.S. Patent Publication No. 2011 / 0213273 [Patent Document 7] U.S. Patent Publication No. 2012 / 0226117 [Patent Document 8] U.S. Patent Publication No. 2010 / 0030040 [Patent Document 9] U.S. Patent Application No. 61 / 242,792 [Patent Document 10] U.S. Patent Application No. 61 / 387457 [Patent Document 11] U.S. Patent Application No. 61 / 645,570 [Patent Document 12] U.S. Patent Application Serial No. 13 / 554,908 [Patent Document 13] U.S. Patent No. 6,157,850 [Patent Document 14] U.S. Patent No. 6,334,065 [Patent Document 15] U.S. Patent Publication No. 2011 / 0105854 [Patent Document 16] U.S. Patent Publication No. 2011 / 0169644 [Patent Document 17] U.S. Patent Publication No. 2007 / 0180140 [Patent Document 18] U.S. Patent Publication No. 2011 / 0172561 [Patent Document 19] U.S. Application Serial No. 14 / 032,132 [Patent Document 20] U.S. Patent No. 9,142,117 [Patent Document 21] U.S. Application No. 62 / 463,262 [Patent Document 22] US Publication No. 2014 / 0077956 [Patent Document 23] U.S. Application Serial No. 14 / 511,972 [Patent Document 24] Application No. 14 / 030,360 [Patent Document 25] U.S. Patent No. 9,749,232 [Patent Document 26] U.S. Patent Application Serial No. 15 / 902,193 Summary of the Invention [Problem to be solved by the invention]
[0008] This disclosure describes embodiments of a medical monitoring hub as a monitoring focal point for a monitored patient. The hub can include configurable medical and serial ports for communicating with other medical devices in the patient's vicinity. Additionally, the hub can communicate with a portable patient monitor. When docked to the hub, the monitor can present different display graphics than when undocked. The display graphics can include anatomical information. The hub can assemble the often vast amounts of electronic medical data, associate it with the monitored patient, and in some embodiments, communicate the data to the patient's medical record. [Means for solving the problem]
[0009] Some aspects of the present disclosure describe a first medical device having a digital logic circuit receiving a physiological signal associated with a patient from a physiological sensor, obtaining a first physiological parameter value based on the physiological signal, and outputting the first physiological parameter value for display. The first medical device can also receive a second physiological parameter value from a second medical device different from the first medical device, the second physiological parameter value being formatted according to a protocol not used by the first medical device, such that the first medical device cannot process the second physiological parameter value to generate a displayable output value. The first medical device can pass physiological parameter data from the first medical device to a separate translation module, receive translated parameter data from the translation module in the first medical device, the translated parameter data can be processed for display by the first medical device, and output and display a second value from the translated parameter data. The first medical device may be, for example, a monitoring hub, a portable physiological monitor, or a multi-patient monitoring system, and the second medical device may be an infusion pump, a ventilator, or the like.
[0010] For purposes of summarizing the disclosure, certain aspects, advantages, and novel features are described herein. It is to be understood that not all such aspects, advantages, or features are necessarily embodied in any particular embodiment of the invention, and one of ordinary skill in the art will recognize from this disclosure that there are myriad combinations of such aspects, advantages, or features.
[0011] The following drawings and the associated description are provided to illustrate embodiments of the present disclosure and not to limit the scope of the claims. [Brief description of the drawings]
[0012] [Figure 1A]FIG. 2 is a perspective view of an exemplary medical monitoring hub according to one embodiment of the present disclosure illustrating the hub with an exemplary docked portable patient monitor according to various embodiments of the present disclosure. [Figure 1B] FIG. 2 is a perspective view of an exemplary medical monitoring hub according to one embodiment of the present disclosure illustrating a hub with a set of medical ports and a non-invasive blood pressure input according to various embodiments of the present disclosure. [Figure 1C] FIG. 2 is a perspective view of an exemplary medical monitoring hub according to one embodiment of the present disclosure illustrating the hub with various exemplary temperature sensors attached thereto according to various embodiments of the present disclosure. [Diagram 2] FIG. 2 is a simplified block diagram illustrating an example monitoring environment including the hub of FIG. 1, according to one embodiment of the present disclosure. [Diagram 3] FIG. 2 is a simplified exemplary hardware block diagram of the hub of FIG. 1 in accordance with one embodiment of the present disclosure. [Figure 4] 2 is a perspective view of an exemplary removable docking station of the hub of FIG. 1 according to one embodiment of the present disclosure. [Diagram 5] 2 is a perspective view showing an exemplary portable patient monitor undocked from the hub of FIG. 1 according to one embodiment of the present disclosure, further illustrating an exemplary alternative docking station. [Figure 6] FIG. 1 is a simplified block diagram illustrating the electrical isolation principle of a conventional patient device. [Figure 7A] FIG. 1 is a simplified block diagram illustrating an exemplary optional patient device isolation system according to an embodiment of the present disclosure. [Figure 7B] FIG. 7B illustrates the addition of an exemplary optional non-isolated power level to the system of FIG. 7A, also according to one embodiment of the present disclosure. [Figure 8] 1A-1C illustrate a simplified exemplary universal medical connector configuration process according to one embodiment of the present disclosure. [Figure 9A] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 9B] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 10] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11A] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11B] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11C] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11D] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11E] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11F] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11G1] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11G2] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11H] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11I]FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11J] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 11K] FIG. 1 is a simplified block diagram illustrating an exemplary universal medical connector having a small cross-sectional size and shape relative to conventional isolation requirements. [Figure 10] 2 is a perspective side view of the hub of FIG. 1 showing an exemplary instrument side channel input to an exemplary universal medical connector according to one embodiment of the present disclosure. [Figure 11A] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11B] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11C] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11D] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11E] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11F] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11G1] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11G2] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11H]1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11I] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11J] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 11K] 1A-1D are various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. [Figure 12] FIG. 2 is a simplified block diagram illustrating a channel system for the hub of FIG. 1 according to one embodiment of the disclosure. [Figure 13] FIG. 2 illustrates an exemplary logical channel configuration according to one embodiment of the present disclosure. [Figure 14] 1A-1C illustrate a simplified exemplary process for fabricating a cable and configuring a channel according to one embodiment of the present disclosure. [Figure 15] FIG. 2 is a perspective view of the hub of FIG. 1 including an exemplary attached board-in cable for forming an input channel, according to one embodiment of the disclosure. [Figure 16] 2 is a rear perspective view of the hub of FIG. 1 showing an exemplary meter-side serial data input according to one embodiment of the present disclosure. [Figure 17A] FIG. 17 illustrates an example monitoring environment communicating over the serial data connection of FIG. 16 in accordance with an embodiment of the present disclosure. [Figure 17B] 2 is a diagram of an example connectivity display of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 18] FIG. 1 illustrates a simplified exemplary patient data flow process, according to one embodiment of the present disclosure. [Figure 19A] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19B]2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19C] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19D] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19E] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19F] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19G] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19H] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19I] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 19J] 2 illustrates an exemplary display of anatomical graphics for the portable patient monitor of FIG. 1 docked to the hub of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 20A] 2A-2C are diagrams illustrating example displays of measurement data showing data separation and data overlap on the display of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 20B] 2A-2C are diagrams illustrating example displays of measurement data showing data separation and data overlap on the display of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 20C] 2A-2C are diagrams illustrating example displays of measurement data showing data separation and data overlap on the display of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 21A] 2A-2C are diagrams illustrating example displays of measurement data showing data separation and data overlap on the display of the portable patient monitor of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 21B] 2A-2C are diagrams illustrating example displays of measurement data showing data separation and data overlap on the display of the portable patient monitor of FIG. 1 in accordance with an embodiment of the present disclosure. [Figure 22A] FIG. 2 illustrates an exemplary analog display indicia according to one embodiment of the present disclosure. [Figure 22B] FIG. 2 illustrates an exemplary analog display indicia according to one embodiment of the present disclosure. [Figure 23A] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, a depth of consciousness monitor is connected to a channel port of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 23B] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, a depth of consciousness monitor is connected to a channel port of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 23C] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, a depth of consciousness monitor is connected to a channel port of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 23D] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, a depth of consciousness monitor is connected to a channel port of the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 23E] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, temperature and blood pressure sensors communicate with the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 23F] 2A-2C are diagrams illustrating example displays of measurement data showing data representations when, for example, an acoustic sensor is also in communication with the hub of FIG. 1 according to an embodiment of the present disclosure. [Figure 24]FIG. 2 illustrates another embodiment of a monitoring environment including the hub of FIG. 1. [Diagram 25] FIG. 1 illustrates one embodiment of a translated message handling process. [Figure 26] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 27] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 28] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 29] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 30] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 31] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 32] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 33] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 34] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 35] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Diagram 36] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 37] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 38] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 39] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 40A] FIG. 1 illustrates an example first medical device and an example second medical device communicating with each other via a translation module. [Figure 40B]FIG. 1 illustrates an example first medical device and an example second medical device communicating with each other via a translation module and a communication bus. [Figure 41A] FIG. 2 illustrates an exemplary input message received by a translation module. [Figure 41B] FIG. 2 illustrates an example message header segment of an input message that has been parsed into several fields. [Figure 41C] FIG. 41C illustrates an exemplary encoded version of the parsed message header segment of FIG. 41B. [Figure 41D] FIG. 41B illustrates an exemplary output message of the translation module based on the input message of FIG. 41A. [Diagram 42] FIG. 2 illustrates an example translation process for generating an output message based on a comparison of an input message with translation rules associated with a translation module. [Figure 43A] FIG. 1 illustrates an exemplary translation process in which a translation module facilitates the transmission of an HL7 message from a hospital information system ("HIS") having a first HL7 format to an intended recipient medical device having a second HL7 format. [Figure 43B] FIG. 1 illustrates an example translation process in which a translation module facilitates communication of an HL7 message from a medical device having a first HL7 format to an HIS having a second HL7 format. [Diagram 44] FIG. 13 illustrates an example screenshot from a messaging implementation tool for manually configuring translation rules to be used by a translation module. [Figure 45A] FIG. 2 illustrates an example automatic rule configuration process that may be performed by a translation module. [Figure 45B] FIG. 2 illustrates an example automatic rule configuration process that may be performed by a translation module. [Figure 45C]FIG. 2 illustrates an example automatic rule configuration process that may be performed by a translation module for messages utilizing the HL7 protocol. [Figure 45D] FIG. 2 illustrates an example automatic rule configuration process that may be performed by a translation module for messages utilizing the HL7 protocol. [Figure 46] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 47] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 48] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 49] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 50] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 51] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 52] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 53] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 54] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 55] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 56] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 57] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 58] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 59] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 60]13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 61] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 62] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 63] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 64] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 65] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 66] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 67] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 68] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 69] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 70] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 71] 13A-13C illustrate additional exemplary hub displays, including displays of measurement data. [Figure 72A] FIG. 1 illustrates a monitoring environment of another embodiment including an augmented reality device. [Fig. 72B] FIG. 1 illustrates an exemplary augmented reality user interface. [Fig. 72C] FIG. 1 illustrates an exemplary augmented reality user interface. [Fig. 72D] FIG. 1 illustrates an exemplary augmented reality user interface. [Fig. 72E] FIG. 1 illustrates an exemplary augmented reality user interface. [Fig. 72F] FIG. 1 illustrates one embodiment of an augmented reality display generation process. [Fig. 72G] FIG. 1 illustrates one embodiment of an augmented reality position determination process. [Figure 73] FIG. 1 illustrates one embodiment of an auxiliary device authentication process. [Figure 74] FIG. 1 illustrates one embodiment of an auxiliary device control process. [Figure 75] FIG. 1 illustrates one embodiment of an auxiliary device data flow process. [Figure 76] FIG. 1 illustrates one embodiment of a user interface for controlling an auxiliary device. [Figure 77A] FIG. 1 illustrates an additional embodiment of a monitoring environment. [Fig. 77B] FIG. 1 illustrates an additional embodiment of a monitoring environment. [Fig. 78A] FIG. 1 illustrates a schematic diagram of an exemplary embodiment of a medical network interface. [Fig. 78B] FIG. 1 illustrates a schematic diagram of an exemplary embodiment of a medical network interface. [Figure 79] FIG. 1 illustrates an exemplary embodiment of a dongle used to pair the medical network interface with another device. [Figure 80] FIG. 1 illustrates an exemplary embodiment of components of a medical network interface. [Figure 81] FIG. 1 illustrates an example embodiment of a flow diagram for pairing a medical network interface with a medical device. [Figure 82] FIG. 1 illustrates an example embodiment of a process for pairing a medical network interface with a medical device. [Figure 83] FIG. 1 illustrates an exemplary embodiment of a process for data processing by a medical network interface. [Fig. 84A]FIG. 1 illustrates an example of a medical network interface in which the medical network interface is removably attached to the bottom surface of a hub. [Fig. 84B] FIG. 1 illustrates an example of a medical network interface in which the medical network interface is removably attached to the bottom surface of a hub. [Fig. 84C] FIG. 13 is a diagram illustrating another example of a medical network interface. [Fig. 84D] FIG. 13 is a diagram illustrating another example of a medical network interface. [Fig. 85A] 1A-1C show exemplary structures for mechanically mounting a medical network interface. [Fig. 85B] 1A-1C show exemplary structures for mechanically mounting a medical network interface. [Fig. 85C] 1A-1C show exemplary structures for mechanically mounting a medical network interface. [Figure 86A] FIG. 2 illustrates an example of hardware components of a wireless connector. [Figure 86B] FIG. 2 illustrates an example of hardware components of a wireless connector. [Figure 87A] FIG. 1 illustrates an example of a dongle socket that can connect a medical device to a medical network interface via a wireless connector. [Fig. 87B] FIG. 1 illustrates an example of a dongle socket that can connect a medical device to a medical network interface via a wireless connector. [Fig. 87C] FIG. 1 illustrates an example of a dongle socket that can connect a medical device to a medical network interface via a wireless connector. [Fig. 87D] FIG. 1 illustrates an example of a dongle socket that can connect a medical device to a medical network interface via a wireless connector. [Figure 88]13A-13C show additional examples of wireless connectors and dongle sockets. [Figure 89] 13A-13C show additional examples of wireless connectors and dongle sockets. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] While the "Brief Description of the Drawings" above generally refers to various embodiments of the present disclosure, one of ordinary skill in the art will recognize from the disclosure herein that such embodiments are not mutually exclusive. Rather, one of ordinary skill in the art will recognize that there are countless combinations of any or all of such embodiments.
[0014] I. Introduction Based at least on the above, there is a need for a solution that coordinates various medical devices that treat or monitor a patient. Embodiments of such a solution should provide seamless patient identification across device space, and embodiments of such a solution should scale with future technology without necessarily requiring repeated software upgrades. In addition, embodiments of such a solution may include electrical isolation of the patient when desired.
[0015] Thus, the present disclosure is directed to a patient monitoring hub that is central to patient monitoring and treatment activities for a given patient. Patient monitoring hub embodiments provide the flexibility to interface with legacy devices without requiring legacy reprogramming, to interface with future devices without requiring software upgrades, and optionally provide patient electrical isolation. In one embodiment, the hub includes a large display that dynamically provides information to the caregiver regarding a wide variety of measured or otherwise determined parameters. Additionally, in one embodiment, the hub includes a docking station for a portable patient monitor. The portable patient monitor may communicate with the hub through the docking station or through a variety of wireless paradigms known to those skilled in the art from the disclosure herein, including WiFi, Bluetooth, Zigbee, or the like.
[0016] In yet another embodiment, the portable patient monitor modifies its screen when docked. The undocked display indicia is transferred in part or in whole to the hub's larger dynamic display, and the docked display presents one or more anatomical graphics of the monitored body part. For example, the display may present the heart, lungs, brain, kidneys, intestines, stomach, other organs, fingers, gastrointestinal system, or other body parts when docked. In one embodiment, the anatomical graphics may be advantageously displayed in animation. In one embodiment, the animation may generally follow the behavior of the measured parameters, for example, the lungs may inflate in approximate correlation with the measured respiratory rate and / or the determined inhalation portion of the respiratory cycle, and similarly deflate according to its exhalation portion. The heart may beat according to a pulse rate, beat along a commonly understood cardiac contraction pattern of a real heart, and behave in a similar manner. Furthermore, in one embodiment, when the measured parameters indicate the need to alert the caregiver, a changing severity of color may be associated with one or more displayed graphics, such as the heart, lungs, brain, or the like. In yet other embodiments, the body parts may include animations regarding where, when, or how to attach a measurement device to a patient's measurement site. For example, the monitor may provide animated instructions for a CCHD screening procedure or glucose strip reading protocol, application of a forehead sensor, finger or toe sensor, application of one or more electrodes, acoustic sensors, and ear sensors, cannula sensors, or the like.
[0017] The present disclosure pertains to a medical monitoring hub configured to be the center of monitoring activity for a given patient. In one embodiment, the hub is equipped with a large, easy-to-read display, such as an approximately 10 inch display dominating most of the footprint on the front of the hub. The display could be much larger or much smaller depending on design constraints. However, for portability and current design goals, the preferred display size is roughly proportional to the vertical footprint of one of the dockable portable patient monitors. Other considerations will be discernible by one of ordinary skill in the art from the disclosure herein.
[0018] The display provides numerical data in numerical or graphical form for a wide variety of monitored parameters for the patient under observation, and in various embodiments is automatically configured based on the type of data and information received at the hub. In one embodiment, the hub is mobile, portable, and wearable so that it can be positioned in a convenient area within the caregiver's environment. For example, the hubs are contained within a single housing.
[0019] In one embodiment, the hub may advantageously receive data from a portable patient monitor that is docked or undocked from the hub. A typical portable patient monitor, such as an oximeter or CO-oximeter, may provide measurement data for a number of physiological parameters derived from signals output from optical and / or acoustic sensors, electrodes, or the like. Physiological parameters include, but are not limited to, oxygen saturation, carboxyhemoglobin, methemoglobin, total hemoglobin, glucose, pH, bilirubin, saturation fraction, pulse rate, respiratory rate, components of the respiratory cycle, indications of perfusion including perfusion index, signal quality and / or confidence, plethysmographic data, indications of health or health index or other combinations of measurement data, auditory information responsive to respiration, disease identification or diagnosis, blood pressure, patient and / or measurement site temperature, depth of sedation, organ or brain oxygenation, hydration, measurements responsive to metabolism, combinations thereof, or the like, to name a few. In other embodiments, the hub may output sufficient data to effect closed-loop drug administration in conjunction with an infusion pump or the like.
[0020] In one embodiment, the hub communicates with other devices in the monitoring environment that interface with the patient in various ways. For example, the hub advantageously receives serial data from other devices without requiring their reprogramming or the hub's reprogramming. Such other devices include pumps, ventilators, any type of monitor that monitors any combination of the aforementioned parameters, ECG / EEG / EKG devices, electronic patient beds, and the like. Additionally, the hub advantageously receives channel data from other medical devices without requiring their reprogramming or the hub's reprogramming. As devices communicate through channel data, the hub may advantageously modify the large display to include measurement information from the device. Additionally, the hub has access to a nurse call system to ensure that nurse call status from a device is passed to the appropriate nurse call system.
[0021] The hub also communicates with hospital systems, advantageously associating incoming patient measurement and treatment data with the patient being monitored. For example, the hub may communicate wirelessly or otherwise to a multi-patient monitoring system, such as a server or collection of servers, which may then communicate with a caregiver's data management system, such as, for example, an Admission Discharge Transfer ("ADT") system and / or an Electronic Medical Record ("EMR") system. The hub advantageously associates the data flowing therethrough with the patient being monitored, thereby providing electronic measurement and treatment information to be passed to the caregiver's data management system without the caregiver having to associate each device in the environment with a patient.
[0022] In one embodiment, the hub advantageously includes a reconfigurable, removable docking station that can accommodate docking of additional tiers of docking stations to accommodate different patient monitoring devices. In addition, the docking station itself is modularized so that it can be removed if the primary dockable portable patient monitor changes its form factor. Thus, the hub has flexibility in how its docking stations can be configured.
[0023] In one embodiment, the hub comprises mass memory for storing some or all of the data it receives, processes, and / or associates with patients, and / or the results of communications with other devices and systems, some or all of which may advantageously comprise removable SD memory.
[0024] The hub communicates with other devices through at least (1) a docking station for acquiring data from the portable monitor, (2) an innovative universal medical connector for acquiring channel data, (3) a serial data connector such as an RJ port for acquiring output data, (4) Ethernet, USB, and nurse call ports, (5) a wireless device for acquiring data from the portable monitor, and (6) other wired or wireless communication mechanisms known to those skilled in the art. The universal medical connector advantageously includes an optionally electrically isolated power supply and communication capability, which are designed to have a small cross-sectional area compared to the isolation requirements. The connector and hub communicate and advantageously translate or configure data from other devices to be usable and displayable to the hub. In one embodiment, a software development kit ("SDK") is provided to the device manufacturer to determine or define the behavior and meaning of the data output from the device. When the output is defined, the definition is programmed into a memory located on the cable side of the universal medical connector and supplied to the device provider as an original equipment manufacturer ("OEM"). When a cable is connected between the device and the hub, the hub understands the data and can use it for display and processing purposes without requiring software upgrades to the device or hub. In one embodiment, the hub can even negotiate the schema and add additional compression and / or encryption. Through the use of a universal medical connector, the hub organizes the measurement and treatment data into a single display and alarm system, effectively and efficiently sending commands to the monitoring environment.
[0025] As the hub receives and tracks data from other devices according to the channel paradigm, the hub may advantageously perform processing to create virtual channels of patient measurement or treatment data. In one embodiment, the virtual channels may include, for example, non-measured parameters that are the result of processing data from various measured or other parameters. An example of such parameters includes health indicators derived from various measured parameters that provide an overall indication of the health status of the patient being monitored. An example of health parameters is disclosed in U.S. Patent Application Nos. 13 / 269,296, 13 / 371,767, and 12 / 904,925, which are assigned to the assignee of the present disclosure and are incorporated herein by reference. By organizing the data into channels and virtual channels, the hub may advantageously synchronize the incoming data and the virtual channel data on a time basis.
[0026] The hub also receives serial data through a serial communication port, such as an RJ connector. The serial data is associated with the patient being monitored and passed to the multi-patient server system and / or the caregiver backend system described above. Through receiving the serial data, the caregiver advantageously associates devices in the caregiver environment, often from different manufacturers, with a particular patient, avoiding the need to associate each individual device with the patient and possible communication with hospital systems. Such association is important as it reduces the time the caregiver spends entering personal and demographic information about the patient into each device. Additionally, in one embodiment, through the SDK, the device manufacturer may advantageously provide information associated with the measurement delay of the device, thereby further enabling the hub to advantageously synchronize the serial incoming data and other data associated with the patient on an hourly basis.
[0027] In one embodiment, the hub effectively increases its display footprint when a portable patient monitor is docked and includes its own dedicated display. For example, in one embodiment, the portable patient monitor may simply continue to display its measurement and / or treatment data and be duplicated on the hub display, or the docked display may change its display to provide additional information. In one embodiment, the docked display, when docked, presents, for example, anatomical graphic data of the heart, lungs, organs, brain, or other body part being measured and / or treated. The graphic data may advantageously be animated to resemble and match the measurement data. For example, the lungs may expand in approximate correlation to the measured respiratory rate and / or determined inhalation / exhalation portions of the respiratory cycle, the heart may beat according to a pulse rate and generally in line with an understood actual cardiac contraction pattern, the brain may change color or activity based on changing sedation depth, or the like. In one embodiment, when a measured parameter indicates a need to alert a caregiver, a color changing severity may be associated with one or more displayed graphics, such as the heart, lungs, brain, organs, the circulatory system or portions thereof, the respiratory system or portions thereof, other body parts, or the like. In yet other embodiments, the body parts may include animations regarding where, when, or how to attach the measurement device.
[0028] The hub may also advantageously overlay a parameter display to provide additional image information to the caregiver. Such overlay may be user definable and configurable. This display may incorporate analog display icons or graphic indicia.
[0029] For purposes of clarity, not all features of an actual implementation are described herein. Those skilled in the art will of course appreciate that in developing such an actual implementation (as in a development project), numerous implementation-specific decisions must be made to achieve the developer's particular goals and subgoals, such as meeting system and business constraints, which may vary from implementation to implementation. Moreover, it will be appreciated that such development efforts may be complex and time-consuming, but are nevertheless a routine exercise in device design for those skilled in the art having the benefit of this disclosure.
[0030] To promote a thorough understanding of the present disclosure, in the remainder of the detailed description, the present disclosure will be described with reference to the drawings, in which like reference numerals refer to like elements throughout.
[0031] II. Exemplary Hub Embodiments 1A illustrates a monitoring environment including a perspective view of an exemplary medical monitoring hub 100 including an exemplary docked portable patient monitor (PPM) 102 according to one embodiment of the present disclosure. The hub 100 includes a display 104 and a docking station 106, which in one embodiment is configured to mechanically and electrically mate with the portable patient monitor 102, each housed within a movable, wearable, and portable housing 108. The housing 108 includes a generally upright, tilting shape configured to rest on a horizontal, flat surface, although the housing 108 may be affixed to a wide variety of positions and mounts and include a wide variety of shapes and sizes.
[0032] In one embodiment, the display 104 may present a wide variety of measurement and / or treatment data in numerical, graphical, waveform, or other display indicia 110. In one embodiment, the display 104 occupies most of the front surface of the housing 108, although one of ordinary skill in the art would understand that the display 104 may be in a table or tabletop horizontal configuration, a laptop-like configuration, or similar configuration. Other embodiments may include communicating the displayed information and data to a table computer, a smart phone, a television, or a display system understandable to one of ordinary skill in the art. The upright tilted configuration of FIG. 1A presents the displayed information in an easy-to-view manner to the caregiver.
[0033] 1B shows a side perspective view of one embodiment of the hub 100 including the housing 108, the display 104, and the docking station 106 without a portable monitor docked thereto. Also shown is a non-invasive blood pressure connector.
[0034] The portable patient monitor 102 of FIG. 1A is advantageously manufactured by Masimo Inc. of Irvine, Calif. No. 6,157,850, U.S. Pat. No. 6,334,065, and the like. The monitor 102 may communicate with a variety of non-invasive and / or minimally invasive devices, such as optical sensors with optical emission and detection circuitry, acoustic sensors, devices that measure blood parameters from a finger prick, cuffs, ventilators, and the like. The monitor 102 may include its own display 114 that presents its own display indicia 116, described below with reference to Figures 19A-19J. The display indicia may advantageously change based on the docked state of the monitor 102. When undocked, the display indicia may include parameter information and may change its orientation based on, for example, a gravity sensor or an accelerometer.
[0035] In one embodiment, the docking station 106 of the hub 100 includes a mechanical latch 118, or a mechanically releasable catch, to ensure that the monitor 102 is not mechanically detached or attached in a manner that could cause damage if the hub 100 is moved.
[0036] Although disclosed with reference to a particular portable patient monitor 102, those skilled in the art will appreciate from the disclosure herein that there are many different types of medical devices that may be advantageously docked with the hub 100. Additionally, the docking station 106 may advantageously be in electrical but not mechanical communication with the monitor 102 and / or communicate therewith in a wireless manner.
[0037] 2 shows a simplified block diagram illustrating an exemplary monitoring environment 200 including the hub 100 of FIG. 1, according to one embodiment of the disclosure. As shown in FIG. 2, the environment may include a portable patient monitor 102 in communication with one or more patient sensors 202, such as, for example, an oximetry optical sensor, an acoustic sensor, a blood pressure sensor, a respiration sensor, or the like. In one embodiment, additional sensors may communicate directly with the hub 100, such as, for example, an NIBP sensor or system 211 and a temperature sensor or sensor system 213. When in use, the sensors 202, 211, and 213 are typically in the vicinity of the patient being monitored if not actually attached to the patient's measurement site.
[0038] As disclosed, the portable patient monitor 102 communicates with the hub 100, in one embodiment through the docking station 106 when docked and in one embodiment wirelessly when undocked, although such undocked communication is not required. The hub 100 communicates with one or more multi-patient monitoring servers 204 or server systems, such as those disclosed by, for example, U.S. Patent Publication Nos. 2011 / 0105854, 2011 / 0169644, and 2007 / 0180140. In general, the server 204 communicates with a caregiver back-end system 206, such as an EMR and / or ADT system. The server 204 may advantageously obtain patient information entered at the time of patient admission, such as demographic information, billing information, and the like, through push, pull, or combination techniques. The hub 100 accesses this information to seamlessly associate the monitored patient with the caregiver back-end system 206. Communication between the server 204 and the monitoring hub 100 may be by any communication means recognizable to one of skill in the art from the disclosure herein, including wireless, wired, mobile or other computing networks, or the like.
[0039] 2 also shows the hub 100 communicating through a serial data port 210 and a channel data port 212. As disclosed in the above description, the serial data port 210 may provide data from a wide variety of patient medical devices, including an electronic patient bed system 214, an infusion pump system 216 including a closed loop control system, a ventilator system 218, a blood pressure or other vital signs measurement system 220, or the like. Similarly, the channel data port 212 may provide data from a wide variety of patient medical devices, including any of the aforementioned devices, as well as other medical devices. For example, the channel data port 212 may receive data from a depth of consciousness monitor 222, such as those commercially available from SEDLine, a brain or other organ oximeter device 224, a non-invasive blood pressure or acoustic device 226, or the like. In one embodiment, the channel device may comprise a board-in-cable ("BIC") solution, where the processing algorithms and the signal processing devices that perform those algorithms are mounted on a board housed within a cable or cable connector, which in some embodiments does not have additional display technology. The BIC solution outputs its measured parameter data to channel ports 212 for display on display 104 of hub 100. In one embodiment, hub 100 may be advantageously formed in whole or in part as a BIC solution that communicates with other systems, such as, for example, tablets, smartphones, or other computing systems.
[0040] Although disclosed with reference to a single docking station 106, the environment 200 may include stacked docking stations, where a subsequent docking station mechanically and electrically docks to the first docking station to change the form factor for different portable patient monitors as described with reference to Figure 5. Such a stack may include more than two docking stations and may reduce or expand the form factor to mechanically fit mating mechanical structures on the portable device.
[0041] Figure 3 illustrates a simplified exemplary hardware block diagram of the hub 100 of Figure 1, according to one embodiment of the present disclosure. As shown in Figure 3, the housing 108 of the hub 100 positions and / or contains an instrument board 302, a display 104, a memory 304, and various communication connections including a serial port 210, a channel port 212, an Ethernet port 305, a nurse call port 306, other communication ports 308 including standard USB or the like, and a docking station interface 310. The instrument board 302 comprises one or more boards including communication interconnects, wiring, ports, and the like to enable the communications and functions described herein, including inter-board communications. The core board 312 includes the primary parameters, signals, and other processors and memory, the portable monitor board ("RIB") 314 includes patient electrical isolation for the monitor 102 and one or more processors, the channel board ("MID") 316 controls communication with the channel port 212 including optional patient electrical isolation and power supply 318, and the radio board 320 includes components configured for wireless communication. In addition, the instrument board 302 may advantageously include one or more processors and controllers, buses, any type of communication connectivity and electronics, memory, memory readers including EPROM readers, and other electronics as would be recognized by one of ordinary skill in the art from the disclosure herein. Each board includes a substrate for positioning and support, interconnects for communication, controllers, electronic components including logic devices, hardware / software combinations, and the like to accomplish the tasks specified above and other tasks.
[0042] Those skilled in the art will appreciate from the disclosure herein that instrument board 302 may comprise numerous electronic components organized in numerous ways. The use of different boards, such as those disclosed above, can be advantageously used to organize and compartmentalize complex systems.
[0043] FIG. 4 illustrates a perspective view of an exemplary removable docking station 400 for the hub 100 of FIG. 1, according to one embodiment of the present disclosure. As shown in FIG. 4, the docking station 400 provides a mechanical fit to the portable patient monitor 102, providing secure mechanical support when the monitor 102 is docked. The docking station 400 includes a cavity 402 shaped similar to the periphery of the housing of the portable monitor 102. The station 400 also includes one or more electrical connectors 404 that provide communication with the hub 100. Although illustrated as being bolted on, the docking station 400 may be snap-fit, use movable tabs or catches, be magnetically attached, or employ a wide variety of attachment mechanisms or combinations of mechanisms known to those of skill in the art from the disclosure herein. In one embodiment, the attachment of the docking station 400 should be sufficiently secure that when docked, the monitor 102 and docking station cannot be accidentally detached in a manner that could damage the instrument, such as if the hub 100 is accidentally banged, and the monitor 102 and docking station 400 should remain intact.
[0044] The housing 108 of the hub 100 also includes a cavity 406 that houses the docking station 400. To the extent changes to the form factor for the portable patient monitor 102 occur, the docking station 400 is advantageously removable and replaceable. Like the docking station 400, the hub 100 includes an electrical connector 408 within the cavity 406 of the housing 108 that provides electrical communication to the docking station 400. In one embodiment, the docking station 400 includes its own microcontroller and processing capabilities, such as those disclosed in U.S. Patent Publication No. 2002 / 0140675. In other embodiments, the docking station 400 communicates through the electrical connector 408.
[0045] FIG. 4 also shows the housing 108 with an opening for a channel port 212 as a universal medical connector, which is described in more detail below.
[0046] FIG. 5 illustrates a perspective view of exemplary portable patient monitors 502 and 504 undocked from the hub 100 of FIG. 1 according to one embodiment of the disclosure. As shown in FIG. 5, the monitor 502 may be removed and other monitors, such as monitor 504, may be provided. The docking station 106 includes an additional docking station 506 that mechanically mates with the original docking station 106 and provides a form factor that is mechanically matable with the monitor 504. In one embodiment, the monitor 504 mechanically and electrically mates with the stacked docking stations 506 and 106 of the hub 100. As can be readily appreciated by those skilled in the art from the disclosure herein, the stackable feature of the docking stations provides the hub 100 with an extremely flexible mechanism for charging, communicating, and interfacing a wide variety of patient monitoring devices. As noted above, the docking stations can be stacked or, in other embodiments, removed and replaced.
[0047] FIG. 6 shows a simplified block diagram of a conventional patient electrical isolation principle. As shown in FIG. 6, a host device 602 is generally associated with a patient device 604 through communication and power sources. Since the patient device 604 often includes electronic devices near or connected to the patient, such as sensors or the like, certain safety requirements dictate that there should be no electrical path to the patient for electrical surges of energy, for example from the power grid connected to the host device. This generally refers to the term "patient isolation", known in the art, and includes herein the removal of a direct, uninterrupted electrical path between the host device 602 and the patient device 604. Such isolation is achieved, for example, through isolation devices 606 on the power conductors 608 and communication conductors 610. The isolation devices 606 can include transformers, optical devices that emit and detect light energy, and the like. The use of isolation devices, especially on the power conductors, can be expensive in terms of components, costly in terms of size, and waste power. Traditionally, isolation devices have been built into the patient device 604, however, patient devices 604 are trending towards smaller sizes and not all devices incorporate isolation.
[0048] FIG. 7A illustrates a simplified block diagram of an exemplary optional patient isolation system according to one embodiment of the present disclosure. As shown in FIG. 7A, a host device 602 communicates with an isolated patient device 604 through an isolation device 606. However, a memory 702 associated with a particular patient device informs the host 602 whether the device requires an isolated power source. If the patient device 708 does not require an isolated power source, such as some type of cuff, infusion pump, ventilator, or the like, the host 602 can provide a non-isolated power source through a signal path 710. This power source may be significantly more expensive than what can be cost-effectively provided through an isolated power conductor 608. In one embodiment, the non-isolated patient device 708 receives isolated communication because such communication is typically lower voltage and not cost-prohibitive. One skilled in the art will recognize from the disclosure herein that communication can also be non-isolated. Thus, FIG. 7A illustrates a patient isolation system 700 that provides optional patient isolation between the host 602 and a wide variety of potential patient devices 604, 708. In one embodiment, the hub 100 includes a channel port 212 that incorporates similar optional patient isolation principles.
[0049] FIG. 7B adds an exemplary optional non-isolated power level to the system of FIG. 7A according to one embodiment of the present disclosure. As shown in FIG. 7B, after the host 602 recognizes that the patient device 604 includes a self-isolated patient device 708 and therefore does not require isolated power, the host 602 provides power over a separate conductor 710. Since the power is not isolated, the memory 702 can also impose power requirements on the host 602, which may be a selection between two or more voltages or power levels. In FIG. 7B, the host 602 can have a wide range of voltages for the patient device 708, providing either high power, such as about 12 volts, but can have a wide range of voltages or very high power, such as about 24 volts or higher. Those skilled in the art will recognize that the power supply voltage can be advantageously varied to meet the specific requirements of virtually any device 708, and / or the memory can provide information to the host 602 that it has provided a wide range of non-isolated power to the patient device 708.
[0050] Further, using memory 702, the host 602 may determine to simply not enable any unused power sources, whether they are isolated power sources or one or more of the higher voltage non-isolated power sources, thereby increasing the efficiency of the host.
[0051] FIG. 8 illustrates a simplified exemplary universal medical connector configuration process 800 according to one embodiment of the present disclosure. As shown in FIG. 8, the process includes step 802, where a cable is attached to a universal medical connector incorporating optional patient isolation as disclosed in the above description. In step 804, the host device 602 or the hub 100, more specifically the channel data board 316 of the instrument board or an EPROM reader, reads the data stored in the memory 702 and determines in step 806 whether the connected device requires an isolated power source. When an isolated power source is required in step 808, the hub 100 may advantageously enable the isolated power source and enable isolated communications in step 810. When an isolated power source is not required in step 806, the hub 100 may simply enable a non-isolated power source in optional step 812 and enable isolated communications in step 810 in embodiments where communications remain isolated. In another optional embodiment, when an isolated power source is not needed in step 806, the hub 100 may use information from the memory 702 to determine the amount of power needed for the patient device 708 in step 814. When sufficient power is not available, a message may be displayed in step 816 indicating that the power source and power will not be provided, for example because other connected devices are also using the connected power source. When sufficient power is available, a non-isolated power source may be enabled in optional step 812. Alternatively, optional step 818 may determine whether the memory 702 indicates that higher or lower power is desired. When higher power is desired, the hub 100 may enable higher power in step 820, and when not, enable lower power in step 822. The hub 100 then enables isolated communication in step 810. In one embodiment, the hub 100 may simply determine how much power is needed in step 818 and provide at least enough power to the self-isolated device 708.
[0052] One skilled in the art would appreciate from the disclosure herein that hub 100 may not determine whether sufficient power is available or may supply one, two, or many levels of non-isolated voltage based on information from memory 702.
[0053] 9A and 9B show simplified block diagrams illustrating an exemplary universal medical connector 900 having a cross-sectional size and cross-sectional shape that is small relative to conventional isolation requirements. In one embodiment, the connector 900 physically separates non-isolated signals on one side 910 from isolated signals on the other side 920, although the sides can be reversed. The gap between such separation may be dictated at least in part by safety regulations governing patient isolation. In one embodiment, the distance between side 910 and side 920 may appear to be too small.
[0054] As can be seen from the different perspective of Figure 9B, the distance "x" between the connectors appears small. However, with this gap, this distance includes a non-direct path between the conductors. For example, a short must travel path 904, and the distance of such path is within or exceeds such safety regulations in that the distance is greater than "x". It is notable that the non-straight path 904 occurs throughout the connector, for example, at the board connector side where the solder connects the various pins to the PCB board.
[0055] Figure 10 illustrates a side perspective view of the hub 100 of Figure 1 showing an exemplary meter side channel input 1000 as an exemplary universal medical connector. As shown in Figure 10, the input includes a non-isolated side 910, an isolated side 920, and a gap. In one embodiment, the memory 702 communicates through pins on the non-isolated side.
[0056] Figures 11A-11K show various views of an exemplary male universal medical connector and a mating female universal medical connector according to an embodiment of the present disclosure. For example, Figures 11G1 and 11G2 show various preferred, but not required, sizing configurations, and Figure 11H shows the incorporation of electronic components such as memory 702 into the connector. Figures 11I-11K illustrate the wiring diagram when connecting to the universal medical connector and the cabling details of the cable itself.
[0057] FIG. 12 shows a simplified block diagram illustrating a channel system for the hub of FIG. 1, according to one embodiment of the disclosure. As shown in FIG. 12, a male cable connector, such as that shown in FIG. 11 above, includes a memory, such as an EPROM. The memory advantageously stores information describing the type of data the hub 100 may expect to receive and how to receive it. The controller of the hub 100 communicates with the EPROM to negotiate how to receive the data and, if possible, how to display the data on the display 104, alarms when necessary, and the like. For example, a medical device supplier may contact a hub provider and receive a software development kit ("SDK") that provides guidance to the supplier on how to describe the type of data output from the device. After working with the SDK, maps, images, or other translation files may advantageously be loaded into the EPROM, as well as the power and isolation requirements described above. When a channel cable is connected to hub 100 through channel port 212, hub 100 reads the EPROM and the controller in hub 100 negotiates how to handle the incoming data.
[0058] FIG. 13 illustrates an exemplary logical channel configuration that may be stored in the EPROM of FIG. 12. As illustrated in FIG. 13, each incoming channel describes one or more parameters. Each parameter describes anything the hub 100 needs to know about the incoming data. For example, the hub 100 may want to know whether the data is streaming data, waveform data, already determined parameter measurement data, ranges on the data, data delivery rates, units of data, steps of units, colors to display, alarm parameters and thresholds including complex algorithms for alarm calculations, other events driven by parameter values, combinations of these, or the like. Additionally, the parameter information may include device latency to aid in data synchronization or approximation of data synchronization between parameters or other data received by the hub 100. In one embodiment, the SDK presents a schema to the device supplier that self-describes the type and order of incoming data. In one embodiment, this information is advantageously negotiated with the hub 100 to determine whether compression and / or encryption should be applied to the incoming data stream.
[0059] Such an open architecture advantageously allows device manufacturers to port the output of devices to the hub 100 for display, processing, and data management as disclosed in the preceding description. By implementing through the cable connector, the device manufacturer avoids reprogramming its original device, but rather simply informs the hub 100 how the output already present through the cable connector is formatted. Furthermore, by describing the data in a language already understood by the hub 100, the hub 100 also avoids having to upgrade its software to accommodate data from medical devices that are "new to the hub."
[0060] Figure 14 illustrates a simplified exemplary process for configuring channels according to one embodiment of the present disclosure. As shown in Figure 14, the hub provider provides an SDK to the device manufacturer in step 1402, and the manufacturer then uses the SDK to self-describe the output data channel from the device in step 1404. In one embodiment, the SDK is a set of questions that guide development, while in other embodiments, the SDK provides a language and schema for describing data behavior.
[0061] After the device provider describes the data, the hub provider creates a binary image or other file to store in memory in the cable connector in step 1405, although the SDK may create the image and simply communicate it to the hub provider. The cable connector is provided to the provider as an OEM part in step 1410, and the provider fabricates and manufactures the cable to mechanically and electrically mate with the output port on the device in step 1412.
[0062] After the caregiver has a properly manufactured cable with one end matching the device provider's system and the other OEM end matching the hub 100 at its channel port 212, the caregiver can connect the hub between the devices in step 1452. In step 1454, the hub 100 reads its memory, provides isolated or non-isolated power, and the cable controller and hub 100 negotiate a protocol or schema for data delivery. In one embodiment, a controller on the cable may negotiate the protocol, and in an alternative embodiment, the controller of the hub 100 negotiates a particular protocol with another processor on the hub. After the protocol is set, the hub 100 can use, display, or otherwise process the incoming data stream in an intelligent manner.
[0063] Using the universal medical connector described herein, an unlimited number of devices can be connected to the hub 100 through direct programming of the cable connector as opposed to requiring software upgrades for each device.
[0064] FIG. 15 illustrates a perspective view of the hub of FIG. 1 including an exemplary attached board-in cable ("BIC") for forming an input channel, according to one embodiment of the disclosure. As shown in FIG. 15, the SEDLine Depth of Consciousness board communicates data from appropriate patient sensors to the hub 100 for display and review by the caregiver. As described, the board provider need only use the SDK to describe the data channels, and the hub 100 will understand how to present the data to the caregiver.
[0065] FIG. 16 illustrates a perspective view of the back of the hub 100 of FIG. 1 showing exemplary serial data inputs. In one embodiment, the inputs include RJ45 ports or the like. As understood in the art, these ports include data ports similar to those found on computers, network routers, switches, and hubs. In one embodiment, a number of these ports are used to associate data from various devices with a particular patient identified in the hub 100. FIG. 16 also illustrates a speaker, nurse call connector, Ethernet connector, USB, power connector, and medical ground terminal.
[0066] FIG. 17A illustrates an exemplary monitoring environment communicating through a serial data connection of the hub 100 of FIG. 1 according to one embodiment of the present disclosure. As shown and disclosed in the above description, the hub 100 may use the serial data port 210 to collect data from various devices in the monitoring environment, including electronic beds, infusion pumps, ventilators, vital signs monitors, and the like. The difference between the data received from these devices and the data received through the channel port 212 is that the hub 100 may not know the format or structure of this data. The hub 100 may not display information from this data or use this data in calculations or processing. However, porting the data through the hub 100 conveniently associates the data with the patient being specifically monitored throughout the chain of caregiver systems, including the server 204 and end systems 206 discussed above. In one embodiment, the hub 100 may determine enough information about the incoming data to attempt to synchronize that data with the data from the hub 100.
[0067] In Figure 17B, the control screen may provide information regarding the type of data being received. In one embodiment, a green light next to the data indicates the connection to the device and the serial input to which the connection is made.
[0068] FIG. 18 illustrates a simplified exemplary patient data flow process according to one embodiment of the disclosure. As illustrated, when a patient is admitted and enters the caregiver environment in step 1802, data about the patient is written to the caregiver backend system 206. The server 204 may advantageously obtain or receive this information in step 1804 and then make it accessible to the hub 100. When the caregiver assigns the hub 100 to a patient in step 1806, the caregiver simply looks at the currently available patient data and selects the particular patient currently being monitored. The hub 100 then associates the measurement, monitoring, and treatment data it receives and determines with that patient in step 1808. The caregiver does not need to assign another device to the patient again, as long as that device communicates through the hub 100 using (1) a docking station, (2) a universal medical connector, (3) a serial data connector, or (4) other communication mechanisms known to those skilled in the art. In step 1810, some or all of the received, processed, and / or determined data is passed to a server system as described above.
[0069] 19A-19J show exemplary displays of anatomical graphics for a portable patient monitor docked to the hub 100 of FIG. 1 according to an embodiment of the present disclosure. As shown in FIG. 19A, the heart, lungs, and respiratory system are shown while the brain is not highlighted. Thus, a caregiver can easily determine that a depth of consciousness monitoring or cerebral oximetry system is not currently communicating with the hub 100 through the portable patient monitor connection or channel data port. However, acoustic or other respiratory and cardiac data is likely being communicated to or measured by the hub 100. Additionally, a caregiver can easily determine that the hub 100 is not receiving alarming data for the highlighted body part. In one embodiment, the highlighted part may be animated to show the behavior currently being measured, or alternatively, animated in a predetermined manner.
[0070] FIG. 19B illustrates the addition of a virtual channel showing a health indicator. As shown in FIG. 19B, the indicator is positive as it is a "34" on an increasingly severe scale up to "100." The health indicator may also be shaded to indicate a problem. In contrast to FIG. 19B, FIG. 19C illustrates a health number that is becoming or has become a problem, and an alarming cardiac graphic. Thus, by a caregiver responding to the patient alarm on the hub 100, or some other response on another device or system monitoring or treating the patient, it can be quickly determined that a review of vital signs and other parameters related to cardiac function is required to diagnose and / or treat the patient.
[0071] Figures 19D and 19E show the brain included in the highlighted body parts, meaning that the hub 100 is receiving data related to brain function, such as, for example, sedation depth data or cerebral oximetry data, and Figure 19E additionally shows alarming cardiac function similar to Figure 19C.
[0072] In Fig. 19F, additional organs such as the kidneys are monitored, but not the respiratory system. In Fig. 19G, an alarmed cardiac function is illustrated, and in Fig. 19H, an alarmed circulatory system is illustrated. Fig. 19I illustrates the lungs, heart, brain, and kidneys along with health indicators. Fig. 19J illustrates the alarmed lungs, heart, and circulatory system as well as health indicators. Additionally, Fig. 19J illustrates severity contrast, e.g., the heart alarms in red for an emergency and the circulatory system alarms in yellow for a caution warning. Those skilled in the art will recognize other color schemes that are appropriate from the disclosure herein.
[0073] Figures 20A-20C show exemplary displays of measurement data showing data separation and data overlap, respectively, according to an embodiment of the present disclosure. Figures 21A and 21B show exemplary displays of measurement data also showing data separation and data overlap, respectively, according to an embodiment of the present disclosure.
[0074] For example, acoustic data from an acoustic sensor may advantageously provide respiratory sound data, although plethysmograph and ECG or other signals may also be displayed in separate waveforms (FIG. 20A, top of screen capture). The monitor may determine any of a wide variety of respiratory parameters of the patient, including respiratory rate, expiratory flow, tidal volume, minute volume, apnea duration, changes in respiratory sounds such as breath sounds, riles, rhonchi, wheezes, and volumetric reductions or changes in airflow. In addition, in some cases, the system monitors other physiological sounds, such as heart rate, heart sounds (S1, S2, S3, S4, and murmurs) that aid in probe-off detection, and changes in heart sounds such as normal to murmurs or split sounds that indicate fluid overload.
[0075] Providing visual correlation between multiple physiological signals can provide a number of valuable advantages where the signals have some observable physiological correlates. As one example of such correlation, changes in the morphology (e.g., envelope and / or baseline) of the plethysmographic signal can be indicative of the patient's blood or other bodily fluid level. These changes can also be monitored to detect hypovolemia or other fluid level related conditions. For example, a pleth variability index can provide an indication of bodily fluid levels. Changes in the morphology of the plethysmographic signal also correlate with respiration. For example, changes in the envelope and / or baseline of the plethysmographic signal correlate with respiration. This is due, at least in part, to aspects of human anatomy, such as the mechanical relationship and interaction between the heart and lungs during respiration.
[0076] Thus, by overlaying the plethysmograph signal with the respiratory signal (FIG. 20B), the operator can obtain an indication of the validity of the plethysmograph signal or a signal derived therefrom, such as a pleth variability index. For example, if bursts in the respiratory signal indicating inspiration and expiration correlate with changes in the peaks and valleys of the plethysmograph envelope, this provides a visual indication to the monitoring personnel that the plethysmograph changes are indeed due to breathing and not due to some other background factor. Similarly, if bursts in the respiratory signal align with peaks and valleys in the plethysmograph envelope, this provides an indication to the monitoring personnel that the bursts in the respiratory signal are due to patient breath sounds and not due to some other non-target sounds (e.g., non-patient breath sounds or non-patient sounds).
[0077] The monitor may also be configured to process the signals and determine if there is a threshold level of correlation between the two signals or to otherwise assess the correlation. However, by additionally providing a visual indication of the correlation, such as by showing the signals overlaid on one another, the display provides the operator with a continuous, intuitive, and easily observable metric of a particular physiological correlation. For example, by viewing the overlaid signals, a user can observe trends in correlation over time that may not otherwise be visible.
[0078] The monitor can show a visual correlation of a wide variety of other types of signals instead of or in addition to the plethysmograph and respiratory signals. For example, Fig. 20C shows a screenshot of another exemplary monitoring display. As shown in the upper right portion of Fig. 20C, this display superimposes the plethysmograph signal, the ECG signal, and the respiratory signal. In other configurations, more than three different types of signals can be superimposed on one another.
[0079] In one embodiment, the hub 100 provides an interface that allows the user to move the signals together so that they overlap each other. For example, the user may be able to drag and drop the respiratory signal onto the plethysmographic signal using a touch screen interface. Conversely, the user may be able to separate the signals, also using a touch screen interface. In another embodiment, the monitor includes a button that the user can press, or some other user interface that allows the user to overlap and separate the signals as desired. Figures 21A and 21B show a similar separation and combination of the signals.
[0080] In some configurations, in addition to providing a visual correlation between the plethysmographic signal and the respiratory signal, the monitor is further configured to process the respiratory and plethysmographic signals to determine a correlation between the two signals. For example, the monitor may process the signals to determine whether peaks and valleys of the envelope and / or baseline changes of the plethysmographic signal correspond to bursts in the respiratory signal. Then, in response to determining that there is or is not a threshold level of correlation, the monitor may provide some indication to the user. For example, the monitor may provide a graphical indication (e.g., a change in color of the pleth variability index indicator), an audible alarm, or some other indication. The monitor may employ one or more envelope detectors or other suitable signal processing components in making the determination.
[0081] In some embodiments, the system may further provide an audible indication of the patient's breathing sounds instead of or in addition to the graphic indication. For example, the monitor may include a speaker or an earpiece (e.g., a wireless earpiece) may be provided to monitoring personnel to provide an audible output of the patient sounds. Examples of sensors and monitors having such capabilities are described in U.S. Patent Publication No. 2011 / 0172561, which is incorporated herein by reference.
[0082] In addition to the advantages described above, presenting both the acoustic and plethysmographic signals on the same display in the manner described may enable monitoring personnel to more easily detect respiratory pause events, such as the absence of breathing, high environmental noise that may degrade the acoustic signal, improper sensor placement, etc.
[0083] 22A-22B show exemplary analog display indicia according to one embodiment of the present disclosure. As shown in FIGS. 22A and 22B, the screenshots display health indicators of various physiological parameters in addition to other data. Each health indicator can include an analog indicator and / or a digital indicator. In embodiments where the health indicators include analog and digital indicators, the analog and digital indicators can be positioned in any number of arrangements, such as side-by-side, above, below, transposed, etc. In the illustrated embodiment, the analog indicators are positioned above and next to the digital indicators. As more clearly shown in FIG. 22B, the analog display can include colored warning sections, dashes indicating a position on the graph, and digital information specifying quantity information from the graph. In FIG. 22B, for example, the pulse rate PR graph shows that there is a pulse rate of about 50 to about 140 beats per minute, and the graph is neutral or beginning to be in a caution state, but outside of these rates the graph is colored to indicate a critical state. Thus, as the dash moves along the arc, the caregiver can easily see where the current measurement falls within the acceptable, caution, and crisis ranges.
[0084] Each analog indicator of the health index may comprise a dial that moves through an arc based on the measured level of the physiological parameter being monitored. If the measured physiological parameter level increases, the dial may move clockwise, if the measured physiological parameter level decreases, the dial may move counterclockwise, or vice versa. In this manner, a user may quickly determine the patient's status by looking at the analog indicator. For example, if the dial is in the center of the arc, the observer may see that the current physiological parameter measurement is normal, if the dial is tilted too far to the left or right, the observer may quickly assess the severity of the physiological parameter level and take appropriate action. In other embodiments, a normal parameter measurement may be indicated when the dial is to the right or left, etc.
[0085] In some embodiments, the dial may be implemented as a dot, dash, arrow, or the like, and the arc may be implemented as a circle, spiral, pyramid, or other shape, as desired. Additionally, the entire arc may be lit or only a portion of the arc may be lit based on the current physiological parameter measurement level. Additionally, the arc may change color or be highlighted based on the current physiological parameter level. For example, as the dial approaches a threshold level, the arc and / or dial may change from green to yellow to red, become brighter, flash, become larger, move to the center of the display, or the like.
[0086] Different physiological parameters may have different thresholds that indicate an abnormal condition. For example, some physiological parameters may have elevated lower threshold levels, while others only have upper or lower thresholds. Thus, each health index may be adjusted based on the physiological parameter being monitored. For example, the SpO2 health index may have a lower threshold that activates an alarm when met, and the respiration rate health index may have both lower and upper thresholds, with an alarm being activated when either is met. The thresholds for each physiological parameter may be based on standard values, expected thresholds, and / or user-specified thresholds.
[0087] The digital index can provide a numerical representation of the current level of the physiological parameter, the digital index can indicate an actual or normalized level, and can also be used to quickly assess the severity of the patient's condition. In some embodiments, the display includes multiple health indexes for each monitored physiological parameter. In some embodiments, the display includes fewer health indexes than the number of monitored physiological parameters. In such embodiments, the health index can cycle between different monitored physiological parameters.
[0088] 23A-23F show exemplary displays of measurement data, for example showing the data representations of FIGS. 23A-23D, when a depth of consciousness monitor is connected to a channel port of the hub of FIG. 1. As shown in FIGS. 23A-23C, the hub 100 advantageously roughly branches its display 104 to show various information from a SEDLine device, for example, available from Masimo Corp., Irvine, Calif. In FIG. 23D, the hub 100 includes an attached PhaseIn device, available from PHASEIN AB, Sweden, providing information, for example, regarding the patient's respiration. The hub 100 also includes SEDLine information, and thus the hub 100 divides the display 104 accordingly. In FIG. 23E, temperature and blood pressure sensors communicate with the hub of FIG. 1, for which the hub 100 creates appropriate display footprints. In FIG. 23F, an acoustic sensor also communicates with the hub of FIG. 1, as well as the blood pressure and temperature sensors mentioned above. Thus, the hub 100 adjusts its display footprint to accommodate the data from each attached device.
[0089] The term "and / or" as used herein has its broadest, least restrictive meaning, meaning that the disclosure includes A alone, B alone, both A and B together, or A or B in the alternative, but not necessarily both A and B, or one of A or one of B. As used herein, the phrase "at least one of A, B, and C" should be construed to mean the logical A or B or C, using a non-exclusive logical OR.
[0090] The term "plethysmograph" includes its usual broad meaning as known in the art to include data responsive to changes in volume within an organ or the entire body, usually resulting from fluctuations in the amount of blood or air it contains.
[0091] III. Additional Monitoring Environment Embodiments FIG. 24 illustrates another embodiment of a monitoring environment 2000 including the hub 100 of FIG. 1. The monitoring environment 2000 may include all of the features of the monitoring environment 200 of FIG. 2 as well as any of the other features described above. In addition, the monitoring environment 2000 illustrates another embodiment of the multi-patient monitoring system 204, namely, a multi-patient monitoring system (MMS) 2004. The MMS 2004 includes a translation module 2005 that can receive serial data, translate the serial data into a format recognizable by the monitoring hub 100, and provide the serial data to the monitoring hub 100 (among other devices, as the case may be). Also illustrated are auxiliary devices 2040 that may communicate with the MMS 2004, the monitoring hub 100, or the PPM 102 in a wired or wireless manner.
[0092] As described above, the hub 100 may receive serial data from a wide variety of medical equipment, including a patient's bed 214, an infusion pump 216, a ventilator 218, and other vital signs monitors 220. The hub 100 may pass the serial data from these sources to the MMS 2004. As described above, the MMS 2004 may then store the serial data in a caregiver backend system 206, such as an EMR system or an ADT system.
[0093] The serial data may have a known data type, for example, defined based on the SDK described above. When the serial data comes from the medical device, the hub 100 or MMS 2004 can easily identify the data type and frequency. Exemplary data types may include: (1) waveform or high frequency data, (2) parameter data, and (3) event data. Advantageously, in some embodiments, instead of having a huge database containing various data types, a database may be designed based on known data types. The data acquisition process may differ based on the data type. For example, when the data is waveform or high frequency data, the hub 100 or MMS 2004 may not attempt to recover losses as the data comes in from the medical device. Rather, any data received may be streamed as it is acquired and stored in the database. Parameter data may come in (to the hub 100 or MMS 2004) at a particular frequency (e.g., every 1 Hz). As a result, the hub 100 or MMS 2004 may take a snapshot of the data at that frequency. Event data, such as a patient alarm (and optionally parameter data associated with the alarm), may be generated in response to a particular event. The event data may include a timestamp that may be associated with the time the data was taken or the time of the event. Additionally or alternatively, the hub 100 or MMS 2004 may also receive audio or video data associated with the patient.
[0094] The medical devices providing this serial data may use a wide variety of different proprietary protocols, messaging infrastructures, and the like that may not be natively recognizable by the hub 100. Thus, the hub 100 may not have the native capability to read parameter values or other data from the medical devices, and as a result, may not have the capability to display parameter values or other data from these devices. Advantageously, however, the translation module 2005 in the MMS 2004 can receive serial data from these devices, translate the serial data into a format recognizable by the monitoring hub 100, and provide the serial data to the monitoring hub 100. The monitoring hub 100 can then read the parameter values and other data from the translated information and output these values or data to a display, such as any of the displays described above.
[0095] In one embodiment, the translation module 2005 applies one or more translation rules to the serial data to translate or convert the serial data from one format to another. The serial data may be formatted according to the Health Level Seven ("HL7") protocol in one embodiment. The HL7 protocol was developed to provide a messaging framework for communication of clinical messages between medical computer systems and devices. However, the HL7 standard is highly flexible and only provides a framework of guidelines. As a result, medical devices or clinical computer systems that are all HL7 compliant may still not be able to communicate with each other. For example, the medical devices 214-220 may each implement a version of the HL7 protocol, but these implementations may differ from the HL7 protocol implemented by the monitoring hub 100. Thus, the monitoring hub 100 may not be able to parse or read messages from the medical devices 214-220 even though both use the HL7 standard. Additionally, the translation module 2005 may translate between different implementations of common standards other than the HL7 protocol implemented by the hub 100 and medical devices 214-220 in some embodiments.
[0096] In addition to translating between different implementations of a common electronic medical communication protocol (e.g., different formats of HL7 messages), the translation module 2005 can also translate between input and output messages that conform to different communication protocols. In some embodiments, the translation module 2005 can, for example, respond to a message from one medical communication protocol and translate it to a separate medical communication protocol. For example, the translation module 2005 can facilitate communication between messages sent according to the HL7 protocol, the ISO 11073 protocol, other open protocols, or proprietary protocols. Thus, the translation module 2005 can translate an input message sent according to the HL7 protocol to an output message that conforms to a different protocol, or vice versa. In some embodiments, the translation module 2005 can implement any of the translation features described in more detail below in the section entitled "Translation Module Implementations," and in U.S. Application No. 14 / 032,132, entitled "Medical Monitoring System," filed Sep. 19, 2013, the disclosure of which is incorporated herein by reference in its entirety.
[0097] Advantageously, in some embodiments, the translation module 2005 can receive the translated serial data back to the hub 100 or PPM 102. Because the translated data is in a format readable by the hub 100 or PPM 102, the hub 100 or PPM 102 can output the data from the medical devices 214-220 on a display of the hub 100 or PPM 102. In addition, the translation module 2005 can provide the translated data to devices other than the hub 100, including clinician devices (such as cell phones, tablets, or pagers) and auxiliary devices 2040, described below. Furthermore, because the serial data provided by the medical devices 214-220 can include alarm notifications, the translation module 2005 can pass these alarm notifications to the hub 100 or PPM 102. The hub 100 or PPM 102 can then generate visual or audible alarms in response to these alarm notifications. Additionally, the translation module 2005 can provide alarm notifications to clinician devices, for example, over a hospital network or a wide area network (such as the Internet). In addition, the translation module 2005 can provide alarm notifications to auxiliary devices 2040.
[0098] The translation module 2005 is shown implemented in the MMS 2004 because it may be beneficial to maintain and update the translation rules of the translation module 2005 in a single location. However, in other embodiments, the translation module 2005 may also (or instead) be implemented within the hub 100 or PPM 102. Thus, the hub 100 or PPM 102 may access the internal translation module 2005 to translate serial data for output to a display of the hub 100 or PPM 102.
[0099] The auxiliary device 2040 may also be a computing device having physical computer hardware, a display, and the like. For example, the auxiliary device 2040 may be a handheld computing device used by a clinician, such as a tablet, laptop, cell phone or smartphone, personal digital assistant (PDA), wearable computer (such as a smart watch or smart glasses), or the like. The auxiliary device 2040 may also simply be a display device, such as a computer monitor or digital TV. In one embodiment, the auxiliary device 2040 provides a second screen capability for the hub 100, the PPM 102, or the MMS 2004. As such, the auxiliary device 2040 may communicate with the hub 100, the MMS 2004, or the PPM 102 in a wireless manner or through a wired connection.
[0100] As a second screen device, the auxiliary device 2040 can show a copy of at least a portion of the hub 100 (or PPM 102) display or a different version of the hub 100 (or PPM 102) display. For example, the auxiliary device 2040 can receive physiological parameter data, trend data, or waveforms from the hub 100, PPM 102, or MMS 2004 and display the parameter data, trend data, or waveforms. The auxiliary device 2040 can output any information available to the hub 100, PPM 102, or MMS 2004. One use of the auxiliary device 2040 is as a clinician device that can be used by a clinician to view data from the hub 100, PPM 102, or MMS 2004 while away from the patient's room (or even while in the patient's room). The clinician can use the auxiliary device 2040 to view detailed information about the physiological parameters beyond what is displayed on the hub 100 or PPM 102 in one embodiment (see, e.g., FIG. 39). For example, the auxiliary device 2040 may be equipped with a zoom function or similar functionality that allows the clinician to zoom in on a trend or waveform to examine parameter activity more closely.
[0101] One exemplary reason for copying at least a portion of the display of the hub 100 or PPM 102 is to allow different clinicians to have the same view of the data during a surgical procedure. For example, in some surgical procedures, two anesthesiologists monitor a patient, one anesthesiologist monitors the patient's brain function and cerebral oxygenation, and another monitors the patient's peripheral oxygenation. A brain sensor as described above may be attached to the patient to provide brain monitoring and oxygenation data that is output to the hub 100 or PPM 102 for presentation to the first anesthesiologist. Finger or toe / foot light sensors may also be attached to the patient and output data to the hub 100 or PPM 102. For example, light sensors may be attached to the patient's body (e.g., fingers, toes, earlobes, forehead, and other sites). Light emitters may emit light that passes into body tissue, and detectors may receive light attenuated by body tissue to measure data of the patient's blood parameters. The hub 100 or PPM 102 can transmit this data to the auxiliary device 2040, which can be monitored by a second anesthesiologist to observe the oxygenation status in the patient's peripheral limbs. The second anesthesiologist may also need to know the oxygenation at the brain to aid in interpreting the severity of low peripheral oxygenation values or the lack thereof. However, in many surgical procedures, curtains or screens are placed over the patient as part of the procedure, obscuring the second anesthesiologist's view of the hub 100 or PPM 102. Thus, the hub 100 or PPM 102 can output a copy of at least a portion of its display to the auxiliary device 2040 so that the second anesthesiologist can monitor brain function or oxygenation status.
[0102] In one embodiment, the auxiliary device has a larger display area than the display of the hub 100. For example, the hub 100 may have a relatively small display, such as about 10 inches, while the auxiliary device 2040 may be a television monitor or the like with a display as large as 40 inches or larger (although any size display may be used for the auxiliary device 2040). In one embodiment, the auxiliary device 2040 as a television may comprise a hardware module comprising a processor, memory, and a wireless or wired networking interface or the like. The processor may execute programs from the memory, including programs for displaying physiological parameters, trends, and waveforms on the television's display. Because the television monitor is larger compared to the hub 100 embodiment, the television monitor version of the auxiliary device 2040 may display finer details of patient waveforms and trends in some embodiments (see, e.g., FIG. 39).
[0103] In another embodiment, the auxiliary device 2040 may display a portion of any of the displays described herein while the hub 100 displays another portion. For example, the auxiliary device 2040 may display any of the anatomical graphics described above with reference to FIGS. 19A-19J while the hub 100 displays any of the parameter displays described above with reference to FIGS. 20A-23F (or vice versa). Similarly, the auxiliary device 2040 may display translated data received from the translation module 2005 while the hub 100 displays channel data (or vice versa). In another embodiment, the auxiliary device 2040 may display both the translated data and the channel data (see, for example, FIG. 38).
[0104] In yet other embodiments, the auxiliary device 2040 may perform at least some of the processing of the physiological parameters, including any of the functions of the monitoring hub 100. For example, the auxiliary device 2040 may include and perform the features of the translation module 2005.
[0105] FIG. 25 illustrates one embodiment of a translated message processing process 2100. The process 2100 may be implemented by the translation module 2005 described above or by any other computing system. In one embodiment, at block 2502, the translation module 2005 receives a message from the hub 110 (or PPM 102), including a message from a medical device that is not natively compatible with the hub 100 (or PPM 102). At block 2504, the translation module 2005 translates the message based on one or more translation rules to create a translated output message that can be processed by the hub 100 (PPM 102). At block 2506, the translation module provides the translated output message to the hub 100 for display on the hub 100 (or PPM 102) or on the auxiliary device 2040. The hub 100 (or PPM 102) may route the translated data to the auxiliary device 2040, or the auxiliary device 2040 may receive the translated data directly from the translation module 2005.
[0106] For example, in one embodiment, a first medical device having a digital logic circuit receives a physiological signal associated with a patient from a physiological sensor, obtains a first physiological parameter value based on the physiological signal, and outputs the first physiological parameter value for display. The first medical device can also receive a second physiological parameter value from a second medical device different from the first medical device, where the second physiological parameter value is formatted according to a protocol not used by the first medical device, such that the first medical device cannot process the second physiological parameter value to generate a displayable output value. The first medical device can pass physiological parameter data from the first medical device to a separate translation module, receive translated parameter data from the translation module at the first medical device, where the translated parameter data can be processed for display by the first medical device, and output and display a second value from the translated parameter data. The first medical device may be, for example, the hub 100, the PPM 102, or the MMS 2004, and the second medical device may be an infusion pump 216 or a ventilator 218, or the like.
[0107] 26-38 and 46-71 show additional example hub displays, including displays of measurement data. Each of these displays may be implemented by the auxiliary device 2040, although similar displays may also be output directly on the hub 100 (or PPM 102). The example diagrams shown are shown as implemented on a tablet computer with touch screen capability. Touch screen capability is optional and may be replaced by other suitable input devices, such as a keyboard, mouse, track wheel, and the like.
[0108] 26, the user interface shown represents a device connected to an auxiliary device 2040. The device shown is an "Omar's Hawk," which may be one embodiment of the monitoring hub 100. The auxiliary device 2040 is wirelessly connected to the hub 100 in this embodiment to receive data from the hub 100. The auxiliary device may be wirelessly connected to the MMS 2004 or PPM 102 in other embodiments.
[0109] FIG. 27 shows a display of default parameters on the auxiliary device 2040. The parameter values are shown with their waveforms in the upper portion of the display, and other parameters (SpHb, SpMet, PVI, etc.) are shown at the bottom of the display without their corresponding waveforms. Any of these parameters at the bottom of the display can be dragged and dropped to the upper portion of the display to show a waveform. For example, FIG. 28 shows a similar display to FIG. 27 except that the SpHb parameter has been dragged and dropped to the upper portion of the display to show additional details about the SpHb waveform and alarm limits (18 and 7). Similarly, FIG. 29 shows the same display as FIG. 28 except that the SpHb parameter has been dragged and dropped to the upper portion of the display to show its waveform and alarm limits (3).
[0110] In each of the displays of Figures 27-29, a time window button is shown in the upper right corner. This time window button is shown as "1 hr" in Figures 27-29, but may be selected by the user to change the time window, which may affect the window of trend or waveform data shown in the display. User selection of this time window button and change to a 10 minute window is shown in Figure 30. As can be seen, the waveform in Figure 30 is shown in a smaller time window than in the previous figures.
[0111] FIG. 31 shows another version of the display of FIG. 29 with stacked waveforms, including stacked SpO2 and respiration waveforms, similar to other stacked waveforms described elsewhere herein. FIG. 32 shows a display similar to FIG. 29 with the pulse rate (PR) and SpMet (methemoglobin) parameters highlighted as being in an alarm state. The alarm state may be represented in one embodiment as a red box around the parameter value and waveform, or by making at least a portion of the box a transparent red color. The red box or transparency may also flash in one embodiment, and an audible alarm may be heard. Other methods of representing an alarm state are used in other embodiments.
[0112] 33 shows a pop-up interface that allows the user to adjust the alarm limits for a parameter (in this embodiment, SpHb or total hemoglobin). The pop-up interface includes a scroll wheel that allows the user to quickly scroll through the possible parameter limit values and select a value.
[0113] 34-38 show landscape display views as opposed to the portrait orientation displays of FIGS. 26-33. These landscape display views may be accessed by rotating the auxiliary device 2040 (e.g., tablet) to a landscape orientation. FIG. 34 shows a first set of parameters, while FIGS. 35 and 36 add additional parameters dragged and dropped with waveforms and additional alarm limit details similar to those described above with respect to FIGS. 27-29. FIG. 37 shows stacked parameter waveforms, stacking SpO2 and respiration waveforms. FIG. 38 shows both channel parameters (e.g., SpO2, PR (pulse rate), and RRa (acoustic measurement respiration rate)), but also shows translated serial data parameters 2210, including parameters from the pump and vent. These translated serial data parameters 2210 may have been received from the translation module 2005, either through the hub 100 or directly from the MMS 2004.
[0114] 24 , as described above, the hub 100 or PPM 102 may output a copy of at least a portion of the display to the auxiliary device 2040. In other embodiments, the hub 100 or PPM 102 may output data regarding a subset of all parameters shown on the hub 100 or PPM 102 to the auxiliary device 2040. For example, the hub 100 or PPM 102 may include the ability for a clinician to select one or more of the parameters displayed thereon and see only that parameter or parameters displayed on the auxiliary device 2040. Doing so may allow the auxiliary device 2040 to show more detail regarding the selected parameter or parameters, since fewer parameters are shown on the display of the auxiliary device 2040 compared to the hub 100 or PPM 102.
[0115] FIG. 39 illustrates one exemplary display of the auxiliary device 2040 showing data regarding one parameter, namely, respiration rate. Unlike the main display of the hub 100 or PPM 102, the display shown in FIG. 39 includes more than just the current value 2215 of respiration rate, recent trends 2230, and a small waveform. In addition, the display shows a histogram 2220 of the historical highs and lows (e.g., over the past few days) of the patient being monitored. In addition, a detailed waveform 2240 is illustrated, which may be larger than the waveform shown on the main display of the hub 100 or PPM 102, and may give the user more insight into the patient's respiratory status. The user may select to zoom in on the waveform 2240 (or other aspects of the display), which causes the waveform 2242 to expand to fill the display in place of other elements of the display, or the like. Other graphs, tables, waveforms, and data may be shown for the respiratory parameters on the auxiliary device display 2040. Of course, parameters other than respiration rate may also be selected for detailed display on the auxiliary device 2040. For example, the hub 100 or auxiliary device 2040 may indicate cerebral blood flow while the physician is performing the bypass procedure based on the output of the cerebral / organ oximetry (BIC) device 224. Advantageously, in some embodiments, the hub 100 or auxiliary device 2040 may allow the physician to easily view the cerebral blood flow and have time to confirm the adequacy of adequate perfusion to the patient while maintaining the physician's attention on the bypass circuit.
[0116] IV. TRANSLATION MODULE EMBODIMENTS Any of the following features described with reference to Figures 40A to 45D may be implemented by the translation module 2005 of Figure 24 or in conjunction with any of the devices described above with reference to Figure 24.
[0117] Healthcare costs continue to rise, as does the demand for affordable, high quality patient care. Healthcare costs can be reduced by increasing the effectiveness of hospital information systems. One factor that can affect the effectiveness of a healthcare facility is the extent to which the various clinical computer systems employed in the healthcare facility are able to interact with each other to exchange information.
[0118] Hospitals, patient care facilities, and healthcare delivery organizations typically include a wide variety of different clinical computer systems for managing electronic medical information. Each clinical computer system across the IT or management infrastructure can help accomplish a particular category or aspect of the patient care process. For example, a hospital may include patient monitoring systems, medical documentation and / or imaging systems, patient administration systems, electronic medical record systems, electronic medical procedure management systems, business and financial systems (such as pharmacy benefits and billing), and / or communications systems, etc.
[0119] The quality of care in a hospital or other patient care facility could be improved if different clinical computer systems across an IT infrastructure (or even in the same patient room, see, e.g., Figures 1 and 24) were able to effectively communicate with each other. This could allow patient data collected by one clinical computer system to be communicated to another clinical computer system that has access to such patient data. For example, this could allow decisions and actions related to patient care to be made based on a complete analysis of all available information.
[0120] In current practice, separate clinical computer systems can be, and often are, provided by different vendors, and as a result, the separate clinical computer systems may be implemented using dedicated network or communications infrastructures, dedicated communications protocols, etc., and the various clinical computer systems used in a hospital cannot necessarily communicate effectively with one another.
[0121] Medical device and medical system vendors sometimes develop proprietary systems that cannot effectively communicate with other vendors' medical devices and systems in order to increase market share and up-sell additional products, systems, and / or upgrades to healthcare providers. Thus, healthcare providers are forced to make enterprise-wide or system-wide purchasing decisions instead of selecting the best available technology for each type of individual clinical computer system they use.
[0122] One example of where this occurs is in the area of life-saving technology available for patient monitoring. For example, many different bedside devices for monitoring various physiological parameters are available from different vendors or providers. One such provider may offer best-in-class devices for monitoring a particular physiological parameter, while another such provider may offer best-in-class devices for another physiological parameter. Thus, in some situations, it may be desirable for a hospital to have the freedom to use monitoring devices from multiple manufacturers, but this may not be possible if the devices from different manufacturers cannot interface and exchange patient information. Thus, the ability to provide affordable, high-quality patient care may be compromised. In addition, each hospital or patient care facility may also implement its own proprietary communication protocols for the clinical computer network environment, which may further impede the exchange of information.
[0123] As described above, the Health Level Seven ("HL7") protocol was developed to provide a messaging framework for the communication of clinical messages between medical computer systems and devices. The HL7 communication protocol defines a number of standards, guidelines, and methods that various HL7-compliant clinical computer systems can use to communicate with each other.
[0124] The HL7 communication protocol has been adopted by many medical device manufacturers. However, the HL7 standard is very flexible and only provides a framework of guidelines (e.g., a high-level logical structure of messages), so that each medical device or medical system manufacturer or vendor may implement the HL7 protocol somewhat differently while still being HL7 compliant. For example, the format of an HL7 message may vary from implementation to implementation, as described in more detail herein. In some cases, an HL7 message of one implementation may also include information content that is not included in the message by another HL7 implementation. Thus, medical devices or clinical computer systems that are all HL7 compliant may still not be able to communicate with each other.
[0125] As a result, a translation module may be provided that can improve communication of medical messages between medical devices or systems that use different permitted implementations of established communication protocols (e.g., HL7), thereby enhancing the quality of patient care through the integration of multiple clinical computer systems.
[0126] 40A illustrates a first medical device 2405 and a second medical device 2410 communicating with each other via a translation module 2415. The first medical device 2405 is configured to transmit and receive messages according to a first permitted format or implementation of an accepted electronic medical communication protocol, while the second medical device 2410 is configured to transmit and receive messages according to a second permitted format or implementation of the electronic medical communication protocol. In some embodiments, the first and second protocol formats are different implementations of the HL7 communication protocol. Other electronic medical communication protocols besides HL7 can also be used.
[0127] The translation module 2415 receives input messages having a first protocol format from the first medical device 2405 and generates output messages to the second medical device 2410 having a second protocol format. The translation module 2415 also receives input messages having a second protocol format from the second medical device 2410 and generates output messages to the first medical device 2405 having the first protocol format. In this manner, the translation module 2415 can enable the first and second medical devices 2405, 2410 to communicate effectively and seamlessly with each other without necessarily requiring modifications to the communication equipment or protocols implemented by each device.
[0128] In some embodiments, the translation module 2415 determines an expected protocol format, for example by referencing a database that stores protocol formats used by the intended recipient of the input message based on information in the input message or by various devices, and then generates an output message based on the protocol format used by the intended recipient device or system. The output message may be generated based on comparison to and application of a set of translation rules 2420 accessible by the translation module 2415.
[0129] The translation module 2420 can include rules that determine how to handle changes that may occur between formatting implementations within a common protocol. Examples of changes in formatting embodiments of electronic medical communication protocols include, for example, the delimiter or separator characters used to separate data fields, whether certain fields are mandatory or optional, the repeatability of portions of a message (e.g., segments, fields, components, subcomponents), the order of portions of a message (e.g., order of fields or components), whether certain portions of a message are included, the length of a message or portions of a message, and the data types used for various portions of a message.
[0130] In some embodiments, the translation rules 2420 define additions, deletions, swapping, and / or modifications to be performed to "translate" an input message according to a first HL7 implementation into an output message according to a second HL7 implementation. The output message can have, for example, different formatting than the input message while maintaining all or part of the substance or content of the input message.
[0131] In addition to translating between different implementations of a common electronic medical communication protocol (e.g., different formats of HL7 messages), the translation module 2415 can also translate between input and output messages that conform to different communication protocols. In some embodiments, the translation module 2415 can, for example, respond to a message from one medical communication protocol and translate it to a separate medical communication protocol. For example, the translation module 2415 can facilitate communication between messages sent according to the HL7 protocol, the ISO 11073 protocol, other open protocols, and / or proprietary protocols. Thus, an input message sent according to the HL7 protocol can be translated to an output message that conforms to a different protocol, or vice versa.
[0132] The operation of the translation module 2415 and the translation rules 2420 are described in more detail below. Next, various embodiments of system architectures that include the translation module 2415 are described.
[0133] In some embodiments, the first medical device 2405, the second medical device 2410, and the translation module 2415 are communicatively coupled via a connection to a common communications network or directly (via cable or wirelessly) through, for example, the hub 100, the PPM 102, and / or the MMS 2004. In some embodiments, the translation module 2415 may be communicatively coupled between the first medical device 2405 and the second medical device 2410 (with or without a communications network) such that all messages between the first medical device 2405 and the second medical device 2410 are routed through the translation module 2415. Other architectures are possible.
[0134] The first medical device 2405 and the second medical device 2410 and the translation module 2415 may be included, for example, as part of the monitoring environment of Figure 1 or Figure 24 described above. The first medical device 2405 may be, for example, an infusion pump 216 or a ventilator 218, while the second medical device 2410 may be, for example, a monitoring hub 100, a PPM 102, an MMS 2004, or an auxiliary device 2040. The translation module 2415 is one exemplary implementation of the translation module 2005.
[0135] In some embodiments, the translation module 2415 can facilitate communication across multiple networks within a hospital environment. In other embodiments, the translation module 2415 can facilitate communication of messages across one or more networks that extend outside of the hospital or clinical network environment. For example, the translation module 2415 can provide a communication interface with financial institutions, insurance providers, government agencies, outside pharmacies, other hospitals, nursing homes or patient care facilities, physician offices, and the like.
[0136] In some embodiments, the translation module 2415 of FIG. 40 can be a component of the environment 2000 described above, for example, with respect to FIG. 24. For example, the translation module 2415 can be communicatively coupled to a hospital network or other network or monitoring environment described above. In such embodiments, the translation module 2415 can facilitate the exchange of patient monitoring information, including, for example, physiological parameter measurements, physiological parameter trend information, and physiological parameter alarm status, between bedside medical monitor devices, monitoring nurse stations, hospital or clinical information systems (which may store electronic medical records), and / or many other medical devices and systems. The translation module 2415 can enable seamless communication between different medical devices and systems, each of which may use different implementations of electronic medical communication protocols, such as, for example, the HL7 communication protocol, within a clinical or hospital network environment.
[0137] In some embodiments, the translation module 2415 may also facilitate communication between a first medical device that is part of the patient monitoring subsystem and a second medical device that is not part of or external to the patient monitoring system 200. As such, the translation module 2415 may be capable of responding to externally generated medical messages (such as patient information update messages, status inquiry messages, and the like from an HIS or CIS) and generating external reporting messages (such as event reporting messages, alarm notification messages, and the like from a patient monitor or monitoring nurse station).
[0138] In another embodiment, the first medical device 2405 and the second medical device 2410 communicate with each other over a communication bus 2421. The communication bus 2421 may include any one or more of the communication networks, systems, and methods described above, including the Internet, a hospital WLAN, a LAN, a personal area network, etc. For example, any of the networks described above may be used to facilitate communication between multiple medical devices, including the first medical device 2405 and the second medical device 2410 described above. One such embodiment is illustrated in FIG.
[0139] In Figure 40B, a first medical device 2405 sends a message to the communication bus 2421. The message is intended to be received by a second medical device 2410, but because the first medical device 2405 and the second medical device 2410 communicate according to different communication protocol formats, the second medical device 2410 cannot process the message.
[0140] The translation module 2415 monitors the communication bus 2421 for such a message. The translation module receives the message and determines that the first medical device 2405 is attempting to communicate with the second medical device 2410. The translation module 2415 determines that a message translation will facilitate communication between the first medical device 2405 and the second medical device 2410. Thus, the translation module 2415 utilizes appropriate translation rules stored in the translation module 2420. The translation module 2420 can comprise a memory, an EPROM, a RAM, a ROM, etc.
[0141] The translation module 2415 translates the message from the first medical device 2405 according to any of the methods described herein. After translating, the translation module 2415 delivers the translated message to the communication bus 2421. The second medical device 2410 receives the translated message and responds accordingly. For example, the second medical device may perform functions and / or attempt to communicate with the first medical device 2405. The translation module 2415 facilitates communication from the second medical device 2410 to the first medical device 2405 in a similar manner.
[0142] The first medical device 2405 and the second medical device 2410 can be, for example, any of the medical devices or systems communicatively coupled to the hospital network or hub 100, the PPM 102, and / or the MMS 2004. These medical devices or systems can include, for example, point-of-care devices (such as bedside patient monitors), data storage units or patient record databases, hospital or clinical information systems, centralized monitoring rooms (such as monitoring nurse stations), and / or clinician devices (such as pagers, cell phones, smart phones, personal digital assistants (PDAs), laptops, tablet PCs, personal computers, pods, and the like).
[0143] In some embodiments, the first medical device 2405 is a patient monitor that communicatively couples to a patient for tracking physiological parameters (e.g., oxygen saturation, pulse rate, blood pressure, etc.), and the second medical device 2410 is a hospital information system ("HIS") or clinical information system ("CIS"). In some embodiments, the patient monitor can communicate physiological parameter measurements, physiological parameter alarms, or other physiological parameter measurement information generated during monitoring of the patient to the HIS or CIS for inclusion in the patient electronic medical record maintained by the HIS or CIS.
[0144] In some embodiments, the first medical device 2405 is a HIS or CIS and the second medical device 2410 is a monitoring nurse station, as described herein. However, the translation module 2415 can facilitate communication between a wide variety of medical devices and systems used in a hospital or other patient care facility. For example, the translation module 2415 can facilitate communication between patient physiological parameter monitoring devices, between monitoring devices and monitoring nurse stations, etc.
[0145] Using the translation module 2415, a patient monitoring subsystem as described herein (e.g., physiological monitoring system 200) can push data to or pull data from an HIS even if the HIS uses a different implementation of the HL7 protocol, or some other electronic medical communication protocol.
[0146] In some embodiments, the patient monitoring subsystem may be configured to push / pull data at predefined intervals. For example, the patient monitor or bedside monitoring station may automatically download patient data from the HIS at regular intervals such that the patient data is already available when the patient is connected to the patient monitor. Patient data transmitted from the HIS may include Admission / Discharge / Transfer ("ADT") information received after the patient is registered. ADT messages are initiated by the hospital information system and may inform the auxiliary systems, for example, that a patient has been admitted, discharged, transferred, or registered, that patient information has been updated or merged, or that a transfer or discharge has been cancelled.
[0147] In other embodiments, the patient monitoring subsystem may be configured to push data to / pull data from the HIS only when the HIS is requested via a query, for example, a clinician may make a request for information stored in the patient's electronic medical record on the HIS.
[0148] In yet other embodiments, the patient monitoring subsystem may be configured to push data to / pull data from the HIS in response to unsolicited events. For example, a monitored patient physiological parameter may enter an alarm state, which may be automatically transmitted to the HIS and stored in the patient electronic medical record. In still other embodiments, any combination of the above methods or alternative methods may be employed to determine when to communicate messages to and from the HIS.
[0149] An example system architecture and example triggers for communication of messages involving the translation module 2415 have already been described. Turning now to the operation of the translation module, Figures 25A-25D show example medical messages at different phases or steps of the translation process. The translation process is described in more detail below with respect to Figures 26, 27A, and 27B.
[0150] 41A illustrates an exemplary ADT input message 2505 received by the translation module 2415 from the HIS. The ADT input message 2505 is implemented according to the HL7 communication protocol and includes information related to a patient's admission to a hospital. The ADT message 2505 includes a number of segments, including a message header segment 2506, an event segment, a patient identification segment, a patient encounter segment, a job segment, a diagnosis segment, and a number of custom segments.
[0151] In some embodiments, the message header ("MSH") segment 2506 defines how the message is sent, the field delimiters and encoding characters, the message type, the sender and recipient, etc. The first symbol or character after the MSH string may define the field delimiter or separator (in this message, the "caret" symbol). The next four symbols or characters may define the encoding characters. The first symbol defines the component delimiter ("~"), the second symbol defines the repeatable delimiter ("|"), the third symbol defines the escape delimiter ("\"), and the fourth symbol defines the subcomponent delimiter ("&"). All of these delimiters may vary from one HL7 implementation to another.
[0152] In some embodiments, the exemplary header segment 2506 further includes a sending application ("VAFC PIMS"), a receiving application ("NPTF-508"), a message date and time ("20091120104609-0600"), a message type ("ADT- A01"), a message control ID ("58103"), a transaction ID ("P"), and a country code ("USA"). As represented by the successive caret symbols, the header segment also includes a number of empty fields.
[0153] 41B illustrates the message header segment 2506 after it has been parsed into fields or elements based on the identified field delimiters (caret symbols). In some embodiments, the parsed input message includes an XML message that is configured to be transformed according to Extensible Stylesheet Language Transformation (XSLT) rules.
[0154] In some embodiments, the parsed input message may be encoded. Figure 41C illustrates a parsed message header segment of an input message after it has been encoded (e.g., using the Unicode Transformation Format-8 ("UTF-8") encoding scheme).
[0155] The encoded message header segment illustrates some of the various data types that can be used within the message. For example, the third parsed field's sending application ("VAFC PIMS") and the fifth parsed field's receiving application ("NPTF-508") are represented using the hierarchical designator ("HD") name data type. The date and time field (the seventh parsed field) is represented using the timestamp ("TS") data type. The transaction ID field (the eleventh parsed field) is represented using the transaction type ("PT") data type. Fields that do not contain a data type identifier are represented using the string ("ST") data type. Other possible data types include, for example, coding element, structured numeric value, timing quantity, text data, date, input identifier, coding value, numeric value, and sequence identifier. The data types used for the various fields or attributes of the segment may vary from one formatting implementation to another.
[0156] 41D illustrates an example output message 2510 from the translation module 2415 based on the example input message 2505 of FIG.
[0157] Turning to the operation of the translation module, the translation module 2415 can, for example, create, generate, or form an output message that reflects the input message based on application of a set of translation rules 2420. In some embodiments, the translation module 2415 can, for example, translate, transform, convert, reformat, compose, modify, rearrange, modify, adapt, alter, or adjust the input message based on comparison to and application of the set of translation rules 2420 to form the output message. In some embodiments, the translation module 2415 can, for example, replace or substitute the input message with an output message that retains the content of the input message, but has a new formatting implementation based on comparison to and application of the set of translation rules 2420.
[0158] 42 illustrates an example translation process 2600 for generating an output message based on a comparison of an input message to a set of translation rules 2420 associated with a translation module 2415. The translation process 2600 begins at block 2602, where the translation module 2415 receives an input message from a first medical device.
[0159] In block 2604, the translation module 2415 determines the formatting implementation of the input message and the formatting implementation to be used for the output message. In some embodiments, the input message can include one or more identifiers indicating the formatting implementation. In some embodiments, the determination of the formatting implementation can be made by analyzing the message itself, for example, by identifying delimiters or encoding characters used, field order, repetitiveness of segments, fields, or components, data types of fields, or other implementation changes. In some embodiments, the translation module 2415 can separate or parse out the formatting from the content of the message (as shown in FIG. 41B) to aid in determining the formatting implementation. In some embodiments, the translation module 2415 determines the formatting implementation of the input message by referencing a database that stores the implementation used by each device with which the translation module 2415 is configured to interface.
[0160] In some embodiments, the determination of the formatting implementation to be used by the output message can also be made from the input message. For example, the input message can include a field that identifies the intended recipient application, facility, system, device, and / or destination. The input message can alternatively include a field that identifies the type of message being sent (e.g., an ADT message), and the translation module 2415 can determine the appropriate recipient and / or sending application, device, or system from the type of message being sent. The translation module 2415 can then determine the formatting implementation required by the intended recipient of the input message.
[0161] In decision block 2605, the translation module 2415 determines whether a rule set is configured for translating from the identified formatting implementation of the input message to the identified formatting implementation to be used for the output message. The rule set may be manually configured prior to installation of the translation module software or may be automatically configured prior to receiving the input message. If a rule set is already configured, the translation process 2600 continues at block 2606. If a rule set is not configured, the rule set is configured at block 2607. The configuration of the rule set may be performed as described below with respect to Figures 44 and 45A-D. The translation process 2600 then continues at block 2608.
[0162] In block 2606, the translation module 2415 identifies a pre-configured rule from the set of translation rules 2420 that governs the translation between the determined formatting implementation of the input message and the formatting implementation of the output message. In some embodiments, the identification of the pre-configured rule may be performed manually.
[0163] At block 2608, the translation module 2415 generates an output message based on a configured rule set of translation rules 2420. In some embodiments, the output message retains all or at least a portion of the content of the input message but has a format expected and supported by the intended recipient of the input message.
[0164] The translation rules 2420 can include, for example, one-way rules and / or two-way rules. One-way rules can be applied, for example, in the case of a message from a first medical device (e.g., 2405) to a second medical device (e.g., 2410), but not in the case of a message from a second medical device to a first medical device. For example, one-way rules can handle, for example, differences in delimiters used between fields for two different formatting implementations of the HL7 communication protocol. The translation module 2415 can apply field delimiters to determine whether the field delimiters are supported by the intended recipient of the input message. If the field delimiters of the input message are not supported by the intended recipient, the field delimiter rules can replace the delimiters of the fields of the input message with field delimiters supported by the intended recipient.
[0165] For example, an input message from an input medical device may include a formatting implementation that uses a "caret" symbol ("^") as a field delimiter or separator. However, a formatting implementation recognized by an intended recipient medical device may use a "pipe" symbol ("|") as a field delimiter. The translation module 2415 can identify the field delimiter used in the formatting implementation recognized by the intended recipient medical device from a set of translation rules 2420 and generate an output message based on the input message that uses the pipe field delimiter instead of the caret field delimiter used in the input message. The rule substituting the pipe symbol for the caret symbol in this case applies only to messages sent to recipient devices that recognize the pipe symbol as a field delimiter. This rule can be accompanied by a supplemental rule indicating that the caret symbol should be used instead of the pipe symbol for messages directed to recipient devices known to recognize the caret symbol as a field delimiter.
[0166] Another one-way rule can handle the presence or absence of some fields between different formatting implementations. For example, an input message from an input medical device can contain fields that are not recognized by the intended recipient medical device. The translation module 2415 can generate an output message that does not contain the unrecognized or unsupported fields. In a situation where the input message does not contain a field expected by the intended recipient medical device, the set of translation rules 2420 can include rules that insert a null entry or an empty "" string in the field expected by the intended recipient medical device and / or alert the recipient device that the expected field is not present. The sender device can also be notified by the translation module 2415 that the recipient device does not support some parts of the message.
[0167] Other one-way rules can facilitate, for example, conversion from one data type to another (e.g., string ("ST") to text data ("TX") or structured numeric ("SN") to numeric ("NM")), and increasing or decreasing the length of various parts of a message. One-way rules can also be used to handle variations in the repetitiveness of parts of a message. For example, the translation module 2415 can apply field repeatability rules to repeating instances of a message segment, field, component, or subcomponent to determine how many such repeating instances, if any, are supported by the recipient device, and to remove or add any repeating instances if necessary. For example, a phone number field of a patient identification segment can be made a repeatable field to allow for entry of home, work, and mobile phone numbers.
[0168] Bidirectional rules may also be used. Such rules may apply equally to messages between a first medical device and a second medical device (e.g., 2405, 2410) regardless of which device is the sender and which device is the recipient. Bidirectional rules may be used, for example, to handle order changes. In some implementations, an incoming message from an input medical device may include one or more patient name fields in which the first name component appears before the last name component. However, the intended recipient medical device may expect an implementation in which the last name component appears before the first name component. Thus, the set of translation rules 2420 may include bidirectional rules that swap the order of the first and last name components when communicating between two medical devices or between two formatting implementations. In general, field order rules are applied to determine whether fields, components, or subcomponents are in the correct order for the intended recipient, and may be reordered if necessary. Other bidirectional rules may be included to handle other sequential changes, for example, between formatting implementations or other types of changes.
[0169] The translation rules 2420 may also include compound word rules. For example, compound word rules may include if-then series of rules, where rules may depend on the results of other rules. Some of the translation rules 2420 may use calculations and logic (e.g., Boolean logic or fuzzy logic), and the like.
[0170] As described above, messages transmitted over the hospital-based communication network may employ the HL7 protocol. Figures 43A and 43B show translation processes 2700A, 2700B in which HL7 messages are transmitted between the HIS and medical devices over the hospital-based communication network or clinical network. The translation processes 2700A, 2700B are described assuming that rules governing "translation" between a first HL7 format and a second HL7 format have already been configured.
[0171] FIG. 43A shows a translation process 2700A in which a translation module 2415 facilitates transmission of an HL7 message, such as the ADT message of FIG. 41A, from an HIS having a first HL7 format to an intended recipient medical device, such as a patient monitor or clinician monitoring station, having a second HL7 format.
[0172] The translation process 2700A begins at block 2701 where the translation module 2415 receives an input message having a first HL7 format from an HIS. In some embodiments, the input message includes, for example, information regarding a patient's admission and / or patient identification, and patient history information from an electronic medical record database.
[0173] In block 2703, the translation module 2415 determines the formatting implementation of the input message and the formatting implementation to be used for the output message. These determinations may be made in a manner similar to the determinations described above with respect to block 2604 of FIG.
[0174] In block 2705, the translation module 2415 identifies rules governing the translation between the determined HL7 format of the input message and the HL7 format of the output message and generates an output message having a second HL7 format based on the identified rules. In some embodiments, the output message retains the content of the input message sent by the HIS but has a format expected and supported by the intended recipient of the input message.
[0175] In block 2707, the translation module 2415 may output the outgoing message to the intended recipient over the hospital-based communications network. In some embodiments, the intended recipient may send an acknowledgement message back to the hospital information system acknowledging successful receipt or reporting that an error occurred.
[0176] 43B illustrates a translation process 2700B in which the translation module 2415 facilitates communication of an HL7 message from a medical device, such as a patient monitor, having a first HL7 format to an HIS having a second HL7 format. For example, the patient monitor can transmit reporting event data, such as patient alarm data, to the HIS for storage in the patient's electronic medical record.
[0177] The translation process 2700B begins at block 2702 where the translation module 2415 receives an input message having a first HL7 format from a medical device. In some embodiments, the input message includes patient monitoring data or alarm data related to one or more physiological parameters of a monitored patient for storage in an electronic medical record database associated with the HIS.
[0178] In block 2704, the translation module 2415 determines the formatting implementation of the input message and the formatting implementation to be used for the output message. These determinations may be made in a manner similar to the determinations described above with respect to block 2604 of FIG.
[0179] In block 2706, the translation module 2415 identifies rules governing the translation between the determined HL7 format of the input message and the HL7 format of the output message and generates an output message having a second HL7 format based on the identified rules. In some embodiments, the output message retains the content of the input message sent by the medical device but has a format expected and supported by the HIS.
[0180] At block 2708, the translation module 2415 may output the output message to a hospital information system over a hospital-based communications network. In some embodiments, the HIS may send an acknowledgement message back to the medical device acknowledging successful receipt or reporting that an error occurred.
[0181] 42, 43A, and 43B are diagrams for explaining the operation of the translation module 2415. FIG. 44 and FIGS. 45A to 45D are used to illustrate the explanation of the configuration of the translation rules 2420.
[0182] The translation rules 2420 may be implemented as one or more stylesheets, hierarchical relational data structures, tables, lists, other data structures, combinations thereof, and / or the like. In some embodiments, the translation rules 2420 may be stored in local memory within the translation module 2415. In other embodiments, the translation rules 2420 may be stored in external memory or in a data storage device communicatively coupled to the translation module 2415.
[0183] The translation module 2415 can include a single rule set or multiple rule sets. For example, the translation module 2415 can include a separate rule set for each medical device / system and / or for each possible communication pair of medical devices / systems that are coupled to a network or that can be coupled to a network. In some embodiments, the translation module 2415 can include a separate rule set for each possible pair of formatting implementations allowed under a medical communication protocol, such as, for example, the HL7 protocol.
[0184] In some embodiments, the translation rules 2420 may be entered manually, for example, using a messaging implementation software tool 2800 illustrated in Figure 44. For example, a software developer for a particular hospital network may determine the protocol message formats used by devices and / or systems that are or may be coupled to the hospital network, and then manually enter rules to facilitate "translation" between the various protocol message formats supported or recognized by the devices and / or systems.
[0185] FIG. 44 shows an example screenshot from a messaging implementation software tool 2800 for manually configuring translation rules 2420 to be used by the translation module 2415. The screenshot from the messaging implementation software tool 2800 illustrates various parameters that may vary for each formatting implementation of an electronic medical communication protocol, such as HL7. The screenshot also includes an area where a user can enter information used to define or define translation rules for conversion between different HL7 implementations. In some embodiments, the messaging implementation software tool 2800 stores a wide variety of pre-configured rule sets based, for example, on known communication protocol implementations of various medical devices. In such embodiments, a user may configure one or more translation rules 2420 to be used in communications involving such devices by entering identifying information, such as device manufacturer, model number, etc. Based on this identifying information, the messaging implementation tool 2800 may identify a pre-configured set of translation rules for communicating with that device.
[0186] In other embodiments, the translation rules 2420 may be generated automatically. For example, automatic generation of a new set or sets of rules may be triggered by the detection of a newly recognized "communicating" medical device or system on the network. In some embodiments, automatic generation of a new set or sets of rules may occur when a first message is received from or transmitted to a new "communicating" medical device or system coupled to the network. In yet other embodiments, automatic generation of a rule set includes updating or dynamically modifying a pre-existing set of rules.
[0187] The automatic generation of the translation rule set may be performed in a wide variety of ways. For example, in some embodiments, the translation module 2415 may automatically begin using a previously configured set of translation rules 2420 based, for example, on the make and model of a new device recognized on the network. In some embodiments, the translation module 2415 may request one or more messages from the new device or system and then analyze those messages to determine the type of formatting implemented, as illustrated by the automatic rule configuration process 2900A in FIG. 45A. The automatic rule configuration process 2900A begins at block 2901, where the translation module 2415 receives one or more messages from a medical device or system detected on the network. The messages may be received after being transmitted to the intended recipient medical device or system, or in response to a query sent by the translation module 2415 or another medical device or system coupled to the network.
[0188] In block 2903, the translation module 2415 determines the protocol of one or more received messages, for example, by analyzing the message or by consulting a database indicating what communication protocols / formats are implemented by each medical device or system on the network. In some embodiments, the translation module 2415 is configured to handle medical messages that are implemented using a single common protocol, such as HL7. Thus, if a determination is made that the received message is implemented using an unsupported or unrecognized protocol, the translation module can ignore the message received from the detected medical device or system, output a warning or alert, or allow the message to be sent without translation.
[0189] In block 2905, the translation module 2415 determines the formatting implementation of the received message. In some embodiments, the received message may include one or more identifiers indicating the formatting implementation. In other embodiments, the determination of the formatting implementation may be made by analyzing the message itself, for example, by checking field order, delimiters or encoding characters used, or other implementation changes. In some embodiments, the translation module 2415 may separate or parse out the formatting from the contents of the message to aid in determining the formatting implementation.
[0190] In block 2907, the translation module 2415 configures one or more rules or rule sets to handle messages received from and / or sent to the detected medical device or system. In some embodiments, configuring the rules involves creating or generating new rules. In other embodiments, configuring the rules involves modifying or updating existing rules. The configured rules or rule sets may be included with the translation rules 2420. If a set of rules already exists for the formatting implementation used by the new device or system, it may not be necessary to configure new translation rules. Instead, the existing translation rules may be associated with the new device or system and used in communications involving that device or system. In other embodiments, the translation module 2415 may create a new set of rules tailored in a way that is specific to the new device or system, or may modify the existing set of rules based on the identified slight changes in formatting.
[0191] In other embodiments, the translation module 2415 can generate test messages that can be useful in identifying the communication protocol and implementation used by a device or system. For example, the translation module can cause a newly discovered device or system to perform a particular action (e.g., store information) and then query information about the action performed by the newly discovered device to determine whether or how the test message was understood. This is illustrated by the automatic rule configuration process 2900B in FIG. 45B.
[0192] The automatic rule configuration process 2900B begins at block 2902, where the translation module 2415 transmits one or more test, or initialization, messages to remote devices or systems discovered on the network. The test messages may be configured, for example, to instruct the remote devices or systems to perform a particular action (e.g., store patient information). In some embodiments, the test messages may be configured to generate a response indicating a type of formatting recognized or supported by the remote devices or systems. In other embodiments, the test messages may be configured such that only devices or systems that support a particular formatting implementation will understand the test message and perform an appropriate action on the test message.
[0193] In block 2904, the translation module 2415 queries the remote device or system to receive information regarding actions to be taken based on the test message sent to the remote device or system to determine whether the test message was understood. For example, if the test message instructs the remote device or system to store patient information in a particular location, the translation module 2415 may query information from that location to determine whether the test message was understood. If the test message was not understood, the translation module 2415 may, for example, continue to send the test message in a known formatting implementation until a determination is made that the test message was understood.
[0194] In block 2906, the translation module 2415 determines a protocol and formatting implementation based on the received information. As an example, in some embodiments, the test message may include instructions to store patient name information. The test message may comprise a patient name field having a first name component followed by a last name component. The translation module 2415 may then query the remote device or system to return the patient's last name. Depending on whether the patient's last name or first name is returned, this query may be useful in determining information regarding the order of fields in the formatting implementation being used by the remote device or system. As another example, the test message may instruct the detected device or system to store repeated instances of a component. The translation module 2415 may query the device or system to return repeated instances to see which, if any, are stored. This repeatability information may also be useful in determining whether a particular field is allowed to be repeated in the formatting implementation being used by the remote device or system, and if so, how many repeated instances are allowed.
[0195] In block 2908, the translation module 2415 configures one or more rules to handle messages received from and / or sent to the detected medical device or system. For example, the rules may convert messages from a message format used by a first medical device to a message format used by a second medical device, as described herein. In some embodiments, configuring the rules involves creating or generating new rules. In other embodiments, configuring the rules involves modifying or updating existing rules. If a set of rules already exists for the formatting implementation used by the new device or system, it may not be necessary to configure new translation rules. Instead, the existing translation rules may be associated with the new device or system and used in communications involving that device or system.
[0196] 29C and 29D illustrate the automatic rule configuration process performed by the translation module 2415 for messages utilizing the HL7 protocol. The HL7 protocol can be used, for example, to convey electronic messages that support administrative, logistical, financial, and clinical processes. For example, HL7 messages can include patient management messages, such as ADT messages, that are used to exchange patient demographic and visit information across various healthcare systems.
[0197] The automatic rule configuration process 2900C illustrated in Figure 45C is similar to the process 2900A illustrated in Figure 45A. At block 2911, the translation module 2415 receives one or more messages from the HL7 medical device. At block 2915, the translation module 2415 determines a formatting implementation of the HL7 medical device from the received one or more messages. As described above, the determination of the formatting implementation may be made by, for example, checking the order or sequence of fields, field delimiters, repeatability, cardinality, and other HL7 implementation changes.
[0198] At block 2917, the translation module 2415 configures one or more rules to handle messages received from and / or sent to the HL7 medical device. In some embodiments, configuring the rules involves creating or generating new rules for the detected formatting implementation. In other embodiments, configuring the rules involves dynamically modifying or updating existing rules. If a set of rules already exists for the formatting implementation used by the new HL7 medical device, it may not be necessary to configure new translation rules. Instead, the existing translation rules may be associated with the new HL7 medical device and used in communications involving that device.
[0199] The automatic rule configuration process 2900D illustrated in FIG. 45D is similar to the process 2900B illustrated in FIG. 45B. In block 2912, the translation module 2415 transmits one or more test, dummy, or initialization messages to the HL7 medical device. In other embodiments, the translation module 2415 may cause one or more test messages to be transmitted from another HL7 medical device to the new HL7 medical device. As described above, the test message may include a message having a known HL7 format that is configured to determine whether the HL7 device understands the test message. The test message may include, for example, a test ADT message.
[0200] In block 2914, in response to the test message, the translation module 2415 queries the HL7 medical device and receives information regarding actions to be performed or stored information. In block 2916, the translation module 2415 determines a formatting implementation of the HL7 device based on the received information. In some embodiments, the translation module 2415 can analyze the received information and determine whether one or more test messages were properly understood. If none of the test messages were properly understood, the translation module 2415 can send additional test messages having other known HL7 formats and repeat blocks 2914 and 2916.
[0201] At block 2918, the translation module 2415 configures one or more translation rules to handle messages received from and / or sent to the detected HL7 medical device. In some embodiments, configuring the translation rules involves creating or generating new translation rules. In other embodiments, configuring the rules involves modifying or updating existing rules. If a set of translation rules already exists for the formatting implementation used by the new HL7 medical device, it may not be necessary to configure new translation rules. Instead, the existing translation rules may be associated with the new HL7 medical device and used in communications involving the HL7 medical device.
[0202] The automatic rule configuration process described above may be triggered by detection of a network device or system by the translation module 2415. The medical devices referenced in Figures 45A-45D may include any of the devices or systems illustrated in Figures 1 or 24.
[0203] In some embodiments, automatic generation of translation rules may advantageously occur after installation and compilation of messaging subsystem software, including translation module 2415. In some embodiments, automatic generation or dynamic modification of translation rules 2420 may occur without recompiling or rebuilding the translation module software. This feature may be advantageous with respect to efficiently complying with U.S. Food and Drug Administration ("FDA") requirements for validation of software used in healthcare environments.
[0204] Consider, for example, a situation where a medical device manufacturer plans to use the translation module 2415 to facilitate communication between a particular medical device or system (e.g., a patient monitoring system, as described herein) or other patient care equipment to be installed in a hospital and other devices or systems (e.g., an HIS or CIS) already installed in the hospital. Any software required for operation of the new medical device to be installed can be at least partially validated for FDA compliance prior to installation in the hospital despite the fact that, for example, the HL7 implementation of other existing devices or systems in the hospital may still be unknown. For example, any aspect of the software for the new medical device that relies on receiving messages from other hospital devices can be validated prior to installation as being fully and correctly capable of operating when the expected message format is received. Then, after the medical device is installed in the hospital, validation of the software can be accomplished by showing that the translation module 2415 can provide messages in the expected format to the newly installed device. In this way, the FDA validation task can be largely allocated to a pre-installation time frame where it can be more easily performed in a controlled manner rather than in the field.
[0205] In addition, the translation module 2415 can further streamline FDA validation efforts, for example, when a medical device or system is expected to be installed in different hospitals where existing devices use different implementations of, for example, the HL7 protocol. Normally, this type of situation may impose a requirement that the entire functionality of the software for the new medical device be fully validated at each hospital. However, when the translation module 2415 is used to interface between the new medical device and the hospital's existing devices, most of the software functionality can possibly be validated only once before installation, as just described. Then, after installation at each hospital, validation of the software for the medical device can be accomplished by verifying that the correct message format is received from the translation module (field-customizable translation rules). This can result in a significantly more efficient field validation procedure, which advantageously enables more efficient FDA compliance to administer life-saving medical technologies to patients more quickly by using field-customizable translation rules.
[0206] V. Exemplary Embodiments In some embodiments, a system for providing medical data translation results for output on a medical monitoring hub may include a portable physiological monitor comprising a processor capable of receiving a physiological signal associated with a patient from a physiological sensor, calculating a physiological parameter based on the physiological signal, and providing a first value of the physiological parameter to the monitoring hub for display. The monitoring hub may include a docking station capable of receiving the portable physiological monitor. The monitoring hub may receive a first value of the physiological parameter from the portable physiological monitor, output and display the first value of the physiological parameter, receive physiological parameter data from a medical device other than the portable physiological monitor, where the physiological parameter data is formatted according to a protocol other than a protocol natively readable or displayable by the monitoring hub, pass the physiological parameter data to a translation module, receive translated parameter data from the translation module, where the translated parameter data may be readable and displayable by the monitoring hub, and output and display a second value from the translated parameter data.
[0207] The system of the previous paragraph may be combined with any subcombination of the following features, including: the monitoring hub is further configured to output the first value of the physiological parameter and a second value from the translated parameter data to separate displays, the monitoring hub is further configured to output the second value from the translated parameter data to an auxiliary device having a display separate from the display of the monitoring hub, the auxiliary device is selected from the group consisting of a television, a tablet, a phone, a wearable computer, and a laptop, the physiological parameter data includes data from an infusion pump, the physiological parameter data includes data from a ventilator, and the translation module is configured to translate the physiological parameter data from a first Health Level Seven (HL7) format to a second HL7 format.
[0208] In some embodiments, a method of providing medical data translation results for output on a medical monitoring hub may include receiving, under control of a first medical device comprising digital logic circuitry, a physiological signal associated with a patient from a physiological sensor, obtaining a first physiological parameter value based on the physiological signal, outputting and displaying the first physiological parameter value, receiving a second physiological parameter value from a second medical device different from the first medical device, where the second physiological parameter value is formatted according to a protocol not used by the first medical device such that the first medical device is unable to process the second physiological parameter value to generate a displayable output value, passing the physiological parameter data from the first medical device to a separate translation module, receiving translated parameter data from the translation module in the first medical device, where the translated parameter data can be processed for display by the first medical device, and outputting and displaying a second value from the translated parameter data.
[0209] The method of the previous paragraph may be combined with any subcombination of the following features, which are as follows: further including translating the message by translating at least the message from a first Health Level Seven (HL7) format to a second HL7 format, where the message may include data from a physiological monitor, where the message may include data from an infusion pump or a ventilator, and where the message may include data from a hospital bed.
[0210] In some embodiments, a system for providing medical data translation results for output on a medical monitoring hub can include a first medical device, the device acquiring a first physiological parameter value associated with a patient, outputting and displaying the first physiological parameter value, receiving a second physiological parameter value from a second medical device different from the first medical device, the second physiological parameter value being formatted according to a protocol not used by the first medical device such that the first medical device is unable to process the second physiological parameter value to generate a displayable output value, passing physiological parameter data from the first medical device to a translation module, receiving translated parameter data from the translation module at the first medical device, the translated parameter data being capable of being processed for display by the first medical device, and electronic hardware capable of outputting and displaying a second value from the translated parameter data.
[0211] The system of the previous paragraph may be combined with any subcombination of the following features, where the first medical device may output the first value of the physiological parameter and the second value from the translated parameter data on the same display, the first medical device may output the first value of the physiological parameter and the second value from the translated parameter data on separate displays, the first medical device may output the second value from the translated parameter data to an auxiliary device, which may be a television monitor, which may be selected from the group consisting of a tablet, a phone, a wearable computer, and a laptop, the first medical device may comprise a translation module, the first medical device may also pass the physiological parameter data to the translation module over a network, and the physiological parameter data may include data from an infusion pump or a ventilator.
[0212] VI. Augmented Reality Embodiments Today's patient monitoring environments provide one or more conventional displays or screens for clinicians to present data from one or more electronic medical devices associated with a wide variety of monitoring, treatment, or procedures on a patient. Thus, during such patient monitoring, treatment, or procedures, the clinician typically looks at one or more conventional displays to gather information about the patient. However, while the clinician is looking at one or more conventional displays, the clinician's attention may be diverted from the patient, such as when the clinician is performing a surgical procedure and the clinician looks away from the patient to look at the conventional display. For example, during certain surgical procedures, such as an endoscopy or epidural, the clinician performing the procedure would normally look at the patient to see where the probe is going, but the clinician must look away from the patient to look at the conventional display, which is inefficient.
[0213] The systems and methods described herein may advantageously use augmented reality in some embodiments to improve the presentation of data or provide an improved interactive user interface. For example, a clinician using an augmented reality device, such as wearable augmented reality glasses, is presented with medical monitoring data that may be received from a medical monitoring hub as described herein. In some embodiments, an advantage of augmented reality is that the augmented reality display overlays real-world visual information. Thus, the clinician can remain visually focused on the patient while simultaneously receiving the augmented reality information. In some embodiments, an advantage of augmented reality is that the display area for the augmented reality user interface is larger than a conventional display, such as a device screen. For example, the augmented reality display area may be 10 times larger than a conventional display area. The following is an example of an improved augmented reality user interface.
[0214] An exemplary augmented reality device presents one or more user interfaces. Exemplary user interfaces that may be presented on an augmented reality device include any of the user interfaces described herein. Additionally, the augmented reality user interface may improve the efficiency of a surgical procedure. For example, during some procedures, such as an endoscopic or epidural, a clinician can efficiently maintain line of sight on the patient to see where the probe is going, while simultaneously viewing an overlay user interface that includes data that was previously only available on a traditional display. In some embodiments, the augmented reality user interface may be pinned to a particular area in three-dimensional space or within a patient room. For example, a clinician interactively manipulates an augmented reality device to pin the augmented reality user interface to a physical device, location, or patient. Continuing with this example, a clinician using an augmented reality device sees the pinned augmented reality user interface when looking near the physical device or pinned location, but the augmented reality user interface is not presented when the clinician looks away from the physical device or its location. In some embodiments, the auxiliary device 2040 may be optional, or any information displayed on the auxiliary device 2040 may be presented through an augmented reality device.
[0215] Another example of an improved user interface using augmented reality is to present analog display indicia as a superimposition on the patient. Exemplary analog display indicia that may be presented on an augmented reality device include any of the analog display indicia described herein. Exemplary analog display indicia, such as a two-dimensional or three-dimensional lung, heart, brain, or circulatory system, may be superimposed on the patient. Thus, the clinician will see the superimposed analog display indicia when looking at the patient. In some embodiments, the analog display indicia is pinned to the patient such that the analog display indicia is not presented if the clinician looks away from the patient. As described herein, the analog display indicia may present health indicators of various physiological parameters. Exemplary health indicators include color-coded analog display indicia, such as green, yellow, or red indicia, which may indicate nominal, caution, or critical conditions, respectively, which are described in more detail herein.
[0216] In some embodiments, the improved augmented reality user interface allows a user to configure or interact with the user interface. For example, the augmented reality user interface may be a dashboard that allows a user to add or remove certain virtual display panels or change the configuration or location of augmented reality panels or objects. The augmented reality device may receive user input corresponding to a user interaction. Exemplary user interactions include voice input or commands, visual or eye commands, touch input, or movements such as head movements or hand gestures. Exemplary head gestures include head tilts, head nods, or nodding. As another example, a clinician may receive augmented reality patient data when outside a patient's room or area. In an example, a clinician passing by a patient's room interacts with the augmented reality device to receive data about the patient or from an electronic medical device in the patient's room. Continuing with this example, the clinician performs a hand gesture to virtually grab the patient's data, causing the augmented reality device to present the data without entering the patient's room. As another example, the patient data may be virtually posted outside the room. Additionally or alternatively, in some embodiments, patient data may be available anywhere within the medical facility, or even remotely, such as when the clinician is tens or hundreds of miles away from the patient's physical location.
[0217] Additional exemplary user interfaces and systems for patient monitoring and notification are disclosed in US patent application Ser. No. 14 / 511,972, which is assigned to the assignee of the present disclosure and is incorporated herein by reference.
[0218] FIG. 72A illustrates another embodiment of a monitoring environment 7202 including the hub 100 of FIG. 1 and the devices of FIG. 24. The monitoring environment 7202 may include all or some of the features of the monitoring environment 200 of FIG. 2 or the monitoring environment 2000 of FIG. 24, as well as any of the other features described above. In addition, the monitoring environment 7202 illustrates a multi-patient monitoring system (MMS) 2004. The MMS 2004 includes a translation module 2005 that can receive serial data, translate the serial data into a format recognizable by the monitoring hub 100, and provide the serial data to the monitoring hub 100 (and possibly other devices). Also illustrated is an auxiliary device 2040 that may communicate with the MMS 2004, the monitoring hub 100, or the PPM 102 in a wired or wireless manner. Similarly, the augmented reality device 7200 may communicate with the MMS 2004, the monitoring hub 100, or the PPM 102 in a wired or wireless manner.
[0219] Exemplary augmented reality devices 7200 include augmented reality glasses, a head-mounted display, a head-up display, contact lenses, a smartphone, or a tablet. The augmented reality devices 7200 may include some combination of one or more hardware processors, displays, sensors, or input devices. For example, the augmented reality devices 7200 may include a camera, an accelerometer, a gyroscope, a GPS device, or a solid-state compass. The augmented reality devices 7200 may include one or more wired or wireless devices that enable communication over one or more networks, such as Bluetooth, USB, a wired network, or a Global System for Mobile Communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Long Term Evolution (LTE) network, Wi-Fi, or some other type of wireless network. In some embodiments, the augmented reality devices 7200 may communicate with an augmented reality server (not shown), which may handle some augmented reality processing. Thus, the exemplary augmented reality devices may offload some or all of the augmented reality processing to be performed by the augmented reality server in a distributed manner.
[0220] FIG. 72B illustrates an example augmented reality user interface 7204. The example augmented reality user interface 7204 comprises one or more augmented reality user interface objects. As described herein, the medical monitoring system may receive one or more physiological signals associated with a patient being monitored via one or more physiological sensors. The medical monitoring system may calculate physiological parameters based on the physiological signals. The augmented reality device 7200 or another device in the medical monitoring environment may generate one or more augmented reality user interface objects from the physiological monitoring data, including the physiological parameters. As described herein, the physiological monitoring data may update in a real-time or near real-time manner, and thus the augmented reality user interface objects displaying the physiological monitoring data may update in a real-time or near real-time manner. In some embodiments, a clinician using the augmented reality device may configure the augmented reality user interface. For example, the augmented reality device may receive user inputs corresponding to user interactions that configure the augmented reality user interface. Exemplary user configurations of the augmented reality user interfaces include adding or removing augmented reality objects, changing the position of the augmented reality objects, cycling through different augmented reality user interfaces, or selecting a particular augmented reality user interface, for example, a first augmented reality user interface corresponds to a first collection of augmented reality objects for monitoring patient physiological data, a second augmented reality user interface corresponds to a second collection of augmented reality objects for presenting patient medical history, or a third augmented reality user interface corresponds to a third collection of augmented reality objects for presenting patient demographic data.
[0221] 72C illustrates another exemplary augmented reality user interface 7206. The exemplary augmented reality user interface 7206 includes one or more augmented reality objects 7208 and an augmented reality display area 7210. As described herein, the exemplary augmented reality object 7208 includes an analog display indicia superimposed on the patient. For example, the augmented reality object 7208 corresponds to a color-coded visual representation of the patient's lungs to indicate the status of the patient's lungs. The patient may be connected to or worn by one or more devices 7214, which are further connected to another device 7212, which may correspond to, for example, a hub, a monitoring system, or a conventional display. In some embodiments, an augmented reality system, such as the augmented reality device 7200 or an augmented reality server, determines the location of the augmented reality object 7208 based on location information derived from one or more devices 7214. For example, the one or more devices 7214 may include tracking sensors, such as an accelerometer, GPS, gyroscope, solid-state compass, RFID, or wireless sensors. Additionally or alternatively, one or more devices 7214 may include visual markers that can be detected by the augmented reality device 7200 for image registration, or the patient may wear one or more visual markers for image registration. In some embodiments, a clinician using the augmented reality device 7200 may pin the augmented reality display area 7210 to the device 7212. The augmented reality display area 7210 may include any of the example user interfaces described herein.
[0222] The augmented reality system may determine the position of the augmented reality display area 7210 based on visual markers or tracking sensors associated with the device 7210, as well as visual markers or tracking sensors associated with the patient or one or more devices 7214. As described herein, an example augmented reality system determines the position of the augmented reality display area 7210 by identifying a reference object, here the device 7212, determining a reference position relative to the reference object, and calculating a position offset from the reference position. In some embodiments, the position offset may be calculated as a predetermined or configurable distance and direction from the reference object. Continuing with this example, a clinician using an augmented reality device may change or update the position offset of the augmented reality display area 7210.
[0223] 72D and 72E show additional example augmented reality user interfaces 7216A and 7216B, respectively. The example augmented reality user interfaces 7216A and 7216B may be similar to the augmented reality user interface 7206 of FIG. 72C. As illustrated, the example augmented reality user interfaces 7216A and 7216B include user interface display areas 7218A and 7218B, respectively, which include user interface objects 7220A and 7220B, respectively. The example user interface objects 7220A and 7220B may correspond to example user interfaces described herein.
[0224] FIG. 72F illustrates an augmented reality display generation process 7222. Process 7222 illustrates an exemplary mode of operation of environment 7202 of FIG. 72A and may be implemented by various components illustrated in environment 7202, such as augmented reality device 7200, or by an augmented reality server separate from augmented reality device 7200. For convenience, process 7222 is described in the context of environment 7202 (such as being implemented by augmented reality device 7200 or by an augmented reality server, referred to herein as an augmented reality system), but may instead be implemented by other systems described herein or other computing systems not illustrated. Additionally, process 7222 provides an exemplary approach that augmented reality device 7200 or an augmented reality server may use to generate an augmented reality display. Depending on the embodiment, the process of FIG. 72F may include fewer or additional blocks, or the blocks may be performed in a different order than illustrated.
[0225] At block 7224, the augmented reality system server initiates a connection with the communication interface. For example, the augmented reality device 7200 may connect wired or wirelessly to a communication interface of the MMS 2004, the monitoring hub 100, or the PPM 102. In some embodiments, the augmented reality device 7200 must be authenticated via one or more security protocols before a connection with the communication interface can be established.
[0226] At block 7226, the augmented reality system receives data from the communication interface. As described herein, example data includes physiological monitoring data, which may include physiological parameter data from the patient calculated from physiological signals captured by physiological sensors monitoring the patient.
[0227] At block 7228, the augmented reality system formats the received data for presentation. For example, the augmented reality system may access user interface configuration data indicating which augmented reality objects should be displayed or the placement of the augmented reality objects. In some embodiments, a clinician using the augmented reality device 7200 may update or modify the user interface configuration data through one or more user interactions with the augmented reality device 7200 as described herein. Thus, the augmented reality system may format the received data, such as physiological monitoring data, into user interface display data according to the user interface configuration data. For example, the augmented reality system generates one or more augmented reality objects from the physiological monitoring data according to the user interface configuration data that specifies which objects should be generated or where the objects should be presented on the display of the augmented reality device.
[0228] The augmented reality system presents the formatted data in a display of the augmented reality device at block 7230. An exemplary augmented reality user interface is shown and described in further detail with reference to Figures 72B-72E.
[0229] At block 7232, the augmented reality system receives and processes the input data. Exemplary input data includes user interaction data received from the augmented reality system. For example, a clinician may interactively manipulate the augmented reality user interface to modify the user interface. Thus, the augmented reality system may return to block 7226 to receive additional data, continue processing the user interaction data, display data, or monitoring data, and present an updated augmented reality user interface. For example, the augmented reality user interface may update in near real-time or in real-time based on the physiological sensors capturing updated data from the patient or from new data received from the MMS 2004, the monitoring hub 100, or the PPM 102.
[0230] FIG. 72G illustrates an augmented reality position determination process 7234. Process 7234 illustrates an example mode of operation of environment 7202 of FIG. 72A and may be implemented by various components illustrated in environment 7202, such as augmented reality device 7200, or by an augmented reality server separate from augmented reality device 7200. For convenience, process 7234 is described in the context of environment 7202 (e.g., implemented by an augmented reality system), but may instead be implemented by other systems described herein or other computing systems not illustrated. Additionally, process 7234 provides an example approach by which an augmented reality system is used to determine a position relative to one or more augmented reality objects. Depending on the embodiment, the process of FIG. 72G may include fewer or additional blocks, or the blocks may be performed in a different order than illustrated. Additionally, the blocks of process 7234 may correspond to one or more blocks of process 7222 of FIG. 72F, such as blocks 7226, 7228, 7230, or 7232.
[0231] At block 7236, the augmented reality system receives input data. Exemplary input data includes tagged or pinned reference objects or locations. Exemplary tagged and pinned reference objects may correspond to one or more physical objects, such as an auxiliary display, a device of a monitoring system, or a patient. Additionally or alternatively, exemplary input data includes location or positional data, such as image data, video data, accelerometer data, GPS data, gyroscope data, solid state compass data, RFID data, or wireless data. Exemplary location or positional data may correspond to data captured by an augmented reality device or one or devices of a monitoring system, such as one or more devices attached to an auxiliary display or a patient. As another example, the image or video data may capture a known visual marker (also known or referred to as a fiducial marker as used herein) attached to the patient or a device of a monitoring system.
[0232] In block 7238, the augmented reality system determines position display data from the input data. For example, the augmented reality system determines or calculates a reference position to a reference object from image data, video data, accelerometer data, GPS data, gyroscope data, solid state compass data, RFID data, or wireless data. Typically, GPS data is accurate to within a few meters. Thus, the augmented reality system may use other position-related data, such as image or video data, accelerometer data, gyroscope data, solid state compass data, RFID data, or wireless data, to determine a more accurate position relative to the reference object. In a computer vision example, the augmented reality system performs an image registration process that identifies known visual markers through one or more feature detection techniques, such as corner detection, blob detection, edge detection, thresholding, or other image processing techniques. Additionally or alternatively, the augmented reality system uses pose estimation techniques to determine a three-dimensional position relative to the reference object. In some embodiments, the augmented reality system generates a real-world coordinate system from the obtained or generated position data. An exemplary real-world coordinate system includes at least three-dimensional coordinates.
[0233] An exemplary augmented reality system generates position display data from the obtained or generated position data. In a pinning example, the augmented reality system determines a position offset from a reference object, such as a patient or a monitoring system display or device. The augmented reality system may calculate the position offset from a predefined or configurable distance and a direction from the reference object. Exemplary predefined distances include 5 or 10 centimeters to the right or left of the reference object. In some embodiments, user interaction input received from a clinician may update the position offset. For example, the clinician may interactively manipulate the augmented reality object by moving it, such as with a push, pull, or wave gesture. In a direct overlay or superimposition example, the augmented reality system may display one or more augmented reality objects at a reference position relative to the reference object. For example, the patient's reference position may correspond to a particular coordinate in a coordinate system, and the augmented reality system presents the object at that coordinate. As described herein, the augmented reality system may present an analog display indicia at a reference position corresponding to the patient, such as the coordinate position of the patient's lungs, heart, or brain region. Thus, when the reference object moves, the pinned augmented reality object or objects may move along with the reference object.
[0234] VII. Additional Exemplary Aspects of Augmented Reality Embodiments In a first aspect, a method for presenting augmented reality data from a medical monitoring system, the method comprising: receiving physiological monitoring data from a monitoring hub under control of a hardware processor, the physiological monitoring data including physiological parameter values associated with a patient; accessing user interface configuration data; generating a plurality of augmented reality objects from the physiological monitoring data in accordance with the user interface configuration data; and presenting the plurality of augmented reality objects within an augmented reality display.
[0235] In a second aspect, the method of aspect 1, further comprising receiving user interaction data from a user input sensor of the augmented reality device; and generating user interface configuration data from the user interaction data.
[0236] In a third aspect, a method according to either aspect 1 or 2, further comprising: receiving user interaction data from a user input sensor of an augmented reality device; determining a reference object from the user interaction data; determining a reference position relative to the reference object; and calculating a position offset from the reference position, wherein multiple augmented reality objects are presented with respect to the reference position according to the position offset.
[0237] In a fourth aspect, a method according to any of aspects 1 to 3, further comprising determining from user interface configuration data whether to present a direct overlay, determining from the user interface configuration data a reference object, and determining a reference position relative to the reference object, wherein an overlay object of the multiple augmented reality objects is presented at the reference position.
[0238] In a fifth embodiment, the method of embodiment 4, wherein the reference object corresponds to a patient.
[0239] VIII. Additional Auxiliary Device Embodiments Next, several additional embodiments associated with the auxiliary device 2040 are described, including authentication features (see FIG. 73), features for controlling devices that transmit data to the auxiliary device 2040 (see FIGS. 74 and 76), and features for controlling output to the auxiliary device 2040 (see FIG. 75).
[0240] In general, as described above, the auxiliary device 2040 may provide a second screen function for the hub 100, the PPM 102, or the MMS 2004. Additionally, as described above, the translation module 2005 may be implemented in any device, including the hub 100 or the MMS 2004. Data set on the auxiliary device 2040 by the translation module 2005 (or from another device shown in FIG. 24 or FIG. 72A) may be sent in a format suitable for the auxiliary device 2040, which may determine how to display the data on the display of the auxiliary device 2040. In other words, a device may send data to the auxiliary device 2040 without regard to any particular user interface formatting, and the auxiliary device 2040 may determine how to format the data and display it on its display. For example, a software module (not shown) installed on the auxiliary device 2040 may format the received data into any desired user interface format. In one embodiment, the data received by the auxiliary device 2040 is in XML format or another similar format, and software running on the hardware processor of the auxiliary device 2040 parses the XML (or similar) data and generates a display based on that data.
[0241] Referring to FIG. 73, one embodiment of an auxiliary device authentication process 7300 is illustrated. The process 7300 may be implemented using components of the systems described above with respect to FIG. 24 and FIG. 72A. In general, the process 7300 may be implemented by software or firmware running on a hardware processor. The process 7300 may enable the auxiliary device 2040 to authenticate to the hub 100, the MMS 2004, or the PPM 102. (For convenience, the remainder of this disclosure will focus on communications between the auxiliary device 2040 and the hub 100, although it should be understood that any of these communications may also occur between the auxiliary device 2040 and the MMS 2004 or the PPM 102.)
[0242] It may be desirable to authenticate the auxiliary device 2040 to the hub 100 so that communication can occur between the two devices. In another view, the process 7300 may be considered a process for pairing the auxiliary device 2040 with the hub 100. Multiple auxiliary devices 2040 may be paired or otherwise authenticated to the hub 100 at one time. This may be useful, for example, where multiple clinicians may each have a tablet or other auxiliary device 2040 instead of and / or in addition to a TV auxiliary device 2040 being present in the room. Furthermore, in some embodiments, the augmented reality device 7200 described above may be an example of one of the auxiliary devices 2040, and multiple clinicians may have augmented reality devices 7200 that they would like to use with the hub 100 (e.g., whereby each may have a different heads-up display with a set of views customized for that particular clinician).
[0243] In block 7302, a user requests the hub 100 (or MMS 2004, etc.) to wirelessly connect to the auxiliary device 2040 (wired connections are possible in other embodiments). For example, the user may access a settings menu on the hub 100 to initiate pairing or authentication of the auxiliary device 2040. In block 7304, the hub 100 displays a PIN number or other authentication code (e.g., multiple alphanumeric characters) on the display. In block 7306, the user enters the PIN or other authentication code on the auxiliary device. In block 7308, the auxiliary device communicates the PIN or other authentication code to the hub or MMS. In block 7310, the hub or MMS communicates data collected from the patient monitor to the auxiliary device. Block 7310 may be implemented either before, during, or after the process 7300 is performed.
[0244] Referring to FIG. 74, one embodiment of an auxiliary device control process 7400 is illustrated. The process 7400 may be implemented using components of the system described above with respect to FIG. 24 and FIG. 72A. In general, the process 7400 may be implemented by software or firmware running on a hardware processor. The process 7400 may enable the auxiliary device 2040 to control the hub 100 (and / or MMS 2004, etc.). Thus, for example, the auxiliary device 2040 may not only receive data, but also transmit data to the hub 100 or other devices described above. This data may include control data that enables the auxiliary device 2040 to not only passively receive and display data, but also control settings of any of the devices described above, including both third party monitors (e.g., 214-220) serially or otherwise connected to the hub 100 and first party monitors (e.g., 222-226) connected over a channel or otherwise to the hub 100.
[0245] For example, the auxiliary device 2040 can control options or settings that may be controlled on either the patient monitor or the hub 100. For example, alarms, user interface layout, settings, etc. may be controlled via the auxiliary device 2040. The auxiliary device 2040 may output a user interface that allows control of these settings. For example, referring to FIG. 76, an exemplary user interface 7600 is illustrated that includes settings 7610 for controlling infusion pumps, patient beds, and ventilators, as well as displaying parameter values from multiple devices. Thus, a single auxiliary device 2040 can allow a clinician to control several or even all devices in a patient room (e.g., in communication with the hub 100 or MMS 2004).
[0246] In one embodiment, the manufacturer of the hub 100 may provide a software development kit (SDK) that third party patient monitor manufacturers use to enable the auxiliary device 2040 to communicate with their hardware. Using an SDK, for example, the third party monitor manufacturer may install software libraries on the third party patient monitors (e.g., 214-220) to enable the auxiliary device 2040 to communicate changes to settings or other parameters directly to those devices. The one or more software libraries may include, for example, an application programming interface (API) that defines routines or functions and associated parameters that the auxiliary device 2040 can call or invoke to set different settings in the third party device. One or more similar libraries may be installed on a first party device, such as a channel device (222-226). In one embodiment, the auxiliary device 2040 comprises a set of instructions or libraries that the hub 100 can call to send setting changes to the hub 100 (or MMS 2004) that the hub 100 passes on to the third party device or to the first party device. The hub 100 may also translate configuration request changes from the auxiliary devices 2040 into more complex instructions that are provided to individual patient monitors. In one embodiment, the manufacturer of the hub 100 may certify medical devices that can be controlled by the auxiliary devices 2040. In another embodiment, functionality for controlling both third party and first party devices may be implemented directly by the hub 100 instead of or in addition to the auxiliary devices 2040.
[0247] Thus, the hub 100 or auxiliary device 2040 can essentially become the monitor itself, allowing full control of a wide variety of patient monitoring equipment. In another view, the auxiliary device 2040 or hub 100 can provide a unified display for managing multiple patient devices.
[0248] Referring again to FIG. 74, an exemplary process by which the auxiliary device 2040 can make configuration changes to medical devices connected to the hub 100 is illustrated. At block 7402, the auxiliary device accesses the APIs of the devices connected to the hub, either directly or through the hub itself. At block 7404, the auxiliary device exposes the connected device settings, for example, on a user interface (see, e.g., FIG. 76) that the user may access. At block 7460, the auxiliary device receives the configuration changes from the user through the user interface. At block 7408, the auxiliary device accesses the APIs of the appropriate medical devices, either directly or through the hub, to affect the configuration changes. And at block 7410, the auxiliary device receives data from the connected devices. Of course, block 7410 may operate in parallel with process 7400, with data being received before, during, and / or after the settings are changed.
[0249] Referring to Figure 75, one embodiment of an auxiliary device data flow process 7500 is illustrated. The process 7500 may be implemented using components of the systems described above with respect to Figures 24 and 72A. In general, the process 7500 may be implemented by software or firmware running on a hardware processor. The process 7500 may enable the auxiliary device 2040 or the hub 100 to control the flow of data to the auxiliary device 2040.
[0250] In some current implementations, the translation module 2005 pushes most or all of the data received from most or all devices connected to the hub 100 onto the auxiliary devices 2040. For some auxiliary devices 2040 with fewer computing resources (e.g., less processing power, less memory, less battery capacity, less battery power, low bandwidth connection, etc.), this may mean that they may be overwhelmed with the incoming data. As a result, these devices may crash or get poor or incomplete results.
[0251] One way to solve this problem is to have the auxiliary device 2040 request the translation module 2005 to send data less frequently, for example by receiving the data less frequently. Another way is for the auxiliary device 2040 to have a module that reduces the firehose effect of all the data it receives by instead requesting a specific subset of information from the translation module 2005 or the hub 100. One example of such a module is shown in FIG. 72A, which is the IAP (instrument auxiliary protocol) layer 2042. This layer 2042 can automatically request that a subset of information be provided to the auxiliary device 2040. In one embodiment, the IAP layer 2042 exposes a user interface on the auxiliary device 2040 that allows the user to control what data should be provided to the auxiliary device 2040. Similarly, in other embodiments, the layer 2042 can be implemented as a module on the MMS 2004 or directly in the hub 100.
[0252] In another embodiment, instead of being completely flexible, the IAP layer 2042 may have predefined capabilities for receiving data at the auxiliary device 2040. This capability may be determined, for example, by the level of service paid for by the clinical facility using the auxiliary device 2040, or the like. For example, higher levels of service may allow more parameters or a different variety of parameters to be provided to the auxiliary device 2040.
[0253] With particular reference to process 7500 shown in FIG. 75, in block 7502, the auxiliary device outputs a user interface that can allow a user to select information to receive from the hub or MMS. In block 7506, the auxiliary device receives a user selection of specific parameters from the interface. For example, a user may request to display ventilator or pump data to the exclusion of other data. In block 7508, the auxiliary device transmits the user selection to the hub or MMS. And in block 7510, the hub or MMS records the selection and transmits the requested data.
[0254] IX. Additional Exemplary Aspects of Auxiliary Device Embodiments In a first aspect, a method for authenticating an auxiliary device to a medical monitoring hub, the method including: receiving, under control of the medical monitoring hub having a hardware processor, a request to wirelessly connect the auxiliary device to the medical monitoring hub; outputting on a display of the medical monitoring hub an authentication code for a user to enter into the auxiliary device; receiving an indication from the auxiliary device indicating that the authentication code has already been entered into the auxiliary device; and transmitting data to the auxiliary device from one or more patient monitors coupled to the patient.
[0255] In a second aspect, a method for controlling an auxiliary device in communication with a medical monitoring hub, the method comprising: under control of the auxiliary device in communication with the medical monitoring hub, having a hardware processor, accessing a software library corresponding to a medical device connected to the medical monitoring hub; outputting settings associated with the medical device on a display of the auxiliary device; receiving changes to the settings from the display; and communicating the changed settings using the software library to the medical device through the medical monitoring hub.
[0256] In a third aspect, a method for controlling data flow to an auxiliary device in communication with a medical monitoring hub, the method including: outputting, under control of the auxiliary device in communication with the medical monitoring hub, a user interface having a hardware processor and functionality for a user to select a particular type of information to receive from the medical monitoring hub; receiving a user selection of a first type of information to be received by the auxiliary device from the medical monitoring hub; transmitting the user selection to the medical monitoring hub; and receiving data corresponding to the first type of information at the auxiliary device.
[0257] X. Medical Network Interface Embodiments The hub 100 described above beneficially includes functionality for standalone devices (such as beds, pumps, ventilators, and other monitors) to connect to the hub 100, but this functionality is included along with other important patient monitoring functionality in the same box. That is, in some embodiments, the hub 100 can calculate physiological parameters obtained from sensors (202), receive and process channel data from various sensors (e.g., FIGS. 2, 24, and 74A), and can also receive serial data from standalone devices. The hub functionality may advantageously enable channel devices (e.g., 222, 224, 226) and standalone (serial) devices to provide patient data to the MMS 2004 for storage in the EMR, and optionally display data from the channel or serial devices at the hub 100. However, functionality that allows standalone patient devices to communicate data for storage in the EMR requires inclusion of the vendor functionality of the hub 100. It may be desirable to provide this functionality separately when use of hub 100 is not desired, or when hub 100 is unavailable or less capable monitoring equipment is being used.
[0258] This section describes embodiments of a medical network interface that may advantageously provide the network connectivity functionality of the hub 100 without including other functions of the hub 100. For example, the medical network interface may be a network device that receives data from a stand-alone patient device and then forwards this data to the MMS 2004. As described below, the MMS 2004 may also use this data to perform other functions. The medical network interface may function as a networking hub that does not necessarily perform patient monitoring itself (e.g., a network device that does not have patient monitoring functionality as distinguished from the hub 100), a switch, a router, or a network bridge. One medical network interface may be used for one patient, or devices caring for multiple patients may connect to a single medical network interface (e.g., two patients in one hospital room may connect to a single interface). The medical network interface may advantageously provide network operations for stand-alone patient devices that may not have the native ability to connect to a hospital network (e.g., other than having a hardware port to connect to the network, these devices may not be configured with software configured with the necessary information to connect to the MMS 2004). The medical network interface may be an information technology (IT) appliance in some implementations.
[0259] Additionally, as described in more detail below, a wireless pairing system may be used to pair the medical network interface with standalone patient devices so that the devices transmit patient data wirelessly to the medical network interface. The pairing system may include connecting a wireless dongle to the medical network interface to obtain an identifier and / or security key, and then connecting the wireless dongle to the standalone patient device to enable the standalone patient device to transmit data wirelessly--and optionally securely--to the medical network interface. Advantageously, in some embodiments, this pairing system may be easy and quick for clinicians to use, allowing them to spend less time configuring devices and get back to patient care sooner.
[0260] Fig. 77A illustrates another embodiment of a monitoring environment 7700 including a medical network interface 7710, a patient monitor 7701, and the devices and systems of Fig. 24 and Fig. 72A. The monitoring environment 7700 may include all or a portion of the features of the monitoring environment 200 of Fig. 2, the monitoring environment 2000 of Fig. 24, or the monitoring environment 7202, as well as any of the other features described above. In addition, the monitoring environment 7700 illustrates a medical network interface 7710, which is one embodiment of the medical network interface previously described.
[0261] The medical network interface 7710 can support various wired or wireless connections, for example, via a universal medical connector, an Ethernet port, a USB port, Bluetooth, Wi-Fi, or other types of wired or wireless connections described herein. The medical network interface 7710 can be connected to the MMS 2004 using a wired or wireless network connection. In some embodiments, the medical network interface 7710 is also configured to connect to devices such as, for example, a patient monitor 7701, an auxiliary device 2040, an augmented reality device 7200, standalone devices and sensors 7720 (including a patient bed 214, an infusion pump 216, a ventilator 218, a PPM 102), or other devices and sensors described herein. In some implementations, the medical network interface 7710 can be paired with one or more devices prior to data transmission via a wired or wireless connection, as described in more detail below.
[0262] Advantageously, in some embodiments, the medical network interface 7710 provides connectivity for a standalone patient device 7722 to communicate with the MMS 2004. The medical network interface 7710 can provide this connectivity when the monitoring hub 100 is not available or in addition to a monitoring hub in the same patient room. However, in the illustrated embodiment, the hub 100 has been replaced with a patient monitor 7701 that does not directly connect to the standalone patient device 7720. The patient monitor 7701 (complete with docking station, PPM 102, channel ports, augmented reality, etc.) may also be omitted in other embodiments in favor of other types of patient monitors (including less-full-featured monitors) that can connect to the medical network interface 7710, such as the standalone patient device 7720 (see, e.g., FIG. 77B).
[0263] The medical network interface 7710 can pass data obtained from the medical device to the MMS system 2004. During this process, the medical network interface 7710 can automatically discover the communication protocol used by the device connected to the medical network interface 7710. The medical network interface 7710 can further update the message including one or more data packets from the medical device to include an identifier of the medical network interface 7710 before transmitting to the patient monitor 7701 or the MMS 2004. Thus, the patient monitor 7701 and the MMS 2004 can identify the message as being from the medical network interface 7710. Additionally, the medical network interface 7710 can include a display 7712 to facilitate pairing with a standalone patient device 7720 (or for other reasons), as described in more detail below.
[0264] For ease of explanation but not to limit the disclosure, FIG. 77A illustrates only one medical network interface 7710, however, multiple medical network interfaces may be used to connect to the patient monitor 7701, the MMS 2004, and other devices, sensors, or systems. As an example, two medical network interfaces 7710 may be connected to each other, thereby expanding the ports available on one medical network interface. As another example, two or more medical network interfaces 7710 may be connected to the MMS 2004, where each medical network interface is associated with a patient. Thus, the MMS 2004 may process data associated with multiple patients. Additionally, although the example medical network interface 7710 herein is described as being connected to the MMS 2004, in various embodiments, the medical network interface 7710 may also be connected to the patient monitor 7701 (or hub 100) via a wired or wireless connection. For example, the medical network interface 7710 can pass data obtained from medical equipment to the patient monitor 7701 or hub 100 in addition to or instead of the MMS 2004. The patient monitor 7701 or hub 100 can forward this data to the MMS 2004. Thus, for example, the medical network interface 7710 can extend the functionality of the hub 100 by connecting to a port on the hub 100 instead of connecting directly to a medical network. A detailed exemplary description of the medical network interface 7710 is described below with reference to Figures 78A, 78B, and 80.
[0265] FIG. 77B illustrates another example of a monitoring environment 7702 in which a medical network interface 7710 is illustrated. As in FIG. 77A, a stand-alone patient device 7720 connects with the medical network interface 7710, which provides network connectivity for these devices by connecting to a hospital network 7750. Also connected to the hospital network 7750 are the MMS 7704 and other hospital devices 7760, such as, for example, nurse station computers, kiosks, computers on wheels (COWs), and clinician devices (phones, pagers, tablets, and the like). The MMS 7704 can also communicate with an external network 7770, which may also communicate with clinician or patient devices 7780 located away from the hospital. The MMS 7704 also interfaces with an EMR 7790. Thus, in some embodiments, the medical network interface 7710 allows data from the stand location device 7720 to be communicated to any of the other components illustrated in FIG. 77B, among other things.
[0266] The MMS 7704 may have all the functionality of the MMS 2004 described elsewhere herein. The specific functionality shown may also be processed by the MMS 2004. This functionality includes the ability to route data to a nurse's station (sometimes referred to as a central station). Data received from a standalone patient device 7720 on the medical network interface 7710 may be provided to the station, the central station, and clinician devices, among other things. The MMS 7704 may also perform clinician notification, for example, by routing alarms obtained from the patient device 7720 to the devices 7760, 7780. Additionally, the MMS7704 may perform analysis and journaling, for example, as disclosed in U.S. Patent No. 9,142,117, filed September 22, 2015, entitled "Systems and Methods for Storing, Analyzing, Retrieving and Displaying Streaming Medical Data," Attorney Docket No. MASIMO.609P1C1, and U.S. Application No. 62 / 463,262, filed February 24, 2017, entitled "Systems and Methods for Storing, Analyzing, Retrieving and Displaying Streaming Medical Data," Attorney Docket No. MASIM0.1131PR, which are incorporated by reference in their entireties. Additionally, the MMS7704 may include a telepresence module to perform telepresence monitoring of patients by clinicians from remote locations, for example, as described in U.S. Publication No. 2014 / 0077956, filed Sep. 18, 2013, entitled "Intelligent Medical Network Edge Router," which is incorporated herein by reference in its entirety. Additionally, the MMS7704, like the MMS2004, may be expandable and can feed data to other software engines and databases, including the EMR7790.
[0267] Data acquired by the medical network interface 7710 from the standalone patient device 7720 (or from the patient monitor of FIG. 77A) may take one or more of the following forms: waveform data, parameter data, or event data. Waveform data may include trend data, which may be high frequency data. The network interface 7710 and / or MMS 7704 may treat this data similarly to video streaming data, so that if there are losses (e.g., due to buffer overflow), they are ignored. Parameter data (e.g., physiological parameter measurements such as oxygen saturation values) may come at a set frequency, such as once per second (1 Hz). The medical network interface 7710 may combine the parameter data into a patient snapshot and provide this snapshot to the MMS 7704 or other devices shown. Event data may include event-driven data such as alarms (e.g., parameter values going out of bounds) and alerts (e.g., progress slows or alarm settings change on the device 7720). Events may be delivered asynchronously as they occur, and the medical network interface 7710 may time-stamp any events received from the patient device 7720 before delivering the event data to other devices on the network.
[0268] XI. Examples of Medical Network Interfaces Figures 78A and 78B show schematics of an exemplary embodiment of the above described medical network interface 7710. Figure 78A shows a schematic front perspective view 7800a, while Figure 78B shows a schematic rear perspective view 7800b of the exemplary medical network interface 7710.
[0269] The front of the exemplary medical network interface 7710 as shown in FIG. 78A can include an Ethernet port 7810, a channel port 7822, and a USB port 7832 (among other things not shown). The medical network interface 7710 can also include an optional display screen 7850 and a label 7840. The back of the medical network interface 7710 as shown in FIG. 78B can include two USB ports 7824 and an Ethernet port 7834. The back of the medical network interface 7710 can also include a power port 7860 that can accept a power cord. The power cord can connect the medical network interface 7710 to an AC outlet (e.g., on the wall of the patient's room).
[0270] The Ethernet port 7810 may be an example of the "Ethernet" port shown in FIG. 16. The Ethernet port 7810 may also be an embodiment of the serial port 210 shown in FIG. 24 and FIG. 74A. The channel port 7822 is an embodiment of the port 113, the channel port 212, or the universal connector port shown in FIG. 11E and FIG. 11F. The channel port 7822 may be configured to mate with a dedicated connector that can connect to a device (e.g., as illustrated in FIG. 77A) via a cable. Advantageously, in some embodiments, the medical network interface 7710 may include more ports than the hub 100. For example, the hub 100 may include four Ethernet ports 7810, while the medical network interface 7710 may include eight (or more) Ethernet ports 7810. As a result, the medical network interface 7710 can increase the number of devices that can communicate (e.g., via the medical network interface 7710) with the MMS 2004 (and other devices; see FIG. 77B). Alternatively, the medical network interface 7710 may have the same number of ports as the hub 100, or fewer.
[0271] The medical network interface 7710 may also include a USB port for connecting to other devices in the patient's room. The USB port may be configured to support Type-A, Type-A Superspeed, Type-B, Type-B Superspeed, Type-C, Mini or Micro USB (e.g., Mini-A, Mini-AB, Mini-B, Micro-AB, Micro-B, Micro-B Superspeed), or other types of USB connectors known to those skilled in the art.
[0272] In some embodiments, the medical network interface 7710 can also support wireless connections. The wireless connections may involve Bluetooth, Wi-Fi, ZigBee, or other types of wireless connections. As described in further detail below with reference to FIG. 81, the medical network interface 7710 can use a dongle to pair the medical network interface 7710 with a device that can communicate with the medical network interface 7710. For example, the dongle can be plugged into one of the USB ports 7832. The dongle can receive information from the medical network interface 7710 via the connector port 7832. The user can then unplug the dongle from the medical network interface 7710 and plug the dongle into one of the standalone devices. The standalone device can then use the dongle's wireless capabilities to communicate with the medical network interface 7710, which can utilize the dongle's information obtained from the medical network interface 7710.
[0273] The received information may be security information. For example, the dongle may receive a permission key from the medical network interface 7710. This key may be a cryptographic key, which may be used in an asymmetric or symmetric encryption algorithm (such as private or public key). The dongle may then be plugged into a medical device, which also receives or generates the permission key. The medical network interface 7710 may interrogate devices in its environment and identify medical devices that have the permission key. In one embodiment, after the medical network interface 7710 identifies the medical device and authenticates the permission key, the medical network interface 7710 may wirelessly communicate with the medical device.
[0274] The medical network interface 7710 can also receive signals (e.g., RFID, Wi-Fi, Bluetooth) emitted by medical devices seeking to pair directly with the medical network interface 7710. Thus, in one embodiment, a dongle is not required to pair with a standalone patient device. The medical network interface 7710 can reply with a pairing protocol (or permission key) and establish a connection to transfer patient data.
[0275] Another possible approach is for the medical network interface 7710 to interrogate the medical device to determine what protocol the medical device uses to communicate. For example, the medical network interface 7710 may attempt to communicate with the medical device (e.g., wirelessly) using a first protocol, and then, if that protocol does not work, attempt to communicate with a second protocol, and so on until the medical network interface 7710 selects the correct protocol to use to communicate with the medical device. The protocol may refer to the network communication protocol, the message format used by the medical device, and / or the data format used by the medical device. For example, the protocol may refer to whether the messages used by the medical device have a fixed or dynamically variable length, whether checksums or CRC (cyclic redundancy check) codes are used, framing parameters, etc. Additionally, the medical network interface 7710 may communicate with the medical device using standard protocols such as TCP / IP, optionally in addition to a custom application layer specific to the medical device. For example, a medical device may format application layer messages in a manner specific to that medical device, and the medical network interface 7710 may cycle through different possible protocols, including different message formats, until it finds the correct message format that understands the message sent by the medical device.
[0276] For example, the message format may include key-value pairs (sometimes referred to as tag-value pairs) where the key defines a type or category of data (parameter type, alarm, etc.) and the value is an instance of that type or category (a particular parameter value, alarm state, etc.). The protocol or message format used by the medical device may be self-defined, allowing the medical network interface 7710 to inspect messages received from the medical device and thereby automatically determine what message format or protocol is used by the medical device. The message format used by the medical device may be formatted according to XML, allowing the tag-value pairs to be machine readable by the medical network interface 7710 directly from the XML. The medical network interface 7710 may include a library of different protocols or message formats for different medical devices that the medical network interface 7710 can read. In one example implementation, the medical network interface 7710 identifies the type of device wirelessly connecting to the medical network interface 7710 based on analyzing the message format from the medical device, comparing the message format to known message formats in a library of protocols, and identifying the correct medical device from the library.
[0277] The medical network interface 7710 can associate one or more identifiers with data obtained from the patient device. The medical network interface 7710 can have its own identifier, for example. Each standalone patient device can have its own identifier, either provided by the device or generated by the medical network interface 7710. Additionally, each patient can have an identifier. The patient identifier can be obtained by optically scanning a machine-readable code, such as a QR (quick response) code or a barcode, which can take the form of a tag or sticker on the patient's wrist bracelet. An optical scanner can be attached to the medical network interface 7710 for this purpose, or the clinician can use their phone, tablet, or other device to perform the scanning function. The scanning function is described in more detail in U.S. Application Serial No. 14 / 511,972, entitled "Alarm Notification System," filed October 10, 2014, Attorney Docket No. MASIM0.963A, which is incorporated herein by reference in its entirety. The features in the '972 application may be used in conjunction with the features described herein, for example, by using those features to perform a scan of a patient or device identifier.
[0278] In some embodiments, the medical network interface 7710 tags or associates data received from the patient device with a patient identifier, a device identifier, and a medical network interface identifier. The medical network interface 7710 can provide the data along with this identification data to the MMS 2004 or 7704 (for convenience, when the remainder of this specification refers to one of the MMS 2004 or 7704 individually, it may be considered to refer to the other as well).
[0279] Optionally, the medical network interface 7710 may include a display 7850. The display 7850 may indicate which patient the medical network interface 7710 is associated with and which devices are currently communicating with the medical network interface 7710. The display 7850 may also provide an indication of the pairing status. For example, in some embodiments, the display 7850 may show information (and optionally any of the identification information described above) of a medical device that is pairing or has just been paired. The display 7850 may also illuminate a light pattern to indicate that a medical device is paired with the medical network interface 7710.
[0280] In addition to or alternatively to the ports shown in the front perspective view 7800a, the medical network interface 7710 can also include various ports on the back as shown in the rear perspective view 7800b of FIG. 78B. For example, the medical network interface 7710 can include two USB ports 7824 and one Ethernet port 7834. One of the USB ports 7824 can connect the medical network interface 7710 to a patient monitor 7701, while the other USB port can connect the medical network interface 7710 to a display device that can show patient data in aggregate. The medical network interface can also be connected to the hospital's main network using the Ethernet port 7834. The medical network interface 7710 can pass data acquired from the medical devices to the MMS 2004 via the Ethernet port 7834.
[0281] The medical network interface 7710 may also include a power port 7860. A power cord may be used to connect an AC outlet in the environment to the patient monitoring box 7710 (via the power port 7860). In some embodiments, the medical network interface 7710 has a power cord attached and secured to the power port 7860. The medical network interface 7710 may also have a backup battery (such as an uninterruptible power supply (UPS)) in case of a power outage. In some implementations, the power port 7860 (or power cord) is optional. The medical network interface 7710 may be battery powered.
[0282] The medical network interface 7710 may be assigned to a particular patient such that the medical network interface 7710 can obtain data from medical devices (e.g., pumps, ventilators, other devices, or sensors) associated with the patient. The medical network interface 7710 may also be configured to collect data from multiple patients. Advantageously, in some embodiments, some of the medical network interfaces 7710 may be color coded to indicate which patient the data the port is receiving is from. For example, the four ports above the Ethernet port 7810 may be color coded yellow, while the four ports below the Ethernet port 7810 may be color coded blue. (More generally, some of the ports on the device may be color coded to represent one patient, while other of the ports on the device may be color coded to represent another patient.) Yellow may represent data originating from a device associated with patient A, while blue may represent data originating from a device associated with patient B. As another example, the left side of the front of the medical network interface 7710 may be color coded yellow indicating that the ports on this side of the medical network interface 7710 should be connected to patient A's medical devices. The right side of the front of the medical network interface 7710 may be color coded blue indicating that the ports on this side of the medical network interface 7710 should be connected to patient B's medical devices. The display 7850 may also provide an indication as to which patient the medical network interface 7710 is collecting data from. For example, the display 7850 may feature a patient ID associated with patient A on one line and a patient ID associated with patient B on the next line. The display may be a touch screen or other means.
[0283] More generally, data received on a particular color-coded port for one patient may be automatically associated with that patient's ID in the medical network interface, while data received on another color-coded port for another patient may be automatically associated with that patient's ID in the medical network interface.
[0284] In some embodiments, pairing using the dongle does not require entering a passcode on either the dongle or the patient device or the medical network interface. By avoiding this requirement, a clinician can quickly pair the network interface with the patient device without being distracted by entering a pairing code that could take time away from treating the patient. This hands-free operation (other than plugging in the dongle) can allow the clinician to quickly return to patient care and retrieve data from the patient device more quickly. However, in other embodiments, a pairing code is used.
[0285] Exemplary components, including ports 7810, 7822, 7824, 7832, 7834, 7860, display 7850, and label 7840, are shown only diagrammatically. The medical network interface 7710 may include fewer or more components than those shown. Additionally, the locations of these components in FIG. 78A and FIG. 78B are exemplary only, and the components need not be located in the locations illustrated in these figures. For example, one or more of the ports in FIG. 7800a may be moved to the rear of the medical network interface 7710. Additionally, the sizes of these exemplary components are not illustrated to scale. Additionally, some ports may be located on the side of the device instead of or in addition to the front or rear portions.
[0286] XII. Dongle Examples FIG. 79 shows an exemplary embodiment of a dongle 7900 used to pair a medical network interface 7910 with another device. The dongle 7900 may be used for pairing to Bluetooth, Wi-Fi, or other types of wireless communication. Advantageously, in some embodiments, using wireless communication between medical devices may result in a cleaner hospital environment, less infection (e.g., due to less cable sharing), and easier user interaction with medical devices. As an example, by employing wireless communication, operation rooms no longer need to use long Ethernet cables to connect various medical devices.
[0287] The dongle 7900 may be equipped with an antenna 7920 (or beacon), a location tag 7930, a battery 7940, and a processing unit 7910. The processing unit 7910 may comprise a processor 7912, a memory 7914, and a network interface 7916. The processing unit 7910 may include an embodiment of the core board 312. The dongle 7900 may also comprise an optional display 7952 and / or lights 7954. In various embodiments, the dongle 7900 may comprise fewer or more components as illustrated in FIG. 79. For example, the dongle 7900 may comprise either the beacon 7920 or the location tag 7930, but not both.
[0288] The dongle 7900 can be used to pair the medical network interface 7710 to a medical device seeking to communicate with the medical network interface 7710. A clinician may insert the dongle 7900 into one of the USB port 7822 or the Ethernet port 7810 and obtain a permission key. For example, the processing unit 7910 may be programmed to communicate with the medical network interface 7710 and receive a permission key from the medical network interface 7710 after the dongle 7900 is plugged into the medical network interface. The permission key may include a device identifier of the medical network interface 7710. Additionally or alternatively, the permission key may be a password, a token, or an encryption / decryption key to establish communication with the medical network interface 7710.
[0289] The clinician can plug the dongle into the patient device. To establish pairing between the medical network interface 7710 and the patient device after the dongle is inserted, the dongle 7900 can pass the permission key received from the medical network interface 7710 to the medical device, for example, by plugging into a USB port of the medical device. In some embodiments, the medical device may not have a compatible port into which the dongle 7900 can be plugged. As a result, the dongle 7900 may use a connector that allows the dongle 7900 to adapt to connect to a port of the medical device.
[0290] The medical device can retrieve the permission key from the dongle 7900. The medical device can search for the medical network interface 7710 using the device ID (of the medical network interface 7710) received from the dongle 7900. As described above, to speed up pairing, the medical device can optionally avoid the need to provide a password to connect with the medical network interface. In some embodiments, the medical network interface 7710 interrogates the surrounding device for the permission key. The medical network interface 7710 can establish a connection and receive patient data from the medical device if the medical device is able to provide the permission key in response to the medical network interface 7710 interrogation.
[0291] In some embodiments, the permission key is provided and shared among multiple medical devices seeking to connect to the medical network interface 7710. For example, the dongle 7900 may be plugged into medical device A such that medical device A can receive the permission key from the dongle 7900. The dongle 7900 may also be plugged into medical device B and pass the permission key to medical device B. In some implementations, the dongle 7900 may store multiple permission keys and the medical devices may receive different permission keys. For example, the dongle 7900 may store permission keys A and B in the memory 7914, where permission key A may be used to pair the medical network interface 7710 with the patient bed 214 and permission key B may be used to pair the medical network interface 7710 with the ventilator 218. Permission keys A and B may have different expiration dates. For example, permission key A (for the patient bed 214) may include a longer expiration time than permission key B (for the ventilator 218). Furthermore, in some situations, permission keys A and B may originate from two different medical network interfaces.
[0292] In some embodiments, the medical network interface 7710 may update the permission key periodically or based on a trigger event to reduce the probability of a malicious device gaining a connection to the medical network interface 7710. For example, the permission key may automatically expire after a certain period of time (e.g., 24 hours, one week, one month, etc.). The permission key may also be automatically updated, for example, when the medical network interface 7710 is associated with a new patient. The permission key may be stored in memory 7914 so that it can be passed on to another device at a later time. After the old permission key expires, the medical network interface 7710 may need to be re-paired with the other device.
[0293] In addition to or alternatively to pairing using the dongle 7900, other techniques can be used to pair the medical network interface 7710 with another medical device. For example, the medical network interface 7710 and the other device can be paired using a label (e.g., a barcode or RFID, etc.) on the medical network interface 7710 or the other device. In addition, a system administrator can add a device identifier of the medical device to the whitelist of the medical network interface 7710. Thus, the medical network interface 7710 can initiate communication with the medical device when the medical device is within communication range of the medical network interface 7710. In some implementations, the dongle 7900 can obtain a permission key through a wireless connection. For example, the dongle 7900 can establish a connection with the medical network interface 7710 in a wireless manner and then receive a permission key from the medical network interface 7710 using the network interface 7916.
[0294] Advantageously, in some embodiments, the location of the dongle may be tracked by a location tag 7930 in addition to or as an alternative to the antenna 7920. The location tag 7930 may be an RFID tag or the like. The location tag 7930 or antenna 7920 may emit a signal that may be picked up by another device. For example, the patient monitor 7701 may automatically discover the dongle 7900. The patient monitor 7701 may determine a location (e.g., the room in which the dongle 7900 is located) based on the signal emitted by the location tag or antenna 7920. In some implementations, multiple patient monitors 7701 may pick up the dongle 7900 signal. Thus, the location of the dongle 7900 may be identified by triangulation using the location of the patient monitor 7701 or by triangulation using access points within the hospital. In some embodiments, a map of the hospital room may be accessed electronically by any of the devices shown in FIG. 77A or FIG. 77B to determine the location of the dongle within the hospital room. The map can show the location of the dongle, for example, as determined based on this triangulation or RFID tag positioning. If the connection between the dongle and the patient monitor is not working, the dongle can attempt to wirelessly communicate with a nearby patient monitor, which may be in a nearby hospital room. The dongle can wirelessly transmit data to the nearby patient monitor, which can then be sent to a remote server or electronic medical record for subsequent retrieval by the patient monitor in the room with the dongle.
[0295] The dongle 7900 may also include a battery 7940. The battery 7940 may be charged while the dongle 7900 is plugged into one of the USB ports 7822 or the Ethernet port 7810. For example, after the dongle 7900 obtains a permission key from the medical network interface 7710, the dongle 7900 may remain plugged in to charge.
[0296] The dongle 7900 may include an optional display 7952 and an optional light component 7954. The display 7952 and light component 7954 may provide an indication of the pairing status or status of the dongle 7900. For example, after the dongle 7900 is fully charged, the light component 7954 may illuminate a particular color or pattern (e.g., blinking green) to indicate that the battery is full. As another example, the display 7952 may display the device ID of the device in which the dongle 7900 is currently plugged in. As yet another example, the light component 7954 may illuminate or the display 7952 may provide an alert when the medical network interface 7710 is paired with a medical device using a permission key stored in the dongle 7790. In this example, assuming the medical network interface 7710 is paired with the patient monitor 7701, the display 7952 may indicate the hub ID (e.g., 1162) and the status "paired." In addition to or alternatively to the visual indications provided by the display 7952 and light component 7954, the dongle may also include a speaker that plays sounds that indicate the status of the pairing or the status of the dongle 7900. The colors, patterns, sounds, or indications may be easily seen and easily identifiable by the clinician.
[0297] Advantageously, in some embodiments, the dongle 7900 may be hot swapped without interrupting the functionality of the device in which it is plugged. For example, the dongle may be plugged into the patient medical device 7720 (either directly or via a dongle socket). While plugged into the patient medical device 7720, the dongle may consume battery power to communicate with the medical network interface 7710. However, the physician may notice that the dongle's battery power is low because the light component 7954 has turned amber. The physician may unplug the dongle from the patient medical device 7720 and swap the dongle with low battery power with the fully charged dongle currently plugged into the medical network interface 7710. Thus, the physician may plug the fully charged dongle into the patient medical device 7720 while plugging the dongle with low battery power back into the medical network interface 7710 for charging. During this swap process, communication between the patient medical device 7720 and the medical network interface 7710 may remain uninterrupted. For example, to avoid interruptions in data transmission, the patient medical device 7720 may assume that a fully charged dongle has the same permission key (for the same medical network interface 7710) as a dongle with low battery power, and pairing with the fully charged dongle does not need to be performed because the fully charged dongle is plugged into the patient medical device 7720 within a certain threshold period when the dongle with low battery power is unplugged.
[0298] Exemplary Components of a Medical Network Interface FIG. 80 illustrates one exemplary embodiment of components of a medical network interface. These components are for illustrative purposes only, and the medical network interface 7710 may include fewer or more components than those illustrated in FIG.
[0299] The medical network interface 7710 may comprise hardware components such as, for example, a memory 8012, a processor 8014, a network interface 8016, and an optional backup battery 8020. In some embodiments, the hardware components may comprise a core board on which the main processor 8014 (or a separate processor) can act as a network bridge. The network interface controller 8016 may be configured to receive communications from various devices via wired or wireless connections, such as, for example, Ethernet, Wi-Fi, Bluetooth, or other types of connections. The network interface controller 8016 may be configured to pass data to another device, such as, for example, a patient monitor 7701, an MMS2004, a multi-parameter monitor, etc. As further described with reference to the network data processing system 8030, the processor 8014 and memory 8012 together with the network interface controller 8016 may facilitate the transfer of this data. For example, the memory may store instructions associated with the network data processing system 8030 and the processor 8014 may execute these instructions to identify a patient identifier and a device identifier of a device from which a communication is received by the network interface controller 8016. The processor 8014 may also associate the device identifier of the medical network interface 7710 with a data packet received from the device and pass the data packet (updated with the device identifier of the medical network interface 7710) to the patient monitor 7701 and the MMS 2004. In one embodiment, the network interface controller 8016 may act as a network bridge.
[0300] As described above with reference to FIG. 78A, the medical network interface 7710 may include a power port 7860 for obtaining power from an AC outlet. An optional backup battery 8020 may provide battery power in the event that the medical network interface 7710 is unable to obtain power from another source (e.g., during a power outage). Thus, the medical network interface 7710 may be powered entirely by a battery.
[0301] The medical network interface 7710 may also include software components, such as a network data processing system 8030, a device pairing system 8040, and an optional display system 8050. At least a portion of these software components may be stored in the memory 8012. The processor 8104 may be programmed to execute these software components.
[0302] The network data processing system 8030 may be configured to process data received from one device and pass the data on to another device. The network data processing system 8030 may analyze received packets to identify the device ID from which the medical network interface 7710 received data. These packets may include a patient ID (which may be added by the device sending the data packet), and the network data processing system 8030 may identify the patient ID in the data received from the device accordingly. The network data processing system 8030 may also add the medical network interface 7710's device ID to the data received from the device and route the data to another device. Alternatively, the medical network interface 7710 may already have stored the patient ID based on scanning the patient's wrist bracelet, as described above. Thus, the medical network interface 7710 may associate the patient ID, the interface 7710's ID, and the patient device ID together with the data obtained from the patient device and transmit this data to the MMS 2004 or another device (such as the hub 100 or another interface 7710).
[0303] The network data processing system 8030 can recognize the source of the packet by analyzing the packet, but in some embodiments, the network data processing system 8030 does not process the content in the packet (e.g., parameter values of a patient measurement, etc.). As an example of passing data, the medical network interface 7710 can be connected to a patient monitor 7701 and can receive a packet from a pump. The packet can indicate a device ID for the pump and a patient ID. The network data processing system 8030 can add the device ID of the medical network interface 7710 to the header without altering the parameter values obtained by the pump. The network data processing system 8030 can then convey the marked or tagged packet to the MMS 2004.
[0304] Optionally, the network data processing system 8030 can prioritize packets based on a variety of factors, such as, for example, patient ID, source of data (e.g., which device the packet came from), destination of data, or based on an alarm. Additional details regarding routing and prioritizing packets by devices such as the MMS 2004, patient monitor 7701, medical network interface 7710, or another device (and as may be demonstrated herein) are described in application Ser. No. 14 / 030,360, entitled "Intelligent Medical Network Edge Router," Docket No. MASIMO.909A, filed Sep. 18, 2013, now U.S. Patent No. 9,749,232 (the "'232 patent"), which is incorporated herein by reference in its entirety. Additionally, the medical network interface described herein can perform the functions of an edge router as described in the '232 patent. For example, the medical network interface may prioritize alarms over other data, or prioritize parameters over other data (potentially excluding alarms).
[0305] The device pairing system 8040 can control the permission keys, identify devices in the environment to pair with the medical network interface 7710, and establish connections between the devices in the environment and the medical network interface 7710. For example, the device pairing system 8040 can periodically generate or update a permission key for the dongle 7900. The device pairing system 8040 can also receive and process signals from the dongle 7900 or a medical device seeking to pair with the data collection system 7710. The device pairing system 8040 can authenticate a request to connect to the medical network interface based on whether the request includes the correct permission key.
[0306] The optional display system 8050 can generate user interface instructions for the optional display 7850 (shown in FIG. 78A ). For example, when a medical device is paired with the medical network interface 7710, the device pairing system 8040 can instruct the display system 8050 to generate instructions to indicate a device identifier of the medical device on the display 7850. As another example, the display system 8050 can communicate with the network data processing system 8030 or the device pairing system 8040 to obtain the status of the device connected to the medical network interface 7710 (e.g., disconnected, connected, pairing, repair mode, etc.). The display system 8050 can instruct the display 7850 to present the status of the device accordingly.
[0307] XIII. Exemplary Process for Pairing Medical Network Interfaces FIG. 81 illustrates an example embodiment of a state flow diagram for pairing a medical network interface with a medical device. The example environment 8100 of FIG. 81 may be part of the environment 7700 illustrated in FIG. 77. The example environment 8100 may involve a medical device 8110, a medical network interface 7710, and a dongle 7900. The medical device 8110 may be any device illustrated in FIG. 77 or other devices described herein.
[0308] In state (1), the dongle 7900 can receive a permission key and optionally an identifier (of the interface 7710) from the medical network interface 7710. The dongle 7900 can receive the permission key (and optionally an ID) when plugged into the medical network interface 7710. The dongle 7900 can be plugged into a USB port, a medical port, an Ethernet port, or another port on the medical network interface 7710. The dongle 7900 can also receive the permission key (and optionally an ID) from the medical network interface 7710 using other techniques, such as, for example, wireless (e.g., Bluetooth) pairing between the dongle 7900 and the medical network interface 7710.
[0309] In state (2), the dongle 7900 can pass the permission key (and optionally the ID) to the medical device 8110. For example, the dongle 7900 can be unplugged from the medical network interface 7710 and re-plugged into the medical device 8110. The medical device 8110 can detect that the dongle 7900 is connected and can automatically access the permission key (and optionally the ID) stored in the dongle 7900.
[0310] In state (3), the medical device 8110 can establish a connection with the medical network interface 7710. For example, the medical network interface 7710 can interrogate a device in its vicinity and request a permission key to initiate the connection. As another example, the medical device 8110 can contact the medical network interface 7710 with a permission key to gain access to the medical network interface 7710.
[0311] The medical device 8110 can communicate with the medical network interface 7710 to pass patient data (and optionally ID) from the medical device 8110 to the medical network interface 7710. The medical network interface 7710 can further pass patient data to another device, such as, for example, a patient monitor 7701 or MMS2004. Packets communicated from the medical device 8110 can include the patient ID and the device ID of the medical device 8110 (or the patient ID is not in the packet but instead inserted into the data stream by the interface 7710). The medical network interface 7710 can also associate another device ID of the medical network interface 7710 with the data packet before the data is passed to the other device. In some implementations, the medical network interface 7710 can automatically link its device ID with the device ID (and patient ID) of the medical device 8110.
[0312] In some embodiments, the medical network interface 7710 can also receive data from other devices (e.g., from the patient monitor 7701 or the MMS 2004) and pass this data to the medical device 8110. For example, the medical network interface 7710 can receive instructions from the patient monitor 7701 to adjust parameters of the medical device 7710 (e.g., increase the frequency of measurements or adjust the delivery rate of the infusion pump 216). The medical network interface 7710 can pass the instructions received from the patient monitor 7701 to the medical device 7710, causing the medical device 7710 to execute the instructions. In some embodiments, the connection between the medical device 8110 and the medical network interface is maintained while the dongle 7900 is plugged into the medical device 8110. After the dongle 7900 is removed from the medical device 8110, the communication between the medical device 8110 and the medical network interface 7710 can be terminated.
[0313] 82 illustrates an example embodiment of a process for pairing a medical network interface with a medical device. The process 8200 may be performed by the medical network interface 7710.
[0314] At block 8210, the medical network interface may generate a permission key for pairing with the medical device. The permission key may be a randomly generated alphanumeric string. The permission key may also encode device information or a password associated with the medical network interface. The permission key may be updated periodically after initial pairing to reduce the probability of an unauthorized device or user gaining access to the medical network interface.
[0315] In block 8220, the medical network interface may communicate the permission key to a dongle (e.g., dongle 7900, etc.). For example, when the dongle is plugged into a port of the medical network interface, the medical network interface may send the permission key to the dongle or receive a request (from the dongle) to download the permission key.
[0316] At block 8230, the medical network interface may discover medical devices within the medical network interface's environment. For example, the medical network interface may send an interrogation signal to the peripheral device and request the peripheral device to provide a permission key. As another example, the medical device may initiate contact with the medical network interface (e.g., based on the medical network interface's device ID) and provide the permission key to the medical device.
[0317] In block 8240, the medical network interface may validate the permissions of the medical device based at least in part on the permission key. For example, the medical network interface may determine whether a permission key provided by the medical device is valid. In some embodiments, the device pairing occurs in a wired connection. For example, the medical network interface may be connected to the MMS 2004 using a USB connection. The medical network interface and the MMS 2004 may be paired by receiving and recognizing a device identifier of the MMS 2004 via the USB connection. In other embodiments, the medical network interface may pair with another device using a wireless connection without the need for a dongle. For example, the medical network interface may pair with the patient monitor 7701 over Wi-Fi. In this example, the device identifier of the medical network interface may be added to a whitelist of allowed devices for the patient monitor 7701. The patient monitor 7701 may use the device identifier of the medical network interface to find and connect to the medical network interface.
[0318] In block 8250, the medical network interface may establish a connection with the medical device in response to determining that the permissions are valid. The medical network interface may pass data received from the medical device to another device, such as, for example, the patient monitor 7701, the MMS 2004, the multi-parameter monitor, and the augmented reality device 7200.
[0319] XIV. Exemplary Process for Data Processing with a Medical Network Interface FIG. 83 illustrates an exemplary embodiment of a process 8300 for data processing by the medical network interface 7710.
[0320] At block 8310, the medical network interface may receive a data packet from a first medical device. The first medical device may be a medical device (e.g., other devices and sensors 7720 of FIG. 77 ) that may acquire patient data. The patient data acquired by the first medical device may be associated with a patient ID that identifies which patient it was acquired from. The patient data may also be associated with the first device ID, which may be a device identifier of the first medical device.
[0321] The medical device can pass the patient data to the medical network interface via a wired or wireless connection as described with reference to FIG. 78A. The first device ID and the patient ID can be part of a header file for the patient data. In block 8320, the medical network interface can process the data packet to link a second device ID associated with the medical network interface to the first device ID and the patient ID. In some embodiments, the medical network interface can link the second device ID to the first device ID when the medical network interface is paired with the first medical device. Thus, the linking of the first device ID and the second device ID can occur before the first medical device communicates the patient measurement results to the medical network interface. In some embodiments, after the medical network interface links the first device ID and the second patient device ID, the medical network interface can automatically stamp the data packet with the device ID of the medical network interface.
[0322] At block 8330, the medical network interface may identify a second medical device connected to the medical network interface 8330. The second medical device may be a patient monitor 7701, an MMS 2004, a display (e.g., a multi-parameter monitor, etc.), or another device described herein. The medical network interface may identify the second medical device by determining which device is plugged into a port. The medical network interface may also review a list of wirelessly connected devices to identify the second medical device.
[0323] At block 8340, the medical network interface may communicate the data packet to the second device. The data packet may include a first device ID that identifies the first medical device (obtaining the patient data), a patient ID, and a second device ID (which may be imprinted by the medical network interface). The second device may further process the data packet, such as by routing the data packet to another device or system, perform data analysis, or display the patient data.
[0324] Additionally, it should be appreciated that passing an identifier for the medical network interface along with the patient data may enable troubleshooting of the medical network interface.
[0325] Additionally, in another embodiment, the wireless dongle comprises two pieces: a first piece that remains connected to the medical network interface and a second piece that disconnects from the first piece. The second piece connects with a corresponding first piece of a similar dongle in the medical device. The exemplary dongles of Figures 77A-83 are referred to as wireless connectors in Figures 84A-88, as described below.
[0326] XV. Exemplary Techniques for Connecting Medical Network Interfaces to Patient Monitors As described with reference to FIGS. 77A-78B, the medical network interface 7710 may be communicatively coupled to the patient monitor 7701 or hub 100 via a wired or wireless connection. The medical network interface 7710 may also be mechanically coupled to the patient monitor 7701 or hub 100 in addition to or in lieu of a wired or wireless connection. For example, the medical network interface 7710 may be mechanically coupled to the patient monitor 7701 by attaching a top or bottom surface of the medical network interface 7710 to a surface (e.g., a top, bottom, or side) of the patient monitor 7701 or hub 100. In some embodiments, the attachment of the medical network interface 7710 to the patient monitor 7701 or hub 100 is not permanent, and thus the patient monitor 7701 or hub 100 may be detachable from the medical network interface 7710. In other embodiments, the medical network interface 7710 is integrally formed with the hub 100 as part of the hub 100.
[0327] FIGURES 84A and 84B show an exemplary embodiment of a medical network interface where the medical network interface is removably attached to the bottom surface of a hub. The hub 8401 may be an embodiment of the patient monitoring hub 100 or the patient monitor 7701 described herein. The medical network interface 8410 may be an embodiment of the medical network interface 7710 of FIGURES 77A-78B and 80.
[0328] FIG. 84A shows a perspective view 8400a of the hub 8401 and the medical network interface 8410. The front of the medical network interface 8410 can include various ports for interfacing with devices, such as, for example, the patient device 7720 or other devices shown in the computing environment 7700. In FIG. 84A, the front of the medical network interface 8410 includes (by way of example) four interface ports 8412. Other embodiments may include more or fewer ports. The interface ports 8412 can be configured to connect with a wireless connector 8480. The wireless connector 8480 can be an embodiment of the dongle 7900 described in FIG. 79. As illustrated in FIG. 84A, three wireless connectors 8480 are currently plugged into three of the four interface ports 8412. The interface ports 8412 can be an embodiment of the USB port 7832. In some implementations, the wireless connector 8480 is a dedicated connector and the interface port 8412 can be customized to accept the wireless connector 8480.
[0329] The medical network interface 8410 may be attached to the bottom of the hub 8401 using various mounting types or standards, such as GCX® slide-in track, VESA mount, tab mounting, universal mount, etc. The medical network interface 8410 and hub 8401 may also be attached using other techniques, such as clamps or adhesives. As an example, one side of the hub 8401 may include one or more clamps that can be used to hold the medical network interface 8410. In some embodiments, the hub 8401 includes one or more holes on its bottom surface. The top surface of the medical network interface 8410 may include corresponding protrusions for insertion into the holes on the bottom surface of the hub 8401.
[0330] Although FIG. 84A illustrates four interface ports, other types of ports may be provided on the front of the medical network interface 8410. For example, as described with reference to FIG. 78A, the medical network interface 8410 may also include an Ethernet port 7810, a channel port 7822, or a USB port 7832. The medical network interface 8410 may also include fewer and more interface ports 8412, such as, for example, two, three, six, eight, or other numbers of interface ports 8412. Additionally, although four interface ports 8412 are arranged in the same row in FIG. 84A, the layout of the interface ports 8412 may differ in different embodiments. For example, the medical network interface 8410 may include multiple rows (e.g., two) of interface ports 8412, and optionally, each row may include the same number of interface ports.
[0331] The number and layout of the interface ports 8412 on the medical network interface 8410 may be determined based on the size of the medical network interface 8410. For example, if the medical network interface 8410 is designed to be a thin housing that fits directly under the patient monitor 8401, such as the example shown in FIG. 84A, the medical network interface 8410 may include one row of interface ports 8412 to keep the height of the medical network interface 8410 small. On the other hand, if the medical network interface 8410 is designed to be mounted on either side (left or right) of the hub 8401, the medical network interface 8410 may be short in length and tall in height. Thus, the medical network interface 8410 may include four rows of interface ports 8412, with each row including one interface port 8412.
[0332] The number and layout of the interface ports 8412 may also depend on the size and shape of the wireless connector 8480. For example, if the wireless connector 8480 is a USB Type-A connector, the medical network interface 8410 may include more interface ports 8412 than if the wireless connector 8480 takes the shape shown in FIG. 84A because a USB Type-A port may not occupy as much area as a port configured to accept the wireless connector 8480 in the shape shown in FIG. 84A. However, one advantage of the wireless connector configuration shown and described in more detail below is a larger battery capacity than a USB-sized device. This larger battery capacity may allow the wireless connector 8480 to be inserted into a longer standalone medical device than a USB-sized device (which may be useful, for example, when the medical device does not provide power to the wireless connector).
[0333] FIG. 84B illustrates a rear view 8400b of the hub 8401 and the medical network interface 8410. As illustrated, the rear of the hub 8401 can include two USB ports 8403, one Ethernet port 8405, and four channel ports 8422. The two USB ports 8403, one Ethernet port 8405, and four channel ports 8422 can be embodiments of the USB, Ethernet, and RJ ports, respectively, in FIG. 16. The rear of the medical network interface 8410 can include one battery port 8460, two USB ports 8432, three Ethernet ports 8434, and four channel ports 8422. With reference to Figures 78A and 78B, battery port 8460 may be an embodiment of battery port 7860, USB port 8432 may be an embodiment of USB port 7832, Ethernet port 8434 may be an embodiment of Ethernet ports 7810 and 7834, and channel port 8422 may be an embodiment of channel port 8422.
[0334] Although the medical network interface 8410 is shown with a port under the hub 8401, in some implementations the medical network interface 8410 may be omitted. Rather, the hub 8401 itself may include a port, such as port 8422, for example, on the front, back, side, or top of the hub 8401. Thus, some or all of the functionality of the medical network interface 8410 may be incorporated within the hub 8401 or within another monitor or medical device. For example, an anesthesia machine (such as a Draeger Apollo™ or similar) could incorporate the features of the medical network interface 8410. Additionally, any of the medical network interfaces described herein may also be capable of communicating with the hub 8401 through one of the hub's channel ports using, for example, the Masimo Open Connect (MOC) protocol, as described, for example, in U.S. patent application Ser. No. 15 / 902,193, filed Feb. 22, 2018, entitled "System for Displaying Medical Monitoring Data," which is incorporated herein by reference in its entirety.
[0335] Figures 84C and 84D show another example of a medical network interface 8410. The medical network interface 8410 may be connected to a monitoring hub 8401 as described with reference to Figures 84A and 84B.
[0336] FIG. 84C illustrates a front perspective view 8400c of the medical network interface 8410. Similar to FIG. 84A, the front of the medical network interface 8410 may include various ports for interfacing with devices, such as, for example, the patient device 7720 or other devices shown in the computing environment 7700. In contrast to FIG. 84A, the front of the medical network interface includes, for example, three interface ports 8412 and a display 8482. As described herein, the interface port 8412 may be configured to connect to a wireless connector 8480.
[0337] The display 8482 may be an example of the display 7850 shown in FIG. 78A. The display 8482 may be located in the left-most area of the front of the hub as shown in FIG. 84C. The medical network interface 8410 may replace one interface port 8412 with the display 8482 (compared to FIG. 84A). The display 8482 may show various information related to the medical network interface 8410, the hub 8401, and other devices connected to the network interface 8410. For example, the medical network interface 8410 may be connected to one or more medical devices via the hub 8401 and the wireless connector 8480. The display 8482 may provide an indication of the connection status for the hub 8401 and the medical device 8480. The display 8482 may also show information of the patient to which the medical network interface is connected (e.g., patient identifier, parameters being monitored, etc.) via the hub 8401 or other medical devices. The display 8482 may also display information indicating the status for the wireless connector or the battery charge status. The display 8482, or any display herein, may also output patient data such as waveforms, trends, and / or physiological parameter values. Thus, the medical network interface described herein may also act as a patient monitor based on data received through the interface port.
[0338] FIG. 84D illustrates a rear view 8400d of the medical network interface 8410. Similar to the view 8400b of FIG. 84B, the rear of the medical network interface 8410 can include two USB ports 8432, three Ethernet ports 8434, and four channel ports 8422. The medical network interface 8410 can also include a battery port 8462. The battery port 8462 can be an example of the battery port 7860 shown in FIG. 78B. The battery port 8462 can be configured to connect the medical network interface 8410 to an AC power outlet in the environment via a power connector. In this exemplary view 8400d, the battery port 8462 accepts a different power connector than the battery port 8460 shown in FIG. 84B.
[0339] As illustrated in FIGS. 77A-78B, the medical network interface 8410 can connect to various medical devices, such as the patient device 7720, the hub 7801, the multi-patient monitoring system 2004, etc., using ports 8432, 8434, 8422, or 8412. For example, one of the USB ports 8432 can be connected to one of the USB ports 8403 on the hub 7801. The other USB port 8432 of the medical network interface 8410 can connect to a physician's computer. In addition to using the USB port 8432, the hub 7801 and the medical network interface 8410 can connect to each other via other technologies, such as, for example, channel ports 8422 and 8407, Ethernet ports 8432 and 8405, or a dedicated port (not shown). In some embodiments, the dedicated port can be located on the top surface of the medical network interface 8410, and a connector to the dedicated port can be attached to the hub 8401. As another example, a dedicated port may be located on the hub 8401 (eg, on the bottom or left / right surfaces) and the connector may be on the medical network interface 8410.
[0340] In some embodiments, the medical network interface 8410 can be used as a docking station for the hub 8401. The medical network interface 8410 can duplicate existing ports already on the hub 8401 or provide additional ports, either alone or in combination. Advantageously, in some embodiments, the medical network interface 8410 can provide a greater number of ports than are physically present on the hub 8401. This allows the hub 8401 to have fewer physical ports (or no such ports at all) while still providing the same range of features. For example, the Ethernet port 8434 can increase the number of Ethernet connections from one (as provided by the Ethernet port 8405) to three. Similarly, the USB port 8432 can provide two additional USB connections and four additional channel ports to the hub 8401, allowing more devices to communicate with the hub 8401 (through the medical network interface 8410).
[0341] As described with reference to FIG. 78B, the medical network interface 8410 may be powered by a battery or connected to an AC outlet when a power cord is plugged into port 8460. In some embodiments, when the hub 8401 is connected to the medical network interface 8410, both the hub 8401 and the medical network interface 8410 may be powered when port 8460 is connected to an outlet via a power cord. As another example, when the hub 8401 is connected to a power source, the power source may be used to power both the hub 8401 and the network interface 8410.
[0342] As shown in FIG. 84A and FIG. 84B, the medical network interface 8410 may be mechanically attached to the hub 8401. For example, the top housing of the medical network interface 8410 may be attached to the bottom of the hub 8401. In various other embodiments, the top housing of the medical network interface 8410 may also be attached to the side or back of the hub 8401. The hub 8401 may also be mechanically attached to a surface of a physical structure in a hospital environment. For example, the bottom of the hub 8401 may be attached to a wall, door, or table in a patient's room. In some embodiments, the medical network interface 8410 is simultaneously attached to the physical structure and the hub 8401, such that the medical network interface is sandwiched between the physical structure and the hub 8401. In other embodiments, the medical network interface 8410 is attached to one side of either the physical structure or the hub 8401, but not both. The medical network interface 8410 can also be attached to the hub 8401 using other mechanisms, such as via magnetic forces where a portion of the medical network interface 8410 (e.g., the top of the medical network interface 8410), a portion of the hub 8401, or both, include magnets.
[0343] FIG. 85A, FIG. 85B, and FIG. 85C show exemplary structures for mechanically mounting the medical network interface. FIG. 85A shows an exemplary top housing 8510 of the medical network interface 8410. The top housing 8510 can have four holes for mounting to the hub 8401 or a physical structure. FIG. 85B shows a bottom view 8520 of the hub 8401. The bottom 8530 can have a connection plate 8524. The connection plate 8524 has four slots 8522 as illustrated in FIG. 85B. The connection plate 8524 can be a VESA standard 75 / 100 connection plate that can have 100×100 mm or 75×75 mm square holes. The connecting plate 8524 in Figure 85B shows a 100x100mm square hole pattern, even though in other examples the connecting plate 8524 can have a 75x75mm square hole pattern or a combination of 75x75mm and 100x100mm square hole patterns (the connecting plate 8524 has 8 slots 8522). Other configurations are possible.
[0344] The top housing 8510 of the medical network interface 8410 can be attached to the bottom of the hub 8401 using screws. For example, four M4 screws can be used to attach the slots 8522 of the connection plate 8524 to the holes 8512 on the top housing 8510.
[0345] In this example, the connection plate 8524 is disposed on the bottom surface of the hub 8401, but the connection plate 8524 does not have to be on the hub 8401. For example, the connection plate 8524 may be disposed on the medical network interface 8410, and the bottom surface of the hub 8401 may include four holes for mounting the medical network interface 8410.
[0346] FIG. 85C shows a bottom perspective view of the medical network interface 8410 after it is attached to the hub 8401. The bottom surface 8540 can include holes 8542. The holes 8542 can also follow a 100×100 mm or 75×75 mm square hole pattern. The medical network interface 8410 can be mounted to a wall using a wall mount. For example, one end of the wall mount can be attached and fixed to the wall, while the other end of the wall mount can include a connection plate with the same hole pattern as the hole pattern of the holes 8542. Thus, the medical network interface 8410 can be attached to a wall mount by attaching the wall mount at the bottom surface 8540 using screws.
[0347] Although a VESA mount is used as an example in FIG. 85A-FIG. 85C, other types of mounting interfaces may be used on the top housing 8510 of the medical network interface 8410, the bottom surface 8540 of the hub 8401, or the bottom surface 8540 of the medical network interface 8410. For example, the hole pattern may also mirror a universal mount. As another example, the medical network interface 8410 and the hub 8401 may be mounted using a GCX® slide-in mount. Furthermore, the top and bottom surfaces of the medical network interface 8410 may not have the same hole pattern. For example, the bottom surface of the medical network interface 8410 may have a hole pattern for a universal mount (which may facilitate wall mounting), but the top surface of the medical network interface 8410 may have a VESA mount. As another example, the medical network interface 8410 may not have holes on both the top and bottom surfaces if the medical network interface 8410 may be mounted on one side. In one embodiment, the holes are located on the top surface of the medical network interface 8410. The top surface is attached to the hub 8401, while the bottom surface may rest on a table top. The medical network interface 8410 may also be mounted alone to a wall (e.g., via the top surface) without the hub 8401 being attached to the bottom surface.
[0348] The medical network interface 8410 does not have to be mounted to the hub 8401 in the same manner as illustrated in FIGS. 85A-85C. The medical network interface 8410 can be mounted on the left side, right side, or back side using the techniques described herein. For example, the back side of the hub 8401 can include a connection plate for mounting the medical network interface 8410 using the VESA standard. Furthermore, it is not necessary that the medical network interface 8410 be attached to the hub 8401 using the top surface of the medical network interface 8410. For example, the bottom surface, left surface, or right surface can also be used to mount the medical network interface 8410 to the hub 8401.
[0349] In addition to or alternatively to mounting to the hub 8401, similar techniques may also be used to mount the medical network interface 8410 with other medical devices, such as the patient device 7720, the device 7760, or other devices illustrated in the computing environments 7700 and 7702. For example, the medical network interface 8410 may be mounted to a patient bed using techniques described herein.
[0350] XVI. Exemplary Mechanical Structures of Wireless Connectors and Dongle Sockets As described herein, the medical network interface 8410 may be communicatively coupled to various devices and systems, such as a hub 8401, an MMS 2004, a patient device 7720, or another medical network interface 8410, using a wired or wireless connection. The medical network interface 8410 may include an interface port 8412 configured to receive a wireless connector 8480. The wireless connector 8480 may be used to pair the medical network interface 8410 with another device to achieve communication in a wireless manner. The interface port 8412 may be a dedicated port, a USB port, or another type of port, as described with reference to FIG.
[0351] The wireless connector 8480 may comprise various software and hardware components for achieving the functionality described above with reference to, for example, Figures 77A-83. Figures 86A and 86B show an example embodiment of the hardware components of the wireless connector. The wireless connector 8480 may be an embodiment of the dongle 7900 described in Figure 79. The dongle 8480 of Figure 86A may comprise a housing 8670, a data storage and processing component 8610, and optionally one or more lights 8654 (e.g., elongated light emitting diodes (LEDs)).
[0352] The housing 8670 can house various hardware components therein. For example, a portion of the data storage and processing component 8610 and a battery 8640 are positioned inside the housing 8670 as shown in FIG. 86B. The battery may be a 3.7V, 280mAh battery, although other specifications are possible. In some embodiments, there are two batteries 8640 inside the housing 8670. As an example, one battery may be positioned on top of the data storage and processing component 8620 and the other battery may be located below the data storage and processing component 8620. The battery 8640 may be charged when the wireless connector 8480 is plugged into the medical network interface 8410 (e.g., via the interface port 8412) as described in FIG. 79 or when the wireless connector is plugged into the standalone patient device 7720 as described with reference to FIGS. 87A-88.
[0353] The data storage and processing component 8610 may include a processing unit 7910. Thus, the data storage and processing component 8610 may perform functions such as pairing, data reception and transmission, and various other functions as described in Figures 77A-83. If the wireless connector 8480 includes a battery 8640, the data storage and processing component 8610 may also include an antenna 7920 in addition to the processing unit 7910. The antenna 7920 may be disposed inside the housing 8670.
[0354] The light 8654 may be an embodiment of the light component 7954 shown in FIG. 79. The light 8654 may comprise a strip of LEDs or a strip of LEDs. As described in FIG. 79, the light pattern that the light 8654 illuminates may indicate the status of the wireless connector 8480. The status may include, among other things, a connection status (e.g., whether the medical device is paired with the medical network interface 8410), a handshake status (which may be part of the connection status), or a battery status. As an example of indicating the battery status, the light 8654 may illuminate a green light when the battery is full and an amber light when the battery is about to be empty. Multiple lights may be provided, such as one light indicating a charging status and one light indicating a connection status, a data transfer status, or the like.
[0355] 86A and 86B, the housing 8670 can house other components therein as well. For example, the housing 8670 can also house a location tag 7930 that can facilitate another device (the hub 8401) determining the location of the wireless connector 8480.
[0356] The wireless connector 8480 can have a back side 8602 and a front side 8604. The front side 8604 can include a light 8654. The back side 8602 can be plugged into an interface port 8412, thereby establishing communication between the wireless connector 8480 and the medical network interface 8410. The back side 8602 can also be plugged into a port in the medical device 8110 to enable the medical device 8110 to communicate with the medical network interface 8410 in a wireless manner.
[0357] In some circumstances, the medical device 8110 may not have a suitable port (e.g., an interface port or USB port) into which the wireless connector 8480 can be plugged. To enable wireless communication via the wireless connector 8480, advantageously, in some embodiments, a dongle socket can be provided with a medical connector for connecting to a port on the medical device 8110. The dongle socket can be provided with the wireless connector 8480, thereby enabling the wireless connector 8480 to be connected to the medical device via the medical connector.
[0358] 87A-87D show an example embodiment of a dongle socket that can connect a medical device with a wireless connector. The dongle socket may be referred to as a dongle in the examples described with reference to FIGS. 87A-88. FIG. 87A shows a medical network interface 8410 attached to a hub 8401 and a dongle 8710 that may be connected to a medical device 8110, such as a pump or vent (see, e.g., FIG. 81).
[0359] The dongle 8710 can include a front side 8702 and a back side 8704. The front side 8702 can include a socket housing 8712 that can house the wireless connector 8480.
[0360] The wireless connector 8480 may have been previously plugged into the medical network interface 8410 for charging or to obtain a permission key. The socket housing 8712 may be connected to a medical device connector 8714 located on the back 8704 of the dongle 8710 via a wire 8724. The medical device connector 8714 may be plugged into a portion of the medical device 8110. The port of the medical device 8110 may be a video graphics array (VGA) port, a digital visual interface (DVI) port, a high definition multimedia interface (HDMI) port, a USB port, an Ethernet port, a dedicated port, or other type of port configured for electronic data transmission. Advantageously, in some embodiments, by connecting the wireless connector 8480 to a port of the medical device 8110 via the dongle 8710, the medical device 8110 may be paired with the medical network interface 8410 and communicate data to the medical network interface 8410 in a wireless manner.
[0361] Additionally or alternatively, pairing between the medical device 8110 and the medical network interface 8410 may be achieved by bringing the dongle 8710 close to the medical network interface 8410. The medical network interface 8410 may automatically scan for nearby devices and identify the dongle 8710 when it comes within range of the medical network interface 8410. In this embodiment, the separate wireless connector 8480 may be omitted, and thus the functionality of the wireless connector 8480 is integrated within the dongle 8710. Alternatively, the dongle 8710 may include a removable wireless connector 8480. The back 8704 of the dongle 8710 may be plugged into the medical device 8110. After the wireless connector 8480 (integrated or separate) in the dongle 8710 is recognized, the medical network interface 8410 may assign and establish a connection to the medical device 8110 (via the wireless connector 8480). Advantageously, in some embodiments, by integrating the functionality of the wireless connector 8480 with the dongle 8710 (e.g., by having a transceiver and battery integrated with the dongle 8710), the dongle 8710 can be paired by simply bringing the dongle 8710 within wireless range of the medical network interface 8410.
[0362] In some embodiments, the wireless connector 8480 does not have a battery and the medical device 8110 can provide power to the wireless connector 8480 via the dongle 8710. For example, the medical device 8110 can be plugged into a power outlet and direct power to the dongle 8710 via the medical device connector 8714.
[0363] The wireless connector 8480 or dongle 8710 can also be wirelessly charged, thereby reducing the need to physically plug into the medical device 8110 or medical network interface 8410. The wireless charging functionality can be enabled by any one of the medical device 8110, medical network interface 8410, or hub 8401. The medical device 8110, medical network interface 8410, or hub 8401 can include a transmitter that can be powered by an alternating current and generate a magnetic field, which can then induce a current in a receiver in the wireless connector 8480 or dongle 8710 to wirelessly charge the wireless connector 8480.
[0364] In some circumstances, the dongle 8710 may connect to a port on the medical device 8110 that is not configured to provide power. As a result, the dongle 8710 may include a power cable 8726 for charging the wireless connector 8480, and the dongle 8710 is connected to a port on the medical device 8110. The power cable 8726 may be connected to the socket housing 8712 at one end and to a power source at the other end. The power source may be obtained, for example, from another port on the medical device 8110 or from a wall socket. The power cable 8726 may be implemented using various types of cables, such as coaxial cables, ribbon cables, twisted pair cables, or shielded cables. In some embodiments, the power cable 8726 may be a USB cable. In addition to or instead of the power cable 8726 and the medical device connector 8714, the dongle may also include other types of cables. In other embodiments, these cables may be connected to the front end 8702 of the dongle 8710 via the socket 8738. Power cable 8726 may be useful for connecting with older devices that typically do not have a power source and use RS232 (e.g., to connect to port 8714). For devices that have a USB connection or other powered connection, port 8714 may be a USB port and power cable 8726 may be omitted.
[0365] If the wireless connector 8480 can be charged via the cable 8726 of the dongle 8710 or via the medical device 8110, the hub 8401 may not need to provide the functionality for accepting or charging the wireless connector 8480. For example, the wafer under the hub 8401 may not have a slot for charging.
[0366] Although the example of FIG. 87A is described with reference to connecting the wireless connector 8480 to the medical device 8110 via a dongle 8710, the wireless connector 8480 can be connected directly to the medical device 8110, where the medical device 8110 has an available interface port 8412.
[0367] FIG. 87B illustrates exemplary components of the dongle 8710. The dongle 8710 can include a socket housing 8712, a medical device connector 8714, a wire 8724 (for connecting the medical device connector 8714 to the housing 8712), and a power cable 8726. The socket housing 8712 can have a front end 8722a and a rear end 8722b. The front end 8722a can include an opening that is generally shaped to receive the wireless connector 8480. Although not shown, there can be a connector on the inside of the socket housing 8712 that receives the connector on the wireless co...
Claims
1. 1. A pulse oximetry system operable to measure a blood parameter of a patient and transmit said blood parameter along with a third party medical device parameter to a remote device, comprising: a patient monitor configured to measure the blood parameter of the patient by obtaining a signal from an optical sensor coupled to the patient, the signal corresponding to light attenuated by biological tissue of the patient; The patient monitor is configured to communicate with a medical network interface over a hospital network that transmits the measured blood parameters and third party medical device parameters from a third party medical device, the medical network interface comprising: a plurality of ports, at least one of the ports being configured to accept a wireless dongle; a network interface controller configured to implement a wireless communications stack; a memory configured to store processor-executable instructions; 1. A processor comprising: providing the wireless dongle with information sufficient to enable the wireless dongle to provide wireless connectivity to the third party medical device; wirelessly pairing with the wireless dongle in response to receiving a pairing request signal from the third party medical device in response to the wireless dongle being inserted into the third party medical device; After pairing, wirelessly receiving a data stream from the wireless dongle, the data stream including an identifier of the third party medical device and the third party medical device parameters associated with the patient; Associating the data stream with an identifier for the patient, an identifier for the medical network interface, and an identifier for the patient monitor to generate a modified data stream; and a processor programmed to execute instructions to transmit the modified data stream, the measured blood parameters, and the third party medical device parameters over a hospital network and to allow the modified data stream and the measured blood parameters to be accessed by a clinician.
2. 10. The pulse oximetry system of claim 1, wherein the plurality of ports includes two or more of a Universal Serial Bus port, an Ethernet port, and a serial port with patient isolation hardware.
3. 10. The pulse oximetry system of claim 1, wherein the processor is further programmed to receive an optical scan of a patient wristband, thereby obtaining the patient identifier.
4. The processor, generating a permission key for pairing the third-party medical device with the medical network interface; communicating the permission key to the third-party medical device; receiving a communication from the third party medical device having the permission key; 10. The pulse oximetry system of claim 1, further programmed to establish communications with the third party medical device in response to determining that the permissions key is authenticated.
5. 5. The pulse oximetry system of claim 4, wherein in response to determining that the permissions key is authenticated, the processor is further programmed to link the patient identifier and the medical network interface identifier to an identifier of the third-party medical device.
6. 10. The pulse oximetry system of claim 1, wherein the wireless dongle or the medical network interface further comprises a display configured to indicate at least one of a status of the medical network interface, a status of a first medical device, a status of a second medical device, or a status of pairing between the first medical device and the second medical device.
7. 10. The pulse oximetry system of claim 1, wherein the wireless dongle or the medical network interface further comprises a light configured to indicate at least one of a status of the medical network interface, a status of the first medical device, a status of the second medical device, a status of pairing between the first medical device and the second medical device, or a power status associated with the dongle.
8. 10. The pulse oximetry system of claim 1, wherein the plurality of ports comprises a first port of a first color and a second port of a second color.
9. 2. The pulse oximetry system of claim 1, wherein data received from the first port is automatically associated with the patient identifier and data received from the second port is automatically associated with a second patient identifier for a second patient.
10. 2. The pulse oximetry system of claim 1, wherein the wireless dongle comprises two pieces, a first piece that remains connected to the medical network interface and a second piece that disconnects from the first piece.
11. 11. The pulse oximetry system of claim 10, wherein the second piece connects at a corresponding first piece of a second dongle in the standalone medical device.
12. The processor, Accessing a first identifier for pairing the third party medical device with the medical network interface; communicating the first identifier to the third party medical device; receiving a communication from the third party medical device having the first identifier; 10. The pulse oximetry system of claim 1, further programmed to establish communication with the third party medical device in response to determining that the first identifier is authenticated.
13. 2. The pulse oximetry system of claim 1, wherein the medical network interface comprises a front face and a back face, the front face comprising an interface port configured to receive the wireless dongle.
14. 14. The pulse oximetry system of claim 13, wherein the wireless dongle is associated with a power cable extending between the socket housing and the medical device connector, the power cable configured to power the wireless dongle.
15. 1. A method comprising: detecting an insertion of a wireless dongle into a port of a medical network interface; In response to said insertion, providing an identifier to the wireless dongle, the wireless dongle communicating the identifier to the standalone medical device upon insertion into the standalone medical device; after removing the wireless dongle from the port of the medical network interface; receiving, by a hardware processor, a pairing request signal from the standalone medical device, the pairing request signal including the identifier previously provided to the wireless dongle; After the pairing, providing one or both of a visual or audio indication that the pairing was successful; wirelessly receiving a data stream from the stand-alone medical device, the data stream including patient data associated with a patient; associating the data stream with an identifier for the patient and an identifier for the medical network interface to generate a modified data stream; transmitting the modified data stream to a server over a hospital network and enabling distribution of the modified data stream from the server to a plurality of devices.
16. 16. The method of claim 15, wherein the providing step includes the step of activating a light.
17. 16. The method of claim 15, wherein the providing step includes outputting information on a display, and optionally, the information includes the identifier of the standalone medical device.
18. 16. The method of claim 15, wherein the pairing request is a modified Bluetooth pairing request that does not require entering a PIN or other number or password into either the medical network device or the standalone medical device.
19. The method of claim 15, further comprising associating an identifier of the standalone medical device with the data stream.
20. 16. The method of claim 15, further comprising obtaining the patient identifier from an optical scan of a wrist bracelet worn by the patient.
Citation Information
Patent Citations
Remote monitoring of analyte measurements
CN108937856A
Systems and methods for diabetes management using consumer electronic devices
JP2010510586A
Systems, methods, and apparatus for electronic patient care
JP2015508526A
Secure communication between medical devices and their remote devices
JP2015531184A
Remote monitoring of sample measurement
JP2016512965A
