Respiratory therapy data management system, device, and method

JP2023548463A5Inactive Publication Date: 2024-11-12VENTEC LIFE SYSTEMS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023526016
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-03-08
Filing Date
2021-11-05
Publication Date
2024-11-12
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

There is a need for a system that can monitor, record, analyze, and report patient treatment data associated with respiratory therapy devices, as healthcare providers cannot be in close physical proximity to patients at all times and in all settings.

Method used

A respiratory therapy data management system that collects, stores, monitors, and analyzes patient treatment data from multiple respiratory therapy devices, generating customizable therapy reports and summaries to facilitate informed treatment decisions and proactive clinical interventions.

Benefits of technology

The system enables remote monitoring and analysis of patient therapy data, improving treatment effectiveness, coordinating care across providers, and optimizing therapy regimens based on real-time and historical data analysis.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

The present technology is directed to respiratory therapy data management systems, devices, and methods. The systems can collect, store, monitor, report, and / or analyze patient treatment data associated with patient use of one or more respiratory therapy devices. The patient treatment data can include therapy data related to the use of multiple respiratory therapies, such as ventilation, oxygen, cough assistance, suction, and nebulization. The patient treatment data may be collected from multiple respiratory devices associated with a particular patient or from a single respiratory device associated with a particular patient. The systems can generate customizable reports detailing the patient treatment data. The reports can summarize patient use, illustrate therapy trends, and / or provide therapy recommendations.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Provisional Application No. 63 / 110,893, entitled "RESPIRATORY THERAPY DATA MANAGEMENT SYSTEMS, DEVICES, AND METHODS," filed November 6, 2020, and U.S. Provisional Application No. 63 / 158,266, entitled "RESPIRATORY THERAPY DATA MANAGEMENT SYSTEMS, DEVICES, AND METHODS," filed March 8, 2021, both of which are incorporated herein by reference in their entireties.

[0002] The present technology generally relates to systems and methods for collecting, storing, monitoring, reporting, and / or analyzing patient treatment data associated with a patient's usage of one or more respiratory therapy devices. [Background technology]

[0003] Respiratory therapies, such as artificial ventilation, supplemental oxygen, and the like, are administered to patients in a variety of settings. For example, patients may receive respiratory therapy in an intensive care unit, emergency room, clinic, long-term care facility, rehabilitation facility, or at home. It is often not practical or even possible for a healthcare provider to be physically proximate to the patient at all times and in every setting to monitor the patient's respiratory therapy. Thus, a need exists for a system that can monitor, record, analyze, and / or report patient treatment data associated with patient usage of respiratory therapy devices. Summary of the Invention [Means for solving the problem]

[0004] Detailed Description The present technology is directed to respiratory therapy data management systems, devices, and methods. The systems described herein can collect, store, monitor, report, and / or analyze patient therapy data associated with patient use of one or more respiratory therapy devices. The patient therapy data can include therapy data related to the use of multiple respiratory therapies, such as ventilation, oxygen, cough assistance, suction, and nebulization. The patient therapy data may be collected from multiple respiratory devices associated with a particular patient or from a single respiratory device associated with a particular patient. The systems can generate customizable therapy reports and / or summaries detailing the patient therapy data. The patient therapy reports can summarize the patient's use of various respiratory therapies, illustrate therapy trends, and / or provide therapy recommendations. Without being bound by theory, the systems described herein can thus facilitate informed treatment decisions, foster proactive clinical intervention, control costs, and help coordinate treatment across multiple healthcare providers.

[0005] In an exemplary embodiment, the present technology provides a method for monitoring a patient's therapy. The method can include collecting patient therapy data associated with multiple respiratory therapies used by the patient. The multiple respiratory therapies can include, for example, ventilation therapy, oxygen therapy, cough-assisted therapy, inhalation therapy, and / or nebulization therapy. The method can further include transmitting the collected patient therapy data to a server including a patient data module that stores data associated with multiple individual patients. The method can further include generating and displaying a patient therapy report summarizing the patient's use of various respiratory therapies, illustrating therapy trends, and / or providing therapy recommendations to improve the patient's quality of life.

[0006] Further aspects and advantages of the present devices, methods and uses will become apparent from the ensuing description, which is given by way of example only. [Brief explanation of the drawings]

[0007] Many aspects of the present technology can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present technology.

[0008] [Figure 1A] 1A and 1B are schematic diagrams of a respiratory therapy data management system configured in accordance with one embodiment of the present technology. [Figure 1B] 1A and 1B are schematic diagrams of a respiratory therapy data management system configured in accordance with one embodiment of the present technology.

[0009] [Figure 2] FIG. 2 is a schematic diagram of a series of features of the respiratory therapy data management system shown in FIGS. 1A and 1B.

[0010] [Figure 3] FIG. 3 illustrates an exemplary trend summary report displaying simulated patient therapy data and generated in accordance with one embodiment of the present technology.

[0011] [Figure 4A] 4A-4C illustrate exemplary therapy usage and settings summary reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 4B] 4A-4C illustrate exemplary therapy usage and settings summary reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 4C] 4A-4C illustrate exemplary therapy usage and settings summary reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology.

[0012] [Figure 5] FIG. 5 displays simulated patient therapy data and illustrates an exemplary alert report generated in accordance with one embodiment of the present technology.

[0013] [Figure 6A] 6A-6E illustrate exemplary monitoring detail reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 6B] 6A-6E illustrate exemplary monitoring detail reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 6C] 6A-6E illustrate exemplary monitoring detail reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 6D] 6A-6E illustrate exemplary monitoring detail reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology. [Figure 6E] 6A-6E illustrate exemplary monitoring detail reports displaying simulated patient therapy data and generated in accordance with a series of embodiments of the present technology.

[0014] [Figure 7] FIG. 7 illustrates an exemplary therapy log report displaying simulated patient therapy data and generated in accordance with one embodiment of the present technology.

[0015] [Figure 8] FIG. 8 is a flowchart of a method 800 for monitoring respiratory therapy administered to a patient, in accordance with an embodiment of the present technology. DETAILED DESCRIPTION OF THE INVENTION

[0016] The terminology used in the description provided below is intended to be interpreted in its broadest reasonable manner, even when used in conjunction with the detailed description of a specific embodiment of the present technology. Certain terms may be further emphasized below; however, any terminology intended to be interpreted in any limited manner will be clearly and specifically defined as such in this detailed description section. In addition, the present technology can include other embodiments within the scope of the examples that are not described in detail with respect to Figures 1A-8.

[0017] Throughout this specification, a reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the technology. Thus, the appearances of the phrase "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, particular features or characteristics may be combined in any suitable manner in one or more embodiments.

[0018] Throughout this specification, references to relative terms such as, for example, "generally," "approximately," and "about" are used herein to mean ±10% of the stated value. The term "substantially" or grammatical variations thereof refers to at least about 50%, e.g., 75%, 85%, 95%, or 98%.

