GUI synchronization of medical device and remote monitoring device

Abstract

The disclosure relates to a system for remote monitoring of a patient (1) located at a patient site (5). The system is configured to display patient data obtained by a medical device (3A-C) co-located with the patient (1) on a graphical user interface, GUI, of the medical device (3A-C), and to communicate the patient data to a remote display device (7A-D) for display of the patient data on a GUI of the remote display device. The system is configured to operate in a first mode of operation in which the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-D) are configured to enable simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device (3A-C) on the medical device (3A-C) and the remote display device (7A-D). In this first mode of operation, the system is configured to detect a GUI synch initiation event occurring at the medical device (3A-C) or the remote display device (7A-7D), and to synchronize the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-7D) by causing a common GUI view to be displayed on both GUIs, in response to detection of the GUI synch initiation event.

Description

[0001] GUI Synchronization of Medical Device and Remote Monitoring Device

[0002] Technical field

[0003] The present disclosure pertains to the field of remote display of patient data including data related to a patient and / or a medical device connected to the patient. In particular, the present disclosure relates to a system, method and computer program for remote monitoring of a patient, as defined in the introductory parts of the appended independent claims.

[0004] Background art

[0005] Remote patient monitoring (RPM) involves collection of patient data by means of an electronic medical device, and transmission of the patient data from the medical device to a remote healthcare provider who can then analyse the data and track the health of the patient remotely. Real-time RPM is a subset of RPM where the patient data is transmitted to the healthcare provider in real-time, so that the healthcare provider can monitor the patient’s current health status.

[0006] Medical devices for collecting the patient data in a real-time RPM system may, for example, include wearables, 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 rates.

[0007] Examples of medical treatment devices that may offer remote access to patient data obtained during ongoing treatment include mechanical ventilators. Today, many leading ventilator manufactures offer products that can be used to give a remote clinician access to patient data obtained by the ventilator during ongoing mechanical ventilation via a remote display or monitor. Such patient data may relate both to the patient and to the operation of the ventilator. A few solutions even enables remote control of the ventilator via the remote display or monitor.

[0008] This disclosure addresses issues pertaining to remote real-time monitoring of patients who are connected to a medical device further offering bedside monitoring of the patient via a graphical user interface (GUI) of the medical device. The medical device may, e.g., be a bedside medical monitor or a medical treatment device having an integrated monitor, such as a mechanical ventilator or a heart-lung machine.

[0009] In real-time monitoring of a patient via both a bedside monitor (i.e., the monitor of the medical device) and a remote monitor, it is often advantageous if the graphical user interface (GUI) of the remote monitor is a replica of the GUI of the bedside monitor since this makes a remote clinician, who is typically an experienced clinician who is familiar with the GUI of the bedside monitor, capable of navigating the GUI of the remote monitor without specific training. Another advantage is that a bedside clinician and a remote clinician can be presented with the same GUI views, which facilitates collaboration between the bedside clinician and the remote clinician, e.g., in patient diagnosis and determination of suitable adjustments of medical device settings.

[0010] To ensure that the bedside clinician and the remote clinician are presented with the same or corresponding GUI views, the bedside monitor and the remote monitor are sometimes operated in a master-slave mode in which the remote monitor is configured to always reflect the GUI view currently being displayed on the bedside monitor. This way, changes to the GUI view of the bedside monitor, initiated by the bedside clinician, are immediately reflected on the GUI of the remote monitor.

[0011] However, the master-slave configuration of the bedside monitor and the remote monitor limits the possibility of the remote clinician to be presented with the patient data needed in order for the remote clinician to better assess the physiological status of the patient and / or the operation of the medical device. Therefore, in order to improve patient diagnosis and / or medical device operation during remote monitoring of a patient, there is a need for improvement within the field.

[0012] Summary

[0013] It is an object of the present disclosure to mitigate, alleviate or eliminate one or more of the above-identified deficiencies and disadvantages in the prior art.

[0014] In particular, it is an object of the present disclosure to provide means for facilitating collaboration between a bedside clinician monitoring a patient via a bedside monitor of a medical device, and a remote clinician monitoring the patient via a remote monitor or display device.

[0015] Ultimately, it is an object of the present disclosure to improve patient safety through improved remote patient monitoring.

[0016] According to a first aspect of the present disclosure there is provided a system for remote monitoring of a patient located at a patient site. The system is configured to display patient data obtained by a medical device co-located with the patient at the patient site, on a graphical user interface (GUI) of the medical device. The system is further configured to communicate the patient data to a remote display device for display of the patient data on a GUI of the remote display device. The system is configured to operate in a first mode of operation in which the GUI of the medical device and the GUI of the remote display device are configured to enable simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device on the medical device and the remote display device. When operated in this first mode of operation, the system is configured to detect a GUI synch initiation event occurring at the medical device or the remote display device, and to at least temporarily synchronize the GUI of the medical device and the GUI of the remote display device by causing a common GUI view to be displayed on both GUIs, in response to detection of the GUI synch initiation event.

[0017] In the first mode of operation, the remote monitoring system enables the remote clinician to select the GUI view and hence the patient data presentation of her interest, independent of the GUI view selected by the other clinician. However, when a GUI synch initiation event is detected, the common GUI view is displayed to both clinicians, thus forcing the clinicians to be presented with the same view, thereby minimizing the risk of misunderstandings and facilitating collaboration in patient diagnosis and / or adjustment of medical device settings.

[0018] This means that, in the first mode of operation, the GUI of the medical device and the GUI of the remote display device are configured to be operated in a non-synchronized manner that enables simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device on the GUI of the medical device and the GUI of the remote display device.

[0019] That GUI views for presenting patient data obtained by the medical device are ‘mutually different’ herein means that the type of patient data displayed in each GUI view is different, or that the same patient data is presented in a different way (i.e. in a different format) in each GUI view. Likewise, that a common GUI view is displayed on both the GUI of the medical device and the GUI of the remote display device herein means that a GUI view presenting the same patient data in the same or substantially the same way (i.e., in the same or substantially the same format) is displayed on both GUIs.

