Remote ventilator adjustment

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 (V_T), 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_I), 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_I). 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_I) 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_I), 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_I), 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_I), 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_I) 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_I) 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_I), 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_I), 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_I), 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_I). 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_I), 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 a first request, from a remote device, over a wireless connection between the remote device and the relay transceiver, to access ventilator data of a first ventilator;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 to cause a portion of a ventilator user interface of the first ventilator to be replicated at 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 to cause a portion of a ventilator user interface of the second ventilator to be replicated at the remote device.
2. 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, 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.
3. The relay transceiver of claim 1, wherein the set of operations further comprises receiving an assignment for the relay transceiver to a user.
4. The relay transceiver of claim 3, 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;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.
5. The relay transceiver of claim 4, wherein the assignment of the relay transceiver is to a user group including the user.
6. The relay transceiver of claim 5, wherein the user group is a team of medical professionals on-site with the relay transceiver.
7. The relay transceiver of claim 1, wherein the ventilator data of the first ventilator includes a video feed of at least a portion of the ventilator user interface of the first ventilator.
8. A method for remotely adjusting a ventilator, the method comprising: receiving, at a relay transceiver from a remote device over a wireless connection, a first request to access ventilator data of a first ventilator;in response to the first request, 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 over the wireless connection, the ventilator data of the second ventilator to cause a portion of a ventilator user interface of the second ventilator to be replicated at the remote user interface of the remote device.
9. The method of claim 8, further comprising: receiving, at a relay transceiver, an assignment for the relay transceiver to a user; andauthenticating the remote device at the relay transceiver, wherein authenticating the remote device includes determining that the remote device is accessed by the user.
10. The method of claim 9, wherein the assignment of the relay transceiver is to a user group including the user.
11. The method of claim 9, wherein the remote device is a first remote device, and the method 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;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.
12. The method of claim 8, wherein the remote user interface includes a virtual bezel key representing at least one physical bezel key on the first ventilator.
13. The method of claim 8, wherein the wireless connection between the remote device and the relay transceiver is over a hospital network.
14. The method of claim 8, wherein the ventilator data of the first ventilator includes a video feed of at least a portion of the ventilator user interface of the first ventilator.
15. The method of claim 8, wherein the remote device is a first remote device, and wherein the method 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, 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.
16. A ventilation system comprising: a first ventilator;a second ventilator; anda 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 a first request, from a remote device, over a wireless connection between the remote device and the relay transceiver, to access ventilator data of the first ventilator;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 to cause a portion of a ventilator user interface of the first ventilator to be replicated at 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 the 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 to cause a portion of a ventilator user interface of the second ventilator to be replicated at the remote device.
17. The ventilation system of claim 16, wherein the operations further comprise: receiving, at a relay transceiver, an assignment for the relay transceiver to a user; andauthenticating the remote device at the relay transceiver, wherein authenticating the remote device includes determining that the remote device is accessed by the user.
18. The ventilation system of claim 17, wherein the assignment of the relay transceiver is to a user group including the user.
19. The ventilation system of claim 16, wherein the ventilator data of the first ventilator includes a video feed of at least a portion of the ventilator user interface of the first ventilator.
20. The ventilation system of claim 19, wherein the remote interface includes a virtual bezel key representing at least one physical bezel key on the first ventilator.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/241,638, filed Apr. 27, 2021, which claims the benefit of U.S. Provisional Application No. 63/023,343, filed May 12, 2020, and U.S. Provisional Application No. 63/050,214, filed Jul. 10, 2020, the complete disclosures of which are hereby incorporated herein by reference in their entireties.

US Referenced Citations (920)

