Patent Application
20140002246
Typically, a ventilator includes a single direction of communication. For example, a ventilator is only able to send data outbound to another entity. Also, the communication is a wire line communication. Accordingly, the wire line single direction ventilator communication functionality is limited.
Moreover, several other aspects of a conventional ventilator are inefficient. As a result, work flow associated with the ventilator is inefficient and negatively affected.
The drawings referred to in this description should be understood as not being drawn to scale except if specifically noted.
Reference will now be made in detail to embodiments of the present technology, examples of which are illustrated in the accompanying drawings. While the technology will be described in conjunction with various embodiment(s), it will be understood that they are not intended to limit the present technology to these embodiments. On the contrary, the present technology is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the various embodiments as defined by the appended claims.
Furthermore, in the following description of embodiments, numerous specific details are set forth in order to provide a thorough understanding of the present technology. However, the present technology may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present embodiments.
Although system 100 depicts ventilator 110 that is able to bi-directionally communication with medical entity 120, it should be appreciated other medical devices may be able to bi-directionally communicate with medical entity 120. However, for clarity and brevity, the description below will primarily focus primarily on the structure and functionality of a ventilator.
In general, ventilator 110 can be any medical ventilator configured to provide the mechanism to move breathable air into and out of the lungs of a patient. For example, ventilator 110 can include a compressible air reservoir or turbine, air and oxygen supplies, a set of valves and tubes, and a patient circuit (not shown).
In particular, ventilator 110 also includes receiver 112 and transmitter 114. Receiver 112 is configured for receiving communication 113 from medical entity 120. Receiver 112 can be a wireless receiver configured for receiving a wireless communication.
Transmitter 114 is configured for transmitting communication 115 to medical entity 120 or to a plurality of different medical entities. Transmitter 114 can be a wireless transmitter for wirelessly transmitting a communication.
Communication 113, received by ventilator 110, can occur in a variety of forms. For example, communication 113 can include, instructions to stream ventilator information, instructions to provide a snapshot of ventilator information, remotely control ventilator 110, instructions to annotate ventilator information, etc.
In one embodiment, communication 113 is associated with ventilator manipulation. For example, communication 113 is associated with the manipulation of ventilator functionality (e.g., changing ventilator settings, etc.).
In some embodiments, communication 113 affects the functionality of ventilator 110. For example, communication 113 facilitates in the changing of configurations and/or ventilator settings of ventilator 110. Accordingly, communication 113 is not simply a request for ventilator information. As such, communication 113 is not required to be a request for ventilator information.
In one embodiment, communication 115 is transmitted to and stored in medical entity 120. Also, communication may be transmitted from ventilator 110 and stored separately from medical entity 120, for example, in a database or server.
In another embodiment, communication 115 is transmitted directly to medical entity 120. For example, communication is streaming data transmitted directly to a hand held device, which is discussed in further detail below. As such, communication 115 is not stored (or not required to be stored) in a database or server. In another embodiment, the hand held device does comprise server communication.
Medical entity 120 is any medical entity that is able to bi-directionally communicate with ventilator 110 (or other medical devices).
In one embodiment, medical entity 120 is a healthcare facility network. In general, a healthcare facility network is a network (or plurality of networks) that facilitates in the management and communication of information regarding medical devices and/or patient care. In regards to a healthcare facility, the bi-directional communication with ventilator 110 is wireless. For example, the wireless bi-directional communication can include 802.11/WiFi for communication with a LAN in the healthcare facility.
In another embodiment, medical entity 120 is wide area network (WAN). In such an embodiment, the bi-directional communication is wireless. For example, medical entity 120 may include a cellular modem to communicate with the WAN, for example, in a home healthcare environment. The WAN can also communicate with a healthcare facility network or a ventilator knowledge portal. It should be appreciated that the WAN can be set up by a third party vendor of ventilators.
In a further embodiment, medical entity is a hosted knowledge portal. As described in detail below, the hosted knowledge portal is a system that collects and aggregates ventilator information and also provides collective knowledge, predictions, trending, reports, etc.
Bi-directional communication (wired or wireless) between ventilator 110 and the hosted knowledge portal can be accomplished via a WAN or LAN. For example, the wireless bi-directional communication can include 802.11/WiFi for communication with a LAN or a cellular modem for communication with a WAN.
In another embodiment, medical entity 120 is a hand held device. For example, the hand held device can be, but is not limited to, a tablet personal computer (PC), a personal digital assistant (PDA), a cell phone, a smart phone, etc. In such an embodiment, the wireless bi-directional communication can be accomplished via Bluetooth or other short range wireless communication protocols. As a result, in one embodiment, direct bi-directional communication can occur between ventilator 110 and the hand held device.
In various embodiments, communication 115, transmitted by ventilator 110, can include streaming ventilator data, a snapshot of ventilator data, etc. Additionally, communication 113, received by ventilator 110, can include remotely accessing/controlling ventilator 110, annotating ventilator data/information during rounds, etc.
In one embodiment, medical entity 120 is a medical device(s). For example, medical entity 120 is one or more of a ventilator, infuser, O2 sensor, patient orientation sensors, etc.
A wireless bi-directional communication between ventilator 110 and the bi-directional communication enabled medical device can include ZigBee or similar 802.15 devices for a wireless personal area network (WPAN). The communication system between the devices can be used for low rate networking.
In one embodiment, network 200 is an ad hoc wireless network of medical devices. For example, ventilator 110, 210 and medical device 220 are able to make daisy chain extensions within the range of a LAN or WAN when one WPAN enabled medical device or ventilator is within range of an access point (wired or wireless). In such an example, ventilator 210 utilizes ZigBee or similar 802.15 wireless protocol to connect to network 200 via an access point (not shown). As depicted, medical device 220, is not able to directly connect to the network because it is not within range of the access point. However, medical device 220 is within range of ventilator 210 and is able to wirelessly connect with ventilator 210. As such, ventilator 110, 210 and medical device 220 are able to make a daisy chain extensions within the range of a LAN or WAN.
Also, network 200 and associated devices are enabled for automated discovery of other enabled devices and auto setup of the WPAN.
At 310 of method 300, a communication is received at the ventilator from a medical entity, wherein the communication is associated with ventilator manipulation. For example, ventilator 110 receives communication 113 from medical entity 120.
In one embodiment, at 311, a wireless communication is received. For example, ventilator 110 receives a wireless communication from medical entity 120.
In another embodiment, at 312, a wireless communication is received directly from the medical entity. For example, ventilator 110 receives a wireless communication directly from (e.g., without requiring any intermediary communication devices) a hand held device, such as, a smart phone.
In a further embodiment, at 313, the ventilator functions are remotely controlled. For example, ventilator functions (e.g., O2 levels, gas supply parameters, ventilator mode, etc.) of ventilator 110 are remotely controlled via medial entity 120.
In another embodiment, at 314, ventilator information is annotated. For example, a clinician annotates ventilator information of ventilator 110 in a rounding report via a tablet PC.
In one embodiment, at 315, instructions to stream ventilator information are received. For example, ventilator 110 receives instructions from medical entity 120 to stream ventilator information (e.g., communication 115) such that a clinician is able to view the ventilator information in real-time via a hand held device.
In another embodiment, at 316, instructions to provide a snapshot of the ventilator information are received. For example, ventilator 110 receives instructions from medical entity 120 to provide a snapshot of ventilator information such that a clinician is able to view the snapshot of the ventilator information at a hand held device.
In a further embodiment, at 317, a communication is received that is not required to be a request for information that is subsequently stored in a database. For example, communication 113 is not required to be a request for information that is subsequently stored in database. In such an example, communication 113 can be a request for information that is directly communicated from medical entity 120.
At 320, ventilator information is transmitted by the ventilator to the medical entity wherein the ventilator information is associated with the ventilator manipulation. For example, transmitter 114 transmits communication 115, wherein communication 115 is associated with information regarding the manipulation of ventilator functionality (e.g., confirmation of changed ventilator settings, etc.).
Ventilator data accessor 415 is for accessing ventilator data 405. Ventilator data 405 can be any information generated by the ventilator or information associated with ventilator functionality with regards to patient care. For example, ventilator data 405 can be, but is not limited to, ventilator mode, oxygen level, flow rates, timing, etc.
Context data accessor 417 is for accessing context data 407. Context data 407 can be any information that is able to provide context to ventilator data to enhance patient care via a ventilator. For example, context data 407 can be, but is not limited to, patient identification (ID), ventilator ID, caregiver ID, bed ID, location, etc.
In one embodiment, patient ID is associated with or issued from an Admit, Discharge, Transfer (ADT) system (not shown). As such, the patient ID allows system 400 to acquire additional patient specific information to be associated with ventilator data 405. The patient specific information can be, but not limited to, age, sex, height, weight, and treatment information associated with the patient, etc. It should be appreciated that treatment information can be, but is not limited to, surgery, acute care, burn recover, etc.
Patient ID can be accessed through patient logon with the ventilator. For example, a patient ID, which may be worn on a wrist of a patient, is scanned and the patient is subsequently logged on to the ventilator. As such, the patient ID is accessed.
Data associator 420 is configured for associating context data 407 and ventilator data 405 such that ventilator data 405 is contextualized. For example, ventilator data 405 is gas supply parameters and ventilator modes and context data 407 is the caregiver ID of the caregiver for the patient associated with the ventilator. Accordingly, data associator 420 associates the gas supply parameters and ventilator modes with the caregiver ID. Thus, the gas supply parameters and ventilator modes are contextualized by being associated with the caregiver ID.
In one embodiment, data associator 420 is further configured for associating a subset or a portion of ventilator data 405 with context data 407. For example, ventilator data 405 is associated with a caregiver ID and/or certain operations performed on the ventilator. In such an example, the caregiver ID may be accessed locally by scanning the caregiver ID (via a scanner coupled to the ventilator) or remotely (e.g., logon/password from the caregiver) such as through remote login or a hand held interface utilized by the caregiver. As a result, ventilator data 405 is associated with the caregiver (e.g., to a caregiver ID), which in turn, allows for forwarding of information to a hand held device or other device location.
In various embodiments, the caregiver ID is ascertained and/or verified for certain actions such as remote login, accessing certain stored/streaming data, changing certain ventilator settings, implementing an automated protocol, etc.
Transmitter 430 is configured to transmit associated data 440 that is generated by data associator 420. In one embodiment, transmitter 430 is configured to transmit associated data 440 to a hand held device of a caregiver.
In various embodiments, associated data 440 (or contextualized data) can be maintained on a ventilator or a server (e.g., a server application).
At 610 of method 600, ventilator data is accessed, wherein the ventilator data is generated by a ventilator. For example, ventilator data 405 is accessed by ventilator data accessor 415, wherein ventilator data 405 is generated by ventilator 510.
At 620, context data is accessed. For example, context data 407 is accessed by context data accessor 417.
In one embodiment, at 622, a patient ID is accessed. For example, a patient wristband is scanned to access a patient ID or any other unique patient information (e.g., age, sex, height, weight, etc.).
In another embodiment, at 624, a ventilator ID is accessed. For example, a ventilator ID of ventilator 510 is accessed for contextualizing ventilator data 405.
In a further embodiment, at 626, a caregiver ID is accessed. For instance, a caregiver ID (or any other unique caregiver information) is accessed to facilitate in contextualizing ventilator data 405. As a result, associated data 440 is able to be transmitted to a hand held device utilized by the caregiver.
In another embodiment, at 628, context data is scanned. For example, a caregiver ID is scanned in order to access the caregiver ID. In another example, context data is scanned via auto ID technology (e.g., bar codes, RFID, fingerprint, etc.).
In one embodiment, at 629, context data is accessed for a subset of ventilator actions. For example, a caregiver ID is accessed/verified for certain ventilator actions, such as remote login, storing/streaming data, change certain ventilator settings, etc.
At 630, associate the ventilator data with the context data such that the ventilator data is contextualized. For instance, data associator 420 associates ventilator data 405 and context data 407 to generate associated data 440, such that ventilator data 405 is contextualized.
In one embodiment, at 632, a subset of the ventilator data is associated with the context data. For example, ventilator data 405 is gas supply parameters and ventilator modes for an entire duration that a patient is associated with the ventilator. Context data 407 is a first caregiver ID of a plurality of caregivers for the patient associated with the ventilator. Accordingly, data associator 420 associates the gas supply parameters and ventilator modes with the first caregiver ID (rather than a second and third caregiver ID for a second and third caregiver for the patient). Thus, a portion or subset of ventilator data 405 is associated with the first caregiver ID.
At 640, the contextualized ventilator data is transmitted to a caregiver, wherein the context data is a caregiver identification of the caregiver. For example, associated data 440 is transmitted to a tablet PC of the caregiver who is responsible for the care of the patient.
Ventilator component module 705 is configured for housing a plurality of ventilator components that are utilized by ventilator 710 to enhance the functionality of ventilator 710. Ventilator component module 705 includes receiver 712, transmitter 714, processor 720, memory 725, display screen 730, scanner 735 and optionally camera 740, microphone 745, patient orientations monitoring device 750, and an accessory interface 755. It should be understood that ventilator component module 705 can include other devices/components that are utilized by ventilator 710 to enhance the functionality of ventilator 710.
Receiver 712 and transmitter 714 are similar to receiver 112 and transmitter 114, respectively, as described above.
Processor 720 can be any processor that is configured for processing data, applications, and the like for ventilator 710.
Memory 725 is for storing ventilator information. For example, memory 725 stores ventilator data 405, context data 407 and/or associated data 440.
Display screen 730 is for displaying ventilator information. For example, display screen 730 displays a ventilator mode, patient ID, clinician ID, etc. In one embodiment, display screen 730 is a touch display screen that allows access to data on other networked ventilators and/or medical devices.
Scanner 735 is any information reader (e.g., bar code reader, RF reader, etc.) that is able to read medical information that is utilized by ventilator 710. For example, scanner 735 is able to scan patient IDs, caregiver IDs, ventilator IDs, etc.
Camera 740 is for providing image capture functionality for ventilator 710. For example, camera 740 may capture images of a patient, caregiver, other medical devices to facilitate in the care or security of a patient associated with ventilator 710.
Microphone 745 is for providing audio capture functionality for ventilator 710. For example, microphone 745 may capture audio data of a patient to facilitate in the care of a patient associated with ventilator 710. Patient orientation monitoring device 750 is for monitoring the orientation of a patient associated with ventilator 710. For example, patient orientation monitoring device 750 monitors whether the patient is on his/her side, back stomach, etc.
Accessory interface 755 (wired or wireless) is configured to interface other components/devices with ventilator 710. For example, accessory interface 755 is a Universal Serial Bus (USB) interface for third party accessories (e.g., a video camera).
It should be understood that ventilator 710 is operable and provides basic ventilator functionality to provide care for a patient, without ventilator component module 705. However, ventilator component module 705 and its respective components enhance the functionality of ventilator 710, as described above.
Ventilator component module 705 is disposed within the housing of ventilator 710 or is integral with the housing of ventilator 710. However, ventilator component module 705 may also be releasably attached to ventilator 710, as depicted in
Ventilator protocol accessor 915 is for accessing ventilator protocol 905. Ventilator protocol 905 can be any protocol facilitating in the control of ventilator functionality. For example, ventilator protocol 905 can pertain to oxygen level, flow rate, timing, etc. In various embodiments, ventilator protocol 905 can be, but is not limited to, a weaning protocol, an acute care protocol, a neonatal O2 protocol, and a lung protection protocol. In one embodiment, a protocol can be described as a decision tree with respect to ventilator control and functionality. In another embodiment, ventilator protocol 905 provides instructions to clinicians on what to do with respect to the ventilator.
Ventilator protocol 905 may be native to a ventilator and thus, provided by a ventilator (e.g., ventilator 710). In other embodiments, ventilator protocol 905 may be pushed/accessed from other systems, such as, but not limited to, a hosted (or deployed) knowledge portal or a hospital healthcare system.
Ventilator protocol implementor 920 is configured for implementing ventilator protocol 905 via a touch screen display of a ventilator (e.g., display screen 730). In other words, ventilator protocol implementor 920 is configured to implement protocol 905 on a ventilator by way of user input 907 at the ventilator. For example, one or more ventilator protocols (e.g., weaning protocol, lung protection protocol, etc.) may be displayed on a touch display screen of a ventilator. A caregiver then selects (via the touch display screen) which ventilator protocol is to be implemented on the ventilator for patient care. Accordingly, based on user input 907, ventilator protocol implementor 920 automatically implements the selected ventilator protocol on the ventilator.
In various embodiments, ventilator protocol 905 is implemented in combination with a medical device, such as an infusion pump.
Also, ventilator protocol 905 can be controlled or implemented (to some extent) based on patient input. For example, a conscious patient may be able to increase/reduce ventilatory support by self-selection within a protocol-defined range.
Ventilator protocol customizer 925 is configured for customizing ventilator protocol 905. Ventilator protocol customizer 925 can customize ventilator protocol 905 based on unique patient information, for example, a patient ID, patient lab results, patient test results, etc. It should be appreciated that the patient information can be accessed from an ADT system.
At 1010 of method 1000, a ventilator protocol is accessed. For instance, ventilator protocol 905 is accessed by ventilator protocol accessor 915.
In one embodiment, at 1011, a weaning protocol is accessed. In another embodiment, at 1012, an acute care protocol is accessed. In a further embodiment, at 1013, a neonatal O2 protocol is accessed. In yet another embodiment, a lung protection protocol is accessed.
In one embodiment, at 1015, the ventilator protocol is accessed, wherein the ventilator protocol is native to the ventilator. For example, ventilator protocol 905 is accessed, wherein ventilator protocol 905 is native to ventilator 710.
In a further embodiment, at 1016, the ventilator protocol is accessed from a medical entity. For example, ventilator protocol 905 is accessed from medical entity 120.
At 1020, the ventilator protocol on the ventilator is automatically implemented via a touch screen display of the ventilator. For example, a caregiver selects a protocol displayed on a display screen. Accordingly, ventilator protocol implementor 920 automatically implements the selected protocol on the ventilator.
At 1030, the ventilator protocol is customized based on patient information. For example, ventilator protocol customizer 925 customizes ventilator protocol based on patient lab results.
Ventilator rules accessor 1115 is configured for accessing ventilator rules 1105 for a ventilator. Ventilator rules 1105 can be any rule that affects the functionality of a ventilator. For example, ventilator rules 1105 can be, but are not limited to, ventilator function control and gas supply parameters, such as, gas flow rates, etc.
In one embodiment, ventilator rules 1105 can be subset of a protocol. For example, if a certain protocol is implemented then particular rules associated with that specific protocol can be utilized.
In another embodiment, ventilator rules 1105 are not associated or part of a protocol. For example, the rule that a warning appears when a battery is dead is not associated with a protocol.
In one embodiment, ventilator rules 1105 are native to a ventilator (e.g., ventilator 710), thus, ventilator rules 1105 are provided by the ventilator.
In another embodiment, ventilator rules 1105 are accessed from a location, other than the ventilator, for example, from a healthcare facility network (for local rules) or from a knowledge portal (for best practice rules).
Ventilator mode determiner 1117 is configured to determine which mode(s) the ventilator is operating in. For example, a ventilator mode can be, but is not limited to, a pediatric ventilation mode. Depending on the determined ventilator mode of operation, a variety of rules can be displayed on a display screen of the ventilator and/or certain features can be disabled to prevent patient harm, which will be described in further detail below.
Ventilator rules implementor 1120 is configured for implementing at least one of the ventilator rules 1105 in response to a determined mode of operation. For example, if the ventilator is in a pediatric ventilation mode, certain rules pertaining to gas supply may be implemented.
In one embodiment, if a certain rule is implemented, then certain ventilator functions may be locked out, for example, certain gas supply parameters may be locked out to prevent patient harm.
Also, if a certain rule is desired to be implemented, then a specific override may be required to in order to implement the desired rule. This would prevent unintentionally interrupting the implementation of the rule. For example, if a ventilator is running in accordance to a first rule, and a second rule is intended to be implemented which conflicts with the first rule, then an override of the second rule may be required.
Ventilator rule customizer 1130 is configured to customize ventilator rules 1105. In one embodiment, ventilator rules 1105 are customized based on patient contextualized data (e.g., age, sex, weight). For example, maximum and minimum fresh gas flow may be customized based on age, sex or weight of a patient. Customization can take place within the ventilator or may be pushed to the ventilator from an outside device/location.
At 1210 of method 1200, ventilator rules are accessed. For example, ventilator rules accessor 1115 accesses a plurality of rules that affect gas flow rates, ventilator function control, etc.
In one embodiment, at 1212, ventilator rules are accessed from a ventilator. For example, ventilator rules 1105 are accessed from ventilator 710. In another embodiment, at 1214, ventilator rules are accessed from a medical entity, such as a ventilator knowledge portal.
At 1220, a mode of operation of the ventilator is determined. For example, ventilator mode determiner 1117 determines that ventilator mode 1107 is a neonatal ventilator mode.
At 1230, in response to the determined mode of operation, at least one of the ventilator rules implemented. For example, ventilator rules implementor 1120 implements a particular max/min flow rate in response to a neonatal ventilation mode.
In one embodiment, at 1232, ventilator functions are disabled to prevent harm to a patient associated with the ventilator. For example, certain gas supply functions are disabled to prevent patient harm, in response to a determined mode of operation.
In another embodiment, at 1234, a predetermined override is required to enable the functions of the ventilator. For example, if a ventilator function is disabled, then a predetermined override is required to enable the disabled functions of the ventilator.
At 1240, the ventilator rules are displayed. For example, ventilator rules 1105 are displayed on a display screen.
At 1250, ventilator rules are customized based on patient data. For example, ventilator rule customizer 1130 customizes ventilator rules 1105 based on patient age, sex, height, etc.
In particular, system 1300 includes ventilator data accessor 1312, transmitter 1314 and applications 1320.
Ventilator data accessor 1312 is for accessing ventilator data from ventilator 710 (or any other ventilators and/or medical devices). For example, data (e.g., logged in ventilator or streamed from ventilator) is remotely accessed.
Transmitter 1314 is for transmitting a communication/data to a ventilator and/or a medical entity, which will be described in further detail below. In one embodiment, transmitter 1314 transmits ADT information to a ventilator.
Applications 1320 are any application that is utilized by system 1300 for ventilation management. For example, applications 1320 (or other systems described herein), can be, but are not limited to, a billing application, an inventory control application, cost avoidance application, remote access application, harm avoidance application, protocol application and a rules customization application. It is understood that applications 1320 are related to the variety of systems described herein. As such, system 1300 includes and/or utilizes a plurality of systems and functions described herein.
In one embodiment, system 1300 includes and utilizes batch data management. For example, batches of data are able to be sent from a ventilator without real-time communication.
In one embodiment, system 1300 utilizes system 400 for contextualizing ventilator data, which is described in detail above. In such an example, data associator 420 associates context data 407 and ventilator data 405 such that ventilator data 405 is contextualized. Additionally, transmitter 1314 transmits the contextualized data to medical entity 120 (e.g., hand held device, ventilator knowledge portal, etc.).
In another embodiment, system 1300 utilizes system 900 for automatically implementing a ventilator protocol, as described in detail above. For example, ventilator protocol implementor 902 implements a protocol on a ventilator by way of user input at the ventilator.
Furthermore, ventilator protocol customizer 925 customizes ventilator a protocol based on unique patient information, for example, a patient ID, patient lab results, patient test results, etc. It should be understood that the protocols are pushed to the ventilator from system 1300, for example, by transmitter 1314.
In a further embodiment, system 1300 utilizes system 1100 for implementing a ventilator rule on a ventilator, as described in detail above. For example, ventilator rules implementor 1120 implements at least one of the ventilator rules 1105 in response to a determined mode of operation. In such an example, if the ventilator is in a pediatric ventilation mode, certain rules pertaining to gas supply may be implemented.
Furthermore, ventilator rules 1105 are customized based on patient contextualized data (e.g., age, sex, weight). For example, maximum and minimum fresh gas flow may be customized based on age, sex or weight of a patient. It should be understood that the rules are pushed to the ventilator from system 1300, for example, by transmitter 1314.
It should be appreciated that rules and protocols an result in the ventilator doing something automatically (e.g., closed loop) or can result in user guidance (e.g., open loop).
At 1410 of method 1400, ventilator data generated by a ventilator is accessed. For example, ventilator data accessor 1312 accesses ventilator data from ventilator 710.
In one embodiment, at 1412, the ventilator data is wirelessly accessed. For example, ventilator data accessor 1312 wirelessly accesses ventilator data from ventilator 710 via 802.11 WiFi.
At 1420, patient information is accessed, wherein the patient information facilitates in contextualization of the ventilator data. For example, context data (e.g., age, sex, height, etc.) is accessed.
In one embodiment, at 1422, the patient information is wirelessly received. For example, context information is wirelessly received from a medical entity (e.g., medical entity 120).
At 1430, protocols and rules are provided for the ventilator. For example, ventilator protocol implementor 902 implements a protocol on a ventilator by way of user input at the ventilator and ventilator rules implementor 1120 implements at least one of the ventilator rules 1105 in response to a determined mode of operation. In one embodiment, the protocols and rules are wirelessly transmitted to the transmitter.
At 1440, accessed ventilator data is provided to a medical entity. For example, transmitter 1314 transmits the ventilator data to a hand held device.
At 1450, the accessed ventilator data is integrated with a patient record. For example, ventilator data is integrated with unique patient information such that the ventilator data is contextualized.
At 1460, the ventilator rules and protocols are customized. For example, ventilator rule customizer 1130 customizes ventilator rules 1105 based on patient lab results, medications prescribed, etc. In one embodiment, at 1462, the customized protocols and rules are provided to the ventilator (e.g., ventilator 710).
In particular, system 1500 includes ventilator data accessor 1512, transmitter 1514 and applications 1520.
Ventilator data accessor 1512 is for accessing ventilator data from ventilators 510 and/or 710 (or any other ventilators and/or medical devices). For example, data (e.g., logged in ventilator or streamed from ventilator) is remotely accessed.
Transmitter 1514 is for transmitting a communication/data to ventilators and/or a medical entity, which will be described in further detail below. In one embodiment, transmitter 1514 transmits ADT information (or other data) to a ventilator. In various embodiments, transmitter 1514 transmits data to a healthcare facility network to facilitate monitoring patient outcomes after they have been discharged. Additionally, data may be transmitted (or received) in a particular Electronic Medication Administration Record (eMAR) format (e.g., level 7 compatible interface).
Applications 1520 are any application that is utilized by system 1500 for ventilation management. For example, applications 1520 (or other systems described herein), can be, but are not limited to, a billing application, an inventory control application, cost avoidance application, remote access application, harm avoidance application, protocol application and a rules customization application. It is understood that applications 1520 are related to the variety of systems described herein. As such, system 1500 includes and/or utilizes a plurality of systems and functions described herein.
In one embodiment, system 1500 utilizes system 400 for contextualizing ventilator data, which is described in detail above. In such an example, data associator 420 associates context data 407 and ventilator data 405 such that ventilator data 405 is contextualized. Additionally, transmitter 1514 transmits the contextualized data to medical entity 120 (e.g., hand held device, ventilator knowledge portal, etc.).
In another embodiment, system 1500 utilizes system 900 for automatically implementing a ventilator protocol, as described in detail above. For example, ventilator protocol implementor 902 implements a protocol on a ventilator by way of user input at the ventilator.
Furthermore, ventilator protocol customizer 925 customizes a ventilator protocol based on unique patient information, for example, a patient ID, patient lab results, patient test results, etc. It should be understood that the protocols are pushed to the ventilator from system 1500, for example, by transmitter 1514.
In a further embodiment, system 1500 utilizes system 1100 for implementing a ventilator rule on a ventilator, as described in detail above. For example, ventilator rules implementor 1120 implements at least one of the ventilator rules 1105 in response to a determined mode of operation. In such an example, if the ventilator is in a pediatric ventilation mode, certain rules pertaining to gas supply may be implemented.
Furthermore, ventilator rules 1105 are customized based on patient contextualized data (e.g., age, sex, weight). For example, maximum and minimum fresh gas flow may be customized based on age, sex or weight of a patient. It should be understood that the rules are pushed to the ventilator from system 1500, for example, by transmitter 1514.
At 1610, ventilator data generated by a plurality of networked ventilators is accessed. For example, ventilator data generated by ventilators 510 and 710 is wirelessly accessed via a WAN.
At 1620, wirelessly access patient information of patients of the networked ventilators is wirelessly accessed, wherein the patient information facilitates in contextualization of the ventilator data. For example, patient information of patients associated with ventilators 510 and 710 is wirelessly accessed, wherein the patient information facilitates in contextualization of the ventilator data, as described above.
At 1630, protocols and rules are wirelessly transmitted to the plurality of networked ventilators. For example, protocols and rules are wirelessly transmitted to ventilator 510 and 710.
At 1640, the accessed ventilator data is transmitted to a medical entity. For example, the ventilator data is transmitted to medical entity 120 (e.g., a hand held device associated with a caregiver).
At 1650, the accessed ventilator data is integrated with a patient record. For example, the accessed ventilator data is associated with unique patient data such that the ventilator data is contextualized.
At 1660, the ventilator rules and protocols are customized. For example, the rules are customized based on a ventilator mode and the protocols are customized based on patient information.
At 1670, the customized protocols and the customized rules are provided to at least one of the plurality of ventilators. For example, the customized rules and protocols are wirelessly transmitted to at least one of the ventilators (e.g., ventilator 710).
In general, system 1700 is configured for analyzing medical device data, such as data associated with a ventilator(s). Moreover, the analysis (e.g., based on clinical data analysis, disease management strategies, etc.) of medical device data provides continuous quality improvement (CQI) analysis and reporting for ventilators, giving a hospital/caregiver ability to make improvements.
System 1700 includes data accessor 1720, data analyzer 1730 and notification generator 1740. Moreover, system 1700 includes ventilators 1750-1770. Although
Data accessor 1720 is configured for accessing data from a plurality of ventilators. For instance, data accessor 1720 accesses data 1705 from ventilators 1750-1770. In various embodiments, data accessor 1720 can access data from a single ventilator or any number of ventilators (e.g., ventilators 110, 510 and/or 710).
Data 1705 can be any information, provided by a ventilator, such as, information that facilitates in assisting a clinician in observing and inputting certain information for patient care. Data 1705 can be, but is not limited to, modes of operation, vent settings, patient vital signs, breath sounds, patient orientation, etc.
Data analyzer 1730 is configured for analyzing an aggregate of data 1705. Data analyzer 1730 includes ventilator operation trend determiner 1735 and ventilator operation predictor 1737.
Ventilator operation trend determiner 1735 is configured for determining an operational trend 1736 for a ventilator(s), such as ventilators 1750-1770, based on data 1705.
Ventilator operation predictor 1737 is configured for predicting a ventilator operation prediction 1738 for ventilator(s), such as ventilators 1750-1770, based on data 1705.
Notification generator 1740 is configured for generating notification 1741 for one or more ventilators.
System 1700 can be connected to a variety of networks, such as but not limited to, healthcare facility networks, wide area networks, etc. Additionally, system 1700 can also be coupled directly to ventilators, such as ventilators 1750-1770. In one embodiment, one or more components of system 1700 are located within a ventilator.
During use of system 1700, ventilators 1750-1770 are in operation with respective patients. During operation of ventilators 1750-1770, ventilators 1750-1770 generate data 1705 which is accessed by data accessor 1720. Data 1705 is the aggregate data from ventilators 1750-1770. However, if only one ventilator is in operation or connected to system 1700, then data 1705 is data only from that single ventilator.
The ventilators are capable of bi-directional communication with system 1700. That is, the ventilators are able to send information to system 1700 and also receive information from system 1700. In various embodiments, the ventilators can include a camera, information scanner, touch screen display, microphone, memory, etc.
It should be appreciated that data 1705 is accessed over any time period. For example, data 1705 can be the aggregate data provided over days or months. In one embodiment, data 1705 can be stored in memory 1725.
Data analyzer 1730 receives data 1705. In general, data analyzer 1730 facilitates in analyzing data 1705 to provide information which may assist a clinician in observing and inputting certain information with respect to a ventilator.
Ventilator operation trend determiner 1735 determines ventilator operation trend 1736 based on data 1705. In general, ventilator operation trend 1736 applies to a general tendency or course of a particular ventilator's operation with a particular patient based on data 1705.
Ventilator operation predictor 1737 determines ventilator operation prediction 1738 based on ventilator operation trend 1736 and/or data 1705. In general, ventilator operation prediction 1738 applies to an operation of a particular ventilator with a particular patient.
Ventilator operation prediction 1738 can be based on specific ventilator modes of operation and/or patient vitals that are compared to aggregated data 1705. Accordingly, this allows a clinician to know that certain outcomes are likely. Thus, the clinician can prepare accordingly, or provide proactive treatment to prevent the outcomes.
In various embodiments, ventilator operation trend 1736 and/or ventilator operation prediction 1738 provides information that assists a clinician in observing and inputting certain information related to, but not limited to: delivery of neonatal oxygen, lung protective strategy, sedation effects or events surrounding sedation, weaning effects, suction effects, and transpulmonary pressure, etc. Also, ventilator operation trend 1736 and/or ventilator operation prediction 1738 can be displayed on a ventilator's screen, hand-held device, or other network device.
Notification generator 1740 generates notification 1741 based on ventilator operation trend 1736 and/or aggregated data 1705. In other words, system 1700 monitors certain modes of operation and/or patient vitals. Accordingly, notification 1741 is generated for notifying a clinician of various levels of modes of operation and/or patient vitals.
Notification 1741 can be customized. For example, notification 1741 can be selected to be a warning tone in response to: negative trend analysis, ventilation being performed which contradicts with an assigned protocol, or violation of a rule, etc. In various embodiments, notification 1741 is sent to a nursing station, supervisor, care giver, pager, etc.
At 1810 of method 1800, data is accessed from a plurality of ventilators in operation. For example, data 1705 is aggregated data from ventilators 1750-1770 and is accessed by data accessor 1720. In one embodiment, at 1815, data 1705 is automatically accessed from ventilators 150-170.
At 1820, an aggregate of the data is analyzed. For example, data analyzer 1730 (or other components) analyzes data 1705.
At 1830, a ventilator operation trend of a ventilator is determined based on the analyzed aggregated data. For example, ventilator operation trend determiner 1735 determines ventilator operation trend 1736 based on analyzed data 1705.
At 1840, a ventilator operation of the ventilator is predicted based on the ventilator operation trend. For example, ventilator operation predictor 1737 predicts ventilator operation prediction 1738 based on ventilator operation trend 1736.
At 1850, a notification of the predicted ventilator operation is predicted based on one or more of the ventilator operation trend and the aggregated data. For example, notification generator 1740 generates notification 1741 of predicted ventilator operation based on ventilator operation trend 1736 and/or data 1705.
At 1860, a proactive treatment is provided to a patient associated with the ventilator based on the ventilator operation trend.
Ventilator report 1941 can be a variety of different reports. In one embodiment, ventilator report 1941 is a protocol compliance (or success analysis) report which compares the success of a ventilator protocol to other similar protocols. In such a report, the report is based on aggregated data of a plurality of ventilators (e.g., ventilators 1750-1770).
In another embodiment, ventilator report 1941 is a rounding report. Typically, a rounding report is for a clinician or caregiver and summarizes key information from a shift. As such, the rounding report allows for streamlined changeover at the end of a shift of one caregiver and the beginning of a shift of another caregiver. The rounding report can be generated as a service.
In various embodiments, ventilator report 1941 can be based on trend analysis or comparison to aggregated ventilator information. For example, a report can compare best practice rules and/or protocols to collected data to determine discrepancies. Accordingly, the discrepancies are a part of the report.
At 2010 of method 2000, data is accessed from a plurality of ventilators in operation. At 2020, an aggregate of the data is analyzed.
At 2030, a ventilator report of a ventilator is generated based on the analyzed aggregated data. For example, ventilator report generator 1940 generates ventilator report 1941 based on data 1705.
In one embodiment, at 2032, the ventilator report based on a ventilator operation trend. For example, ventilator report generator 1940 generates ventilator report 1941 based on ventilator operation trend 1736.
In another embodiment, at 2034, a ventilator protocol analysis report is generated and configured for reporting one or more of compliance and success of a ventilator protocol.
In a further embodiment, at 2036, a rounding report is generated and configured for reporting summarized key information from a shift.
At 2040, the ventilator report is displayed. For example, ventilator report is displayed on a ventilator.
In general, system 2100 receives patient information such as symptoms, medication, age, sex, weight. Accordingly, ventilator protocol suggestor 2140 suggests a protocol based on clinician based provided diagnostic information and a comparison of the patient information to aggregated ventilation outcome information.
Protocol 2141 may be a variety of different protocols, such as, but not limited to, weaning, sedation, neonatal, O2 settings, etc. In one embodiment, protocol 2141 is customizable. In various embodiments, protocol 2141 can be displayed on a display screen of a ventilator and/or forwarded to a hand-held interface or other network device.
At 2210 of method 2200, data is accessed from a plurality of ventilators in operation. At 2220, an aggregate of the data is analyzed.
At 2230, a protocol for a ventilator is suggested based on the analyzed aggregated data. For example, ventilator protocol suggestor 2140 suggests protocol 2141 for a ventilator.
At 2240, a ventilator operation trend is determined based on the analyzed aggregated data.
At 2250, diagnostic information provided by a clinician is received. For example, data accessor 1720 receives data 1705, which includes diagnostic information provided by a clinician.
At 2260, the protocol is displayed. For example, protocol 2141 is displayed on a display of a ventilator.
At 2270, the protocol is customized according to a patient associated with the ventilator. For example, protocol 2141 is customized according to a patient associated with ventilator 1750.
Ventilation harm index generator 2340 generates ventilation harm index 2341 based on the analyzed aggregated data or outcomes from the plurality of ventilators. In various embodiments, ventilator harm index 2341 can be viewed on the hosted or deployed knowledge portal.
Level of harm assignor 2350 is configured for assigning a level of harm 2351 to a ventilator setting. Typically, a ventilator is able to perform a plurality of operations that are adjusted or controlled by ventilator settings. The ventilator settings may include time of ventilation at various levels, level of oxygen, etc.
During use, when a clinician attempts to set or adjust the operation of the ventilator by inputting a ventilator setting, a level of harm 2351 is assigned to the attempted input or change of ventilator setting.
The level of harm 2351 is displayed or presented to the clinician in response to the attempted input or change of ventilator setting. In various embodiments, the level of harm 2351 includes a degradation of low, medium or high level of harm. It should be appreciated that the level of harm may have other degradations.
In one embodiment, there may be a delayed implementation of the ventilator setting (e.g., three seconds) to allow the clinician to cancel the ventilator setting because the level of harm assigned to the setting was high.
In another embodiment, the clinician may be presented with the level of harm and then required to verify the setting. In such an embodiment, the verification may be required for certain levels of harm.
In a further embodiment, for certain harm index levels, only certain personnel may be allowed to initiate the setting/adjustment of the ventilator. This could be assured by some form of clinician ID, logon etc.
At 2410 of method 2400, data is accessed from a plurality of ventilators in operation. At 2420, an aggregate of the data is analyzed.
At 2430, the ventilation harm index is generated based on the analyzed aggregated data. For example, ventilation harm index generator 2340 generates ventilation harm index 2341.
At 2440, a level of harm is assigned to a ventilator setting. For example, a high level of harm is assigned to a certain level of oxygen setting.
At 2450, the level of harm is displayed in response to an input of the ventilator setting. For example, a clinician adjusts the level of oxygen setting and the level of harm is displayed in response to the adjustment.
At 2460, implementation of the ventilator setting is delayed. For example, the level of oxygen is substantially increased, as a result, the implementation of the increased level of oxygen is delayed such that the clinician can correctly adjust the level of oxygen.
At 2470, a verification of the ventilator setting is required in response to input of the ventilator setting. For example, the level of oxygen is substantially increased, as a result, a verification of the ventilator setting is require to ensure that the level of oxygen change is correct.
At 2480, verification of a clinician is required before implementation of the ventilator setting. For example, certain ventilator settings are only allowed by certain verified clinicians.
During use of system 2500, data accessor 1720 accesses data 1705 from a ventilator (e.g., ventilator 1750) during operation. Data 1705 may be any operation data from the ventilator. For example, data 1705 may be associated with any protocol and/or customizable protocol.
Data comparator 2530 compares data 1705 with historical data 1706. Historical data 1706 is any operational data associated with one or more other ventilators. For example, historical data 1706 can be empirical data, rules of thumb, protocols, operational history, etc. In various embodiments, historical data 1706 can also include hospital costs, such as, reimbursement, cost to ventilate a patient, labor expenses, etc.
Ventilator 1750 may be similar to the other ventilators (e.g., ventilator 1760 and 1770). However, ventilator 1750 is distinguished or different than the other ventilators in some way. For example, ventilator 1750 may be an upgraded version of ventilator 1760 and/or 1770.
Data comparator 2530 compares data 1705 with associated historical data from at least one other ventilator. For example, data comparator compares operation data of ventilator 1750 with historical operation data from another ventilator. In such an example, data comparator 2530 compares the results of protocols related to oxygen levels of ventilator 1750 with results of protocols related to oxygen levels of other ventilators.
Accordingly, report generator 2540 generates ventilator avoidance report 2541 based on the comparison of data comparator 2530. The ventilator avoidance report can describe the costs and/or harm that are avoided by utilizing ventilator 1750 rather than ventilators 1760 and/or 1770. The avoidance of costs can describe the amount of money saved, hospitalization days saved, etc. Moreover, because hospital beds may be scarce commodities, the report can help make the case for the use of ventilator 1750 rather than ventilators 1760 and/or 1770.
The ventilator avoidance report can capture or record harms avoided based on a variety of factors, such as, shorter hospitalization, faster weaning (versus a basic ventilator), number of times that ventilator rules prevented danger to a patient and what the likely outcome would have been (e.g., additional hospitalization, longer ventilation, death, etc.). As a result, the report helps make the case for the benefits of ventilator 1750 versus basic ventilators (e.g., ventilators 1760 and/or 1770) by preventing harms (which would also save money). In one embodiment, ventilator avoidance report 2541 describes how much money was saved by getting the patient off of the ventilator sooner versus a basic ventilator.
At 2610 of method 2600, data is accessed from a ventilator in operation. For example, data 1705 is accessed from ventilator 1750 by data accessor 1720.
At 2620, the data from the ventilator in operation is compared with associated historical data of another ventilator. For example, data 1705 (e.g., oxygen level data) of ventilator 1750 is compared with associated historical data 1706 (e.g., oxygen level data) of ventilator 1760.
In one embodiment, at 2622, the data is compared with associated historical data of a plurality of other ventilators. For example, data 1705 (e.g., oxygen level data) of ventilator 1750 is compared with associated historical data 1706 (e.g., oxygen level data) of ventilators 1760 and 1770.
At 2630, a ventilator avoidance report of the ventilator is generated based on the comparison. For example, report generator 2540 generates avoidance report 2541 based on the comparison by data comparator 2530.
In one embodiment, at 2632, a cost avoidance report is generated. In another embodiment, at 2634, a harm avoidance report is generated. In a further embodiment, a ventilator avoidance report is generated in response to a patient being discharged from the hospital or having the ventilation services end.
Typically, ventilator documentation is executed manually by a clinician and/or executed at a computer system that is in another location than the point of care (e.g., immediate location of ventilator and/or patient). Accordingly, the work flow of ventilator documentation is inefficient. Moreover, human error, such as incorrect transcribing, may occur.
Data accessor 2710 is configured to access data 2705. Data 2705 can be any ventilator data associated with a ventilator. For example, data 2705 is streaming (full) ventilator data or a snapshot of ventilator data that can be annotated for the rounds with patient vitals (e.g., breath sounds) and observations (e.g., patient orientation, rescue equipment is near point of care).
Data 2705 can also include any information that facilitates in ventilator documentation. For example, data 2705 can include ventilator parameters, medication treatment (e.g., assess breathing before and after treatment), ventilator changes, weaning, etc.
Data 2705 can be accessed directly from the ventilator or can be accessed from a medical entity such as a healthcare facility network, knowledge portal, etc. In one embodiment, data 2705 includes any data associated with any another medical device that is associated with the ventilator and/or patient.
Data 2705 is displayed on display 2730. For example, data 2705 is pre-populated into a ventilator documentation format.
Correct ventilator data confirmer 2720 is configured for confirming that ventilator data is correct at point of care based on user input. For example, data 2705 is displayed on display 2730 for viewing by a clinician. The data is used to generate ventilation documentation. The clinician reviews and signs off that the ventilation documentation is correct and thereby confirms whether or not that ventilation documentation is correct.
The confirmed correct ventilation documentation at the point of care improves the accuracy of the ventilation documentation. The accuracy is improved because, but not limited to, transcribing is not required, and the ventilation documentation information is prepopulated and the clinician verifies the documentation, if correct, at the point of care.
Transmitter 2750 is configured to transmit correct ventilator data 2752 (e.g., signed off ventilation documentation). In one embodiment, correct ventilator data 2752 is transmitted to a patient medical record, for example, in EMAR formant (e.g., level 7 compatible interface).
Report generator 2740 is configured to generate reports based on correct ventilator data 2752. In one embodiment, report generator 2740 generates a round report based on correct ventilator data 2752.
In one embodiment, system 2700 is disposed or integrated in medical entity 2780. In one embodiment, medical entity 2780 is a ventilator.
In another embodiment, medical entity 2780 is a handheld device (e.g., handheld computer, tablet, PDA, etc.). In such an embodiment, the handheld device can wirelessly communicate with a ventilator over WiFi, short range wireless, WPAN, or cellular network.
System 2700 can also be utilized for caregiver verification for login/access to a ventilator (e.g., ventilator 110, ventilator 710, etc.). The verification may be authorized by a caregiver identifier obtained by a card, barcode, biometric means, etc.
At 2810, ventilator data of a ventilator associated with a patient is accessed. For example, data 2705 that is associated with a ventilator and a patient is accessed by data accessor 2710.
In one embodiment, at 2812, streaming ventilator data of ventilator associated with the patient is accessed. For example, data accessor 2710 accesses or captures streaming (full) ventilator data from the ventilator. In other words, data accessor 2710 captures data 2705 which is in real-time.
In another embodiment, at 2814, the ventilator data is accessed at a handheld device at the point of care. For example, system 2700 is implemented in a handheld device. Therefore, data 2705 is accessed at the handheld device at the point of care.
In a further embodiment, at 2816, in response to associating the handheld device to the ventilator, the ventilator data at the handheld device is automatically accessed. For example, a handheld device (including system 2700) is associated with the ventilator, for example, by scanning a barcode on the ventilator. As a result the handheld device is synced to the ventilator. In response to the association, all available vitals are automatically accessed and coupled to the handheld device.
At 2820, the ventilator data is displayed at a point of care of the patient. For example, a ventilator (including system 2700) displays data 2705 on display 2730.
In one embodiment, at 2832, the ventilator data is displayed at the point of care on a handheld device. For example, a handheld device associated with a clinician displays data 2705 on display 2730.
At 2830, the ventilator data is confirmed to be correct at the point of care to assist in the ventilator documentation. For example, a clinician reviews data 2705 that is utilized to form ventilator documentation. If the displayed data is correct for proper ventilator documentation, then the clinician confirms the propriety of the ventilator documentation by generating user input 2706.
In one embodiment, at 2832, the ventilator data is confirmed to be correct at a hand held device. For example, the clinician confirms the propriety of the ventilator documentation by generating user input 2706 at the handheld device.
At 2840, in response to the confirmation, transmit the correct ventilator data to a patient medical record. For example, transmitter 2750 transmits correct ventilator data 2752 corresponding to a proper and correct ventilator documentation to a patient medical record.
At 2850, the ventilator data is annotated at the point of care. For example, data 2705 displayed on display 2730 is annotated by a clinician. In such an example, the clinician annotates or inputs data about weaning, change of ventilator, etc.
At 2860, a rounding report based on the confirmed correct ventilator data is generated. For example, report generator 2740 generates a rounding report based on correct ventilator data 2752.
Medical system 2900 includes a hospital 2901 and/or home environment 2902.
In one embodiment, hospital 2901 includes ventilator 2910 (e.g., ventilator 110, ventilator 710, etc.) that bi-directionally communicates with medical entities in a network (e.g., WAN). For example, ventilator 2910 bi-directionally communicates with coordination engine 2920, third party application 2930, knowledge portal 2940, handheld device 2912, etc. Ventilator 2910 can wirelessly connect to the network via WAP 2915 or a wireline.
In one embodiment, home environment 2902 includes ventilator 2911 (e.g., ventilator 110, ventilator 710, etc.) that bi-directionally communicates with medical entities. For example, ventilator 2911 bi-directionally communicates with medical entities in the network of hospital 2901 (as described above) via cellular network 2916 and/or with coordination engine 2921.
In one embodiment, system 2900 allows for contextualizing ventilator data (e.g., patient context) for ventilators 2910 and 2911, as described above with respect to
Coordination engine 2920 and 2921 are an interface for third party applications (e.g., third party applications 2930). For example, ventilator 2910 may access ADT information from a third party ADT via coordination engine 2920. It should be appreciated that the coordination engines can be integrated in a single location, such as a server, or can be distributed across various computer devices/systems.
Third party applications 2930 can include, but are not limited to, an ADT application, electronic medical record (EMR) application, clinical documentation application, various clinical or financial applications, etc.
In various embodiments, ventilators 2910 and/or 2911 may bi-directionally communicate with various applications associated with coordination engine 2920 (or coordination engine 2921). For example, ventilator 2910 bi-directionally communicates with healthcare facility management system 2922.
In another embodiment, ventilator 2910 bi-directionally communicates with respiratory documentation system or application (RDA) 2924. It should be appreciated that the RDA can also run on other medical devices such as handheld device 2912.
In various embodiments, the ventilators are capable of ventilator data logging. For example, ventilator 2911 may be offline, however, it is still able to capture and store data. Once the ventilator comes back online the stored data is transmitted to medical entities such as coordination engine 2921.
Data accessor 3020 is configured to access data 3005. Data 3005 can be any data or information associated with a patient who is being treated by a ventilator (e.g., ventilator 110, ventilator 710, etc.). Data 3005, can be, but is not limited to, ventilator data, trending of ventilator data, contextualized patient data from ADT/lab reports, patient vitals, etc.
In various embodiments, data 3005 can be the output of patient orientation monitoring device 3045 and/or microphone 3046.
Patient orientation monitoring device 3045 is for monitoring the orientation of a patient associated with the ventilator. For example, patient orientation monitoring device 3045 monitors whether the patient is on his/her side, back stomach, etc. In one embodiment, patient orientation monitoring device 3045 is for monitoring patient orientation to facilitate in the determining whether or not suction is needed on a patient, which will be described below. For example, suction is needed less often when a patient is oriented on his or her stomach.
Microphone 3046 is for capturing or sensing breathing sounds of the patient (e.g., wheezing) to facilitate in the determining whether or not suction is needed on a patient, which will be described below.
Data analyzer 3030 receives data 3005 and analyzes data 3005 for ventilator suction management. In particular, data analyzer 3030 includes suction determiner 3032 and suction predictor 3034.
Suction determiner 3032 is configured for determining that suction is needed on the patient based on the analyzed data. For example, based on a patient oriented on his or her back, suction determiner 3032 determines that suction is (presently) needed for the patient. In response to the determination, suction is performed on the patient based on data 3005. It should be appreciated that the term “suction,” as used herein, pertains to any ventilator suction event, for example, the suction of saliva or mucous from the airway of a patient, by a ventilator.
Notification generator 3050 is configured for generating a notification for when suction is needed or required. For example, when suction determiner 3032 determines that suction is presently needed, notification generator 3050 generates a notification that the suction is presently needed. This notification assists the caregiver that the suction is needed and/or to be performed. It should be appreciated that the notification can be, but is not limited to, a message on the screen of the ventilator, sound, light, notice at the nursing station, a page to the caregiver/respiratory therapist, etc.
Suction predictor 3034 is configured for predicting a time when suction is needed and/or to be performed on the patient based on the analyzed data. In one embodiment, if suction determiner 3032 determines that suction is not presently needed for a patient, then suction predictor 3034 will predict a time (in the future) when suction will be needed for the patient based on the analyzed data. In various embodiments, predicting when suction will be needed is a mode of operation which may automatically engage or be manually engaged.
As a result of the predicted time of suction, rounds or visits of a caregiver can be scheduled to coincide with the predicted time for suction.
Comparator 3040 is configured for comparing patient ventilation prior to suction to patient ventilation after suction.
Ventilation tracker 3042 is configured for tracking patient ventilation after suction. In particular, once suction is performed on the patient, ventilator tracker 3042 tracks the patient's respiratory health following the suction. Comparator 3040 compares the patient ventilation prior to suction to patient ventilation after suction to facilitate in determining whether or not the suction improved patient ventilation. If the patient ventilation is improved, the tracking/comparing also determines how effective the suction was at improving ventilation. As a result, the caregiver is able to determine if suction was warranted and/or how effective the suction was at improving ventilation.
At 3110, data associated with a patient is accessed, wherein the patient is associated with a ventilator. For example, data 3005 (e.g., breathing sounds, patient orientation, contextualized data, etc.) that is associated with a patient is accessed by data accessor 3020. In particular, the patient is receiving respiratory care from a ventilator (e.g., ventilator 110).
At 3120, the data is analyzed. For example, data 3005 is analyzed by data analyzer 3030.
At 3130, suction is determined to be needed on the patient based on the analyzed data. For example, suction determiner 3032 determines that a patient is in need of suction based on data 3005. It should be appreciated that suction may be actually performed on the patient subsequent the determination that suction is needed.
At 3132, a time is predicted when the suction is needed on the patient based on the analyzed data. For example, suction predictor 3034 predicts a time when suction is needed on the patient based on data 3005, such as contextualized data.
At 3140, rounds of a caregiver are scheduled to coincide with the predicted time when the suction is needed on the patient. For example, suction predictor 3034 predicts that suction is needed for a patient at 12:00 PM. Accordingly, a round of a caregiver is scheduled to coincide with the predicted suction at 12:00 PM.
At 3145, a notification is generated for when the suction is required. For example, suction determiner 3032 determines that a patient is in need of suction at the present time (e.g., 1:00 PM). Accordingly, notification generator 3050 generates a notification (e.g., beep, text) at 1:00 PM to notify a caregiver that suction is needed for the patient.
At 3150, suction is performed in response to the notification. For example, suction is automatically performed on the patient in response to notification generator 3050 generating a notification that suction is needed.
In one embodiment, at 3155, the patient orientation monitored to facilitate in the determining that suction is needed. For example, a patient is determined to be oriented on his back, based on patient orientation monitoring device 3045. Accordingly, suction determiner 3032 determines that suction is needed and/or to be performed.
In another embodiment, at 3160, breathing sounds of the patient are sensed to facilitate in the determining that the suctioning is needed. For example, wheezing sounds of the patient are captured by microphone 3046. Accordingly, suction determiner 3032 determines that suction is needed.
At 3165, patient ventilation prior to the suction is compared to patient ventilation subsequent the suction. For example, comparator 3040 compares patient ventilation prior to suction to patient ventilation subsequent the suction, to facilitate in determining the effectiveness of the suction.
In general, remote device 3220 is able to remotely communicate (e.g., bi-directionally communicate) with ventilator 3210. For example, ventilator 3210, which is in a home environment (e.g., home environment 2902 of
Ventilator 3210 includes receiver 3212, transmitter 3214 and optionally, display 3030, camera 3040 and microphone 3050. Receiver 3212 is for receiving communication from 3205 from remote device 3220.
Communication 3205 can be any information or data that facilitates in managing/controlling ventilator 3210 and/or providing respiratory care to the patient. In one embodiment, communication 3205, received by receiver 3212, is a request to remotely access ventilator data of ventilator 3210, for example, a request from a caregiver.
In one embodiment, communication 3205 is streaming video (which also includes audio) which is displayed on display 3030 (e.g., a touch screen display). Accordingly, the patient is able to view the video and communicate in real-time with the caregiver.
In various embodiments, communication 3205 (or remote caregiver data) can be, but is not limited to, instructions that remotely control ventilator 3210, suggestions/instructions regarding ventilator setting/protocols, etc.
Communication 3225 can be any information or data (e.g., ventilator data) that facilitates in providing respiratory care to the patient. For example, transmitter 3214 transmits ventilator data to remote device 3220, such that a caregiver is able to review the ventilator data.
In one embodiment, communication 3225 is streaming video of a patient captured by camera 3040. The streaming video is displayed at the remote device, such that the caregiver is able to communicate in real-time with the patient.
In another embodiment, communication 3225 is audio of the patient captured by microphone 3050. For example, a caregiver may listen to the breathing sounds which are transmitted to and received by remote device 3220.
The bi-directional communication between remote device 3220 and ventilator 3210, as described above, allows for a variety of remote caregiving features. For example, a remote caregiver can listen to and see the patient and may discuss patient matters with an on-site caregiver, images may be presented to the patient at display 3030 and/or at remote device 3220, the remote caregiver may suggest or instruct ventilator 3210 with ventilator settings and protocols, etc.
As a result, these features allow for remote consultations with respiratory therapists and/or remote diagnosis. Additionally, these features allow for remotely performing rounds/check-ups on patients.
At 3310, a request to remotely access ventilator data is received, at the ventilator, from a remote device. For example, a request for remotely accessing ventilator data is sent from remote device 3220 to ventilator 3210.
In one embodiment, at 3312, a request from a caregiver to remotely access the ventilator data is received. For example, a remote caregiver requests (via remote device 3220) access to the ventilator data which received at receiver 3212.
At 3320, the ventilator data is transmitted to the remote device from the ventilator. For example, communication 3225 is transmitted to remote device 3220. In one embodiment, at 3322, ventilator data is streamed to the remote device. In another embodiment, at 3324, video of the patient is transmitted to the remote device. In a further embodiment, at 3326, audio of the patient is transmitted to the remote device.
At 3330, remote caregiver data is received, at the ventilator, from the remote device, wherein the remote caregiver data is based on the ventilator data. For example, in response to the caregiver receiving communication 3225 (e.g., ventilator data, breathing sounds, etc.), communication 3205 is received at ventilator 3210 based, in part, to communication 3225.
In one embodiment, at 3332, video of the caregiver is received at ventilator 3210. In another embodiment, at 3334, instructions to remote control the ventilator by the caregiver are received at ventilator 3210. In a further embodiment, at 3336, suggestions of ventilator settings, ventilator protocols, and the like are received at ventilator 3210.
At 3340, communication 3225 (e.g., ventilator data) is transmitted to a medical entity, such as, but not limited to, another remote device, medical device, system, etc.
In one embodiment, subsystem 3405 includes patient orientation data accessor 3440 and ventilator operation modifier 3450. It should be appreciated that system 3400 is utilized in conjunction with a ventilator (e.g., ventilator 110, 710, etc.). For example, subsystem 3450 is integrated with or associated with the ventilator.
Patient orientation monitoring device 3420 is configured to monitor and determine the orientation of a patient (e.g., the patient is on his/her back, side, stomach, etc.) that is associated with a ventilator (e.g., ventilator 110, 710, etc.). In particular, patient orientation monitoring device 3420 generates patient orientation data 3425 that is accessed by patient orientation accessor 3440 to facilitate in modifying ventilator operation based on the patient orientation.
In one embodiment, patient orientation monitoring device 3420 is one or more accelerometers that are attached to the patient.
In another embodiment, patient orientation monitoring device 3420 is a passive RFID coupled with one or more accelerometers. For example, the RFID is “pinged” and briefly energized by the ventilator. In response, the RFID responds with patient orientation data 3425.
In various embodiments, patient orientation monitoring device 3420 is attached in any manner, such as an adhesive patch, at a location on the patient that facilitates in properly determining the orientation of the patient. For example, patient orientation monitoring device 3420 is attached to the middle of the chest or on a shoulder and then initialized.
In one embodiment, patient orientation monitoring device 3420 is attached to or integral with a mask that is placed on the patient.
In a further embodiment, patient orientation monitoring device 3420 is a camera (e.g., camera 730) associated with the ventilator that captures images of the patient. For example, the camera captures images of the physical orientation of the patient. In another example, the camera utilizes facial recognition techniques to facilitate in determining the orientation of the patient.
It should be appreciated that patient orientation monitoring device 3420 may be in wired or wireless communication with patient orientation accessor 3440. It should also be appreciated that patient orientation is useful in predicting when suction may be needed, as described above.
Ventilator operation modifier 3450 is configured to modify the operation of the ventilator based on the patient orientation. In one embodiment, ventilator modifier 3450 receives patient orientation data 3425 from patient orientation data accessor 3440 and provides modified ventilator operation instructions 3455 to the ventilator such that the current or normal operation of the ventilator is modified.
For example, if the patient is on his side or stomach, then ventilator operation modifier 3450 provides modified ventilator operation instructions 3455 that instruct the ventilator to increase the amount of fresh gas (provided by some percentage) to the patient.
In another embodiment, modified ventilator operation instructions 3455 instruct the ventilator to modify one or more protocols (e.g., length of the protocol or amount of fresh gas provided during certain portions of the protocol) based on the orientation of the patient.
At 3510, patient orientation of a patient is monitored, wherein the patient is associated with a ventilator. For example, patient orientation monitoring device 3420 monitors the orientation of the patient.
In one embodiment, at 3512, images of the patient are captured. For example, a video camera captures images of the patient orientation.
In another embodiment, at 3514, monitor patient orientation based on accelerometers attached to the patient. For example, an adhesive patch comprising accelerometers is attached to the back of a patient to monitor patient orientation.
In a further embodiment, at 3516, patient orientation is monitored based on accelerometers attached to a mask. For example, accelerometers attached to a mask are utilized to monitor patient orientation.
In another embodiment, at 3518, patient orientation is periodically monitored. For example, in response to periodic “pinging,” an RFID provides patient orientation.
At 3520, ventilator operation of the ventilator is modified based on the patient orientation. For example, the current or normal operation of the ventilator is modified based on patient orientation.
In one embodiment, at 3522, an amount of fresh gas to the patient is increased. For example, based on the patient laying on his back, ventilator operation modifier 3450 provides modified ventilator operation instructions 3455 to the ventilator to increase the amount of fresh gas provided to the patient.
In another embodiment, at 3524, a protocol of the ventilator is modified. For example, based on the patient orientation, the length of the protocol is modified.
In one example, the ventilator utilizing system 3600 is located at a home of a patient. Accordingly, a caregiver may not be able to check the patient ventilation, in person, very often. However, as will be described in detail further below, ventilator data is able to be logged and provided to a medical entity, such as a client device of the caregiver. Moreover, system 3600 may store and/or forward or allow remote access to the ventilator data.
The ventilator data can be any information generated by the ventilator or information associated with ventilator functionality with regards to patient care. For example, the ventilator data can be, but is not limited to, ventilator mode, oxygen level, flow rates, timing, etc. The term “logging,” used herein describes keeping records or compiling of the ventilator data.
System 3600 includes receiver 3610, data logger 3620 and data provider 3630.
Data logger 3620 is configured for logging the ventilator data. For example, as the ventilator generates ventilator data, data logger 3620 logs the data. In one embodiment, the ventilator data is stored in memory 3625.
Receiver 3610 is configured to receive a request for accessing the logged or stored ventilator data. For example, receiver 3610 receives request 3605 for accessing the logged ventilator data for use be a medical entity. In another embodiment, receiver 3610 receives the ventilator data from the ventilator.
Data provider 3630 is configured to provide ventilator data 3640 for use by a medical entity. For example, in response to request 3605, transmitter 3635 transmits ventilator data 3640 to the medical entity, such as a healthcare system and/or a knowledge portal for patient record keeping.
In various embodiments, the ventilator data is stored for a certain or predetermined amount of time. Also, the ventilator data can be stored locally (e.g., at memory 3625) and forwarded continually, in real-time. In other embodiments, the ventilator data can be forwarded in intervals, or forwarded in response to one or more triggers. It should be appreciated that the ventilator data can be overwritten.
The ventilator data can be logged or captured for billing/charge purposes. For example, the ventilator can track time of use in association with a particular patient to confirm that the patient should be billed for ventilator use. Moreover, the particular ventilator protocols that have been utilized in association with the patient can be tracked. Accordingly, the ventilator data (e.g., the charge information) can be forwarded into a healthcare network (or other network) for use in billing or confirmation of charges.
The ventilator data can be logged or captured for inventory control purposes. For example, the ventilator can positively track the use of oxygen or other gasses, use of disposable tubes/masks, and other consumables associated with the ventilator. In particular, the logging of ventilator data for inventory control purposes is for providing the ventilator data to a healthcare facility network for use in inventory control/reorder.
Based on contextualized data, the ventilator can positively track a time of use and associate that time of use with a patient. In one embodiment, this tracking is for compliance with federal and/or insurance company rules and to prevent billing fraud. For example, certain billing codes are associated with certain amounts of time that a patient is ventilated, such as the 96 hour rule.
For instance, once a patient is ventilated for a minimum of 96 hours, a different billing code is utilized. As a result, the patient's bill may be higher. Therefore, positive tracking of ventilator use in association with a particular patient prevents guessing or estimating a time of use and thus prevents a healthcare facility from committing fraud by overestimating the time a patient has been ventilated.
At 3710 of method 3700, ventilator data is logged, wherein the ventilator data is associated with a ventilator. In one embodiment, at 3712, ventilator data is stored at the ventilator. For example, ventilator data 3640 is stored locally in memory 3625 of the ventilator.
In a further embodiment, at 3714, ventilator data the ventilator is periodically logged. In another embodiment, at 3716, the ventilator use data is logged. For example, the length of use of a ventilator on a patient is logged.
In an additional embodiment, at 3718, ventilator protocols are logged. For example, one or more of a weaning protocol, a lung protection protocol, etc. is logged. In one embodiment, at 3719, use of gasses or oxygen is logged.
At 3720, access to the logged ventilator data is provided for use by a medical entity. For example, a remote caregiver requests access to the logged ventilator data and the ventilator is subsequently transmitted to the remote caregiver. In one embodiment, at 3722, wireless access is provided to the logged ventilator data. For example, logged ventilator data is accessed via a cellular connection with the ventilator.
In another embodiment, at 3724, the logged ventilator data is continually transmitted. For example, the ventilator data is continually transmitted in real-time to a remote caregiver.
In one embodiment, the ventilator data is generated by the ventilator. For example, a ventilator (e.g., ventilator 110 or 710) generates the ventilator data that is logged.
System 3800 includes ventilator data accessor 3812, transmitter 3814 and applications 3820.
Ventilator data accessor 3812 is for accessing ventilator data from ventilator 710 (or any other ventilators and/or medical devices). For example, data (e.g., logged in ventilator or streamed from ventilator) is remotely accessed.
Transmitter 3814 is for transmitting a communication/data to a ventilator and/or a medical entity, which will be described in further detail below. In one embodiment, transmitter 3814 transmits ADT information to a ventilator.
Applications 3820 are any application that is utilized by system 3800 for ventilation management. Applications 3820 can include, but are not limited to, billing application 3822 and inventory control application 3824.
Billing application 3822 can utilize ventilator data to generate billing/charges for a patient. For example, billing application 3822 utilizes tracked time, protocols and the like for billing a patient. In one embodiment, the ventilator data is stored at system 3800, for example, in memory.
Inventory management application 3824 can utilize ventilator data to manage/control inventory. For example, system 3800 receives/accesses ventilator data and inventory management application 3824 utilizes the ventilator data for inventory management. In such an example, the use of consumables such as, disposable tubes and/or masks, are tracked and inventory management application 3824 utilizes this data to reorder the consumables.
As such, system 1300 includes and/or utilizes a plurality of systems and functions described herein.
In one embodiment, system 1300 includes and utilizes batch data management. For example, batches of data are able to be sent from a ventilator without real-time communication.
In one embodiment, system 1300 utilizes system 400 for contextualizing ventilator data, which is described in detail above. In such an example, data associator 420 associates context data 407 and ventilator data 405 such that ventilator data 405 is contextualized. Additionally, transmitter 1314 transmits the contextualized data to medical entity 120 (e.g., hand held device, ventilator knowledge portal, etc.).
In another embodiment, system 1300 utilizes system 900 for automatically implementing a ventilator protocol, as described in detail above. For example, ventilator protocol implementor 902 implements a protocol on a ventilator by way of user input at the ventilator.
Furthermore, ventilator protocol customizer 925 customizes ventilator a protocol based on unique patient information, for example, a patient ID, patient lab results, patient test results, etc. It should be understood that the protocols are pushed to the ventilator from system 1300, for example, by transmitter 1314.
In a further embodiment, system 1300 utilizes system 1100 for implementing a ventilator rule on a ventilator, as described in detail above. For example, ventilator rules implementor 1120 implements at least one of the ventilator rules 1105 in response to a determined mode of operation. In such an example, if the ventilator is in a pediatric ventilation mode, certain rules pertaining to gas supply may be implemented.
Furthermore, ventilator rules 1105 are customized based on patient contextualized data (e.g., age, sex, weight). For example, maximum and minimum fresh gas flow may be customized based on age, sex or weight of a patient. It should be understood that the rules are pushed to the ventilator from system 1300, for example, by transmitter 1314.
It should be appreciated that rules and protocols result in the ventilator doing something automatically (e.g., closed loop) or can result in user guidance (e.g., open loop).
At 3910 of method 3900, ventilator data is accessed. For example, ventilator data accessor 3812 accesses ventilator data from ventilator 710. In one embodiment, at 3912, use of medications information is accessed. For example, the information regarding the medication used by a patient is accessed. Also, medications administered through the ventilator may be tracked or recorded. Such information regarding the use of medications may be accessed.
In another embodiment, at 3914, ventilator protocols are accessed. In a further embodiment, at 3916, time of use of the ventilator is accessed.
At 3920, a patient billing record is generated based on the ventilator data. For example, if a patient uses a ventilator for 48 hours, then billing application 3822 generates a billing record for a patient based on 48 hours of use of the ventilator.
In one embodiment, at 3930, ventilator data is stored. For example, system 3800 locally stores the ventilator data.
At 4010 of method 4000, information regarding use of ventilator consumables is accessed. For example, information regarding tubes, masks is accessed. In one embodiment, at 4012, use of ventilator consumables is accessed by a health care facility ventilation management system. For example, health care facility ventilation management system 3800 accesses the use of ventilator consumables.
At 4020, ventilation inventory is managed based on said use of ventilator consumables. In one embodiment, at 4022, ventilator consumables are reordered. For example, if consumables such as masks, tubes, and the like, are low in quantity, then the consumables are reordered, based in part, on inventor management application 3824.
In one embodiment, at 4030, the information regarding the use of ventilator consumables is stored at system 3800, for example, in memory.
Remote device 4120 includes display 4122 and is able to access ventilator data associated with ventilator 4110. Once remote device 4120 receives the ventilator data, the data can be displayed on display 4122. As such, display 4122 associated with the remote device is a virtual ventilator screen of ventilator 4110.
As a result, depending on the device and the login of the user, the virtual ventilator screen allows for remote viewing of ventilator settings and/or remote changing of settings.
At 4210 of method 4200, ventilator data is accessed by a remote device, wherein the ventilator is associated with a patient. For example, remote device 4120 accesses ventilator data from ventilator 4110.
In one embodiment, at 4212, ventilator data is wirelessly accessed. For example, remote device 4120, located in a hospital, wirelessly accesses ventilator data of ventilator 4110 located at the home of the patient. In another embodiment, at 4214, ventilator settings are accessed.
At 4220, the ventilator data is displayed at the remote device. For example, the ventilator settings are displayed at remote device 4120.
At 4230, the ventilator data is displayed at the ventilator. For example, the ventilator data is concurrently displayed on display 4122 and display 4112. In another embodiment, different ventilator data is displayed on the displays.
At 4240, the ventilator settings are manipulated by the remote device. For example, a caregiver views the ventilator settings on display 4122 and changes/manipulates the ventilator settings of ventilator 4110, via remote device 4120.
Various embodiments of the present invention are thus described. It should be appreciated that embodiments, as described herein, can be utilized or implemented alone or in combination with one another. While the present invention has been described in particular embodiments, it should be appreciated that the present invention should not be construed as limited by such embodiments, but rather construed according to the following claims.
This application is related to U.S. patent application Ser. No. 13/287,419, Attorney Docket Number CAFU-IRS120001US1, entitled, “Bi-Directional Ventilator Communication,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,490, Attorney Docket Number CAFU-IRS120021 US1, entitled, “Contextualizing Ventilator Data,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,876, Attorney Docket Number CAFU-IRS120023US1, entitled, “Ventilator Component Module,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,935, Attorney Docket Number CAFU-IRS120025US1, entitled, “Automatic Implementation of a Ventilator Protocol,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,972, Attorney Docket Number CAFU-IRS120027US1, entitled, “Implementing Ventilator Rules on a Ventilator,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,572, Attorney Docket Number CAFU-IRS120041 US1, entitled, “Healthcare Facility Ventilation Management,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,752, Attorney Docket Number CAFU-IRS120047US1, entitled, “Wide Area Ventilation Management,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,993, Attorney Docket Number CAFU-IRS120048US1, entitled, “Analyzing Medical Device Data,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,995, Attorney Docket Number CAFU-IRS120051 US1, entitled, “Ventilator Report Generation,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/288,000, Attorney Docket Number CAFU-IRS120052US1, entitled, “Suggesting Ventilator Protocols,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/288,013, Attorney Docket Number CAFU-IRS120055US1, entitled, “Ventilation Harm Index,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/287,981, Attorney Docket Number CAFU-IRS120039US1, entitled, “Ventilator Avoidance Report,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/288,006, Attorney Docket Number CAFU-IRS120053US1, entitled, “Assisting Ventilator Documentation at a Point of Care,” by Steinhauer et al., with filing date Nov. 2, 2011, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. ______, Attorney Docket Number CAFU-IRS120029US1, entitled, “Ventilator Suction Management,” by Steinhauer et al., with filing date ______, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. ______, Attorney Docket Number CAFU-IRS120033US1, entitled, “Modifying Ventilator Operation Based on Patient Orientation,” by Steinhauer et al., with filing date ______, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. 13/288,006, Attorney Docket Number CAFU-IRS120035US1, entitled, “Logging Ventilator Data,” by Steinhauer et al., with filing date and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. ______, Attorney Docket Number CAFU-IRS120043US1, entitled, “Ventilator Billing and Inventory Management,” by Steinhauer et al., with filing date ______, and assigned to the assignee of the present application. This application is related to U.S. patent application Ser. No. ______, Attorney Docket Number CAFU-IRS120054US1, entitled, “Virtual Ventilation Screen,” by Steinhauer et al., with filing date ______, and assigned to the assignee of the present application.
