Providing Visual Representations of Patient Monitoring Data

Abstract

providing a patient monitor and a separate user interface for said patient monitor adapted to communicate with each other via a communication path, both of which are capable of independently ascertaining the status of the communication path and visually indicating this status;

Description

Technical Field

[0001] The present invention relates to the field of monitoring patients, and more particularly to the handling of patient monitoring data.

Background Art

[0002] In a clinical environment, such as an intensive care unit or a neonatal intensive care unit, patient monitors are routinely used to autonomously monitor the physiological data of a subject or patient. The patient monitor is adapted to generate patient monitoring data, which can include physiological data and / or data derived from such physiological data.

[0003] It is somewhat common for a patient monitor to generate alarm data, which indicates whether an alarm event (which is either a physiological or technical event important for patient safety) has occurred, and the alarm event is an indication that the patient or the patient monitor has entered an undesirable state. For example, an alarm event related to a physiological property indicates a decrease in the subject's heart rate or SpO2 level, while a technical alarm event indicates a decrease in battery level or a malfunction of the patient monitor.

[0004] Typically, the visual representation of patient monitoring data (and in particular alarm data) is provided by the patient monitor via a two-dimensional screen that is directly connected to the rest of the patient monitor via a wired or other electrical connection, such as via a VGA (Video Graphics Array) cable. In fact, this method of providing a visual representation using a direct wired connection has generally been considered essential to ensure that the patient monitor meets clinical compliance requirements (e.g., providing notification of an alarm event or sufficiently up-to-date information regarding the patient's physiological parameters within a clinically acceptable period).

[0005] It is also known to provide or utilize an additional user interface, such as a tablet or mobile phone, that receives updated information from a patient monitor via a wired or wireless channel. These user interfaces complement the two-dimensional screen of the patient monitoring device by mirroring the visual representation and / or providing additional information regarding the patient monitoring data. Generally, these user interfaces operate by the patient monitor sending an update of the patient monitoring data to the user interface. SUMMARY OF THE INVENTION PROBLEMS TO BE SOLVED BY THE INVENTION

[0006] There is currently a desire to increase the flexibility and usefulness of patient monitoring systems. It is also desirable to reduce the number of alarms or warnings provided to caregivers / clinicians. MEANS FOR SOLVING THE PROBLEMS

[0007] The present invention is defined by the claims.

[0008] According to one aspect of the present invention, there is provided a patient monitor for generating patient monitoring data visually represented by a two-dimensional display screen of a user interface.

[0009] The patient monitor includes a communication system adapted to transmit patient monitoring data via a communication path between the patient monitor and the user interface and to monitor the state of the communication path between the patient monitor and a communication module of the user interface, an input module adapted to obtain physiological data of a patient from one or more patient sensors, a secondary alarm module adapted to provide an output perceptible to a user, Monitor the state of the patient monitor, obtain the physiological data, generate patient monitoring data in response to the physiological data, control the user-perceivable output of the secondary alarm module in response to the state of the communication path, and control the user-perceivable output of the secondary alarm module in response to the state of the patient monitor, and adapt accordingly. A processor of the patient monitor, and An audible output module controlled by the processor of the patient monitor having, the processor of the patient monitor, in response to the state of the communication path indicating that the communication path can successfully carry patient monitoring data and the user interface having an audible output module, prevents any audible output from being generated by the at least one audible output module in response to the alarm data.

[0010] According to the proposed embodiment, there is provided a patient monitor adapted to suppress / mute / prevent an audible output in response to the communication path being capable of carrying patient monitoring data to a connected user interface having an audible output module. Thus, when the user interface can provide an audible output (provided by the patient monitor in another way), the audible alarm in the patient monitor can be suppressed.

[0011] In particular, the patient monitor can be adapted to suppress / mute / prevent an audible output in response to the communication path being capable of carrying patient monitoring data to a connected user interface that can provide an audible output, where the patient monitoring data includes alarm data.

[0012] Some clinical compliance guidelines require the generation of an audible alarm in response to an alarm event (e.g., the patient's heart rate dropping below a predetermined value). In such a scenario, the patient monitor can be adapted to suppress the audible output in response to the communication path being capable of carrying patient monitoring data (including alarm data) and the user interface having a speaker adapted to provide an audible output in response to the patient monitoring data. This enables the clinical compliance guidelines to be safe while reducing the number of audible alarms output by the patient monitor. Reducing the number of audible alarms output by the patient monitor, for example, reduces the stress or anxiety experienced by the patient (and / or nearby patients).

[0013] When the connection to the user interface is stable, the audible alarm is suppressed, prevented, or stopped by the patient monitor. This makes the environment near the patient quieter (since the user interface is placed away), reduces the stress on the patient and the clinician, and reduces the alarm fatigue of the clinician working with the patient. This enables the configuration of the patient monitoring system to be more flexible.

[0014] The proposed patient monitor also enables communication with the user interface in a reliable manner while notifying the clinician of any change in the state of that communication. Such notification enables the clinician to manually pay attention to the patient (i.e., prevent the patient from entering an undesirable clinical state without being pointed out by the patient monitor).

[0015] By checking the state of the communication path / channel, a safe and stable connection to the user interface is ensured. Thus, the patient monitor does not need to have a screen itself for providing the clinician with a visual representation of the patient monitoring data. This feature provides a less expensive patient monitor and enables the centralized visual representation of different patients.

[0016] This allows the proposed patient monitor to enable a more flexible system while also avoiding the need for the patient monitor to have its own screen for displaying patient monitoring data. Thus, the patient monitor may be "headless".

[0017] Monitoring the state of the patient monitor ensures that the patient monitor itself is reliable. Monitoring the state of the patient monitor involves using one or more watchdogs or watchdog timers to repeatedly check or monitor whether the patient monitor has encountered a malfunction or entered an unexpected state. The patient monitor is adapted to ensure that the state of this patient monitor is provided to the user or otherwise indicated, thereby providing a "reliable patient monitor".

[0018] The processor of the patient monitor can be further adapted to monitor the state of the user interface and control the secondary alarm module in response to the state of this user interface.

[0019] In particular, the patient monitor can be adapted to control the secondary alarm module to respond to patient monitoring data in response to determining that the user interface is not functioning (as indicated by the state). This ensures that patient monitoring data continues to be provided or output even if the user interface itself malfunctions.

[0020] In some embodiments, the patient monitor can be adapted to control the secondary alarm module to respond to patient monitoring data in response to determining that the communication path has failed or otherwise cannot successfully convey patient monitoring data.

[0021] In some embodiments, the patient monitor can be adapted to control the secondary alarm module to not respond to patient monitoring data in response to determining that neither the communication path nor the user interface has ceased to function.

[0022] Patient monitoring data generated by a processor of the patient monitor can include alarm data indicating the presence or absence of an alarm event indicating that the patient or the patient monitor has entered an undesirable state.

[0023] In some embodiments, in response to the state of the communication path indicating that the communication path has ceased to function or otherwise cannot successfully convey patient monitoring data, the processor of the patient monitor is adapted to use at least one audible output module to generate an audible output in response to the alarm data.

[0024] The patient monitor is preferably configured to not have any two-dimensional screen for providing a visual representation of patient monitoring data and / or not be able to communicate with a device having a two-dimensional screen via a wired communication path. This helps to reduce the cost and complexity of the patient monitor while ensuring that patient monitoring data can be viewed (via the user interface).

[0025] The communication system is adapted to selectively communicate with two or more different user interfaces.

[0026] Thus, if the communication path or the user interface ceases to function, a new user interface is paired or coupled with the patient monitor to enable a visual representation of the patient monitoring data to be viewed.

[0027] Of course, embodiments enable two or more user interfaces to view (the same or different) patient monitoring data related to the same patient to provide a more flexible working environment.

[0028] The communication system can be adapted to initiate transmission of patient monitoring data to different user interfaces in response to the communication path's state indicating that the communication path has ceased to function or otherwise cannot carry patient monitoring data. This may include establishing a new communication path to a different user interface, the method of which is known in the art.

[0029] According to the proposed concept, a user interface can be provided for providing a visual representation of patient monitoring data obtained by a patient monitor adapted to monitor a patient's physiological parameters.

[0030] The user interface has a communication module that receives patient monitoring data from the patient monitor via a communication path between the patient monitor and the user interface and is adapted to monitor the state of the communication path, an output module for providing user-perceivable output, an output module coupled to a two-dimensional display screen for generating visual output, and a processor of the user interface. The processor of the user interface monitors the states of the user interface and the display screen, obtains patient monitoring data from the communication module, controls the two-dimensional display screen to provide a visual representation of the patient monitoring data based on the patient monitoring data, controls the output module to provide user-perceivable output indicating the state of the communication path, and controls the output module to provide user-perceivable output indicating the state of the user.

[0031] The proposed user interface enables a more flexible patient monitoring system. In particular, the visual representation of patient monitoring data and the delivery of user-perceivable alerts are provided remotely and reliably, eliminating the need to provide a visual representation on the patient monitor itself.

[0032] As a general rule, for the purpose of clinical compliance, the visual representation of patient monitoring data and the delivery of any alerts actuated by physiological or technical events must be reliable and must guarantee that the latest available acquisitions of patient monitoring information are represented. The proposed user interface enables the reliability of the communication from the patient monitor to be guaranteed, thereby meeting the clinical compliance requirements without the need for a physical connection. This improves the flexibility of the entire patient monitoring system.

[0033] In some embodiments, the processor of the user interface is further adapted to monitor the state of the patient monitor and to control the output module to provide a user-perceivable output indicating this state of the patient monitor. This is done, for example, by monitoring the heartbeat signal generated by the patient monitor.

[0034] In some embodiments, the process of monitoring the state of the user interface, performed by the processor of the user interface, has the repeated confirmation, using one or more watchdog timers, of whether the user interface has encountered a malfunction.

[0035] Monitoring the state of the user interface guarantees that the user interface itself is reliable. Monitoring the state of the user interface has the repeated / iterative confirmation or monitoring, using one or more watchdogs or watchdog timers, of whether the user interface has encountered a malfunction or entered an unexpected state. The user interface is adapted, in particular, to guarantee that the state of the user interface is provided to the user or otherwise indicated, thereby providing a "reliable user interface". The patient monitoring data may have alarm data indicating the presence or absence of an alarm event indicating that the patient or the patient monitor has entered an undesirable state.

[0036] The output module may have a speaker for generating voice output, and the processor may be further adapted to control the speaker to provide a voice representation of patient monitoring data and / or the status of the communication path (e.g., when an alarm related to a physiological event is activated).

[0037] Voice output of patient monitoring data (e.g., alarm data) is a requirement for meeting several clinical compliance guidelines. By providing voice output in the (remote) user interface, the voice output at the patient's location (patient monitor) can be muted, suppressed, or stopped in other ways. This can make the environment near the patient quieter, reduce the patient's stress, reduce distraction for the clinician, and (if the patient monitoring data includes alarm data) reduce alarm fatigue for the clinician near the patient.

[0038] The communication module is adapted to monitor the status of the communication path by repeatedly verifying the presence of a bidirectional link provided by the communication path, where the duration between successive verifications is less than 3 seconds.

[0039] Performing such repeated verifications can enhance compliance with the clinical guidelines of the entire patient monitoring system. In particular, such periodic verifications can ensure that either the patient monitoring data is updated at sufficient intervals for the clinician to monitor, or (e.g., so that the clinician can manually check the patient's status) the clinician is alerted to communication failures. This reduces the possibility that the patient may enter a clinically undesirable state for a long period without the clinician (observing the user interface) noticing.

[0040] The communication module can be adapted to communicate selectively with two or more different patient monitors.

[0041] In another embodiment, the user interface further includes, for example, a two-dimensional display screen that is part of the output module.

[0042] According to an example of another aspect of the present invention, there is provided a patient monitoring system having at least one user interface described herein and at least one patient monitor described herein.

[0043] Having both the user interface and the patient monitor allows for checking their own status, and the communication path ensures that end-to-end reliable verification is performed. This means that the entire patient monitoring system is reliable by ensuring that the user is warned of any problems when presenting patient monitoring data to the user (for example, during generation of patient monitoring data in the patient monitor, while communicating this data to the user interface, or during display of patient monitoring data). This reduces the possibility that, for example, if the patient monitoring system fails, the user will not notice and the patient will enter a clinically undesirable state or the medical device will malfunction, as the user is prompted to manually check the patient monitor.

[0044] According to an example of another aspect of the present invention, there is provided a method of supplying patient monitoring data to a user interface for display using a patient monitor having a secondary alarm module adapted to controllably generate a user-perceivable output.

[0045] The method includes steps of obtaining physiological data of a patient from one or more patient sensors, generating patient monitoring data responsive to the physiological data, transmitting the patient monitoring data to a user interface via a communication path, monitoring a state of the communication path, monitoring a state of a patient monitor, controlling a user-perceivable output of a secondary alarm module responsive to the state of the communication path, controlling a user-perceivable output of the secondary alarm module responsive to the state of the patient monitor, determining whether the user interface has an audible output module, and preventing any audible output module of the patient monitor from generating an audible output in response to alarm data in response to the state of the communication path indicating that the communication path can successfully carry patient monitoring data and the user interface has an audible output module.

[0046] A method of displaying patient monitoring data obtained by a patient monitor on a user interface coupled to a two-dimensional display screen is also provided. The method includes steps of receiving patient monitoring data from the patient monitor via a communication path, controlling the two-dimensional display screen to provide a visual representation of the patient monitoring data based on the patient monitoring data, monitoring a state of the communication path between the patient monitor and the user interface, monitoring states of the user interface and the two-dimensional display screen, controlling an output module to provide a user-perceivable output indicating the state of the communication path, and controlling the output module to provide a user-perceivable output indicating the state of the user interface.

[0047] According to an example of another aspect of the present invention, a computer program having code means for the method described herein is provided when the computer program is executed on a processing system.

[0048] These and other aspects of the invention will become apparent from, and will be elucidated with reference to, the embodiments described hereinafter.

Brief Description of the Drawings

[0049] For a better understanding of the present invention and to more clearly show how the present invention is implemented, the accompanying drawings are referred to by way of example only.

Figure 1

Figure 2

Figure 3

Figure 4

Modes for Carrying Out the Invention

[0050] The present invention will be described with reference to the drawings.

[0051] It should be understood that the detailed description and specific examples, while indicating exemplary embodiments of the apparatus, system, and method, are for the purpose of illustration only and are not intended to limit the scope of the present invention. These and other features, aspects, and advantages of the apparatus, system, and method of the present invention will be better understood from the following description, the appended claims, and the accompanying drawings. It should be understood that the drawings are merely schematic and are not drawn to scale. It should be understood that the same reference numbers are used throughout the drawings to indicate the same or similar parts.

[0052] The present invention provides a new and flexible concept for a patient monitoring system that obviates the need for a display and / or an alarm system near the patient. The concept of the present invention is achieved using two interrelated products, namely, a patient monitor and a separate user interface for this patient monitor. These patient monitor and separate user interface are adapted to communicate with each other via a communication path. Both the patient monitor and the separate user interface can independently check their own and the state of the communication path and visually indicate the results of checking these states. This helps not only to provide a reliable connection between the patient monitor and the user interface but also to have up-to-date information regarding the "wellbeing" of each of these devices and to help ensure that clinical compliance guidelines are met.

[0053] Embodiments can be used in a clinical environment, such as a hospital ward or an intensive care unit, where (automated) patient monitoring is performed.

[0054] FIG. 1 shows a patient monitoring system 1 according to an embodiment of the present invention. This patient monitoring system has a user interface 100 and a patient monitor 150.

[0055] The user interface 100 represents one embodiment of the concept of the present invention, the patient monitor 150 represents another embodiment of the concept of the present invention, and the patient monitoring system 1 represents yet another embodiment of the concept of the present invention.

[0056] The user interface 100 has a communication module 101 and an output module 102 having a user interface processor 103 and preferably a two-dimensional display screen 102A. The user interface is adapted to provide a visual representation of patient monitoring data obtained by the patient monitor on the display screen.

[0057] The output module is shown as having a display screen 102A which is an integral part of this output module. However, those skilled in the art will also understand that the user interface 100 having the output module 101 can be coupled to an external display screen in the form of a separate unit.

[0058] The user interface 100 can be any device that conveys patient monitoring data and is capable of displaying this data on a two - dimensional display screen, such as, for example, a mobile phone, a tablet, a laptop, a computer, a smartwatch, and smart glasses.

[0059] The patient monitor 150 has a communication system 151, an input module 152, a secondary alarm module 153, and a processor 154 of the patient monitor. The patient monitor 150 is adapted to monitor one or more physiological characteristics of a patient and generate patient monitoring data that is visually presented by the user interface.

[0060] As those skilled in the art will understand, the operations of the user interface 100 and the patient monitor are controlled by the processor 103 of the user interface and the processor 154 of the patient monitor, respectively.

[0061] The user interface 100 and the patient monitor 150 communicate with each other, at least by the patient monitor 150 transmitting patient monitoring data to the user interface 100. In particular, the communication module 101 of the user interface 100 is adapted to receive information / signals (having patient monitoring data) from the patient monitor 150, and the communication system 151 of the patient monitor 150 is adapted to transmit information (having patient monitoring data) to the user interface 100.

[0062] Preferably, the communication between the user interface 100 and the patient monitor 150 is bidirectional, i.e., the user interface can supply input to the patient monitor and vice versa. For example, when selected by the user, the user interface 100 can be adapted to control a visual representation of the acquired physiological data in the form of a waveform. Depending on the expertise of the user (physician or nurse), it may be beneficial to display the physiological waveforms on the display screen in a different order or arrangement. Further, the user interface enables the user to change the thresholds for activating physiological alarms on the patient's side.

[0063] Preferably, to improve freedom, the communication path is a wireless communication path. Thus, the user interface 100 and the patient monitor 150 communicate wirelessly with each other at least by the patient monitor 150 wirelessly transmitting patient monitoring data to the user interface 100.

[0064] Generally speaking, there may also be unreliable communication paths, such as those that depend on components that cannot be controlled by the provider / operator of the user interface and / or patient monitor, for example.

[0065] A communication path is considered wireless if at least a part (e.g., part or all) of the communication path between the patient monitor and the user interface (through which communication occurs) is performed via a wireless channel.

[0066] In such embodiments, any suitable wireless communication protocol or technology is used. Suitable wireless communication protocols used by the patient monitor and the user interface for communication include, for example, infrared links, Zigbee®, Bluetooth®, wireless LANs such as those compliant with the IEEE 802.11 standard, and telecommunication protocols such as 2G, 3G, or 4G. Other forms will be readily apparent to those skilled in the art.

[0067] Communication via the communication path between the patient monitor and the user interface is encoded or formatted using MDDL (medical device data language) or by establishing a TCP (Transmission Control Protocol) link between the patient monitor and the user interface. Other suitable ways of encoding or formatting data will be apparent to those skilled in the art.

[0068] Preferably, the communication path provides a direct communication link between the patient monitor and the user interface using, for example, Near Field Communication (NFC), Bluetooth® or ZigBee® protocol. In other embodiments, the communication path is a personal area network or local area network established using Wi-Fi technology (but without a wide area network). In yet other embodiments, the communication path has a wide area network, such as the Internet.

[0069] Communication from the patient monitor to the user interface includes patient monitoring data generated by the patient monitor (examples of which are described below). Thereby, such communication enables the patient monitor to effectively stream the patient monitoring data to the user interface.

[0070] The user interface 100 (processor 103 thereof) obtains patient monitoring data and controls the screen 102A to display a visual representation of the patient monitoring data (e.g., in the form of waveforms and numerical representations). An example of a suitable visual representation is shown in FIG. 1.

[0071] In some examples, the output module 102 further includes a speaker 102B for generating audio output. (Even if the speaker could be used alternatively or additionally for other purposes described below) The processor 103 of the user interface 100 can control the speaker 102B in response to patient monitoring data. Of course, the speaker may be controlled via an I2S interface, a digital audio path, a digital-to-analog converter (DAC), an amplifier, etc.

[0072] Patient monitoring data responds to at least the patient's physiological data, but can also respond to other parameters or variables. By way of example, patient monitoring data can respond to the state of a patient monitor or a physiological / patient sensor that communicates with this patient monitor.

[0073] Methods for generating patient monitoring data are well known to those skilled in the art. Typically, such methods include, in the input module 152, receiving one or more physiological data streams / signals from patient sensors (not shown), such as a heart rate monitor and a pulse oximeter. The patient monitor 150 (processor 154 thereof) is adapted to receive such information and generate patient monitoring data for display (e.g., in the form of waveforms).

[0074] In some embodiments, the patient monitor 150 has one or more patient sensors (not shown) for the monitor itself to directly obtain the patient's physiological data, and can have, for example, one or more of a camera, a heart rate monitor, a respiratory rate monitor, a pulse oximeter, and a blood pressure monitor.

[0075] Patient monitoring data can have, for example, the physiological information of a patient (such as heart rate, respiratory rate, SpO2 level, body temperature, urine volume, etc.). The physiological information can be, for example, information regarding any vital sign of the patient, any other sign / symptom of the patient, or any other measurable quantity of the patient or a treatment device applied to the patient (such as the amount remaining in the intravenous drip or the current battery level of the pacemaker).

[0076] In addition to the data responsive to the patient's physiological information, the patient monitoring data can further have data responsive to the state of the patient monitor and / or any patient sensor communicating with the patient monitor. For example, the patient monitoring data can have an indication of whether an electrode (for example, for monitoring heart rate) is electrically connected to the patient. Thus, the data transmitted to the user interface 100 can include the medical data of the patient (physiological data obtained by at least one sensor), technical data regarding the functions of the patient monitor or various units coupled to the patient monitor, and the results of checking the state of the patient monitor and the communication path.

[0077] Preferably, the patient monitoring data has alarm data indicating the occurrence or presence of an alarm event.

[0078] As described above, an alarm event is an indication that the patient or the patient monitor has entered an undesirable state. For example, the alarm event can indicate that the subject's heart rate or SpO2 level is low, the battery level is low, the lead wire is disconnected, or there is a malfunction of the patient monitor. In particular, when the level of the measured physiological parameter exceeds a predetermined threshold (for example, exceeds the maximum threshold or is below the minimum threshold), an alarm event occurs.

[0079] For example, it is clear that the method of generating alarm data by comparing the value of the obtained physiological data with one or more thresholds or by receiving an interrupt from an element of the patient monitor is readily apparent to those skilled in the art.

[0080] In such an example, when an alert event is detected in the received patient monitoring data or transmitted with the data, the user interface 100 can display a visual representation of the alert (e.g., a warning symbol such as red light or an exclamation mark) on the screen 102A. In an embodiment where the user interface has a speaker 102B for generating audio output, the processor can control the speaker to generate an audio warning in response to the alert event (e.g., a fast beep sound or a continuous beep sound when an alert event occurs, or silence when no alert event occurs). In some examples, the output module 102 further has a dedicated (i.e., separate from the screen 102A) warning light output 102C that can visually indicate the occurrence of the alert event to assist in providing a characteristic identification of the alert event.

[0081] The patient monitoring data is formatted to be suitable for being handled by the processor of the user interface such that a visual representation of this patient monitoring data is provided.

[0082] For example, the patient monitoring data may be formatted as raw data (e.g., raw physiological data or raw alert events) for being processed into a visual representation by the processor of the user interface. In such an embodiment, the user interface is adapted to receive the patient monitoring data and generate display data for controlling a two-dimensional screen to provide a visual representation of this patient monitoring data.

[0083] In other examples, the patient monitoring data may be formatted as display data such as numerical values and waveforms (which define a visual representation on a two-dimensional display screen). This enables the patient monitor 150 to control the appearance of the visual representation provided by the user interface 100 on screen 102B. This reduces the processing power required of the user interface 100.

[0084] In this way, since the patient monitor 150 defines the visual representation displayed by the screen of the user interface, this visual representation provides information regarding the patient monitoring data.

[0085] Both the user interface 100 and the patient monitor 150 are adapted to independently monitor the state of the communication path 190 between the user interface 100 and the patient monitor 150.

[0086] In particular, the user interface 100 and the patient monitor 150 are adapted to independently determine whether the communication path is not functioning and / or whether the communication path is unable to successfully convey / stream patient monitoring data from the patient monitor. In other words, the user interface 100 and the patient monitor 150 each determine whether the communication path is stable enough to convey the patient monitoring data. A failure in the conveyance of this information may be due to, for example, the user interface 100 going out of range, the user interface not functioning (e.g., battery drained), or the communication path being bandwidth saturated, e.g., due to excessive traffic / noise (e.g., transmissions from other patient monitors within the same frequency band).

[0087] In a preferred embodiment, the user interface and the patient monitor can be adapted to determine whether the communication path can successfully convey patient monitoring data from the patient monitor to the user interface within a predetermined time period, thereby determining the state of the communication path. The length of this predetermined time period is preferably greater than or equal to the allowable delay for generating an alarm perceptible to the user in response to an undesirable condition of the patient, for example, according to clinically acceptable guidelines. For example, the length of this predetermined time period is preferably less than 3 seconds and can be in the range of 0.1 to 3 seconds, such as 0.1 to 2 seconds or 0.1 to 1 second.

[0088] The user interface 100 monitors the state of the communication path 190 using a communication module. The patient monitor 150 monitors the state of the communication path 190 using a communication system.

[0089] Methods for monitoring the state of a communication path are known to those skilled in the art and depend on the type, structure, format, or protocol of the communication path.

[0090] As a simple example, the state of the communication path is confirmed by initiating a handshake protocol or pinging another device on the communication path. The response from this other device is confirmed (e.g., the time lag in the communication path is confirmed), and this response is used to determine the state of the communication path.

[0091] In another example, a certain communication protocol involves transferring (a certain amount of) information at regular intervals. By determining whether the information is received within the regular interval, the state of the communication is confirmed, where a communication failure indicates a deterioration of the communication path, i.e., a change in state.

[0092] In yet another example, the communication protocol has timestamping communication (e.g., from the patient monitor to the user interface or vice versa). The state of the communication path can be verified by determining whether a timestamped communication has been received within a predetermined time period (from the timestamp), and this predetermined time period can be the expected length of time for the communication being made. The inability to receive the communication within this predetermined time period indicates a deterioration of the communication path, i.e., a change in state.

[0093] Both the user interface 100 and the patient monitor 150 are adapted to monitor their own states. Thus, the user interface 100 monitors the state of the user interface 100 and the display screen coupled to the user interface, and the patient monitor monitors the state of the patient monitor 150. Therefore, the processors of the user interface 100 and the patient monitor 150 are adapted to independently monitor their own functions (such as battery level, software errors, and the state of the output module, etc.).

[0094] In some embodiments, the patient monitor 150 can be adapted to check whether there are any problems (errors) in the generation and delivery of patient monitoring data, i.e., whether the patient monitoring data is reliably generated and delivered. Similarly, the user interface 100 is adapted to check whether there are any problems in receiving the patient monitoring data and displaying it on the display screen (e.g., from the reception of the patient monitoring data to the display of the patient monitoring data).

[0095] The advantage of this solution is to enable any display screen with user interface functionality. Usually, the display screen of a patient monitor needs to comply with strict medical requirements. In that case, the visualization functions of the display screen (contrast, active pixels, etc.) need to be always available for several months if not years. This requirement increases the price of the patient monitoring system. The present invention advantageously provides an alternative solution that does not impose strict requirements on the display screen, but enables physiological data to be monitored and provides a self-check status function to the user interface. This self-check status function also includes monitoring the visual performance of the display, which notifies the user immediately when the quality of the display falls below the medically imposed threshold.

[0096] Methods for monitoring the state of an electronic device (e.g., user interface and patient monitor), i.e., for detecting the occurrence of malfunctions within the electronic device, are well known to those skilled in the art.

[0097] The present invention enables any device with a display screen and speakers to be an active device for patient alarm management as long as the user interface guarantees the reliable functionality of a separate unit coupled, for example, to the display screen and / or speakers.

[0098] In a particular example, a software and / or hardware watchdog, such as a watchdog timer, is used to monitor the state of the electronic device. The watchdog operates to ensure that a status display is provided. In particular, the presence or absence of malfunctions is detected. Thereby, the watchdog ensures that the electronic device is reliable. In particular, since the watchdog operates in a "fail-safe" mode, a system or electronic device malfunction is noticed by the operator of this device.

[0099] Some methods for monitoring the state of an electronic device include monitoring the state of an output module, such as a speaker or an audible output module. A malfunction of the output module indicates a malfunction of the electronic device.

[0100] As a mere example, a method for monitoring a state includes controlling the speaker or the audible output module to supply an inaudible test signal, so that a measurement circuit can obtain the magnitude of the signal at the frequency of this test signal. This magnitude can be used to obtain information regarding the function / state of the speaker or the audible output module and the electrical connection to a host device (i.e., a user interface or a patient monitor).

[0101] In particular, the measurement circuit can be adapted to measure an alternating current in the signal path of the audible output module. This enables the test signal in the circuit of the audible output module to be easily measured, for example, by a shunt resistor. Alternatively, the audible output can be measured indirectly by other means, such as using a microphone or an optical sensor, or by measuring the supply current of the audible output module.

[0102] This enables the state of the speaker or the audible output module to be accurately evaluated and potentially forms the aspect of monitoring the state of the entire user interface or patient monitor.

[0103] In some examples, the inaudible test signal may be added on top of the normal audio signal of the speaker or the audible output module. In this way, the normal audio signal is not affected and the environment is not disturbed by the inaudible test signal.

[0104] The measurement circuit can be adapted to measure the alternating current in the signal path of the audible output module. This enables the test signal in the circuit of the audible output module to be easily measured, for example, by the shunt resistor. Alternatively, the audible output can be measured indirectly by other means, for example, using a microphone or an optical sensor, or by measuring the supply current of the audible output module.

[0105] Those skilled in the art understand that when monitoring the state of the user interface or the patient monitor, other output modules can be monitored in a similar manner, for example, by monitoring the voltage drop of the output element (e.g., to detect whether this output element is short-circuited).

[0106] Both the user interface 100 and the patient monitor 150 are adapted to control one or more user-perceivable outputs (e.g., visual, auditory, or tactile outputs) in response to the independently determined state of the communication path and the independently determined state of themselves.

[0107] The user interface 100 uses the output module 102 to indicate its own state and the state of the communication path, for example, via a two-dimensional display screen 102A, an (optional) speaker 102B, and / or a dedicated light output 102D (forming any part of the output module 102).

[0108] Indicating the state of the communication path means, for example, providing no user-perceivable output (e.g., no audible output or no visual representation) when the communication path is stable enough to carry patient monitoring data, and providing a user-perceivable output (e.g., the presence of an audible output or a specific visual representation) when it is determined that the communication path is not stable enough to carry patient monitoring data.

[0109] In other words, at least one user-perceivable output is controlled according to the state of the communication path.

[0110] Similarly, indicating the state of the user interface 100 may involve not providing a perceptible output to the user if the user interface has completely failed (e.g., power has been lost), not detecting a malfunction, providing a first perceptible output to the user (e.g., no audible sound or green light), and / or providing a second user-perceptible output (e.g., audible sound or red light) if at least one malfunction is detected.

[0111] The user interface is adapted to operate in a "fail-safe" mode, in which a malfunction of the user interface is notified to those skilled in the art. For example, the user interface can be adapted to provide a perceptible output to the user when no malfunction is detected and not provide a perceptible output to the user when a malfunction is detected. Thus, a complete malfunction of the user interface (e.g., since no perceptible output is provided to the user) can be notified to the user.

[0112] Other ways of indicating the state and suitable modules for providing a perceptible output to the user will be apparent to those skilled in the art.

[0113] The patient monitor 150 can indicate the state of the communication path and the state of the patient monitor 150 in a similar manner using the secondary alarm module 153, which can provide one or more of visual output, audible output, or tactile output. Preferably, the secondary alarm module is or has a speaker to eliminate the need for the patient monitor 150 to have a screen. The secondary alarm module 153 is coupled to the processor 154 of the patient monitor and can have additional functionality of the general alarm module (configured to provide user-perceptible physiological alarms and / or technical alarms) of the patient monitor.

[0114] As an example, the secondary alarm module can have a speaker 153A for generating an audible alarm. In another example, the secondary alarm module 153 can have a dedicated visual output (e.g., a lamp) 153B for generating a visual alarm.

[0115] Indicating the state of the communication path means, for example, that when the communication path is stable enough to carry patient monitoring data, no user-perceivable output is provided (e.g., no audible output or no visual representation), and when it is determined that the communication path is not stable enough to carry patient monitoring data, a user-perceivable output (e.g., an audible output or the presence of a specific visual representation) is provided.

[0116] Similarly, indicating the state of the patient monitor 100 itself means that when the patient monitor has completely failed (e.g., power has been lost), no user-perceivable output is provided, when no malfunction is detected, a first user-perceivable output (e.g., no audible sound or green light) is provided, and / or when at least one malfunction is detected, a second user-perceivable output (e.g., an audible sound or red light) is provided.

[0117] The control of the user-perceivable output is performed by the respective processors of the user interface 100 and the patient monitor 150.

[0118] In an embodiment where the output module 102 further has a speaker 102B, the processor can be further adapted to control the speaker to provide an audio representation of the state of the communication path.

[0119] The visual output of the state of the communication path can, for example, provide no visual representation when the state of the communication path is acceptable, and provide a visual representation (e.g., light or a warning mark) when the state of the communication path is unacceptable.

[0120] As an example, the visual output of the state of the communication path has a visual representation of that state shown via a screen beside (above, below, left, or right) the visual representation of the patient monitoring data.

[0121] Merely as an example, the detection of an undesirable communication path can trigger the generation of a technical alarm (malfunction), which can operate as an interrupt. This technical alarm can then, if necessary, trigger the provision of user-perceivable outputs such as, for example, audible and visual alarms.

[0122] The user interface and the patient monitor can be adapted to check the state of the communication path one or more times per 0.1 - 3 seconds. In certain embodiments, the acceptable period between checks of the state of the communication path may be, for example, above the acceptable delay for generating a user-perceivable alarm in response to an undesirable state of the patient, according to clinically acceptable guidelines.

[0123] In other words, indicating the state of either the communication path or the user interface or the patient monitor can be in the form of an audible output signal, a visual output signal, or a tactile output signal, similar to indicating the state of the communication path.

[0124] In some embodiments, the patient monitor 150 is adapted to control or communicate with other modules such as, for example, a paging system or a communication system of a central controller, in response to a determined state of the communication path and / or the functions of the patient monitor itself. For example, the patient monitor can control a paging system (e.g., send a call (page) or signal to a user device if its communication path fails to function) in response to the determined state of the communication path, or can alert a central monitoring system in response to the determined state.

[0125] Monitoring of the communication paths independently performed by the user interface 100 and the patient monitor 150 effectively provides the "watchdog" communication path function to both elements.

[0126] Providing such a watchdog function for communication between the user interface and the patient monitor means that a stable and secure connection between these two devices can be established and guaranteed (any connection problems are warned to the user). This enables suppression of user-perceivable outputs (such as audible warnings) by the entity in the patient monitor or physically connected to this patient monitor (i.e., in the vicinity of the patient monitor).

[0127] Accordingly, in some embodiments, the patient monitor is adapted to suppress / mute / prevent audible output in response to the communication path being capable of carrying patient monitoring data to the connected user interface. Accordingly, if the user interface can provide information about data that induces audible output, audible alarms can be suppressed in the patient monitor.

[0128] In particular, the patient monitor is adapted to suppress / mute / prevent audible output in response to the communication path being capable of carrying patient monitoring data to the connected user interface, where the patient monitoring data includes alarm data.

[0129] Some clinical compliance guidelines involve the generation of audible alarms in response to alarm events (such as the patient's heart rate dropping below a predetermined value).

[0130] In such a scenario, the patient monitor can be adapted to suppress the audible output in response to the communication path being capable of carrying patient monitoring data (including alarm data) and the user interface having a speaker adapted to provide an audible output in response to the patient monitoring data. This enables the clinical compliance guidelines to be safely met while reducing the number of audible alarms output by the patient monitor.

[0131] Of course, the patient monitor 150 can be adapted to provide an audible output (in response to the alarm data) in response to the communication path being unable to carry patient monitoring data (including alarm data) or the user interface not having a speaker adapted to provide an audible output in response to the patient monitoring data. This enables the clinical compliance guidelines to be safely met and provides an appropriate backup option in the event that the communication path fails.

[0132] These advantages enable flexible use cases to be supported, such as ensuring that either the caregiver is able to be in a separate (observation) room while patient monitoring data is supplied to the caregiver, or that the caregiver is alerted in the event that patient monitoring data cannot be provided.

[0133] Similarly, the watchdog function can be provided to the patient monitor without the patient monitor having a screen or a physical connection to a screen for displaying a visual representation of the patient monitoring information. This is because the visual representation of the patient monitoring information is reliably provided by the user interface (such reliability being ensured or indicated by the watchdog function).

[0134] To improve safety and provide a fall-back, the secondary alarm module 153 of the patient monitor can have a dedicated visual output system 153C (e.g., a lamp bar) for providing information regarding the occurrence of an alarm.

[0135] To further improve safety, the secondary alarm module 153 is adapted to supply a user-perceivable output (e.g., an audible alarm) corresponding to the patient monitoring data when the patient monitor 150 determines that the state of the communication path 190 is such that it cannot convey the patient monitoring data to the user interface 100 (thereby performing the function of a general alarm module). This ensures an appropriate backup in case of a malfunction of the communication path (or the user interface).

[0136] The user interface and the patient monitor can each be adapted to monitor the state of other devices. Thus, the user interface can be adapted to monitor the state of the patient monitor, and the patient monitor can be adapted to monitor the state of the user interface.

[0137] Checking the state of other devices may be done according to any known method of monitoring the state of other devices, e.g., using a heartbeat protocol or by repeatedly requesting status information from other devices. In particular, since each of these devices is configured to monitor its own state, information regarding the state of that device is transmitted to other devices, thereby enabling other devices to monitor the state of the original device.

[0138] The user interface and the patient monitor may be further adapted to provide a user-perceivable output in response to the state of other devices being monitored. The user interface can use an output module to supply this output, and the patient monitor can use the secondary alarm module to supply this output. This improves the user's awareness of device malfunctions.

[0139] Of course, those skilled in the art understand that the user interface and / or patient monitor can be adapted to perform certain steps in response to a determination that other devices have failed. Such steps can be adapted from the exemplary steps described above that are performed in response to a determination that the communication path cannot carry patient monitoring data.

[0140] In one example, in response to a determination that the user interface has failed, the patient monitor is adapted to control user-perceivable output in response to patient monitoring data. This ensures that patient monitoring data warns the user even if the user interface fails.

[0141] Accordingly, in some examples, the patient monitor controls a secondary alarm module in response to patient monitoring data when it is determined that the communication path has failed (the communication path cannot successfully carry patient monitoring data) or the user interface has failed (e.g., cannot provide user-perceivable output in response to patient monitoring data). Of course, if neither the communication path nor the user interface is malfunctioning, the patient monitor can be adapted so that the secondary alarm module does not respond to patient monitoring data.

[0142] Other steps may be similar to the above-described steps that are performed in response to a determination that the communication path cannot successfully carry patient monitoring data to the user interface.

[0143] Preferably, the patient monitor is adapted to be able to communicate with more than one user interface, i.e., preferably, the patient monitor is not restricted to communicating with only a single user interface.

[0144] In some examples, the patient monitor is adapted to send the same or different information representing patient monitoring data to two or more user interfaces. Thus, two different user interfaces may display either a visual representation of the same patient monitoring data (e.g., substantially the same visual representation), or visual representations of different types of patient monitoring data (e.g., the first user interface displays heart rate information while the second user interface displays SpO2 information). Thus, each type of patient monitoring data reflects a part of the overall patient monitoring data.

[0145] In some examples, the patient monitor is adapted to selectively communicate with one or more of the selected user interfaces. This is done by establishing communication paths with two or more user interfaces, as is known in the art.

[0146] Establishing a communication path between the user interface and the patient monitor can be done according to any known "pairing" protocol, such as a wireless "pairing" protocol. Such protocols typically have the function of connecting two or more devices to a single "master" device (which may be the patient monitor here).

[0147] Thus, it is clear that the role / task of displaying the visual representation of patient monitoring data can be shared or exchanged between different user interfaces by changing, for example, which user interface has established a communication path with the patient monitor, which user interface 100 the patient monitor 150 is sending patient monitoring information to, and / or which patient monitoring information is associated with the information sent to different user interfaces.

[0148] A number of preferred examples are described below. A patient monitoring system (and thus, a patient monitor and / or user interface) is adapted to be able to perform any one or more of such examples.

[0149] In some examples, two or more user interfaces display a visual representation of the same patient monitoring data. In such examples, the patient monitor is adapted to send this same patient monitoring data to two or more user interfaces.

[0150] In some examples, the visual representation of patient monitoring data is split across multiple user interfaces (e.g., a first representation that displays a first portion of the visual representation and a second representation that displays a second portion of the visual representation, etc.). Of course, some user interfaces can provide a visual representation of the same portion as other portions of the patient monitoring data. Thus, the patient monitor can send different instances or portions of the patient monitoring data to different user interfaces.

[0151] These embodiments are particularly useful when different clinical practitioners are responsible for separate aspects of a patient's condition. For example, a first portion of the patient monitoring data can correlate to the patient's cardiovascular information (to be handled / inspected by a cardiovascular team looking at a first user interface), while a second portion of the patient monitoring data can correlate to the patient's respiratory information (to be handled / inspected by a respiratory team looking at a second user interface).

[0152] In yet another example, the visual representation of the alert thresholds associated with patient monitoring data and physiological data provided by a single patient monitor varies for each user interface. Thus, each user interface can adapt the visualization and the alerts perceptible to the user according to the skill set of the physician observing the corresponding user interface. This can optimally divide the alerts actionable among users based on the severity of the patient, i.e., when the patient's condition is deteriorating, the nurse receives the alert, while the physician is called immediately when the patient's condition becomes life-threatening to the patient.

[0153] In some examples, only a single user interface displays a (portion of the) visual representation of the patient monitoring data, where the selection of this single user interface is changed or passed between different user interfaces.

[0154] Thus, from the above, it is clear that the responsibility for displaying the visual representation of (a portion of) the patient monitoring data can be passed between different user interfaces.

[0155] Such a handover is preferably controlled such that the time period during which the user interface does not provide a visual representation of (a portion of) the patient monitoring data is less than a predetermined duration. The length of this predetermined duration is preferably greater than the acceptable time period between detecting the occurrence of an alert event and generating an output perceptible to the user (e.g., in accordance with clinical compliance guidelines). In some embodiments, the length of this duration is less than 3 seconds, for example, in the range of 0.1 second to 3 seconds or 0.1 second to 1 second.

[0156] In some examples, this is achieved by simply stopping communication with the first user interface (thereby stopping the first user interface from providing a suitable visual representation) when a communication path with a second different user interface is established (and, preferably, when transmission of patient monitoring data to the second user interface is initiated).

[0157] In another example, this is achieved by quickly switching communication (of the patient monitor) between the first user interface and the second user interface, for example, when the patient monitor is configured to be able to communicate with only a single user interface. Other methods will be apparent to those skilled in the art.

[0158] Of course, it is also understood that the user interface 100 can communicate with two or more patient monitors 150. Thus, the user interface can switch between displaying a visual representation of patient monitoring data generated by a first patient monitor and a visual representation of patient monitoring data generated by a second different patient monitor.

[0159] In some embodiments, such switching is performed only when the patient monitor 150 can communicate with another user interface (e.g., a second user interface), ensuring that a visual representation of patient monitoring data is continuously displayed.

[0160] In some embodiments, in response to indicating that the communication path is no longer functioning or otherwise unable to carry patient monitoring data (or that the connected user interface is no longer functioning), the patient monitor 150 can adapt to begin transmitting patient monitoring data to a different user interface via another communication path.

[0161] In this way, in response to communication with a non-functional (which would otherwise display such visual representations) user interface, the patient monitor can automatically cause a different user interface to display a visual representation of the patient monitoring data. This provides an alternative to ensure that the patient monitoring data continues to be provided to the clinician.

[0162] In any of the embodiments described above, it is clear that when a patient is not being monitored by the patient monitoring system, there is no need to provide a visual representation of the patient monitoring data. This can be controlled manually.

[0163] Figure 2 shows a scenario of a usage case of a patient monitoring system 200 according to an embodiment of the present invention.

[0164] The patient monitoring system 200 has a plurality of different patient monitors 150 and a plurality of different user interfaces 100. In this illustrated scenario, each patient monitor is adapted to communicate with a single user interface, and each patient monitor is associated with each bed 240.

[0165] The patient monitor 150 is positioned in a first room 205 (e.g., an intensive care unit). The user interface 100 is positioned in a second different room 206 (e.g., an observation room) to which a clinician 250 is assigned.

[0166] As described above, each patient monitor 150 communicates with its respective user interface 100. This enables patient monitoring data, such as for example alert data, to be sent from the room where the patient monitor is located to a separate room 206. This then enables the suppression (alternatively, this may be provided by the user interface instead) of alerts or other user-perceivable outputs at each patient monitor 150, resulting in a quieter first room 205. This can significantly reduce the stress of the patient in the first room 205 and / or the alert fatigue of the clinician, while ensuring that appropriate data is still provided to the clinician 250 (who is in the second room 206).

[0167] Accordingly, the proposed patient monitoring system enables the reduction of patient stress and alert fatigue by reliably transferring patient monitoring data to the user interface, while ensuring that the user is notified of any failure in the transfer of patient monitoring data.

[0168] Figure 3 shows a method 300 performed by a user interface having an output module with a two-dimensional display screen. The method 300 is for displaying patient monitoring data obtained by a patient monitor at the user interface.

[0169] The method 300 has a step 301 of receiving patient monitoring data from the patient monitor via a communication path.

[0170] The method 300 has a step 302 of controlling the two-dimensional display screen to provide a visual representation of the patient monitoring data based on the patient monitoring data.

[0171] The method 300 has a step 303 of monitoring the state of the communication path between the patient monitor and the user interface.

[0172] Method 300 has a step 304 of monitoring the state of the user interface.

[0173] Method 300 also has a step 305 of controlling the output module so as to provide a user-perceivable output indicating the state of the communication path.

[0174] Method 300 also has a step 306 of controlling the output module so as to provide a user-perceivable output indicating the state of the user interface.

[0175] Steps 301 and 302 may be grouped in one procedure thread. Steps 303 and 305 may be grouped in another procedure thread. Steps 304 and 306 may be grouped in yet another procedure thread. These three procedure threads may be executed continuously and / or in parallel with each other.

[0176] FIG. 4 shows a method 400 performed by a patient monitor having a secondary alarm module adapted to controllably generate a user-perceivable output according to an embodiment of the present invention. This method is for providing patient monitoring data to a display user interface using a patient monitor.

[0177] Method 400 has a step 401 of obtaining physiological data of a patient from one or more patient sensors.

[0178] Method 400 has a step 402 of generating patient monitoring data in response to the physiological data.

[0179] Method 400 has a step 403 of transmitting the patient monitoring data to a user interface via a communication path.

[0180] Method 400 has a step 404 of monitoring the state of the communication path.

[0181] Method 400 includes a step 405 of monitoring the state of the patient monitor.

[0182] Method 400 includes a step 406 of controlling an output perceptible to a user of the secondary alarm module in response to the state of the communication path.

[0183] Method 400 includes a step 407 of controlling an output perceptible to a user of the secondary alarm module in response to the state of the patient monitor.

[0184] Steps 401, 402, and 403 may be grouped in one procedure thread. Steps 404 and 406 may be grouped in another procedure thread. Steps 405 and 407 may be grouped in yet another procedure thread. These three procedure threads may be executed sequentially and / or in parallel with each other.

[0185] One skilled in the art can easily develop a processing system for implementing any method described herein. Accordingly, each step of the flowchart represents different operations performed by the processing system and can be performed by respective modules of the processing system.

[0186] Accordingly, embodiments can utilize a processing system. The processing system is implemented in various ways using software and / or hardware to perform the various required functions. A processor is an example of a processing system that uses one or more microprocessors programmed with software (e.g., microcode) to perform the required functions. However, the processing system can be implemented with or without using a processor and may be implemented as a combination of dedicated hardware for performing some functions and a processor (one or more programmed microprocessors and associated circuitry) for performing other functions.

[0187] Examples of components of a processing system used in various embodiments of the present disclosure include, but are not limited to, conventional microprocessors, application specific integrated circuits (ASICs), and field-programmable gate arrays (FPGAs).

[0188] In various implementations, the processor or processing system may be associated with one or more storage media of computer memory, such as volatile and non-volatile, such as RAM, PROM, EPROM, and EEPROM. The storage medium may be encoded with one or more programs that perform the required functions when executed on one or more processors and / or processing systems. The various storage media may be mounted within the processor or processing system, or may be transportable such that one or more programs stored on the storage medium are loaded into the processor or processing system.

[0189] It is understood that the disclosed method is preferably a method implemented by a computer. As such, the concept of a computer program having code means for implementing any of the described methods when the program is executed on a processing system, such as a computer, is also proposed. Accordingly, different portions, lines, or blocks of the code of a computer program according to one embodiment can be executed by a processing system or computer to perform any of the methods described herein. In some alternative implementations, the functions described in the block diagrams or flowcharts may be performed in an order different from the order described in the drawings. For example, two blocks shown in succession may actually be performed substantially simultaneously, or these blocks may be performed in the reverse order at times, depending on the functions involved.

[0190] Variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, upon consideration of the drawings, this disclosure, and the appended claims. In the claims, the term "comprising" does not exclude other elements or steps, and the fact that an element is plural does not exclude the possibility that there are a plurality of such elements, even if not stated. A single processor or other unit may perform the functions of several items recited in the claims. The mere fact that certain methods are recited in mutually different dependent claims does not indicate that combinations of these methods cannot be used advantageously. Where a computer program is described, it may be stored / distributed on a suitable medium, such as an optical storage medium or a solid state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunication systems. When the term "adapted to" is used in the claims or the specification, this term "adapted to" is meant to be equivalent to the term "configured to". Any reference signs in the claims should not be construed as limiting their scope.

Claims

1. In a patient monitor for generating patient monitoring data visually presented by a two-dimensional display screen of a user interface, the patient monitor is configured to transmit patient monitoring data via a communication path between the patient monitor and the user interface, and monitor the state of the communication path between the patient monitor and a communication module of the user interface, a communication system adapted as such, an input module adapted to obtain physiological data of a patient from one or more physiological / patient sensors, a secondary alarm module adapted to provide an output perceptible to a user, monitor the state of the patient monitor, obtain the physiological data, generate patient monitoring data in response to the physiological data, control the output perceptible to the user of the secondary alarm module in response to the state of the communication path, and control the output perceptible to the user of the secondary alarm module in response to the state of the patient monitor a processor of the patient monitor adapted as such, and an audible output module included in the secondary alarm module and controlled by the processor of the patient monitor wherein the processor of the patient monitor is configured to determine whether the user interface has an audible output module separate from the audible output module included in the secondary alarm module, and in response to the state of the communication path indicating that the communication path can successfully carry the patient monitoring data and that the user interface has an audible output module separate from the audible output module included in the secondary alarm module, prevent the audible output module included in the secondary alarm module from generating any audible output in response to alarm data a patient monitor adapted as such.

2. The processor of the patient monitor is configured to monitor the state of the user interface, and control the secondary alarm module in response to the state of the user interface The patient monitor according to claim 1, further adapted as such.

3. In response to the communication path being indicated as non-functional or otherwise unable to successfully convey the patient monitoring data, the processor of the patient monitor is adapted to use the audible output module to generate an audible output in response to the alarm data. The patient monitor according to claim 1 or 2.

4. The patient monitor is configured not to have any two-dimensional display screen for providing a visual representation of the patient monitoring data and / or not to be able to communicate with a device having a two-dimensional display screen via a wired communication path. The patient monitor according to any one of claims 1 to 3.

5. In a patient monitoring system having a patient monitor according to any one of claims 1 to 4 and a user interface for providing a visual representation of patient monitoring data obtained by the patient monitor, the user interface receives patient monitoring data from the patient monitor via a communication path between the patient monitor and the user interface, and monitors the state of the communication path a communication module adapted to an output module for providing user-perceivable output, the output module being couplable to a two-dimensional display screen for generating a visual output monitors the state of the user interface, obtains the patient monitoring data from the communication module, controls the two-dimensional display screen to provide a visual representation of the patient monitoring data based on the patient monitoring data, controls the output module to provide a user-perceivable output indicating the state of the communication path, and controls the output module to provide a user-perceivable output indicating the state of the user interface a processor of the user interface adapted to A patient monitoring system having

6. In a method of providing patient monitoring data to a user interface for display using a patient monitor having a secondary alarm module adapted to controllably generate user-perceivable output and an audible output module included in the secondary alarm module, the method comprises: obtaining physiological data of a patient from one or more patient sensors; generating patient monitoring data in response to the physiological data; transmitting the patient monitoring data to a user interface via a communication path; monitoring the state of the communication path; monitoring the state of the patient monitor; controlling a user-perceivable output of the secondary alert module in response to the state of the communication path; controlling a user-perceivable output of the secondary alert module in response to the state of the patient monitor; determining whether the user interface has an audible output module separate from an audible output module included in the secondary alert module; and preventing the audible output module included in the secondary alert module from generating any audible output in response to alert data in response to the state of the communication path indicating that the communication path can successfully carry the patient monitoring data and that the user interface has an audible output module separate from an audible output module included in the secondary alert module A method having the above steps.

Images