Number	Name	Date	Kind
3577984	Levy et al.	May 1971	A
3659590	Jones et al.	May 1972	A
3871371	Weigl	Mar 1975	A
3940742	Hudspeth et al.	Feb 1976	A
3961624	Weigl	Jun 1976	A
3961627	Ernst et al.	Jun 1976	A
3977394	Jones et al.	Aug 1976	A
3991304	Hillsman	Nov 1976	A
3996928	Marx	Dec 1976	A
4034743	Greenwood et al.	Jul 1977	A
4036217	Ito et al.	Jul 1977	A
4053951	Hudspeth et al.	Oct 1977	A
4090513	Togawa	May 1978	A
4112931	Burns	Sep 1978	A
4187842	Schreiber	Feb 1980	A
4215409	Strowe	Jul 1980	A
4241739	Elson	Dec 1980	A
4258718	Goldman	Mar 1981	A
4296756	Dunning et al.	Oct 1981	A
4308872	Watson et al.	Jan 1982	A
4323064	Hoenig et al.	Apr 1982	A
4326513	Schulz et al.	Apr 1982	A
4391283	Sharpless et al.	Jul 1983	A
4401115	Monnier	Aug 1983	A
4401116	Fry et al.	Aug 1983	A
4407295	Steuer et al.	Oct 1983	A
4440177	Anderson et al.	Apr 1984	A
4444201	Itoh	Apr 1984	A
4463764	Anderson et al.	Aug 1984	A
4473081	Dioguardi et al.	Sep 1984	A
4495944	Brisson et al.	Jan 1985	A
4537190	Caillot et al.	Aug 1985	A
4550726	McEwen	Nov 1985	A
4579115	Wallroth et al.	Apr 1986	A
4637385	Rusz	Jan 1987	A
4654029	D'Antonio	Mar 1987	A
4736750	Valdespino et al.	Apr 1988	A
4790327	Despotis	Dec 1988	A
4796639	Snow et al.	Jan 1989	A
4813409	Ismach	Mar 1989	A
4852582	Pell	Aug 1989	A
4867152	Kou et al.	Sep 1989	A
4876903	Budinger	Oct 1989	A
4917108	Mault	Apr 1990	A
4984158	Hillsman	Jan 1991	A
4990894	Loescher et al.	Feb 1991	A
5003985	White et al.	Apr 1991	A
5004472	Wallace	Apr 1991	A
5009662	Wallace et al.	Apr 1991	A
5020527	Dessertine	Jun 1991	A
5021046	Wallace	Jun 1991	A
5057822	Hoffman	Oct 1991	A
5058601	Riker	Oct 1991	A
5137026	Waterson et al.	Aug 1992	A
5163423	Suzuki	Nov 1992	A
5167506	Kilis et al.	Dec 1992	A
5203343	Axe et al.	Apr 1993	A
5224487	Bellofatto et al.	Jul 1993	A
5231981	Schreiber et al.	Aug 1993	A
5235973	Levinson	Aug 1993	A
5237987	Anderson et al.	Aug 1993	A
5246010	Gazzara et al.	Sep 1993	A
5251632	Delpy	Oct 1993	A
5261397	Grunstein	Nov 1993	A
5261415	Dussault	Nov 1993	A
5277195	Williams	Jan 1994	A
5279304	Einhorn et al.	Jan 1994	A
5293875	Stone	Mar 1994	A
5303698	Tobia et al.	Apr 1994	A
5303699	Bonassa et al.	Apr 1994	A
5307795	Whitwam et al.	May 1994	A
5319355	Russek	Jun 1994	A
5333106	Lanpher et al.	Jul 1994	A
5339825	McNaughton et al.	Aug 1994	A
5355893	Mick et al.	Oct 1994	A
5357975	Kraemer et al.	Oct 1994	A
5363842	Mishelevich et al.	Nov 1994	A
5365922	Raemer	Nov 1994	A
5373851	Reinhold, Jr. et al.	Dec 1994	A
5383470	Kolbly	Jan 1995	A
5402796	Packer et al.	Apr 1995	A
5404871	Goodman et al.	Apr 1995	A
5442940	Secker et al.	Aug 1995	A
5445160	Culver et al.	Aug 1995	A
5446449	Lhomer et al.	Aug 1995	A
5448996	Bellin et al.	Sep 1995	A
5452714	Anderson et al.	Sep 1995	A
5456264	Series et al.	Oct 1995	A
5464410	Skeens et al.	Nov 1995	A
5479939	Ogino	Jan 1996	A
5487731	Denton	Jan 1996	A
5495848	Aylsworth et al.	Mar 1996	A
5501231	Kaish	Mar 1996	A
5507291	Stirbl et al.	Apr 1996	A
5517985	Kirk et al.	May 1996	A
5518002	Wolf et al.	May 1996	A
5534851	Russek	Jul 1996	A
5537992	Bjoernstijerna et al.	Jul 1996	A
5542410	Goodman et al.	Aug 1996	A
5549117	Tacklind et al.	Aug 1996	A
5553620	Snider et al.	Sep 1996	A
5558086	Smith et al.	Sep 1996	A
5560353	Willemot et al.	Oct 1996	A
5564414	Walker et al.	Oct 1996	A
5564432	Thomson	Oct 1996	A
5571142	Brown et al.	Nov 1996	A
5575283	Sjoestrand	Nov 1996	A
5579775	Dempsey et al.	Dec 1996	A
5582167	Joseph	Dec 1996	A
5590648	Mitchell et al.	Jan 1997	A
5591130	Denton	Jan 1997	A
5596984	O'Mahony et al.	Jan 1997	A
5606976	Marshall et al.	Mar 1997	A
5611335	Makhoul et al.	Mar 1997	A
5626144	Tacklind et al.	May 1997	A
5632281	Rayburn	May 1997	A
5634461	Faithfull et al.	Jun 1997	A
5634471	Fairfax et al.	Jun 1997	A
5642735	Kolbly	Jul 1997	A
5647346	Holscher	Jul 1997	A
5651264	Lo et al.	Jul 1997	A
5655516	Goodman et al.	Aug 1997	A
5660168	Ottosson et al.	Aug 1997	A
5669379	Somerson et al.	Sep 1997	A
5676129	Rocci, Jr. et al.	Oct 1997	A
5676132	Tillotson et al.	Oct 1997	A
5678539	Schubert et al.	Oct 1997	A
5683424	Brown et al.	Nov 1997	A
5687717	Halpern et al.	Nov 1997	A
5692497	Schnitzer et al.	Dec 1997	A
5704346	Inoue	Jan 1998	A
5704366	Tacklind et al.	Jan 1998	A
5704367	Ishikawa et al.	Jan 1998	A
5706801	Remes et al.	Jan 1998	A
5724990	Ogino	Mar 1998	A
5730140	Fitch	Mar 1998	A
5730145	Defares et al.	Mar 1998	A
5735287	Thomson	Apr 1998	A
5738092	Mock et al.	Apr 1998	A
5740792	Ashley et al.	Apr 1998	A
5743267	Nikolic et al.	Apr 1998	A
5752506	Richardson	May 1998	A
5752509	Lachmann et al.	May 1998	A
5755218	Johansson et al.	May 1998	A
5758652	Nikolic	Jun 1998	A
5778874	Maguire et al.	Jul 1998	A
5794612	Wachter et al.	Aug 1998	A
5800361	Rayburn	Sep 1998	A
5806514	Mock et al.	Sep 1998	A
5809997	Wolf	Sep 1998	A
5813397	Goodman et al.	Sep 1998	A
5819723	Joseph	Oct 1998	A
5822715	Worthington et al.	Oct 1998	A
5826570	Goodman et al.	Oct 1998	A
5827179	Lichter et al.	Oct 1998	A
5839430	Cama	Nov 1998	A
5865171	Cinquin	Feb 1999	A
5865174	Kloeppel	Feb 1999	A
5875777	Eriksson	Mar 1999	A
5878744	Pfeiffer	Mar 1999	A
5881723	Wallace et al.	Mar 1999	A
5884622	Younes	Mar 1999	A
5891023	Lynn	Apr 1999	A
5899203	Defares et al.	May 1999	A
5915379	Wallace et al.	Jun 1999	A
5915380	Wallace et al.	Jun 1999	A
5921920	Marshall et al.	Jul 1999	A
5924418	Lewis	Jul 1999	A
5931160	Gilmore et al.	Aug 1999	A
5932812	Delsing	Aug 1999	A
5937854	Stenzler	Aug 1999	A
5956501	Brown	Sep 1999	A
5957861	Combs et al.	Sep 1999	A
5971937	Ekstrom	Oct 1999	A
5975081	Hood et al.	Nov 1999	A
5979440	Honkonen et al.	Nov 1999	A
5980466	Thomson	Nov 1999	A
6003070	Frantz	Dec 1999	A
6012450	Rubsamen	Jan 2000	A
6017315	Starr et al.	Jan 2000	A
6024089	Wallace et al.	Feb 2000	A
6026323	Skladnev et al.	Feb 2000	A
6032119	Brown et al.	Feb 2000	A
6055506	Frasca, Jr.	Apr 2000	A
6073110	Rhodes et al.	Jun 2000	A
6099481	Daniels et al.	Aug 2000	A
6106481	Cohen	Aug 2000	A
6118847	Hernandez-Guerra et al.	Sep 2000	A
6119684	Nohl et al.	Sep 2000	A
6148814	Clemmer et al.	Nov 2000	A
6148815	Wolf	Nov 2000	A
6155257	Lurie et al.	Dec 2000	A
6158432	Biondi et al.	Dec 2000	A
6159147	Lichter et al.	Dec 2000	A
6162183	Hoover	Dec 2000	A
6167362	Brown et al.	Dec 2000	A
6168568	Gavriely	Jan 2001	B1
6171264	Bader	Jan 2001	B1
6176833	Thomson	Jan 2001	B1
6179784	Daniels	Jan 2001	B1
6186956	McNamee	Feb 2001	B1
6190326	McKinnon et al.	Feb 2001	B1
6192876	Denyer et al.	Feb 2001	B1
6198963	Haim et al.	Mar 2001	B1
6199550	Wiesmann et al.	Mar 2001	B1
6202642	McKinnon et al.	Mar 2001	B1
6213955	Karakasoglu et al.	Apr 2001	B1
6223744	Garon	May 2001	B1
6224553	Nevo	May 2001	B1
6233539	Brown	May 2001	B1
6234963	Blike et al.	May 2001	B1
6240920	Strom	Jun 2001	B1
6251082	Rayburn	Jun 2001	B1
6261238	Gavriely	Jul 2001	B1
6269810	Brooker et al.	Aug 2001	B1
6269812	Wallace et al.	Aug 2001	B1
6273088	Hillsman	Aug 2001	B1
6279574	Richardson et al.	Aug 2001	B1
6283923	Finkelstein et al.	Sep 2001	B1
6287264	Hoffman	Sep 2001	B1
6301497	Neustadter	Oct 2001	B1
6302106	Lewis	Oct 2001	B1
6305373	Wallace et al.	Oct 2001	B1
6322502	Schoenberg et al.	Nov 2001	B1
6339410	Milner et al.	Jan 2002	B1
6340348	Krishnan et al.	Jan 2002	B1
6342040	Starr et al.	Jan 2002	B1
6349722	Gradon et al.	Feb 2002	B1
6349724	Burton et al.	Feb 2002	B1
6355002	Faram et al.	Mar 2002	B1
6360745	Wallace et al.	Mar 2002	B1
6362620	Debbins et al.	Mar 2002	B1
6367475	Kofoed et al.	Apr 2002	B1
6369838	Wallace et al.	Apr 2002	B1
6370419	Lampotang et al.	Apr 2002	B2
6375614	Braun et al.	Apr 2002	B1
6377046	Debbins et al.	Apr 2002	B1
6379301	Worthington et al.	Apr 2002	B1
6390088	Nohl et al.	May 2002	B1
6390091	Banner et al.	May 2002	B1
6390092	Leenhoven	May 2002	B1
6390977	Faithfull et al.	May 2002	B1
6397286	Chatenever et al.	May 2002	B1
6402698	Mault	Jun 2002	B1
6408043	Hu et al.	Jun 2002	B1
6415792	Schoolman	Jul 2002	B1
6416471	Kumar et al.	Jul 2002	B1
6421650	Goetz et al.	Jul 2002	B1
6427687	Kirk	Aug 2002	B1
6435175	Stenzler	Aug 2002	B1
6436053	Knapp, II et al.	Aug 2002	B1
6450164	Banner et al.	Sep 2002	B1
6454708	Ferguson et al.	Sep 2002	B1
6459933	Lurie et al.	Oct 2002	B1
6463930	Biondi et al.	Oct 2002	B2
6471658	Daniels et al.	Oct 2002	B1
6477424	Thompson et al.	Nov 2002	B1
6488029	Hood et al.	Dec 2002	B1
6488629	Saetre et al.	Dec 2002	B1
RE37970	Costello, Jr.	Jan 2003	E
6511426	Hossack et al.	Jan 2003	B1
6512938	Claure et al.	Jan 2003	B2
6515683	Wright	Feb 2003	B1
6517497	Rymut et al.	Feb 2003	B2
6533723	Lockery et al.	Mar 2003	B1
6533730	Strom	Mar 2003	B2
6543449	Woodring et al.	Apr 2003	B1
6543701	Ho	Apr 2003	B1
6544192	Starr et al.	Apr 2003	B2
6547728	Cornuejols	Apr 2003	B1
6551252	Sackner et al.	Apr 2003	B2
6553992	Berthon-Jones et al.	Apr 2003	B1
6557554	Sugiura	May 2003	B1
6566875	Hasson et al.	May 2003	B1
6571122	Schroeppel et al.	May 2003	B2
6571796	Banner et al.	Jun 2003	B2
6578575	Jonson	Jun 2003	B1
6581117	Klein et al.	Jun 2003	B1
6581592	Bathe et al.	Jun 2003	B1
6584973	Biondi et al.	Jul 2003	B1
6597939	Lampotang et al.	Jul 2003	B1
6599252	Starr	Jul 2003	B2
6603494	Banks et al.	Aug 2003	B1
6606993	Wiesmann et al.	Aug 2003	B1
6620106	Mault	Sep 2003	B2
6621917	Vilser	Sep 2003	B1
6629934	Mault et al.	Oct 2003	B2
6630176	Li et al.	Oct 2003	B2
6644312	Berthon-Jones et al.	Nov 2003	B2
6645158	Mault	Nov 2003	B2
6650346	Jaeger et al.	Nov 2003	B1
6651653	Honkonen et al.	Nov 2003	B1
6656129	Niles et al.	Dec 2003	B2
6665385	Rogers et al.	Dec 2003	B2
6668829	Biondi et al.	Dec 2003	B2
6671529	Claure et al.	Dec 2003	B2
6673018	Friedman	Jan 2004	B2
6675801	Wallace et al.	Jan 2004	B2
6679258	Strom	Jan 2004	B1
6681764	Honkonen et al.	Jan 2004	B1
6698423	Honkonen et al.	Mar 2004	B1
6707476	Hochstedler	Mar 2004	B1
6708688	Rubin et al.	Mar 2004	B1
6709405	Jonson	Mar 2004	B2
6712762	Lichter et al.	Mar 2004	B1
6718975	Blomberg	Apr 2004	B2
6725077	Balloni et al.	Apr 2004	B1
6725860	Wallroth et al.	Apr 2004	B2
6733449	Krishnamurthy et al.	May 2004	B1
6738079	Kellerman et al.	May 2004	B1
6740046	Knapp, II et al.	May 2004	B2
6743172	Blike	Jun 2004	B1
6744374	Kuenzner	Jun 2004	B1
6745764	Hickle	Jun 2004	B2
6755193	Berthon-Jones et al.	Jun 2004	B2
6755787	Hossack et al.	Jun 2004	B2
6760610	Tschupp et al.	Jul 2004	B2
6776159	Pelerossi et al.	Aug 2004	B2
6782888	Friberg et al.	Aug 2004	B1
6790178	Mault et al.	Sep 2004	B1
6792066	Harder et al.	Sep 2004	B1
6796305	Banner et al.	Sep 2004	B1
6801227	Bocionek et al.	Oct 2004	B2
6801802	Sitzman et al.	Oct 2004	B2
6804656	Rosenfeld et al.	Oct 2004	B1
6805118	Brooker et al.	Oct 2004	B2
6807965	Hickle	Oct 2004	B1
6820614	Bonutti	Nov 2004	B2
6820618	Banner et al.	Nov 2004	B2
6822223	Davis	Nov 2004	B2
6824520	Orr et al.	Nov 2004	B2
6828910	VanRyzin et al.	Dec 2004	B2
6830046	Blakley et al.	Dec 2004	B2
6834647	Blair et al.	Dec 2004	B2
6837242	Younes	Jan 2005	B2
6839753	Biondi et al.	Jan 2005	B2
6845773	Berthon-Jones et al.	Jan 2005	B2
6858006	MacCarter et al.	Feb 2005	B2
6860266	Blike	Mar 2005	B2
6866629	Bardy	Mar 2005	B2
6893397	Bardy	May 2005	B2
6895963	Martin	May 2005	B1
6899103	Hood et al.	May 2005	B1
6899683	Mault et al.	May 2005	B2
6899684	Mault et al.	May 2005	B2
6910481	Kimmel et al.	Jun 2005	B2
6921369	Gehrke et al.	Jul 2005	B1
6923079	Snibbe	Aug 2005	B1
6931269	Terry	Aug 2005	B2
6932083	Jones et al.	Aug 2005	B2
6932767	Landry et al.	Aug 2005	B2
6947780	Scharf	Sep 2005	B2
6951541	Desmarais	Oct 2005	B2
6954702	Pierry et al.	Oct 2005	B2
6956572	Zaleski	Oct 2005	B2
6970919	Doi et al.	Nov 2005	B1
6976958	Quy	Dec 2005	B2
6986347	Hickle	Jan 2006	B2
6997185	Han et al.	Feb 2006	B2
6997880	Carlebach et al.	Feb 2006	B2
7002468	Eveland et al.	Feb 2006	B2
7008380	Rees et al.	Mar 2006	B1
7017574	Biondi et al.	Mar 2006	B2
7019652	Richardson	Mar 2006	B2
7033323	Botbol et al.	Apr 2006	B2
7036504	Wallace et al.	May 2006	B2
7039878	Auer et al.	May 2006	B2
7040315	Strömberg	May 2006	B1
7040318	Däscher et al.	May 2006	B2
7040321	Göbel	May 2006	B2
7046254	Brown et al.	May 2006	B2
7047092	Wimsatt	May 2006	B2
7051088	Sesek	May 2006	B2
7051736	Banner et al.	May 2006	B2
7062251	Birkett et al.	Jun 2006	B2
7066173	Banner et al.	Jun 2006	B2
7077125	Scheuch	Jul 2006	B2
7081091	Merrett et al.	Jul 2006	B2
7081095	Lynn et al.	Jul 2006	B2
7083574	Kline	Aug 2006	B2
7089927	John et al.	Aug 2006	B2
7089932	Dodds	Aug 2006	B2
7089937	Berthon-Jones et al.	Aug 2006	B2
7094208	Williams et al.	Aug 2006	B2
7099801	McBride et al.	Aug 2006	B1
7116810	Miller et al.	Oct 2006	B2
7117438	Wallace et al.	Oct 2006	B2
7128578	Lampotang et al.	Oct 2006	B2
7147600	Bardy	Dec 2006	B2
7154397	Zerhusen et al.	Dec 2006	B2
7154398	Chen et al.	Dec 2006	B2
7156808	Quy	Jan 2007	B2
7162296	Leonhardt et al.	Jan 2007	B2
7164972	Imhof et al.	Jan 2007	B2
7165221	Monteleone et al.	Jan 2007	B2
7169112	Caldwell	Jan 2007	B2
7171606	Blackburn et al.	Jan 2007	B2
7172557	Parker	Feb 2007	B1
7182083	Yanof et al.	Feb 2007	B2
7187790	Sabol et al.	Mar 2007	B2
7188621	DeVries et al.	Mar 2007	B2
7201734	Hickle	Apr 2007	B2
7203353	Klotz et al.	Apr 2007	B2
7210478	Banner et al.	May 2007	B2
7211049	Bradley et al.	May 2007	B2
7219666	Friberg et al.	May 2007	B2
7220230	Roteliuk et al.	May 2007	B2
7222054	Geva	May 2007	B2
7223965	Davis	May 2007	B2
7225809	Bowen	Jun 2007	B1
7228323	Angerer et al.	Jun 2007	B2
7241269	McCawley et al.	Jul 2007	B2
7246618	Habashi	Jul 2007	B2
7247154	Hickle	Jul 2007	B2
7252640	Ni et al.	Aug 2007	B2
7256708	Rosenfeld et al.	Aug 2007	B2
7258670	Bardy	Aug 2007	B2
7261690	Teller et al.	Aug 2007	B2
7264730	Connell et al.	Sep 2007	B2
7270126	Wallace et al.	Sep 2007	B2
7275540	Bolam et al.	Oct 2007	B2
7278579	Loffredo et al.	Oct 2007	B2
7282032	Miller	Oct 2007	B2
7285090	Stivoric et al.	Oct 2007	B2
7294105	Islam	Nov 2007	B1
7294112	Dunlop	Nov 2007	B1
7298280	Voege et al.	Nov 2007	B2
7300418	Zaleski	Nov 2007	B2
7303680	Connell et al.	Dec 2007	B2
7307543	Rosenfeld et al.	Dec 2007	B2
7308550	Cornett	Dec 2007	B2
7310551	Koh et al.	Dec 2007	B1
7310720	Cornett	Dec 2007	B2
7311665	Hawthorne et al.	Dec 2007	B2
7314451	Halperin et al.	Jan 2008	B2
7315825	Rosenfeld et al.	Jan 2008	B2
7316231	Hickle	Jan 2008	B2
7318808	Tarassenko et al.	Jan 2008	B2
7318892	Connell et al.	Jan 2008	B2
7321802	Wasner et al.	Jan 2008	B2
7321862	Rosenfeld et al.	Jan 2008	B2
7322352	Minshull et al.	Jan 2008	B2
7322937	Blomberg et al.	Jan 2008	B2
7331340	Barney	Feb 2008	B2
7333969	Lee et al.	Feb 2008	B2
7334578	Biondi et al.	Feb 2008	B2
7337778	Martin	Mar 2008	B2
7343916	Biondo et al.	Mar 2008	B2
7343917	Jones	Mar 2008	B2
7347200	Jones et al.	Mar 2008	B2
7347207	Ahlmen et al.	Mar 2008	B2
7351340	Connell et al.	Apr 2008	B2
7362341	McGuire et al.	Apr 2008	B2
7367337	Berthon-Jones et al.	May 2008	B2
7367955	Zhang et al.	May 2008	B2
7369757	Farbarik	May 2008	B2
7374535	Schoenberg et al.	May 2008	B2
7377276	Roy et al.	May 2008	B2
7380210	Lontka et al.	May 2008	B2
RE40365	Kirchgeorg et al.	Jun 2008	E
7383148	Ahmed	Jun 2008	B2
7387610	Stahmann et al.	Jun 2008	B2
7395216	Rosenfeld et al.	Jul 2008	B2
7413546	Agutter et al.	Aug 2008	B2
7422562	Hatib et al.	Sep 2008	B2
7425201	Euliano et al.	Sep 2008	B2
7433827	Rosenfeld et al.	Oct 2008	B2
7435220	Ranucci	Oct 2008	B2
7438072	Izuchukwu	Oct 2008	B2
7438073	Delache et al.	Oct 2008	B2
7448383	Delache et al.	Nov 2008	B2
7452333	Roteliuk	Nov 2008	B2
7454359	Rosenfeld et al.	Nov 2008	B2
7454360	Rosenfeld et al.	Nov 2008	B2
7464339	Keenan, Jr. et al.	Dec 2008	B2
7467094	Rosenfeld et al.	Dec 2008	B2
7469698	Childers et al.	Dec 2008	B1
7475019	Rosenfeld et al.	Jan 2009	B2
7487774	Acker	Feb 2009	B2
7490085	Walker et al.	Feb 2009	B2
7496400	Hoskonen et al.	Feb 2009	B2
7500481	Delache et al.	Mar 2009	B2
7504954	Spaeder	Mar 2009	B2
7512450	Ahmed	Mar 2009	B2
7512593	Karklins et al.	Mar 2009	B2
7527053	DeVries et al.	May 2009	B2
7527054	Misholi	May 2009	B2
7530353	Choncholas et al.	May 2009	B2
RE40806	Gradon et al.	Jun 2009	E
7543582	Lu et al.	Jun 2009	B2
7548833	Ahmed	Jun 2009	B2
7552731	Jorczak et al.	Jun 2009	B2
7556036	Bouillon et al.	Jul 2009	B2
7559903	Moussavi et al.	Jul 2009	B2
7562657	Blanch et al.	Jul 2009	B2
7565905	Hickle	Jul 2009	B2
7574368	Pawlikowski	Aug 2009	B2
7584712	Lu	Sep 2009	B2
7590551	Auer	Sep 2009	B2
7597099	Jones et al.	Oct 2009	B2
7603170	Hatlestad et al.	Oct 2009	B2
7603631	Bermudez et al.	Oct 2009	B2
7606668	Pierry et al.	Oct 2009	B2
7609138	Dietrich et al.	Oct 2009	B2
7610915	Dittmann	Nov 2009	B2
7618378	Bingham et al.	Nov 2009	B2
7625345	Quinn	Dec 2009	B2
7630755	Stahmann et al.	Dec 2009	B2
7650181	Freeman et al.	Jan 2010	B2
7650291	Rosenfeld et al.	Jan 2010	B2
7652571	Parkulo et al.	Jan 2010	B2
7654966	Westinskow et al.	Feb 2010	B2
7658188	Halpern et al.	Feb 2010	B2
7662106	Daniels et al.	Feb 2010	B2
7668579	Lynn	Feb 2010	B2
7669598	Rick et al.	Mar 2010	B2
7671733	McNeal et al.	Mar 2010	B2
7678063	Felmlee et al.	Mar 2010	B2
7682312	Lurie	Mar 2010	B2
7684931	Pierry et al.	Mar 2010	B2
7693697	Westenskow et al.	Apr 2010	B2
7698156	Martucci et al.	Apr 2010	B2
7708015	Seeger et al.	May 2010	B2
7717112	Sun et al.	May 2010	B2
7731663	Averina et al.	Jun 2010	B2
7736132	Bliss et al.	Jun 2010	B2
7740013	Ishizaki et al.	Jun 2010	B2
7753049	Jorczak et al.	Jul 2010	B2
7766012	Scheuch et al.	Aug 2010	B2
7771364	Arbel et al.	Aug 2010	B2
7772965	Farhan et al.	Aug 2010	B2
7778709	Gollasch et al.	Aug 2010	B2
7778851	Schoenberg et al.	Aug 2010	B2
7784461	Figueiredo et al.	Aug 2010	B2
7785263	Roteliuk et al.	Aug 2010	B2
7785265	Schätzl	Aug 2010	B2
7793659	Breen	Sep 2010	B2
7793660	Kimmel et al.	Sep 2010	B2
7810497	Pittman et al.	Oct 2010	B2
7814906	Moretti	Oct 2010	B2
7819815	Younes	Oct 2010	B2
7831450	Schoenberg et al.	Nov 2010	B2
7832394	Schechter et al.	Nov 2010	B2
7836882	Rumph et al.	Nov 2010	B1
7837629	Bardy	Nov 2010	B2
7844657	Novak	Nov 2010	B2
7850619	Gavish et al.	Dec 2010	B2
7855656	Maschke	Dec 2010	B2
7855716	McCreary et al.	Dec 2010	B2
7859401	Falck et al.	Dec 2010	B2
7866317	Muellinger et al.	Jan 2011	B2
7871394	Halbert et al.	Jan 2011	B2
7874290	Chalvignac	Jan 2011	B2
7881780	Flaherty	Feb 2011	B2
7883480	Dunlop	Feb 2011	B2
7885828	Glaser-Seidnitzer et al.	Feb 2011	B2
7886231	Hopermann et al.	Feb 2011	B2
7891353	Chalvignac	Feb 2011	B2
7895527	Zaleski et al.	Feb 2011	B2
7909033	Faram	Mar 2011	B2
7912537	Lee et al.	Mar 2011	B2
7927286	Ranucci	Apr 2011	B2
7931601	Ranucci	Apr 2011	B2
7953419	Jost et al.	May 2011	B2
7956719	Anderson, Jr. et al.	Jun 2011	B2
7958892	Kwok et al.	Jun 2011	B2
7970450	Kroecker et al.	Jun 2011	B2
7981042	Stahmann	Jul 2011	B2
8015972	Pirzada	Sep 2011	B2
8105282	Susi	Jan 2012	B2
8151792	Ishizaki	Apr 2012	B2
8214231	Martucci	Jul 2012	B2
8276585	Buckley	Oct 2012	B2
8381724	Bowen	Feb 2013	B2
8500694	Susi	Aug 2013	B2
8545416	Kayyali	Oct 2013	B1
8596269	Chalvignac	Dec 2013	B2
8627819	DeVries	Jan 2014	B2
8679012	Kayyali	Mar 2014	B1
8747329	Bardy	Jun 2014	B2
8795168	Goh	Aug 2014	B2
8844522	Huby	Sep 2014	B2
8881724	Choncholas	Nov 2014	B2
8882747	Hood	Nov 2014	B2
8938753	Tang	Jan 2015	B2
8939147	Henry	Jan 2015	B2
8968195	Tran	Mar 2015	B2
9058741	Steinhauer	Jun 2015	B2
9098114	Potter	Aug 2015	B2
9155919	Huh	Oct 2015	B2
9177109	Steinhauer	Nov 2015	B2
9202008	Frederick	Dec 2015	B1
9210359	Kim	Dec 2015	B2
9327090	Steinhauer	Mar 2016	B2
9330497	Byrd	May 2016	B2
9364625	Silver	Jun 2016	B2
9426607	Shelly	Aug 2016	B2
9436645	Al-Ali	Sep 2016	B2
9463294	Laura Lapoint	Oct 2016	B2
9533114	Kayyali	Jan 2017	B1
9550037	Seiver	Jan 2017	B2
9600304	DiVincent	Mar 2017	B2
9621433	Yoshida	Apr 2017	B2
9662464	Shelly	May 2017	B2
9671928	Kreiner	Jun 2017	B2
9734293	Collins, Jr.	Aug 2017	B2
9736546	Ferren	Aug 2017	B2
9737675	Frame	Aug 2017	B2
9737676	Steinhauer	Aug 2017	B2
9743890	Lord	Aug 2017	B2
9769413	Kim	Sep 2017	B2
9775566	Sullivan	Oct 2017	B2
9820658	Tran	Nov 2017	B2
9821129	Steinhauer	Nov 2017	B2
9833584	Ahmad	Dec 2017	B2
9839058	Shelly	Dec 2017	B2
9839398	Yamamori	Dec 2017	B2
9861743	Susi	Jan 2018	B2
9876652	Tatzel	Jan 2018	B2
9888881	Hulvershorn	Feb 2018	B2
9895066	Krauss	Feb 2018	B2
9913617	Al-Ali	Mar 2018	B2
9956365	Bonassa	May 2018	B2
9993207	Al-Ali	Jun 2018	B2
9998580	Brogan	Jun 2018	B2
10076269	Kayyali	Sep 2018	B1
10098594	Shtalryd	Oct 2018	B2
10117975	Wall	Nov 2018	B2
10159811	Silver	Dec 2018	B2
10179217	Steinhauer	Jan 2019	B2
10245437	Kantor	Apr 2019	B2
10255647	Rodman	Apr 2019	B2
10334888	Cameron	Jul 2019	B2
10335031	Kundu	Jul 2019	B1
10448885	Schmid	Oct 2019	B2
10478118	Frederick	Nov 2019	B1
10569036	Delangre	Feb 2020	B2
10576226	Kwok	Mar 2020	B2
10638999	Shah	May 2020	B2
10646673	Steinhauer	May 2020	B2
10646674	Steinhauer	May 2020	B2
10668234	Paul	Jun 2020	B2
10678400	Kreiner	Jun 2020	B2
10679748	Durlach	Jun 2020	B2
10734112	Bychkov	Aug 2020	B2
10744284	Paul	Aug 2020	B2
10814082	Birnkrant	Oct 2020	B2
10828438	Thompson	Nov 2020	B2
10835700	Lunz	Nov 2020	B2
10843014	Dobbing	Nov 2020	B2
10905611	Sidhu	Feb 2021	B2
20010056358	Dulong et al.	Dec 2001	A1
20020026941	Biondi et al.	Mar 2002	A1
20020044059	Reeder et al.	Apr 2002	A1
20020077863	Rutledge et al.	Jun 2002	A1
20020091548	Auer et al.	Jul 2002	A1
20020133061	Manetta	Sep 2002	A1
20020177758	Schoenberg et al.	Nov 2002	A1
20030028226	Thompson et al.	Feb 2003	A1
20030060723	Joo et al.	Mar 2003	A1
20030062045	Woodring et al.	Apr 2003	A1
20030106553	Vanderveen	Jun 2003	A1
20030130567	Mault et al.	Jul 2003	A1
20030130595	Mault	Jul 2003	A1
20030140928	Bui et al.	Jul 2003	A1
20030140929	Wilkes et al.	Jul 2003	A1
20030141368	Pascual et al.	Jul 2003	A1
20030141981	Bui et al.	Jul 2003	A1
20030144878	Wilkes et al.	Jul 2003	A1
20030144880	Talachian et al.	Jul 2003	A1
20030144881	Talachian et al.	Jul 2003	A1
20030144882	Talachian et al.	Jul 2003	A1
20030201697	Richardson	Oct 2003	A1
20030204414	Wilkes et al.	Oct 2003	A1
20030204416	Radpay et al.	Oct 2003	A1
20030204419	Wilkes et al.	Oct 2003	A1
20030204420	Wilkes et al.	Oct 2003	A1
20030208152	Avrahami et al.	Nov 2003	A1
20030208465	Yurko et al.	Nov 2003	A1
20030222548	Richardson et al.	Dec 2003	A1
20030230308	Linden	Dec 2003	A1
20040010425	Wilkes et al.	Jan 2004	A1
20040034289	Teller et al.	Feb 2004	A1
20040059604	Zaleski	Mar 2004	A1
20040073453	Nenov et al.	Apr 2004	A1
20040078231	Wilkes et al.	Apr 2004	A1
20040121767	Simpson et al.	Jun 2004	A1
20040122294	Hatlestad et al.	Jun 2004	A1
20040143677	Novak	Jul 2004	A1
20040150525	Wilson et al.	Aug 2004	A1
20040167465	Mihai et al.	Aug 2004	A1
20040167804	Simpson et al.	Aug 2004	A1
20040172222	Simpson et al.	Sep 2004	A1
20040172300	Mihai et al.	Sep 2004	A1
20040172301	Mihai et al.	Sep 2004	A1
20040172302	Martucci et al.	Sep 2004	A1
20040176667	Mihai et al.	Sep 2004	A1
20040224293	Penning et al.	Nov 2004	A1
20040236240	Kraus et al.	Nov 2004	A1
20040249673	Smith	Dec 2004	A1
20050016534	Ost	Jan 2005	A1
20050033198	Kehyayan et al.	Feb 2005	A1
20050054910	Tremblay et al.	Mar 2005	A1
20050055242	Bello et al.	Mar 2005	A1
20050055244	Mullan et al.	Mar 2005	A1
20050065817	Mihai et al.	Mar 2005	A1
20050075542	Goldreich	Apr 2005	A1
20050075904	Wager et al.	Apr 2005	A1
20050085869	Tehrani et al.	Apr 2005	A1
20050108057	Cohen et al.	May 2005	A1
20050112013	DeVries et al.	May 2005	A1
20050112325	Hickle	May 2005	A1
20050124866	Elaz et al.	Jun 2005	A1
20050133027	Elaz et al.	Jun 2005	A1
20050137480	Alt et al.	Jun 2005	A1
20050139213	Blike	Jun 2005	A1
20050143632	Elaz et al.	Jun 2005	A1
20050156933	Lee et al.	Jul 2005	A1
20050171876	Golden	Aug 2005	A1
20050177096	Bollish et al.	Aug 2005	A1
20050177400	Rosenfeld et al.	Aug 2005	A1
20050188083	Biondi et al.	Aug 2005	A1
20050192488	Bryenton et al.	Sep 2005	A1
20050204310	De Zwart et al.	Sep 2005	A1
20050215904	Sumanaweera et al.	Sep 2005	A1
20050217674	Burton et al.	Oct 2005	A1
20050251040	Relkuntwar et al.	Nov 2005	A1
20050288571	Perkins et al.	Dec 2005	A1
20060025657	Rosenfeld et al.	Feb 2006	A1
20060047202	Elliott	Mar 2006	A1
20060078867	Penny et al.	Apr 2006	A1
20060080140	Buttner et al.	Apr 2006	A1
20060080343	Carter et al.	Apr 2006	A1
20060085229	Rosenfeld et al.	Apr 2006	A9
20060102171	Gavish	May 2006	A1
20060122474	Teller et al.	Jun 2006	A1
20060129055	Orr et al.	Jun 2006	A1
20060144396	DeVries et al.	Jul 2006	A1
20060149144	Lynn et al.	Jul 2006	A1
20060149589	Wager	Jul 2006	A1
20060150982	Wood	Jul 2006	A1
20060155206	Lynn	Jul 2006	A1
20060155207	Lynn et al.	Jul 2006	A1
20060161071	Lynn et al.	Jul 2006	A1
20060173257	Nagai et al.	Aug 2006	A1
20060174884	Habashi	Aug 2006	A1
20060178911	Syed et al.	Aug 2006	A1
20060189880	Lynn et al.	Aug 2006	A1
20060189900	Flaherty	Aug 2006	A1
20060195041	Lynn et al.	Aug 2006	A1
20060196507	Bradley	Sep 2006	A1
20060200009	Wekell et al.	Sep 2006	A1
20060213518	DeVries et al.	Sep 2006	A1
20060229822	Theobald et al.	Oct 2006	A1
20060235324	Lynn	Oct 2006	A1
20060237015	Berthon-Jones et al.	Oct 2006	A1
20060249151	Gambone	Nov 2006	A1
20060249153	DeVries et al.	Nov 2006	A1
20060264762	Starr	Nov 2006	A1
20060271409	Rosenfeld et al.	Nov 2006	A1
20060278221	Schermeier et al.	Dec 2006	A1
20060278222	Schermeier et al.	Dec 2006	A1
20060293609	Stahmann et al.	Dec 2006	A1
20060294464	Tokimoto et al.	Dec 2006	A1
20070000490	DeVries et al.	Jan 2007	A1
20070000494	Banner et al.	Jan 2007	A1
20070016441	Stroup	Jan 2007	A1
20070017515	Wallace et al.	Jan 2007	A1
20070021673	Arbel et al.	Jan 2007	A1
20070028921	Banner et al.	Feb 2007	A1
20070038081	Eck et al.	Feb 2007	A1
20070060812	Harel et al.	Mar 2007	A1
20070062532	Choncholas	Mar 2007	A1
20070062533	Choncholas et al.	Mar 2007	A1
20070073181	Pu et al.	Mar 2007	A1
20070113849	Matthews et al.	May 2007	A1
20070119453	Lu et al.	May 2007	A1
20070123758	Miesel et al.	May 2007	A1
20070123792	Kline	May 2007	A1
20070129647	Lynn	Jun 2007	A1
20070149860	Lynn et al.	Jun 2007	A1
20070155208	Pirzada	Jul 2007	A1
20070156060	Cervantes	Jul 2007	A1
20070156456	McGillin et al.	Jul 2007	A1
20070157931	Parker et al.	Jul 2007	A1
20070163589	DeVries et al.	Jul 2007	A1
20070179357	Bardy	Aug 2007	A1
20070185390	Perkins et al.	Aug 2007	A1
20070191697	Lynn et al.	Aug 2007	A1
20070199566	Be'eri	Aug 2007	A1
20070208438	El-Mankabady et al.	Sep 2007	A1
20070215155	Marx et al.	Sep 2007	A1
20070225574	Ueda	Sep 2007	A1
20070241884	Yamazaki et al.	Oct 2007	A1
20070265510	Bardy	Nov 2007	A1
20070265877	Rice et al.	Nov 2007	A1
20070271122	Zaleski	Nov 2007	A1
20070272241	Sanborn et al.	Nov 2007	A1
20070272242	Sanborn et al.	Nov 2007	A1
20070273216	Farbarik	Nov 2007	A1
20070276439	Miesel et al.	Nov 2007	A1
20070293741	Bardy	Dec 2007	A1
20080000477	Huster et al.	Jan 2008	A1
20080000479	Elaz et al.	Jan 2008	A1
20080033661	Syroid et al.	Feb 2008	A1
20080039735	Hickerson	Feb 2008	A1
20080041380	Wallace et al.	Feb 2008	A1
20080045844	Arbel et al.	Feb 2008	A1
20080047554	Roy et al.	Feb 2008	A1
20080053438	DeVries et al.	Mar 2008	A1
20080064963	Schwaibold et al.	Mar 2008	A1
20080065420	Tirinato et al.	Mar 2008	A1
20080066753	Martin et al.	Mar 2008	A1
20080072896	Setzer et al.	Mar 2008	A1
20080072900	Kenyon et al.	Mar 2008	A1
20080072901	Habashi	Mar 2008	A1
20080072902	Setzer et al.	Mar 2008	A1
20080076970	Foulis et al.	Mar 2008	A1
20080077038	McDonough et al.	Mar 2008	A1
20080078390	Milne et al.	Apr 2008	A1
20080092043	Trethewey	Apr 2008	A1
20080103368	Craine et al.	May 2008	A1
20080110460	Elaz et al.	May 2008	A1
20080125873	Payne et al.	May 2008	A1
20080143515	Wood et al.	Jun 2008	A1
20080161653	Lin et al.	Jul 2008	A1
20080178880	Christopher et al.	Jul 2008	A1
20080178882	Christopher et al.	Jul 2008	A1
20080183057	Taube	Jul 2008	A1
20080185009	Choncholas et al.	Aug 2008	A1
20080208012	Ali	Aug 2008	A1
20080214947	Hunt et al.	Sep 2008	A1
20080230057	Sutherland	Sep 2008	A1
20080236582	Tehrani	Oct 2008	A1
20080236585	Parker et al.	Oct 2008	A1
20080243016	Liao et al.	Oct 2008	A1
20080251070	Pinskiy et al.	Oct 2008	A1
20080255880	Beller et al.	Oct 2008	A1
20080270912	Booth	Oct 2008	A1
20080281219	Glickman et al.	Nov 2008	A1
20080293025	Zamierowsi et al.	Nov 2008	A1
20080295830	Martonen et al.	Dec 2008	A1
20080295839	Habashi	Dec 2008	A1
20080306351	Izumi	Dec 2008	A1
20080308109	Brain	Dec 2008	A1
20080312954	Ullrich et al.	Dec 2008	A1
20080319513	Pu et al.	Dec 2008	A1
20090005651	Ward et al.	Jan 2009	A1
20090007909	Carrico	Jan 2009	A1
20090038921	Kaps et al.	Feb 2009	A1
20090054743	Stewart	Feb 2009	A1
20090062725	Goebel	Mar 2009	A1
20090063181	Nho et al.	Mar 2009	A1
20090065004	Childers et al.	Mar 2009	A1
20090076342	Amurthur et al.	Mar 2009	A1
20090124917	Hatlestad et al.	May 2009	A1
20090125333	Heywood et al.	May 2009	A1
20090126734	Dunsmore et al.	May 2009	A1
20090131758	Heywood et al.	May 2009	A1
20090133701	Brain	May 2009	A1
20090143694	Krauss et al.	Jun 2009	A1
20090145438	Brain	Jun 2009	A1
20090149200	Jayasinghe et al.	Jun 2009	A1
20090149723	Krauss et al.	Jun 2009	A1
20090149927	Kneuer et al.	Jun 2009	A1
20090150184	Spahn	Jun 2009	A1
20090171167	Baker, Jr.	Jul 2009	A1
20090192421	Huster et al.	Jul 2009	A1
20090209828	Musin	Aug 2009	A1
20090209849	Rowe et al.	Aug 2009	A1
20090216145	Skerl et al.	Aug 2009	A1
20090221926	Younes	Sep 2009	A1
20090240523	Friedlander et al.	Sep 2009	A1
20090241952	Nicolazzi et al.	Oct 2009	A1
20090241956	Baker, Jr. et al.	Oct 2009	A1
20090241957	Baker, Jr.	Oct 2009	A1
20090241958	Baker, Jr.	Oct 2009	A1
20090244003	Bonnat	Oct 2009	A1
20090250054	Loncar et al.	Oct 2009	A1
20100004517	Bryenton et al.	Jan 2010	A1
20100022904	Centen	Jan 2010	A1
20100030092	Kristensen et al.	Feb 2010	A1
20100048985	Henke et al.	Feb 2010	A1
20100048986	Henke et al.	Feb 2010	A1
20100049034	Eck et al.	Feb 2010	A1
20100049264	Henke et al.	Feb 2010	A1
20100049265	Henke et al.	Feb 2010	A1
20100056852	Henke et al.	Mar 2010	A1
20100056853	Henke et al.	Mar 2010	A1
20100056855	Henke et al.	Mar 2010	A1
20100056929	Stahmann et al.	Mar 2010	A1
20100056941	Henke et al.	Mar 2010	A1
20100056942	Henke et al.	Mar 2010	A1
20100057148	Henke et al.	Mar 2010	A1
20100059061	Brain	Mar 2010	A1
20100063348	Henke et al.	Mar 2010	A1
20100063350	Henke et al.	Mar 2010	A1
20100063365	Pisani et al.	Mar 2010	A1
20100069774	Bingham et al.	Mar 2010	A1
20100072055	Tanaka et al.	Mar 2010	A1
20100076278	van der Zande et al.	Mar 2010	A1
20100081890	Li et al.	Apr 2010	A1
20100083968	Wondka et al.	Apr 2010	A1
20100095961	Tornesel et al.	Apr 2010	A1
20100130873	Yuen et al.	May 2010	A1
20100160839	Freeman et al.	Jun 2010	A1
20100274100	Behar et al.	Oct 2010	A1
20100298718	Gilham et al.	Nov 2010	A1
20100312132	Wood et al.	Dec 2010	A1
20100317980	Guglielmino	Dec 2010	A1
20110004489	Schoenberg et al.	Jan 2011	A1
20110009746	Tran et al.	Jan 2011	A1
20110015493	Koschek	Jan 2011	A1
20110041849	Chen et al.	Feb 2011	A1
20110054289	Derchak et al.	Mar 2011	A1
20120185268	Wiesner	Jul 2012	A1
20150070187	Wiesner	Mar 2015	A1
20150099458	Wiesner	Apr 2015	A1
20170372600	Palin	Dec 2017	A1
20180181091	Funk	Jun 2018	A1