[0020] The common GUI view may be a current GUI view of the medical device at the time of detection of the GUI synch initiation event, a current GUI view of the remote display device at the time of detection of the GUI synch initiation event, 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.

[0021] Preferably, the GUI of the remote display device is a replica of the GUI of the medical device, effectively making the remote display device serve as a digital twin of the GUI of the medical device. This brings about several advantages in terms of training of medical personnel, collaboration, patient diagnosis, treatment optimization, etc., as discussed above. According to some embodiments, the GUI synch initiation event is a user input indicating a desire of a user to synchronize the GUI of the medical device and the GUI of the remote display device, input to the system via one of the medical device and the remote display device. This gives the bedside clinician and the remote clinician the freedom of exploring and selecting the GUI views of their choice 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.

[0022] Upon reception of a request for GUI synchronization from the bedside clinician or the remote clinician, the system may be configured to seek approval from the other clinician before synchronizing the GUIs. Thus, according to some embodiments, the GUI synch initiation event that triggers GUI synchronization is a user input that indicates an approval of a request for GUI synchronization, input to the system via one of the medical device and the remote display device in response to a request for GUI synchronization from the other device. This is advantageous in that the common GUI view cannot override a current GUI view studied by a clinician without approval from the clinician.

[0023] According to some embodiments, the GUI synch initiation event is a change in a GUI view of the medical device or the remote display device. For example, the system may be configured to enable the remote clinician to change the GUI view of the remote display device independent of the GUI view of the medical devices as long as the GUI view of the medical device remains the same. However, as soon as the GUI view of the medical device is changed, the new GUI view of the medical device is transferred to the remote display device, thus overriding the current GUI view of the remote display device. This may be advantageous in scenarios where an experienced remote clinician is supporting a less experienced bedside clinician. The more experienced remote clinician may then move around freely between different GUI views on the remote display device while knowing that he or she will be made aware of any changes made to the GUI view of the medical device.

[0024] According to some embodiments, the GUI synch initiation event is a change in an operational setting of the medical device. This brings about the same advantages as discussed above, only in this case the current GUI view of the remote display device is not overridden by the GUI view of the medical device upon just any change in GUI view of the medical device, but only upon a change in an operational setting of the medical device. From the perspective of patient safety, a change in an operational parameter of the medical device is a more critical event than a change in a GUI view of the medical device. Thus, this feature may have the effect of lending the remote clinician more freedom in his choice of GUI view, while ensuring that the remote clinician is presented with the relevant GUI view in case of a change in an operational setting of the medical device. In cases where the operational setting is changed via the GUI of the medical device, this means that the GUI view in which the setting can be changed will be transferred to the remote display device, which in turn makes the remote clinician immediately aware of any changes in operational settings. Typically, patient data, including operational settings of the medical device, is always synchronized between the medical device and the remote display device. Nevertheless, if the remote clinician would happen to study a GUI view not presenting the operational setting in question, there might be a risk that the remote clinician does not perceive a change in the operational setting. This risk is hence effectively eliminated by causing the GUI view of the medical device to override the current view of the remote display device in response to a change in an operational setting of the medical device. The operational setting may, for example, be a setting relating to and affecting an ongoing treatment of the patient, provided by the medical device.

[0025] According to some embodiments, the GUI synch initiation event is a change in an alarm status of the medical device. This is advantageous in that the triggering of an alarm in the medical device may trigger a common GUI view, e.g. a GUI view presenting relevant alarm data, to be displayed on both the medical device and the remote display device.

[0026] According to some embodiments, the GUI synch initiation event is a change in a sensor- obtained measurement value, obtained by a sensor of the medical device. This is advantageous in that both the bedside clinician and the remote clinician can be made aware of an unexpected change in a measurement value by displaying a common GUI view presenting relevant measurement data on both the medical device and the remote display device.

[0027] According to some embodiments, the system is configured to temporarily synchronize the GUIs upon the detection of the GUI synch initiation event, whereafter the GUI views of the medical device and the remote display device are allowed to diverge. This is advantageous in that the bedside clinician and the remote clinician can be presented with the same GUI view when required or desired, whereafter they can continue to study the GUI view of their choice, independent of each other.

[0028] According to some embodiments, the system is configured to enter into a master-slave mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the master-slave mode of operation, prevent changes to the GUI view of one of the medical device and the remote display device acting as a slave in the masterslave mode of operation, and re-synchronize the GUIs of the medical device and the remote display device in response to a change in the GUI view of the other device acting as a master in the master-slave mode of operation. This is advantageous since it is often desired to present the same GUI views to the bedside clinician and the remote clinician for a period of time following the GUI synch initiation event. For example, if the GUI synchronization is requested by the bedside clinician 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 masterslave mode of operation ensures that any changes made to the GUI view of the medical device are reflected by the GUI view of the remote display device. This makes it possible for the bedside clinician to “bring the remote clinician along” when switching between different GUI views that may be helpful in the discussion. The system may be configured to maintain the master-slave mode of operation during a predetermined period of time, or until a request for reentering into the first mode of operation, or some other mode of operation, is received by the system via any of the medical device or the remote display device.

[0029] According to some embodiments, the system is configured to enter into a mode of operation which is herein referred to as a dual semi-independent mode of operation at least for a certain period of time following the detection of the GUI synch initiation event. In the dual semiindependent mode of operation, the system is configured to re-synchronize the GUIs of the medical device and the remote display device in response to a change in the GUI view of any one of the medical device and the remote display device. This means that both the bedside clinician and the remote clinician may change the GUI view of their device but any changes to the GUI view will be transferred to the other device, thus overriding the current GUI view studied by the other clinician. This is advantageous in that it allows the bedside clinician and the remote clinician to take turns on showing each other relevant GUI views for a period of time following the GUI synch initiation event. The system may be configured to maintain the dual semi-independent mode of operation during a predetermined period of time, or until a request for re-entering into the independent mode of operation, or some other mode of operation, is received by the system via any of the medical device or the remote display device.

