Gui synchronization of medical devices with remote monitoring devices

Abstract

This disclosure relates to a system for remotely monitoring a patient (1) located at a patient site (5). The system is configured to display patient data acquired by the medical devices (3A to 3C) on a graphical user interface (GUI) of medical devices (3A to 3C) located at the same location as the patient (1), and to transmit the patient data to remote display devices (7A to 7D) for display on the GUI of the remote display devices. The system is configured to operate in a first operating mode in which the GUIs of the medical devices (3A to 3C) and the remote display devices (7A to 7D) are configured to simultaneously display distinct GUI views on both the medical devices (3A to 3C) and the remote display devices (7A to 7D) that present the patient data acquired by the medical devices (3A to 3C). In this first operating mode, the system is configured to: detect a GUI synchronization initiation event occurring at a medical device (3A to 3C) or a remote display device (7A to 7D), and in response to detecting the GUI synchronization initiation event, synchronize the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) by displaying a common GUI view on the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D).

Description

Technical Field

[0001] This disclosure relates to the field of remote display of patient data, including data relating to a patient and / or medical devices connected to the patient. In particular, this disclosure relates to systems, methods, and computer programs for remote patient monitoring as defined in the preamble of the appended independent claims. Background Technology

[0002] Remote patient monitoring (RPM) involves collecting patient data using electronic medical devices and transmitting that data from the devices to a remote healthcare provider, who can then analyze the data and remotely track the patient's health. Real-time RPM is a subset of RPM in which patient data is transmitted to a healthcare provider in real time, allowing the provider to monitor the patient's current health status.

[0003] Medical devices used to collect patient data in a real-time RPM system may include, for example, wearable devices, sensors, medical treatment devices, local patient monitoring systems, and other monitoring tools that can track vital signs such as heart rate, blood pressure, oxygen levels, and respiratory rate.

[0004] Examples of medical devices that can provide remote access to patient data acquired during ongoing treatment include mechanical ventilators. Many leading ventilator manufacturers today offer products that can grant remote clinicians access to patient data acquired by the ventilator during ongoing mechanical ventilation via a remote display or monitor. This patient data can be correlated with both the patient and the operation of the ventilator. Some solutions even enable remote control of the ventilator via a remote display or monitor.

[0005] This disclosure addresses issues related to remote, real-time monitoring of patients connected to a medical device that also provides bedside monitoring via a graphical user interface (GUI). The medical device can be, for example, a bedside medical monitor or a medical treatment device with integrated monitors, such as a mechanical ventilator or cardiopulmonary bypass machine.

[0006] When monitoring a patient in real time via both a bedside monitor (i.e., the monitor of the medical device) and a remote monitor, it is generally advantageous if the graphical user interface (GUI) of the remote monitor is a copy of the GUI of the bedside monitor. This is because it allows the remote clinician (who is typically an experienced clinician familiar with the GUI of the bedside monitor) to navigate the GUI of the remote monitor without specific training. Another advantage is that the same GUI view can be presented to both the bedside and remote clinicians, which facilitates collaboration between them, for example, in patient diagnosis and determining appropriate adjustments to medical device settings.

[0007] To ensure that the same or corresponding GUI view is presented to both bedside and teleclinic physicians, the bedside monitor and remote monitor sometimes operate in a master-slave mode. In master-slave mode, the remote monitor is configured to always reflect the GUI view currently displayed on the bedside monitor. Thus, changes to the GUI view of the bedside monitor initiated by the bedside clinician are immediately reflected in the remote monitor's GUI.

[0008] However, the master-slave configuration of bedside and remote monitors limits the possibility of presenting the necessary patient data to teleclinics so that they can better assess the patient's physiological condition and / or the operation of medical devices. Therefore, there is a need for improvements in this area to enhance patient diagnosis and / or medical device operation during remote patient monitoring. Summary of the Invention

[0009] The purpose of this disclosure is to mitigate, reduce or eliminate one or more of the defects and disadvantages described above in the prior art.

[0010] In particular, the purpose of this disclosure is to provide a means to facilitate collaboration between bedside clinicians who monitor patients via bedside monitors of medical devices and remote clinicians who monitor patients via remote monitors or display devices.

[0011] Ultimately, the purpose of this disclosure is to improve patient safety through enhanced remote patient monitoring.

[0012] According to a first aspect of this disclosure, a system for remotely monitoring a patient located at a patient site is provided. The system is configured to display patient data acquired by a medical device located at the same patient site as the patient on a graphical user interface (GUI) of a medical device. The system is also configured to transmit the patient data to a remote display device for display on the GUI of the remote display device. The system is configured to operate in a first operating mode, in which the GUI of the medical device and the GUI of the remote display device are configured to simultaneously display distinct GUI views on both the medical device and the remote display device, representing the patient data acquired by the medical device. When operating in this first operating mode, the system is configured to: detect a GUI synchronization initiation event occurring at either the medical device or the remote display device, and in response to detecting the GUI synchronization initiation event, synchronize the GUI of the medical device and the GUI of the remote display device at least temporarily by displaying a common GUI view on both the medical device's GUI and the remote display device's GUI.

[0013] In the first operating mode, the remote monitoring system enables remote clinicians to select a GUI view independently of that selected by another clinician, and thus choose the presentation of patient data of interest. However, when a GUI synchronization initiation event is detected, a common GUI view is displayed to both clinicians, thus forcing them to be presented with the same view, thereby minimizing the risk of misunderstanding and facilitating collaboration on adjustments to patient diagnosis and / or medical device settings.

[0014] This means that, in the first operating mode, the GUI of the medical device and the GUI of the remote display device are configured to operate asynchronously, which enables the simultaneous display of different GUI views on the medical device's GUI and the remote display device's GUI for presenting patient data obtained by the medical device.

[0015] The term "different from each other" in this document means that the type of patient data displayed in each GUI view is different, or that the same patient data is presented in different ways (i.e., in different formats) in each GUI view. Similarly, "displaying a common GUI view on both the medical device's GUI and the remote display device's GUI" means that the same patient data is presented in the same or substantially the same way (i.e., in the same or substantially the same format) on both the medical device's GUI and the remote display device's GUI.

[0016] A common GUI view can be the current GUI view of the medical device when a GUI synchronization initiation event is detected, the current GUI view of the remote display device when a GUI synchronization initiation event is detected, or a GUI view that is different from both the current GUI view of the medical device and the current view of the remote display device.

[0017] Preferably, the GUI of the remote display device is a copy of the GUI of the medical device, thereby effectively enabling the remote display device to function as a digital twin of the GUI of the medical device. As discussed above, this brings several advantages in areas such as medical staff training, collaboration, patient diagnosis, and treatment optimization.

[0018] According to some implementations, a GUI synchronization initiation event is a user input expected by the user that prompts the synchronization of the GUI of a medical device and the GUI of a remote display device, said user input being entered into the system via one of the medical device and the remote display device. This gives bedside clinicians and teleclinicians the freedom to explore and select their preferred GUI views, while still ensuring that they can be presented with the same GUI view by manually requesting GUI synchronization via the medical device and / or the remote display device.

[0019] Upon receiving a GUI synchronization request from a bedside clinician or a remote clinician, the system can be configured to seek approval from another clinician before GUI synchronization. Therefore, according to some implementations, a GUI synchronization initiation event that triggers GUI synchronization is user input indicating approval of the GUI synchronization request entered into the system via the other device in response to a GUI synchronization request from one of the medical devices or a remote display device. This is advantageous because a public GUI view cannot overwrite the current GUI view being studied by the clinician without the clinician's approval.

[0020] According to some implementations, a GUI synchronization initiation event is a change in the GUI view of a medical device or a remote display device. For example, the system can be configured such that a remote clinician can change the GUI view of the remote display device independently of the medical device's GUI view, as long as the medical device's GUI view remains unchanged. However, once the medical device's GUI view is changed, the new GUI view is transmitted to the remote display device, overriding the remote display device's current GUI view. This can be advantageous in scenarios where an experienced remote clinician is supporting a less experienced bedside clinician. The more experienced remote clinician can then move freely between different GUI views on the remote display device, knowing that he or she will be aware of any changes made to the medical device's GUI view.

[0021] In some implementations, the GUI synchronization initiation event is a change in the operating settings of the medical device. This brings the same advantages discussed above, except that in this case, the current GUI view of the remote display device will not be reflected in the GUI view of the medical device. Figure 1 Instead of overwriting the medical device's GUI view with any changes, this feature only overwrites the GUI view when the medical device's operating settings change. From a patient safety perspective, changes to the medical device's operating parameters are more critical events than changes to the GUI view. Therefore, this feature can have the following effect: giving remote clinicians more freedom in choosing the GUI view while ensuring that the relevant GUI view is presented to them when the medical device's operating settings change. In the case of changing operating settings via the medical device's GUI, this means that the GUI view where the settings can be changed is transmitted to the remote display device, thus making the remote clinician immediately aware of any changes to the operating settings. Typically, patient data, including the medical device's operating settings, is always synchronized between the medical device and the remote display device. However, if the remote clinician happens to be studying a GUI view that does not present the operating settings in question, there is a risk that the remote clinician may not be aware of the change in operating settings. Therefore, by making the medical device's GUI view overwrite the current view of the remote display device in response to changes in the medical device's operating settings, this risk is effectively eliminated. For example, operating settings may be settings related to and affecting the treatment the patient is undergoing, provided by the medical device.

[0022] According to some implementations, the GUI synchronization initiation event is a change in the alarm status of the medical device. This is advantageous because triggering an alarm in the medical device can trigger a common GUI view (e.g., a GUI view that presents the relevant alarm data) to be displayed on both the medical device and the remote display device.

[0023] According to some implementations, the GUI synchronization initiation event is a change in the measurement value obtained by the sensors of the medical device. This is advantageous because by displaying a common GUI view of the relevant measurement data on both the medical device and the remote display device, both the bedside clinician and the remote clinician can become aware of the unexpected change in the measurement value.

[0024] According to some implementations, the system is configured to temporarily synchronize the GUI upon detecting a GUI synchronization initiation event, thereby allowing the GUI views of the medical device and the remote display device to diverge. This is advantageous because the same GUI view can be presented to both the bedside clinician and the remote clinician when needed or desired, after which they can independently continue to study their preferred GUI view.

[0025] According to some implementations, the system is configured to enter a master-slave operating mode for at least a certain period of time after detecting a GUI synchronization initiation event. In this mode, changes to the GUI view of one device (acting as a slave in the master-slave mode) are prevented, and the GUIs of the medical device and the remote display device are resynchronized in response to changes to the GUI view of the other device (acting as the master in the master-slave mode). This is advantageous because it is generally desirable to present the same GUI view to both the bedside clinician and the remote clinician for a certain period of time after a GUI synchronization initiation event. For example, if the bedside clinician requests GUI synchronization (because the bedside clinician wants to show and discuss patient data presented in the current GUI view of the medical device with the remote clinician), the master-slave operating mode ensures that any changes made to the GUI view of the medical device are reflected in the GUI view of the remote display device. This allows the bedside clinician to "bring the remote clinician along" when switching between different GUI views that might facilitate discussion. The system can be configured to maintain the master-slave operating mode for a predetermined period of time, or to maintain the master-slave operating mode until the system receives a request to re-enter a first operating mode or some other operating mode via either the medical device or the remote display device.

[0026] According to some implementations, the system is configured to enter an operating mode, referred to herein as a dual semi-independent operating mode, for at least a certain period of time after detecting a GUI synchronization initiation event. In dual semi-independent operating mode, the system is configured to resynchronize the GUIs of the medical device and the remote display device in response to a change in the GUI view of either the medical device or the remote display device. This means that both the bedside clinician and the remote clinician can change the GUI view of their devices, but any changes to the GUI view will be transmitted to the other device, thus overriding the current GUI view being studied by the other clinician. This is advantageous because it allows the bedside clinician and the remote clinician to alternately display each other's relevant GUI views for a certain period of time after a GUI synchronization initiation event. The system can be configured to maintain the dual semi-independent operating mode for a predetermined period of time, or to maintain the dual semi-independent operating mode until the system receives a request via either the medical device or the remote display device to re-enter an independent operating mode or some other operating mode.

[0027] According to some implementations, the system includes a server configured to receive patient data acquired by a medical device and transmit the patient data to a remote display device for real-time patient data display. In other implementations, the acquired patient data can be sent directly to the remote display device via the medical device or any other device at the patient's location that can communicate with the medical device. However, using an intermediate server to receive the acquired patient data and transmit it to the remote display device offers several advantages in terms of system architecture and functionality. For example, the intermediate server enables centralized buffering and / or storage of patient data on the server and facilitates access to patient data from different remote display devices.

[0028] According to some implementations, the server is configured to provide the functionality described herein via a web application stored on the server and accessible by a web browser on the remote display device. Based on the teachings of this disclosure, this enables any display device equipped with a web browser to be used as a remote display device for remote monitoring of a patient.