[0019] FIG. 1A is a schematic diagram of a respiratory therapy data management system 10 (“system 10”) configured in accordance with a series of embodiments of the present technology. System 10 includes multiple ventilators 100a-d and a server 150. The ventilators 100a-d can be configured to provide ventilation and / or other respiratory therapies to patients in need thereof. The ventilators 100a-d can be the same model or different models and can be manufactured by the same entity or by different entities. Each ventilator 100a-d can be associated with a specific individual patient. For example, a first ventilator 100a may be associated with a first specific patient, a second ventilator 100b may be associated with a second specific patient, a third ventilator 100c may be associated with a third specific patient, and a fourth ventilator 100d may be associated with a fourth specific patient. In some embodiments, more than one ventilator is associated with a specific patient. For example, first ventilator 100a and second ventilator 100b may both be associated with the same particular patient. Furthermore, although shown as a ventilator for providing mechanical respiratory assistance, system 10 may include other respiratory therapy devices in addition to or in place of ventilators 100a-d. For example, system 10 may include an oxygen concentrator, a cough assist device, a medication infusion pump, or the like.

[0020] Server 150 can be a local server or a remote server and can include one or more computing devices and / or systems. As discussed further herein, server 150 can include one or more processors and memory that stores instructions executable by the one or more processors for performing the methods described herein. In some embodiments, server 150 is implemented as a distributed “cloud” computing system or facility across any suitable combination of hardware and / or virtual computing resources.

[0021] As described in more detail with reference to FIG. 2, ventilators 110a-d are configured to transmit patient treatment data collected and / or generated by ventilators 110a-d to server 150 for collection, storage, reporting, analysis, or the like. The transmitted patient treatment data may include patient data, ventilator data, therapy data, or the like. Patient data may include data associated with a particular patient, such as a patient identifier, age, height, weight, sex, medical history, diagnosis, test results, medical condition, therapy prescription, therapy recommendation, prognosis, or the like, with which a corresponding ventilator is associated. Ventilator data may include data associated with a ventilator, such as manufacturer, make, model, serial number, parts list, feature list, location (e.g., ventilator GPS location), battery status, media bed status, environmental conditions, or the like. Therapy data may include usage data, recorded or measured parameters, alert data, event data, diagnostic data, or the like. Additional details of the patient treatment data transmitted to server 150 are described below with reference to FIG. 2.

[0022] In some embodiments, the ventilators 100a-d include corresponding data transfer elements 130a-d for collecting patient treatment data from the ventilators 100a-d and / or transferring patient treatment data from the ventilators 100a-d to the server 150. As described in more detail with reference to FIG. 2 , the data transfer elements 130a-130d can establish wired or wireless connections with the ventilators 100a-100d and the server 150 and can therefore be used to securely transmit data from the ventilators 100a-100d to the server 150.

[0023] System 10 may further optionally include one or more computing devices 170. Computing device 170 may be used to access server 150 to download, review, and / or analyze data stored on server 150. Computing device 170 may be any suitable user device known in the art, such as a smartphone, mobile device, laptop, desktop, personal computer, tablet, or other such device. As discussed in further detail with reference to FIG. 2 , computing device 170 may include a communications module for communicating with server 150 and a display for displaying data to a user. In some embodiments, computing device 170 may be associated with a healthcare provider treating a patient. In some embodiments, computing device 170 may be associated with a patient receiving respiratory therapy from one of ventilators 100a-d and / or a caregiver for the patient receiving respiratory therapy.

[0024] As one skilled in the art will appreciate, system 10 can include any number of ventilators 100. For example, system 10 can have as few as a single ventilator in some embodiments (e.g., if the server is a local server dedicated to a single patient). In other embodiments, the system may include 10 or more, 50 or more, 100 or more, 500 or more, or 1,000 or more ventilators or other respiratory devices (e.g., if the server is a remote server receiving data from many different patients). Thus, in some embodiments, system 10 can be configured to collect, store, monitor, report, and / or analyze patient treatment data for a plurality of patients (e.g., 10 or more, 50 or more, 100 or more, 500 or more, 1,000 or more, etc.).

[0025] FIG. 1B illustrates additional aspects of system 10. For example, server 150 can be configured to receive multiple therapy data, including ventilation therapy data 102, cough-assist therapy data 104, oxygen therapy data 106, inhalation therapy data 108, and / or nebulized therapy data 110. The therapy data can be associated with a single patient or multiple patients. Additionally, if therapy data is associated with a single patient, the data can be received from the same or different devices (and / or from one or more data transfer elements 130). For example, in some embodiments, therapy data is received from a single respiratory device (e.g., ventilator 200 described with reference to FIG. 2) incorporating each of five therapies. In other embodiments, therapy data is received from multiple individual devices (e.g., ventilation therapy data 102 is received from a ventilator, cough-assist therapy data 104 is received from a cough-assist device, oxygen therapy data 106 is received from an oxygen concentrator, etc.). Additional details of therapy data are described below with reference to FIG. 2. Additionally, and as described in more detail below, server 150 can generate a single, comprehensive patient therapy report that includes some or all of the received therapy data, which can be transmitted to computing device 170 for display to a user.

[0026] FIG. 2 is a schematic diagram of system 10 shown in FIGS. 1A and 1B, illustrating additional features of ventilation device 200 (which may be one of ventilation devices 100a-d or a separate ventilation device also included in system 10), data transfer element 230 (which may be one of data transfer elements 130a-d or a separate data transfer element also included in system 10), server 150, and computing device 170.

[0027] As provided above, ventilator 200 is configured to provide respiratory therapy to a patient in need thereof. Ventilator 200 can include multiple therapy modules for delivering different therapies to the patient. For example, in the illustrated embodiment, ventilator 200 includes a ventilation module 202 for providing respiratory therapy to the patient, a cough assist module 204 for providing cough assistance to the patient, an oxygen module 206 for providing oxygen therapy to the patient, a suction module 208 for providing suction to the patient, and a nebulizer module 210 for delivering a therapeutic agent to the patient. Ventilator 200 can include additional or fewer therapy modules than those illustrated in FIG. 2 . For example, ventilator 200 can include any combination of the five therapy modules illustrated in FIG. 2 and / or additional therapy modules not explicitly described herein.

[0028] Ventilator 200 may further include memory 212. Memory 212 may record and store patient treatment data. For example, memory 212 may store preferred ventilator settings / parameters for the patient, patient usage of various therapy modules, and the like. Ventilator 200 may further include port 214 for receiving or otherwise interfacing with data transfer elements, such as data transfer element 230. As one skilled in the art would understand, the ventilator 200 may have additional features not expressly described herein, such as any of those described in U.S. Patent Nos. 9,956,371, 10,046,132, 10,105,509, 10,245,406, 10,315,002, 10,518,059, 10,758,699, and 10,773,049 (the disclosures of which are incorporated by reference in their entirety herein for all purposes).

[0029] The ventilator 200 can be operably coupled to a data transfer element 230. The data transfer element 230 can be a bridge or other transmitter configured to transmit data from the ventilator 200 to the server 150, as described below. In some embodiments, the data transfer element 230 is removably coupleable to the ventilator 200 (e.g., via port 214). In other embodiments, the data transfer element 230 is integrated into the ventilator 200 itself. In some embodiments, the data transfer element 230 can be wirelessly coupled to the ventilator 200. Nevertheless, the data transfer element 230 can interface persistently or semi-persistently with the ventilator 200 over a period of time to record, store, monitor, and transmit patient treatment data from the ventilator 200 to the server 150. In some embodiments, the data transfer element 230 can include a memory 231 for storing patient treatment data. In such embodiments, the memory 231 may store patient treatment data in addition to, or instead of, the memory 212 of the ventilator 200, which stores patient treatment data.