[0030] According to some embodiments, the system comprises a server configured to receive the patient data obtained by the medical device and communicate the patient data to the remote display device for display as real-time patient data. In other embodiments, the obtained patient data may be transmitted directly to the remote display device by the medical device or any other device at the patient site to which the medical device is communicatively connectable. However, using an intermediate server that receives the obtained patient data and communicates the patient data to the remote display device brings about several advantages in terms of system architecture and functionality. For example, it allows patient data to be buffered and / or saved centrally in the server, and facilitates access to patient data from different remote display devices. According to some embodiments, the server is configured to provide the functionality described herein via a web application that is stored on the server and accessible by the remote display device via a web browser of the remote display device. This allows any web browser-equipped display device to serve as a remote display device for remote monitoring of patients, in accordance with the teachings of the present disclosure.

[0031] The medical device of the present disclosure may be any type of electronic medical device. In some embodiments, the medical device is a medical device providing critical care treatment to the patient at the patient site, such as a mechanical ventilator or anaesthesia machine providing respiratory treatment to the patient, or an extracorporeal membrane oxygenation (ECMO) device providing ECMO treatment to the patient. In other embodiments, the medical device may be a bedside patient monitor for bedside monitoring of a physiological status of the patient, or a wearable medical device configured to be worn on the body of the patient. The medical device comprises a monitor or a display on which the GUI of the medical device is displayed.

[0032] According to a second aspect of the present disclosure there is provided a method in a system for remote monitoring of a patient located at a patient site, wherein the system is configured to display patient data obtained by a medical device co-located with the patient on a GUI of the medical device, and to communicate the patient data to a remote display device for display of the patient data on a GUI of the remote display device. The method comprises the steps of operating the system in a first mode of operation in which the GUI of the medical device and the GUI of the remote display device are configured to enable simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device on the medical device and the remote display device. The method further comprises the steps of, detecting, in the first mode of operation, a GUI synch initiation event occurring at the medical device or the remote display device, and at least temporarily synchronizing the GUIs of the medical device and the remote display device by causing a common GUI view to be displayed on both GUIs, in response to detection of the GUI synch initiation event.

[0033] According to some embodiments, the GUI synch initiation event is a user input indicating a desire of a user to synchronize the GUI of the medical device and the GUI of the remote display device, input to the system via one of the medical device (3A-C) and the remote display device.

[0034] According to some embodiments, the user input indicates an approval of a request for GUI synchronization, input to the system via one of the medical device and the remote display device in response to a request for GUI synchronization from the other device. According to some embodiments, the GUI synch initiation event is a change in a GUI view of the medical device or the remote display device.

[0035] According to some embodiments, the GUI synch initiation event is a change in an operational setting of the medical device.

[0036] According to some embodiments, the method comprises a step of temporarily synchronizing the GUIs upon the detection of the GUI synch initiation event, whereafter the GUI views of the medical device and the remote display device are allowed to diverge.

[0037] According to some embodiments, the method comprises a step of operating the system in a master-slave mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the master-slave mode of operation, preventing changes to the GUI view of one of the medical device and the remote display device acting as a slave in the master-slave mode of operation, and re-synchronizing the GUIs of the medical device and the remote display device in response to a change in the GUI view of the other device acting as a master in the master-slave mode of operation.

[0038] According to some embodiments, the method comprises a step of operating the system in a dual semi-independent mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the dual semi-independent mode of operation, re-synchronizing the GUI of the medical device and the GUI of the remote display device in response to a change in the GUI view of any of the medical and the remote display device.

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

[0040] The method is a computer-implemented method that is performed by the system upon execution of a computer program by one or more processors of the system.

[0041] Thus, according to a third aspect of the present disclosure, there is provided a computer program for a system for remote monitoring of a patient located at a patient site, wherein the system is configured to display patient data obtained by a medical device co-located with the patient on a GUI of the medical device, and to communicate the patient data to a remote display device for display of the patient data on a GUI of the remote display device. The computer program comprises computer-readable instructions which, when executed by at least one processor of the system, causes the system to perform the above-described method.

[0042] According to some embodiments, the computer program is a web application residing in the above-mentioned server, accessible by the remote display device via a web browser of the remote display device.

[0043] In other embodiments, the principles of the present disclosure may be implemented by means of a distributed computer program, such as a client-server application. In this scenario, the method may be performed upon execution of a client application for remote patient monitoring residing in the remote display device, which client application is configured to communicate with a server application residing in the server.

[0044] In yet other embodiments, the method may be performed upon execution of first computer program component residing in the remote display device, which first computer program communicates with a second computer program component residing in the medical device, whereby the patient data obtained by the medical device may be transmitted directly to the remote display device, without any intermediate server.

[0045] According to a fourth aspect of the present disclosure there is provided at computer program product comprising a data storage medium, such as a non-transitory memory hardware device, storing the above-mentioned computer program.

[0046] Effects and features of the second, third and fourth aspects of the present disclosure are to a large extent analogous to those described above in connection with the first aspect.

[0047] Other effects and advantages of the system, method and computer program of the present disclosure will become apparent from the detailed description following hereinafter

[0048] Brief descriptions of the drawings

[0049] The above objects, as well as additional objects, features and advantages of the present disclosure, will be more fully appreciated by reference to the following illustrative and nonlimiting detailed description of example embodiments of the present disclosure, when taken in conjunction with the accompanying drawings.

[0050] Figure 1 illustrates a system for remote monitoring of a patient located at a patient site, according to an exemplary embodiment of the present disclosure.

[0051] Figure 2 illustrates an example of a view of a graphical user interface (GUI) presenting realtime patient data from the patient site on a display of a remote display device. Figure 3 illustrates a GUI synchronization window for adjusting a GUI synchronization setting of the remote monitoring system illustrated in Figure 1.

[0052] Figures 4A-4D illustrate schematically GUI views of the medical device and the remote display device for some different GUI synchronization settings.

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

[0054] Detailed description