[0029] The medical device disclosed herein can be any type of electronic medical device. In some embodiments, the medical device is a device that provides intensive care treatment to a patient at the patient's location, such as a mechanical ventilator or anesthesia machine that provides respiratory therapy, or an extracorporeal membrane oxygenation (ECMO) device that provides ECMO treatment. In other embodiments, the medical device can be a bedside patient monitor for bedside monitoring of a patient's physiological condition, or a wearable medical device configured to be worn on a patient's body. The medical device includes a monitor or display on which a GUI of the medical device is displayed.

[0030] According to a second aspect of this disclosure, a method is provided in a system for remotely monitoring a patient located at a patient site, wherein the system is configured to display patient data acquired by a medical device on a GUI of a medical device located at the same location as the patient, and to transmit the patient data to a remote display device for display on the GUI of the remote display device. The method includes the steps of: operating the system in a first operating mode, wherein the GUI of the medical device and the GUI of the remote display device are configured such that distinct GUI views for presenting the patient data acquired by the medical device can be simultaneously displayed on both the medical device and the remote display device. The method further includes the steps of: in the first operating mode, detecting a GUI synchronization initiation event occurring at the medical device or the remote display device, and in response to detecting the GUI synchronization initiation event, at least temporarily synchronizing the GUIs of the medical device and the remote display device by displaying a common GUI view on both the medical device and the remote display device.

[0031] According to some implementations, a GUI synchronization initiation event is a user input expected by the user that instructs the synchronization of the GUI of the medical device and the GUI of the remote display device, the user input being input to the system via one of the medical device (3A to 3C) and the remote display device.

[0032] According to some implementations, user input indicates approval of the GUI synchronization request by inputting it into the system via the other device in response to a GUI synchronization request from one of the medical devices and the remote display device.

[0033] According to some implementations, a GUI synchronization initiation event is a change in the GUI view of a medical device or remote display device.

[0034] According to some implementations, GUI synchronously initiates events when the operating settings of the medical device are changed.

[0035] According to some implementations, the method includes the following steps: temporarily synchronizing the GUI when a GUI synchronization initiation event is detected, and thereafter allowing the GUI views of the medical device and the remote display device to be different.

[0036] According to some implementations, the method includes the following steps: after detecting a GUI synchronization initiation event, operating the system in master-slave mode for at least a certain period of time, and in master-slave mode, preventing changes to the GUI view of one device acting as a slave in master-slave mode of medical device and remote display device, and resynchronizing the GUIs of medical device and remote display device in response to changes in the GUI view of the other device acting as master in master-slave mode.

[0037] According to some implementations, the method includes the following steps: after detecting a GUI synchronization initiation event, operating the system in a dual semi-independent operation mode for at least a certain period of time, and in the dual semi-independent operation mode, resynchronizing the GUI of the medical device and the GUI of the remote display device in response to a change in the GUI view of either the medical device or the remote display device.

[0038] According to some implementations, the common GUI view is the current GUI view of the medical device, the current GUI view of the remote display device, or a GUI view different from both the current GUI view of the medical device and the current GUI view of the remote display device. In most scenarios, especially when GUI synchronization is performed in response to a GUI synchronization command or request from a bedside clinician or a remote clinician, the common GUI view will typically be either the current GUI view of the medical device or the current view of the remote display device.

[0039] This method is a computer-implemented method, which is executed by the system when a computer program is executed by one or more processors of the system.

[0040] Therefore, according to a third aspect of this disclosure, a computer program is provided for a system for remotely monitoring a patient located at a patient site, wherein the system is configured to display patient data acquired by a medical device on a GUI of a medical device located at the same location as the patient, and to transmit the patient data to a remote display device for display on the GUI of the remote display device. The computer program includes computer-readable instructions that, when executed by at least one processor of the system, cause the system to perform the methods described above.

[0041] According to some implementations, the computer program is a web application residing in the aforementioned server and accessible by a remote display device via a web browser on the remote display device.

[0042] In other embodiments, the principles of this disclosure can be implemented using a distributed computer program, such as a client-server application. In this case, the method can be performed while executing a client application for remote patient monitoring residing on a remote display device, which is configured to communicate with a server application residing on a server.

[0043] In other embodiments, the method may be performed while executing a first computer program component residing in a remote display device, the first computer program communicating with a second computer program component residing in a medical device, thereby allowing patient data obtained through the medical device to be sent directly to the remote display device without any intermediate server.

[0044] According to a fourth aspect of this disclosure, a computer program product is provided, the computer program product including a data storage medium for storing the aforementioned computer program, such as a non-transitory memory hardware device.

[0045] The effects and features of the second, third, and fourth aspects of this disclosure are largely similar to those described above in conjunction with the first aspect.

[0046] Other effects and advantages of the systems, methods, and computer programs disclosed herein will become apparent from the following detailed description. Attached Figure Description

[0047] The above-mentioned objects, as well as other objects, features, and advantages of this disclosure, will be more fully understood through the following illustrative and non-limiting detailed description of exemplary embodiments of this disclosure taken in conjunction with the accompanying drawings.

[0048] Figure 1 A system for remotely monitoring a patient located at the patient's site, according to an exemplary embodiment of the present disclosure, is shown.

[0049] Figure 2 An example is shown of a graphical user interface (GUI) view that presents real-time patient data from the patient site on a display of a remote display device.

[0050] Figure 3 It shows the adjustment Figure 1 The GUI synchronization window for the remote monitoring system shown is the GUI synchronization settings.

[0051] Figures 4A to 4D The diagram schematically illustrates GUI views of medical devices and remote display devices for several different GUI synchronization settings.

[0052] Figure 5 This is a flowchart illustrating a method performed in a system for remotely monitoring a patient located at a patient site, according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0053] Figure 1 An exemplary embodiment of a system for remotely monitoring a patient 1 located at a patient site 5 and connected to medical devices 3A to 3C located at the same patient site 5 as the patient 1 is shown. Medical devices 3A to 3C are configured to acquire patient data related to the patient 1 and / or the medical treatments the patient is undergoing. Patient data related to the patient 1 may include any type of data indicating the patient's physiological state or condition. Patient data related to the medical treatment the patient is undergoing may include medical device settings, data indicating the operation of the medical devices, data indicating the medical effects of the ongoing treatment, etc. Therefore, in this context, patient data should be broadly interpreted to include any type of data related to the patient 1 or the medical devices 3A to 3C to which the patient is connected.