[0030] In some embodiments, the data transfer element 230 can record, collect, and / or monitor patient treatment data associated with other medical devices in addition to the ventilator 200. For example, the data transfer element 230 can also be connected (e.g., physically or wirelessly, e.g., via Bluetooth) to a blood pressure monitor for measuring patient blood pressure, a blood glucose monitor for measuring patient blood glucose, a heart rate monitor for measuring patient heart rate, an SpO2 monitor (e.g., a pulse oximeter) for measuring oxygen saturation, a carbon dioxide monitor for measuring exhaled carbon dioxide (ECO2), a weighing scale for monitoring patient weight, a drug delivery device (e.g., an infusion pump, an inhaler, etc.) for administering therapeutic medication, an activity monitor for monitoring patient activity, a smart watch, or the like. In some embodiments, the data transfer element 230 can be connected to both the ventilator 200 and one or more additional medical devices simultaneously. Thus, the data transfer element 230 can collect patient treatment data across multiple medical devices associated with the treatment of a particular patient. As explained in more detail below, the collected patient treatment data for these multiple devices can be compiled into a single patient treatment report for ease of viewing. Also explained in more detail below, without being bound by theory, collecting patient data from multiple devices and / or for multiple therapies is expected to improve patient treatment by allowing healthcare providers to perform a more comprehensive review of a patient's therapies and associated symptoms, as opposed to reviewing each therapy type in isolation.

[0031] In some embodiments, the data transfer element 230 can transmit patient treatment data to the server 150 wirelessly. For example, the data transfer element 230 can include a communication module 232 for establishing a wireless connection with the server 150. The communication module 232 can be configured to connect the data transfer element 230 to the server 150 using cellular, WIFI, Bluetooth, RF communication, near field communication, or other suitable wireless communication techniques. In some embodiments, the data transfer element 230 can be physically connected to the server 150 and transfer the patient treatment data thereto. For example, the data transfer element 230 can be a USB drive or other physical device that has memory and can be plugged into the server 150 (or computing device 170) and transfer the patient treatment data thereto. Although described as transmitting data directly to the server 150, in some embodiments, the data transfer element 230 can transmit the data to one or more intermediate devices (e.g., the computing device 170), which can transmit the data to the server 150. In such embodiments, the data transfer element 230 may transmit data to one or more intermediate devices via a physical connection mechanism or via any of the wireless communication networks described above. The data transfer element 230 can be configured to transmit data to the server 150 continuously, periodically (e.g., twice per day, once per day, twice per week, once per week, twice per month, once per month, etc.), and / or on demand (e.g., when the patient or healthcare provider selects an “upload data” option on a controller interface (not shown) on the ventilator 200 and / or computing device 170).

[0032] In some embodiments, server 150 is configured to receive patient treatment data from multiple sources. For example, in embodiments in which server 150 receives and stores patient treatment data from multiple ventilators, some ventilators may transmit patient treatment data directly to server 150 via data transfer element 230, while other ventilators may upload the patient treatment data to a secondary server or cloud platform, and server 150 can then retrieve the uploaded patient treatment data from the secondary server or cloud platform. Enabling server 150 to receive patient treatment data from different sources is expected to enable system 10 to collect and store patient treatment data for many different medical devices, even if the medical devices have their own data collection or communication systems, for example. For example, as described above, system 10 can collect and store data associated with numerous ventilators, even if the ventilators have different manufacturers and / or collect and transmit data in different ways. Without being bound by theory, system 10 can thus provide a central, integrated database of patient treatment data regardless of the manufacturer of the medical device from which the patient treatment data is being collected.

[0033] Patient treatment data collected and stored (transmitted to server 150) by ventilator 200 and / or data transfer element 230 may include patient data, ventilator data, and / or therapy data. Patient data may include a patient identifier (e.g., a unique alphanumeric code that is HIPAA compliant for use with electronic medical records), age, height, weight, sex, diagnosis, test results, medical condition, medical history, or the like. Ventilator data may include manufacturer, make, model, serial number, parts list, feature list, location (e.g., GPS location of the ventilator), battery status, media bed status, environmental conditions, or the like. As described in more detail below, therapy data may include usage data (e.g., usage data associated with various therapy modules), trend data, event data, alert data, medication adherence data, diagnostic data, or the like.

[0034] In some embodiments, therapy data may include ventilation therapy data (e.g., ventilation therapy data 102, FIG. 1B ), which may include usage data associated with the ventilation module 202. For example, usage data may include the hours per day the ventilation module 202 was used by the patient during a series of time periods, the number of days the ventilation module 202 was used by the patient within a series of time periods, and / or other data associated with usage of the ventilation module 202. Ventilation therapy data may also include additional data associated with patient use of the ventilation module 202, including, but not limited to, data (e.g., measured or calculated parameters) associated with expiratory tidal volume (VTE), respiratory rate, minute ventilation, mean airway pressure (MAP), peak inspiratory pressure (PIP), positive end-expiratory pressure (PEEP), positive expiratory airway pressure (EPAP), leak, patient triggers (e.g., percentage of breaths triggered by the patient), inspiratory-expiratory (I:E) ratio, plateau pressure, static compliance, airway clearance, or the like. The ventilation therapy data may also include pressure waveforms, flow waveforms, and / or ventilation waveforms for the patient.

[0035] In some embodiments, the therapy data may further include cough-assist therapy data (e.g., cough-assist therapy data 104, FIG. 1B ), which may include usage data associated with the cough-assist module 204. For example, the usage data may include the number of days the cough-assist module 204 was used by the patient within a set of time periods, the number of cough-assist maneuvers performed using the cough-assist module 204 within a set of time periods, the average number of cough-assist maneuvers per day performed using the cough-assist module 204 within a set of time periods, and / or other data associated with usage of the cough-assist module 204. The cough-assist therapy data may also include additional data associated with patient use of the cough-assist module 204, including, without limitation, data (e.g., measured or calculated parameters) associated with peak cough flow rate, cough volume, forced inspiratory pressure, forced exhaust pressure, forced inspiration time, forced exhaust time, pause time, and / or forced inspiration rise time.

[0036] In some embodiments, the therapy data may further include oxygen therapy data (e.g., oxygen therapy data 106, FIG. 1B ), which may include usage data associated with the oxygen module 206. For example, the usage data may include the hours per day the oxygen module 206 is used by the patient within a series of time periods, the number of days the oxygen module 206 is used by the patient within a series of time periods, and / or other data associated with usage of the oxygen module 206. The oxygen therapy data may also include additional data associated with patient use of the oxygen module 206, including, but not limited to, the oxygen source (e.g., high-pressure oxygen generator, low-pressure oxygen generator, integrated oxygen generator, etc.), the oxygen delivery mode (e.g., FiO2, pulse dose, bleed-in, etc.), the oxygen flow equivalent, the average FiO2 fraction, the low FiO2 fraction, and / or the high FiO2 fraction.