[0055] Figure 1 illustrates an exemplary embodiment of a system for remote medical monitoring of a patient 1 located at a patient site 5 and connected to a medical device 3A-C that is colocated with the patient 1 at the patient site 5. The medical device 3A-C is configured to obtain patient data related to the patient 1 and / or an ongoing medical treatment of the patient. Patient data relating to the patient 1 may comprise any type of data that is indicative of a physiological state or status of the patient. Patient data relating to an ongoing medical treatment of the patient may comprise medical device settings, data indicative of the operation of the medical device, data indicative of a medical effect of the ongoing treatment, etc. Patient data should in this context hence be interpreted broadly, as including any type of data related to the patient 1 or the medical device 3A-C to which the patient is connected.

[0056] The system is a remote patient monitoring (RPM) system for near real-time monitoring of the patient 5 from a location that is remote from the patient site 5. The system may hereinafter sometimes be referred to as a real-time RPM system.

[0057] The device 3A-C may be any type of electronic medical device configured to obtain patient data at the patient site and facilitate communication of the patient data from the patient site to a remote display device 7A-D.

[0058] In some embodiments, the medical device 3A-C is a critical care treatment device, i.e. a medical treatment device configured to provide critical care treatment to the patient 1. For example, the medical device may be a breathing apparatus for providing respiratory treatment to the patient 1 , such as a mechanical ventilator 3A or an anaesthesia machine. According to another example, the medical device is a heart-lung machine for oxygenation of the blood of the patient 1, such as an extracorporeal membrane oxygenation (ECMO) device 3B for providing ECMO treatment to the patient.

[0059] In other embodiments, the medical device 3A-C may be a bedside patient monitoring system 3C that is co-located with the patient at the patient site 5. The medical device 3A-C is typically configured to obtain the patient data using one or more sensors for measuring patient parameters or internal states and / or settings of the medical device.

[0060] In embodiments where the medical device is a breathing apparatus, such as a mechanical ventilator 3A, non-limiting examples of patient data that may be obtained by the medical device include an airway pressure (Paw) of the patient, a positive end-expiratory pressure (PEEP) applied to the airways of the patient, a respiratory rate (RR) of the patient, a minute ventilation (MV) of the patient, a tidal volume (VT) of breathing gas inspired and / or expired by the patient, an inspiratory to expiratory ratio (l:E) of the patient, an oxygen concentration of the breathing gas delivered to the patient, a carbon dioxide concentration of expiration gas exhaled by the patient, a dynamic compliance (Cdyn) of the patient, an electromyographic (EMG) signal of the patient, a heart rate, a mean arterial blood pressure (MAP), a body temperature, a blood oxygen saturation level and a central venous pressure (CVP).

[0061] In embodiments where the medical device is a heart-lung machine, such as an ECMO device 3B, non-limiting examples of patient data that may be obtained by the medical device include a flow rate of sweep gas supplied to an oxygenator of the ECMO device, pre- and / or post oxygenator oxygen and / or carbon dioxide concentrations, a pressure drop over the oxygenator, a gas transfer resistance of the oxygenator, blood parameters determined using a blood gas analyser (BGA) of the ECMO device, a venous and / or arterial pressure of the patient, a heart rate, a body temperature, a blood oxygen saturation level and CVP.

[0062] In embodiments where the medical device is a bedside patient monitoring system 3C, nonlimiting examples of patient data that may be obtained by the medical device include a heart rate, ECG signals, a respiratory rate, a blood pressure, a body temperature and a blood oxygen saturation level.

[0063] The medical device 3A-C comprises a monitor 4A-4C for presenting the obtained patient data to the patient 1 and / or a bedside clinician via a graphical user interface (GUI) of the medical device. The GUI of the medical device 3A-C may be navigated and manipulated by the bedside clinician and / or the patient in order to present relevant patient data, change medical device settings, set alarms, etc.

[0064] The system is further configured to communicate the patient data obtained by the medical device 3A-C to the remote display device 7A-D. In the illustrated embodiment, the patient data is transmitted from the patient site 5 by a transmission module 9A-C of the medical device 3A- C. The transmission module 9A-C may be integrated in the medical device 3A-C or it may be an add-on transmission module that can be connected to a communication port of the medical device to provide the medical device with network connectivity capabilities. The transmission module 9A-C may be configured to transmit the patient data to a system server 13. The server 13 is configured to receive and process the patient data and to communicate the patient data to the remote display device 7A-D.

[0065] The transmission module 9A-C is typically but not necessarily configured to communicate the patient data to the server 13 wirelessly, e.g. via a wireless network. The network used for transmission of patient data from the transmission module 9A-C to the server 13 may be the Internet or a healthcare provider IT network, such as a local area network (LAN) of a health care facility or a private wide area network (WAN) of a health care organization. The transmission module 9A-C may be configured to use any available wireless communication technology, such as a Wi-Fi technology, a 4G or 5G mobile network technology, or the like. It should also be noted that the present disclosure is not limited to wireless communication and that the principles for remote monitoring of a patient described herein are applicable also when patient data is communicated from the patient site 5 to the remote display device 7A-D partly or completely via a wired connection.

[0066] The server 13 may be a web server connected to the Internet in order to allow remote monitoring of the patient 1 via any type of Internet-connected display device. The server 13 comprises at least one processor 10 and may be configured to provide the functionality described herein upon execution by the at least one processor of a computer program stored in a data storage medium 14 of the server 13, such as a non-transitory memory hardware device of the server 13.

[0067] In the illustrated example, the computer program stored in the server 13 is a web application that can be accessed via a web browser stored in a data storage medium 12A-C of the remote display device 7A-D, such as a non-transitory memory hardware device of the remote display device. The patient data is hence received from the transmission module 9A-C by the server 13, and communicated to the display device 7A-D via the web application stored in the server 13. Of course, in other embodiments, several network nodes may be involved in the communication of the patient data from the patient site 5 to the remote display device 7A-D. For example, the system may comprise a web server for receiving and / or storing the patient data from the patient site 5, and a web application server for hosting and running the web application that communicates the patient data to the remote display device 7A-D.