Foreign Referenced Citations (99)

Number	Date	Country
0414777	Mar 1991	EP
1421966	May 2004	EP
1464357	Oct 2004	EP
2319967	Jun 1998	GB
WO 9014852	Dec 1990	WO
WO 9308534	Apr 1993	WO
WO 9312823	Jul 1993	WO
WO 9314696	Aug 1993	WO
WO 9414374	Jul 1994	WO
WO 9508471	Mar 1995	WO
WO 9532480	Nov 1995	WO
WO 9624285	Aug 1996	WO
WO 9720592	Jun 1997	WO
WO 9811840	Mar 1998	WO
WO 9814116	Apr 1998	WO
WO 9829790	Jul 1998	WO
WO 9833554	Aug 1998	WO
WO 9840014	Sep 1998	WO
WO 9841267	Sep 1998	WO
WO 9841267	Sep 1998	WO
WO 9841269	Sep 1998	WO
WO 9841270	Sep 1998	WO
WO 9841271	Sep 1998	WO
WO 9858219	Dec 1998	WO
WO 9903524	Jan 1999	WO
WO 9952431	Oct 1999	WO
WO 9952437	Oct 1999	WO
WO 9959460	Nov 1999	WO
WO 9962403	Dec 1999	WO
WO 0018293	Apr 2000	WO
WO 0019886	Apr 2000	WO
WO 0062664	Oct 2000	WO
WO 200079466	Dec 2000	WO
WO 0100264	Jan 2001	WO
WO 0100265	Jan 2001	WO
WO 0128416	Apr 2001	WO
WO 0134022	May 2001	WO
WO 0245566	Jun 2002	WO
WO 02082967	Oct 2002	WO
WO 03015005	Feb 2003	WO
WO 03024317	Mar 2003	WO
WO 03045493	Jun 2003	WO
WO 03053503	Jul 2003	WO
WO 03060650	Jul 2003	WO
WO 03060651	Jul 2003	WO
WO 03075989	Sep 2003	WO
WO 03075990	Sep 2003	WO
WO 03075991	Sep 2003	WO
WO 03084405	Oct 2003	WO
WO 04014216	Feb 2004	WO
WO 04014226	Feb 2004	WO
WO 04032719	Apr 2004	WO
WO 04043254	May 2004	WO
WO 2005010796	Feb 2005	WO
WO 05024729	Mar 2005	WO
WO 05055825	Jun 2005	WO
WO 05056087	Jun 2005	WO
WO 05069740	Aug 2005	WO
WO 05077260	Aug 2005	WO
WO 05112739	Dec 2005	WO
WO 06008745	Jan 2006	WO
WO 06009830	Jan 2006	WO
WO 06037184	Apr 2006	WO
WO 06050388	May 2006	WO
WO 06051466	May 2006	WO
WO 06078432	Jul 2006	WO
WO 06094055	Sep 2006	WO
WO 06096080	Sep 2006	WO
WO 06109072	Oct 2006	WO
WO 06123956	Nov 2006	WO
WO 06125986	Nov 2006	WO
WO 06125987	Nov 2006	WO
WO 06125989	Nov 2006	WO
WO 06125990	Nov 2006	WO
WO 06137067	Dec 2006	WO
WO 2007033050	Mar 2007	WO
WO 2007106804	Sep 2007	WO
WO 07145948	Dec 2007	WO
WO 2008030091	Mar 2008	WO
WO 2008042699	Apr 2008	WO
WO 2008058997	May 2008	WO
WO 2008062554	May 2008	WO
WO 2008113410	Sep 2008	WO
WO 2008118951	Oct 2008	WO
WO 2008140528	Nov 2008	WO
WO 2008146264	Dec 2008	WO
WO 2008148134	Dec 2008	WO
WO 2009024967	Feb 2009	WO
WO 2009027864	Mar 2009	WO
WO 2009036334	Mar 2009	WO
WO 2009124297	Oct 2009	WO
WO 2010009531	Jan 2010	WO
WO 2010020980	Feb 2010	WO
WO 2010021730	Feb 2010	WO
WO 2010039989	Apr 2010	WO
WO 2010126916	Nov 2010	WO
WO 2010141415	Dec 2010	WO
WO 2011005953	Jan 2011	WO
WO 2011022242	Feb 2011	WO