[0037] In some embodiments, the therapy data can further include inhalation therapy data (e.g., inhalation therapy data 108, FIG. 1B ), which can include usage data associated with the inhalation module 208. For example, the usage data can include the number of days the inhalation module 208 was used by the patient within a series of time periods, the number of inhalation sessions performed using the inhalation module 208 within a series of time periods, the average number of inhalation sessions per day performed using the inhalation module 208, the duration of each inhalation session, the minimum number of inhalation sessions performed on a single day within a series of time periods, the maximum number of inhalation sessions performed on a single day within a series of time periods, the maximum number of nebulizer sessions performed on a single day within a series of time periods, and / or other data associated with usage of the inhalation module 208. The inhalation therapy data can also include additional data associated with use of the inhalation module 208, including, without limitation, data associated with vacuum pressure during inhalation sessions.

[0038] In some embodiments, the therapy data can further include nebulization therapy data (e.g., nebulization therapy data 110, FIG. 1B ), which can include usage data associated with the nebulizer module 210. For example, the usage data can include the number of days the nebulizer module 210 was used by the patient within a series of time periods, the number of nebulizer sessions performed using the nebulizer module 210 within a series of time periods, the average number of nebulizer sessions per day performed using the nebulizer module 210 within a series of time periods, the duration of each nebulizer session, the minimum number of nebulizer sessions performed on a single day within a series of time periods, the maximum number of nebulizer sessions performed on a single day within a series of time periods, and / or other data associated with the usage of the nebulizer module 210. The nebulization therapy data can also include additional data associated with the use of the nebulizer module 210, including, but not limited to, the type of therapeutic agent or drug administered, the dose of the therapeutic agent delivered during each nebulizer session, the total dose of the therapeutic agent administered over a given period of time, and / or the average daily dose of the therapeutic agent administered.

[0039] Any of the foregoing parameters may be measured, determined, collected, stored, and / or reported as continuous values ​​(e.g., shown on a line graph), periodic values ​​(e.g., values ​​captured once every second, once every 5 seconds, once every 10 seconds, once every 15 seconds, once every 30 seconds, once every minute, once every 2 minutes, once every 5 minutes, once every 10 minutes, etc.), and / or average values ​​(e.g., hourly averages, daily averages, weekly averages, etc.). As one skilled in the art will appreciate, therapy data may include additional data associated with patient use of ventilator 200 not explicitly described herein. The foregoing parameters are provided by way of example only and are not intended to limit the scope of the present disclosure in any way.

[0040] 2 , server 150 includes a processor 252 and a memory 254. Memory 254 stores one or more software modules for performing one or more steps of the methods described herein. For example, memory 254 may store a data storage module 256, a report generation module 258, and a data analysis module 260. In alternative embodiments, one or more of these modules may be combined with one another or omitted. Thus, while certain operations are described herein with respect to a particular module or modules, this is not intended to be limiting, and such operations may be performed by a different module or modules in alternative embodiments.

[0041] The data storage module 256 can receive and store patient treatment data. For example, the data storage module 256 can receive patient treatment data from the ventilator 200 via the data transfer element 230. The data storage module 256 can also store past patient treatment data associated with a particular patient so that received patient treatment data can be compared to past patient treatment data for the same patient. The data storage module 256 can therefore generate and maintain multiple patient profiles, each corresponding to a particular patient. The patient profiles can be anonymized or otherwise encrypted to comply with HIPAA and privacy requirements.

[0042] The report generation module 258 can generate patient reports or summaries of therapy data received and / or stored within the data storage module 256. For example, the report generation module 258 can prepare a report / summary for a particular patient in response to a user request. The report generation module 258 can therefore interact with the data storage module 256 to identify and retrieve patient treatment data therefrom. The report generation module 258 can then generate a patient therapy report based on the retrieved patient treatment data, and the server 150 can transmit the generated patient therapy report to the computing device 170 for display to the user. Although described as generating a "report," in some embodiments, a user can directly access the data storage module 256 (e.g., via the computing device 170) and directly review, filter, or analyze the data stored therein.

[0043] In some embodiments, a patient therapy report or summary includes therapy data related to multiple respiratory and / or non-respiratory therapies. For example, a patient therapy report can include therapy data related to respiratory therapies, such as ventilation therapy, cough therapy, oxygen therapy, inhalation therapy, and / or nebulization therapy. In addition, a patient therapy report can also include data related to non-respiratory therapies, such as diabetes therapy or the like. A patient therapy report can also include therapy data collected from other medical devices that monitor various physiological parameters of the patient, such as a heart rate monitor, blood pressure monitor, blood glucose monitor, SpO monitor, carbon dioxide monitor, weighing scale, drug delivery device, activity monitor, smart watch, or the like. Thus, a patient therapy report can provide a comprehensive or holistic overview of a patient's treatment, response to treatment, symptoms, and the like. Without being bound by theory, it is expected that providing a comprehensive patient therapy report will enable healthcare providers to better identify patient trends and interactions between various therapy types. As a non-limiting example, if a patient therapy report includes ventilation therapy data, cough therapy data, and suction therapy data, a healthcare provider can review the cough therapy data and suction therapy data to examine the extent to which the patient's use of cough therapy and suction therapy affects the patient's ventilation. As another non-limiting example, if a patient therapy report includes ventilation therapy data (e.g., from a ventilator), blood pressure measurements (e.g., from a blood pressure monitor), and heart rate measurements (e.g., from a heart rate monitor), a healthcare provider can review the ventilation therapy data to examine the extent to which different ventilation therapy modes or operating parameters affect the patient's blood pressure and heart rate. Without being bound by theory, providing an integrated, comprehensive report is therefore expected to improve patient treatment outcomes by enabling healthcare providers to simultaneously review data across multiple therapy modalities, thus "fine-tuning" therapy and optimizing patient outcomes.

[0044] As noted above, the patient therapy data stored on server 150 can include ventilation therapy data, including pressure waveforms, flow waveforms, and / or ventilation waveforms (collectively referred to as "waveform data"). In some embodiments, the generated patient therapy report or summary can include waveform data, thus allowing a healthcare provider to remotely monitor and / or review these waveforms. In some embodiments, server 150 can store historical waveform data for a patient over the previous 30, 60, 90, etc. days, allowing a healthcare provider to review the waveform data for any period within the stored period. In some embodiments, as described in more detail below, system 10 allows a healthcare provider to review the waveform data in substantially real time.

[0045] In some embodiments, the data analysis module 260 can also analyze the patient treatment data stored in the data storage module 256. For example, the data analysis module 260 may analyze the patient treatment data to review the patient's compliance with a prescribed and / or recommended therapy regimen. As a first non-limiting example, the data analysis module 260 can compare whether the number or rate of cough-assisted maneuvers performed over a series of time periods is identical to the prescribed or recommended number of cough-assisted maneuvers to be performed over a given period. If the number or rate of cough-assisted maneuvers performed over a given period is less than the prescribed or recommended amount, the data analysis module 260 can instruct the server 150 to (i) send a reminder to the patient to increase their use of the cough-assisted module 204, (ii) send a notification to the patient's healthcare provider that the patient is not complying with the prescribed or recommended therapy regimen, and / or (iii) include a notification of the patient's non-compliance with the prescribed or recommended therapy regimen on a patient therapy report generated by the report generation module 258. As a second non-limiting example, data analysis module 260 can determine whether a patient has received a prescribed dosage of a therapeutic medication by analyzing therapy data associated with nebulizer module 210. If the received dosage is not within a threshold degree of deviation of the prescribed dosage (e.g., within 5% of the prescribed dose, within 10% of the prescribed dose, etc.), data analysis module 260 can instruct server 150 to (i) send instructions to the patient to modify its use of nebulizer module 210 so that the patient receives the prescribed dosage, (ii) send a notification to the patient's healthcare provider that the patient has not received the prescribed dosage, and / or (iii) include a notification that the patient has not received the prescribed dosage on a patient therapy report generated by report generation module 258.As one skilled in the art will appreciate, the data analysis module 260 can analyze a patient's adherence to any number of prescribed, recommended, or preferred therapy regimens and is not limited by the foregoing examples.