[0054] This system is a remote patient monitoring (RPM) system used for near real-time monitoring of patient 5 from a location far from the patient site 5. This system may sometimes be referred to as a real-time RPM system below.

[0055] Devices 3A to 3C can be any type of electronic medical device configured to acquire patient data at the patient site and facilitate the transmission of patient data from the patient site to remote display devices 7A to 7D.

[0056] In some embodiments, medical devices 3A to 3C are intensive care treatment devices, i.e., medical treatment devices configured to provide intensive care treatment to patient 1. For example, the medical device may be a respiratory device for providing respiratory therapy to patient 1, such as a mechanical ventilator 3A or an anesthesia machine. According to another example, the medical device is a cardiopulmonary bypass machine for oxygenating the blood of patient 1, such as an ECMO device 3B for providing extracorporeal membrane oxygenation (ECMO) therapy to patient 1.

[0057] In other embodiments, medical devices 3A to 3C may be bedside patient monitoring systems 3C located at the patient site 5 along with the patient.

[0058] Medical devices 3A to 3C are typically configured to acquire patient data using one or more sensors for measuring patient parameters or the internal state and / or settings of the medical device.

[0059] In embodiments where the medical device is a respiratory device such as a mechanical ventilator 3A, non-limiting examples of patient data obtainable through the medical device include: the patient's airway pressure (P... aw ), positive end-expiratory pressure (PEEP) applied to the patient's airway, the patient's respiratory rate (RR), the patient's minute ventilation (MV), the tidal volume (VT) of the inhaled and / or exhaled respiratory gases, the patient's inspiratory to expiratory ratio (I:E), the oxygen concentration of the respiratory gases delivered to the patient, the carbon dioxide concentration of the exhaled respiratory gases, and the patient's dynamic compliance (C). dyn The patient's electromyography (EMG) signal, heart rate, mean arterial blood pressure (MAP), body temperature, blood oxygen saturation level, and central venous pressure (CVP) were measured.

[0060] In embodiments where the medical device is a cardiopulmonary bypass machine, such as an ECMO device 3B, non-limiting examples of patient data obtainable through the medical device include: the flow rate of purge gas supplied to the oxygenator of the ECMO device, the oxygen and / or carbon dioxide concentrations in the pre-oxygenator and / or post-oxygenator, the pressure drop across the oxygenator, the gas delivery resistance of the oxygenator, blood parameters determined using a blood gas analyzer (BGA) of the ECMO device, the patient's venous pressure and / or arterial pressure, heart rate, body temperature, blood oxygen saturation level, and CVP.

[0061] In the implementation of the medical device as a bedside patient monitoring system 3C, non-limiting examples of patient data that can be obtained through the medical device include: heart rate, ECG signal, respiratory rate, blood pressure, body temperature, and blood oxygen saturation level.

[0062] Medical devices 3A to 3C include monitors 4A to 4C for presenting acquired patient data to the patient 1 and / or bedside clinician via the medical device's graphical user interface (GUI). The GUI of medical devices 3A to 3C can be navigated and manipulated by the bedside clinician and / or patient to present relevant patient data, change medical device settings, set alarms, etc.

[0063] The system is also configured to transmit patient data obtained through medical devices 3A to 3C to remote display devices 7A to 7D. In the illustrated embodiment, patient data is transmitted from the patient site 5 by transmission modules 9A to 9C of medical devices 3A to 3C. Transmission modules 9A to 9C may be integrated into medical devices 3A to 3C, or they may be additional transmission modules that can be connected to the communication ports of the medical devices to provide network connectivity to the medical devices. Transmission modules 9A to 9C may be configured to send patient data to system server 13. Server 13 is configured to receive and process patient data and transmit the patient data to remote display devices 7A to 7D.

[0064] Transmitting modules 9A to 9C are typically, but not necessarily, configured to wirelessly transmit patient data to server 13, for example, via a wireless network. The network used to transmit patient data from transmitting modules 9A to 9C to server 13 can be the Internet or a healthcare provider's IT network, such as a healthcare institution's local area network (LAN) or a healthcare organization's private wide area network (WAN). Transmitting modules 9A to 9C can be configured to use any available wireless communication technology, such as Wi-Fi, 4G, or 5G mobile network technology. It should also be noted that this disclosure is not limited to wireless communication, and the principles described herein for remote patient monitoring also apply when patient data is transmitted, partially or entirely, from the patient site 5 to remote display devices 7A to 7D via a wired connection.

[0065] Server 13 may be a web server connected to the Internet to enable remote monitoring of patient 1 via a display device connected to the Internet of any type. Server 13 includes at least one processor 10 and may be configured to provide the functionality described herein when the at least one processor executes a computer program stored in a data storage medium 14 (e.g., a non-transitory memory hardware device of server 13).

[0066] In the illustrated example, the computer program stored in server 13 is a web application accessible via a web browser stored in data storage media 12A to 12C (e.g., non-transitory memory hardware devices of the remote display devices) on remote display devices 7A to 7D. Therefore, patient data is received by server 13 from sending modules 9A to 9C and transmitted to display devices 7A to 7D via the web application stored in server 13. Of course, in other embodiments, the transmission of patient data from patient site 5 to remote display devices 7A to 7D may involve several network nodes. For example, the system may include a web server for receiving and / or storing patient data from patient site 5, and a web application server for hosting and running the web application that transmits patient data to remote display devices 7A to 7D.

[0067] The system is configured to transmit patient data obtained at five locations at the patient site via medical devices 3A to 3C to remote display devices 7A to 7D in near real-time, and to display the patient data as real-time patient data on displays 11A to 11D of the remote display devices 7A to 7D.

[0068] Figure 2 An exemplary view 16 is shown of a GUI 15 of remote display devices 7A to 7D, which is displayed on displays 11A to 11D of the remote display devices 7A to 7D by a web application residing in server 13 running in a web browser on the remote display devices. Strictly speaking, GUI 15 is the GUI of the web application residing in server 13, and not the actual GUI of the remote display devices 7A to 7D. However, throughout this disclosure, the GUI of a remote display device should be interpreted as any GUI presented on displays 11A to 11D of the remote display devices 7A to 7D.