Non-Patent Literature Citations (10)

Entry
US 7,284,551 B2, 10/2007, Jones et al. (withdrawn)
7200 Series Ventilator, Options, and Accessories: Operator's Manual. Nellcor Puritan Bennett, Part No. 22300 A, Sep. 1990, pp. 1-196.
7200 Ventilatory System: Addendum/Errata. Nellcor Puritan Bennett, Part No. 4-023576-00, Rev. A, Apr. 1998, pp. 1-32.
800 Operator's and Technical Reference Manual. Series Ventilator System, Nellcor Puritan Bennett, Part No. 4-070088-00, Rev. L, Aug. 2010, pp. 1-476.
840 Operator's and Technical Reference Manual. Ventilator System, Nellcor Puritan Bennett, Part No. 4-075609-00, Rev. G, Oct. 2006, pp. 1-424.
Puritan Bennett 980 Series Ventilator Operator's Manual, Covidien, Jan. 29, 2014, Part. No. 10077893 A Jan. 2014, 506 pages.
International Written Opinion for International Application No. PCT/US2021/030117 mailed Jul. 15, 2021 (11 pages).
International Search Report for International Application No. PCT/US2021/030117 mailed Jul. 15, 2021 (4 pages).
Anonymous “Mobile High-Definition Link—Wikipedia” retrieved from the internet Jan. 16, 2020—hllps://en.wikipedia.org/w/index.php?lille=Mobile_High-Definition_Link&oldid=936134359.
Patel. “Apr. 7, 2021 Overview of Mechanical Ventilation—Critical Care Medicine—MSD Manual Professional Edition Overview of Mechanical Ventilation.” Retrieved from the Internet: Mar. 13, 2020 https://www.msdmanuals.com/professional/critical-care-medicine/respiratory-failure-and-mechanical-venlilalion/overview--0f-mechanical-venlilalion#.

Related Publications (1)

	Number	Date	Country
	20230211099 A1	Jul 2023	US

Provisional Applications (2)

	Number	Date	Country
	63050214	Jul 2020	US
	63023343	May 2020	US

Continuations (1)

	Number	Date	Country
Parent	17241638	Apr 2021	US
Child	18185767		US

Remote ventilator adjustment

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract