Remote ventilator adjustment

Abstract

Aspects of the technology include methods and systems for performing remote adjustments to a ventilator with a remote device. A remote device may include an interactive display including a remote position indicator. The remote position indicator may be associated or correlated with a local ventilator position indicator. A selection and/or adjustment at the remote device (or an activation at the remote device) at the interactive display may result in a selection, adjustment, or activation at the ventilator. Information may be transmitted to the ventilator from the remote device to remotely adjust the ventilator. Additionally or alternatively, the remote device may additionally display a view of, or replicate, some or all portions of the ventilator display.

Description

INTRODUCTION

Medical ventilator systems have long been used to provide ventilatory and supplemental oxygen support to patients. These ventilators typically comprise a connection for pressurized gas (air, oxygen) that is delivered to the patient through a conduit or tubing. As each patient may require a different ventilation strategy, modern ventilators can be customized for the particular needs of an individual patient. For example, several different ventilator modes or settings have been created to provide better ventilation for patients in different scenarios, such as mandatory ventilation modes, spontaneous ventilation modes, and assist-control ventilation modes. Ventilators monitor a variety of patient parameters and are well equipped to provide reports and other information regarding a patient's condition. To change modes and the settings therein, medical care professionals must interact directly with the ventilator.

SUMMARY

Aspects of the present disclosure relate to remotely adjusting a ventilator. A remote device (e.g., located outside of a room of a ventilator which the remote device is controlling) may receive an input at a remote user interface of the remote device to cause a settings change at the ventilator. The input may vary based on what is displayed on the remote user interface. In an example, the remote user interface may be a trackpad with an adjustment element. In this instance, the input may correlate a remote position indicator with a local ventilator position indicator. In another example, the remote user interface may replicate a portion of the ventilator GUI. In this instance, selectable elements at the remote user interface may be associated with an overlay to correlate with a selection at the ventilator.

The remote device and the ventilator may be connected via a relay transceiver. The relay transceiver may be movable between two or more ventilators. The relay transceiver may have a wired connection with a ventilator and a wireless connection with a remote device. Multiple remote devices may be capable of connecting with a single relay transceiver. Inputs at the remote device may effectuate settings changes at the ventilator using the relay transceiver.

Additionally, the remote user interface may include user interface elements associated with physical user interface element of the ventilator (e.g., a physical bezel key or a physical dial). For example, the remote user interface may include a virtual bezel key or an adjustment element. The remote user interface may be subdivided into sections or panels, such as a changeable section (e.g., changeable based on a view mode), a selection section, or an adjustment section.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts a diagram illustrating an example of a ventilator connected to a human patient.

FIG. 1B depicts a diagram illustrating the ventilator of FIG. 1A, a remote display, and a remote device for adjusting the ventilator and/or viewing data from the ventilator.

FIG. 1C depicts a schematic diagram illustrating features of the remote device.

FIGS. 2A-2C depict example systems for remotely adjusting a ventilator with a remote device.

FIG. 3 depicts an example method for remotely adjusting a ventilator based on a time-varying user input received at a remote device.

FIG. 4 depicts another example method for remotely adjusting a ventilator based on a time-varying user input received at a remote device.

FIGS. 5A and 5B depict example user interfaces of a ventilator and a remote device.

FIG. 5C depicts an example remote user interface on a remote display of a remote device.

FIG. 6 depicts a method for remotely adjusting and/or accessing a ventilator based on an input received at a remote device.

FIGS. 7A, 7B, 7C, and 7D depict examples of a remote user interface.

FIGS. 8A and 8B depict example systems for remotely adjusting a ventilator with a remote device.

FIG. 9 depicts a diagram showing example allocations of relay transceivers.

FIG. 10 depicts a method for remotely adjusting a ventilator from a perspective of a remote device.

FIG. 11 depicts a method for remotely adjusting a ventilator from a perspective of a relay transceiver.

FIG. 12 depicts a method for pairing a relay transceiver with multiple ventilators.

FIG. 13 depicts a method for receiving changes to be caused at a ventilator from multiple remote devices.

While examples of the disclosure are amenable to various modifications and alternative forms, specific aspects have been shown by way of example in the drawings and are described in detail below. The intention is not to limit the scope of the disclosure to the particular aspects described. On the contrary, the disclosure is intended to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure and the appended claims.

DETAILED DESCRIPTION

Ventilation provided to patients via a ventilator is controlled based, at least in part, on settings and inputs provided by a medical professional. To provide those inputs and settings, however, the medical professional must directly interact with the ventilator, such as by pressing buttons, providing touch inputs, rotating knobs or dials, etc. Directly interacting with the ventilator may present risks to the medical professional as well as the patient. For example, physically touching different ventilators increases the risk of cross-contamination and the potential spread of diseases. In addition, direct interaction with a ventilator requires physical access to the ventilator, which can be a challenge particularly in the case of patients with highly contagious diseases that may be quarantined.

The present technology looks to alleviate some of those problems by providing remote control or remote adjustment of the ventilator by a remote device. In an embodiment, the remote device receives an input at a remote user interface that is correlated or associated with a ventilator user interface displayed on the ventilator. The input may be a time-varying user input received over time. Additionally, aspects of the remote user interface on the remote device are associated with physical input components (e.g., buttons, knobs, dials, switches, etc.) on the ventilator, such that an adjustment at the remote user interface causes the same change on the ventilator user interface as a physical input. Accordingly, the ventilator may be remotely controlled by a medical professional from the remote device. By being remote from the ventilator, the medical professional does not have to physically interact with the ventilator itself.

The present technology is directly applicable to treatment of patients having highly contagious respiratory diseases, such as a coronavirus disease (COVID-19) caused by the severe acute respiratory syndrome coronavirus 2 (SARS-CoV-2). Remotely controlling a ventilator allows for the enhancement of COVID-19 patient care by: (1) increasing patient and clinician safety, (2) reducing usage of personal protective equipment (PPE), (3) providing easily accessible patient status and wellbeing information, and (4) allowing remote consultations with global experts.

First, patient and clinician safety are improved by the present technology. Clinician safety is improved by allowing a clinician to provide care to a contagious patient (e.g., a patient that contracted COVID-19) from outside of the patient's room. The clinician may therefore provide care with less exposure to contagion. Additionally, patient safety is also improved by the present technology by reducing the patient's exposure to the clinician. A clinician may interact with multiple ventilators and multiple patients throughout a hospital and may thus spread infection even when asymptomatic. Limiting the clinician's entry into a patient room reduces the risk of cross-contamination of COVID-19, or other contagious diseases, spread by a clinician.

Second, the present technology reduces usage of PPE. During a global pandemic, such as COVID-19, there can be a shortage of PPE. This is, in part, due to an increase in usage of PPE by all people (e.g., not just patient care providers) and an increase in global purchases of PPE by treatment facilities, businesses, and everyday consumers. Additionally, PPE is expensive, time-consuming to don correctly, may cause discomfort or even injury to the wearer, may impede wearer focus, and increases waste build-up due to limited reuse. Thus, reducing usage of PPE improves quality and speed of care, reduces cost, and protects the environment. Specifically, conserving PPE helps a clinician by increasing comfort and preventing lack of focus or impatience caused by uncomfortable or painful PPE, preserves the availability of PPE when needed, and reduces the risk of a clinician wearing PPE incorrectly and resulting in accidental exposure to contagious diseases. Conserving PPE helps patients by reducing delays in patient care caused by the time needed to correctly don PPE. This delay accumulates throughout the day as clinicians reposition or replace PPE, thus reducing overall time otherwise spent with patients. By allowing access to patients without requiring PPE, clinicians may be able to provide quicker patient care.

Third, the present technology reduces stress of clinicians and loved ones by providing easily accessible patient status and wellbeing information. By allowing remote viewing and control of a ventilator, clinician stress may be reduced by easily viewing ventilator settings remotely. For example, a clinician may check on multiple patients while saving time otherwise spent walking from room to room. Additionally, a view of the ventilator screen and the patient's status may be available for friends and family of a contagious patient who otherwise could not be in the room with the patient (e.g., to prevent spread).

Fourth, the present technology allows remote consultation with global experts. During a global pandemic, such as COVID-19, experts around the globe are working together to combat spread of a contagious disease. This includes experts such as COVID-19 recovery experts, ventilator diagnostic experts, vaccination and antibody experts, other clinical or medical experts (e.g., a clinical hotline), service experts (e.g., a manufacturer consult for if a ventilator appears to be malfunctioning), and product training experts (e.g., to consult with a manufacturer for training or use cases of a ventilator), etc. These experts are not located in a single treatment facility, nor are these experts located in each treatment facility. To provide the best care to COVID-19 patients world-wide, the present technology allows for remote ventilator view sharing for consultation with a variety of experts located around the world. Thus, the present technology provides a variety of advantages specific to treating COVID-19.

Beyond the pandemic scenario and COVID-19 specifically, the present technology has a variety of other practical applications for patient care. For example, the present technology may be used for patient isolation rooms, such as when a patient has or might have a communicable disease, when PPE is required to enter a room, or if the patient or equipment inside a room presents any danger to anyone entering the room. Additionally, the present technology may be used to limit direct interaction with a patient that is immunocompromised or otherwise susceptible to infection, such as a patient recovering from an organ transplant. The present technology may also be implemented when access is limited for safety, such as when a sterile procedure is being performed (e.g., limiting entry into a room while changing a wound dressing or a catheter), or when radiation is utilized (e.g., limiting exposure to a clinician in imaging rooms for computerized tomography (CT), magnetic resonance imaging (MRI), x-ray imaging, etc). Moreover, use of the present technology may also apply to areas of a hospital that have limited access due to security, such as the maternity ward or neonatal care areas (e.g., neonatal intensive care unit, NICU).

The present technology may also be implemented to limit movement in and out of a patient room and limit visible interactions with the ventilator. This may significantly reduce the stress of patients and visitors. For example, visitors may experience stress when watching a clinician adjust ventilator settings in person. By allowing the clinician to perform minor adjustments just outside of the room, stress of visiting family members and friends may be reduced. Additionally, remote ventilator viewing and adjustment allows visitors to have longer periods of uninterrupted time with the patient. This may be particularly impactful for certain patient populations, such as fragile NICU patients, or terminal patients.

The present technology can also increase the speed or daily rounds by a pulmonologist, clinician, or other assigned caregiver by reducing the amount of time otherwise required to walk from bedside-to-bedside. Additionally, the present technology may provide viewing of live data for teaching opportunities, such as for study by residents, students, ongoing clinical trials, etc. Further, the present technology provides a gateway for remote collaboration and consultation by medical teams or experts located outside of a treatment facility or far away, including longer-term care facilities, home care patients, transportation of patients between facilities (e.g., a patient being transferred or travelling via plane, helicopter, or ambulance), military care locations (e.g., temporary facilities, field hospitals, aircrafts, naval vessels, etc.), or rural care facilities (e.g., rural ICUs).

FIG. 1A depicts a diagram illustrating an example of a ventilator 100 connected to a human patient 150. Ventilator 100 includes a pneumatic system 102 (also referred to as a pressure generating system 102) for circulating breathing gases to and from patient 150 via the ventilation tubing system 130, which couples the patient to the pneumatic system via an invasive (e.g., endotracheal tube, as shown) or a non-invasive (e.g., nasal mask) patient interface 180.

Ventilation tubing system 130 may be a two-limb (shown) or a one-limb circuit for carrying gases to and from the patient 150. In a two-limb example, a fitting, typically referred to as a “wye-fitting” 170, may be provided to couple the patient interface 180 to an inhalation limb 134 and an exhalation limb 132 of the ventilation tubing system 130.

Pneumatic system 102 may have a variety of configurations. In the present example, system 102 includes an exhalation module 108 coupled with the exhalation limb 132 and an inhalation module 104 coupled with the inhalation limb 134. Compressor 106 or other source(s) of pressurized gases (e.g., air, oxygen, and/or helium) is coupled with inhalation module 104 to provide a gas source for ventilatory support via inhalation limb 134. The pneumatic system 102 may include a variety of other components, including mixing modules, valves, sensors, tubing, accumulators, filters, etc.

Controller 110 is operatively coupled with pneumatic system 102, signal measurement and acquisition systems, and an operator interface 120 that may enable an operator to interact with the ventilator 100 (e.g., change ventilator settings, select operational modes, view monitored parameters, etc.). Controller 110 may include memory 112, one or more processors 116, storage 114, and/or other components of the type found in command and control computing devices. In the depicted example, operator interface 120 includes a display 122 that may be touch-sensitive and/or voice-activated, enabling the display 122 to serve both as an input and output device.

The memory 112 includes non-transitory, computer-readable hardware storage media that stores software that is executed by the processor 116 and which controls the operation of the ventilator 100. In an example, the memory 112 includes one or more solid-state storage devices such as flash memory chips. In an alternative example, the memory 112 may be mass storage connected to the processor 116 through a mass storage controller (not shown) and a communications bus (not shown).

FIG. 1B depicts a diagram illustrating the ventilator 100 of FIG. 1A, a first remote device 160, and a second remote device 194. The first remote device 160 and the second remote device 194 may be capable of adjusting the ventilator 100 and/or viewing data from the ventilator 100. The display 122 of the ventilator is communicatively coupled to the remainder of the ventilator components, such as memory, processors, sensors, etc. The display 122 is configured to display the ventilator graphical user interface (GUI) 123. The ventilator GUI 123 may be an interactive display, e.g., a touch-sensitive screen or otherwise, and may provide various windows (i.e., visual areas) comprising elements for receiving user input and interface command operations and for displaying ventilatory information (e.g., ventilatory data, alerts, patient information, parameter settings, etc.). The elements may include controls, graphics, charts, tool bars, input fields, icons, etc. Alternatively, other suitable means for providing input may be provided on the ventilator 100, for instance by a wheel, dial, knob, keyboard, mouse, bezel key, or other suitable interactive device. Thus, ventilator user interface 123 on the display may accept commands and input through display 122 as touch input or through other input devices. Inputs may be received by the ventilator 100 from a clinician 190.

The ventilator user interface 123 may also provide useful information in the form of various ventilatory data regarding ventilation of the patient, the physical condition of a patient, and/or a prescribed respiratory treatment. The useful information may be derived by the ventilator 100, based on data collected by sensors, and the useful information may be displayed in the form of graphs, wave representations (e.g., a waveform), pie graphs, numbers, or other suitable forms of graphic display. Additionally, the ventilator user interface 123 may provide selectable and/or adjustable ventilator control elements to select or adjust associated ventilatory settings. In an example, the ventilator control element may be an icon on the ventilator user interface 123. In another example, the ventilator control element may be a physical input at the ventilator 100.

The ventilator controls ventilation of a patient 150 according to the ventilatory settings. Ventilatory settings (or ventilation settings) may include any appropriate input for configuring the ventilator to deliver breathable gases to a particular patient, including measurements and settings associated with exhalation flow of the breathing circuit. Ventilatory settings may be entered or adjusted, e.g., by a clinician based on a prescribed treatment protocol for the particular patient, or automatically generated by the ventilator, e.g., based on attributes (i.e., age, diagnosis, ideal body weight, gender, etc.) of the particular patient according to any appropriate standard protocol or otherwise. Ventilatory settings may include inhalation flow, frequency of delivered breaths (e.g., respiratory rate), tidal volume, positive end-expiratory pressure (PEEP), etc.