[0069] The GUI 15 of the remote display devices 7A to 7D may be a copy of the GUI of the medical devices 3A to 3C. The fact that the GUI 15 of the remote display devices 7A to 7D is a copy of the GUI of the medical devices means that at least some views of the GUI of the remote display devices are substantially the same as the corresponding GUI views of the medical devices. A GUI view is generally defined as a specific visual representation or arrangement of information and elements on a screen. In the context of this disclosure, substantially the same corresponding GUI views means that patient data presented in the corresponding views (e.g., in placement, font, size, color, etc.) is presented in substantially the same manner. Preferably, most menus, controls, and other GUI objects are also presented in substantially the same manner in the corresponding GUI views. Ideally, substantially all patient data and substantially all GUI objects in the corresponding GUI views are presented in substantially the same manner, such that a remote clinician perceives the GUI views of the remote display devices 7A to 7D as the corresponding GUI views of the medical devices 3A to 3C.

[0070] Preferably, the GUI 15 of the remote display devices 7A to 7D is configured to selectively present GUI views corresponding to most and preferably all GUI views available via the GUI of the medical devices 3A to 3C, thereby effectively making the remote display devices 7A to 7D look and behave largely like the monitors 4A to 4C or the medical devices 3A to 3C. In this way, in a sense, the GUI of the remote display devices 7A to 7D can become a "digital twin" of the GUI of the medical devices 3A to 3C by running a web application provided by the system server 13. In the illustrated example, while referring to... Figure 1 The GUI 15 of the remote display device is a copy of the GUI of the mechanical ventilator 3A presented on the ventilator monitor 4A. The exemplary GUI view 16 is a real-time view including at least one real-time data field 18 for displaying real-time patient data 17 obtained by the ventilator 3A.

[0071] In this context, it should be noted that this disclosure does not relate to remote control of medical devices, and that changes to the operation of medical devices 3A to 3C cannot be made via the GUI 15 of the remote display devices 7A to 7D. The digital twin of the medical device GUI displayed on the remote display devices 7A to 7D is used solely for the purpose of presenting patient data to remote clinicians so that they can assess the patient's physiological condition and / or ongoing treatments provided by medical devices 3A to 3C.

[0072] Refer again Figure 1The remote monitoring system is configured to operate in a first operating mode, in which the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D are configured to simultaneously display different GUI views on the monitors 3A to 3C of the medical devices and the detectors 11A to 11D of the remote display devices. In this first operating mode, the remote monitoring system thus allows a remote clinician located at the same location as the remote display devices 7A to 7D to select a GUI view and therefore choose the presentation of patient data of interest to him or her, regardless of which GUI view the bedside clinician is currently studying.

[0073] To facilitate collaboration between bedside clinicians and teleclinicians, and to avoid misunderstandings due to discrepancies in patient data presentation, the remote monitoring system is configured to, at least temporarily, simultaneously display a common GUI view on both the GUI of medical devices 3A to 3C and the GUI of remote display devices 7A to 7D in response to the detection of certain events (referred to herein as GUI synchronization initiation events). Therefore, when the remote monitoring system detects a GUI synchronization initiation event, the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D are synchronized at least temporarily to display the same or common GUI view to both the bedside clinician and the teleclinician. Furthermore, to further facilitate collaboration between bedside clinicians and teleclinicians, medical devices 3A to 3C and remote display devices 7A to 7D may include functions enabling communication between the bedside clinician and the teleclinician via the medical devices and remote display devices. Such functions may include, for example, functions for voice, text, chat, and / or video communication.

[0074] The common GUI view can be the current GUI view of medical devices 3A to 3C when a GUI synchronization initiation event is detected, the current GUI view of remote display devices 7A to 7D when a GUI synchronization initiation event is detected, or even a GUI view different from both the current GUI view of the medical devices and the current view of the remote display devices. The remote monitoring system can be configured to select which GUI view should be displayed as the common GUI view based on the type and source of the GUI synchronization initiation event.

[0075] In some implementations, the first operating mode is an independent operating mode in which the GUI of medical devices 3A to 3C and the GUI of remote display devices 7A to 7D can be configured independently to enable bedside clinicians and remote clinicians to select a GUI view and thus select the presentation of patient data of interest independently of the current GUI view and any changes made to the current GUI view of the other device.

[0076] A GUI synchronization initiation event can be a user input that instructs the user to synchronize the GUI of a medical device with the GUI of a remote display device, said user input being entered into the system via one of the medical devices 3A to 3C and the remote display devices 7A to 7D. This gives bedside clinicians and remote clinicians the freedom to explore and select their preferred GUI views, while still ensuring that they can have the same GUI view as another clinician presented by manually requesting GUI synchronization.

[0077] Upon receiving a GUI synchronization request from a bedside clinician or a remote clinician, the system can be configured to seek approval from another clinician before GUI synchronization. For example, the system can be configured to prompt another clinician for approval of the GUI synchronization request by displaying a confirmation or accept button on the GUI of the other clinician's device, and to synchronize the GUI only if the button is pressed. Therefore, according to some implementations, the GUI synchronization initiation event that triggers GUI synchronization is user input indicating approval of the GUI synchronization request entered into the system via another device among medical devices 3A to 3C and remote display devices 7A to 7D in response to a GUI synchronization request from one of the devices 3A to 3C and 7A to 7D. This is advantageous because a public GUI view cannot overwrite the current GUI view being studied by the clinician without the clinician's approval.

[0078] In some implementations, the first operating mode may be a semi-independent operating mode. Similarly, in semi-independent operating mode, the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D can be configured to allow a bedside clinician and a remote clinician to select a GUI view of interest independently of the GUI view currently being studied by the other clinician. However, in semi-independent operating mode, one of the devices acts as the master device, and any changes made to the GUI view of the master device trigger synchronization of the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D, so that the changed GUI view of the master device is displayed on both devices.

[0079] For example, a remote monitoring system can be configured with medical devices 3A to 3C acting as the master device. This means that as long as the GUI view of medical devices 3A to 3C remains unchanged, remote clinicians can freely move between different GUI views on remote display devices 7A to 7D. However, once the GUI view of medical devices 3A to 3C changes, the new GUI view of the medical devices is transmitted to remote display devices 7A to 7D, thus overriding the current GUI view of the remote display devices.

[0080] Therefore, the semi-independent operation mode is an operation mode in which the change of the GUI view of medical devices 3A to 3C or remote display devices 7A to 7D (whichever acts as the master device) constitutes a GUI synchronization initiation event, which causes a common GUI view corresponding to the changed GUI view of the master device to be displayed on both medical devices 3A to 3C and remote display devices 7A to 7D.