[0068] The system is configured to communicate the patient data obtained by the medical device 3A- C at the patient site 5 to the remote display device 7A-D in near real time, and to display the patient data as real-time patient data on a display 11 A-D of the remote display device 7A-D. Figure 2 illustrates an exemplary view 16 of a GUI 15 of the remote display device 7A-D, which GUI is caused to be displayed on the display 11 A-D of the remote display device 7A-D by the web application residing in the server 13, when run by the web browser of the remote display device. Strictly speaking, the GUI 15 is rather the GUI of the web application residing in the server 13 than a GUI of the actual remote display device 7A-D. However, throughout this disclosure, a GUI of the remote display device should be interpreted as any GUI that is presented on the display 11 A-D of the remote display device 7A-D.

[0069] The GUI 15 of the remote display device 7A-D may be a replica of the GUI of the medical device 3A-C. That the GUI 15 of the remote display device 7A-D is a replica of the GUI of the medical device means that at least some views of the GUI of the remote display device are substantially identical to corresponding GUI views of the medical device. A GUI view is typically defined as a specific visual representation or arrangement of information and elements on a screen. That corresponding GUI views are substantially identical means, in the context of the present disclosure, that patient data presented in the corresponding views are presented in substantially the same manner, e.g., in terms of placement, font, size, colour, etc. Preferably, in corresponding GUI views, most menus, controls and other GUI objects are also presented in substantially the same manner. Ideally, substantially all patient data and substantially all GUI objects of corresponding GUI views are presented in substantially the same manner, making the remote clinician perceive the GUI view of the remote display device 7A-D as the corresponding GUI view of the medical device 3A-C.

[0070] Preferably, the GUI 15 of the remote display device 7A-D is configured to selectively present GUI views corresponding to most and preferably all GUI views available via the GUI of the medical device 3A-C, effectively making the remote display device 7A-D look and to most extent behave like the monitor 4A-C or the medical device 3A-C. This way, the GUI of the remote display device 7A-D may, in a sense, be turned into a “digital twin” of the GUI of the medical device 3A-C by running the web application provided by the system server 13. In the illustrated example, with simultaneous reference to Figure 1, the GUI 15 of the remote display device is a replica of the GUI of the mechanical ventilator 3A, presented on the ventilator monitor 4A. The exemplary GUI view 16 is real-time view comprising 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 the medical device and that changes to the operation of the medical device 3A-C cannot be effectuated via the GUI 15 of the remote display device 7A-D. The digital twin of the medical device GUI, displayed on the remote display device 7A-D, only serves the purpose of presenting patient data to the remote clinician in order for the remote clinician to assess the physiological status of the patient and / or an ongoing treatment provided by the medical device 3A-C.

[0072] With reference again made to Figure 1 , the remote monitoring system is configured to operate in a first mode of operation in which the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D are configurable to enable simultaneous display of mutually different GUI views on the monitor 3A-C of the medical device and the monitor 11 A-D of the remote display device. In this first mode of operation, the remote monitoring system hence enables a remote clinician co-located with the remote display device 7A-D to select the GUI view and hence the patient data presentation of his or her interest, independent of which GUI view is currently being studied by the bedside clinician.

[0073] To facilitate collaboration between the bedside clinician and the remote clinician, and to avoid misunderstandings due to differences in patient data presentation, the remote monitoring system is configured to at least temporarily cause a common GUI view to be simultaneously presented on both the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D in response to detection of certain events, herein referred to as GUI synch initiation events. Thus, when a GUI synch initiation event is detected by the remote monitoring system, the GUIs of the medical device 3A-C and the remote display device 7A-D are at least temporarily synchronized to display a same or common GUI view to the bedside clinician and the remote clinician. Also, to further facilitate collaboration between the bedside clinician and the remote clinician, the medical device 3A-C and the remote display device 7A-D may comprise functionality for enabling the bedside clinician and the remote clinician to communicate with each other via the medical device and the remote display device. Such functionality may, e.g., include functionality for voice, text, chat and / or video communication.

[0074] The common GUI view may be a current GUI view of the medical device 3A-C at the time of detection of the GUI synch initiation event, a current GUI view of the remote display device 7A- D at the time of detection of the GUI synch initiation event, or even 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. The remote monitoring system may be configured to select which GUI view should be displayed as the common GUI view in dependence of the type and the source of the GUI synch initiation event.

[0075] In some embodiments, the first mode of operation is an independent mode of operation in which the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D are independently configurable to enable the bedside clinician and the remote clinician to select the GUI view and hence the patient data presentation of his or her interest, independent of the current GUI view and any changes made to the current GUI view of the other device. The GUI synch initiation event may be a user input indicating a desire of a user to synchronize the GUI of the medical device and the GUI of the remote display device, input to the system via one of the medical device 3A-C and the remote display device 7A-D. This gives the bedside clinician and the remote clinician the freedom of exploring and selecting the GUI views of their choice while still ensuring that they can be presented with the same GUI view as the other clinician by manually requesting GUI synchronization.

[0076] Upon reception of a request for GUI synchronization from the bedside clinician or the remote clinician, the system may be configured to seek approval from the other clinician before synchronizing the GUIs. For example, the system may be configured to prompt the other clinician to approve a request for GUI synchronization by causing a confirmation or acceptance button to be displayed on the GUI of the device of the other clinician and to synchronize the GUIs only if the button is pressed. Thus, according to some embodiments, the GUI synch initiation event that triggers GUI synchronization is a user input that indicates an approval of a request for GUI synchronization, input to the system via one of the medical device 3A-C and the remote display device 7A-D in response to a request for GUI synchronization from the other device. This is advantageous in that the common GUI view cannot override a current GUI view studied by a clinician without approval from that clinician.

[0077] In some embodiments, the first mode of operation may be a semi-independent mode of operation. Also in the semi-independent mode of operation, the GUI of the medical device 3A- C and the GUI of the remote display device 7A-D are configurable to enable the bedside clinician and the remote clinician to select the GUI view of his or her interest, independent of the GUI view currently studied by the other clinician. However, in the semi-independent mode of operation, one of the devices acts as a principal device and any changes made to the GUI view of the principal device trigger synchronization of the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D, thus causing the changed GUI view of the principal device to be displayed on both devices.

[0078] For example, the remote monitoring system may be set up with the medical device 3A-C acting as a principal device, meaning that the remote clinician can move around freely between different GUI views of the remote display device 7A-D as long as the GUI view of the medical device 3A-C remains unchanged. However, as soon as the GUI view of the medical device 3A- C is changed, the new GUI view of the medical device is transferred to the remote display device 7A-D, thus overriding the current GUI view of the remote display device.

[0079] Thus, the semi-independent mode of operation is a mode of operation in which a change in a GUI view of the medical device 3A-C or the remote display device 7A-D (which ever acts as the principal device) constitutes a GUI synch initiation event that causes a common GUI view corresponding to the changed GUI view of the principal device to be displayed on both the medical device 3A-C and the remote display device 7A-D.

[0080] In some embodiments, the GUI synch initiation event is a critical event requiring increased vigilance from the clinicians. Non-limiting examples of such a critical event include a change in an operational setting of the medical device 3A-C, a change in an alarm status of the medical device 3A-C, and a change in a sensor-obtained measurement value, obtained by a sensor of the medical device 3A-C. In response to detection of the critical event, the remote monitoring system may be configured to display a common GUI view presenting data relating to the critical event on both the medical device 3A-C and the remote display device 7A-D.

[0081] The remote monitoring system may be configured to temporarily synchronize the GUI views of the medical device 3A-C and the remote display device 7A-D upon the detection of the GUI synch initiation event, whereafter the GUI views of the medical device and the remote display device are allowed to diverge again. In some embodiments, the GUI synchronization may be momentary, whereby the GUI views of the medical device 3A-C and the remote display device 7A-D are allowed to diverge immediately following the GUI synchronization. In this case, the remote monitoring system may be configured to remain in the first mode of operation after detection of the GUI synchronization event.

[0082] In other embodiments, the remote monitoring system is configured to switch from the first mode of operation to a second mode of operation, at least for a certain period of time, upon detection of the GUI synch initiation event. The second mode of operation is a synchronized mode of operation in which the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D are synchronized to always display the same GUI view. The synchronized mode of operation may be maintained during a predetermined period of time, or until a request for re-entering into the first mode of operation or another unsynchronized mode of operation is received by the system via any of the medical device 3A-C and the remote display device 7A- D. When switching from a synchronized mode of operation to an unsynchronized mode of operation, the GUI of the medical device 3A-C and / or the GUI of the remote display device 7A- D may be configured to maintain the current GUI view (i.e. , the GUI view corresponding to the common GUI view that was displayed on both GUIs at the time of switching from the synchronized mode of operation), or to switch to a default GUI view. Such a default GUI view may be different for the medical device 3A-C and the remote display device 7A-D.

[0083] Alternatively, the GUI of the medical device 3A-C and / or the GUI of the remote display device 7A-D may be configured to switch to a previous GUI view when going from the synchronized mode of operation to the unsynchronized mode of operation. The previous GUI view may, for example, be the GUI view displayed by the respective device before entering into the synchronized mode of operation.

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

[0085] In another example, the system may be configured to enter into a dual semi-independent mode of operation at least for a certain period of time following the detection of the GUI synch initiation event. A dual semi-independent mode of operation herein refers to a semiindependent mode of operation as described above, where both the medical device 3A-C and the remote display device 7A-D act as principal devices. This means that in the dual semiindependent mode of operation, both the bedside clinician and the remote clinician can select the GUI view of his or her choice, only not at the same time. A change to the GUI view made by any of the bedside clinician or the remote clinician will be reflected on the GUI of both the medical device 3A-C and the remote display device 7A-D.

[0086] An exemplary embodiment of an implementation of the proposed GUI synchronization functionality will now be described with reference to Figure 3 and Figures 4A-D.

[0087] Figure 3 illustrates a GUI synchronization window 20 for adjusting a GUI synchronization setting of the remote monitoring system illustrated in Figure 1. The GUI synchronization window 20 may be accessible via the GUI of any or both of the medical device 3A-C and the remote display device 7A-D.

[0088] According to this example, the GUI synchronization window 20 comprises four radio buttons B1-B4, corresponding to a respective GUI synchronization setting. Furthermore, the GUI synchronization window 20 comprises two press buttons B5-B6 for transfer of the current GUI view of the medical device monitor 4A-C to the remote display device 7A-D (button B5), and for transfer of the current GUI view of the remote display device 7A-D to the medical device monitor 4A-C (button B6).

[0089] The first GUI synchronization setting B1 is selected by default. This setting puts the remote monitoring system into the above mentioned independent mode of operation. In other embodiments, the default mode of operation of the system may be the above-described semiindependent mode of operation, e.g., with the medical device 3A-C acting as principal device.

[0090] The second GUI synchronization setting B2 puts the remote monitoring system into a masterslave mode of operation with the medical device monitor 4A-C acting as a master and the remote display device 7A-D acting as a slave. When a master-slave mode of operation is selected, the system is configured to first transfer the current GUI view of the master to the slave, and then continue to transfer all changes made to the GUI view of the master to the GUI of the slave. In this regard it should be noted that a change in a GUI view may include any visibly perceivable change made to the GUI view, including display of pop-up windows, dropdown menus, entering of data, animations for indicating user selections, etc. Thus, as long as the remote monitoring system is operated in the master-slave mode of operation, 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 mode of operation is the default mode of operation of the system, the second GUI synchronization setting B2 may put the remote monitoring system in a semi-independent mode of operation with the medical device 3A-C acting as principal device.

[0091] The third GUI synchronization setting B3 also puts the remote monitoring system into a master-slave mode of operation, only this time with the remote display device 7A-D acting as a master and the bedside or medical device monitor 4A-C acting as a slave. Optionally, in other embodiments where the independent mode of operation is the default mode of operation of the system, the third GUI synchronization setting B3 may put the remote monitoring system in a semi-independent mode of operation with the remote display device 7A-D acting as principal device.

[0092] The fourth GUI synchronization setting B4 puts the remote monitoring system into the abovedescribed dual semi-independent mode of operation, i.e. a semi-independent mode of operation where both the medical device 3A-C and the remote display device 7A-D act as principal devices.

[0093] The press button B5 for momentary GUI synchronization serves to momentarily transfer the GUI view of the medical device 3A-C to the GUI of the remote display device 7A-D while maintaining the independent mode of operation of the remote monitoring system, thereby allowing both clinicians to change the GUI view of their respective device immediately after synchronization.

[0094] The press button B6 for momentary GUI synchronization serves to momentarily transfer the

[0095] GUI view of the remote display device 7A-D to the GUI of the medical device 3A-C while maintaining the independent mode of operation of the remote monitoring system, thereby allowing both clinicians to change the GUI view of their respective device immediately after synchronization.

[0096] The press of any of the buttons B2-B6 constitutes a user input indicating a desire to synchronize the GUI of the medical device 3A-C and the GUI of the remote display device 7A- D. The remote monitoring system may be configured to effectuate the GUI synchronization in direct response to detection of the press of the button. Preferably, however, the system is configured to interpret the press of the button as a request for GUI synchronization from the user pressing it (i.e. the bedside clinician or the remote clinician), and to prompt the other user to confirm or accept GUI synchronization before effectuating the synchronization. In one example (not illustrated in the drawings), the system may cause an acceptance button to be displayed on the GUI of the other user, together with information indicating the type of GUI synchronization requested, and to effectuate GUI synchronization in response to detection of a press of the acceptance button. As understood from Figure 3 in conjunction with the above description, the type of GUI synchronization may hence be any type of GUI synchronization selected from the group consisting of:

[0097] GUI synch with bedside master and remote slave in master-slave mode (button B2) GUI synch with bedside principal in semi-independent mode

[0098] GUI synch with remote master and bedside slave in master-slave mode (button B3) GUI synch with dual semi-independent mode (button B4)

[0099] GUI synch with momentary transfer of bedside GUI view (button B5) GUI synch with momentary transfer of remote GUI view (button B6)

[0100] The remote monitoring system is preferably configured to indicate a current state of the GUI synchronization setting on the GUI of the medical device 3A-C and / or the remote display device 7A-D. The current state of the GUI synchronization setting may, for example, be indicated by a GUI synch indicator that is displayed in all GUI views, e.g. in a status bar that is shown in all GUI views, or be accessible via a setting menu of the GUI. Likewise, the GUI synchronization window 20 for adjusting a GUI synchronization setting may be accessible, e.g., by clicking the GUI synch indicator or by clicking the GUI synchronization setting in the setting menu.

[0101] With simultaneous reference still made to the remote monitoring system in Figure 1, Figures 4A-4D illustrate schematically the GUI view displayed on the monitor 4A-C of the medical device 3A-C (left-hand column) and the GUI view displayed on the remote display device 7A-D (right-hand column) for some different GUI synchronization settings. In Figure 4A, the remote monitoring system is operated in the default independent mode of operation, as also manually selectable via the button B1 in Figure 3. This is indicated by a GUI synch indicator 22, indicating that no synchronization is currently performed between the GUI view of the medical device 3A-C and the GUI view of the remote display device 7A-D. The GUI synch indicator 22 is displayed in both a current GUI view ‘A’ of the medical device monitor 4A- C and a current view ‘B’ of the remote display device 7A-D.

[0102] In Figure 4B, the remote monitoring system is operated in a master-slave mode of operation with the medical device monitor 4A-C acting as a master and the remote display device 7A-D acting as a slave, as selectable via the button B2 in Figure 3.

[0103] In Figure 4C, the remote monitoring system is operated in a master-slave mode of operation with the remote display device 7A-D acting as a master and the medical device monitor 4A-C acting as a slave, as selectable via the button B3 in Figure 3.

[0104] In Figure 4D, the remote monitoring system is operated in a dual semi-independent mode, as selectable via the button B4 in Figure 3.

[0105] It should be noted that a plurality of remote display device 7A-D could be used for remote monitoring of one and the same patient 1 and the operation of one and the same medical device, such as the mechanical ventilator 3A providing ventilatory treatment to the patient 1. In this scenario, it is contemplated that the plurality of remote display devices 7A-D could use the same or different GUI synchronization settings. For example, the remote monitoring system may be configured to enable each remote clinician to set his or her own GUI synchronization settings via a GUI synchronization window, such as the GUI synchronization window illustrated in Figure 3, accessible via the GUI of the respective remote display device 7A-D. The server 13 of the remote monitoring system could then keep track of the GUI synchronization settings of the different remote display devices 7A-D and effectuate GUI synchronization between the single medical device and the plurality of remote display devices in accordance with the GUI synchronization setting of the respective remote display device.

[0106] Although the remote monitoring system has been described above with reference to embodiments incorporating a server 13 for receiving, processing and forwarding patient data obtained at the patient site 5 to the remote display device 7A-D, it should be appreciated that the principles of the present disclosure could be utilized also in a remote monitoring system without such a server. For example, as illustrated by the dashed arrow 33 in Figure 1 , the patient data obtained at the patient site 5 may be transmitted directly to the remote display device 7A-D by the transmission module 9A-C at the patient site 5. Figure 5 is a flowchart illustrating an exemplary embodiment of a method performed in and by a system for remote monitoring of a patient located at a patient site, such as the remote monitoring system illustrated in Figure 1. The method is a computer-implemented method performed by the remote monitoring system upon execution of a computer program by one or more processors of the system. For example, the method may be performed by the system upon execution of a computer program stored in the data storage medium 14 of the server 13, upon execution of the computer program by the at least one processor 10 of the server.

[0107] In a first step, S1, the remote monitoring system is operated in a first mode of operation in which the GUI of the medical device 3A-C and the GUI of the remote display device 7A-D are configured to enable display of different GUI views on the medical device 3A-C and the remote display device 7A-D. As discussed above, this mode of operation may be an independent mode of operation or a semi-independent mode of operation.

[0108] In a second step, S2, the system detects a GUI synch initiation event occurring at the medical device 3A-C or the remote display device 7A-7D. As discussed above, the GUI synch initiation event may be, e.g., a user input indicating a desire for GUI synchronisation, a change in a GUI view of one of the medical device 3A-C or the remote display device 7A-D acting as a principal device in a semi-independent mode of operation, a change in an operational setting of the medical device, a change of an alarm status, or a change in a measurement value obtained by a sensor of the medical device 3A-C.

[0109] In a third step, S3, the GUI of the medical device 3A-C and the GUI of the remote display device 7A-7D are at least temporarily synchronized by causing a common GUI view to be displayed on both GUIs, in response to the detection of the GUI synch initiation event.

[0110] As should be appreciated by any person skilled in the art in view of the foregoing description, the proposed principles for GUI synchronization in remote monitoring of a patient may be implemented in many different ways. The principles are not limited to any particular type of network architecture or topology and modifications and variations are possible within the scope of the appended claims.

Claims

Claims1 . A system for remote monitoring of a patient (1) located at a patient site (5), the system being configured to display patient data obtained by a medical device (3A-C) co-located with the patient (1) on a graphical user interface [GUI] of the medical device (3A-C), and to communicate the patient data to a remote display device (7A-D) for display of the patient data on a GUI of the remote display device, wherein the system is configured to operate in a first mode of operation in which the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-D) are configured to enable simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device (3A-C) on the medical device (3A-C) and the remote display device (7A-D), wherein, when operated in the first mode of operation, the system is configured to detect a GUI synch initiation event occurring at the medical device (3A-C) or the remote display device (7A-7D), and to at least temporarily synchronize the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-7D) by causing a common GUI view to be displayed on both GUIs, in response to detection of the GUI synch initiation event.

2. The system according to claim 1 , wherein the GUI synch initiation event is a user input indicating a desire of a user to synchronize the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-D), input to the system via one of the medical device (3A-C) and the remote display device (7A-7D).

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

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

5. The system according to claim 1 , wherein the GUI synch initiation event is a change in an operational setting of the medical device.

6. The system according to any of the previous claims, wherein the system is configured to temporarily synchronize the GUIs upon the detection of the GUI synch initiation event, whereafter the GUI views of the medical device (3A-C) and the remote display device (7A- 7D) are allowed to diverge.

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

8. The system according to any of the claims 1-5, wherein the system is configured to enter into a dual semi-independent mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the dual semi-independent mode of operation, re-synchronize the GUIs of the medical device (3A-C) and the remote display device (7A-7D) in response to a change in the GUI view of any of the medical device (3A-C) and the remote display device (7A-7D).

9. The system according to any of the previous claims, wherein the common GUI view is a current GUI view of the medical device (3A-C) or the remote display device (7A-7D) at the time of detection of the GUI synch initiation event.

10. A method in a system for remote monitoring of a patient (1) located at a patient site (5), wherein the system is configured to display patient data obtained by a medical device (3A- C) co-located with the patient (1) on a graphical user interface [GUI] of the medical device (3A-C), and to communicate the patient data to a remote display device (7A-D) for display of the patient data on a GUI of the remote display device, the method comprising: operating (S1) the system in a first mode of operation in which the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-D) are configured to enable simultaneous display of mutually different GUI views for presenting patient data obtained by the medical device (3A-C) on the medical device (3A-C) and the remote display device (7A-D);- when operated in the first mode of operation, detecting (S2) a GUI synch initiation event occurring at the medical device (3A-C) or the remote display device (7A-7D), and at least temporarily synchronizing (S3) the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-7D) by causing a common GUI view to be displayed on both GUIs, in response to detection of the GUI synch initiation event.

11. The method according to claim 10, wherein the GUI synch initiation event is a user input indicating a desire of a user to synchronize the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-D), input to the system via one of the medical device (3A-C) and the remote display device (7A-7D).

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

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

14. The method according to claim 10, wherein the GUI synch initiation event is a change in an operational setting of the medical device.

15. The method according to any of the claims 10-14, comprising a step of temporarily synchronizing the GUIs upon the detection of the GUI synch initiation event, whereafter the GUI views of the medical device (3A-C) and the remote display device (7A-7D) are allowed to diverge.

16. The method according to any of the claims 10-14, comprising a step of operating the system in a master-slave mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the master-slave mode of operation, preventing changes to the GUI view of one of the medical device (3A-C) and the remote display device (7A-D) acting as a slave in the master-slave mode of operation, and resynchronizing the GUIs of the medical device (3A-C) and the remote display device (7A- 7D) in response to a change in the GUI view of the other device acting as a master in the master-slave mode of operation.

17. The method according to any of the claims 10-14, comprising a step of operating the system in a dual semi-independent mode of operation at least for a certain period of time following the detection of the GUI synch initiation event, and, in the dual semi-independent mode of operation, re-synchronizing the GUI of the medical device (3A-C) and the GUI of the remote display device (7A-7D) in response to a change in the GUI view of any of the medical (3A-C) and the remote display device (7A-7D).

18. The method according to any of the claims 10-17, wherein the common GUI view is a current GUI view of the medical device (3A-C) or the remote display device (7A-7D) at the time of detection of the GUI synch initiation event.

19. A computer program for a system for remote monitoring of a patient (1) located at a patient site (5), wherein the system is configured to display patient data obtained by a medical device (3A-C) co-located with the patient (1) on a graphical user interface [GUI] of the medical device (3A-C), and to communicate the patient data to a remote display device (7A-D) for display of the patient data on a GUI of the remote display device, wherein the computer program comprises computer-readable instructions which, when executed by at least one processor (10) of the system, causes the system to perform the method of any of the claims 10-18.

Images