The first remote device 160 may include a first remote display 162 that is capable of displaying a first remote GUI 163. Similarly, the second remote device 194 may include a second remote display 196 that is capable of displaying a second remote GUI 198. In an example, the first remote device 160 may be a tablet computer and the second remote device 194 may be a laptop computer. Other types of devices are also possible. The first remote GUI 163 and the second remote GUI 198 may replicate the ventilator GUI 123, or a portion thereof. In other examples, the first remote GUI 163 or the second remote GUI 198 may display alternate views or perspectives of the ventilator GUI 123. In some examples, the first remote GUI 163 may be different from the second remote GUI 168. The first remote display 162 and/or the second remote display 196 may be a touchscreen for receiving inputs and interactions with the first remote GUI 163 and the second remote GUI 198, respectively. In other examples, the first remote device 160 and/or the second remote device 194 may also include other input means, including voice input or other input elements such as keyboards, buttons, wheels, mouse, trackpad, bezel key, etc. for inputting data into the first remote device 160 and the second remote device 194, respectively. The first remote device 160 may establish a first wired or wireless connection 164 with the ventilator 100. Similarly, the second remote device 194 may also establish a second wired or wireless connection 192 with the ventilator 100. The first wired or wireless connection 164 and the second wired or wireless connection 192 may be any type of connection capable of transmitting data between two devices, such as radio-frequency wireless connections, cables, etc. For example, the first wired or wireless connection 164 and/or the second wired or wireless connection 192 may be a WIFI-based connection, a BLUETOOTH-based connection, an RF-LITE-based connection, a ZIGBEE-based connection, an ultra-wideband-based connection, an Ethernet connection, a network-based connection (e.g., local area network (LAN), wide area network (WAN), etc.), an Internet-based connection, and/or an optical connection, such as an infrared-based connection.

The first wired or wireless connection 164 and the second wired or wireless connection 192 may be used to transmit data to the ventilator 100 and/or receive data from the ventilator 100 via a data signal. For example, data may be transmitted, via the first wired or wireless connection 164 and/or the second wired or wireless connection 192, from the ventilator 100 to the first remote device 160 and/or the second remote device 194. The transmitted data or data signal may be used to populate one or more of the first remote GUI 163 and the second remote GUI 198. In addition, data may be transmitted, via the first wired or wireless connection 164 and/or second wired or wireless connection 192, from the first remote device 160 and/or second remote device 194 to the ventilator 100. The transmitted data may be indicative of an input or change in a value associated with a ventilatory setting for the ventilator 100, as received as an input at the first remote device 160 or the second remote device 194. The input may be received over a period of time, or alternatively may be associated with one point in time. Accordingly, settings for the ventilator 100 may be changed remotely via the first remote device 160 and/or second remote device 194.

As an example, the first remote device 160 may display a first remote GUI 163 that is interactive, or available to receive a time-varying user input at the first remote device 160. Alternatively, the first remote device 160 may be non-interactive (e.g., the first remote GUI 163 may be limited to remote viewing of the ventilator GUI 123 without accepting any inputs or adjustments). The first remote GUI 163 may be the same (e.g., replicated) or different from the ventilator GUI 123. In an example, the first remote GUI 163 may be a virtual trackpad. In another example, the first remote GUI 163 may be a user interface that is specific to attributes of the first remote device 160. For example, the first remote GUI 163 may manipulate UI elements of the ventilator GUI 123 (e.g., change all or a portion of element size or orientation, reorganize, show a subset of elements, etc.) based on screen size, application real estate, type of device (e.g., mobile device, tablet, laptop, etc.). As another example, the first remote GUI 163 may fill all or a portion of the first remote display 162 of the first remote device 160. The second remote device 194 may display a second remote GUI 198 that may be the same or different from the first remote GUI 163. In an example, the first remote device 160 may be interactive, while the second remote device 194 may non-interactive, or display-only. In a further example, the first remote device 160 may be a tablet with a first screen size and manipulated UI elements, while the second remote device 194 may be a laptop with a second screen size replicating the ventilator GUI 123.

In an example where the first remote GUI 163 or second remote GUI 198 is capable of receiving user interaction (e.g., interactive), a time-varying user input may be received at the first remote device 160 or second remote device 194 at a first remote position indicator 165 or second remote position indicator 199, such as registered touch on a touchscreen, hovering over a touchscreen, a mouse cursor position, a trackpad cursor position, selected UI elements, etc. The first remote position indicator 165 and/or second remote position indicator 199 may be correlated with, or correspond to, a local ventilator position indicator 127 on the ventilator GUI 123. In some examples, the local ventilator position indicator 127 may be a cursor or other visual element that indicates a current selection position. The ventilator 100 may send data via a data signal to the interactive first remote device 160 and/or second remote device 194 to allow replication of portions of the ventilator GUI 123, including the local ventilator position indicator 127.

The ventilator 100 may include at least one physical input component 129. For example, the physical input component 129 may be a button, wheel, dial, slide, switch, key, etc. The physical input component 129 may be positioned or located on the ventilator 100 outside of the ventilator GUI 123. Additionally, a physical input, from a clinician, at the physical input component 129 may be associated with an adjustment of a selected ventilator control element on the ventilator GUI 123. In an example, the second remote GUI 198 may include one or more remote adjustment elements 197 correlated with or associated with a physical input at the physical input component 129. The remote adjustment elements 197 may be virtual elements that are displayed on the second remote GUI 198. The remote adjustment elements 197 may also be displayed in a format that is based on the corresponding physical input component. For instance, in the example depicted, the remote adjustment element 197 appears as a virtual dial, and the remote adjustment element may be manipulated in the same manner as a dial (e.g., a touch input to rotate the virtual dial, as may be received over time). An adjustment input associated with the remote adjustment element 197 on the second remote GUI 198, as may be a time-varying user input or alternatively associated with one point in time, may be transmitted through a data signal over the second wired or wireless connection 192 to the ventilator 100. Based on the adjustment input transmitted through an adjustment data signal, the ventilator may determine a change in a selected ventilator setting as if the physical input component 129 was physically adjusted. The remote adjustment element may be overlaid or outside of user interface elements displayed on the second remote GUI 198.

A clinician may perform an input action at the remote device (e.g., first remote device 160 and/or second remote device 194) to effectuate a change at the ventilator 100. A user action received at the remote device may be a user input (as may be a time-varying) or other user interaction, as otherwise described herein. In examples, an input action may be received at a wheel, dial, knob, keyboard, mouse, bezel key, touchpad, microphone, or other suitable interactive device associated with the remote device. Physical buttons and/or keys on a keyboard may include up or down arrows, numerical keys, mouse buttons, a mouse wheel, etc. The input action received at a suitable interactive device communicatively coupled with a remote device may then be associated with an input at the ventilator 100. For instance, an input action of selecting an up arrow on a keyboard communicatively coupled to the remote device may increase a value at the ventilator 100.

Scrolling a mouse wheel associated with the remote device may also effectuate a change at the ventilator 100. In an example, scrolling a mouse wheel associated with the remote device may increase or decrease a value at the ventilator 100. For instance, after a selection at the remote device (e.g., received at any suitable interactive device) that is associated with a selection at the ventilator 100 (e.g., selection of any user interface element on the ventilator GUI 123 and/or selection of a physical input 129 at the ventilator 100), a scroll of a mouse wheel at the remote device may change a value associated with the selection at the ventilator 100. Alternatively, a scroll of a mouse wheel associated with the remote device may change an associated value at the ventilator 100 without a prior selection at the remote device (e.g., a value associated with a current position indicator or cursor without a selection). Although a mouse wheel is described, it should be appreciated that these examples may be applied to any rotatable element, such as a physical wheel, dial, or any other variable, physical input associated with the remote device.

An input action at the remote device may also be a gesture. A gesture received at the remote device may be associated with a change at the ventilator 100. For example, the change at the ventilator 100 may be the same result as if the gesture were directly received at the ventilator GUI 123. A gesture at the remote device may be received at any of the interactive devices described herein (e.g., mouse, touchpad, touchscreen, etc.). A variety of gestures may be supported by the remote device, including a swipe, double-tap, drag, touch and hold, drag and drop, etc. One or more controls on the ventilator GUI 123 may be configurable to change in response to one or more gestures at the remote device. Gestures at the remote device may cause visual changes (or visually change) of one or more portions of the ventilator GUI 123, such as maximizing, minimizing, enlarging, shrinking, expanding, collapsing, scrolling, condensing, or otherwise augmenting the view of a portion of the ventilator GUI 123. One or more gestures at the remote device may effectuate the same or similar visual changes on one or more portions of the ventilator GUI 123. Examples of a portion of the ventilator GUI 123 that may be visually changed include a dialog, panel, waveform, tooltip, list, alarm, alarm banner, patient data, patient data panel, graph axis scale, waveform cursor, scrollbar, etc., on the ventilator GUI 123.

As an example gesture, a swipe gesture may include substantially linear movement in a specific direction. Thus, a swipe gesture includes a line with a start position and an end position. In an example, the movement associated with the swipe is rapid. A swipe at the remote device, or a swipe at the remote GUI of the remote device (e.g., first remote GUI 163 of first remote device 160 or at a second remote GUI 198 at second remote device 194), may visually change a portion of the ventilator GUI 123. In an example, a swipe toward the center of the remote GUI may open a dialog and/or panel on the ventilator GUI 123, and a swipe toward a side (e.g., right side, left side, top side, bottom side) of the remote GUI may close a dialog and/or panel on the ventilator GUI 123. The dialogs and/or panels may slide in or out from one or more sides of the ventilator GUI 123 and/or remote GUI. In another example, a paused waveform on the ventilator GUI 123 may be moved in a desired direction on the ventilator GUI 123 by a swipe at the remote device in the desired direction.

If a portion of the swipe gesture received at the remote device (i.e., a portion of the line which may include the start position and/or end position) is associated with at least a portion of a control on the ventilator GUI 123 (e.g., overlaps a control on the ventilator GUI 123), then a visual aspect of the control on the ventilator GUI 123 may change. For example, a swipe at the remote GUI, for which at least a portion of the swipe is associated with a portion of a waveform on the ventilator GUI 123, may cause a visual change of the waveform on the ventilator GUI 123. For instance, an upward swipe at the remote device that is associated with an overlap of a waveform on a ventilation GUI 123 may maximize or enlarge the waveform, while a downward swipe may minimize or shrink the waveform.

In another example, a swipe at the remote GUI, for which at least a portion of the swipe is associated with a portion of a tooltip on the ventilator GUI 123, may cause a change in the displayed description associated with the tooltip. As referred to herein, a tooltip is information related to providing assistance or help related to the ventilator 100 and/or user interface elements displayed on the ventilator GUI 123. For instance, an upward swipe at the remote device that is associated with an overlap of a tooltip on the ventilator GUI 123 may expand the tooltip description (e.g., display a longer description or open the description), while a downward swipe may collapse the tooltip description (e.g., display a shorter description or close the description).

In a further example, a swipe at the remote GUI, for which at least a portion of the swipe is associated with a portion of a patient panel on the ventilator GUI 123, may cause a change in the display of the patient panel. For instance, an upward swipe at the remote device that is associated with an overlap of a patient panel on the ventilator GUI 123 may display additional information (e.g., open the patient panel or open an additional patient panel or otherwise display additional information associated with the patient) on the ventilator GUI 123, while a downward swipe may enlarge aspects of the patient panel (e.g., display larger font).

A double-tap gesture may include two selection inputs (e.g., mouse clicks, touches, button presses, etc.) associated with a substantially same position within a shortened time or in rapid succession. A double-tap at the remote device may visually change a portion of the ventilator GUI 123 (e.g., at a position on the ventilator GUI 123 associated with the position at which the double-tap is received at the remote device). For example, a double-tap received at the remote device may maximize or minimize a portion of a waveform on the ventilator GUI 123, expand or collapse a tooltip description (e.g., as may be similar to swiping over a tooltip) on the ventilation GUI 123, display a pop-up menu on the ventilator GUI 123, etc.

A drag gesture may include an uninterrupted selection and movement. For example, a drag may include movement of a touch interaction across a touch surface without losing contact with the touch surface. The drag gesture may be similar to a swipe gesture over a longer time and/or at a slower speed. A drag gesture at the remote device may visually change a portion of the ventilator GUI 123 (e.g., at one or more positions on the ventilator GUI 123 associated with one or more positions at which the drag gesture was received at the remote device).

For example, a drag at the remote device may scroll through a list on the ventilator GUI 123 (e.g., drag upward, drag downward, drag to the right, or drag to the left, or any combination of directions). The scroll on the ventilator GUI 123 may be in the same or opposite direction of that of the drag at the remote device. The scroll speed may be based on a distance of the associated drag outside of a boundary of the list. For instance, a drag at the remote device associated with a position at the ventilator GUI 123 that is further outside the boundary of a list may cause faster scrolling of the list at the ventilator GUI 123. Scrolling on the ventilator GUI 123 may be automatic when the drag at the remote device begins at a position associated inside the list and ends at a position associated outside the list.

In another example, a drag at the remote device that is associated with an axis of a graph on the ventilator GUI 123 may change a scale of the graph axis. For instance, a drag to the right at the remote device may increase the scale of the axis of a graph on the ventilator GUI 123, a drag to the left may decrease the scale of the axis, an upward drag may increase a scale of a y-axis of the graph, a downward drag may decrease the scale of the y-axis of the graph, etc. As a further example, when a waveform is paused on the ventilator GUI 123, a drag at the remote device may move a cursor on the waveform and/or the graph of the waveform on the ventilator GUI 123.

A touch and hold gesture may include a continuous selection lapsing at least a threshold of time. For example, a touch and hold gesture may include a selection continuously received for at least 0.5 seconds. A touch and hold at the remote device may visually change a portion of the ventilator GUI 123 (e.g., at the position on the ventilator GUI 123 associated with the position at which the touch and hold is received at the remote device). For example, a touch and hold received at the remote device may display a tooltip dialog for a user interface element on the ventilator GUI 123. A tooltip dialog appearing on the ventilator GUI 123 as a result of a touch and hold at a remote device may be visually emphasized (e.g., highlighting, tinting, blinking, glowing, etc.) to indicate an association with a touch and hold gesture.

A drag and drop gesture may include an uninterrupted selection and movement (i.e., drag gesture) accompanied by a de-selection. For example, a drag and drop gesture may include receiving a touch selection, drag, and touch release at the remote device, associated with a portion of the ventilator GUI 123. A drag and drop gesture at the remote device may visually change a portion of the ventilator GUI 123 (e.g., at a position on the ventilator GUI 123 associated with a start position and/or end position at which the drag and drop is received at the remote device). For example, a drag and drop received at the remote device may visually display a help icon on the ventilator GUI 123 (e.g., dragging and dropping) onto a displayed user interface element on the ventilator GUI 123. If the help icon is “dropped” onto a user interface element on the ventilation GUI 123, a help description may be displayed (e.g., a help description associated with the user interface element onto which the help icon was dropped). Prior to “dropping” the help icon, a visual indication of whether additional information is available for the overlaid element may be displayed (e.g., the overlaid element and/or the dragged help icon may be glowing, highlighted, display a symbol or other icon, etc.).

The remote device may have a variety of configurations or may have limited components. For example, the remote device may not include a display or may not include a computer. Alternatively, the remote device may be a peripheral device for receiving a clinician's input at the remote device (e.g., mouse, keyboard, touchpad, microphone, number pads, etc.). For example, the remote device may be a peripheral device for receiving input from a clinician that sends information associated with the input to the ventilator 100.