[0046] The data analysis module 260 can also analyze patient treatment data to derive patient trends, diagnose patient conditions / events, provide therapy recommendations, predict disease progression, or the like. For example, the data analysis module 260 can analyze usage data over an extended period of time (e.g., 3 months, 6 months, 9 months, 1 year, 2 years, 3 years, 5 years, 10 years, or more) to assess patient dependency on various therapy functions and / or disease progression. In some embodiments, an increase in patient dependency on a set of ventilator functions (e.g., time spent relying on the ventilation module 202 to provide breaths, reliance on the oxygen module 204 to provide additional oxygen, etc.) may indicate disease progression and / or a declining patient condition. Similarly, a change in one or more parameters associated with patient usage of ventilator functions (e.g., rate of patient-triggered breaths) may also indicate disease progression and / or a declining patient condition.

[0047] The data analysis module 260 may also compare therapy data for a particular patient with aggregated therapy data for multiple other patients who share one or more common characteristics with the patient (e.g., age, sex, weight, height, diagnosis, age at diagnosis, medical condition, disease state, test results, activity level, etc.). Based on the comparison, the data analysis module 260 may provide one or more therapy recommendations to slow disease progression, reduce patient symptoms, reduce or eliminate side effects, improve the patient's quality of life, or the like. The data analysis module 260 may also provide an estimate of disease progression based on the comparison.

[0048] The data analysis module 260 may rely on one or more artificial intelligence (AI) techniques to analyze patient treatment data and provide recommendations. Suitable AI techniques include, but are not limited to, case-based reasoning, rule-based systems, artificial neural networks, decision trees, support vector machines, regression analysis, Bayesian networks (e.g., naive Bayes classifiers), genetic algorithms, cellular automata, fuzzy logic systems, multi-agent systems, swarm intelligence, data mining, machine learning (e.g., supervised learning, unsupervised learning, reinforcement learning), and hybrid systems. In some embodiments, for example, the data analysis module 260 includes a trained machine learning module that analyzes patient treatment data for a particular patient and provides one or more recommended adjustments to the patient's therapy regime to slow disease progression, reduce patient symptoms, reduce or eliminate side effects, improve the patient's quality of life, or the like. The machine learning module can be trained based on previously received patient treatment datasets, including, for example, scored outcomes corresponding to the patient's symptoms, side effects, quality of life, disease progression, etc.

[0049] As provided above, system 10 may further include computing device 170. Computing device 170 may include input device 272, a communications module 274, and a display 276. Input device 272 may be any suitable input device, such as a mouse, keyboard, touchscreen, touchpad, microphone, or other user input device. Communications module 274 may be configured to establish a wireless connection with server 150 using any suitable wireless communication technique (e.g., Wi-Fi, Bluetooth, cellular, etc.). Display 276 may be configured to display various types of output, such as patient therapy reports generated by report generation module 258 and described in detail below. In some embodiments, display 276 includes the input device as part of display 276, such as when the input device includes a touchscreen. In other embodiments, display 276 is separate from the input device. Examples of suitable display 276 include, but are not limited to, an LCD display screen, an LED display screen, or the like.

[0050] In operation, a user (e.g., a healthcare provider, a patient, a patient's caregiver, or other user) can request a patient therapy report for a particular patient via input device 272 on computing device 270. For example, the user may access a website, intranet, mobile phone application, or other application via computing device 270 and enter patient identification information (e.g., the patient's unique alphanumeric identifier, the patient's name, the patient's unique login information, etc.). In some embodiments, the user can customize the report. For example, the user can specify the time period for which they want to review patient treatment data, the medical devices for which they want to review data (if more than one, e.g., ventilators, cough assist devices, heart rate monitors, infusion pumps, etc.), the patient data the user wants to include in the report (e.g., usage data, specific events of interest, etc.), and / or the type of report to be generated (e.g., interactive, digital, printed, etc.). In embodiments in which the patient also receives non-respiratory therapies (e.g., treatment for diabetes, etc.), the user can select to include data associated with the non-respiratory therapies (e.g., diabetes treatment data, etc.) so that the report is a single, comprehensive report of the patient's health. Thus, in some embodiments, the patient therapy report is customized and / or customizable according to the user's preferences. In some embodiments, the patient therapy report may take different forms depending on whether the patient therapy report is requested by the patient or a healthcare provider. Computing device 170 then communicates the user's request to server 150 via communication module 274. In response to receiving the user request, report generation module 258 identifies and retrieves the requested patient therapy data from data storage module 256 and generates the patient therapy report according to the user's preferences. Server 150 transmits the patient therapy report to computing device 170, where it can be presented to the user via display 276 (e.g., shown diagrammatically as patient therapy report 259 in FIG. 2 ).

[0051] In some embodiments, patient therapy reports generated by the report generation module 258 and displayed by the computing device 170 can be interactive. For example, a user can select or deselect certain parameters or values, select a specific date range for display, toggle between different pages showing different parameters, adjust the graphical display of patient therapy data (e.g., adjust the scale, graph type, etc.), select or mark specific events, add notes (e.g., annotations, reminders, suggestions, etc.) to the report, or the like. In some embodiments, selecting a specific event (e.g., an event marked by the patient) causes the report to display relevant therapy data associated with the event (e.g., ventilation therapy data such as pressure, flow, and ventilation waveforms) during, before, and / or after the event. In some embodiments, patients can add comments or questions to the report or otherwise mark specific portions of the report that they want to discuss with their healthcare provider. For example, patients may add comments or otherwise mark events or periods in which they felt worse than usual. The report can then be transmitted to the patient's healthcare provider, who may review the corresponding patient treatment data as well as any comments, questions, and other markings on the report. Similarly, the healthcare provider can also add comments or notes to the report before sending it to the patient, the patient's caregiver, or another physician. Additional details of exemplary patient therapy reports are described below with respect to Figures 3-7.

[0052] In some embodiments, system 10 can be used to remotely monitor a patient in substantially real time, in addition to or instead of reviewing historical patient treatment data. For example, system 10 can enable a healthcare provider to monitor a patient receiving respiratory therapy in a non-clinical setting (e.g., at home) without the need for physical proximity to the patient. For example, data transfer element 230 can transmit patient treatment data to server 150 in substantially real time (e.g., with a delay of about 10 seconds or less, about 30 seconds or less, about 60 seconds or less, etc.), and server 150 can generate a patient therapy report using the received patient treatment data. Server 150 can transmit the patient therapy report to computing device 270 for review by the healthcare provider and / or provide an alert to computing device 270 as needed (e.g., in response to detecting non-compliance with a prescribed therapy). In some embodiments, data transfer element 230 may transmit patient respiratory data directly to computing device 270 when operating in a “live monitoring” mode. Nevertheless, the delay between the ventilator 200 measuring the data and the computing device 270 displaying the data can be less than about 30 seconds, less than about 60 seconds, and / or less than about 120 seconds. Thus, in some embodiments, the system 10 is adapted to "live stream" patient treatment data to a healthcare provider in a remote setting.

