Providing visual representations of patient monitoring data

Abstract

A patient monitor and a separate user interface for the patient monitor, adapted to communicate with each other over a communication path. Both the patient monitor and the separate user interface are able to independently check the status of the communication path and visually indicate that status.

Description

Technical Field

[0001] This invention relates to the field of patient monitoring, and more particularly to the processing of patient monitoring data. Background Technology

[0002] In clinical settings, such as intensive care units or neonatal intensive care units, patient monitors are routinely used to monitor the physiological data of subjects or patients. Patient monitors can be adapted to generate patient monitoring data, which may include physiological data and / or data derived therefrom.

[0003] A slightly more common approach is for patient monitors to generate alarm data that indicates whether an alarm event (a physiological or technical event critical to the patient's safety) has occurred. An alarm event is an indication that the patient or the patient monitor has entered an undesirable state. For example, an alarm event associated with a physiological characteristic might indicate a low heart rate or SpO2 level, while a technical alarm event might indicate a low battery level or malfunction in the patient monitor.

[0004] Typically, the visual representation of patient monitoring data (and particularly 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 wires or other electrical connections, such as via a video graphics array (VGA) cable. In practice, this method of providing visual representation using a direct wired connection has generally been considered necessary to ensure that the patient monitor meets clinical compliance requirements (e.g., providing notification of alarm events or providing sufficiently up-to-date information about the patient's physiological parameters within a clinically acceptable timeframe).

[0005] It is also known to provide or utilize additional user interfaces, such as tablets or mobile phones, that receive updates from the patient monitor via wired or wireless channels. These user interfaces supplement the two-dimensional screen of the patient monitoring device by mirroring the visual representation and / or providing additional information about the patient monitoring data. Typically, these user interfaces operate by having the patient monitor push updates to the user interface.

[0006] There is a continued expectation to increase the flexibility and availability of patient monitoring systems. There is also an expectation to reduce the number of alerts or warnings provided to care providers / clinicians. Summary of the Invention

[0007] This invention is defined by the claims.

[0008] According to an aspect of the invention, a patient monitor is provided for generating patient monitoring data to be 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; monitor the state of the communication path between the patient monitor and a communication module of the user interface; and an input module adapted to acquire physiological data of a patient from one or more patient sensors; an auxiliary alarm module adapted to provide a user-perceptible output; a patient monitor processor adapted to: monitor the state of the patient monitor; acquire the physiological data and generate patient monitoring data in response to the physiological data; control the user-perceptible output of the auxiliary alarm module in response to the state of the communication path; and control the user-perceptible output of the auxiliary alarm module in response to the state of the patient monitor; and an audible output module controlled by the patient monitor processor, wherein the patient monitor processor is adapted to indicate, in response to the state of the communication path, that the communication path can successfully carry the patient monitoring data and that the user interface includes the audible output module, and to prevent at least one audible output module from generating any audible output in response to alarm data.

[0010] According to the proposed embodiment, a patient monitor is provided that is adapted to suppress / mute / block audible output in response to a communication path capable of carrying patient monitoring data to a connected user interface having an audible output module. Therefore, if the user interface can provide audible output (otherwise provided by the patient monitor), audible alarms can be suppressed at the patient monitor.

[0011] Specifically, the patient monitor may be adapted to suppress / mute / block audible output in response to the communication path being able to carry the patient monitoring data to a connected user interface that can provide audible output, wherein the patient monitoring data includes alarm data.

[0012] Some clinical adherence guidelines require generating audible alarms in response to alarm events (e.g., a patient's heart rate dropping below a predetermined value). In such cases, the patient monitor can be adapted to suppress audible output in response to a communication path capable of carrying patient monitoring data (including alarm data) and a user interface including a speaker adapted to provide audible output in response to the patient monitoring data. This allows clinical adherence guidelines to be safely met while reducing the number of audible alarms output by the patient monitor. Reducing the number of audible alarms output by the patient monitor can, for example, reduce the stress or anxiety experienced by the patient (and / or nearby patients).

[0013] When a stable connection to the user interface is established, audible alarms can be suppressed, blocked, or stopped by the patient monitor. This provides a quieter environment near the patient (because the user interface can be placed remotely), reducing stress on both the patient and clinician, and reducing alarm fatigue for clinicians working near the patient. This allows for greater flexibility in configuring the patient monitoring system.

[0014] The proposed patient monitor also enables reliable communication with the user interface while notifying clinicians of any changes in the communication status. This notification allows clinicians to manually care for patients (i.e., to prevent patients from entering undesirable clinical states without being noticed by the patient monitor).

[0015] By checking the status of the communication path / channel, a secure and stable connection to the user interface can be ensured. Therefore, the patient monitor itself does not need to include a screen for providing visual representations of patient monitoring data to clinicians. This capability allows for more affordable patient monitors and centralized visual representations of different patients.

[0016] Therefore, the proposed patient monitor achieves a more flexible system while avoiding the need for the patient monitor to have its own screen for displaying patient monitoring data. Thus, the patient monitor can be "headless".

[0017] Monitoring the status of a patient monitor ensures that the monitor itself is reliable. Monitoring the status of a patient monitor may include using one or more watchdogs or watchdog timers to iteratively check or monitor whether the patient monitor has encountered an error or entered an unexpected state. In particular, the patient monitor may be adapted to guarantee to the user, or otherwise indicate the status of the patient monitor, thereby providing a “reliable patient monitor.”

[0018] The patient monitor processor may also be adapted to: monitor the status of the user interface; and control the auxiliary alarm module in response to the status of the user interface.

[0019] Specifically, the patient monitor can be adapted to control an auxiliary alarm module in response to patient monitoring data in response to determining that the user interface has failed (as indicated in the status). This ensures that patient monitoring data continues to be provided or output even if the user interface itself fails.

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

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

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

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

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

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

[0026] Therefore, in the event of a failure in the communication path or user interface, the new user interface can be paired or coupled with the patient monitor to enable a visual representation of the patient monitoring data.

[0027] Of course, the implementation allows more than one user interface to view (the same or different) patient monitoring data associated with the same patient, providing a more flexible working environment.

[0028] The communication system may be adapted to initiate the transmission of patient monitoring data to a different user interface in response to a status indication that the communication path has failed or is otherwise unable to carry the patient monitoring data. This may include establishing a new communication path using a different user interface, methods of which are known in the art.

[0029] Based on 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 the patient's physiological parameters.

[0030] The user interface includes: a communication module adapted to: receive patient monitoring data from the patient monitor via a communication path between the patient monitor and the user interface; and monitor the status of the communication path; an output module for providing user-perceptible output, the output module being coupled to a two-dimensional display screen to generate visual output; and a user interface processor adapted to: monitor the status of the user interface and the display screen; obtain the patient monitoring data from the communication module; control the two-dimensional display screen based on the patient monitoring data to provide a visual representation of the patient monitoring data; control the output module to provide user-perceptible output indicating the status of the communication path; and control the output module to provide user-perceptible output indicating the user's status.

[0031] The proposed user interface enables a more flexible patient monitoring system. In particular, it can provide a visual representation of patient monitoring data and deliver user-perceptible alarms remotely and reliably, thereby eliminating the need to provide a visual representation at the patient monitor itself.

[0032] Typically, for clinical compliance purposes, it is necessary to ensure that the visual representation of patient monitoring data and the delivery of any alarms triggered by physiological or technical events are reliable, and that the patient monitoring information is up-to-date with available acquisition. The proposed user interface enables the reliable communication from the patient monitor, thus meeting 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 user interface processor is also adapted to monitor the state of the patient monitor and control the output module to provide a user-perceptible output indicating the state of the patient monitor. This can be done by monitoring, for example, a heartbeat signal generated by the patient monitor.

[0034] In some embodiments, the process of monitoring the state of the user interface, performed by the user interface processor, includes using one or more watchdog timers to repeatedly check whether the user interface has encountered an error.

[0035] Monitoring the state of the user interface ensures that the user interface itself is reliable. Monitoring the state of the user interface may include using one or more watchdogs or watchdog timers to iteratively / repeatedly check or monitor whether the user interface has encountered an error or entered an unexpected state. In particular, the user interface may be adapted to guarantee the supply of or otherwise indicate the state of the user interface to the user, thereby providing a "reliable user interface." Patient monitoring data may include alarm data indicating the presence or absence of an alarm event that indicates a patient or patient monitor has entered an undesirable state.

[0036] The output module may include a speaker for generating audio output, and the processor may also be adapted to control the audio representation of patient monitoring data provided by the speaker (e.g., when an alarm related to a physiological event is triggered) and / or the state of the communication path.

[0037] Audio output of patient monitoring data (alarm data) can meet the requirements of some clinical compliance guidelines. By providing audio output at the (remote) user interface, audio output at the patient's location (at the patient monitor) can be muted, suppressed, or otherwise stopped. This achieves a quieter environment near the patient, reduces patient stress, reduces clinician distraction, and (where patient monitoring data includes alarm data) reduces alarm fatigue for clinicians near the patient.

[0038] The communication module can be adapted to monitor the status of the communication path by iteratively checking the presence of the bio-oriented link provided by the communication path, wherein the duration between iterative checks is not less than 3 seconds.

[0039] Performing such iterative checks can increase the overall patient monitoring system's adherence to clinical guidelines. In particular, such periodic checks ensure that patient monitoring data is updated at sufficient intervals for clinician monitoring purposes, or that clinicians are alerted to communication errors (e.g., so they can then manually check the patient's status). This reduces the likelihood that patients will progress to clinically undesirable conditions over extended periods without the clinician's (observation of the user interface) awareness.

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

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

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

[0043] Both the user interface and the patient monitor check their own condition and the state of the communication path to ensure that end-to-end reliability checks are performed. This means that the entire patient monitoring system is reliable by ensuring that any errors in presenting patient monitoring data to the user are alerted (e.g., during the generation of patient monitor data at the patient monitor, during the transmission of that data to the user interface, or during the display of patient monitoring data). This reduces the chance of patients entering clinically undesirable states or medical equipment malfunctions without the user's notice, for example, because if the patient monitoring system has malfunctioned, the user can be prompted to manually check the patient monitor.

[0044] According to an example of another aspect of the invention, a method is provided for providing patient monitoring data to a user interface for display using a patient monitor, the patient monitor including an auxiliary alarm module adapted to controllably generate user-perceptible output.

[0045] The method includes: acquiring 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 the user-perceptible output of an auxiliary alarm module in response to the state of the communication path; controlling the user-perceptible output of the auxiliary alarm module in response to the state of the patient monitor; determining whether the user interface includes an audible output module; and preventing the audible output module of the patient monitor from generating any audible output in response to the alarm data in response to the communication path state indicating that the communication path can successfully carry the patient monitoring data and that the user interface includes an audible output module.

[0046] A method is also provided for displaying patient monitoring data obtained by a patient monitor at a user interface that can be coupled to a two-dimensional screen. The method includes: receiving patient monitoring data from the patient monitor via a communication path; controlling the two-dimensional display screen based on the patient monitoring data to provide a visual representation of the patient monitoring data; monitoring the state of the communication path between the patient monitor and the user interface; monitoring the state of the user interface and the two-dimensional display screen; controlling the output module to provide a user-perceptible output indicating the state of the communication path; and controlling the output module to provide a user-perceptible output indicating the state of the user interface.

[0047] According to an example of another aspect of the invention, a computer program is provided, comprising code modules for any of the methods described herein when the program is run on a processing system.

[0048] These and other aspects of the invention will become apparent from the embodiments described below and will be set forth with reference to the embodiments described below. Attached Figure Description

[0049] To better understand the invention and to more clearly illustrate how it can be implemented, reference will now be made to the accompanying drawings by way of example only, wherein:

[0050] Figure 1 The illustration shows a patient monitoring system including a patient monitor and a user interface according to an embodiment of the present invention;

[0051] Figure 2 The diagram illustrates a use case scenario for a patient monitoring system;

[0052] Figure 3 The diagram illustrates a method for displaying patient monitoring data obtained by a patient monitor at a user interface; and

[0053] Figure 4 Another method according to an embodiment is illustrated. Detailed Implementation

[0054] The invention will be described with reference to the accompanying drawings.

[0055] It should be understood that the detailed descriptions and specific examples, when indicating exemplary embodiments of the apparatus, systems, and methods, are intended for illustrative purposes only and are not intended to limit the scope of the invention. These and other features, aspects, and advantages of the apparatus, systems, and methods 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 not drawn to scale. It should also be understood that the same reference numerals are used throughout the drawings to indicate the same or similar parts.

[0056] This invention provides a novel and flexible concept for patient monitoring systems that eliminates the need for displays and / or alarm systems near the patient. The concept is realized using two interconnected products: a patient monitor and one or more separate user interfaces for the patient monitor. The patient monitor and the separate user interfaces are adapted to communicate with each other via a communication path. Both the patient monitor and the separate user interfaces are capable of independently checking their own status and the status of the communication path, and visually indicating the results of the status checks. This helps ensure not only a reliable connection exists between the patient monitor and the user interface, but also up-to-date information about the "health" of each device, helping to ensure compliance with clinical adherence guidelines.

[0057] The embodiments can be used in clinical settings where (automated) patient monitoring occurs, such as in wards or intensive care units.

[0058] Figure 1 The illustration shows a patient monitoring system 1 according to an embodiment of the present invention. The patient monitoring system includes a user interface 100 and a patient monitor 150.

[0059] User interface 100 represents one embodiment of the inventive concept, patient monitor 150 represents another embodiment of the inventive concept, and patient monitoring system 1 represents yet another embodiment of the inventive concept.

[0060] User interface 100 includes a communication module 101 and an output module 102. The output module 102 includes 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.

[0061] Although the output module is illustrated as having a display screen 102A as an integrated part of the module, those skilled in the art will understand that the user interface 100, including the output module 101, may be a separate unit and coupled to an external display screen.

[0062] User interface 100 can be any device capable of communicating and displaying patient monitoring data on a two-dimensional display screen, such as mobile phones, tablets, laptops, computers, smartwatches, smart glasses, etc.

[0063] The patient monitor 150 includes a communication system 151, an input module 152, an auxiliary alarm module 153, and a patient monitor processor 154. The patient monitor 150 is adapted to monitor one or more physiological characteristics of a patient and generate patient monitoring data for visual representation by a user interface.

[0064] The operation of the user interface 100 and the patient monitor is controlled by the user interface processor 103 and the patient monitor processor 154, respectively, as will be known to a technician.

[0065] User interface 100 and patient monitor 150 communicate with each other at least by transmitting patient monitoring data from patient monitor 150 to user interface 100. Specifically, communication module 101 of user interface 100 is adapted to receive communications / signals (including patient monitoring data) from patient monitor 150, and communication system 151 of patient monitor 150 is adapted to transmit communications (including patient monitoring data) to user interface 100.

[0066] Preferably, the communication between the user interface 100 and the patient monitor 150 is bidirectional, meaning the user interface can provide input to the patient monitor and vice versa. For example, at the user's choice, the user interface 100 can be adapted to control the visual representation of the acquired physiological data in the form of waveforms. Depending on the user's expertise (doctor or nurse), presenting physiological waveforms on the display screen in different orders or arrangements may be beneficial. Furthermore, the user interface can allow the user to change the threshold that triggers physiological alarms on the patient side.

[0067] Preferably, for improved flexibility, the communication path is a wireless communication path. Therefore, the user interface 100 and the patient monitor 150 can communicate wirelessly with each other, at least by the patient monitor 150 wirelessly transmitting patient monitoring data to the user interface 100.

[0068] Generally, communication paths can be potentially unreliable, for example, relying on components outside the control of the user interface and / or the provider / operator of the patient monitor.

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

[0070] In such embodiments, any suitable wireless communication protocol or technology can be used. Suitable wireless communication protocols for communication between the patient monitor and the user interface include infrared links, ZigBee, Bluetooth, wireless LAN protocols such as those according to the IEEE 802.11 standard, 2G, 3G, or 4G telecommunications protocols, etc. Other formats will be readily apparent to those skilled in the art.

[0071] Communication along the communication path between the patient monitor and the user interface can be encoded or formatted using Medical Device Data Language (MDDL) or by establishing a Transmission Control Protocol (TCP) link between the patient monitor and the user interface. Other suitable methods for encoding or formatting data will be readily apparent to the technician.

[0072] Preferably, the communication path provides a direct communication link between the patient monitor and the user interface, such as using Near Field Communication (NFC), Bluetooth, or the ZigBee protocol. In other embodiments, the communication path is a personal or local area network, such as those that can be established using WiFi technology (but excluding wide area networks). In yet another embodiment, the communication path includes a wide area network, such as the Internet.

[0073] Communication from the patient monitor to the user interface includes patient monitoring data generated by the patient monitor (examples of which will be given later). Therefore, such communication enables the patient monitor to efficiently stream patient monitoring data to the user interface.

[0074] User interface 100 (user interface processor 103) acquires patient monitoring data and controls screen 102A to display a visual representation of the patient monitoring data (e.g., in waveform and numerical form). Figure 1 The diagram illustrates an example of a suitable visual representation.

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

[0076] Patient monitoring data responds at least to the patient's physiological data, but may also respond to other parameters or variables. For example, patient monitoring data may respond to the state of the patient monitor or physiological / patient sensors communicating with the patient monitor.

[0077] Methods for generating patient monitoring data will be well known to those skilled in the art. Typically, such methods involve receiving one or more physiological data streams / signals at an input module 152 from a patient sensor (not shown) (such as a heart rate monitor, pulse oximeter, etc.). The patient monitor 150 (of which the processor 154) is adapted to receive such information and generate patient monitoring data for display (e.g., in waveform form).

[0078] In some embodiments, the patient monitor 150 itself may include one or more patient sensors (not shown) for directly obtaining physiological data of the patient, such as one or more of the following: a camera, a heart rate monitor, a respiratory rate monitor, a pulse oximeter, a blood pressure monitor, etc.

[0079] Patient monitoring data may include, for example, the patient's physiological information (e.g., heart rate, respiratory rate, SpO2 level, temperature, urine output, etc.). Physiological information may include, for example, information about any vital signs of the patient, any other signs / symptoms of the patient, or any other measurable quantity of the patient or the treatment device provided to the patient (such as the amount remaining in an intravenous infusion or the current battery level of a pacemaker).

[0080] In addition to data responding to the patient's physiological information, patient monitoring data may also include data responding to the status of the patient monitor and / or any patient sensors communicating with the patient monitor. For example, patient monitoring data may include an indication of whether an electrode (e.g., for monitoring heart rate) is electrically connected to the patient. Therefore, the data transmitted to user interface 100 may include the patient's medical data (physiological data acquired by at least one sensor), technical data related to the function of the patient monitor or various units coupled thereto; and the results of status checks on the patient monitor and communication paths.

[0081] Preferably, the patient monitoring data includes alarm data indicating the occurrence or presence of alarm events.

[0082] As previously explained, an alarm event is an indication that a patient or patient monitor has entered an undesirable state. For example, an alarm event could indicate a low heart rate or SpO2 level, low battery level, a disconnected lead, or a malfunction of the patient monitor. Specifically, an alarm event occurs if the measured level of a physiological parameter crosses a predetermined threshold (e.g., above a maximum threshold or below a minimum threshold).

[0083] Clearly, the method for generating alarm data will be readily apparent to technicians, for example, by comparing the values ​​of the obtained physiological data with one or more thresholds or by receiving interruptions from components of the patient monitor.

[0084] In such examples, when an alarm event is detected in or transmitted along with received patient monitoring data, the user interface 100 may display a visual representation of the warning (e.g., a red light or warning symbol, such as an exclamation mark) on screen 102A. In embodiments where the user interface includes a speaker 102B for generating audio output, the processor may control the speaker to generate an audio warning in response to an alarm event (e.g., a rapid or continuous beeping sound in the event of an alarm event, or silence in the absence of an alarm event). In some examples, the output module 102 may also include a dedicated alarm light output 102C that can visually indicate the occurrence of an alarm event (i.e., separate from screen 102A) to aid in the distinguishable identification of the alarm event.

[0085] Patient monitoring data is formatted to be suitable for processing by a user interface processor, enabling the provision of a visual representation of the patient monitoring data.

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

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

[0088] In this way, the patient monitor 150 defines a visual representation displayed on the screen of the user interface, such that the visual representation provides information about the patient monitoring data.

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

[0090] Specifically, they can be adapted to independently determine whether the communication path has failed and / or whether the communication path is unable to successfully carry / stream patient monitoring data from the patient monitor. In other words, they both determine whether the communication path is stable enough to carry patient monitoring data. Failure to carry this information could be due to, for example, user interface 100 being out of range, user interface failure (e.g., battery depletion), or the communication path having saturated bandwidth, such as excessive traffic / noise (e.g., transmissions from other patient monitors in the same frequency band).

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

[0092] User interface 100 uses a communication module to monitor the status of communication path 190. Patient monitor 150 uses a communication system to monitor the status of communication path 190.

[0093] Methods for monitoring the status of communication paths will be known to technicians and will depend on the type, structure, format, or protocol of the communication path.

[0094] With a simple example, the state of a communication path can be checked by initiating a handshake protocol or "inspecting" another device in the communication path. The response from the other device can be examined (e.g., hysteresis in the communication path can be checked) and used to determine the state of the communication path.

[0095] In another example, a communication protocol may include transmitting (a specific amount) of information at periodic intervals. The state of the communication can be checked by determining whether information has been received within the periodic intervals, where lost communication indicates a deterioration of the communication path, i.e., a change in state.

[0096] In another example, the communication protocol may include timestamping of communications (e.g., from a patient monitor to a user interface, or vice versa). The state of the communication path can be checked by determining whether timestamped communications have been received within a predetermined time period (since the timestamp), which may be the expected length of time for the communications to occur. Failure to receive communications within the predetermined time period can indicate a deterioration in the communication path, i.e., a change in state.

[0097] Both the user interface 100 and the patient monitor 150 are adapted to monitor their own state. Thus, the user interface 100 monitors the state of itself and the display screen to which it is coupled, and the patient monitor monitors the state of the patient monitor 150. Therefore, the user interface 100 and the patient monitor 150 (and its processor) are also adapted to independently monitor their own functions (e.g., checking battery levels, software errors, output module status, etc.).

[0098] In some examples, the patient monitor 150 may be adapted to check for any errors in the generation and transmission of patient monitor data, i.e., whether the patient monitoring data is reliably generated and transmitted. Similarly, the user interface 100 may be adapted to check for any errors in the reception and display of patient monitoring data at the screen (e.g., from receiving patient monitoring data to displaying patient monitoring data).

[0099] The advantage of this solution is that it enables any display screen with user interface functionality. Typically, patient monitor displays need to meet stringent medical requirements, where their visualization capabilities (contrast, active pixels, etc.) need to operate 24 / 7 for months (if not years). This requirement drives the emphasis on patient monitoring systems. This invention advantageously provides an alternative solution that allows, rather than imposes stringent requirements on the display screen, in which physiological data is monitored to provide a self-checking status function to the user interface. This self-checking status function also includes monitoring the display's visual performance, which notifies the user if the display quality deteriorates below a medically imposed threshold.

[0100] Methods for monitoring the state of electronic devices (such as user interfaces and patient monitors) (i.e., detecting the occurrence of errors within electronic devices (such as user interfaces and patient monitors)) are well known to those skilled in the art.

[0101] This invention allows any device with a display screen and a speaker to become an active device for patient alarm management, provided that the user interface ensures the reliable functioning of the individual units to which it is coupled (such as the display screen and / or speaker).

[0102] In specific examples, software and / or hardware watchdogs (such as watchdog timers) can be used to monitor the state of electronic devices. Watchdog operation ensures that an indication of the state can be provided. Specifically, the presence or absence of errors can be detected. Thus, the watchdog ensures the reliability of the electronic device. In particular, the watchdog can operate in a "fail-safe" mode, allowing the operator of the device to notice any malfunctions in the system or electronic device.

[0103] Some methods for monitoring the status of electronic devices can include monitoring the status of output modules (e.g., speakers or audible output modules). A fault in an output module can indicate a fault in the electronic device.

[0104] By way of example only, a status monitoring method may include controlling a speaker or audible output module to provide an inaudible test signal, such that measuring circuitry can obtain the amplitude of the signal at the frequency of the test signal. This amplitude can be used to obtain information about the function / status of the speaker or audible output module and its electrical connections to a host device (i.e., a user interface or patient monitor).

[0105] Specifically, the measurement circuit can be adapted to measure the alternating current in the signal path of the audible output module. This allows for easy measurement of the test signal in the circuitry of the audible output module, for example, via a shunt resistor. Alternatively, the audible output can be measured either by other modules (e.g., using a microphone or optical sensor) or indirectly by measuring the supply current of the audible output module.

[0106] This allows the status of the speaker or audible output module to be accurately assessed, potentially forming an aspect of monitoring the status of the entire user interface or patient monitor.

[0107] In some examples, an inaudible test signal can be added on top of the normal audio signal from a speaker or audible output module. In this way, the normal audio signal remains unaffected, and the environment is not disturbed by the inaudible test signal.

[0108] The measurement circuitry can be adapted to measure the alternating current in the signal path of the audible output module. This allows for easy measurement of test signals in the circuitry of the audible output module, for example, via a shunt resistor. Alternatively, the audible output can be measured either by other modules (e.g., using a microphone or optical sensor) or indirectly by measuring the supply current of the audible output module.

[0109] Technicians will realize that when monitoring the status of the user interface or patient monitor, other output modules can be monitored in a similar way. For example, by monitoring the voltage drop across the output element (e.g., to detect if the output element is short-circuited).

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

[0111] User interface 100 uses output module 102 to indicate the status of itself and the communication path, for example via two-dimensional display 102A, (optional) speaker 102B and / or dedicated light output 102D (which forms an optional part of output module 102).

[0112] The state of the communication path can include, for example, providing no user-perceptible output (e.g., no audible output or no visual representation) if the communication path is determined to be unstable enough to carry patient monitoring data; and providing user-perceptible output (e.g., audible output or the presence of a visual representation) if the communication path is determined to be unstable enough to carry patient monitoring data.

[0113] In other words, at least one user-perceptible output is controlled in response to the state of the communication path.

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

[0115] The user interface can be adapted to operate in a "fail-safe" mode, where technicians are notified of any failures in the user interface. For example, the user interface can be adapted to provide user-aware output if no error is detected, and not provide user-aware output if an error is detected. Therefore, the user can be notified of a complete failure of the user interface (e.g., because no user-aware output will be provided).

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

[0117] The patient monitor 150 uses an auxiliary alarm module 153 in a similar manner to indicate the status of the communication path and the status of the patient monitor 150. The auxiliary alarm module 153 can provide one or more of visual, auditory, or tactile outputs. Preferably, the auxiliary alarm module is or includes a speaker to avoid the need for a screen on the patient monitor 150. The auxiliary alarm module 153 can be coupled to the patient monitor processor 154 and has additional functionality as a general alarm module of the patient monitor (arranged to provide user-perceived physiological and / or technical alarms).

[0118] By way of example, the auxiliary alarm module may include a speaker 153A for generating audible warnings. In another example, the auxiliary alarm module 153 may include a dedicated visible output (e.g., a light) 153B for generating visual warnings.

[0119] The state of the communication path can include, for example, providing no user-perceptible output (e.g., no audible output or no visual representation) if the communication path is determined to be unstable enough to carry patient monitoring data; and providing user-perceptible output (e.g., the presence of audible output or a visual representation) if the communication path is determined to be unstable enough to carry patient monitoring data.

[0120] Similarly, indicating the state of the patient monitor 100 itself may include not providing user-perceptible output if the patient monitor has completely failed (e.g., power failure), providing a first user-perceptible output (e.g., green light or no audible sound) if no error is detected, and / or providing a second user-perceptible output (e.g., red light or audible sound) if at least one error is detected.

[0121] Control of one or more user-perceptible outputs is performed by the corresponding processors of the user interface 100 and the patient monitor 150.

[0122] In embodiments where the output module 102 also includes a speaker 102B, the processor may also be adapted to control the speaker to provide an audio representation of the state of the communication path.

[0123] For example, if the state of the path is acceptable, the visual output of the state of the communication path may not provide a visual representation, and if the state of the path is unacceptable, the visual output of the state of the communication path may provide a visual representation (e.g., light or warning symbol).

[0124] By way of example, the visual output of the status of the communication path may include presenting a visual representation of the status via a screen at the (top, bottom, left, or right) side of the visual representation of the patient monitoring data.

[0125] By way of example only, the detection of an unwanted communication path can trigger the generation of a technical alert (Inop), which can then be used as an interrupt. This technical alert can then trigger the provision of user-perceptible outputs (e.g., auditory alarms, visual alarms, etc., depending on the situation).

[0126] The user interface and patient monitor may be adapted to check the status of the communication path at least once every 0.1 to 3 seconds. In a particular embodiment, the permissible duration between checks of the status of the communication path may be no less than the permissible delay for generating a user-aware alarm in response to an undesirable patient condition (e.g., according to clinically acceptable guidelines).

[0127] In other words, in a manner similar to indicating the state of the communication path, the state of the user interface or patient monitor can take the form of audible, visual, or tactile output signals.

[0128] In some embodiments, the patient monitor 150 is adapted to control or contact other modules, such as a paging system or a central controller communication system, in response to the state of a determined communication path and / or its own functionality. For example, the patient monitor may control the paging system (e.g., send a paging or signal to the user equipment if the path fails) in response to a determined state of the path, or alert the central monitoring system in response to a determined state.

[0129] The monitoring of the communication path, performed independently by the user interface 100 and the patient monitor 150, effectively provides a "watchdog" communication path function to both components.

[0130] Providing such a watchdog function to the communication between the user interface and the patient monitor means that a stable and secure connection can be established and ensured between the two devices (whereby the user is alerted to any errors in the connection). This enables the suppression of user-perceptible output at the patient monitor (e.g., audio warnings) or user-perceptible output from entities physically connected to the patient monitor (i.e., in its vicinity).

[0131] Therefore, in some embodiments, the patient monitor is adapted to suppress / mute / block audible output in response to the communication path being able to carry patient monitoring data to a connected user interface. Thus, if the user interface can provide information about data that will trigger audible output, audible alarms can be suppressed at the patient monitor.

[0132] Specifically, the patient monitor may be adapted to suppress / mute / block audible output in response to a communication path capable of carrying patient monitoring data to a connected user interface, wherein the patient monitoring data includes alarm data.

[0133] Some clinical compliance guidelines require the generation of audible alarms in response to alarm events (e.g., a patient's heart rate drops below a predetermined value).

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

[0135] Of course, the patient monitor 150 may be adapted to provide audible output (in response to alarm data) in response to a communication path that cannot carry patient monitoring data (including alarm data) or a user interface that does not include a speaker adapted to provide audible output in response to patient monitoring data. This allows clinical compliance guidelines to be safely met in the event of a communication path failure, thus providing an appropriate backup option.

[0136] These advantages enable support for more flexible use cases, such as allowing care providers to be positioned in a separate (observation) room while ensuring that patient monitoring data is provided to them or that they are aware of any failure to provide patient monitoring data.

[0137] Similarly, the watchdog function enables the provision of a visual representation of patient monitoring information in the absence of a screen or a physical connection to a screen. This is because the visual representation of patient monitoring information can be reliably provided by the user interface (such reliability is guaranteed or ensured by the watchdog function).

[0138] To improve safety and provide backup, the patient monitor’s auxiliary alarm module 153 may include a dedicated visual output system 153C (e.g., a light bar) for providing information about the occurrence of an alarm.

[0139] To further improve security, the auxiliary alarm module 153 can be adapted to provide user-perceptible output (e.g., an audible alarm) for the patient monitoring data (thus performing the functions of a general alarm module), provided that the patient monitor 150 determines the state of the communication path 190 such that it cannot transmit patient monitoring data to the user interface 100. This ensures adequate backup for failures in the communication path (or user interface).

[0140] Both the user interface and the patient monitor can be adapted to monitor the status of another device. Therefore, the user interface can be adapted to monitor the status of the patient monitor, and the patient monitor can be adapted to monitor the status of the user interface.

[0141] The status of another device can be checked using any known method for monitoring the status of another device, such as using a heartbeat protocol or by iteratively requesting status information from the other device. In particular, since each device is configured to monitor its own status, information about the status of a device can be transmitted to another device, thereby enabling the other device to monitor the status of the original device.

[0142] The user interface and patient monitor can also be adapted to provide user-perceptible output in response to the monitored status of another device. The user interface can provide this output using an output module, and the patient monitor can provide it using an auxiliary alarm module. This improves the user's awareness of device malfunctions.

[0143] Of course, technicians will recognize that the user interface and / or patient monitor can be adapted to perform certain steps in response to determining that another device has failed. Such steps can be adapted from the exemplary steps previously described that can be taken in response to determining that the communication path cannot carry patient monitoring data.

[0144] In one example, in response to determining that the user interface has malfunctioned, the patient monitor may be adapted to control user-perceptible outputs in response to patient monitoring data. This ensures that patient monitoring data alerts the user even if the user interface has malfunctioned.

[0145] Therefore, in some examples, if it is determined that the communication path has failed (unable to successfully carry patient monitoring data) or the user interface has failed (e.g., unable to provide user-perceptible output in response to patient monitoring data), the patient monitor controls the auxiliary alarm module in response to the patient monitoring data. Of course, if neither the communication path nor the user interface has failed, the patient monitor can be adapted to prevent the auxiliary alarm module from responding to the patient monitoring data.

[0146] Other steps may be similar to those previously described and performed in response to determining that the communication path cannot successfully carry patient monitoring data to the user interface.

[0147] Preferably, the patient monitor is adapted to be able to communicate with more than one user interface, that is, the patient monitor is preferably not limited to communicating with only a single user interface.

[0148] In some examples, the patient monitor is adapted to transmit the same or different information representing patient monitoring data to more than one user interface. Thus, two different user interfaces can (on their respective screens) display visual representations 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 can display heart rate information, while the second user interface can display SpO2 information). Therefore, each type of patient monitoring data can reflect a portion of some overall patient monitoring data.

[0149] In some examples, the patient monitor is adapted to selectively communicate with one or more of a selection of user interfaces. This can be done by establishing communication paths to more than one user interface, as is known in the art.

[0150] Establishing a communication path between the user interface and the patient monitor can be performed using any known pairing protocol, such as a wireless pairing protocol. Such protocols typically have the ability to connect more than one device to a single "master" device (which, in this case, could be the patient monitor).

[0151] Therefore, it will be clear that the roles / tasks of displaying the visual representation of patient monitoring data can be shared or exchanged between different user interfaces, for example, by changing which user interfaces establish communication paths with the patient monitor, which user interfaces the patient monitor 150 transmits patient monitoring information to, and / or which patient monitoring information is associated with the information transmitted to different user interfaces.

[0152] Several suitable examples will be described below. A patient monitoring system (and therefore (one or more) patient monitors and / or (one or more) user interfaces) may be adapted to perform any one or more of such examples.

[0153] In some examples, more than one user interface displays a visual representation of the same patient monitoring data. In such examples, the patient monitor may be adapted to transmit the same patient monitoring data to more than one user interface.

[0154] In some examples, the visual representation of patient monitoring data is split across multiple user interfaces (e.g., a first user interface displays a visual representation of a first portion, a second user interface displays a visual representation of a second portion, and so on). Of course, some user interfaces may provide a visual representation of a portion of the same patient monitoring data as another user interface. Therefore, the patient monitor can transfer different instances or portions of patient monitoring data to different user interfaces.

[0155] These implementations are particularly useful when different clinicians are responsible for different aspects of a patient's condition. For example, a first portion of the patient monitoring data may be related to the patient's cardiology information (which can be processed / viewed by the cardiology team viewing the first user interface), while a second portion of the patient monitoring data may be related to the patient's respiratory information (which can be processed / viewed by the respiratory team viewing the second user interface).

[0156] In another example, the visual representation of patient monitoring data provided by a single patient monitor and the alarm thresholds associated with physiological data differ for each user interface. Therefore, each user interface can tailor the visualization and user-perceived alarms based on the skill set of the medical practitioner observing the corresponding user interface. This allows for optimal separation of actionable alarms based on their severity among users: nurses will be alerted when a patient's condition worsens, while doctors will be called once the patient's condition becomes life-threatening.

[0157] In some examples, only a single user interface displays a visual representation (partial) of the patient monitoring data, and the selection of a single user interface can be changed or switched between different user interfaces.

[0158] Therefore, it will be clear from the foregoing that the responsibility for the visual representation of (partial) patient monitoring data can be switched between different user interfaces.

[0159] Preferably, such switching is controlled such that the period during which no visual representation of the patient monitoring data (partially) is provided by the user interface is less than a predetermined duration. The length of this predetermined duration is preferably not less than the allowable time interval between detecting an alarm event and generating a user-perceptible output (e.g., according to clinical compliance guidelines). In some embodiments, the length of this duration is not less than 3 seconds, for example, in the range of 0.1 seconds to 3 seconds or 0.1 seconds to 1 second.

[0160] In some examples, this can be achieved by stopping communication to the first user interface (thus stopping the first user interface from providing a suitable visual representation) only when a communication path to a second, different user interface has been established (and preferably the transmission of patient monitoring data to the second user interface has been initiated).

[0161] In another example, this can be achieved by quickly switching the patient monitor's communication between a first user interface and a second user interface, for example, if the patient monitor is configured to communicate only with a single user interface. Other methods will be obvious to technicians.

[0162] Of course, it will be appreciated that the user interface 100 can also communicate with more than one patient monitor 150. Therefore, the user interface can switch between displaying a visual representation of patient monitoring data generated by a first patient monitor and displaying a visual representation of patient monitoring data generated by a second, different patient monitor.

[0163] In some embodiments, this switching is performed only if the patient monitor 150 is able to communicate with another user interface (e.g., a second user interface) to ensure that the visual representation of the patient monitoring data is displayed continuously.

[0164] In some embodiments, the patient monitor 150 may be adapted to begin transmitting patient monitoring data to a different user interface via a different communication path in response to a status indication that the communication path has failed or is otherwise unable to carry patient monitoring data (or the connected user interface has failed).

[0165] In this way, the patient monitor can attempt to automatically switch to a different user interface to display a visual representation of the patient monitoring data in response to a failure in communication with the user interface (which initially displays such a visual representation). This provides a backup location to ensure that patient monitoring data continues to be provided to clinicians.

[0166] In any of the foregoing embodiments, it will be apparent that if no patient is 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.

[0167] Figure 2 The illustration shows a use case scenario of a patient monitoring system 200 according to an embodiment of the present invention.

[0168] The patient monitoring system 200 includes multiple different patient monitors 150 and multiple different user interfaces 100. In the illustrated scenario, each patient monitor is adapted to communicate with a single user interface, and each patient monitor is associated with a corresponding bed 240.

[0169] The patient monitor 150 is located in a first room 205 (e.g., an intensive care unit). The user interface 100 is located in a second separate room 206 (e.g., an observation room) where the clinician 250 can be assigned.

[0170] Each patient monitor 150 communicates with a corresponding user interface 100, as previously described. This allows patient monitoring data, such as alarm data, to be transmitted to a separate room 205 occupied by the patient monitor. This, in turn, enables the suppression of alarms or other user-perceptible outputs at each patient monitor 150 (as this can be alternatively provided by the user interface), resulting in a quieter first room 205. This can significantly reduce patient stress and / or alarm fatigue for clinicians present in the first room 205, while ensuring that appropriate data is still provided to clinicians 250 (present in the second room 205).

[0171] Therefore, the proposed patient monitoring system can reduce patient stress and alarm fatigue by reliably transmitting patient monitoring data to the user interface, while ensuring that the user is notified of any failure to transmit patient monitoring data.

[0172] Figure 3 The illustration shows method 300 performed by a user interface, which includes an output module with a two-dimensional display screen. Method 300 is used to display patient monitoring data obtained by a patient monitor at the user interface.

[0173] Method 300 includes step 301 of receiving patient monitoring data from a patient monitor via a communication path.

[0174] Method 300 includes step 302 of controlling a two-dimensional display screen based on patient monitoring data to provide a visual representation of the patient monitoring data.

[0175] Method 300 includes step 303 of monitoring the state of the communication path between the patient monitor and the user interface.

[0176] Method 300 includes step 304 of monitoring the status of the user interface.

[0177] Method 300 also includes step 305, which controls the output module to provide a user-aware output indicating the status of the communication path.

[0178] Method 300 also includes step 306, which controls the output module to provide user-aware output indicating the state of the user interface.

[0179] Steps 301 and 302 can be grouped into one program thread. Steps 303 and 305 can be grouped into another program thread. Steps 304 and 306 can be grouped into yet another program thread. The three program threads can be executed continuously and / or in parallel with each other.

[0180] Figure 4The illustration depicts a method 400 performed by a patient monitor according to an embodiment of the present invention. The patient monitor includes an auxiliary alarm module adapted to controllably generate user-perceptible output. The method is used to provide patient monitoring data to a user interface for display using the patient monitor.

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

[0182] Method 400 includes step 402 of generating patient monitoring data in response to physiological data.

[0183] Method 400 includes step 403 of transmitting patient monitoring data to a user interface via a communication path.

[0184] Method 400 includes step 404 of monitoring the status of the communication path.

[0185] Method 400 includes step 405 of monitoring the status of the patient monitor.

[0186] Method 400 further includes step 406 of controlling the user-aware output of the auxiliary alarm module in response to the state of the communication path.

[0187] Method 400 further includes step 407 of controlling a user-aware output of the auxiliary alarm module in response to the state of the patient monitor.

[0188] Steps 401, 402, and 403 can be grouped into one program thread. Steps 404 and 406 can be grouped into another program thread. Steps 405 and 407 can be grouped into yet another program thread. The three program threads can be executed continuously and / or in parallel with each other.

[0189] Technicians will be able to easily develop processing systems for performing any of the methods described herein. Therefore, each step of the flowchart can represent a different action performed by the processing system, and can be executed by the corresponding module of the processing system.

[0190] Therefore, embodiments can utilize processing systems. Processing systems can be implemented in various ways using software and / or hardware to perform a variety of desired functions. A processor is one example of a processing system employing one or more microprocessors, which can be programmed using software (e.g., microcode) to perform desired functions. However, processing systems can be implemented with or without processors, and can also be implemented as a combination of dedicated hardware performing some functions and processors (e.g., one or more programmed microprocessors and associated circuitry) performing other functions.

[0191] Examples of processing system components that may be employed in various embodiments of this disclosure include, but are not limited to, conventional microprocessors, application-specific integrated circuits (ASICs), and field-programmable gate arrays (FPGAs).

[0192] In various implementations, a processor or processing system may be associated with one or more storage media, such as volatile and non-volatile computer memories, such as RAM, PROM, EPROM, and EEPROM. The storage media may be encoded with one or more programs that, when run on one or more processors and / or processing systems, perform desired functions. Various storage media may be fixed within the processor or processing system, or may be transportable, allowing one or more programs stored thereon to be loaded into the processor or processing system.

[0193] It will be understood that the disclosed methods are preferably computer-implemented methods. This also leads to the concept of a computer program comprising code modules for implementing any described method when the program is run on a processing system (such as a computer). Therefore, different portions, lines, or blocks of code of the computer program according to embodiments can be run by a processing system or computer to perform any of the methods described herein. In some alternative embodiments, the functions annotated in one or more block diagrams or flowcharts may occur out of order. For example, two blocks shown consecutively may actually operate substantially simultaneously, or blocks may sometimes operate in reverse order, depending on the functions involved.

[0194] By studying the accompanying drawings, disclosure, and claims, those skilled in the art will be able to understand and implement variations of the disclosed embodiments in practicing the claimed invention. In the claims, the word "comprising" does not exclude other elements or steps, and the words "a" or "an" do not exclude a plurality. A single processor or other unit may perform the functions of several items recited in the claims. Although specific measures are recited in dissimilar dependent claims, this does not indicate that combinations of these measures cannot be advantageously used. If a computer program has been discussed above, it may be stored / distributed on a suitable medium, such as an optical storage medium or solid-state medium provided with or as part of other hardware, but it may also be distributed in other forms, such as via the Internet or other wired or wireless telecommunications systems. If the term "suitable" is used in the claims or description, it should be noted that the term "suitable" is intended to be equivalent to the term "configured as." No reference numerals in the claims should be construed as limiting the scope.

Claims

1. A patient monitor for generating patient monitoring data to be visually represented by a two-dimensional display screen with a user interface, the patient monitor comprising: Communication systems suitable for: Patient monitoring data is transmitted via the communication path between the patient monitor and the user interface; Monitor the status of the communication path between the patient monitor and the communication module of the user interface; as well as An input module adapted to acquire patient physiological data from one or more physiological / patient sensors; An auxiliary alarm module, which is suitable for providing user-perceptible output; Patient monitor processor, which is suitable for: Monitor the status of the patient monitor; The physiological data is obtained and patient monitoring data is generated in response to the physiological data; The user-perceptible output of the auxiliary alarm module is controlled in response to the state of the communication path; and The user-perceptible output of the auxiliary alarm module is controlled in response to the state of the patient monitor; The auxiliary alarm module is controlled by the patient monitor processor. The patient monitor processor is adapted to: Determine whether the user interface includes an audible output module; and In response to the state of the communication path indicating that the communication path can successfully carry the patient monitoring data, and the user interface including an audible output module, the auxiliary alarm module of the patient monitor is prevented from generating any audible output in response to alarm data.

2. The patient monitor according to claim 1, wherein, The patient monitor processor is also adapted to: monitor the status of the user interface; and control the auxiliary alarm module in response to the status of the user interface.

3. The patient monitor according to any one of claims 1 to 2, wherein, The patient monitor processor is adapted to use the auxiliary alarm module to generate an audible output in response to alarm data, in response to the status indication of the communication path indicating that the communication path has failed or otherwise cannot successfully carry the patient monitoring data.

4. The patient monitor according to claim 1 or 2, wherein, The patient monitor does not have any two-dimensional screen for providing a visual representation of the patient monitoring data, and / or is configured not to communicate with devices having two-dimensional screens via a wired communication path.

5. A patient monitoring system, comprising a patient monitor according to any one of claims 1 to 4 and a user interface, the user interface being configured to provide a visual representation of patient monitoring data obtained by the patient monitor, the user interface comprising: Communication module, suitable for: Patient monitoring data is received from the patient monitor via the communication path between the patient monitor and the user interface; and Monitor the status of the communication path; An output module for providing user-perceptible output, the output module being coupled to a two-dimensional display screen to generate visual output; User interface processor, suitable for: Monitor the status of the user interface; The patient monitoring data is obtained from the communication module; The two-dimensional display screen is controlled based on the patient monitoring data to provide a visual representation of the patient monitoring data; The output module is controlled to provide a user-aware output indicating the state of the communication path; and The output module is controlled to provide user-aware output indicating the state of the user interface.

6. A method for providing patient monitoring data to a user interface for display using a patient monitor, the patient monitor including an auxiliary alarm module adapted to controllably generate user-perceptible output, the method comprising: Obtain patient physiological data from one or more patient sensors; Patient monitoring data is generated in response to the physiological data; Patient monitoring data is transmitted to the user interface via a communication path; Monitor the status of the communication path; Monitor the status of the patient monitor; The user-perceptible output of the auxiliary alarm module is controlled in response to the state of the communication path; The user-perceptible output of the auxiliary alarm module is controlled in response to the state of the patient monitor; Determine whether the user interface includes an audible output module; and In response to the state of the communication path indicating that the communication path can successfully carry the patient monitoring data, and the user interface including an audible output module, the auxiliary alarm module of the patient monitor is prevented from generating any audible output in response to alarm data.

Images