In another example, the ventilator 100 may be “headless” (e.g., have no display or GUI) and may send display information to a display device, such as replicate display device 216 in FIG. 2A. For instance, the ventilator 100 may receive information from a peripheral device (i.e., the remote device) and then send display information to a third device that may be positioned remotely from the ventilator 100 (e.g., outside of a room in which the ventilator 100 is located and/or in a different room from which the ventilator 100 is located).

FIG. 1C depicts a schematic diagram illustrating features of the first remote device 160 and second remote device 194. In some examples, first remote device 160 and/or the second remote device 194 may be a tablet, smartphone, laptop, or other type of computing device. The first remote device 160 may be different from the second remote device 194. In its most basic configuration, the first remote device 160 and second remote device 194 typically include at least one processor 171 and hardware memory 173. Depending on the exact configuration and type of computing device, memory 173 (storing, among other things, instructions to perform the proximity, control, and display methods disclosed herein) can be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.), or some combination of the two. This most basic configuration is illustrated in FIG. 1C is indicated by dashed line 175. Further, first remote device 160 and second remote device 194 may also include storage devices (removable, 177, and/or non-removable, 179) including, but not limited to, solid-state devices, magnetic or optical disks, or tape. Similarly, first remote device 160 and second remote device 194 can also have input device(s) 183 such as touch screens, keyboard, mouse, pen, voice input, etc., and/or output device(s) 181 such as a display, speakers, printer, etc. Also included in the environment can be one or more communication connections 185, such as LAN, WAN, point to point, Bluetooth, RF, etc.

The first remote device 160 and second remote device 194 may each be a single computing device operating in a networked environment using logical connections to one or more remote computers. The remote computer can be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above as well as others not so mentioned. The logical connections can include any method supported by available communications media. Such networking environments may be commonplace in hospitals, offices, enterprise-wide computer networks, intranets, and the Internet.

FIGS. 2A-2C depict example systems for remotely adjusting a ventilator 202 with a remote device 226. More specifically, FIG. 2A depicts an example system 200A for remote adjustment of a ventilator 202 based on an input, as may be time-varying, received at a remote device 226. The system 200A includes a ventilator 202, a replicate display device 216, and a remote device 226. The ventilator 202 may be similar to ventilator 100 described herein. For example, the ventilator 202 may include a display 204 (similar to display 122) and a ventilator GUI 206 (similar to ventilator GUI 123). The ventilator GUI 206 may include a local ventilator position indicator 208 (similar to local ventilator position indicator 127). The local ventilator position indicator 208 may also include past movement data 210. The past movement data 210 may indicate the prior position of the local ventilator position indicator 208 or a vector of prior positions of the local ventilator position indicator 208. In some sense, the past movement data 210 may effectively be a trail of the local ventilator position indicator 208. All, or a portion of, the past movement data 210 may be displayed as an indicator on the ventilator GUI 206 and/or remote GUI 230.

The ventilator 202 may be physically separated or distanced from the replicate display device 216 and/or the remote device 226 by a physical separation 212, such as a distance, a room, a wall or separator, a door, a window, a screen, etc. In an example, the ventilator GUI 123 may not be visible from the location of the remote device 226. The replicate display device 216 and the remote device 226 may be communicatively coupled to the ventilator via a first wired or wireless connection 214A and a second wired or wireless connection 214B, respectively, which may be similar to wired or wireless connections 164, 192. The first wired or wireless connection 214A and the second wired or wireless connection 214B may be different.

The replicate display device 216 includes a replicate display 218 with a replicate GUI 220. The replicate display device 216 receives data via the wired or wireless connection 214A to replicate the ventilator GUI 206, which may include a replicate position indicator 222 (replicating the ventilator position indicator 208). The replicate position indicator 222 and the ventilator position indicator 208 may be based on past movement data 210, 224. The replicate GUI 220 may replicate all or a portion of the ventilator GUI 206. Additionally or alternatively, the replicate GUI 220 may display a different view or perspective of the ventilator GUI 206 and/or display 204. In an example, the wired or wireless connection 214A between the ventilator 202 and the replicate display device 216 may be one-way such that data is transmitted from the ventilator 202 to the replicate display device 216. The replicate display device 216 may be non-interactive. As an example, the replicate display device 216 may be a television or a monitor.

The replicate display device 216 may be located outside of separation 212 or, alternatively, located proximate to the ventilator 100. In an example where the replicate display device 216 is located proximate to the ventilator 100, the replicate display device 216 may be positioned to allow visibility of the replicate display 218 from outside of the separation 212. For example, the replicate display device 216 may be mounted inside of a room of a hospital, facing outward, or alternatively mounted outside of the room. In either of these examples, the replicate GUI 220 of the replicate display device 216 may be viewable from outside of the room by a clinician using a remote device 226. In a further example, the replicate display device 216 and the remote device 226 may be proximate one another, such that a user of the remote device 226 may track the replicate position indicator 222 on the replicate GUI 220 (replicated from the local ventilator position indicator 208 on the ventilator GUI 206) as the user moves the trackpad (also moving the remote position indicator 232).

The remote device 226 may include a remote display 228 with a remote GUI 230. The remote device 226 may be similar to the remote devices 160, 194 described in FIGS. 1B and 1C. For example, the remote GUI 230 may include a remote position indicator 232 based on remote past movement data 234. The remote GUI 230 may also include a first remote adjustment element 236 and a second remote adjustment element 238, which may allow a virtual adjustment of a physical input component 129 of the ventilator 100. For example, first remote adjustment element 236 and the second remote adjustment element 238 may be a variety of inputs, including a virtual numerical input, a slider bar, a dial, a wheel, an arrow, an up/down control, a voice input, a haptic input, etc. While the remote adjustment element 236 and the second remote adjustment element 238 are generally virtual elements displayed in a GUI, in some examples, the remote adjustment element 236 and/or the second remote adjustment element 238 may be a physical element (such as a physical dial) that is incorporated on the remote device 226. In an example, the first remote adjustment element 236 and the second remote adjustment element 238 may be different. For example, the first remote adjustment element 236 may be a dial and the second remote adjustment element 238 may be up/down controls.

In use, the remote device receives position and selection input from a user which corresponding to a ventilator setting. That position and selection input is sent to the ventilator, which causes the ventilator setting to be selected. Once that setting is selected, the user can interact with the remote adjustment elements 236, 238 to adjust the setting. The interactions with the remote adjustment elements are transmitted as adjustment data to the ventilator to change the setting.

Additionally or alternatively to the first remote GUI 163 or the second remote GUI 198 described in FIG. 1B, the remote GUI 230 of the remote device 226 may include a virtual trackpad. In an example where the remote GUI 230 is, or includes, a virtual trackpad, the remote GUI 230 may include a portion of the remote GUI 230 to appear blank or otherwise lack any user interface elements. As an example, all or a portion of the elements displayed on the replicate GUI 220 may be displayed on a portion of the remote GUI 230. In an example, a portion of the replicate GUI 220 may be displayed on the remote GUI 230 adjacent to a trackpad. The virtual trackpad may allow for a remote position indicator 232 on the remote device 226 to be correlated with the local ventilator position indicator 208 on the ventilator 202. The correlated position information, based on a position input, may be sent to the ventilator 202 over the wired or wireless connection 214B. The position input may be a time-varying user input.

Correlation of the remote position indicator 232 with the local ventilator position indicator 208 may be determined based on a one-to-one overlay and/or may be movement-based. In an example where the direct correlation is an overlay, there may be a one-to-one mapping of x-y coordinates on the remote GUI 230 with x-y coordinates on the ventilator GUI 206. As a further example, a one-to-one overlay may occur where the ventilator GUI 206 is replicated on the remote GUI 230 of the remote device 226. Accordingly, an input at a remote position indicator 232 on the remote GUI 230 may have a direct correspondence with a local ventilator position indicator 208 on the ventilator GUI 206. In an example where the direct correlation is movement based, remote past movement data 234 on the remote GUI 230 may be associated with a local ventilator past movement data 210. For example, the local ventilator position indicator 208 may change location or position on the ventilator GUI 206 based on the remote past movement data 234, irrespective of an x-y coordinate of the remote past movement data 234. For instance, the starting position of the remote past movement data 234 may be zeroed for the local ventilator position indicator 208. As an example, dragging the remote position indicator 232 on the virtual trackpad causes a corresponding movement of the local ventilator position indicator 208.

The features of the remote GUI 230 may have various advantages. For example, the use of a virtual trackpad allows for the transmission of position and click (or gesture) information, rather than commands for specific setting types and values for those settings. Additionally, correlation of inputs to a virtual trackpad may reduce translation requirements and errors in data signals sent from the remote device 226 to the ventilator 202, because the remote device is responsible only for the trackpad data (positions, clicks, gestures) and not specific ventilator settings such as breath modes, etc. (for which the ventilator remains responsible). As another example, a virtual trackpad may not need to be device-specific and may have a faster learning curve for users. Alternatively, a remote GUI with user interface elements (such as the remote GUI 198 described in FIG. 1B) may also have advantages. For example, a remote GUI with user interface elements may not require a replicate display device 216 and may lower the amount of time and/or energy of a user comparing an input with a replicate display 218 to understand what is happening on the ventilator 202. Thus, aspects of the present technology may include one or more features of each example of the remote GUI 230, 163.

In the system 200A shown in FIG. 2A, the remote device 226 may receive an input associated with the remote GUI 230. The input may be a movement of the remote position indicator 232 over time, a selection input at the remote position indicator 232 at a position, an adjustment input of a remote adjustment element 236, 238 at the remote position indicator 232 over time or at one point in time, or any other user input at the remote GUI 230. The remote position indicator 232 may be displayed on the remote GUI 230. The remote device 226 may determine input information to send to the ventilator 202 over the connection 214B. The input information may include remote position and/or coordinate information, movement information, selection information, or adjustment information, based on the input received at the remote device 226. The ventilator 202 may receive the input information and determine an associated ventilator input. For example, the ventilator input associated with movement information may be moving a local ventilator position indicator 208 displayed on the ventilator GUI 206. As another example, the ventilator input associated with selection information may be selecting a ventilator control element displayed on the ventilator GUI 206. As a further example, the ventilator input associated with adjustment information may be adjusting a value or values associated with a selected ventilator control element.

The ventilator may update one or more ventilation settings associated with the ventilator input, and/or update the ventilator GUI 206 based on the ventilator input (e.g., moving a local ventilator position indicator 208, selecting a ventilator control element on the ventilator GUI 206, or adjusting a selected ventilator control element). As the ventilator 202 updates the ventilator GUI 206, the ventilator 202 may send update information to the replicate display device 216 and/or the remote device 226 over the wired or wireless connections 214A, 214B. The update information may include display information used to replicate all or a portion of the ventilator GUI 206 and/or value information associated with a change in a value of a selected ventilator control element. The display information may include local ventilator position indicator 208. The local ventilator position indicator 208 may be displayed on the ventilator GUI 206 and/or the replicate GUI 220. In an example, the local ventilator position indicator 208 may be displayed on the replicate GUI 220, but not the ventilator GUI 206.

In an example, the remote device 226 and/or replicate display device 216 may be dedicated to, or specific to, one ventilator 202, or may be capable of communicating with a plurality of ventilators 202 over one or more separations 212. In this example, the remote device 226 may be portable. The remote device 226 and/or replicate display device 216 may also be a part of a central monitoring system communicatively coupled with a plurality of ventilators in one or more facilities. In another example, the replicate display device 216 may be specific to one ventilator 202 while the remote device 226 may be capable of communicating with multiple ventilators. As a further example, the remote device 226 may be specific to one ventilator 202 while the replicate display device 216 may be capable of receiving display information from multiple ventilators. In a further example, both the replicate display device 216 and the remote device 226 are specific to one ventilator 202.

FIG. 2B depicts another example system 200B for remote adjustment of a ventilator 202 based on a time-varying user input received at a remote device 226. System 200B is similar to system 200A, with the exception of an intermediate device 240, such as a relay transceiver or remote-control accessory, which may be located communicatively between the ventilator 202 and the remote device 226 to relay communications. The intermediate device 240 may have similar computing components as remote devices 160, 194, 226 described in FIGS. 1B, 1C, and 2A. Intermediate device 240 may be proximate to the ventilator 202, such as located inside the separation 212. Intermediate device 240 may receive data from remote device 226 over wired or wireless connection 214C. The intermediate device 240 may then relay the data to the ventilator 202 over wired or wireless connection 214B. The intermediate device 240 may act as a relay and/or translator to process or translate the data received from the remote device 226 prior to relaying processed data to the ventilator 202. For instance, the intermediate device 240 may translate the selection and position information received from the remote device 226 into a format that can be processed by the ventilator 202. In another example, the intermediate device 240 may be controlled by the remote device 226 similar to how the remote device 226 controls the ventilator 202 in FIGS. 1B and 2A. In an example, the intermediate device 240 may be specific to one ventilator 202 or may be capable of communicating with multiple ventilators 202. In another example, the intermediate device 240 is specific to one ventilator 202 while the remote device 226 may be capable of communicating with multiple ventilators 202 via multiple intermediate devices 240. For example, a first ventilator may have a wired connection with a first intermediate device and a second ventilator may have a wired connection with a second intermediate device and a remote device may be capable of controlling the first intermediate device and the second intermediate device via a wireless connection. In a further example, the intermediate device 240 may have a wired connection 214B with the ventilator 100 to facilitate a wireless connection 214C between the intermediate device 240 and the remote device 226.

FIG. 2C depicts another example system 200C for remote adjustment of a ventilator 202 based on a time-varying user input received at a remote device 226. System 200C is similar to system 200B, with the exception of no replicate display device 216 and the remote GUI 230 including a remote trackpad GUI 230A and remote replicate display GUI 230B side by side on the same display. In this example, the replicate GUI 220 may be displayed on the remote replicate display GUI 230B, thus rendering a replicate display device 216 redundant. In this system 200C, as the ventilator 202 updates the ventilator GUI 206 (concurrently or after updating), the ventilator 202 may send update information (e.g., display information and/or value information) to the intermediate device 240 over the wired or wireless connection 214B, which may relay the update information to the remote device 226 over the wired or wireless connection 214C.

FIG. 3 depicts an example method 300 for remotely adjusting a ventilator (e.g., ventilator 100, 202) based on a time-varying user input received at a remote device (e.g., remote device 160, 194, 226). The operations of method 300 may be performed by the ventilator and/or other components described in the above systems. At operation 302 the ventilator displays, on a display (e.g., display 122, 204), a ventilator user interface (e.g., ventilator GUI 123, 206) comprising a ventilator control element. There may be a plurality of ventilator control elements each associated with different ventilation settings. For example, a ventilator control element may be a graphical element for adjusting settings or entering data. For example, the settings or data may include a new patient entry, a stored patient entry, setup information (such as predicted body weight, gender, height, or other patient information), ventilation type (e.g., invasive, NIV, HFO₂T), mode (e.g., A/C, SIMV, SPONT, BiLevel, CPAP), mandatory type (e.g., PC, VC, VC+), spontaneous type (e.g., PS, TC, VS, PAV+), trigger type (e.g., P-Trig, V-Trig, IE Sync), respiratory rate (f), tidal volume (VT), peak inspiratory flow ({dot over (V)}_MAX), flow sensitivity ({dot over (V)}_SENS), oxygen concentration (O₂%), peak circuit pressure (P_PEAK), plateau time (T_PL), positive end-expiratory pressure (PEEP), rise time percent (P), inspiratory time (T₁), inspiratory pressure (P₁), start ventilation control, cancel control, alarm settings, menu control, or any other selectable or controllable user interface element that may be display on a ventilator user interface. As a further example, the ventilator control element on the ventilator GUI may be another type of user interface element, such as an icon, a control, a checkbox, a radio button, a dropdown list, a button, a toggle, a text field, a slider, a page tab, a search field, a tag, etc. In an example (as further shown in FIGS. 5A and 5B), the ventilator control element may be an icon representing inspiratory time (T₁). The ventilator control element representing inspiratory time may be selectable and include an adjustable value. For example, the value associated with the inspiratory time may be 0.40 seconds.