[0053] In some embodiments, “live streaming” of patient treatment data can occur on an as-needed basis. For example, rather than continuously streaming patient treatment data to server 150, a healthcare provider tasked with remotely monitoring a patient can use computing device 170 to request real-time data regarding a particular patient. In response to the healthcare provider's request, server 150 can pull real-time data associated with the particular patient from data transfer element 230 and display the real-time data without substantial delay (e.g., a delay of about 10 seconds or less, about 30 seconds or less, about 60 seconds or less, etc.). This can be useful, for example, when a patient or caregiver contacts a healthcare provider to discuss their current therapy, and the healthcare provider can have immediate access to current patient treatment data and advise the patient regarding an appropriate course of action. Any of the patient treatment data described herein, including ventilator waveform data (e.g., pressure waveform, flow waveform, ventilation waveform), can be collected and reported in substantially real time to facilitate remote patient monitoring.

[0054] System 10 can also be integrated with existing hospital communication / monitoring systems to provide enhanced monitoring of patient status and recording of patient treatment in a hospital or other clinical setting. For example, system 10 can stream patient treatment data in substantially real time to monitors in nurses' stations, provide remote alerts, automatically feed patient treatment data electronically into a hospital's electronic medical record system, or the like.

[0055] In some embodiments, system 10 can thus be used to monitor and / or perform analysis on multiple patients. A healthcare provider, ventilator manufacturer, durable medical equipment (DME) company, or other user with authorized access may be able to access, review, and / or analyze patient treatments stored on data system 10 for multiple patients. In some embodiments, for example, a user may filter patients based on various patient or therapy factors, such as to identify patients who meet one or more predetermined criteria selected by the user. Based on the selected criteria, server 150 may filter, rank, or otherwise list the patients and display the list of filtered patients to the user, such as via computing device 170. Depending on the user (e.g., if the user is a ventilator manufacturer rather than a healthcare provider), patient therapy data may be filtered using HIPAA-compliant identifiers to maintain patient privacy. Exemplary criteria that may be selected by a user may include, for example, non-adherence to prescribed therapy, detected leaks above a predetermined threshold, oxygen consumption, number of alerts, etc.

[0056] In some embodiments, system 10 can be used to monitor and / or perform analysis on multiple ventilators. For example, an entity associated with a ventilator (e.g., a ventilator manufacturer, a DME company, etc.) may want to access patient therapy data stored on server 150 and analyze its ventilator utilization, adherence to prescribed or recommended therapy regimens, effectiveness of courses of therapy, accessory alerts, service alerts, location of their ventilators, or the like. As explained above, the patient therapy data may be anonymized to comply with privacy and HIPAA requirements while still allowing the manufacturer to review the patient therapy data and derive useful trends regarding ventilator usage and status.

[0057] 3 illustrates an exemplary trend summary 300 that may be included as part of a patient therapy report (e.g., patient therapy report 259, FIG. 2) generated by report generation module 258. Trend summary 300 may include a summary of therapy data for a particular patient, such as the patient's usage of a series of respiratory therapies (e.g., ventilation V, cough-assisted C, oxygen O, inhaled S, nebulized N, etc.) and other associated respiratory parameters over a series of time periods. Trend summary 300 may also include a summary of non-respiratory therapies used by the patient (not shown in FIG. 3). Trend summary 300 may also include a medication adherence calendar illustrating usage of various therapies by date.

[0058] 4A-4C illustrate an exemplary therapy use and settings summary 400 that may be included as part of a patient therapy report (e.g., patient therapy report 259, FIG. 2) generated by report generation module 258. The therapy use and settings summary 400 may display the use of various respiratory therapies (e.g., ventilation, cough assistance, oxygen, suction, nebulization, etc.) over a series of time periods and parameters associated with that use. The therapy use and settings summary may also display the use of non-respiratory therapies used by the patient and parameters associated therewith (not shown in FIGS. 4A-4C). In some embodiments, therapy use and settings summary 400 includes data that is the same as or similar to trend summary 300. In some embodiments, therapy use and settings summary 400 is expanded depending on the data provided in trend summary 300.

[0059] FIG. 5 illustrates an exemplary alert summary 500a. The alert summary 500a and alert log 500b can be included as part of a patient therapy report (e.g., patient therapy report 259, FIG. 2) generated by the report generation module 258. As illustrated in FIG. 5, the alert summary 500a can provide a summary of the frequency and type of alerts or warnings generated by a corresponding ventilator or other respiratory or medical device over a series of time periods. The alerts / alerts can include any warnings or alerts provided by the ventilator or respiratory device. For example, the alerts can include a high pressure warning, a low inspiratory pressure warning, a patient circuit disconnect warning, a low minute ventilation warning, a low battery warning, etc. The alert summary may also provide an alert log (not shown) that provides a list of each individual warning generated over a given period of time, the timing of the warning, and the duration of the warning.

[0060] 6A-6E illustrate example monitor details 600 that may also be included as part of a patient therapy report (e.g., patient therapy report 259, FIG. 2) generated by report generation module 258. Monitor details 600 may illustrate a set of patient and / or ventilator parameters associated with various respiratory therapies. For example, FIGS. 6A-6C illustrate a set of parameters associated with ventilation therapy V (e.g., respiratory support provided by ventilation module 202 (FIG. 2) of ventilator 200), FIG. 6D illustrates a set of parameters associated with oxygen therapy O (e.g., oxygen provided by oxygen module 206 of ventilator 200), and FIG. 6E illustrates a set of parameters associated with cough assist therapy C (e.g., cough assist provided by cough assist module 204).

[0061] 7 illustrates an exemplary therapy log 700 that may also be included as part of a patient therapy report (e.g., patient therapy report 259, FIG. 2) generated by report generation module 258. The therapy log 700 may provide a list of each use of various respiratory therapies, illustrating the start time / date, end time / date, and duration for each use of each respiratory therapy. In some embodiments, the therapy log 700 may integrate other non-respiratory therapies into the same therapy log as the respiratory therapy log, so that a patient's use of both respiratory and non-respiratory therapies may be viewed as part of a single log.

[0062] As those skilled in the art will understand from the disclosure herein, Figures 3-7 are provided by way of example only. As previously explained, the systems described herein are capable of generating patient treatment reports having a variety of forms, data, representations, modes (e.g., digital, printed, interactive, etc.), and the like. Indeed, an expected benefit of the present technology is the ability to provide customizable patient treatment reports that provide comprehensive patient treatment data across multiple therapy modalities. Thus, the present technology is not limited by the examples provided herein and includes other patient treatment reports generated in accordance with the description herein.

[0063] FIG. 8 is a flowchart of a method 800 for monitoring respiratory therapies administered to a patient, in accordance with embodiments of the present technology. Method 800 can begin at step 802 by collecting patient treatment data associated with multiple respiratory therapies. The respiratory therapies can include, but are not limited to, ventilation therapy, oxygen therapy, cough-assisted therapy, inhalation therapy, nebulization therapy, and any combination thereof. The patient treatment data can include any of the patient treatment data described previously herein. In some embodiments, collecting the patient treatment data can include receiving the patient treatment data at a data transfer element (e.g., data transfer element 230). In some embodiments, collecting the patient treatment data can include collecting patient treatment data from a single respiratory device configured to deliver multiple respiratory therapies. In other embodiments, collecting the patient treatment data can include collecting patient treatment data from multiple respiratory devices configured to deliver multiple respiratory therapies. In some embodiments, collecting the patient treatment data can include collecting patient treatment data from multiple patient monitors (e.g., pulse oximeters, blood pressure monitors, etc.) in addition to collecting patient treatment data from the respiratory devices.

[0064] Method 800 may proceed at step 804 by transmitting the collected patient treatment data to a server (e.g., server 150). The patient treatment data may be transmitted via a wired or wireless connection, as described above. In some embodiments, the patient treatment data is transmitted via a data transfer element (e.g., data transfer element 230). The patient treatment data may be transmitted automatically, periodically (e.g., daily, weekly, once every two weeks, once every month, etc.), continuously, and / or on demand and in response to a user request for patient treatment data.

[0065] Method 800 may proceed at step 806 by generating a patient therapy report that includes at least a portion of the patient therapy data collected at step 802. For example, report generation module 258 of server 250 may generate the patient therapy report. In some embodiments, step 806 is performed in response to receiving a user request to generate the patient report. In some embodiments, the generated user report is customized according to user preferences (e.g., as specified in the user request), as described above.

[0066] The method 800 may proceed by displaying the patient therapy report in step 808. For example, the patient therapy report may be displayed on a digital display (e.g., display 276 on computing device 170) so that a healthcare provider or other user may review the contents of the report. In some embodiments, the patient therapy report is interactive, allowing the healthcare provider or other user to manipulate aspects of the report (e.g., view, scale, graph type, etc.) by interacting with the digital display.

[0067] The systems and methods described herein can be used to collect, store, monitor, report, and / or analyze patient care data for patients with various conditions. For example, the systems and methods can be used in conjunction with respiratory therapy provided to treat conditions such as neuromuscular diseases (e.g., muscular dystrophy, amyotrophic lateral sclerosis, etc.), pulmonary dysfunction (e.g., caused by COPD, cystic fibrosis, lung cancer, emphysema, viral infections, or other respiratory diseases), spinal cord injuries, and childhood developmental complications (e.g., premature birth, chronic lung disease, etc.).

[0068] As described herein, one expected advantage of the present technology is the ability to collect patient treatment data, including both respiratory and non-respiratory therapy data, from multiple different devices / sources and to provide a single, comprehensive, customizable report for a particular patient. Another expected advantage is the ability for both healthcare providers and patients or their caregivers to access and review patient treatment data and / or annotate or add comments to summaries of patient treatment data. Of course, embodiments of the present technology may provide other advantages described throughout this detailed description and other advantages not expressly disclosed herein. Thus, without being bound by theory, the present technology is expected to improve patient treatment by, for example, enabling a patient's healthcare provider to review a comprehensive profile of a patient's therapy and provide recommended therapy adjustments, alert physicians to patient non-compliance, improve patient-physician communication, improve real-time and / or remote monitoring of patients, and the like.

[0069] The systems and methods described herein can be implemented with and / or distributed across computing architectures. For example, many of the systems described herein include memory, which stores data, software modules, instructions, or the like. The memory described herein can include one or more of various hardware devices for volatile and non-volatile storage, and can include both read-only and writable memory. For example, memory can include random access memory (RAM), various caches, CPU registers, read-only memory (ROM), and writable non-volatile memory such as flash memory, hard drives, floppy disks, CDs, DVDs, magnetic storage devices, tape drives, device buffers, etc. Memory is not a propagating signal separate from the underlying hardware; memory is therefore non-transitory. In some embodiments, memory is a non-transitory computer-readable storage medium, e.g., storing programs, software, data, or the like.

[0070] As those skilled in the art will understand from the disclosure herein, various components of the systems described above can be omitted without departing from the scope of the present technology. Similarly, additional components not explicitly described above can be added to the system without departing from the scope of the present technology. For example, while specific examples of the present technology have been described herein for illustrative purposes, it should be understood that well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the present technology. Also, while specific embodiments of the present technology and examples thereof have been described above for illustrative purposes, various equivalent modifications are possible within the scope of the present technology, as those skilled in the art will recognize. For example, while steps are presented in a given order, alternative embodiments may perform steps in a different order. The various embodiments described herein can also be combined to provide further embodiments. Thus, the present technology is not limited to the configurations explicitly identified herein, but rather encompasses variations and modifications of the described systems and methods.

[0071] Furthermore, although advantages associated with some embodiments of the present technology have been described in the context of those embodiments, other embodiments may also exhibit such advantages, and not all embodiments necessarily exhibit such advantages to fall within the scope of the present technology. Thus, the present disclosure and associated technology may encompass other embodiments not explicitly shown and described herein.

[0072] Unless the context clearly requires otherwise, throughout the description and examples, the terms "comprise," "comprising," and the like, should be interpreted in an inclusive sense, i.e., "including, but not limited to," as opposed to an exclusive or inclusive sense. As used herein, the terms "connected," "coupled," or any variant thereof, mean any connection or coupling, either direct or indirect, between two or more elements, and the coupling of connections between elements can be physical, logical, or a combination thereof. In addition, the terms "herein," "above," "below," and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, terms in the above detailed embodiments using singular or plural numbers may also include plural numbers or singular numbers, respectively. As used herein, the phrase "and / or," such as in "A and / or B," refers to A only, B only, or both A and B. Furthermore, where specific integers that have known equivalents in the art to which the embodiments pertain are set forth herein, such known equivalents are deemed to be incorporated herein as if individually set forth.

Claims

1. 1. A computer-implemented method for monitoring a treatment of a particular patient, the method comprising: collecting patient treatment data associated with a plurality of respiratory therapies used by the particular patient, the plurality of respiratory therapies including at least two of ventilation therapy, oxygen therapy, cough assisted therapy, inhalation therapy, and nebulization therapy; transmitting the collected patient treatment data to a server, the server including a patient data module that stores data associated with a plurality of individual patients; A method comprising:

2. the plurality of medical devices at least one respiratory device configured to provide the plurality of respiratory therapies; At least one additional medical device, the at least one additional medical device being a blood pressure monitor, a blood glucose monitor, a heart rate monitor, an SpO 2 at least one additional medical device, including a monitor, a weight monitor, a carbon dioxide monitor, and / or a drug delivery device; Including, 2. The method of claim 1, wherein the patient treatment data includes (i) first patient treatment data associated with the plurality of respiratory therapies and the at least one respiratory device, and (ii) second patient treatment data associated with the at least one additional medical device.

3. 2. The method of claim 1, wherein collecting patient treatment data associated with the multiple respiratory therapies comprises collecting the patient treatment data from a single respiratory device configured to deliver the multiple respiratory therapies to the particular patient.

4. 2. The method of claim 1, wherein collecting patient treatment data associated with the multiple respiratory therapies comprises collecting the patient treatment data from at least two respiratory devices configured to deliver the multiple respiratory therapies to the particular patient.