[0081] In some implementations, the GUI-initiated event is a critical event requiring alertness from clinicians. Non-limiting examples of such critical events include: changes in the operating settings of medical devices 3A to 3C, changes in the alarm status of medical devices 3A to 3C, and changes in sensor measurements obtained by sensors of medical devices 3A to 3C. In response to the detection of a critical event, the remote monitoring system can be configured to display a common GUI view on both medical devices 3A to 3C and remote display devices 7A to 7D, presenting data related to the critical event.

[0082] The remote monitoring system can be configured to temporarily synchronize the GUI views of medical devices 3A to 3C with those of remote display devices 7A to 7D upon detecting a GUI synchronization initiation event, after which the GUI views of the medical devices and the remote display devices are allowed to diverge again. In some embodiments, GUI synchronization can be instantaneous, thereby allowing the GUI views of medical devices 3A to 3C and remote display devices 7A to 7D to diverge immediately after GUI synchronization. In this case, the remote monitoring system can be configured to remain in a first operating mode after detecting a GUI synchronization event.

[0083] In other embodiments, the remote monitoring system is configured to switch from a first operating mode to a second operating mode for at least a certain period of time upon detecting a GUI synchronization initiation event. The second operating mode is a synchronous operating mode, in which the GUIs of medical devices 3A to 3C and the GUIs of remote display devices 7A to 7D are synchronized to always display the same GUI view. The synchronous operating mode may be maintained for a predetermined period of time, or it may be maintained until the system receives a request to re-enter the first operating mode or another asynchronous operating mode via either medical devices 3A to 3C or remote display devices 7A to 7D. When switching from the synchronous operating mode to the asynchronous operating mode, the GUIs of medical devices 3A to 3C and / or the GUIs of remote display devices 7A to 7D may be configured to maintain the current GUI view (i.e., the GUI view corresponding to the common GUI view displayed on the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D when switching from the synchronous operating mode) or switch to a default GUI view. Such a default GUI view may be different for medical devices 3A to 3C and remote display devices 7A to 7D. Alternatively, the GUI of the medical devices 3A to 3C and / or the GUI of the remote display devices 7A to 7D can be configured to switch to the previous GUI view when switching from synchronous operation mode to asynchronous operation mode. The previous GUI view may, for example, be the GUI view displayed by the respective device before entering synchronous operation mode.

[0084] For example, the system can be configured to enter master-slave operation mode for at least a certain period of time after detecting a GUI synchronization initiation event. In master-slave operation mode, one of the medical devices 3A to 3C and the remote display devices 7A to 7D acts as the master device and the other as the slave device. The GUI view of the master device can be changed, but the GUI view of the slave device cannot be changed. Any changes to the GUI view of the master device and any changes made to the GUI view of the master device are reflected in the GUI of the slave device, ensuring that the GUI views of the master device and the slave device always remain the same.

[0085] In another example, the system can be configured to enter a dual semi-independent operating mode for at least a certain period of time after detecting a GUI synchronization initiation event. The dual semi-independent operating mode in this document refers to the semi-independent operating mode described above, in which both medical devices 3A to 3C and remote display devices 7A to 7D act as the master devices. This means that in the dual semi-independent operating mode, both the bedside clinician and the remote clinician can select their preferred GUI view, but not simultaneously. Changes to the GUI view made by either the bedside clinician or the remote clinician will be reflected in the GUIs of both medical devices 3A to 3C and remote display devices 7A to 7D.

[0086] Now refer to Figure 3 as well as Figures 4A to 4D This section describes an exemplary implementation of the proposed GUI synchronization function.

[0087] Figure 3 It shows the method for... Figure 1 The GUI synchronization window 20 shown is used to adjust the GUI synchronization settings of the remote monitoring system. The GUI synchronization window 20 can be accessed via the GUI of any one or both of the medical devices 3A to 3C and the remote display devices 7A to 7D.

[0088] According to this example, the GUI synchronization window 20 includes four radio buttons B1 to B4 corresponding to the respective GUI synchronization settings. Furthermore, the GUI synchronization window 20 includes two push buttons B5 to B6 for transmitting the current GUI view of medical device monitors 4A to 4C to remote display devices 7A to 7D (button B5) and for transmitting the current GUI view of remote display devices 7A to 7D to medical device monitors 4A to 4C (button B6).

[0089] The default selection is the first GUI synchronization setting B1. This setting places the remote monitoring system in the aforementioned standalone operating mode. In other embodiments, the system's default operating mode may be the aforementioned semi-standalone operating mode, for example, where medical devices 3A to 3C act as the master device.

[0090] The second GUI synchronization setting B2 places the remote monitoring system in a master-slave operation mode, where medical device monitors 4A to 4C act as the master and remote display devices 7A to 7D act as slaves. When the master-slave operation mode is selected, the system is configured to first transmit the current GUI view of the master to the slave, and then continue to transmit all changes made to the GUI view of the master to the GUI of the slave. In this regard, it should be noted that changes to the GUI view can include any visually perceptible changes made to the GUI view, including the display of pop-ups, drop-down menus, data input, animations to indicate user selections, etc. Therefore, as long as the remote monitoring system operates in master-slave operation mode, the GUI of the slave will replicate the GUI of the master, and the remote clinician and the bedside clinician will always be presented with the same information. Optionally, in other embodiments where the independent operation mode is the default operation mode of the system, the second GUI synchronization setting B2 can place the remote monitoring system in a semi-independent operation mode, where medical devices 3A to 3C act as the master devices.

[0091] The third GUI synchronization setting B3 also places the remote monitoring system in a master-slave operation mode, except that this time the remote display devices 7A to 7D act as the master and the bedside or medical device monitors 4A to 4C act as slaves. Optionally, in other embodiments where the independent operation mode is the default operation mode of the system, the third GUI synchronization setting B3 can place the remote monitoring system in a semi-independent operation mode, in which the remote display devices 7A to 7D act as the master devices.

[0092] The fourth GUI synchronization setting B4 places the remote monitoring system in the above-mentioned dual semi-independent operation mode, that is, the medical devices 3A to 3C and the remote display devices 7A to 7D both act as the main devices in the semi-independent operation mode.

[0093] The press button B5 for instant GUI synchronization is used to instantly transmit the GUI view of medical devices 3A to 3C to the GUI of remote display devices 7A to 7D, while maintaining the independent operation mode of the remote monitoring system, so that two clinicians can immediately change the GUI view of their respective devices after synchronization.

[0094] The press button B6 for instant GUI synchronization is used to instantly transmit the GUI view of remote display devices 7A to 7D to the GUI of medical devices 3A to 3C, while maintaining the independent operation mode of the remote monitoring system, so that two clinicians can immediately change the GUI view of their respective devices after synchronization.

[0095] Pressing any of buttons B2 through B6 constitutes a user input indicating a desire to synchronize the GUIs of medical devices 3A through 3C and the GUIs of remote display devices 7A through 7D. The remote monitoring system can be configured to perform GUI synchronization directly in response to detecting a button press. However, preferably, the system is configured to interpret a button press as a GUI synchronization request from the user pressing the button (i.e., a bedside clinician or a remote clinician), and prompt another user to acknowledge or accept GUI synchronization before performing synchronization. In one example (not shown in the figures), the system may display an accept button along with information indicating the type of GUI synchronization requested on another user's GUI, and perform GUI synchronization in response to detecting a press of the accept button. As described above... Figure 3 Understood, the type of GUI synchronization can therefore be any type of GUI synchronization selected from the following groups:

[0096] - In master-slave mode, the bedside device acts as the master and the remote device as the slave device for GUI synchronization (button B2).

[0097] - In semi-independent mode, the bedside serves as the host for GUI synchronization.

[0098] - In master-slave mode, the remote device is the master and the bedside device is the slave device (button B3) for GUI synchronization.

[0099] - GUI synchronization in dual semi-independent mode (button B4)

[0100] - Including instantaneous transmission of the bedside GUI view for GUI synchronization (button B5).

[0101] - This includes GUI synchronization for instantaneous transmission of remote GUI views (button B6).

[0102] The remote monitoring system is preferably configured to indicate the current state of GUI synchronization settings on the GUI of medical devices 3A to 3C and / or remote display devices 7A to 7D. The current state of GUI synchronization settings can be indicated, for example, by a GUI synchronization indicator displayed in all GUI views (e.g., in the status bar displayed in all GUI views), or can be accessed via the GUI's settings menu. Similarly, the GUI synchronization window 20 for adjusting GUI synchronization settings can be accessed, for example, by clicking the GUI synchronization indicator or by clicking GUI synchronization settings in the settings menu.

[0103] Still referencing Figure 1 Remote monitoring system in China Figures 4A to 4D The diagram schematically illustrates the GUI views (left column) displayed on monitors 4A to 4C of medical devices 3A to 3C and the GUI views (right column) displayed on remote display devices 7A to 7D for some different GUI synchronization settings.

[0104] exist Figure 4A In the middle, the remote monitoring system operates in the default standalone mode, and can also be accessed via... Figure 3 Button B1 is manually selected. This is indicated by GUI synchronization indicator 22, which indicates that synchronization is not currently being performed between the GUI views of medical devices 3A to 3C and the GUI views of remote display devices 7A to 7D. GUI synchronization indicator 22 is displayed in both the current GUI view 'A' of medical device monitors 4A to 4C and the current view 'B' of remote display devices 7A to 7D.

[0105] exist Figure 4B In this system, the remote monitoring system operates in a master-slave mode, where it can be accessed via... Figure 3 Selected by button B2, medical device monitors 4A to 4C act as the master, while remote display devices 7A to 7D act as slaves.

[0106] exist Figure 4C In this system, the remote monitoring system operates in a master-slave mode, where it can be accessed via... Figure 3The remote display devices 7A to 7D, selected by button B3, act as the master, while the medical device monitors 4A to 4C act as slaves.

[0107] exist Figure 4D In this system, the remote monitoring system operates in a dual semi-independent mode, such as via... Figure 3 The button B4 in the middle is selected.

[0108] It should be noted that multiple remote display devices 7A to 7D can be used to remotely monitor the operation of the same patient 1 and the same medical device (e.g., mechanical ventilator 3A providing ventilation therapy to patient 1). In this case, it is conceivable that multiple remote display devices 7A to 7D can use the same or different GUI synchronization settings. For example, the remote monitoring system can be configured so that each remote clinician can access the system via a GUI synchronization window (e.g., Figure 3 The GUI synchronization window shown in the diagram allows the user to set their own GUI synchronization settings, which can be accessed via the GUI of the respective remote display devices 7A to 7D. The server 13 of the remote monitoring system can then keep track of the GUI synchronization settings of the different remote display devices 7A to 7D and implement GUI synchronization between a single medical device and multiple remote display devices according to the GUI synchronization settings of the respective remote display devices.

[0109] Although the remote monitoring system has been described above with reference to an embodiment incorporating a server 13 for receiving, processing, and forwarding patient data acquired at five patient sites to remote display devices 7A to 7D, it should be understood that the principles of this disclosure can also be used in remote monitoring systems without such a server. For example, as described by Figure 1 As shown by the dashed arrow 33, patient data obtained at the patient site at point 5 can be directly transmitted to remote display devices 7A to 7D via transmission modules 9A to 9C at the patient site at point 5.

[0110] Figure 5 This illustrates a system for remotely monitoring patients located at the patient's field (e.g., Figure 1 The flowchart illustrates an exemplary implementation of a method executed in and through the remote monitoring system shown. This method is a computer-implemented method executed by the remote monitoring system when a computer program is executed by one or more processors of the system. For example, the method may be executed by the system when a computer program stored on data storage medium 14 of server 13 is executed, or when the computer program is executed by at least one processor 10 of the server.

[0111] In the first step S1, the remote monitoring system operates in a first operating mode, wherein the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D are configured to display different GUI views on the medical devices 3A to 3C and the remote display devices 7A to 7D. As discussed above, this operating mode can be a standalone operating mode or a semi-standalone operating mode.

[0112] In the second step S2, the system detects a GUI synchronization initiation event occurring at the medical devices 3A to 3C or the remote display devices 7A to 7D. As discussed above, the GUI synchronization initiation event may be, for example, a user input indicating a desired GUI synchronization, a change in the GUI view of one of the medical devices 3A to 3C or the remote display devices 7A to 7D acting as the master device in semi-independent operation mode, a change in the operating settings of the medical device, a change in alarm status, or a change in measurement values ​​obtained by sensors of the medical devices 3A to 3C.

[0113] In the third step S3, in response to the detection of a GUI synchronization initiation event, the GUIs of medical devices 3A to 3C and remote display devices 7A to 7D are synchronized at least temporarily by displaying a common GUI view on the GUIs of medical devices 3A to 3C and the GUIs of remote display devices 7A to 7D.

[0114] As any person skilled in the art will understand from the foregoing description, the proposed principle for GUI synchronization in remote patient monitoring can be implemented in many different ways. The principle is not limited to any particular type of network architecture or topology and can be modified and varied within the scope of the appended claims.

Claims

1. A system for remotely monitoring a patient (1) located at a patient site (5), the system being configured to: display patient data obtained by the medical devices (3A to 3C) at the same location as the patient (1) on a graphical user interface (GUI) of the medical devices (3A to 3C), and transmit the patient data to a remote display device (7A to 7D) for display on the GUI of the remote display device, wherein, The system is configured to operate in a first operating mode, in which the GUI of the medical devices (3A to 3C) and the GUI of the remote display devices (7A to 7D) are configured to simultaneously display different GUI views on the medical devices (3A to 3C) and the remote display devices (7A to 7D) for presenting patient data obtained by the medical devices (3A to 3C). When operating in the first operating mode, the system is configured to: detect a GUI synchronization initiation event occurring at the medical device (3A to 3C) or the remote display device (7A to 7D), and in response to detecting the GUI synchronization initiation event, synchronize the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) at least temporarily by displaying a common GUI view on the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D).