At operation 304, the ventilator receives, from a remote device, selection data including position information and selection information. In an example, the selection data may be received over a wired or wireless connection (such as connections 164, 192, 214A, 214B, 214C). As an example, the position information may be associated with a remote position indicator (such as remote position indicators 165, 199, 232) and/or a local ventilator position indicator (such as local ventilator position indicators 127, 208). As described herein, the position information may be correlated between coordinates of the remote device user interface and the ventilator user interface. Selection information may be any information associated with a selection (e.g., activation or click) of a ventilator user interface element at the position indicated by the position information. It should also be appreciated that the ventilator may receive separate data for position information and/or selection information. In an example, position data may include position information related to a change in position of a remote position indicator (such as a movement shown by past movement data 210 and/or remote past movement data 234). The position information may or may not be associated with selection information (e.g., when a remote position indicator moves without a selection). In another example, selection data may include selection information without position information (e.g., when a mouse is clicked without moving). In this example, the selection information may be associated with a current position indicator on the ventilator.

At operation 306, the ventilator determines a selection of the ventilator control element based on received selection data. For example, if the position information and the selection information associated with a local ventilator position indicator are associated with (correspond with or are correlated with) coordinates of a ventilator control element on the ventilator user interface, then the associated ventilator control element may be selected by the ventilator. As a further example, a ventilator control element representing inspiratory time (T₁) may be associated with a set of coordinates or a region on the ventilator GUI. In this example, the ventilator control element representing inspiratory time is selected when the position information of the selection is associated with the set of coordinates of region on the ventilator GUI associated with the ventilator control element.

At operation 308, the ventilator displays, on the user interface, a value associated with the selected ventilator control element. In a further example, the ventilator may also display an indication of the selected ventilator control element. An indication of the selected ventilator control element may include bolding, highlighting, blinking, resizing, replicating, or any other form of emphasizing the ventilator control element. The value associated with the selected ventilator control element may be a selectable, scalable, adjustable, or otherwise variable. The value may be displayed on, or as a part of, the ventilator control element. Additionally or alternatively, the value may be displayed in another location on the user interface of the ventilator. In another example, a local ventilator position indicator may be displayed. Continuing the above example where the ventilator control element represents inspiratory time (T₁), the ventilator control element may be emphasized on the ventilator GUI, for example by bolding, highlighting, etc., and the value of 0.40 seconds associated with the inspiratory time may be adjustable.

At operation 310, the ventilator receives, from the remote device, adjustment data. The adjustment data is generated from interactions with the remote adjustment elements (e.g., dial, up/down buttons). The adjustment data is associated with the selected ventilator control element. The adjustment data may be correlated with an adjustment on the ventilator (via the user interface, or via physical input at a physical input component, such as physical input component 129) and an adjustment on the remote device. For instance, rotation of the virtual dial generates adjustment data that may correspond to the same type of rotation on the physical dial of the ventilator.

At operation 312, based on the adjustment data, the ventilator determines a change in the value associated with the selected ventilator control element. Continuing the example where the ventilator control element represents inspiratory time (T₁), the value may be adjustable at the ventilator based on a physical input at a physical input component (such as an angle of rotation of a dial). The adjustment information may be associated with a virtual rotation of a virtual dial (as received at the remote device via a time-varying user input, transmitted through selection data and/or adjustment data), which may correspond with the physical input at the physical input component on the ventilator. Thus, the adjustment data may correspond with a change in the value (e.g., an inspiratory time of 0.40 seconds may be changed to 0.30 seconds).

At operation 314, the ventilator displays, on the user interface, the change in the value. For example, the ventilator may show the change by displaying the updated/changed value, the previous value, a change or difference in the value, or a combination. Additionally or alternatively, the updated value may be associated with an indication that the value was changed. Continuing the example where the ventilator control element represents inspiratory time (T₁), and the value is changing from 0.40 seconds to 0.30 seconds, the ventilator may display the new value (0.30 seconds), an indication that the value recently changed, the prior value (0.40 seconds), and/or the change in the value (0.10 seconds). At operation 316, the ventilator updates a ventilation setting based on the change in the value. Ventilation settings, or ventilatory settings, are described further in FIG. 1A. For example, the ventilator may update the inspiratory time, or the time that flow is commanded into the breathing circuit, from 0.40 seconds to 0.30 seconds. Ventilation of the patient is then provided based on the changed value(s) for the ventilation setting(s).

One or more operations of method 300 may repeat. For example, operations 304-308 may repeat as new selection data is received from the remote device. For example, the ventilator may de-select the ventilator control element associated with inspiratory time (T₁) and may instead select a ventilator control element associated with PEEP. As another example, operations 310-216 may repeat as different adjustment data is received from the remote device for a same selected ventilator control element. For example, the ventilator may receive a further adjustment to the inspiratory time value, such as further changing the value from 0.30 seconds to 0.35 seconds, in the above example. In a further example, operations 304-316 may repeat for new selection data and associated adjustment data received from the remote device for a different selected ventilator control element. For example, the ventilator may de-select the ventilator control element associated with inspiratory time (T₁) and may instead select a ventilator control element associated with PEEP, thereafter receiving adjustment data to adjust the value associated with the PEEP ventilator control element.

FIG. 4 depicts a method 400 for remotely adjusting a ventilator (such as ventilators 100, 202) based on an input received at a remote device (e.g., remote devices 160, 194, 226). The operations of method 400 may be performed by the remote device and/or other components described in the above systems. At operation 402, the remote device may display a remote user interface (such as remote GUIs 163, 198, 230). The remote user interface may include a virtual trackpad, a remote replicate display (which may be interactive) which may show one or more features of a ventilator user interface, a remote adjustment element, or any combination thereof, as described herein. In an example, the remote adjustment element may be a virtual dial associated with a physical dial on the ventilator.

At operation 404, the remote device receives, at the remote user interface, an input comprising an input position, with associated position information, and an input selection, with associated selection information. The input may be received at a touchscreen of the remote user interface, or otherwise received via user interaction with the remote device. The input position may be associated with the remote position indicator (such as remote position indicators 165, 199) on the remote user interface of the remote device. At operation 406, the remote device may send to the ventilator, selection data based on the input position and the input selection. In an example (as further shown in FIGS. 5A and 5B), the selection received at the remote device may correspond with a ventilator control element on the ventilator GUI.

At operation 408, the remote device may receive, from the ventilator, a selection indication of a selected ventilator control element associated with the selection data. In an example where the remote user interface includes a replicate display including the ventilator control element, the replicate display may be updated based on the selection indication.

In another example, the selection indication may cause the remote device to allow adjustment to a remote adjustment element (such as remote adjustment element 236, 238). As a further example, the remote adjustment element may (e.g., virtual dial) be disabled when the selection indication indicates that a ventilator control element is not selected (e.g., upon receiving a de-selection indication or prior to receiving a selection indication), and enabled when the selection indication indicates that the ventilator control element is selected.

Continuing the above example where the selected ventilator control element represents inspiratory time (T₁), the remote GUI may display an indication that “inspiratory time” is selected and/or display the current value of 0.40 seconds. The virtual dial may be enabled after receiving a selection indication of a selected ventilator control element from the ventilator. The virtual dial may be disabled when there is no ventilator control element selected at the ventilator (as determined from one or more selection indications received from the ventilator).

At operation 410, the remote device receives, at the remote user interface, an adjustment input associated with the selected ventilator control element (e.g., virtual dial). The adjustment input may be received via user interaction with a remote adjustment element (such as remote adjustment elements 236, 238) at one time or over a period of time. Additionally, or alternatively, the adjustment input may be received as a variety of input forms, such as numerical, slide, dial, wheel, arrow, up/down control, voice, haptic, etc. The adjustment input is associated with a change in a value associated with the selected ventilator control element. A greater change in the adjustment input (e.g., larger rotation of the dial) may be associated with a greater change in the value. The adjustment input may also be a scroll of a mouse wheel or a swipe of a screen via touch input.

At operation 412, the remote device sends, to the ventilator, adjustment data based on the adjustment input. Continuing the above example where the ventilator control element represents inspiratory time (T₁), the adjustment input may be a rotation of a virtual dial on the remote GUI over time to change the inspiratory time value as if a physical dial were being rotated on the ventilator. In an example, the change in the value may be based on the angle of rotation of the virtual dial, with a positive or negative angle indicating direction. For example, the rotation of the virtual dial may include position and selection information associated with the virtual dial over a period of time. Alternatively, the adjustment input may be a selection of an adjustment icon (e.g., Up/Down icon) at a point in time. In this example, each selection of the adjustment icon may change the value by a predetermined amount, such that more selections of the adjustment icon (or selecting the adjustment icon over a period of time) may result in a greater change in the value.

At operation 414, the remote device may receive, from the ventilator, a change indication of a change in a value associated with the selected ventilator control element. Based on the change indication, the remote device may show, on the remote user interface, the updated/changed value, the previous value, a change or difference in the value, or a combination. Continuing the above example where the ventilator control element represents inspiratory time (T₁), the change indication may include information that the value associated with inspiratory time has changed (e.g., from 0.40 seconds to 0.30 seconds). The remote GUI may display the new value (0.30 seconds), an indication that the value recently changed, the prior value (0.40 seconds), and/or the change in the value (0.10 seconds).

One or more operations of method 400 may repeat. For example, operations 404-408 may repeat as a new selection or position input is received at the remote device. For example, the remote device may send a de-selection to de-select the ventilator control element associated with inspiratory time (T₁). Alternatively, a selected ventilator control element may be automatically de-selected upon receiving selection data at the ventilator to select a different ventilator control element (e.g., associated with PEEP). As another example, operations 410-414 may repeat as different adjustment inputs are received at the remote device for a same selected ventilator control element. For example, the remote device may receive a further adjustment input to the inspiratory time value, such as further rotating a virtual dial to change the value at the ventilator from 0.30 seconds to 0.35 seconds, in the above example. In a further example, operations 404-414 may repeat for new selection inputs, new position inputs, and new adjustment inputs received at the remote device for a different selected ventilator control element. For example, the remote device may send selection data to de-select the ventilator control element associated with inspiratory time (T₁), and instead select a ventilator control element associated with PEEP. The adjustment input may then adjust a value associated with a ventilator control element representing PEEP.

FIGS. 5A and 5B depict an example remote user interface 524 on a remote display 522 of a remote device 520, and a ventilator display 504 of a ventilator 502 showing a ventilator user interface 506. Aspects of FIGS. 5A and 5B show changing a value associated with a selected ventilator control element 518 of available ventilator control elements 512. Specifically, FIGS. 5A and 5B show a remote user interface 524 and ventilator user interface 506. The local ventilator position indicator 508 is associated with the remote position indicator 526, and may have associated past movement data 510, 528. In FIG. 5A, a particular ventilator setting (the control element 518) is selected, and in FIG. 5B it is adjusted.

For example, FIG. 5B shows the remote position indicator 526 rotating a virtual dial 530. The virtual dial 530 may be associated with a physical dial 516 on the ventilator (such as physical input component 129). Although a dial is used in this example, it should be appreciated that other virtual adjustment elements (such as soft key or button 534) may be displayed on the remote user interface 524 to be associated with a variety of physical input components (such as hard keys 514). In this way, a virtual input at the virtual dial 530 or soft key 534 may be associated with a physical input on a ventilator 502. An adjustment of the virtual dial 530 may be equivalent to an adjustment of the physical dial 516. The remote adjustment element 530, 534 may be overlaid or separate from the trackpad or elements of the remote user interface 524. In either example, the remote adjustment element 530, 534 may be positioned on the remote user interface 524 to not overlap with ventilator control elements 512 and/or disable selection of a ventilator control element 512 when receiving an adjustment input.

In this example, the adjustment input is a counterclockwise rotation (a negative angle of rotation) of the virtual dial 530 from a first position 532A to a second position 532B. The difference between the first position 532A and the second position 532B may be proportional to the change in the value associated with the selected ventilator control element 518. For example, the difference between the first position 532A and the second position 532B on virtual dial 530 may be an angle of rotation. The direction of rotation of the virtual dial 530 may represent a positive or negative change in the value. In this example, the selected ventilator control element 518 is adjusted from 0.40 s to 0.30 s, based on the angle of counterclockwise rotation between the first adjustment 532A and the second position 532B. As shown, the local ventilator position indicator 508 may have a past movement data 510 associated with the remote past movement data 528 on the remote user interface 524. In this case, the virtual dial 530 is positioned in an adjustment section 542B of the remote user interface 524 to correlate with a non-selectable region 542A of the ventilator user interface 506 to prevent unintended selection of a different ventilator control element 512 when receiving adjustment input. For example, when a remote position indicator 526 is positioned inside of the adjustment section 542B, the local ventilator position indicator 508 does not overlay with any ventilator control element 512. In this way, a selection of an adjustment element (e.g., the virtual dial 530) inside of the adjustment section 542B is not also associated with a selection of a ventilator control element 512.

In a further example, an adjustment caused by a mouse scroll or other input action at the remote device 520 may be visually indicated at the remote user interface 524. For instance, if a mouse scroll is received at the remote device 520 then a visual indication of a value adjustment may be shown on the remote user interface 524 (e.g., rotation of the virtual dial, varying color, varying brightness, otherwise emphasizing all or a portion of one or more bezel keys 536, a change in a displayed numerical value, etc.). Although examples describe rotation of a mouse wheel, it should be appreciated that any other input at the remote device 520 associated with a control at the ventilator (e.g., a local ventilator position indicator 508 is hovered-over the control or the control is selected) may result in an adjustment of the value associated with the control at the ventilator.

FIG. 5C depicts an example remote user interface 524 on a remote display 522 of a remote device 520. As shown, the remote user interface 524 may include a first interface portion 525A and a second interface portion 525B. As shown, the first interface portion 525A and the second interface portion 525B are displayed in separate portions, segments, or windows of the remote user interface 524. The portions, segments, or windows may be resizeable and repositionable about the remote user interface 524. Additionally or alternatively, the remote user interface 524 may split display of the first interface portion 525A and the second interface portion 525B (e.g., in a split screen arrangement), and/or the first interface portion 525A and the second interface portion 525B may be overlaid. Other visual arrangements of the first interface portion 525A and the second interface portion 525B are also possible.

In an example, the first interface portion 525A may replicate a ventilator GUI (e.g., ventilator GUI 123) and user interface elements in the first interface portion 525A may not be selectable. The second interface portion 525B may include selectable and/or interactive user interface elements. For example, the second interface portion 525B may include features or elements similar to remote user interfaces (e.g., remote GUIs 163, 198, 230, 524) described herein. In this example, the second interface portion 525B may include a set of GUI control keys 536, a trackpad 538, and a remote position indicator 526. The set of GUI control keys 536 may include one or more control keys (or virtual bezel keys), such as a display brightness key, a display lock key, an alarm volume key, a manual inspiration key, an inspiratory pause key, an expiratory pause key, an alarm reset key, an audio paused key, etc. Each GUI control key in the set of GUI control keys 536 is associated with a control on the ventilator to which the remote device 520 is connected for remote control. In an example, the GUI control key may be associated with a ventilator GUI element. In another example, the GUI control key may be associated with a physical input at the ventilator. For example, a virtual dial 530 may be included in the set of GUI control keys 536 as associated with a physical input, as further described herein.

In an example, when a GUI control key in the set of GUI control keys 536 is selected at the remote user interface 524, the virtual dial 530 may then be selected and adjusted to adjust a value associated with the selected GUI control key at the ventilator. For example, a display brightness key may be selected. While the display brightness key is selected at the remote user interface 524, the virtual dial 530 may be adjusted and/or up/down adjustment keys may be selected to adjust or change the screen brightness value of the ventilator. In another example, an alarm volume key may be selected at the remote user interface 524 to adjust a volume value associated with the alarm at the ventilator. While the alarm volume key is selected, the volume value may be adjusted via interaction with the virtual dial 530 and/or up/down keys at the remote user interface 524.

In another example, a display lock key may be selected at the remote user interface 524 to prevent inadvertent settings changes to the ventilator (including the knob function) while the display is locked. In a further example, a manual inspiration key may be selected at the remote user interface 524. In examples, the manual inspiration key can be used to deliver mandatory breaths to the patient and/or to run an inspiratory pause maneuver in SPONT mode. In another example, selection of an inspiratory pause key at the remote user interface 524 may initiate an inspiratory pause maneuver at the ventilator. This may close the inspiratory and exhalation valves and extend the inspiratory phase of a mandatory breath for the purposes of measuring end inspiratory pressure for calculation of plateau pressure, static compliance, and static resistance. In a further example, selecting an expiratory pause key at the remote user interface 524 may initiate an expiratory pause maneuver at the ventilator, which may extend the expiratory phase of the current breath to measure total PEEP (PEEP_TOT). In another example, an alarm reset key may be selected at the remote user interface 524 to clear active alarms and/or reset high-priority alarms and/or cancel an active audio paused interval at the ventilator. In yet another example, selection of an audio paused key at the remote user interface 524 may pause alarms for a predetermined period of time at the ventilator.

In examples, the remote device 520 may replicate the ventilator GUI at the first interface portion 525A. The first interface portion 525A may include a replicate position indicator 540, replicating the local ventilator position indicator at the ventilator GUI. In this example, a clinician may interact with the trackpad 538 of the remote user interface 524 of the remote device 520 to control the ventilator without directly seeing the ventilator GUI. The clinician controlling the ventilator at the trackpad 538 may visually compare a remote position indicator 526 with the replicated display shown in the first interface portion 525A of the remote user interface 524 on the same remote device 520, without requiring a direct view of the ventilator GUI at the ventilator.

The remote user interface 524 may include additional information or controls associated with the remote device 520, connected ventilator, and/or data received or sent by the remote device 520. As shown, this additional information may be displayed at the second interface portion 525B. For example, the remote user interface 524 may include a disconnect key to disconnect for a ventilator and/or switch to control of a different ventilator. As another example, the remote user interface 524 may display additional, non-selectable information including a value associated with a currently selected GUI element and/or bezel key, a determine adjustment or change in the value, position information of a physical input at the ventilator, etc. For example, the remote user interface 524 may include a disconnect control to disconnect the remote device 520 from the ventilator and/or an intermediate device. In another example, the remote user interface 524 may include a serial number of the ventilator, X-Y coordinates of the remote position indicator 526 (e.g., X-Y coordinates at the remote user interface 524, X-Y coordinates at the ventilator GUI, and/or X-Y coordinates at an intermediate device GUI). Additionally or alternatively, the remote user interface 524 may include other system information (e.g., IP address, port, etc.).

FIG. 6 depicts a method 600 for remotely adjusting and/or accessing a ventilator (such as ventilators 100, 202, 502) based on an input received at a remote device (e.g., remote devices 160, 194, 226, 520). The operations of method 600 may be performed by the remote device and/or other components described in the above systems. At operation 602, a remote computing device may be connected to a ventilator, via a wired or wireless connection (e.g., wired or wireless connections 164, 192, 185, 214A, 214B, 214C), the ventilator having a ventilator display (e.g., ventilator displays 122, 204, 504). At operation 604, a view of the ventilator display may be provided on the remote computing device. For example, the view may be a replicate or copy of the ventilator display in a remote GUI (e.g., remote GUIs 163, 198, 230), such as described for the first interface portion 525A in remote user interface 524.

At operation 606, cursor movement and activations may be tracked on the remote computing device (e.g., via remote position indicator 165, 199, 232, 526). Cursor movement may be associated with a change in position of the cursor (e.g., as described for remote past movement data 234, 528). An activation may include a variety of interactions at the remote computing device, such as a selection (e.g., described herein at least with respect to selection input, selection information, and selection data) and/or an adjustment (e.g., described herein at least with respect to adjustment input, adjustment element, adjustment information, and adjustment data). The activation may include an interaction that is associated with an interaction at the ventilator.

At operation 608, the cursor movements may be overlaid on the view of the ventilator display and displayed on the remote computing device. In an example, the view of the ventilator display may be updated continually based on display information of the ventilator. In another example, operation 608 may be updated with operation 604, as the view of the ventilator display is provided. In another example, operation 608 may be based on a predetermined correlation of the view of the ventilator display with a cursor position at the remote computing device. Alternatively, cursor movements on the view of the ventilator display may be displayed without receiving information from the ventilator (e.g., the remote device may estimate the cursor position).

At operation 610, the cursor activation may be transmitted to the ventilator, via the wired or wireless connection. As described herein, the cursor activation at the remote device may be associated with a cursor activation at the ventilator at the position indicated on the view of the ventilator screen at the remote device. Thus, interactions at the remote device may control or adjust the ventilator over the wired or wireless connection.

One or more operations of method 600 may repeat. For example, operations 604-610 may repeat as the ventilator display changes or updates. For example, the ventilator display may change or update based on the cursor activations sent to the ventilator.

FIGS. 7A, 7B, 7C, and 7D depict example view modes of remote user interfaces 700A, 700B, 700C, 700D on a remote display 701 of a remote device. Specifically, FIGS. 7A, 7B, and 7C show different view modes of a remote user interface 700A, 700B, 700C in a window displayed on a remote device and FIG. 7D shows an example window with a setup view mode of a remote user interface 700D on a display 701 of a remote device. The view modes may be associated with an application running on the remote device in communication with a relay transceiver (e.g., relay transceivers described with respect to FIGS. 8A, 8B, and 9).

Regarding FIGS. 7A, 7B, and 7C, a remote user interface can operate in a ventilator view mode (FIG. 7A), in a patient view mode (FIG. 7B), and in a ventilator and patient inset view mode (FIG. 7C). These views are displayed on a display 701 of a remote device (e.g., a device located remote from the ventilator, such as outside of the room in which a ventilator is located). For example, a remote user interface 700A in a ventilator view mode shows a remote ventilator user interface (UI) 702 replicated from the ventilator GUI. The remote ventilator UI 702 may replicate an entire GUI displayed on a ventilator or may replicate a portion of the ventilator GUI. In some examples, at least 80 or 90 percent of the ventilator GUI (in terms of screen area) is replicated in the remote ventilator UI 702. The remote ventilator UI 702 includes at least one ventilator settings icon that is selectable at the remote ventilator UI 702 and/or the ventilator GUI. As shown in FIG. 7A, ventilator settings icons include respiratory rate (f), inhalation time, exhalation time, volume of synchronized intermittent mandatory ventilation (Vsimv), inhalation-to-exhalation (I:E) ratio, tidal volume, ventilation type, alarm settings, among other settings shown or not shown in FIG. 7A that are selectable on a GUI of a ventilator.

The remote ventilator UI 702 may be rearranged and/or reformatted based on the size of a display 701 of the remote device or a size of the window or panel displaying the remote ventilator UI 702. For example, at least one ventilator settings icon may be rearranged or reformatted (e.g., enlarged). The portion of the ventilator GUI displayed at the remote device may be a cropped portion of the ventilator GUI or one or more ventilator settings icons (including a subset of the ventilator settings icons displayed on the ventilator GUI). In an example, a subset of ventilator settings icons displayed at the remote ventilator UI 702 may change over time, such as being scrolled manually or automatically, or replaced at a time interval. One or more ventilator settings icons may be resized (e.g., enlarge, shrink, change an aspect ratio, change a shape, etc.) compared to other replicated aspects of the ventilator GUI. As an example, ventilator settings icons that are most frequently changed may be enlarged as compared to other ventilator settings icons. In some examples, the least frequently changed settings may be omitted from the remote ventilator GUI 702 or included at the end of a scrollable interface. A format or arrangement of the remote ventilator UI 702 may be based on threshold of the display size. For example, a first format or first arrangement may be displayed if a display size is less than a threshold and a second format or second arrangement may be displayed if the display size is greater than or equal to the threshold.

A patient view mode of a remote user interface 700B shows a patient video feed 722 (or a patient image 722) obtained via a video or camera input (e.g., as received as input into a relay transceiver or the ventilator). A ventilator and patient inset view mode of a remote user interface 700C shows a patient inset remote ventilator UI 724 including a small version of the patient video feed 722.

All three of the example view modes shown on the remote user interface 700A, 700B, 700C (e.g., the ventilator view mode, the patient view mode, and the ventilator and patient inset view mode) may include additional sections, such as a selection section (represented by panel 704) and an adjustment section (represented by panel 706), that may remain unchanged regardless of the view mode. These panels 704, 706 are used to display information or graphical elements that remain available in all view modes.

The panels 704, 706 may be located on any region or section in the remote user interface 700A, 700B, 700C, which may be separate or combined. For example, as shown in FIGS. 7A, 7B, and 7C, the panel 704 is positioned on a left panel of the remote user interface 700A, 700B, 700C and the panel 706 is positioned on a right panel of the remote user interface 700A, 700B, 700C. Panel sizes, positions, formats, or arrangements may be based on a size of the display 701 and/or a size of the window displaying the remote user interface 700A, 700B, 700C, 700D. Panels may be expandable or capable of being minimized and enlarged or expanded.

In an embodiment, the panel 704 is an icon panel that includes a variety of selectable icons not displayed on a ventilator GUI of the actual ventilator itself. For example, the icon panel 704 may include a connect or disconnect button 708 that is selectable (e.g., via touch on a touchscreen display or via a mouse click on a mouse-controlled display). When the remote device is connected to a ventilator, selection of the disconnect button 708 may cause the remote device to disconnect from the ventilator or relay transceiver. When the remote device is not connected to a ventilator or relay transceiver, the connect button 708 may be selected to connect to a ventilator or launch a connection routine to connect to a ventilator or relay transceiver. The connect or disconnect button 708 may indicate if a connection between the remote device and a relay transceiver is stable. For instance, the display of the connect or disconnect button 708 may change based on the connection status.

Information 710 may be displayed in the icon panel 704, or in any other area of the view, to provide status information (e.g., information that indicates whether the remote device is connected to a ventilator or relay transceiver, the remote device is disconnected from a ventilator or relay transceiver, the remote device is connected with view-only access, with view and control access, etc.). Additionally, the information 710 displayed may include ventilator identification information, relay transceiver identification information, patent identification information, and/or remote device identification information. Ventilator identification information may include a ventilator serial number, a room number or site identifier of the ventilator, a name of the ventilator, an IP address of a ventilator, a user to which the ventilator is assigned (e.g., doctor, clinician, medical team, etc.), or any other information specific to a ventilator that is being remotely accessed. Relay transceiver identification information may include a relay transceiver serial number, a room number or site identifier of the relay transceiver, a name of the relay transceiver, an IP address of the relay transceiver, a user to which the relay transceiver is assigned (e.g., doctor, clinician, medical team, etc.), or any other information specific to a relay transceiver for providing remote access to a ventilator by a remote device. Patent identification information may include a patient identifier (e.g., name, initials, bodyweight, gender, etc.), a patient room number or site identifier, a patent infectious code, an anonymized patient identifier, etc. Remote device identification information may include a device serial number, a name of the device, an IP address of the device, a user to which the device is assigned (e.g., doctor, clinician, medical team, etc.), or any other information specific to a remote device remotely accessing a ventilator, or any other remote devices concurrently remotely accessing the ventilator (e.g., via a relay transceiver).

In an embodiment, the icon panel 704 also includes a view selector 712, which allows a user to switch to a different view mode. For example, a selection of the view selector 712 may cause a sequential change in view between the remote user interface 700A in a ventilator view mode, a remote user interface 700B in a patient view mode 700B, and a remote user interface 700C in a ventilator and patient inset view mode. If only two view modes are available, then a selection of the view selector 712 may toggle between the two view modes. Additionally or alternatively, the view selector 712 may allow a user to select which view to show (e.g., via a dropdown menu or other selection menu). The view selector 712 may also allow for camera control where a camera is available. For instance, a camera may be connected to the ventilator and/or the relay transceiver to allow for a view of the patient. The view selector 712 may control the direction of the camera or other camera properties. Selection of the view selector 712 may provide options for rotating the camera and or changing other camera properties (e.g., zoom).

The icon panel 704 may also include one or more virtual bezel keys 714. that correspond with physical bezel keys on the ventilator. Selection of the virtual bezel keys 714 at the remote device represents a physical selection of a bezel key at the ventilator. Descriptions of physical bezel keys and bezel key user interface elements are further discussed with respect to FIG. 5C. The virtual bezel keys 714 may be displayed in any configuration, such as a compact rectangular tile configuration shown in FIGS. 7A, 7B, and 7C.

In an embodiment, the panel 706 is an interactive panel used to accept adjustments of the selected ventilator setting icon (e.g., a selected virtual bezel key 714 or a selected icon). The adjustment section (represented by panel 706) may include one or more adjustment elements (e.g., up icon, down icon, slide bar, rotatable dial, etc.). In FIG. 7A, the panel 706 includes a slide bar 720 with up and down slide icons 716, 718. The slide bar 720 or icons 716, 718 are used to change the selected ventilator setting. For instance, a single selection of the up icon 716 or the down icon 718 may cause a single, stepwise adjustment of the selected ventilator setting in either the upward or downward direction, respectively. Multiple selections of the up icon 716 or the down icon 718 may cause multiple, stepwise adjustments of the selected ventilator setting in either the upward or downward direction, respectively.

The slide bar 720 may adjust a selected ventilator setting based on a select, drag, and drop interaction with the slide bar 720. For example, dragging up on the slide bar 720 may adjust a selected setting upwards and dragging down may adjust a selected setting downwards. This drag action may be performed using a touch interaction or a mouse interaction. The slide bar 720 may vary in incremental adjustments based on an acceleration of a user's drag motion. For example, a setting may be adjusted more quickly (e.g., in larger step increments) for a drag with faster acceleration than a drag with slower acceleration. Alternatively, the slide bar 720 may adjust a setting linearly (e.g., in standardized increments based on distance of a drag motion), regardless of drag acceleration. The slide bar 720 may be a replacement for the functionality described for the virtual dial 530 described in FIGS. 5A, 5B, and 5C. Alternatively, the panel 760 may display the virtual dial 530 instead of or in addition to the slide bar 720. Other types of interactive adjustment UI elements for increasing or decreasing settings may also be utilized.

FIG. 7D shows a display 701 of a remote device in a system view mode of a remote user interface 700D. This view mode includes a settings window 728 (with user settings, access permissions, default views, and preferences) and a selection window 730 showing available relay transceivers and/or ventilators represented by icons 732. The setup view mode of the remote user interface 700D may be displayed when the remote device is not connected to ventilator and/or relay transceiver. For instance, when a clinician or other user first picks up the remote device to interact with a ventilator, the setup view mode of the remote user interface 700D may be displayed to allow for setup and connection to a ventilator. The setup view mode of the remote user interface 700D may also be displayed when a user intends to connect to a different ventilator and/or relay transceiver.

For instance, each icon 732 may correspond to a different ventilator and/or relay transceiver that is available to be controlled or viewed remotely. Each of the icons 732 may be labelled or named with an identifier such as the ventilator identification information, relay transceiver identification information, or patent identification information. A selection indicator (such as box 734) indicates which icon is currently selected.

Additionally or alternatively, a warning message 726 may be displayed prior to allowing selection of a ventilator (via icon 734) for remote access. The warning message 726 may require user action, such as a usage agreement or confirmation.

FIGS. 8A and 8B depict example systems for remotely adjusting a ventilator with a remote device. Specifically, FIG. 8A shows an example system 800A with one ventilator 802 paired with one relay transceiver 808, accessed by multiple remote devices (e.g., laptop 812 and remote server 814 or other remote devices such as a tablet, smartphone, laptop computer, desktop computer, or others) to allow for remote-control of the ventilator 802. FIG. 8B shows an example system 800B with a variety of connections between ventilators, relay transceivers, remote devices, and users.

Referring to FIG. 8A, a ventilator 802 may be paired with a relay transceiver 808 in a one-to-one relationship. The relay transceiver 808 allows for connectivity of one or more remote devices 812, 814 with the ventilator 802. The relay transceiver 808 may be attachable to, or removable from, the ventilator 802. For example, the relay transceiver 808 may plug into a data port (such as an HDMI or USB port) of the ventilator 802 (directly or through an adapter 804), or may communicate with the ventilator wirelessly (directly or through an adapter 804).

The relay transceiver 808 is hardware, and can take the form of a laptop, a miniature computer, processing box (such as a headless computer), a dongle, a smart cable, or other small portable processor. One example relay transceiver 808 may include a NUC PC available from the Intel Corporation. In an embodiment, the relay transceiver 808 is external to the ventilator 802 and is portable such that a clinician may easily move the relay transceiver 808 to different rooms or different ventilators. In some examples, the relay transceiver 808 may have a volume of less than 500 cubic centimeters. Alternatively, the relay transceiver 808 may be embedded, internal, and/or integrated into a ventilator 802.

In an embodiment, the relay transceiver provides the connectivity hardware and software needed for the remote devices 812 and 814, such that no changes (e.g., hardware or software changes) need to be made to the ventilator 802 itself. Thus, the relay transceiver 808 adds remote connectivity functionality to a standalone or offline ventilator 802.

As shown in FIG. 8A, a camera 806 may be paired with a relay transceiver 808 and/or a ventilator 802 to allow a patient video or image to be captured for display on a remote device (e.g., laptop 812 or server 814). The camera 806 may be a webcam, standalone camera, portable camera, USB camera, or other device with video or camera capability. Audio may also be captured and transmitted by the camera 806. Thus, a clinician using a remote device may be able to see and hear the patient.

In some examples, another camera may be integrated into one or more of the remote devices, such as a selfie or front-facing camera on a tablet. The camera may be used to capture video of the clinician, to enable two-way video and/or audio communication between the clinician and the patient, transmitted via the relay transceiver 808.

The relay transceiver 808 allows for access (e.g., view and/or control) to a ventilator 802 to be unbounded by geography or distance. In some examples, remote devices in any location may be given access permissions to connect to a ventilator 802 via the relay transceiver 808. Access may be limited by security credentials and authentication protocols based on a facility's security policies and network configurations. For example, the relay transceiver 808 may implement a lockout feature to prevent setting changes from two or more remote device from occurring simultaneously (e.g., changes are received in sequence or changes may be limited to a quantity of devices allowed to access a relay transceiver in a control mode).

The security policies and access controls may be based on, or managed by, the hospital or medical facility in which the ventilators 802/or relay transceiver 808 are housed. For example, clinicians within, or associated with, the medical facility may be required to log in to the remote devices 812, 814. Logging in to the remote device 812 then provides access to the relay transceiver 808 connected to a particular ventilator 802. For example, once logged into the remote device, the clinician may be able to access the setup view mode of the remote user interface 700D and/or the other remote-control interfaces shown in FIGS. 7A-7D.

The remote server 814 may provide a connection to the Internet 815 to allow for cloud storage or access to the ventilator. Notably, the relay transceiver is not a secondary head or a second UI of the ventilator 802; instead, the relay transceiver 808 provides a path to a laptop, tablet, or other remote device for user interaction.

FIG. 8B shows an example system 800B having a variety of configurations of ventilators (e.g., ventilator 802 and ventilator 803), relay transceivers 808 and 809, remote devices (e.g., laptop 812, tablet 816, laptop 818), and remote users (e.g., user 820 and user 822). As shown, ventilator 802 can be paired with two relay transceivers 808, 809, which each communicate with a subset of the remote devices 812, 816, and 818. The ventilator 803 is paired with a single relay transceiver 809. This figure shows that a single ventilator may be paired with one or more relay transceivers, multiple ventilators may be paired with a single relay transceiver, and multiple ventilators may be paired with multiple relay transceivers.

As also shown in FIG. 8B, the relay transceivers 808, 809 may be configured in a variety of device relationships. Rather than accessibility being limited to one remote device 812, the relay transceivers can authorize or enable connection to multiple remote devices 812, 816, 818. For example, a one-to-many configuration may be permitted for remote devices accessing the ventilator with view-only permissions, while limiting to a one-to-one configuration for remote devices with control or adjustment permissions.

FIG. 8B also depicts a variety of configurations for remote devices and users. For example, a singe remote device (e.g., laptop 812) may be used by a single user (e.g., user 820) in a one-to-one relationship of device-to-user. Additionally, multiple remote devices (e.g., laptop 812 and tablet 816) may be accessed by a single user (e.g., user 820) in a many-to-one relationship. In another configuration, a single remote device (e.g., tablet 816) may be accessed by multiple users (e.g., user 820 and user 822) in a one-to-many relationship. For example, multiple clinicians may share a remote device, such as a tablet assigned to a specific hospital area (wing, ICU, etc.) and/or specific ventilator. The tablet may be passed among users of a medical team, or passed to a different user from shift-to-shift, etc. Further, multiple remote devices may be accessible by multiple users.

The relay transceiver may also store and/or generate usage logs and usage statistics. For example, when a relay transceiver is accessed by a remote device, a remote device identifier (e.g., serial number, IP address, account, etc.) is logged and timestamped in association with a ventilator identifier (e.g., serial number, IP address, name, room number, etc.) of the ventilator(s) being accessed via the relay transceiver. The usage log may also record and store information relating to how many times a remote device accessed the relay transceiver, which virtual bezel keys were selected, which locations in the window were selected (e.g., via touch or mouse-click), etc. Statistics and/or reports may be generated based on a usage log for analysis. For example, statistics and/or reports may provide insight for care givers (e.g., frequency and instances of remote care, use of remote devices, last user to log in, etc.), diagnostics, feature development, security (e.g., cybersecurity considerations), or for any other reason.