5. The method of any of claims 1 to 4, wherein collecting patient treatment data includes collecting ventilation therapy data including at least one of a pressure waveform, a flow waveform, or a ventilation waveform.

6. The method of any one of claims 1 to 5, wherein transmitting the collected patient treatment data to the server comprises automatically and periodically transmitting the collected patient treatment data to the server.

7. A method according to any one of claims 1 to 6, further comprising generating a bidirectional patient therapy report, the bidirectional patient therapy report including a graphical display of at least a portion of the patient treatment data transmitted to the server, and the bidirectional patient therapy report being customized based on user preferences.

8. receiving from a user one or more annotations or markings to be added to the report; in response to receiving the one or more annotations or markings, adding the one or more annotations or markings to the report; The method of claim 7 further comprising:

9. 9. The method of claim 1, further comprising: analyzing the collected patient data; and providing, based on the analysis, one or more recommendations associated with at least one of the plurality of therapies.

10. 10. The method of claim 9, wherein analyzing the collected patient data comprises using a trained machine learning model to identify the one or more recommendations associated with at least one of the plurality of therapies.

11. The patient treatment data is first patient treatment data, and the method includes: collecting second patient treatment data associated with a plurality of non-respiratory therapies used by the particular patient; transmitting the collected second patient treatment data to the server; generating a patient report including at least the first subset of patient treatment data and the second subset of patient treatment data; The method of any one of claims 1 to 10, further comprising:

12. 1. A computer-implemented method for generating a patient therapy report displaying patient therapy data associated with a particular patient, the method comprising: receiving a request to generate the patient therapy report, the request including a patient identifier associated with the particular patient; in response to receiving the request, using the patient identifier to identify patient treatment data associated with the particular patient, the patient treatment data associated with the particular patient being stored on a server that stores patient treatment data associated with a plurality of individual patients including the particular patient, the patient treatment data associated with the particular patient including therapy data associated with a plurality of respiratory therapies used by the particular patient; generating a patient therapy report, the patient therapy report including a graphical representation of at least a portion of the patient treatment data associated with the particular patient; transmitting the patient therapy report to a device configured to display the patient therapy report; A method comprising:

13. 13. The method of claim 12, wherein the plurality of respiratory therapies includes ventilation therapy, oxygen therapy, cough assisted therapy, inhalation therapy, and nebulization therapy.

14. The method of claim 12 or 13, wherein the patient treatment data includes usage data associated with the plurality of respiratory therapies.

15. The method of any of claims 12 to 14, wherein the patient therapy report is a customized patient therapy report, and receiving the request to generate the patient therapy report includes receiving a user selection defining at least one parameter to be included in the patient therapy report.

16. The method of any of claims 12 to 15, wherein the patient identifier is a unique alphanumeric code associated with the patient.

17. 1. A system including a non-transitory computer readable medium storing instructions that, when executed, cause the system to: an act of collecting patient treatment data associated with a plurality of respiratory therapies used by a particular patient, the plurality of respiratory therapies including at least two of ventilation therapy, oxygen therapy, cough assisted therapy, inhalation therapy, and nebulization therapy; transmitting the collected patient treatment data to a server, the server including a patient data module storing patient treatment data for a plurality of individual patients, including the particular patient; A system that implements the above.

18. 20. The system of claim 17, wherein the system includes a data transfer element, the operation of collecting the patient treatment data includes receiving the patient treatment data at the data transfer element, and the operation of transmitting the collected patient treatment data includes transmitting the patient treatment data from the data transfer element to the server.

19. 20. The system of claim 18, wherein the data transfer element is capable of being coupled to a plurality of medical devices, and the operation of receiving the patient treatment data at the data transfer element comprises receiving patient treatment data associated with the plurality of medical devices.

20. the plurality of medical devices at least one respiratory device configured to provide the plurality of respiratory therapies; At least one additional medical device, the at least one additional medical device being a blood pressure monitor, a blood glucose monitor, a heart rate monitor, an SpO 2 at least one additional medical device, including a monitor, a weight monitor, a carbon dioxide monitor, and / or a drug delivery device; Including, 20. The system of claim 19, wherein the patient treatment data includes (i) first patient treatment data associated with the plurality of respiratory therapies and the at least one respiratory device, and (ii) second patient treatment data associated with the at least one additional medical device.

21. 20. The system of claim 17 or 18, wherein the act of collecting patient treatment data associated with the multiple respiratory therapies includes collecting the patient treatment data from a single respiratory device configured to deliver the multiple respiratory therapies to the particular patient.

22. 20. The system of claim 17 or 18, wherein the operation of collecting patient treatment data associated with the multiple respiratory therapies includes collecting the patient treatment data from at least two respiratory devices configured to deliver the multiple respiratory therapies to the particular patient.

23. The system of any of claims 17 to 22, wherein the operation of transmitting the collected patient treatment data to the server includes automatically and periodically transmitting the collected patient treatment data to the server.

24. The system of any one of claims 17 to 22, wherein the operation of transmitting the collected patient treatment data to the server includes transmitting the collected patient treatment data to the server in response to a user selection to transmit the collected patient treatment data to the server.

25. The system of any of claims 17 to 22, wherein the act of transmitting the collected patient treatment data to the server comprises transmitting the collected patient treatment data to the server on a continuous basis.

26. The system of any of claims 17 to 25, wherein the instructions, when executed, further cause an operation to generate a patient therapy report, the patient therapy report including a graphical representation of at least a portion of the patient treatment data transmitted to the server.

27. 27. The system of claim 26, wherein the instructions, when executed, further cause an action of displaying the patient therapy report via a digital display.

28. 30. The system of claim 27, wherein the displayed patient therapy report is interactive.

29. 29. The system of claim 27 or 28, wherein the displayed patient therapy report is customized based on user preferences.

30. The system of any one of claims 17 to 29, wherein the plurality of respiratory therapies includes ventilation therapy, oxygen therapy, and cough support therapy.

31. The system of any of claims 17-30, wherein the instructions, when executed, further cause an operation of analyzing the collected patient data and providing one or more recommendations associated with at least one of the plurality of therapies based on the analysis.

32. 32. The system of claim 31 , wherein the operation of analyzing the collected patient data includes using a trained machine learning model to identify the one or more recommendations associated with at least one of the plurality of therapies.

33. 1. A computer-implemented method for monitoring a treatment of a particular patient, the method comprising: collecting first patient treatment data associated with a first medical device used by the particular patient; collecting second patient treatment data associated with a second medical device used by the particular patient; transmitting the collected first and second patient treatment data to a server, the server including a patient data module storing data associated with a plurality of individual patients, including the particular patient; generating a report including the first patient treatment data and the second patient treatment data; A method comprising:

34. the first medical device is a respiratory device providing at least one of ventilation therapy, oxygen therapy, cough assisted therapy, inhalation therapy, or nebulization therapy; The second medical device may be a blood pressure monitor, a blood glucose monitor, a heart rate monitor, an SpO 2 34. The method of claim 33, wherein the device is a monitor, a weight monitor, a carbon dioxide monitor, and / or a drug delivery device.

35. 35. The method of claim 33 or 34, wherein the first patient treatment data is associated with a respiratory therapy and the second patient treatment data is associated with a non-respiratory therapy.