2. The system according to claim 1, wherein, The GUI synchronization initiation event is a user input expected by the user that instructs the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) to synchronize, the user input being input to the system via one of the medical device (3A to 3C) and the remote display device (7A to 7D).

3. The system according to claim 2, wherein, The user input indication is an approval of the GUI synchronization request input into the system via the other device among the medical devices (3A to 3C) and the remote display devices (7A to 7D) in response to a GUI synchronization request from one of the medical devices (3A to 3C) and the remote display devices (7A to 7D).

4. The system according to claim 1, wherein, The GUI synchronization initiation event is a change in the GUI view of the medical device (3A to 3C) or the remote display device (7A to 7D).

5. The system according to claim 1, wherein, The GUI synchronous event is a change in the operation settings of the medical device.

6. The system according to any one of the preceding claims, wherein, The system is configured to temporarily synchronize the GUI when a GUI synchronization initiation event is detected, thereby allowing the GUI views of the medical device (3A to 3C) and the remote display device (7A to 7D) to be different thereafter.

7. The system according to any one of claims 1 to 5, wherein, The system is configured to: enter a master-slave operation mode for at least a certain period of time after detecting the GUI synchronization initiation event; and in the master-slave operation mode, prevent changes to the GUI view of one of the medical devices (3A to 3C) and the remote display devices (7A to 7D) that acts as a slave in the master-slave operation mode; and in response to a change in the GUI view of the other device that acts as a master in the master-slave operation mode, resynchronize the GUIs of the medical devices (3A to 3C) and the remote display devices (7A to 7D).

8. The system according to any one of claims 1 to 5, wherein, The system is configured to: enter a dual semi-independent operation mode for at least a certain period of time after detecting the GUI synchronization initiation event, and in the dual semi-independent operation mode, in response to a change in the GUI view of either the medical device (3A to 3C) or the remote display device (7A to 7D), resynchronize the GUIs of the medical device (3A to 3C) and the remote display device (7A to 7D).

9. The system according to any one of the preceding claims, wherein, The public GUI view is the current GUI view of the medical device (3A to 3C) or the remote display device (7A to 7D) when the GUI synchronization initiation event is detected.

10. A method in a system for remotely monitoring a patient (1) located at a patient site (5), wherein, The system is configured to: display patient data obtained by the medical devices (3A to 3C) at the same location as the patient (1) on a graphical user interface (GUI), and transmit the patient data to a remote display device (7A to 7D) for display on the GUI of the remote display device, the method comprising: - The system is operated in a first operating mode (S1), in which the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) are configured to enable the simultaneous display of different GUI views on the medical device (3A to 3C) and the remote display device (7A to 7D) for presenting patient data obtained by the medical device (3A to 3C); - When operating in the first operating mode, detect (S2) a GUI synchronization initiation event occurring at the medical device (3A to 3C) or the remote display device (7A to 7D), and - In response to the detection of the GUI synchronization initiation event, the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) are synchronized at least temporarily by displaying a common GUI view on the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) (S3).

11. The method according to claim 10, wherein, The GUI synchronization initiation event is a user input expected by the user that instructs the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) to synchronize, the user input being input to the system via one of the medical device (3A to 3C) and the remote display device (7A to 7D).

12. The method according to claim 11, wherein, The user input indication is an approval of the GUI synchronization request input into the system via the other device among the medical devices (3A to 3C) and the remote display devices (7A to 7D) in response to a GUI synchronization request from one of the medical devices (3A to 3C) and the remote display devices (7A to 7D).

13. The method according to claim 10, wherein, The GUI synchronization initiation event is a change in the GUI view of the medical device (3A to 3C) or the remote display device (7A to 7D).

14. The method of claim 10, wherein, The GUI synchronous event is a change in the operation settings of the medical device.

15. The method according to any one of claims 10 to 14, comprising the following steps: When the GUI synchronization initiation event is detected, the GUI is temporarily synchronized, thereafter allowing the GUI views of the medical device (3A to 3C) and the remote display device (7A to 7D) to be different.

16. The method according to any one of claims 10 to 14, comprising the following steps: After detecting the GUI synchronization initiation event, the system is operated in master-slave mode for at least a certain period of time. In master-slave mode, changes to the GUI view of one of the medical devices (3A to 3C) and the remote display devices (7A to 7D) that acts as a slave in master-slave mode are prevented. In response to changes to the GUI view of the other device that acts as a master in master-slave mode, the GUIs of the medical devices (3A to 3C) and the remote display devices (7A to 7D) are resynchronized.

17. The method according to any one of claims 10 to 14, comprising the following steps: After detecting the GUI synchronization initiation event, the system is operated in a dual semi-independent operation mode for at least a certain period of time, and in the dual semi-independent operation mode, in response to a change in the GUI view of either the medical device (3A to 3C) or the remote display device (7A to 7D), the GUI of the medical device (3A to 3C) and the GUI of the remote display device (7A to 7D) are resynchronized.

18. The method according to any one of claims 10 to 17, wherein, The public GUI view is the current GUI view of the medical device (3A to 3C) or the remote display device (7A to 7D) when the GUI synchronization initiation event is detected.

19. A computer program for a system of remotely monitoring a patient (1) located at a patient site (5), wherein, The system is configured to: display patient data obtained by the medical device (3A to 3C) on a graphical user interface (GUI) of a medical device (3A to 3C) located at the same position as the patient (1), and transmit the patient data to a remote display device (7A to 7D) to display the patient data on the GUI of the remote display device, wherein the computer program includes computer-readable instructions that, when executed by at least one processor (10) of the system, cause the system to perform the method according to any one of claims 10 to 18.

Images