FIG. 9 depicts a diagram 900 showing example allocations of relay transceivers (such as relay transceivers 808, 809). As further described herein, relay transceivers may be flexibly paired with ventilators in a care facility (e.g., hospital). The diagram 900 depicted in FIG. 9 shows example relationships between on-site ventilators 902 (e.g., a fleet of ventilators available, maintained, or in use at a care facility or hospital); on-site relay transceivers 904 (e.g., relay transceivers located at the same care facility or hospital as the on-site ventilators 902); on-site assignment 906 (e.g., assignment of an on-site ventilator 902 or on-site relay transceiver 904 to a user located at the same care facility or hospital as the on-site ventilators 902); and remote assignment 908 (e.g., assignment of an on-site relay transceiver 904 to a remote or off-site consultant, transferring patient, etc.). As otherwise used herein, a user may refer to an individual (e.g., a doctor, clinician, etc.) or a team of associated individuals (e.g., multiple users or a team of users, such as a doctor and the doctor's supporting staff/team). Each region of the diagram 900 shown in FIG. 9 represents a different allocation of resources (e.g., on-site ventilators 902 and/or on-site relay transceivers 904).

As shown, the quantity of on-site ventilators 902 and the quantity of on-site relay transceivers 904 may be different. For example, there may be less on-site relay transceivers 904 than on-site ventilators 902 (e.g., the on-site relay transceivers may be paired with some ventilators on a need-basis), or there may be more on-site relay transceivers 904 than on-site ventilators 902 (e.g., to allow remote access capability to at least every ventilator). Alternatively, the quantity of on-site ventilators 902 and the quantity of on-site relay transceivers 904 may be the same.

Region 910 represents on-site ventilators 902 that are not paired with an on-site relay transceiver 904 and are not assigned (e.g., to a user, function, location, etc.). This region 910 includes on-site ventilators 902 for general use that may not benefit from pairing with an on-site relay transceiver 904. For example, region 910 may include a ventilator supporting a patient that does not have an infectious disease and/or is not immunocompromised, ventilators supporting a patient that is in a fragile state that would benefit from in-person interactions such as neonatal patients, or ventilators that are not in use or reserved.

Region 912 represents on-site ventilators 902 that are paired with relay transceivers 904 and are not assigned. This region 912 may include on-site relay transceivers 904 paired with specific on-site ventilators 902. On-site relay transceivers 904 that are paired with specific on-site ventilators 902 may be used to manage a ventilator fleet, such as providing a remote view of an entire fleet of ventilators, determining which ventilators in a specific fleet are currently running, a status or stage of ventilator associated with each of the ventilators (e.g., how many ventilators are using high-flow oxygen therapy or other ventilator modes, how many are weaning and may soon be available, how many are being serviced/require diagnostics, etc.).

Region 914 represents on-site relay transceivers 904 that are not paired with an on-site ventilator 902 and are unassigned. This region 914 includes on-site relay transceivers 904 that are available for pairing with a ventilator and not otherwise reserved.

Referring to assignment of on-site ventilators 902 and on-site relay transceivers 904, ventilators and/or relay transceivers may be assigned to a specific user (e.g., user or team of users), for a specific function (e.g., for infectious patients, terminal patients, neonatal patients, etc.), or to a specific location (e.g., maternity ward, floor of a hospital, pediatric ward, etc.). Regions 916, 918, 920, and 922 discuss how an assignment may impact allocation of resources. The diagram 900 shown in FIG. 9 shows assignments classified in two ways: on-site assignment 906 (e.g., assignment to a user, team of users, ventilator, patient, function, room, ward, site, etc. internal to the care facility or hospital in which the on-site ventilators 902 are located), and remote assignment 908 (e.g., assignment to a user, team of users, patient, function, remote consult, etc. external to the care facility or hospital in which the on-site ventilators 902 are located). Assignment of resources (e.g., ventilators and/or relay transceivers) may be permanent, semi-permanent, or temporary.

Region 916 represents on-site ventilators 902 that are not paired with an on-site relay transceiver 904 and are assigned. The ventilators in this region 916 may be reserved for use associated with their specific assignment and may be pairable with an on-site relay transceiver that is not yet paired (e.g., regions 914, 922) or pairable with an on-site relay transceiver 904 that is already paired (e.g., regions 912, 918, 920, if the ventilator is pairable with multiple relay transceivers). For example, a set of ventilators may be assigned to a COVID-19 recovery ward where patients may no longer be infectious (e.g., use of an on-site relay transceiver may be more beneficial paired to other ventilators).

Region 922 represents on-site relay transceivers 904 that are not paired with an on-site ventilator 902 and are assigned. The on-site relay transceivers in this region 922 may be reserved for use associated with their specific assignment. For example, an on-site relay transceiver may be assigned to a remote consultant (e.g., diagnostics team, remote doctor, educational team, etc.) for which a consult is not yet needed (e.g., the relay transceiver is available for a time when a consult is required or desired).

Region 918 represents on-site ventilators 902 that are paired with an on-site relay transceiver 904 and have an on-site assignment 906. The ventilators and/or relay transceivers in this region 916 may be reserved for use associated with their specific on-site assignment. For example, an on-site relay transceiver 904 may be assigned to a specific patient any may travel with the patient through a hospital (e.g., pairing with a different ventilator as the patient is paired with a different ventilator). Alternatively, a ventilator and/or relay transceiver may be assigned to a specific room, site, or wing of a hospital (e.g., imaging room or neonatal ward). In another example, a relay transceiver may be assigned to a specific clinician, doctor, or doctor support team, based on which patients or ventilators are currently assigned to the user or user team.

Region 920 represents on-site relay transceivers 904 that are paired with an on-site ventilator 902 and have a remote assignment 908. The ventilators and/or relay transceivers in this region 920 may be reserved for use associated with their specific remote assignment. For example, a relay transceiver may be assigned to a remote consultant and paired to a ventilator for viewing of ventilator data by the remote consultant. Alternatively, a relay transceiver may be assigned to a patient that is going to be transported to a different facility or a patient that was recently transported from a different facility (e.g., the relay transceiver may be paired with different ventilators as the patient is transferred from ventilator to ventilator in transit).

In non-limiting examples, relay transceivers may be assigned in the following ways: to a patient (e.g., as a patient travels or is connected to different ventilators); to a site or room (e.g., assigned to “Room 123”, assigned to an MRI room, assigned to a terminal care room, assigned to a neonatal ward, assigned to a floor or region of a facility treating infectious disease, etc.); to a user (e.g., a doctor such as on-site doctor or remote consulting doctor, a clinician or care giver, a doctor support team, an educational facility, a diagnostics team, an expert consultant, etc.); or to a ventilator. In an instance where a relay transceiver is assigned to a remote doctor, the relay transceiver may be one of multiple relay transceivers paired with a single ventilator (e.g., multiple consults, or in addition to an on-site assigned relay transceiver). Additionally, as otherwise described herein, remote viewers may be limited to accessing a ventilator and/or a relay transceiver in a view-only mode.

FIG. 10 depicts a method 1000 for remotely adjusting and/or accessing a ventilator (such as ventilators 100, 202, 502, 802, 803) via a relay transceiver (e.g., relay transceivers 808, 809, 904), based on an input received at a remote device (e.g., remote devices 160, 194, 226, 520, 812, 816, 818), from a perspective of a remote device. At operation 1002, user authentication information is received. The user authentication information may be used to log in to the remote device, log in to a network of the remote device (e.g., a hospital VPN or hospital network), or otherwise verify an identity of the remote device or a user of the remote device. As otherwise described herein, the authentication information may be based on hospital security requirements and/or may utilize multi-factor authentication techniques.

At operation 1004, available relay transceivers are displayed. Relay transceivers may be indicated as available when paired with a ventilator (which may or may not be currently ventilating a patient). The available relay transceivers may be provided in a list, as icons, or otherwise organized. Relay transceivers may be named. A name of a relay transceiver may include identification information, such as an identifier associated with an assignment of the relay transceiver (e.g., Dr. J, Room 123, neonatal, etc.), or an identifier associated with a paired ventilator or the relay transceiver (e.g., IP address, serial number, etc. of the paired ventilator and/or the relay transceiver).

At operation 1006, a selection of a relay transceiver is received. For instance, a selection of an icon representing a relay transceiver may be received. A selection of a relay transceiver may cause the remote device to connect with the relay transceiver. At operation 1008, authentication information is provided to the selected relay transceiver. The authentication information may be the same or different authentication information received at operation 1002. For example, a hospital's multi-factor authentication may be used to identify a user to log in to a remote device and also act as authentication of a remote device or the user of the remote device.

At operation 1010, a disclaimer is received and/or accessed locally on the remote device. The disclaimer may include a usage agreement, setting preferences, or other warnings or information. In an example, a usage agreement is received from the selected relay transceiver every time a remote device connects to the relay transceiver. The usage agreement may require action (e.g., accept or deny) before proceeding to remote ventilator access via the relay transceiver. At operation 1012, an acceptance of the disclaimer is received by the remote device from the user and an indication of the acceptance may be sent to the selected relay transceiver.

At operation 1014, a connection to the selected relay transceiver is established. As further described herein, access permissions of the connection may include view-only permissions or view and control permissions.

At operation 1016, ventilator data is received. The ventilator data may be continuously updated. As further described herein, the ventilator data may include a video feed or successive image captures in substantially real time to replicate at least a portion of the ventilator GUI (displayed at the ventilator) at the remote user interface (on the remote device). At operation 1018, a remote user interface is displayed based on the ventilator data. The remote user interface that is replicating a portion of a live ventilator display may be associated with an overlay to recognize how a selection at the remote user interface of the remote device correlates with a selection at the live ventilator display. Additionally, the remote user interface may include one or more features described herein, including user interface elements (e.g., a virtual bezel key, a ventilator setting icon, an adjustment user interface element, etc.), subdivision into one or more sections (e.g., a selection section/panel, an adjustment section/panel, or a mode-changeable section/panel changeable to display different view modes). Operations 1016 and 1018 may repeat as required or desired (e.g., while the remote device is connected to the relay transceiver) such that the ventilator data may be used to replicate the ventilator UI in real time.

If access to the relay transceiver is a view-only mode, method 1000 may end at operation 1018. At operation 1020, a change associated with a selected ventilator setting icon is received. An increment of the change to the ventilator setting associated with the ventilator settings icon may be indicated based on an interaction with an adjustment element at the remote user interface (e.g., slide bar, an upward or downward adjustment icon, a rotatable dial, etc.). At operation 1022, the change is transmitted to the relay transceiver. The change (e.g., including the ventilator setting and an increment to adjust the ventilator setting) is associated with an update of a setting on the ventilator paired with the relay transceiver. Operations 1016 through 1022 may repeat as required or desired (e.g., while the remote device is connected to the relay transceiver) such that the ventilator data may be used to replicate the ventilator UI in real time (e.g., as ventilator settings are changed).

FIG. 11 depicts a method 1100 for remotely adjusting and/or accessing a ventilator (such as ventilators 100, 202, 502, 802, 803) via a relay transceiver (e.g., relay transceivers 808, 809, 904), based on an input received at a remote device (e.g., remote devices 160, 194, 226, 520, 812, 816, 818), from a perspective of a relay transceiver. At operation 1102, a request to access the relay transceiver is received. The request may be received from a remote device that communicates with the relay transceiver via a wired or wireless connection. The request to access the relay transceiver may be authenticated to verify a remote device and/or a user of the remote device requesting access.

At operation 1104, a disclaimer is provided to the remote device. The disclaimer may be similar to the disclaim described above for operation 1010 in FIG. 10. At determination 1106, it is determined if one or more portions of the disclaimer are accepted. If an acceptance is not received (e.g., the disclaimer times out or is declined at the remote device), flow proceeds as “NO” to operation 1108 where access to ventilator data (e.g., data received from a paired ventilator) is denied. Denial may prompt closing of an application on the remote device.

If, alternatively, an acceptance is received, flow proceeds as “YES” to operation 1110. At operation 1110, ventilator data is received (e.g., from the ventilator to the relay transceiver). The ventilator data may be similar to that described in operation 1016 in FIG. 10.

At operation 1112, the ventilator data is transmitted. The relay transceiver may send or forward the ventilator data to the remote device to allow the remote device to replicate the ventilator GUI. The transmission may be continuously forwarded as ventilator information is received by the relay transceiver from the ventilator. Operations 1110 and 1112 may repeat as required or desired (e.g., while the remote device is connected to the relay transceiver) to allow an application running on the remote device to display the ventilator UI in real time.

At operation 1114, a settings change is received from the remote device. The settings change may be associated with a ventilator setting and an adjustment increment to adjust a value of the ventilator setting. At operation 1116, the settings change is transmitted. The settings change is transmitted to the ventilator to update a setting of the ventilator paired with the relay transceiver. Operations 1110 through 1116 may repeat as required or desired (e.g., while the remote device is connected to the relay transceiver) such that the ventilator data may be used to replicate the ventilator UI in real time at the remote device (e.g., as ventilator settings are changed).

FIG. 12 depicts a method 1200 for pairing a relay transceiver (e.g., relay transceivers 808, 809, 904) with multiple ventilators (e.g., ventilators 100, 202, 502, 802, 803). At operation 1202, first ventilator data is received from a first ventilator via a first connection. The first connection between the relay transceiver and the first ventilator may be a physical connection (e.g., a wired connection, a connection via a port on the ventilator, integrated into the ventilator, etc., as otherwise described herein). The first ventilator data may be continuously received while the first connection is established (e.g., until the relay transceiver is physically disconnected from the first ventilator). The relay transceiver may transmit a disconnection notice to the remote device when a connection between the relay transceiver and a ventilator is lost or disconnected (e.g., as may be displayed at a remote user interface of the remote device as a connect or disconnect button 708 or as information 710).

At operation 1204, the first ventilator data is transmitted to a remote device via a second connection. The second connection (the connection between the relay transceiver and the remote device) may be a wireless connection. The first ventilator data may be continuously transmitted or forwarded to the remote device while the first connection and the second connection are established (e.g., until the relay transceiver is disconnected from the first ventilator or until the remote device is disconnected from the relay transceiver).

At operation 1206, a first change, to be caused at the first ventilator, is received form the remote device. As otherwise described herein, a change (e.g., the first change) may be associated with a ventilator setting and an adjustment increment to adjust a value of the ventilator setting (e.g., by selection of a ventilator settings icon displayed at the remote device). The adjustment increment may be indicated based on an interaction with an adjustment element at the remote user interface.

At operation 1208, the first change is transmitted to the first ventilator. Transmission of the change may cause a setting of the ventilator to be adjusted by an amount indicated by the first change. For instance, upon receiving the first change or indication of the first change, the ventilator changes or adjusts the respective setting. Operations 1202-1204 and 1202-1208 may repeat as required or desired.

At operation 1210, second ventilator data is received from a second ventilator via a third connection. The third connection, between the relay transceiver and the second ventilator, may be the same or similar to the connection described in operation 1202 between the relay transceiver and the first ventilator.

To establish the first connection and/or the third connection, relay transceiver may be required or desired to be located near (e.g., in the same room) as the ventilator to which it is connected. The first ventilator and the second ventilator may be in different locations (e.g., different rooms of a hospital, different wings of a hospital, different buildings, etc.). In this instance, the relay transceiver may be in a first room when receiving the first ventilator data over the first connection and may be relocated to a second room when receiving the second ventilator data over the third connection. For instance, a clinician may unplug the relay transceiver from the first ventilator, carry the relay transceiver to the second ventilator, and plug the relay transceiver into the second ventilator. Additionally, the first connection and the third connection may be established at different times and may be mutually exclusive. Alternatively, the relay transceiver may establish the first connection and the third connection concurrently. For instance, multiple ports of the relay transceiver may be used. A first cable from a first port of the relay transceiver may be connected to a port of the first ventilator, and a second cable from a second port of the relay transceiver may be connected to a port of the second ventilator. In an example where the first connection and the third connection are not established concurrently, the first connection may be disconnected prior to establishing the third connection and prior to receiving second ventilator data from the second ventilator at operation 1210.

At operation 1212, the second ventilator data is transmitted to the remote device via the second connection. At operation 1214, a second change, to be caused at the second ventilator, is received from the remote device. At operation 1216, the second change is transmitted to the second ventilator. Operations 1212-1216 may be the same or similar to operations 1204-1208, except relating to the third connection between the relay transceiver and the second ventilator (instead of the first connection between the relay transceiver and the first ventilator). Operations 1210-1212 and 1210-1216 may repeat as required or desired.

FIG. 13 depicts a method 1300 for receiving changes to be caused at a ventilator (e.g., ventilators 100, 202, 502, 802, 803) from multiple remote devices (e.g., remote devices 160, 194, 226, 520, 812, 816, 818). At operation 1302, ventilator data is received from a ventilator. The ventilator data may be received over a connection between a relay transceiver and the ventilator. The connection between the relay transceiver and the ventilator may be a physical connection (e.g., a wired connection, a connection via a port on the ventilator, integrated into the ventilator, etc.). The ventilator data may be continuously received while the connection between the relay transceiver and the ventilator is established (e.g., until the relay transceiver is disconnected from the ventilator).

At operation 1304, the ventilator data is transmitted to a first remote device via a first connection and a second remote device via a second connection. The first connection, the connection between the relay transceiver and the first remote device, and/or the second connection, the connection between the relay transceiver and the second remote device, may be wireless connections. The ventilator data may be continuously transmitted or forwarded to the first remote device and the second remote device as it is received from the ventilator. The first remote device and/or the second remote device may be located outside of a room in which the ventilator is located. Operations 1302-1304 may repeat as required or desired.

At operation 1306, a first change to be caused at the ventilator is received from the first remote device. As further described herein, a change (e.g., the first change) may be associated with a ventilator setting (associated with a ventilator settings icon at the remote device) and an adjustment increment (associated with an adjustment element at the remote device) to adjust a value of the ventilator setting.

At operation 1308, the first change is transmitted to the ventilator. Transmission of the first change may cause a first setting of the ventilator to be adjusted by an amount indicated by the first change. Operations 1302-1308 may repeat as required or desired.

At operation 1310, a second change to be caused at the ventilator is received from the second remote device. Similar to the first change described in operation 1306, the second change may be associated with a ventilator setting and an adjustment increment to adjust a value of the ventilator setting. The first change and the second change may be associated with different ventilator settings or the same ventilator setting. Additionally, the first change and the second change may be associated with a same or different adjustment increment (e.g., a same change to a value of a setting). For example, a first change may be a +0.1 cmH₂O adjustment increment to PEEP and the second change may also be a +0.1 cmH₂O adjustment increment to PEEP, resulting in a total change of +0.2 cmH₂O to the PEEP ventilation setting. In another example, a first change may be a +0.1 cmH₂O adjustment increment to PEEP and a second change may be a −2 f/mm adjustment increment to respiratory rate.

Adjustments to ventilator settings (e.g., a first change and a second change) may be restricted. For example, the second change may be prevented from being received at the relay transceiver (and/or prevented from being received at a user interface of the second remote device) until after receiving and/or transmitting, or between receiving and transmitting, the first change (e.g., while the first change is being caused at the ventilator). Additionally or alternatively, local control of the ventilator (e.g., at the user interface of the ventilator itself) may be prevented until after receiving and/or transmitting, or between receiving and transmitting, the first change. The local control at the ventilator or one or more remote devices may be prioritized for causing changes to ventilator settings. For example, the local control may override any incoming changes from remote devices (e.g., the first remote device or the second remote device). In another example, a prioritized remote device may override any changes to ventilator settings (e.g., local changes or changes from other remote devices). In another example, changes from remote devices may be prevented for a lockout period (e.g., a specified period of time, such as 10 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, 10 minutes, etc.) when local control of the ventilator is detected (e.g., by the relay transceiver determining a change in the ventilator data and/or a change in one or more values of a ventilator setting). If changes are not currently available at a remote device, the remote device may be designated in a view-only mode (e.g., have view-only access or permission to the ventilator data). If changes are permitted by the remote device, the remote device, then the remote device may be operating in a view and control mode (e.g., have view and control access or permission to the ventilator data).

At operation 1312, the second change is transmitted to the ventilator. Transmission of the second change may cause a second setting of the ventilator (e.g., which may be the same as or different from the first setting associated with the first change) to be adjusted by an amount indicated by the second change. Operations 1302-1312 may repeat as required or desired. Although two remote devices are provided in the example method 1300, any number of remote devices is appreciated.

Those skilled in the art will recognize that the methods and systems of the present disclosure may be implemented in many manners and as such are not to be limited by the foregoing aspects and examples. In other words, functional elements being performed by a single or multiple components, in various combinations of hardware and software or firmware, and individual functions, can be distributed among software applications at either the client or server level or both. In this regard, any number of the features of the different aspects described herein may be combined into single or multiple aspects, and alternate aspects having fewer than or more than all of the features herein described are possible. Functionality may also be, in whole or in part, distributed among multiple components, in manners now known or to become known. Thus, myriad software/hardware/firmware combinations are possible in achieving the functions, features, interfaces, and preferences described herein. In addition, some aspects of the present disclosure are described above with reference to block diagrams and/or operational illustrations of systems and methods according to aspects of this disclosure. The functions, operations, and/or acts noted in the blocks may occur out of the order that is shown in any respective flowchart. For example, two blocks shown in succession may in fact be executed or performed substantially concurrently or in reverse order, depending on the functionality and implementation involved.

Further, as used herein and in the claims, the phrase “at least one of element A, element B, or element C” is intended to convey any of: element A, element B, element C, elements A and B, elements A and C, elements B and C, and elements A, B, and C. In addition, one having skill in the art will understand the degree to which terms such as “about” or “substantially” convey in light of the measurement techniques utilized herein. To the extent such terms may not be clearly defined or understood by one having skill in the art, the term “about” shall mean plus or minus ten percent.

Numerous other changes may be made which will readily suggest themselves to those skilled in the art and which are encompassed in the spirit of the disclosure and as defined in the appended claims. While various aspects have been described for purposes of this disclosure, various changes and modifications may be made which are well within the scope of the disclosure. Numerous other changes may be made which will readily suggest themselves to those skilled in the art and which are encompassed in the spirit of the disclosure and as defined in the claims.

In an aspect, the present technology relates to a system for remotely adjusting a ventilator. The system includes a display, a processor, and memory storing instructions that, when executed by the processor, cause the system to perform a set of operations. The set of operations include displaying, on the display, a ventilator user interface comprising an icon associated with a ventilation setting. The set of operations further include receiving, from a remote device, selection data comprising position information and selection information of a time-varying user input. Based on the selection data, the set of operations include determining a selection of the icon. The set of operations additionally includes displaying, on the ventilator user interface a value associated with the selected icon. Thereafter, the set of operations includes determining, based on the selection data, a change in the value associated with the selected icon. Additionally, the set of operations includes displaying, on the ventilator user interface, the change in the value and updating the ventilation setting based on the change in the value.

For example, the set of operations further includes sending display information to a replicate display device to replicate a portion of the ventilator user interface. In another example, the replicate display device is the remote device. In a further example, the replicate display device is different from the remote device and is non-interactive. In yet another example, an intermediate device relays the selection data from the remote device to the ventilator. In still a further example, the system further includes a physical input component configured to adjust the value. In another example, the physical input component is a rotatable dial, and the change in the value is associated with an angle of rotation of the rotatable dial. In a further example, the set of operations further includes receiving, from the remote device, adjustment data associated with the change in the value.

In another example, a method for remotely adjusting a ventilator is provided. The method includes displaying, on a remote device, a remote user interface and receiving, at the remote user interface, a time-varying user input comprising an input position and an input selection. The method further includes sending, to the ventilator, selection data based on the input position and the input selection and receiving, from the ventilator, a selection indication of a selected ventilator icon associated with the selection data. Thereafter, the method includes receiving, from the ventilator, a change indication of a change in a value associated with the selected ventilator icon.

In examples, the remote user interface includes a virtual trackpad. In another example, the method further includes receiving, from the ventilator, display data comprising display information to replicate a portion of the ventilator user interface. In a further example, the remote user interface includes the portion of the ventilator user interface and a virtual trackpad, the portion of the ventilator user interface comprising a local position indicator. In yet another example, the method further includes receiving, at the remote user interface, an adjustment input associated with the selected ventilator icon, wherein the remote user interface comprises a remote adjustment element and the adjustment input is based on the time-varying user input at the remote adjustment element. In still a further example, the remote adjustment element is a virtual rotatable dial capable of receiving the adjustment input. In another example, the virtual rotatable dial is associated with a physical rotatable dial on the ventilator. In yet another example, a position of the remote adjustment element is associated with a non-selectable region of a corresponding ventilator user interface. In a further example, the method further includes enabling the remote adjustment element based on the selection indication. In another example, the method further includes receiving, from the ventilator, a de-selection indication of the selected ventilator control element; and disabling the remote adjustment element. In a further example, the method further includes displaying the selection indication on the remote user interface.

In a further example, a method for remotely adjusting a ventilator is provided. The method includes displaying, by the ventilator, a ventilator user interface comprising a ventilator control element associated with a ventilation setting and displaying, on a remote device, a remote user interface. The method further includes receiving, at the remote device, a time-varying user input at the remote user interface comprising an input position and an input selection and sending, from the remote device to the ventilator, selection data based on the selection input. Additionally, the method includes receiving, at the ventilator, the selection data from the remote device and determining, by the ventilator, a selection of the ventilator control element, based on the selection data. The method includes displaying, by the ventilator on the ventilator user interface a value associated with the selected ventilator control element. Thereafter, the method includes determining, by the ventilator, a change in a value associated with the selected ventilator control element. The method further includes displaying, by the ventilator on the ventilator user interface, the change in the value; and updating the ventilation setting based on the change in the value.

In another example, a method for remotely accessing a medical ventilator is provided. The method includes connecting, via a wired or wireless connection, a remote computing device to a ventilator, the ventilator having a ventilator display; and providing, on the remote computing device, a view of the ventilator display. The method further includes tracking, on the remote computing device, cursor movement and a cursor activation. Additionally, the method includes displaying, on the remote computing device, the cursor movement overlaid on the view of the ventilator display; and transmitting the cursor activation to the ventilator, via the wired or wireless connection.

In an example, the set of operations further includes: receiving updated ventilator data from the relay transceiver associated with the settings change caused at the ventilator; and updating the remote user interface based on the updated ventilator data. In another example, the set of operations further comprise: displaying, on the display, a plurality of relay icons corresponding to a plurality of relay transceivers; receiving a selection of a particular relay icon; and based on the received selection of the particular relay icon, establishing a connection with a particular relay transceiver corresponding to the particular relay icon. In a further example, the system is located outside a of a room in which the particular relay transceiver and the ventilator are located. In yet another example, the ventilator data is received over a wireless network of a hospital. In still a further example, the remote ventilator user interface includes at least one ventilator settings icon, and wherein the selected ventilator setting is the at least one ventilator settings icon. In another example, the remote interface includes a virtual bezel key representing at least one physical bezel key on the ventilator, and wherein the selected ventilator setting is the virtual bezel key. In a further example, the remote user interface includes an adjustment element, and wherein the settings change is defined by a received interaction with the adjustment element. In yet another example, the adjustment element is a slide bar. In still a further example, the remote user interface comprises three panels: a changeable panel including the remote ventilator user interface; a selection panel including the virtual bezel key; and an adjustment panel including the adjustment element.

In another aspect, a relay transceiver for remotely adjusting a ventilator is disclosed. The relay transceiver system includes a processor; and memory storing instructions that, when executed by the processor, cause the system to perform a set of operations. The set of operations includes: receiving a request, from a remote device over a wireless connection between the remote device and the relay transceiver, to access ventilator data of a ventilator; and receiving the ventilator data from the ventilator over a wired connection between the ventilator and the relay transceiver. The set of operations further includes transmitting the ventilator data to the remote device over the wireless connection, the ventilator data causing a portion of the ventilator user interface to be replicated at the remote user interface. Additionally, the set of operations includes receiving, from the remote device over the wireless connection, a settings change of the at least one adjustable ventilator setting; and transmitting the settings change to the ventilator over the wired connection.

In an example, the wireless connection between the remote device and the relay transceiver is over a hospital network. In another example, the wired connection between the ventilator and the relay transceiver is established with at least one of: an HDMI-to-USB adapter; a dongle; a self-supported HDMI connection; and a smart cable. In a further example, the set of operations further includes: receiving a patient video feed from a camera; and transmitting the patient video feed to the remote device for display at the remote user interface. In yet another example, the ventilator data includes a video of the ventilator user interface. In still a further example, the at least one adjustable ventilator setting is associated with one of: a physical bezel key on the ventilator; and a ventilator user interface element on the ventilator user interface. In another example, the at least one adjustable ventilator setting associated with the physical bezel key is one of: a display brightness; a display lock; an alarm volume; a manual inspiration; an inspiratory pause; an expiratory pause; an alarm reset; and an audio pause. In a further example, the at least one adjustable ventilator setting associated with the ventilator user interface element is one of: an inhalation flow; a respiratory rate; a tidal volume; and a positive end-expiratory pressure (PEEP). In yet another example, the set of operations further includes in response to receiving the request to access ventilator data of the ventilator, transmitting a usage agreement to the remote device over the wireless connection; and receiving an acceptance of the usage agreement from the remote device over the wireless connection.

In a further aspect, a method for remotely accessing a ventilator is disclosed. The method includes receiving ventilator data from a relay transceiver communicatively coupled to a ventilator. Based on the ventilator data, the method includes displaying a remote user interface including a remote ventilator user interface replicating at least a portion of a ventilator user interface of the ventilator. Additionally, the method includes receiving, at the remote user interface, a selection of a ventilator setting; receiving, at the remote user interface, a settings change to the selected ventilator setting; and transmitting the settings change to the relay transceiver.

In another aspect, a method for pairing a relay transceiver with a first ventilator and a second ventilator is described. The method includes: receiving first ventilator data from a first ventilator over a first wired connection between the relay transceiver and the first ventilator; and transmitting the first ventilator data to a remote device over a wireless connection between the relay transceiver and the remote device. Additionally, the method includes receiving, from the remote device, a first change to be caused at the first ventilator; transmitting the first change to the first ventilator; and receiving second ventilator data from a second ventilator over a second wired connection between the relay transceiver and the second ventilator. The method further includes transmitting the second ventilator data to the remote device over the wireless connection; receiving, from the remote device, a second change to be caused at the second ventilator; and transmitting the second change to the second ventilator.

In an example, the first wired connection and the second wired connection are not concurrently established. In another example, the relay transceiver is physically disconnected from the first ventilator prior to the second wired connection being established. In a further example, the method further includes: when receiving the first ventilator data, the relay transceiver is removably attached to a physical port of the first ventilator accessible outside of a housing of the first ventilator; and when receiving the second ventilator data, the relay transceiver is removably attached to a physical port of the second ventilator accessible outside of a housing of the second ventilator. In yet another example, when receiving the second ventilator data, the relay transceiver is not attached to the physical port of the first ventilator. In still a further example, the first ventilator and the second ventilator are in different rooms of a hospital. In another example, the first wired connection is contained inside a room of a hospital and the remote device is outside of the room. In a further example, transmitting the first change to the first ventilator causes a settings change at the first ventilator. In yet another example, the method further includes transmitting a disconnection notice to the remote device. In still a further example, the first ventilator data includes video data.

In a further aspect, a method for receiving settings changes from multiple remote devices at a relay transceiver is disclosed. The method includes receiving ventilator data from a ventilator over a wired connection; and transmitting the ventilator data to a first remote device over a first wireless connection and a second remote device over a second wireless connection. The method further includes receiving, from the first remote device, a first change to be caused at the ventilator; and transmitting the first change to the ventilator. Additionally, the method includes receiving, from the second remote device, a second change to be caused at the ventilator; and transmitting the second change to the ventilator.

In an example, the first wireless connection and the second wireless connection are over a hospital network. In another example, the ventilator data includes video data associated with the ventilator. In a further example, the method further includes: receiving a patient video feed from a camera; and transmitting the patient video feed to the first remote device. In yet another example, the first remote device and the second remote device are located outside of a room in which the ventilator is located. In still a further example, the ventilator data is continuously received and transmitted. In another example, the second change is prevented from being received until after transmitting the first change. In a further example, changes from the first remote device and the second remote device are prevented for a lockout period when local control of the ventilator is detected. In yet another example, the method further includes transmitting the ventilator data to a third remote device while preventing any changes to be received from the third remote device. In still a further example, the first remote device has view and control access to the ventilator data and the third remote device has view-only access to the ventilator data.

Claims

1. A relay transceiver for remotely adjusting a ventilator, the relay transceiver comprising: a processor;memory storing instructions that, when executed by the processor, cause the relay transceiver to perform a set of operations comprising: receiving an assignment for the relay transceiver to a user;receiving a first request, from a remote device accessed by the assigned user, over a wireless connection between the remote device and the relay transceiver, to access ventilator data of a first ventilator;based on the first request and the assignment to the user, authenticating the remote device;in response to authenticating the remote device, receiving the ventilator data from the first ventilator over a first wired connection between the first ventilator and the relay transceiver;transmitting the ventilator data to the remote device over the wireless connection, the ventilator data causing a portion of a ventilator user interface of the first ventilator to be replicated at a remote user interface of the remote device;receiving a second request, from the remote device over the wireless connection between the remote device and the relay transceiver, to access ventilator data of a second ventilator connected to the relay transceiver via a second wired connection; andin response to the second request, transmitting the ventilator data of the second ventilator to the remote device over the wireless connection.

2. The relay transceiver of claim 1, wherein the assignment of the relay transceiver is associated with permissions of the ventilator data of the first ventilator, the permissions being one of: a view-only permission; ora view and control permission.

3. The relay transceiver of claim 1, wherein the assignment of the relay transceiver is to a user group including the user.

4. The relay transceiver of claim 3, wherein the user group is a team of medical professionals on-site with the relay transceiver.

5. The relay transceiver of claim 3, wherein authenticating the remote device includes comparing authentication information associated with the request with the assignment to determine that the authentication information is associated with the user group.

6. The relay transceiver of claim 3, wherein authenticating the remote device further includes multi-factor authentication based on hospital security requirements.

7. The relay transceiver of claim 3, wherein the user group includes a consultant off-site from the relay transceiver.

8. The relay transceiver of claim 1, wherein the ventilator data of the first ventilator includes a video feed of at least a portion of a ventilator user interface of the first ventilator.

9. The relay transceiver of claim 1, wherein the remote device is a first remote device, and wherein the set of operations further comprises: receiving a third request, from a second remote device over a wireless connection between the second remote device and the relay transceiver, to access the ventilator data of the first ventilator;based on the third request and the assignment, authenticating the second remote device; andin response to authenticating the second remote device, transmitting the ventilator data of the first ventilator to the second remote device while transmitting the ventilator data of the first ventilator to the first remote device.

10. The relay transceiver of claim 1, wherein the remote device is a first remote device, and wherein the set of operations further comprises: receiving a third request, from a second remote device over a wireless connection between the second remote device and the relay transceiver, to access the ventilator data of the ventilator;determining that third request is not valid, based on the assignment; anddenying access of the second remote device to the ventilator data of the first ventilator.

11. The relay transceiver of claim 1, wherein the assignment is a first assignment, the remote device is a first remote device, and wherein the set of operations further comprises: receiving a second assignment for the relay transceiver, the second assignment being different than the first assignment;receiving a third request, from a second remote device over a wireless connection between the second remote device and the relay transceiver, to access the ventilator data of the first ventilator;based on the second request, validating the second assignment of the relay transceiver; andin response to validating the second assignment of the relay transceiver, transmitting the ventilator data of the first ventilator to the second remote device.

12. The relay transceiver of claim 11, the set of operations further comprises: based on the second assignment, determining access permissions of the remote device, wherein access permissions are one of:a view-only mode of the ventilator data; ora view and control mode of the ventilator data.

13. A relay transceiver for remotely adjusting a ventilator, the relay transceiver comprising: a processor;memory storing instructions that, when executed by the processor, cause the relay transceiver to perform a set of operations comprising: receiving an assignment for the relay transceiver to a user;receiving first ventilator data for a first ventilator over a first wired connection between the ventilator and the relay transceiver;receiving a first request, from a remote device accessed by the assigned user, over a wireless connection between the remote device and the relay transceiver, to access the first ventilator data of the first ventilator;in response to the first request, transmitting the first ventilator data to the remote device over the wireless connection;receiving second ventilator data for a second ventilator over a second wired connection between the ventilator and the relay transceiver;receiving a second request, from the remote device over the wireless connection between the remote device and the relay transceiver, to access the second ventilator data of the second ventilator; andin response to the second request, transmitting the second ventilator data to the remote device over the wireless connection, the second ventilator data including a portion of a ventilator user interface of the second ventilator to be replicated at a remote user interface of the remote device.

14. The relay transceiver of claim 13, wherein the first wired connection is disconnected prior to the second wired connection being established.

15. The relay transceiver of claim 13, wherein the first ventilator data and the second ventilator data include first ventilator identification information and second ventilator identification information to identify the first ventilator and second ventilator, respectively.

16. The relay transceiver of claim 15, wherein the first ventilator identification information and the second ventilator identification information are a first room in which the first ventilator is located and a second room in which the second ventilator is located, respectively, the first room being different from the second room.

17. The relay transceiver of claim 13, wherein the first wired connection and the second wired connection to the relay transceiver are established concurrently.

18. The relay transceiver of claim 13, wherein transmitting the first ventilator data to the remote device includes authenticating the remote device with respect to a first user group allowed to access the first ventilator data, and wherein transmitting the second ventilator data to the remote device includes authenticating the remote device with respect to a second user group allowed to access the second ventilator data.

19. The relay transceiver of claim 13, wherein transmitting the first ventilator data and the second ventilator data to the remote device is based on multi-factor authentication of the remote device, wherein the multi-factor authentication is based on hospital security requirements.

20. A method for remotely adjusting a ventilator, the method comprising: receiving, at a relay transceiver, an assignment for the relay transceiver to a user group;receiving, at a relay transceiver, ventilator data from a first ventilator;receiving, at the relay transceiver from a remote device over a wireless connection, a first request to access the ventilator data of the first ventilator;authenticating the remote device at the relay transceiver, wherein authenticating the remote device includes determining that the remote device is accessed by a user of the user group;in response to authenticating the remote device, transmitting, from the relay transceiver to the remote device in real time, the ventilator data from the first ventilator to cause a portion of a ventilator user interface of the first ventilator to be replicated at a remote user interface of the remote device;receiving, at the relay transceiver from the remote device, a second request to access ventilator data of a second ventilator; andin response to the second request, transmitting, from the relay transceiver to the remote device in real time, the ventilator data of the second ventilator to the remote device over the wireless connection.