System and method for varying the amount of data sent to an external source

Through the cloud-connected chronic disease management platform, data is collected and sent by using respiratory pressure therapy devices, the problem of insufficient data volume of respiratory pressure therapy devices is solved, detailed monitoring and compliance assessment of patients' health status is achieved, and treatment effect and cost are improved. manage.

CN113382676BActive Publication Date: 2024-11-26RESMED INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980087157.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-09-16
Filing Date
2019-10-31
Publication Date
2024-11-26
Estimated Expiration
2039-10-31

AI Technical Summary

Technical Problem

The existing respiratory pressure therapy devices have insufficient data in sending data, resulting in limited real-time monitoring and analysis capabilities of patients' health status, and difficulty in assessing user compliance, which affects treatment effect and cost management.

Method used

A cloud-connected chronic disease management platform was designed to collect low-resolution and high-resolution data through a respiratory pressure therapy device, and dynamically adjust the data transmission volume based on the trigger event, sending low-resolution data and high-resolution data to external systems. to achieve detailed analysis of patient health status and assessment of user compliance.

Benefits of technology

It improves the real-time monitoring and analysis capabilities of patients' health status, enhances user compliance assessment and treatment effect management, reduces medical costs, and improves the efficiency and accuracy of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113382676B_ABST
    Figure CN113382676B_ABST
Patent Text Reader

Abstract

A system and method for monitoring the health of a patient is disclosed. The system includes a respiratory therapy device having a transmitter and an air control device to provide respiratory therapy to the patient. The respiratory therapy device collects operational data and transmits the collected operational data. A health analysis engine communicates with the respiratory therapy device. The health analysis engine receives the collected data to determine the health status of the patient based on the collected data. The respiratory therapy device transmits low or high resolution data to the health analysis engine. High resolution data is transmitted based on the occurrence of an event detected based on the low resolution data.
Need to check novelty before this filing date? Find Prior Art

Description

1. Background of the invention

[0001] 1.1 Priority claim

[0002] This application claims priority to U.S. Provisional Application No. 62 / 753,828, filed on October 31, 2018, entitled “SYSTEM FOR VARYING DATA VOLUME TRANMITTED TO EXTENSION SOURCE,” and U.S. Provisional Application No. 62 / 900,982, filed on September 16, 2019, entitled “SYSTEM AND METHOD FOR CLODBASED HEALTH CARE ANALYSIS FROM OPERATIONAL DATA COLLECTED FROM A RESPIRATORYTHERAPY DEVICE,” the disclosures of which are incorporated herein by reference in their entirety. 1.2 Technical Field

[0004] The technology relates to one or more of screening, diagnosis, monitoring, treatment, prevention and improvement of breathing-related disorders. The technology also relates to medical devices or apparatuses, and to changing data sent from medical devices to external storage systems. 1.3 Background Technology

[0006] The respiratory system of the body facilitates gas exchange. The nose and mouth form the entrance to the patient's airway. The airway includes a series of branching tubes, which become narrower, shorter and more numerous as the branching trachea penetrate deeper into the lungs. The main function of the lungs is gas exchange, allowing oxygen to enter the venous blood from the inhaled air and expel carbon dioxide in the opposite direction. The trachea is divided into the left main bronchi and the right main bronchi, which are eventually divided into terminal bronchioles. The bronchi constitute the conducting airways and do not participate in gas exchange. Further airway division leads to respiratory bronchioles and ultimately to alveoli. The alveolar region of the lungs is where gas exchange occurs and is called the respiratory zone. See "Respiratory Physiology", 9th edition, published by John B.West, Lippincott Williams & Wilkins in 2012.

[0007] There are a range of respiratory disorders. Some disorders can be characterized by specific events such as apnea, hypopnea, and hyperpnea. Examples of respiratory disorders include obstructive sleep apnea (OSA), Cheyne-Stokes respiration (CSR), respiratory insufficiency, obesity hyperventilation syndrome (OHS), chronic obstructive pulmonary disease (COPD), neuromuscular disease (NMD), and chest wall disorders.

[0008] Chronic diseases are the leading cause of death and disability worldwide. By 2020, their contribution is expected to rise to 73% of all deaths and 60% of the global burden of disease. This is associated with the growth of health care costs. Chronic diseases are the main driver of health care costs, accounting for ninety cents (90¢) of every dollar spent in the United States. In 2015, 1 in 8 people worldwide were over the age of 60. By 2030, it is estimated that 1 in 6 people will be over the age of 60.

[0009] There are chronic disease management (CDM) applications and services to track chronic conditions. An example is the Twine service recently acquired by FitBit. In addition, there are telehealth services that use wired and wireless sensors and cellular data connections to monitor people at home. There is a trend towards technological solutions, and there is increasing acceptance for older people with higher incidences of sleep-disordered breathing and comorbid conditions. Such solutions can include smartphone applications, continuous positive airway pressure (CPAP) use applications, wearable activity monitors, the Internet of Things (IoMT), artificial intelligence (AI), and communication technologies such as Wi-Fi, Bluetooth, 4G and 5G.

[0010] Current chronic disease management apps tend to have poor compliance because users must interact with them regularly and may provide inaccurate information to the app. This is especially the case if the user believes certain responses may change price / cost or insurance or availability of care. In other cases, the user simply cannot tell if their condition is getting worse, or which symptoms are more important than others. In other words, the system removes the boundary between the user and their health management.

[0011] A range of treatments have been used to treat or ameliorate such conditions. In addition, such treatments can be used by otherwise healthy individuals to prevent the onset of respiratory disorders. However, these have a number of disadvantages.

[0012] Various therapies, such as continuous positive airway pressure (CPAP) therapy, non-invasive ventilation (NIV), and invasive ventilation (IV) have been used to treat one or more of the above-mentioned breathing disorders.

[0013] Continuous positive airway pressure (CPAP) has been used to treat obstructive sleep apnea (OSA). Its mechanism of action is that the continuous positive airway pressure acts as a pneumatic splint and prevents upper airway obstruction, such as by pushing the soft palate and tongue forward and away from the posterior oropharyngeal wall. Treatment of OSA by CPAP therapy can be voluntary, so patients may choose not to comply with the therapy if they find the device used to provide this therapy to be one or more of the following: uncomfortable, difficult to use, expensive, and unsightly.

[0014] Non-invasive ventilation (NIV) provides ventilation support to patients through the upper airway to help patients breathe and / or maintain adequate oxygen levels in the body by performing some or all of the work of breathing. The ventilation support is provided via a non-invasive patient interface. NIV has been used to treat CSR and respiratory failure in the form of OHS, COPD, NMD and chest wall disease. In some forms, the comfort and effectiveness of these therapies can be improved.

[0015] Invasive ventilation (IV) provides ventilation support to patients who are no longer able to breathe effectively on their own and may be provided using a tracheostomy tube. In some forms, the comfort and effectiveness of these therapies may be improved.

[0016] These respiratory therapies can be provided by a therapeutic system or device. Such systems and devices can also be used to screen, diagnose, or monitor a condition without treating it. A respiratory pressure therapy (RPT) device can be used alone or as part of a system to deliver one or more of the above-mentioned multiple therapies, for example by operating the device to generate an air flow for delivery to an airway interface. A respiratory therapy system can include a respiratory pressure therapy device (RPT device), an air circuit, a humidifier, a patient interface, an oxygen source, and data management.

[0017] The patient interface can be used to connect a respiratory device to its wearer, for example, by providing a flow of air to an entrance to the airway. The flow of air can be provided to the patient's nose and / or mouth via a mask, to the mouth via a tube, or to the patient's trachea via a tracheostomy tube. Depending on the treatment to be applied, the patient interface can form a seal (e.g., a seal) with an area of ​​the patient's face to facilitate delivery of gas at a positive pressure of about 10 cmH2O relative to ambient pressure and at a pressure that varies substantially from ambient pressure to achieve treatment. For other forms of treatment, such as oxygen delivery, the patient interface may not include a seal sufficient to facilitate delivery of a supply of gas at a positive pressure of about 10 cmH2O to the airway.

[0018] Air pressure generators are known in the context of applications such as industrial scale ventilation systems. However, air pressure generators for medical applications have specific requirements that are not met by more general air pressure generators, such as reliability, size and weight requirements for medical devices. Furthermore, even devices designed for medical use may have disadvantages with respect to one or more of the following: comfort, noise, ease of use, efficacy, size, weight, manufacturability, cost and reliability.

[0019] Due to the difficulty of user compliance, such CPAP devices are configured to transmit certain operational data during operation by the user. Such data allows for a determination as to whether a patient who has been prescribed respiratory therapy has been "compliant," e.g., that the patient has used their respiratory pressure therapy device in accordance with one or more "compliance rules." An example of a compliance rule for CPAP therapy is a requirement that, in order to be considered compliant, a patient use the respiratory pressure therapy device for at least four hours per night on at least twenty-one (21) days out of thirty (30) consecutive days. In order to determine the patient's compliance, a provider of the respiratory pressure therapy device, such as a healthcare provider, may manually obtain data describing the patient's therapy using the respiratory pressure therapy device. The provider may calculate usage over a predetermined time period and compare it to the compliance rules. Once the healthcare provider has determined that the patient has used their respiratory pressure therapy device in accordance with the compliance rules, the healthcare provider may notify a third party (such as a payer) that the patient is compliant.

[0020] However, currently, such devices send very limited respiratory summary data to a remote location via a network such as the cloud, for example, only ten (10) kilobytes per night or three hundred (300 kilobytes) per month. This data is typically provided using only one-way communication, or with very limited two-way service. Detailed data is typically not stored by current devices, or is only stored on a memory card that can be manually read periodically. No real-time cardiac / chronic disease insights are gained from the limited data, as such data is typically only used to determine the operation of the CPAP device.

[0021] It would be advantageous for a system to use existing operational data collected by a respiratory pressure therapy device for disease management. A system is needed that increases the rate of data collected from a respiratory pressure therapy device to analyze health status based on triggering events. There is also a need to integrate additional external data with data collected from a respiratory pressure therapy device to determine a patient's health status. 2. Summary of the invention

[0022] The present technology relates to providing a medical device for screening, diagnosing, monitoring, improving, treating or preventing respiratory disorders with one or more of improved comfort, cost, efficacy, ease of use and manufacturability. Specifically, the present disclosure relates to regulating data used in screening, diagnosing, monitoring, improving, treating or preventing respiratory disorders.

[0023] The present disclosure relates to a cloud-connected chronic disease management platform. The system includes a respiratory pressure therapy device, such as a cloud-connected positive airway pressure (PAP) device. The PAP device includes mechanical components that are traditionally used to treat sleep-disordered breathing (SDB). For example, when using PAP device therapy, patients and / or payers (such as integrated care providers) not only receive data from the device to understand the efficacy and compliance of sleep-disordered breathing treatment, but also understand patient health status, such as atrial fibrillation, potential stroke risk, hypertension (including resistant hypertension), heart failure, type 2 diabetes, and obesity (body fat content) information. Cardiac information can be derived from heart rate, heartbeat information, cardiac output, etc. This is preferably derived from a mask interface with the patient, machine, and related sensors. The system can be connected to other data, such as data contained in the patient's electronic health record (EHR), as part of the overall chronic disease management provision.

[0024] A respiratory therapy system can include a respiratory pressure therapy (RPT) device, an air circuit, a humidifier, a patient interface, an oxygen source, and data management. The RPT device can be used alone or as part of a system to deliver one or more of the above-mentioned multiple therapies, for example by operating the device to generate an air flow for delivery to an airway interface. The airflow can be pressure-controlled (for respiratory pressure therapy) or flow-controlled (for flow therapy, such as high-flow therapy). Therefore, a respiratory pressure therapy device can also act as a flow therapy device. Examples of respiratory pressure therapy devices include PAP devices and ventilators.

[0025] Current respiratory pressure therapy devices, such as CPAP devices, collect data from patients during use. Such collected data is provided to a central hub, such as the device itself or a mobile computing device, to be sent to a cloud-based analysis engine for further analysis primarily related to the patient's health. The disclosed platform uses the increased collection of CPAP data to provide health status analysis for patients. The determined health status of the patient can be used for additional treatment, evaluation of treatment, patient or caregiver warnings, and other purposes.

[0026] In one example, a patient treatment device is provided, comprising a controller, a sensor, a memory, and a transmitter, wherein the sensor is configured to collect data from the patient, and the collected data is stored in the memory, the collected data comprising low-resolution data and high-resolution data; and wherein the transmitter is controlled by the controller to send the low-resolution data or the high-resolution data to an external system, the high-resolution data being sent based on the occurrence of an event detected based on the low-resolution data.

[0027] In one example, a system for sending varying amounts of data is provided, comprising one or more of the patient treatment devices, remote external devices and / or local external devices; wherein a transmitter of the patient treatment device is connectable to a remote external communication network and / or a local external communication network; and wherein the remote external communication network is connectable to the remote external device and / or the local external communication network is connectable to the local external device.

[0028] In one example, a method for sending a varying amount of patient data to an external system is provided, wherein the patient data is stored in a memory, and the patient data includes low-resolution data and high-resolution data, the method comprising: sending the low-resolution data from the memory to the external system via a transmitter inside or outside a respiratory pressure therapy device; determining the occurrence of an event based on the low-resolution data; and when the event occurs, changing the transmitter via a controller inside or outside the respiratory pressure therapy device to send the high-resolution data to the external system.

[0029] One disclosed example is a system for monitoring the health of a patient. The system includes a respiratory therapy device having a transmitter and an air control device to provide respiratory therapy to the patient. The respiratory therapy device collects operational data and transmits the collected operational data. A health analysis engine communicates with the respiratory therapy device. The health analysis engine receives the collected data to determine the health status of the patient based on the collected data.

[0030] Another disclosed example is a method for monitoring the health of a patient using a respiratory therapy device. Operational data of the respiratory therapy device is collected. The collected data is transmitted to a health analysis engine. The health analysis engine determines the health status of the patient based on the collected data.

[0031] The above summary is not intended to represent every embodiment or every aspect of the present disclosure. Rather, the foregoing summary of the invention only provides examples of some of the novel aspects and features set forth herein. The above features and advantages of the present disclosure and other features and advantages will become apparent from the following detailed description of representative embodiments and modes for implementing the present invention when taken in conjunction with the accompanying drawings and the appended claims. 3. Description of the drawings

[0032] The present technology is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like reference numerals refer to like elements, including:

[0033] Figure 1A A system is shown including a patient 1000 wearing a patient interface 3000 in the form of a nasal pillow, receiving a positive pressure air supply from a respiratory pressure therapy (RPT) device 4000. In this example, the respiratory pressure therapy device may include a PAP device, a non-invasive ventilation (NIV) device, or an adaptive support ventilation (ASV) device. Of course, other devices may also perform the functions of the RPT device 4000 described herein. Air from the RPT device 4000 is humidified in a humidifier 5000 and flows along an air circuit 4170 to the patient 1000. A bed partner 1100 is also shown. The patient 1000 sleeps in a supine sleeping position. The health analysis system collects data from the RPT device 4000 used by the patient 1000.

[0034] Figure 1B A system is shown that includes a patient 1000 wearing a patient interface 3000 in the manner of a nasal mask receiving a supply of air under positive pressure from an RPT device 4000. Air from the RPT device is humidified in a humidifier 5000 and flows along an air circuit 4170 to the patient 1000.

[0035] Figure 1C A system is shown that includes a patient 1000 wearing a patient interface 3000 in the form of a full face mask receiving a supply of air under positive pressure from an RPT device 4000. Air from the RPT device is humidified in a humidifier 5000 and flows along an air circuit 4170 to the patient 1000. The patient sleeps in a side-lying sleeping position.

[0036] Figure 2 An overview of the human respiratory system is shown, including the nasal and oral cavities, larynx, vocal cords, esophagus, trachea, bronchi, lungs, alveolar sacs, heart, and diaphragm.

[0037] Figure 3 A patient interface in the form of a nasal mask is shown in accordance with one form of the present technology.

[0038] Figure 4A One form of RPT device according to the present technology is shown.

[0039] Figure 4Bis a schematic diagram of the pneumatic path of an RPT device in accordance with one form of the present technology. Upstream and downstream directions are indicated with reference to a blower and a patient interface. The blower is defined as upstream of the patient interface and the patient interface is defined as downstream of the blower, regardless of the actual flow direction at any particular moment. Items within the pneumatic path between the blower and the patient interface are downstream of the blower and upstream of the patient interface.

[0040] Figure 4C is a schematic diagram of the electrical components of an RPT device according to one form of the present technology.

[0041] Figure 4D is a schematic diagram of an algorithm implemented in an RPT device according to one form of the present technology.

[0042] Figure 4E is a diagram showing a form of the present technology. Figure 4D A flowchart of a method performed by a treatment engine module.

[0043] Figure 5A is an isometric view of a humidifier according to one form of the present technology.

[0044] Figure 5B An isometric view of a humidifier in accordance with one form of the present technology is shown showing the humidifier reservoir 5110 removed from the humidifier reservoir base 5130.

[0045] Figure 6 A model typical breathing waveform of a person during sleep is shown.

[0046] Fig. 7A A patient is shown undergoing a polysomnography (PSG) examination. The patient sleeps in a supine sleeping position.

[0047] Figure 7B A monitoring device for monitoring a patient's condition is shown. The patient is sleeping in a supine sleeping position.

[0048] Figure 7C is a block diagram illustrating a screening / diagnosis / monitoring device that can be used to implement PSG.

[0049] Fig. 8A is a block diagram of a system for receiving modulated data from a monitoring device.

[0050] Figure 8B is a block diagram of an alternative system for receiving modulated data from a monitoring device.

[0051] Fig. 9 It is from Figure 4A and Fig. 7A Flow chart of the process of modulating the data sent by the monitoring device described in the figure.

[0052] Fig.10 It is based on trigger events to increase data collection and provide Figure 4A and Fig. 7A A flow chart of the routine for monitoring device health analysis described in FIG. 4. Specific implementation methods

[0053] Before describing the present technology in further detail, it should be understood that the present technology is not limited to the specific examples described herein, which may be varied. It should also be understood that the terminology used in the present disclosure is only for the purpose of describing the specific examples described herein and is not intended to be limiting.

[0054] The following description is provided about various examples that can share one or more common characteristics and / or features. It should be understood that one or more features of any example can be combined with one or more features of other examples. In addition, in any of the examples, any single feature or combination of features can constitute another example.

[0055] The present disclosure relates to a system that utilizes operational data collected by a respiratory pressure therapy device to allow analysis of patient health status in a cloud-based engine. The system provides connected care service value in the healthcare (and particularly integrated care) market, thereby reducing the burden of care, particularly for those with sleep-disordered breathing and complications, by incorporating sensing technology into positive airway pressure-enabled devices and services supported by communication technologies such as Wi-Fi, Bluetooth, 3G, 4G / LTE, 5G / New Radio, fixed wireless, satellite, etc.

[0056] An exemplary respiratory pressure therapy device can monitor and collect operational data, such as motor voltage, RPM, airflow, and mask leakage. An exemplary respiratory pressure therapy device can also monitor and collect physiological data via a microphone in or near the tube, from a mask signal, from an optical sensor near or on the face (such as in a mask), from electrodes (in or on a mask, headgear), from a connection patch with electrical or optical sensing, from a heart signal obtained from a smart watch, bracelet, or ring. Gas analysis can be sampled at the mask or in the pipeline or device. Sweat analysis can be performed at the mask. Data can also be integrated from other devices used by the patient, such as a smart inhaler.

[0057] Indeed, the disclosed exemplary respiratory data collection platform may encompass chronic disease management beyond sleep disordered respiratory therapy, such as hypertension, stroke, COPD, congestive heart failure (CHF), cardiac arrhythmias such as atrial fibrillation, asthma, diabetes, as well as dementia, mental health issues (e.g., depression, bipolar disorder, ADHD), and other disorders.

[0058] 4.1 Treatment

[0059] In one form, the present technology comprises a method for treating a respiratory disorder comprising: Figures 1A-1C In some examples of the present technology, a positive pressure is applied to the airway entrance of the patient 1000. In some examples of the present technology, a supply of air under positive pressure is provided to the nasal passages of the patient via one or both nostrils. In some examples of the present technology, mouth breathing is restricted, restricted or prevented.

[0060] 4.2 Treatment system

[0061] In one form, the present technology includes an apparatus or device for treating a respiratory disorder. The apparatus or device may include an RPT device 4000 for supplying pressurized air to a patient 1000 via an air circuit 4170 to a patient interface 3000 or 3800 .

[0062] 4.3 Patient Interface

[0063] A non-invasive patient interface 3000 according to one aspect of the present technology includes the following functional aspects: a seal-forming structure 3100, a plenum chamber 3200, a positioning and stabilizing structure 3300, a vent 3400, a connection port 3600 for connecting to a form of air circuit 4170, and a forehead support 3700. In some forms, the functional aspects may be provided by one or more physical components. In some forms, one physical component may provide one or more functional aspects. In use, the seal-forming structure 3100 is arranged to surround the entrance of the patient's airway to facilitate the supply of positive pressure air to the airway.

[0064] The unsealed patient interface 3800 in the form of a nasal cannula comprises nasal prongs 3810a, 3810b, which can deliver air to the corresponding nostrils of the patient 1000. Such nasal prongs are usually not sealed with the inner or outer skin surface of the nostrils. Air can be delivered to these nasal prongs by one or more air supply lumens 3820a, 3820b connected to the nasal cannula 3800. Lumens 3820a, 3820b are guided from the nasal cannula 3800 to the RT device, which generates air flow with a high flow rate. The "vent" at the unsealed patient interface 3800 is a passage to the atmosphere via the patient's nostrils between the ends of the nasal prongs 3810a and 3810b of the cannula 3800, and excess airflow escapes to the surrounding environment through the vent.

[0065] 4.4RPT device

[0066] The RPT device 4000 according to one aspect of the present technology includes mechanical, pneumatic and / or electrical components and is configured to execute one or more algorithms 4300, such as any of the methods described herein in whole or in part. The RPT device 4000 can be configured to generate an air flow for delivery to the airway of a patient, such as for treating one or more respiratory conditions described elsewhere in this document.

[0067] In one form, the RPT device 4000 is constructed and arranged to deliver air flow in the range of -20 L / min to +150 L / min while maintaining a positive pressure of at least 6 cmH2O, or at least 10 cmH2O, or at least 20 cmH2O.

[0068] The RPT device can have an outer housing 4010 that is constructed in two parts: an upper portion 4012 and a lower portion 4014. In addition, the outer housing 4010 can include one or more panels 4015. The RPT device 4000 includes a chassis 4016 that supports one or more internal components of the RPT device 4000. The RPT device 4000 can include a handle 4018.

[0069] The pneumatic path of the RPT device 4000 may include one or more air path items, such as an inlet air filter 4112, an inlet muffler 4122, a pressure generator 4140 (e.g., a blower 4142) capable of supplying air at a positive pressure, an outlet muffler 4124, and one or more converters 4270, such as a pressure sensor 4272 and a flow sensor 4274.

[0070] One or more air path items may be disposed within a removable separate structure, which will be referred to as a pneumatic block 4020. The pneumatic block 4020 may be disposed within the outer housing 4010. In one form, the pneumatic block 4020 is supported by, or forms part of, the chassis 4016.

[0071] The RPT device 4000 may have a power source 4210, one or more input devices 4220, a central controller 4230, a treatment device controller 4240, a pressure generator 4140, one or more protection circuits 4250, a memory 4260, a converter 4270, a data communication interface 4280, and one or more output devices 4290. The electrical components 4200 may be mounted on a single printed circuit board assembly (PCBA) 4202. In an alternative form, the RPT device 4000 may include more than one PCBA 4202.

[0072] The RPT device may include one or more of the following components in an integral unit. In an alternative form, one or more of the following components may be provided as separate units.

[0073] An RPT device according to one form of the present technology may include an air filter 4110, or multiple air filters 4110.

[0074] In one form, the inlet air filter 4112 is positioned at the beginning of the pneumatic path upstream of the pressure generator 4140 .

[0075] In one form, an outlet air filter 4114 , such as an antimicrobial filter, is positioned between the outlet of the pneumatic block 4020 and the patient interface 3000 .

[0076] An RPT device according to one form of the present technology may include a silencer 4120 , or a plurality of silencers 4120 .

[0077] In one form of the present technology, the inlet muffler 4122 is positioned in the pneumatic path upstream of the pressure generator 4140 .

[0078] In one form of the present technology, an outlet muffler 4124 is positioned in the pneumatic path between the pressure generator 4140 and the patient interface 3000 .

[0079] In one form of the present technology, the pressure generator 4140 for generating an air flow or air supply under positive pressure is a controllable blower 4142. For example, the blower 4142 may include a brushless DC motor 4144 having one or more impellers. These impellers may be located in a volute. The blower is capable of delivering an air supply, for example, at a rate of up to about 120 liters per minute, at a positive pressure ranging from about 4 cmH2O to about 20 cmH2O, or in other forms up to about 30 cmH2O. The blower may be as described in any of the following patents or patent applications, the contents of which are incorporated herein by reference in their entirety: U.S. Patent No. 7,866,944; U.S. Patent No. 8,638,014; U.S. Patent No. 8,636,479; and PCT Patent Application Publication No. WO2013 / 020167.

[0080] The pressure generator 4140 is under the control of the treatment device controller 4240. In other words, the pressure generator 4140 may be a piston driven pump, a pressure regulator connected to a high pressure source (eg, a compressed air reservoir), or a bellows.

[0081] The transducer may be internal to the RPT device 4000, or external to the RPT device. An external transducer may be located, for example, on or form part of an air circuit (e.g., a patient interface). An external transducer may be in the form of a non-contact sensor, such as a Doppler radar motion sensor that transmits or transfers data to the RPT device.

[0082] In one form of the present technology, one or more transducers 4270 are located upstream and / or downstream of the pressure generator 4140. The one or more transducers 4270 may be constructed and arranged to generate a signal representative of a characteristic of the air flow at that point in the pneumatic path, such as flow, pressure or temperature.

[0083] In one form of the present technology, one or more transducers 4270 may be located proximate to the patient interface 3000 or 3800. In one form, the signals from the transducers 4270 may be filtered, such as by low pass, high pass or band pass filtering.

[0084] A flow sensor 4274 according to the present technology may be based on a differential pressure transducer, such as the SDP600 series differential pressure transducer from SENSIRION. In one form, the central controller 4230 receives a signal representing flow from the flow sensor 4274 .

[0085] A pressure sensor 4272 according to the present technology is in fluid communication with the pneumatic path. An example of a suitable pressure transducer is a sensor from the HONEYWELL ASDX series. Another suitable pressure transducer is a sensor from the GENERAL ELECTRIC NPA series. In one form, a signal from the pressure sensor 4272 is received by the central controller 4230.

[0086] In one form of the present technology, a motor speed converter 4276 is used to determine the rotational speed of the motor 4144 and / or blower 4142. A motor speed signal from the motor speed converter 4276 may be provided to the treatment device controller 4240. The motor speed converter 4276 may be, for example, a speed sensor, such as a Hall effect sensor.

[0087] In one form of the present technology, an anti-spillback valve 4160 is positioned between the humidifier 5000 and the pneumatic block 4020. The anti-spillback valve is constructed and arranged to reduce the risk of water flowing upstream from the humidifier 5000 to the motor 4144, for example.

[0088] The power supply 4210 may be located inside or outside of the housing 4010 of the RPT device 4000. In one form of the present technology, the power supply 4210 provides power only to the RPT device 4000. In another form of the present technology, the power supply 4210 provides power to both the RPT device 4000 and the humidifier 5000.

[0089] In one form of the present technology, the RPT device 4000 includes one or more input devices 4220 in the form of buttons, switches, or dials to allow a person to interact with the device. The buttons, switches, or dials may be physical devices, or software devices accessible via a touch screen. In one form, these buttons, switches, or dials may be physically connected to the external housing 4010, or in another form, may be in wireless communication with a receiver electrically connected to a central controller 4230.

[0090] In one form, input device 4220 may be constructed and arranged to allow a person to select values ​​and / or menu options.

[0091] Internal sensors such as flow sensor 4274, pressure sensor 4272, and motor speed converter 4276 may be coupled to Figure 4C 1 . An optional internal audio sensor 4278 may be embedded in the interface 3000 of FIG. 1 to detect specific patient air sounds. An optional external audio sensor 4279 (e.g., a microphone) may be located external to the RPT device 4000, interface 3000, or humidifier 5000 to collect additional audio data. Additional sensors, such as a heart rate sensor, an ECG sensor (providing cardiac baseline parameters whose peaks can be processed to estimate heart rate, detect arrhythmias, etc.), a pulse oximeter (SpO2) sensor (providing heart rate, oxygen saturation, and potential estimation of blood pressure from pulse transit time), a blood pressure sensor, a room temperature sensor; a contact or non-contact body temperature sensor, a room humidity sensor, a proximity sensor, a posture sensor, a touch sensor, a gas sensor, an air quality sensor, a particle sensor, an accelerometer, a gyroscope, a tilt sensor, other acoustic sensors such as passive or active SONAR, an ultrasound sensor, a radio frequency sensor, an accelerometer, a light intensity sensor, a LIDAR sensor, an infrared sensor (passive, transmissive or reflective), a carbon dioxide sensor, a carbon monoxide sensor, or a chemical sensor can be connected to the central controller 4230 via an external port. Data from these additional sensors can also be collected by the central controller 4230. Data from sensors 4272, 4274, 4276, 4278, and 4279 can be collected periodically by the central controller 4230. This data typically relates to the operating status of the RPT device 4000.

[0092] In one form of the present technology, the central controller 4230 is one or more processors suitable for controlling the RPT device 4000. Suitable processors may include x86 INTEL processors based on the ARM Holdings -M processor, such as the STM32 series microcontroller from STMICROELECTRONICS. In some alternative forms of the present technology, a 32-bit RISC CPU manufactured by TEXAS INSTRMENTS (such as the STR9 series microcontroller from ST MICROELECTRONICS) or a 16-bit RISC CPU (such as a processor from the MSP430 series microcontroller) may also be suitable.

[0093] In one form of the present technology, the central controller 4230 is a dedicated electronic circuit. In one form, the central controller 4230 is an application specific integrated circuit. In another form, the central controller 4230 contains discrete electronic components.

[0094] The central controller 4230 may be configured to receive one or more input signals from one or more transducers 4270, one or more input devices 4220, and the humidifier 5000. The central controller 4230 may be configured to provide output signals to one or more of the output device 4290, the treatment device controller 4240, the data communication interface 4280, and the humidifier 5000.

[0095] The controller 4230 may collect data at different rates. For example, during normal use, data may be collected at a low resolution rate. As will be explained, a triggering event may cause the controller 4230 to begin collecting data at a different collection rate, such as at a higher resolution for collecting more data and / or additional types of data over a comparative time period for a more detailed analysis of the patient 1000. In this example, the central controller 4230 encodes such data from the sensor in a proprietary data format. The data may also be encoded in a standardized data format.

[0096] In some forms of the present technology, the central controller 4230 is configured to implement one or more methods described herein, such as one or more algorithms 4300 represented as computer programs stored in a non-transitory computer-readable storage medium (such as memory 4260). In some forms of the present technology, the central controller 4230 may be integrated with the RPT device 4000. However, in some forms of the present technology, some methods may be performed by a remotely located device. For example, the remotely located device may determine control settings for the ventilator or detect breathing-related events by analyzing stored data (such as data from any sensor described herein). As described above, all data and operations of the external source or central controller 4230 are generally proprietary to the manufacturer of the RPT device 4000. Therefore, the data from the sensors and any other additional operational data are generally not accessible by any other device.

[0097] The RPT device 4000 may include a clock 4232 connected to a central controller 4230 .

[0098] In one form of the present technology, the treatment device controller 4240 is a treatment control module 4330 that forms part of an algorithm 4300 executed by the central controller 4230, such as Figure 4D In one form of the present technology, the treatment device controller 4240 is a dedicated motor control integrated circuit. For example, in one form, the MC33035 brushless DC motor controller manufactured by ONSEMI is used.

[0099] One or more protection circuits 4250 in accordance with the present technology may include electrical protection circuits, temperature and / or pressure safety circuits.

[0100] According to one form of the present technology, the RPT device 4000 includes a memory 4260, such as a non-volatile memory. In some forms, the memory 4260 may include a battery-powered static RAM. In some forms, the memory 4260 may include a volatile RAM. The memory 4260 may be located on the PCBA 4202. The memory 4260 may be in the form of an EEPROM or NAND flash memory. Additionally or alternatively, the RPT device 4000 includes a removable form of memory 4260, such as a memory card manufactured in accordance with the Secure Digital (SD) standard. In one form of the present technology, the memory 4260 acts as a non-transitory computer-readable storage medium on which computer program instructions are stored that express one or more methods described herein, such as one or more algorithms 4300.

[0101] In one form of the present technology, a data communication interface 4280 is provided and connected to the central controller 4230. The data communication interface 4280 may be connected to a remote external communication network 4282 and / or a local external communication network 4284. The remote external communication network 4282 may be connected to a remote external device 4286. The local external communication network 4284 may be connected to a local external device 4288.

[0102] In one form, the data communication interface 4280 is part of the central controller 4230. In another form, the data communication interface 4280 is separate from the central controller 4230 and may include an integrated circuit or processor. In one form, the remote external communication network 4282 is the Internet. The data communication interface 4280 may be connected to the Internet using wired communication (e.g., via Ethernet or optical fiber) or a wireless protocol (e.g., CDMA, GSM, LTE). In one form, the local external communication network 4284 utilizes one or more communication standards, such as Bluetooth or consumer infrared protocols.

[0103] In one form, the remote external device 4286 is one or more computers, such as a networked computer cluster. In one form, the remote external device 4286 can be a virtual computer rather than a physical computer. In either case, such a remote external device 4286 can be accessed by a properly authorized person (such as a clinician). The local external device 4288 can be a personal computer, a mobile phone, a tablet computer, or a remote control.

[0104] Output devices 4290 in accordance with the present technology may take the form of one or more of visual, audio, and tactile units. [000170] The visual display may be a liquid crystal display (LCD) or a light emitting diode (LED) display.

[0105] Driver 4292 is shown receiving as input characters, symbols, or images to be displayed on display 4294 and converting them into commands that cause display 4294 to display these characters, symbols, or images.

[0106] The display 4294 is configured to visually show characters, symbols, or images in response to commands received from the display driver 4292. For example, the display 4294 may be an eight-segment display, in which case the display driver 4292 converts each character or symbol, such as the number "0," into eight logic signals indicating whether to activate the eight corresponding segments to show the particular character or symbol.

[0107] As described above, in some forms of the present technology, the central controller 4230 may be configured to implement Figure 4D 43. One or more algorithms 4300 are represented in FIG. 43 as computer programs stored in a non-transitory computer-readable storage medium, such as memory 4260. Algorithms 4300 are generally grouped into groups called modules.

[0108] A pre-processing module 4310 according to one form of the present technology receives as input a signal from a transducer 4270 (e.g., a flow sensor 4274 or a pressure sensor 4272) and performs one or more process steps to calculate one or more output values ​​to be used as input to another module (e.g., a therapy engine module 4320).

[0109] In one form of the present technology, the output values ​​include interface pressure Pm, respiratory flow Qr, and leak flow Ql. In various forms of the present technology, the pre-processing module 4310 includes one or more of the following algorithms: interface pressure estimation 4312, vent flow estimation 4314, leak flow estimation 4316, and respiratory flow estimation 4318.

[0110] The interface pressure estimation algorithm 4312 provides as an output an estimated pressure Pm in the patient interface 3000 or 3800. The ventilation flow estimation algorithm 4314 estimates the ventilation flow Qv of air from the vent 3400 in the patient interface 3000 or 3800. The leak flow estimation algorithm 4316 estimates the leak flow Ql by calculating the average of the difference between the total flow Qt and the vent flow Qv over a sufficiently long period of time (e.g., about 10 seconds). The respiratory flow estimation algorithm 4318 estimates the respiratory flow Qr of air to the patient by subtracting the ventilation flow Qv and the leak flow Ql from the total flow Qt.

[0111] In one form of the present technology, the therapy engine module 4320 receives as input one or more of a pressure Pm in the patient interface 3000 or 3800 and a respiratory flow Qr of air to the patient, and provides as output one or more therapy parameters such as one or more of a therapy pressure Pt, a pressure variation amplitude, a basal pressure, and a target ventilation volume.

[0112] In various forms, the therapy engine module 4320 includes one or more of the following algorithms: phase determination 4321, waveform determination 4322, ventilation determination 4323, inspiratory flow limitation determination 4324, apnea / hypopnea determination 4325, snoring determination 4326, airway patency determination 4327, target ventilation determination 4328 and therapy parameter determination 4329.

[0113] Phase determination algorithm 4321 provides as output the phase Φ of the current breathing cycle of patient 1000 .

[0114] The waveform determination algorithm 4322 provides a waveform template Π(Φ) having values ​​in the range [0, 1] over the domain of the phase value Φ provided by the phase determination algorithm 4321 for use by the therapy parameter determination algorithm 4329. The ventilation determination algorithm 4323 receives an input of the respiratory flow Qr and determines a measured value Vent indicative of the current patient ventilation. The inspiratory flow limitation determination algorithm 4324 receives as input the respiratory flow signal Qr and provides as output a measure of the degree to which the inspiratory portion of the breath exhibits inspiratory flow limitation.

[0115] The apnea / hypopnea determination algorithm 4325 receives as input the respiratory flow signal Qr and provides as output a flag indicating that an apnea or hypopnea has been detected. The snoring determination algorithm 4326 receives as input the respiratory flow signal Qr and provides as output a measure of the degree to which snoring is present.

[0116] Airway patency determination algorithm 4327 receives the respiratory flow signal Qr as input and determines the signal power in the frequency range of about 0.75 Hz and about 3 Hz. The presence of a peak in this frequency range is used to indicate an open airway. The absence of a peak is considered an indication of a closed airway.

[0117] The central controller 4230 takes the current ventilation Vent as input and executes one or more target ventilation determination algorithms 4328 for determining a ventilation target value Vtgt.

[0118] The central controller 4230 executes one or more treatment parameter determination algorithms 4329 for determining one or more treatment parameters, such as instantaneous treatment pressure Pt, using values ​​returned by one or more other algorithms in the treatment engine module 4320.

[0119] The therapy control module 4330 according to one aspect of the present technology receives as input therapy parameters from the therapy parameter determination algorithm 4329 of the therapy engine module 4320 and controls the pressure generator 4140 to deliver air flow according to the therapy parameters.

[0120] In one form of the present technology, the central controller 4230 executes one or more methods 4340 for detecting a fault condition. The fault condition detected by the one or more methods 4340 may include at least one of the following:

[0121] Power failure (no power or insufficient power)

[0122] Converter Fault Detection

[0123] Unable to detect the presence of parts

[0124] Operating parameters outside recommended ranges (e.g. pressure, flow, temperature, PaO2).

[0125] The test alarm cannot generate a detectable alarm signal.

[0126] Upon detecting a fault condition, the corresponding algorithm 4340 signals the presence of the fault by one or more of:

[0127] Activate audible, visual and / or dynamic (e.g., vibration) alarms

[0128] Sending messages to external devices

[0129] Event Logging

[0130] 4.5 Air circuit

[0131] The air circuit 4170 according to one aspect of the present technology is a conduit or tube that, when in use, is constructed and arranged to allow air flow to travel between two components, such as the RPT device 4000 and the patient interface 3000 or 3800 .

[0132] Specifically, the air circuit 4170 can be fluidly connected to the outlet of the pneumatic block 4020 and the patient interface. The air circuit can be referred to as an air delivery tube. In some cases, there can be separate branches for the inspiratory and expiratory circuits. In other cases, a single limb is used.

[0133] In some forms, the air circuit 4170 may include one or more heating elements configured to heat the air in the air circuit, for example to maintain or increase the temperature of the air. The heating element may be in the form of a heating wire loop and may include one or more transducers, such as a temperature sensor. In one form, the heating wire loop may be helically wound around the axis of the air circuit 4170. The heating element may be in communication with a controller such as a central controller 4230. An example of an air circuit 4170 including a heating wire loop is described in U.S. Patent 8,733,349, which is incorporated herein by reference in its entirety.

[0134] In one form of the present technology, supplemental gas (e.g., oxygen) 4180 is delivered to one or more points in the pneumatic pathway, such as upstream of the pneumatic block 4020 , to the air circuit 4170 , and / or to the patient interface 3000 or 3800 .

[0135] 4.6 Humidifier

[0136] In one form of the present technology, a humidifier 5000 (e.g., as in Figure 5A ) to change the absolute humidity of air or gas for delivery to a patient relative to ambient air. Typically, a humidifier 5000 is used to increase the absolute humidity and increase the temperature of the air stream (relative to ambient air) before delivery to the patient's airway.

[0137] The humidifier 5000 may include a humidifier reservoir 5110, a humidifier inlet 5002 for receiving an air flow, and a humidifier outlet 5004 for delivering a humidified air flow. Figure 5A and 5B As shown, the inlet and outlet of the humidifier reservoir 5110 can be respectively a humidifier inlet 5002 and a humidifier outlet 5004. The humidifier 5000 can also include a humidifier base 5006, which can be adapted to receive the humidifier reservoir 5110 and include a heating element 5240.

[0138] 4.7 Respiratory waveform

[0139] Figure 6 A typical breathing waveform of a model of a person during sleep is shown. The horizontal axis is time, and the vertical axis is respiratory flow. While the parameter values ​​may vary, a typical breath may have the following approximate values: tidal volume Vt 0.5L, inspiratory time Ti 1.6s, peak inspiratory flow Qpeak 0.4L / s, expiratory time Te 2.4s, peak expiratory flow Qpeak-0.5L / s. The total duration of the breath Ttot is about 4s. A person typically breathes at a rate of about 15 breaths per minute (BPM), with a ventilation outlet of about 7.5L / min. A typical duty cycle, the ratio of Ti to Ttot is about 40%.

[0140] 4.8 Screening, diagnosis and monitoring systems

[0141] Fig. 7A A patient 1000 undergoing a polysomnogram (PSG) is shown. The PSG system includes a headbox 2000 that receives and records signals from the following sensors: EOG electrodes 2015; EEG electrodes 2020; ECG electrodes 2025; submandibular EMG electrodes 2030; snoring sensor 2035; respiratory inductive plethysmogram (respiratory effort sensor) 2040 on a chest strap; respiratory inductive plethysmogram (respiratory effort sensor) 2045 on an abdominal strap; oral and nasal cannula 2050 with oral thermistor; photoplethysmograph (pulse oximeter) 2055; and body position sensor 2060. The electrical signals are referenced to a ground electrode (ISOG) 2010 located at the center of the forehead.

[0142] Figure 7B An example of a monitoring device 7100 for monitoring the breathing of a sleeping patient 1000 is shown. The monitoring device 7100 includes a non-contact motion sensor generally directed toward the patient 1000. The motion sensor is configured to generate one or more signals representing body motion of the patient 1000, from which signals a signal representing the patient's breathing motion can be obtained.

[0143] Respiratory polygraph (RPG) is a term used for a simplified form of PSG that does not have electrical signals (EOG, EEG, EMG), snoring, or body position sensors. The RPG contains at least a chest motion signal from a respiratory induced plethysmogram (motion sensor) on a chest strap, such as motion sensor 2040, a nasal pressure signal sensed via a nasal cannula, and an oxygen saturation signal from a pulse oximeter (e.g., pulse oximeter 2055). These three RPG signals or channels are received by an RPG headbox similar to PSG headbox 2000.

[0144] In certain configurations, the nasal pressure signal is a satisfactory proxy for the nasal flow signal generated by a flow transducer in line with a sealing nasal mask because the nasal pressure signal is comparable in shape to the nasal flow signal. If the patient's mouth remains closed, i.e., there is no mouth leak, then the nasal flow is equal to the respiratory flow.

[0145] Figure 7C 7200 is a block diagram illustrating a screening / diagnostic / monitoring device 7200 that can be used to implement an RPG headbox in an RPG screening / diagnostic / monitoring system. The screening / diagnostic / monitoring device 7200 receives the three RPG channels (a signal indicating chest movement, a signal indicating nasal flow, and a signal indicating oxygen saturation) described above at a data input interface 7260. The screening / diagnostic / monitoring device 7200 also includes a processor 7210 configured to execute coded instructions. The screening / diagnostic / monitoring device 7200 also includes a non-transitory computer readable memory / storage medium 7230.

[0146] The memory 7230 may be an internal memory of the screening / diagnosis / monitoring device 7200, such as RAM, flash memory, or ROM. In some embodiments, the memory 7230 may also be a removable or external memory linked to the screening / diagnosis / monitoring device 7200, such as, for example, an SD card, a server, a USB flash drive, or an optical disk. In other embodiments, the memory 7230 may be a combination of an external memory and an internal memory. The memory 7230 includes storage data 7240 and a processor control instruction (code) 7250 suitable for configuring the processor 7210 to perform a specific task. The storage data 7240 may include RPG channel data received by the data input interface 7260, as well as other data provided as a component of the application. The processor control instruction 7250 may also be provided as a component of the application. The processor 7210 is configured to read the code 7250 from the memory 7230 and execute the encoded instructions. Specifically, the code 7250 may include instructions suitable for configuring the processor 7210 to execute a method for processing the RPG channel data provided by the interface 7260. One such method may be to store the RPG channel data as data 7240 in memory 7230. Another such method may be to analyze the stored RPG data to extract features. Processor 7210 may store the results of such analysis as data 7240 in memory 7230.

[0147] The screening / diagnostic / monitoring device 7200 may also include a communication interface 7220. The code 7250 may include instructions configured to allow the processor 7210 to communicate with an external computing device (not shown) via the communication interface 7220. The communication mode may be wired or wireless. In one such embodiment, the processor 7210 may send the stored RPG channel data from the data 7240 to a remote computing device. In such an embodiment, the remote computing device may be configured to analyze the received RPG data to extract features. In another such embodiment, the processor 7210 may send the analysis results from the data 7240 to the remote computing device.

[0148] Alternatively, if the memory 7230 is removable from the screening / diagnostic / monitoring device 7200, the remote computing device may be configured to connect to the removable memory 7230. In such an embodiment, the remote computing device may be configured to analyze the RPG data retrieved from the removable memory 7230 to extract features.

[0149] 4.9 Respiratory therapy mode

[0150] Various respiratory therapy modes can be implemented by the RPT device 4000. In some embodiments of respiratory pressure therapy, the central controller 4230 sets the therapy pressure Pt according to the therapy pressure equation (1) as part of the therapy parameter determination algorithm 4329.

[0151] Pt=AΠ(Φ,t)+P0 (1)

[0152] Where: A is the amplitude, Φ(Πt) is the waveform template value (in the range of 0 to 1) at the current value of phase Φ and time t, and P0 is the reference pressure.

[0153] In one such embodiment, the amplitude A is equal to zero, so the treatment pressure Pt (which represents the target value achieved by the interface pressure Pm at the current moment) is equal to zero throughout the breathing cycle. Such embodiments are generally grouped under the heading of CPAP therapy. In these embodiments, the treatment engine module 4320 is not required to determine the phase, Φ or the waveform template, Φ(Π).

[0154] In CPAP therapy, the basal pressure P0 may be a constant value that is hard-coded or manually input into the RPT device 4000. Alternatively, the central controller 4230 may repeatedly calculate the basal pressure P0 based on indicators or measurements of sleep-disordered breathing (such as one or more of flow limitation, apnea, hypopnea, openness, and snoring) returned by a corresponding algorithm in the therapy engine module 4320. This alternative approach is sometimes referred to as APAP therapy.

[0155] Figure 4E is a flow chart illustrating a method 4500 executed by the central controller 4230 to continuously calculate a basal pressure P0 when the pressure support A is equal to zero as part of an APAP therapy implementation of the therapy parameter determination algorithm 4329.

[0156] The method 4500 begins at step 4520, where the central controller 4230 compares the measure of the presence of an apnea / hypopnea to a first threshold and determines whether the measure of the presence of an apnea / hypopnea has exceeded the first threshold for a predetermined period of time, indicating that an apnea / hypopnea is occurring. If so, the method 4500 proceeds to step 4540; otherwise, the method 4500 proceeds to step 4530. At step 4540, the central controller 4230 compares the measure of airway patency to a second threshold. If the measure of airway patency exceeds the second threshold, indicating that the airway is patent, the detected apnea / hypopnea is considered central and the method 4500 proceeds to step 4560; otherwise, the apnea / hypopnea is considered obstructive and the method 4500 proceeds to step 4550.

[0157] At step 4530, central controller 4230 compares the measure of flow limitation to a third threshold. If the measure of flow limitation exceeds the third threshold, indicating that inspiratory flow is limited, method 4500 proceeds to step 4550; otherwise, method 4500 proceeds to step 4560.

[0158] In step 4550, if the obtained process pressure Pt does not exceed the maximum process pressure P max , the central controller 4230 increases the base pressure P0 by a predetermined pressure ΔP. In one embodiment, the predetermined pressure ΔP and the maximum treatment pressure P max In other embodiments, the pressure ΔP may be as low as 0.1 cmH2O and as high as 3 cmH2O, or as low as 0.5 cmH2O and as high as 2 cmH2O. In other embodiments, the maximum treatment pressure P max It may be as low as 15 cmH 2 O and as high as 35 cmH 2 O, or as low as 20 cmH 2 O and as high as 30 cmH 2 O. Method 4500 may then return to step 4520 .

[0159] At step 4560, the central controller 4230 reduces the base pressure P0 by a decrement as long as the reduced base pressure P0 does not drop to the minimum process pressure P min The method 4500 may then return to step 4520. In one embodiment, the reduction is related to P0-P min The value of is proportional to that in which, in the absence of any detected event, P0 to the minimum process pressure P min The reduction is exponential. In one embodiment, the proportionality constant is set so that the time constant of the exponential decrease of P0 is 60 minutes, and the minimum treatment pressure P min In other embodiments, the time constant can be as low as 1 minute and as high as 300 minutes, or as low as 5 minutes and as high as 180 minutes. In other embodiments, the minimum treatment pressure P min It can be as low as 0 cmH2O and as high as 8 cmH2O, or as low as 2 cmH2O and as high as 6 cmH2O. Alternatively, the reduction amount of P0 can be preset so that if no event is detected, P0 to the minimum treatment pressure P min The reduction is linear.

[0160] In other embodiments of this form of the present technology, the value of the amplitude A in equation (1) can be positive. Such an embodiment is referred to as bi-level therapy because when the treatment pressure Pt is determined using equation (1) with a positive amplitude A, the treatment parameter determination algorithm 4329 oscillates the treatment pressure Pt between two values ​​or levels that are synchronized with the spontaneous breathing efforts of the patient 1000. That is, based on the above-mentioned typical waveform template, Φ(Πt), the treatment parameter determination algorithm 4329 increases the treatment pressure Pt to P0+A (referred to as IPAP) at the beginning of exhalation or during inspiration, and reduces the treatment pressure Pt to the base pressure P0 (referred to as EPAP) at the beginning of exhalation or during exhalation.

[0161] In certain forms of bi-level therapy, IPAP is a therapy pressure that has the same purpose as the therapy pressure in the CPAP therapy mode, and EPAP is IPAP minus amplitude A, which has a "small" value (a few cmH2O), sometimes referred to as expiratory pressure relief (EPR). This form is sometimes referred to as CPAP therapy with EPR, which is generally considered to be more comfortable than straight CPAP therapy. In CPAP therapy with EPR, one or both of IPAP and EPAP can be constant values ​​that are hard-coded or manually entered into the RPT device 4000. Alternatively, the therapy parameter determination algorithm 4329 can repeatedly calculate IPAP and / or EPAP during CPAP and EPR. In this alternative, the therapy parameter determination algorithm 4329 repeatedly calculates EPAP and / or IPAP based on indicators or measurements of sleep disordered breathing returned by the corresponding algorithm in the therapy engine module 4320 in a manner similar to the calculation of the basal pressure P0 in APAP therapy described above.

[0162] In other forms of bi-level therapy, Amplitude A is large enough that the RPT device 4000 performs some or all of the work of breathing for the patient 1000. In this form of therapy, called pressure support ventilation, Amplitude A is called pressure support or swing. In pressure support ventilation therapy, IPAP is the base pressure P0 plus pressure support A, and EPAP is the base pressure P0.

[0163] In some forms of pressure support ventilation therapy, referred to as fixed pressure support ventilation therapy, the pressure support A is fixed at a predetermined value, such as 10 cmH 2 O. The predetermined pressure support value is a setting of the RPT device 4000 and may be set, for example, by hard coding during configuration of the RPT device 4000 or by manual entry via the input device 4220.

[0164] In other forms of pressure support ventilation therapy, broadly referred to as servo-ventilation, a therapy parameter determination algorithm 4329 takes as input some currently measured or estimated parameter of the respiratory cycle (e.g., a currently measured value of ventilation Vent) and a target value for that respiratory parameter (e.g., a target value of ventilation Vtgt), and repeatedly adjusts the parameters of equation (1) to bring the currently measured value of the respiratory parameter to the target value. In a form of servo-ventilation known as adaptive servo-ventilation (ASV), which has been used to treat CSR, the respiratory parameter is ventilation, and the target ventilation value Vtgt is calculated by a target ventilation value determination algorithm 4328 based on a typical recent ventilation value Vtyp, as described above.

[0165] In some forms of servo-ventilation, the therapy parameter determination algorithm 4329 applies a control method to repeatedly calculate the pressure support A in order to bring the current measured value of the respiratory parameter to the target value. One such control method is proportional integral (PI) control. In one embodiment of PI control, applicable to ASV mode, where the target ventilation volume Vtgt is set slightly less than the typical recent ventilation volume Vtyp, the pressure support A is repeatedly calculated as:

[0166] A=G∫(Vent-Vtgt)dt (2)

[0167] Where G is the gain of the PI control. Larger gain values ​​G can result in positive feedback in the treatment engine module 4320. Smaller gain G values ​​can allow for some residual untreated CSR or central sleep apnea. In some embodiments, the gain G is fixed to a predetermined value, such as -0.4cmH2O / (L / min) / sec. Alternatively, the gain G can vary between treatment periods, starting small and increasing from one period to another until a value is reached that substantially eliminates the CSR. In such an embodiment, a conventional device for retrospectively analyzing parameters of a treatment period to assess the severity of CSR during the treatment period can be employed. In other embodiments, the gain G can vary based on the difference between the current ventilation measurement Vent and the target ventilation Vtgt.

[0168] Other servo-ventilation control methods that may be applied by the therapy parameter determination algorithm 4329 include proportional (P), proportional-derivative (PD), and proportional-integral-derivative (PID).

[0169] The value of the pressure support A calculated via equation (2) may be limited to a range defined as [Amin, Amax].

[0170] In this embodiment, the pressure support A is at the minimum pressure support Amin by default until the measured value of the current ventilation Vent drops below the target ventilation Vtgt, at which point A starts to increase and only drops back to Amin when Vent exceeds Vtgt again.

[0171] The pressure support limits Amin and Amax are settings of the RPT device 4000 , such as by hard coding during configuration of the RPT device 4000 or by manual entry through the input device 4220 .

[0172] In the pressure support ventilation therapy mode, EPAP is the base pressure P0. As with the base pressure P0 in CPAP therapy, EPAP can be a constant value that is specified or determined during titration. Such a constant EPAP can be set, for example, by hard coding during configuration of the RPT device 4000 or by manual input via the input device 4220. This alternative approach is sometimes referred to as fixed EPAP pressure support ventilation therapy. Titration of a given patient's EPAP can be performed by a clinician with the aid of a PSG during a titration session with the goal of preventing obstructive apnea and thereby maintaining an open airway for pressure support ventilation therapy in a manner similar to the titration of the base pressure P0 in constant CPAP therapy.

[0173] Alternatively, the therapy parameter determination algorithm 4329 can repeatedly calculate the basal pressure P0 during the pressure support ventilation therapy. In such an embodiment, the therapy parameter determination algorithm 4329 repeatedly calculates EPAP based on an indicator or metric of sleep disordered breathing returned by a corresponding algorithm in the therapy engine module 4320, such as one or more of flow limitation, apnea, hypopnea, openness, and snoring. Because the continuous calculation of EPAP is similar to the manual adjustment of EPAP by a clinician during EPAP titration, the process is sometimes also referred to as automatic titration of EPAP, and the therapy mode is referred to as automatically titrating EPAP pressure support ventilation therapy or automatic EPAP pressure support ventilation therapy.

[0174] In other forms of respiratory therapy, the pressure of the air flow is not controlled as it is used for respiratory pressure therapy. Instead, the central controller 4230 controls the pressure generator 4140 to deliver an air flow whose device flow Qd is controlled to a therapeutic or target flow Qtgt. These forms are typically grouped under the heading of flow therapy. In flow therapy, the therapeutic flow Qtgt can be a constant value that is hard-coded or manually entered into the RPT device 4000. If the therapeutic flow Qtgt is sufficient to exceed the patient's peak inspiratory flow, the therapy is typically referred to as high flow therapy (HFT). Alternatively, the therapeutic flow can be a curve Qtgt(t) that varies with the respiratory cycle.

[0175] 4.10 Data transmission resolution

[0176] Figure 1A A system 100 for monitoring the health of a patient 1000 is shown. Thus, the system 100 includes a respiratory pressure therapy device 4000, a humidifier 5000, an optional external device such as a mobile device 110, and a body-mounted health monitoring device 120. The system 100 also includes a remote cloud-based health data analysis engine 130. The health data analysis engine 130 can be run on one or more networked computing devices available through the cloud. The analysis engine 130 in this example can be a cloud-based system coupled via a network 140. The health analysis engine 130 is therefore in network communication with the respiratory therapy device 4000.

[0177] The respiratory pressure therapy device 4000 includes a transmitter and an air control device for providing respiratory therapy to the patient 1000. As will be explained, the respiratory pressure therapy device 4000 collects operational data and transmits the collected operational data to the remote health data analysis engine 130. The health data analysis engine 130 receives the collected data from the respiratory therapy device 4000 to determine the health status of the patient 1000 based on the collected data. The engine 130 can also receive and add other relevant data from the patient information database 150, the health monitoring device 120, and the mobile device 110. External databases (such as database 160) can also provide additional data for analyzing health status. For example, the database 160 can contain "big data" from other respiratory pressure therapy devices and corresponding patients. The database 160 can also store relevant external data from other sources, such as environmental data, scientific data, and demographic data. External devices such as workstations 170 that can be accessed by healthcare providers can be connected to the health analysis engine 130, as will be explained below.

[0178] The data from the database 150 and the health condition may be further correlated by the machine learning engine 180. The machine learning engine 180 may implement machine learning structures such as neural networks, decision tree ensembles, support vector machines, Bayesian networks, or gradient boosting machines. Such structures may be configured to implement linear or nonlinear predictive models for determining different health conditions. For example, data processing, such as classification of health conditions, may be performed by any one or more of supervised machine learning, deep learning, convolutional neural networks, and recurrent neural networks. In addition to descriptive and predictive supervised machine learning with handcrafted features, deep learning may also be implemented on the machine learning engine 180. This typically relies on a larger amount of scored (labeled) data for normal and abnormal conditions (such as hundreds of nights of scored sleep and health data from different RPT devices). This approach may implement multiple interconnected layers of neurons to form a neural network ("deeper" than a simple neural network), so that each layer "learns" increasingly complex features. Machine learning may use more variables than handcrafted features or simple decision trees.

[0179] Convolutional neural networks (CNNs) are widely used in audio and image processing to infer information (such as for facial recognition), and can also be applied to audio spectrograms, or even population-scale genomic datasets created from data collected in the system 100 represented as images. When performing image or spectrogram processing, the system cognitively "learns" temporal and frequency characteristics from the intensity, spectrum, and statistical estimates of the digitized image or spectrogram data.

[0180] In contrast to CNNs, not all problems can be represented as problems with fixed-length inputs and outputs. For example, processing breath sounds or heart sounds has similarities with speech recognition and time series prediction. Therefore, sound analysis can benefit from systems that store and use contextual information such as recurrent neural networks (RNNs), which can take previous outputs or hidden states as input. In other words, they can be multi-layer neural networks capable of storing information in context nodes. RNNs allow for processing variable-length inputs and outputs by maintaining state information across time steps, and can contain LSTMs (Long Short-Term Memory, a type of “neuron” that enables RNNs to have increased control over it, which can be unidirectional or bidirectional) to manage the vanishing gradient problem and / or by using gradient clipping.

[0181] The machine learning engine 180 can be trained for supervised learning of known health conditions from known data inputs to help analyze the input data. The machine learning engine 180 can also be trained for unsupervised learning to determine unknown correlations between input data and health conditions, thereby increasing the scope of analysis of the health data analysis engine 130.

[0182] Data from additional sensors may be collected, such as sensors on a body-mounted health monitoring device 120 worn by the patient 1000. The body-mounted health monitoring device 120 may be a smart wearable garment, a smart watch, or a smart device to continuously capture data from the patient 1000 in a low-impact manner. For example, the health monitoring device 120 may include one or more sensors, such as an audio sensor, a heart rate sensor, a respiration sensor, an ECG sensor, a photoplethysmography (PPG) sensor, an infrared sensor, an activity sensor, a radio frequency sensor, a SONAR sensor, an optical sensor, a Doppler radar motion sensor, a thermometer, or an impedance, piezoelectric, photoelectric, or strain gauge type sensor. The data may be fused with other data sources collected during the day or during certain time periods, such as data from operating the RPT device 4000. The data may be sent to a mobile computing device 110 that may communicate with the RPT device 4000. Alternatively, data from additional sensors on the health monitoring device 120 may be sent directly to the RPT device 4000. Data from the health monitoring device 120 , the RPT device 4000 , or the mobile computing device 110 may be sent to the cloud 140 .

[0183] In the examples herein, the RPT device 4000 may include electronic components to act as a communication hub to manage data transmission with other sensors in the vicinity of the patient 1000, as well as to transmit the collected data for remote processing by the health analysis engine 130. Examples of other sensors may include blood pressure monitors, weighing scales, sleep sensors, blood glucose monitors, and smart medication / drug adhesive boxes. Such data may be collected by the RPT device 4000 even when the RPT device 4000 itself is not delivering therapy. Alternatively, the mobile device 110 may collect data from the health monitoring device 120, the RPT device 4000, and other data sources, and thus act as a communication hub to manage data transmission for remote processing to the health analysis engine 130. Other devices that can communicate with the RPT device 4000, such as a personal digital assistant, may also act as a communication hub.

[0184] The exemplary RPT device 4000 includes integrated sensor and communication electronics such as Figure 4C Older RPT devices can be updated with a sensor module that can contain communication electronics for sending collected data. Such a sensor module can be attached to the RPT device and thus send operational data to the remote analysis engine 130.

[0185] “Integrated care” is a term that reflects the focus on improving the patient experience and achieving greater efficiency and value from the health delivery system. Figure 1AThe example system 100 in is directed to providing a complete solution for patients, healthcare providers, and payers that incorporates high data rate and / or intelligent sensing and analysis of data from respiratory therapy devices.

[0186] In this example, the system 100 can vary the "resolution of data" uploaded to the cloud 140, edge of the cloud, etc. from a PAP device such as the RPT device 4000 based on events and / or for specific purposes that require more detail in the collected data. These intelligent health insights into co-morbidities with high resolution data and sensing can be achieved by utilizing the RPT device 4000 in contact with the patient 1000 throughout the night (mask / pillow). This allows for a change from traditional low resolution respiratory analysis to high resolution cardiopulmonary insights, enhanced by cloud processing from the health analytics engine 130.

[0187] In this example, the RPT device 4000 can output airflow and pressure signals at a relatively low frequency (e.g., 25 Hz). Other low-resolution data, such as mask pressure, air pressure, EPR pressure, leak data, respiratory rate, tidal volume, minute ventilation, snoring, and flow limitation, can be collected every two (2) seconds. Optional external sensors that can be connected to the RPT device 4000 can allow collection of other data, such as oxygenation (SpO2) and pulse rate. In addition, the collected data can be annotated for medical data exchange and storage using standards such as the European Data Format (EDF). As will be explained, the above data can be collected in a higher resolution mode. In addition, the high resolution mode can allow collection of additional types of data or data derived from the basic data.

[0188] The exemplary health monitoring system 100 is based on an exemplary RPT device 4000 that functions as a connected hub in a home environment. In this example, the hub role is combined with an external health data analysis engine 130 for managing sleep disordered breathing and chronic conditions. This can be provided as a service to a comprehensive payer. The RPT device 4000 and associated sensors (such as health monitoring devices 120) can monitor all aspects of chronic conditions that the patient 1000 may have. For example, the analysis engine 130 can predict exacerbations (e.g., asthma attacks, COPD exacerbations) or cardiac conditions (paroxysmal atrial fibrillation, worsening atrial fibrillation, or stroke) before they occur based on triggering events that can be determined from the collected data. Other diseases and health conditions can be monitored based on correlations with the collected data. Such correlations can be determined by Figure 1A The machine learning engine 180 in is determined.

[0189] In this example, there are different triggering events that can result in an increase in the rate and type of data collected from the RPT device 4000. Therefore, the RPT device 4000 can include two data collection modes. The low rate collection mode can include collecting standard operating data. The high rate collection mode can increase the collection rate and / or type of data that can be used to analyze health status over a predetermined time period compared to the low rate collection mode. The process for the health monitoring system is based on triggering events determined from data collected in the low rate collection mode. A determination is made as to whether a triggering event has occurred and what the event indicates.

[0190] After detecting a triggering event, it may be determined whether the triggering event is real. Verification of a real triggering event may be based on data from multiple sensors or the duration of the event. If it is determined that the triggering event is not real, data collection returns to the data collection level prior to the triggering event. Optionally, the device involved in the triggering event may perform diagnostics to determine if there is a problem / error that generated the false event. If the trigger reflects a real event, processing may proceed in different modes based on data collection.

[0191] The changed data resolution can be a higher data rate sampled by the device and uploaded to the cloud or a higher data rate uploaded to the cloud but already sampled by the device. Figure 4C The sensors shown are sampled. These can include sensors in the mask 3000, as well as flow sensors and acoustic sensors in the respiratory pressure therapy device 4000. Additional sensors can be turned on / off to control the amount of data and / or data rate (increase / decrease).

[0192] In the case of a real triggering event, a severity check can be performed to determine the urgency or severity required for the response action. The severity determination is based on how severe the triggering event may be. For example, a low severity event can trigger a notification to a patient to take action. A high severity event may require a clinician to take action or require an emergency response. The determination of triggering events and the assessment of event severity can be rule-based or automatically controlled by a machine learning algorithm. The machine learning engine 180 can be taught to determine different triggering events based on the collected input data and a training set of triggering events. Similarly, the machine learning engine 180 can be taught to determine the severity and appropriate response of different triggering events. The weights used to determine triggering events and response levels can be refined by the machine learning engine 180 as additional data is collected, and the results are evaluated.

[0193] For example, a triggering event may be a request to create a health record for a user or patient, which may be initiated by the patient 1000 or a caregiver. The health record may be created via the mobile device 110 or a remote external device (e.g. Figure 1ASuch commands may be provided remotely from a workstation 170 in the system. For example, a request to create a health record may be made to establish a new baseline for the user, to detect normal trends for the user for comparison with future longitudinal data, or to access an electronic health record. Alternatively, the baseline may be determined by adding data from the patient to a baseline associated with a patient population with standard values ​​for the patient type.

[0194] The data collected for such a request may include cardiac information, such as heart rate values, average (e.g., running mean or median) heart rate, baseline heart rate, heart rate trends on different time scales, heart rate variability (variation in the interval between beats) on different time scales. The different time scales may be seconds, minutes, hours, multiple hours, days, or other intervals. The heart rate values ​​(when combined with PAP and non-PAP sensing) may also be associated with the time of day or night, whether the user is asleep, and in what sleep stage, whether the user is sitting quietly, exercising, and any other relevant factors. Cardiac output and CO2 levels may also be monitored over time. Analysis of cardiogenic oscillations may be used to infer the health of the lungs (and heart) over time by providing insight into the local airflow and distribution within the lungs. Similarly, the data may include motion metrics that are processed to estimate activities on different time scales and processes, such as the user's motion in bed with or without PAP, or during daily life. These data may be processed to calculate the patient's energy expenditure.

[0195] Respiratory data can be processed to track inhalation and exhalation values, estimate respiratory rate, determine any apnea or hypopnea, determine snoring duration, intensity and type, and trends on different time scales. Machine parameters such as mask leak or vent leak can be tracked over time, which will be explained below. The gas content in the exhaled breath can be analyzed to detect abnormal content, as well as chemicals in the environment (e.g., regular tobacco, tobacco smoke, scented laundry detergents, etc.). An estimate of dyspnea can be generated based on respiratory rate, respiratory curve (indicating faster and shallower breathing), cardiac changes (such as potential changes in palpitations and cardiac output), and subjective feedback from the user that it is difficult to breathe or feel suffocated can be included. Changes in sleep structure can also be captured, such as an increase in wake-up time, and / or more segmented sleep (the number of wake-ups or wake-ups, and the duration of each cycle). Any of these parameters can be compared with a global or personalized trigger level.

[0196] Another example of a triggering event is an unusual lack of use of an RPT device. An interruption in the low rate data collection from the exemplary RPT device 4000 can alert a healthcare provider or patient that the patient is away from home and has not taken the travel device with him. Another situation may be if the patient is too sick to operate the treatment device. In this case, other living space sensors such as smart assistants, mattress or bed sensors, light sensors, temperature sensors, occupancy sensors, passive infrared (PIR) sensors, video / security cameras, radio frequency (RF) imaging sensors (such as UWB or IR-UWB), microwave sensors, building or home smart management systems, intruder alarm sensors and settings (current mode, such as enabled or disabled), smart meters (measuring electricity usage), door operation switches, audio detection sensors, fall detection sensors, the presence of smart phones and / or Bluetooth beacons, smart phone battery / charging / usage including user interface (UI) interactions or movement can be accessed to check the patient's condition.

[0197] Another exemplary situation may be if a patient forgets to operate their therapeutic device. A push notification may be sent to a smart device such as mobile device 110 to remind the patient. Another exemplary situation may be if a consumable such as a filter, oxygen tank, or battery has been depleted, preventing the device from being used. System 100 may then provide communication to a supply system to deliver replacement consumables directly to the patient, or provide delivery of consumables to a pharmacy for patient pickup or to a technician for installation at the patient location.

[0198] Another example of triggering enhanced data collection is the provision of a new medication or treatment. For example, if a new medication is provided to a user, or a new medication is provided to a market where a user is starting a new or changed medication regimen, the system 100 can monitor respiration and cardiac activity (and possibly perform gas analysis) at a higher collection rate to check that the new treatment is successful and does not have side effects or interact with other medications. Key data may include changes in cardiac status, such as changes in heart rate over time (and changes in heart rate due to sleep stage), changes in heart rate variability (e.g., greater variability can be a sign of improvement), reduction in paroxysmal atrial fibrillation, increase in cardiac output, changes in blood pressure, changes in respiratory rate, changes in breathing depth, changes in activity level, reduction in estimated discomfort, improvement in sleep quality, reduction in insomnia symptoms, increase in reported energy level, reduction in residual apnea or snoring or wheezing or coughing, improvement in lung function, reduction in required PAP pressure, increase in PAP use, and reduction in reported depression or anxiety. Insomnia is a complaint of dissatisfaction with sleep quality or duration, involving difficulty in starting to sleep, frequent or prolonged awakenings, or early morning awakenings without being able to return to sleep. In addition, it can include significant daytime distress, functional impairment, mood disturbances, cognitive decline, and fatigue.

[0199] A similar procedure can be used to evaluate medications or treatments that are typically used for a patient. If a patient has medication delivery via a platform integrated with the RPT device 4000, the dosage or frequency of administration can be automatically adjusted. Such a delivery platform can include a drug reservoir. For example, a drug reservoir can be used in conjunction with a patch for daytime delivery (thereby saving power and the medication contained in the patch. Thus, when the RPT device 4000 is in use (typically during the night shift), the RPT device 4000 can control the drug reservoir to administer the medication. Thus, a drug delivery platform with regular or abnormal delivery of medication based on trigger events is implemented. Based on clinical review and approval, certain medications such as bronchodilators, anti-inflammatory drugs, and antibiotics can be delivered to patients. These can be delivered while the patient is awake and wearing a patient interface. Delivery of these medications can be performed by pressing a button. For example, such delivery can be combined with oxygen delivery. For people who are detected to be having an asthma attack, instead of the RPT device 4000 increasing pressure (which may worsen the situation), the system 100 can provide the patient with a request (or automatically) to deliver a relief dose via the patient interface or mobile device 110 The mobile device 110 may include an application that sends additional instructions to the patient. For example, the application may also require the patient to sit upright and may contact emergency services or other healthcare providers. Similarly, medication may be provided to patients suffering from (or predicted to suffer from) COPD exacerbation or CHF decompensation. Other medications (such as nasal decongestants) may treat upper respiratory tract infections associated with the common cold or flu (e.g., Alzheimer's disease) in an attempt to prevent such exacerbations from worsening. Other devices for administering medication may be communicatively integrated with the RPT device 4000. For example, medication may be delivered via a smart inhaler, a combination monitor accessory attached to the inhaler (such as those provided by Propeller Health), or other smart connected metered drug delivery systems / devices that may communicate the occurrence and other data of the medication dose inhaled by the patient 1000.

[0200] Enhanced data can be used to analyze different elements of respiratory pressure therapy, such as whether the patient's condition is changing, or whether a threshold or trend is met. For example, airflow data can be used to determine how the CPAP device adapts to the patient. This data can be used to determine whether sleep-disordered breathing worsens or improves over time. For example, an open or closed patient airway can be detected by inducing airflow with a CPAP device and generating pressure modulation. The airflow signal measured by demodulating the flow sensor 4274 separates the modulated signal from the heartbeat and other factors. If the average sensed signal is greater than 0.03l / sec, it indicates that the airway is open, and if the average sensed signal is less than 0.03l / sec, it indicates that the airway is closed. Other data can be collected to estimate cardiovascular fitness or determine the respiratory rate, hydration, local ischemia, blood pressure, and cholesterol levels of the patient 1000.

[0201] Flow data, motor speed, pressure, and acoustic data from an exemplary RPT device 4000 can be used to characterize the RPT device 4000. As explained above, these sensors can be used to detect flow generation from the motor, characteristics of the respiratory device conduit (e.g., the tube or hose to the mask), the mask or cannula fit, motor speed, and gas volume flow and outlet pressure (from a pressure transducer or flow sensor). For example, the data can be used to identify accessories and components such as mask type, tube or hose, number of hoses, and connectors. Data can be collected to determine any leaks indicating whether the fit of the mask interface 3000 is within acceptable parameters. This can also be related to whether the patient is using the optimal size or type of mask, or whether the mask specifically must be replaced due to common wear and tear. Tubes can be used as a signal from the mask interface 3000 to identify any leaks. Figure 4C The acoustic waveguide of the internal acoustic sensor 4278 in the flow generator. Data can be collected by the flow generator running at a constant speed (to have a substantially flat acoustic data signal) or with variations introduced at specific times.

[0202] The raw acoustic data from the acoustic sensor 4278 can be processed to determine the transfer function of the tube, mask, and respiratory system, thereby obtaining new insights into the condition of the equipment, the lungs of the patient 1000, and the gas composition. The transfer function can also be used to detect patient motion. For example, the reflections from the motor sound can show peaks associated with the round trip time from the acoustic sensor 4278 to the mask cavity and back. The system knows the tube length and sound speed of various gases (e.g., typical composition of air, composition changes when the inhaled air and exhaled carbon dioxide are greater than the basic CO2 level in the air, or indeed any expected changes due to supplemental oxygen, changes in sound speed of different gases at different temperature and humidity settings).

[0203] One method of modeling a transfer function by calculating an impulse response function is to use "cepstral" analysis. Cepstrum analysis originates from analyzing seismic events and is useful in processing echo signals. Cepstrum analysis can allow the separation of different effects because different events can be added in the logarithm of the power spectrum and are separable. Other processing methods may include the use of logarithmic power spectrum (LogFFT), segmented Chirp Z transform (SCZT) and flexible windows, or time-frequency representations (TFRs), such as short-time Fourier transforms (STFTs), Gabor expansions, cross-ambiguity functions (CAFs) and quadratic TFRs, such as Wigner-Ville distributions (WVDs). When considering cepstrum analysis, the autospectrum is the cepstrum of the autocorrelation of the signal. Cepstrum analysis involves processing a sound sample from a tube, performing a Fourier transform, taking the logarithm, and then performing an inverse Fourier transform. The purpose of this process is to convert the convolution of the impulse response function (IRF) and the noise or sound signal into an addition operation to more easily allow the separation of the IRF for analysis.

[0204] For example, to detect a kink or blockage in a tube, a reference value can be first calculated (e.g., a training sample of a tube without blockage), then a new measurement can be made while the tube is in operation (e.g., where the tube has kinked, causing a blockage), and the difference (e.g., a constant value of significant samples of the difference) calculated to estimate the location (in the tube) by determining the location of "significant" samples such as peaks. The degree or severity of the blockage can be determined based on changes in peak amplitude or profile. Alternatively, autocorrelation (inverse Fourier transform of the power spectrum) can be used. In a similar manner, mask type, size, and the person's respiratory system can be modeled based on analysis of the IRF, such as using deep learning imaging / spectrogram methods (or directly, based on processing of received audio samples).

[0205] The collected data can also be used to determine the analysis of sleep stages. For example, the movement of a patient interface such as a mask 3000 can be determined from an embedded motion sensor to determine the patient's movement. Normalized respiratory rate changes and inhalation / exhalation ratio changes can be determined for sleep stage analysis. Heart rate change trends can also be determined for sleep stage analysis. For example, by tracking the peaks in the cardiogenic signal seen in one or more of the flow, pressure or microphone signals, the peak-to-peak time can be used to estimate the number of heart beats per minute (HR bpm) and good heart rate variability (such as spectral analysis of the time between heart beats). Such data can be related to how the sleep structure develops and used to determine whether the patient is experiencing the expected number of sleep stages, whether the patient is sleeping in segments, whether the patient is receiving enough REM and deep sleep, and whether the patient is going to the toilet for frequent urination. As input to the machine learning model, features such as age and gender information can be used. Estimated movement intensity, duration and activity pattern, heart rate, heart rate variability, respiratory rate, respiratory rate variability, normalized respiratory rate variability, respiratory signal waveform (inhalation, exhalation pause) can be calculated as part of the sleep stage analysis system. In some embodiments, the stream and / or microphone signal can be directly provided to a model, such as a deep learning neural network system. The system can calculate wakefulness (conscious and unconscious micro-awakening cycles, light sleep (stages NREM, N1, N2), N3 deep sleep / slow wave sleep, and REM sleep). The system learns changes in respiratory rate and / or heart rate variability during different stages of sleep, as well as the relationship with the patient's movement. Knowledge of sleep stage patterns can be used to adjust treatment settings to optimize deep sleep and REM sleep, maximize total sleep time, and reduce wakefulness and light sleep. Demographic data such as age and gender information can be input into the machine learning model to determine the sleep stage. The input can include age, gender, estimated exercise intensity, duration and activity pattern, heart rate, heart rate variability, respiratory rate, respiratory rate variability, normalized respiratory rate variability, and respiratory signal waveform shape (inhalation, exhalation pause) of the sleep staging analysis block of the machine learning model.

[0206] Sleep stage analysis can also be combined with other data to determine stress, mental health problems or other physiological problems. For example, during the sleep stage, a decrease in heart rate and blood pressure can be expected. If the collected data indicates a deviation from the expected drop, this provides an indication of stress, mental health problems or other physiological problems. Another example can be to predict the possibility of complex sleep apnea before starting continuous positive airway pressure ventilation. This can be related to the severity of sleep disorder breathing diagnosed before treatment, the prevalence of central events during the test, and continuous monitoring of central and obstructive events (and examples of periodic breathing) after diagnosis but before treatment (such as via acoustic or RF sensing or other motion and sleep breathing estimators). Analysis of sleep hypnosis / sleep structure, especially interruption / fragmentation, and the ratio of NREM to REM sleep in hypopnea density can also be used as input features. Appropriate therapy can then be selected to address the disease.

[0207] The collected data can be used to determine respiratory changes for tracking condition changes, such as COPD (e.g., higher than normal respiratory rate / shortness of breath). The collection of respiratory data over time can determine how the basal (e.g., average "baseline" level) respiratory rate evolves over time. The collection of respiratory data can also be used to measure exhalation, expiratory pressure release (EPR) compensation time during exhalation (e.g., as configured and delivered by the RPT), total inspiratory time and amplitude, and breath holding time (time before the next cycle). Such disease analysis can include tracking worsening disease conditions. The collected data can be analyzed to detect worsening asthma, pollen allergies, common colds, or respiratory infections. For example, lung impedance can be monitored to detect changes in lung conditions over time. Other increases in a patient's airway resistance can indicate a worsening condition. For example, COPD and asthma are diseases in which airway narrowing occurs and therefore exhibits increased airway resistance, which can be detected or estimated.

[0208] Data from sensing devices such as a spirometer (or similar device combined with or enabled by an RPT) can measure respiratory flow and calculate inspiratory and expiratory lung volumes. In addition to data collected from devices such as glucose monitors or gas detection of volatile organic compounds (VOCs) produced by the body's metabolic activity, the data can also be related to blood chemistry; these gas molecules can be detected from the breath. For example, certain VOCs are associated with COPD, asthma, and CHF. Therefore, the data can determine detected biomarkers that suggest CHF, diabetes, other chronic conditions. Blood glucose can be determined from breath sampling throughout the night. For example, a volatile organic compound sensor can be added to the RPT 4000 to monitor diabetes. VOC sensors can also be used to monitor the endocrine system by sampling signals to measure gas content (including CO2) to understand hormone balance during sleep. Sleep stages can be checked against hormone production via gas analysis, respiratory, cardiac, and movement parameters determined from the collected data.

[0209] The collected data can also be analyzed to determine other health events that are not directly related to respiratory conditions. For example, the data can be related to changes in heart rate, cardiac output, and cardiac reference signals. Heart rate can be determined by pressure modulation caused by the heartbeat caused by cardiogenic oscillations. The data can be related to determining whether the heart is operating effectively as a pump, whether the heart rate drops as expected during sleep, horizontal or respiratory sinus arrhythmia, signs of bradycardia, tachycardia, premature atrial contraction (PAC), premature ventricular contraction (PVC), paroxysmal atrial fibrillation (PAF), atrial fibrillation (AF), atrial flutter, ventricular tachycardia, and ventricular fibrillation. Certain conditions such as ventricular fibrillation can cause an alarm to be generated (e.g., a medical emergency) or cause treatment to be applied. Additional correlations for non-respiratory conditions can be determined by data collected from multiple patients via the machine learning engine 180.

[0210] Audio data can be used to confirm or enhance health status analysis. For example, Figure 4C The sound data from the patient's breathing from the internal audio sensor 4278 in can be used in conjunction with the external sounds detected by the external audio sensor 4279 to determine the sound data. In order to collect detailed audio data, the RPT 4000 can be controlled to reduce or stop the blower to obtain sufficient audio samples. An example of sound data processing can be the above-mentioned cepstrum analysis.

[0211] The sound data may include the level of residual snoring, wheezing, stridor, sputtering, and the sound of the heartbeat. These sounds can be used to determine respiratory and other health conditions. For example, the intensity and timing (inhalation or exhalation) of the wheezing sound can be a symptom of a respiratory condition, disorder, or disease. In addition, the absence of sounds, such as a silent chest, may indicate a combination of severe asthma and other vital signs such as a higher heart rate and respiratory rate.

[0212] Can be obtained from Figure 4C Acoustic processing of data from internal and external acoustic sensors 4278 and 4279 in the ventilator to gain cardiac insight. This data can be combined with the use of mask and airflow data to monitor cardiac output and heart rate. The acoustic data can be used to model the catheter, mask and upper airway (nose, pharynx and larynx) and lower airway (trachea, bronchi and alveoli).

[0213] The collected data may be analyzed in the context of a specific patient condition that may be derived from data from other sources. Such data may include data entered through an application running on the mobile device 110, or from a database such as Figure 1A Thus, the patient-specific data may contain conditions that the patient may have, such as pre-existing problems, demographic details (BMI, age, gender) and geographic details (allergen risk due to pollen count, heat exhaustion due to outside temperature, air quality and oxygen amount due to altitude), and medications relevant to the patient.

[0214] The patient input data may include subjective feedback about how the patient feels, whether the patient feels tired, and sleepiness level. This data may be used to determine the patient's sleep quality. This may be a comparison to the patient's personal baseline, a correlation to weather data, a comparison to an average sleeper of their age and gender (with the goal of being better than average), or a comparison to an average of people with the same chronic condition and / or disease progression. As described above, the baseline may be a baseline determined from a normal patient population relative to the patient. Such data may be shown in an application executed by the mobile device 110. Such data may also be obtained by a healthcare professional at the workstation 170.

[0215] Sensors on the RPT device 4000 can sense the gas (breath) from the patient 1000 using, for example, a cross-reactive sensor array and pattern recognition / deep learning to identify characteristic changes in certain VOCs due to disease progression. Additional sensors can detect gases, smoke, or particles (e.g., measuring the amount of PM2.5 (respirable particles typically 2.5 microns or less in diameter) and PM10 (particles 10 microns or less in diameter) in the room environment in which the RPT device 4000 is located and in the patient's exhaled gas. This data can be used to determine whether bacteria, viruses, and other contaminants have been adequately filtered, such as removing particles 0.3 microns and smaller, including most mold, mildew, and viruses, via a HEPA filter.

[0216] As described above, another device such as a smart phone, a smart device, a smart speaker such as Alexa or Google Home, a smart service such as Siri or Bixby, etc. may contain an application that can trigger increased data collection. For example, acoustic sensing can be run on the device to listen for breathing sounds such as inhalation, exhalation, coughing, wheezing, nasal congestion, sneezing, stridor, and whistling. Acoustic sensing can also be activated using sonar to sense reflected signals from the chest. RF sensors can be integrated into the smart device to detect ballistocardiograms (motion or heart), movement of the chest and abdomen with breathing, or activity.

[0217] If a new sensor or other data stream becomes available, a processing event can be triggered. This can include allocating more processing resources to analyze more detailed waveforms over a period of time (e.g., requiring higher data transmission, and potentially higher energy consumption) to identify and manage new or worsening conditions. In addition, a new device (e.g., a new CPAP) can trigger increased data collection. This increased data can allow for changes to the device, calibration to new settings, and configuration of an optimized profile for that user. The increased data can be used to confirm that the RPT device 4000 (including the motor) is operating as expected. For example, a filter can be determined to be clean based on processing of data from the internal acoustic sensor 4278.

[0218] For example, an event could be if ECG data is derived from the collected data that shows left ventricular hypertrophy, the presence of atrial fibrillation (irregular beats), or signs of tachycardia. The system could then determine that the event represents a possible stroke. Such data could also represent a heart attack, stress (heart rate averages not decreasing as expected during sleep), COPD, or complex apnea (increase in central events seen before and during early treatment).

[0219] Such triggering events may also indicate incorrect RPT device settings, uncomfortable users, blood pressure, asthma attacks, and arrhythmias such as diabetes. Typically, the results are then determined by analysis. The patient is notified and the patient can take recommended measures. For example, the action may include an action that can be sent to the patient via the mobile device 110. For example, a message may be sent to the patient to check the biosignals associated with the event. These actions may also include a notification indicating the need for medication, which the patient may already have. The event may be a reminder of the patient's current feeling or health status. For example, an application on the mobile device 110 may ask the patient to enter a response to a query such as "How do you feel" or other questions related to the patient's current state. Such data can be collected from the patient input to the application in the form of a slider or a numerical rating. Such subjective information can provide additional verification to cross-check the collected objective data stream. Therefore, the patient's response can be used as a feedback mechanism to reduce the risk of false positive triggering events. The response can also be compared with previous patient input. Changes in one or some of these user-reported problems (as well as perceived increases in quality of life, such as increased alertness, ability to walk or walk longer distances, not feeling breathless, or elimination of respiratory infections), along with improvements in the analysis of the collected data, can be captured by the system. The application on the mobile device 100 can also suggest that the patient consult a healthcare professional. The application can present the patient with basic data generated from the health analysis engine 130. The application can provide data indicative of good health, which can be used for rewards or incentives, such as health insurance discounts. Training can be provided to the patient based on the granular data.

[0220] In other examples, other actors such as payers can take action in response to the triggering event. For example, the payer can be a government official, an employer, an insurance provider, or a physician. The information can allow the payer to request that the patient go to a healthcare facility for new testing because the information can indicate a new and / or unknown / undiagnosed condition. The payer can determine if a sleep-related disorder is occurring and avoid patient readmissions. Clinician-specific analytics can allow healthcare providers to focus on which patients to insure / treat and track the efficacy of medications / treatments.

[0221] Such as Figure 4A The RPT 4000 connection device in the can store and send different levels of data. For example, Figure 4C The central controller 4230 in the RPT 4000 may send data to an external source 4286. Such data may include data collected by a sensor of the RPT 4000 (such as a flow sensor 4272 or a pressure sensor 4272), data generated by an algorithm of a pre-processing module 4310, or data generated by an algorithm of a treatment engine module 4320. Alternatively, such as Fig. 7AThe headbox 2000 in the apparatus may include sensors as described above that may provide additional data. Such data may be combined for analysis by algorithms that generate more data.

[0222] Such data can be separated into low-resolution data sent externally under most normal operating conditions of the RPT 4000 and high-resolution data sent under certain abnormal conditions. In this example, the low-resolution data can be considered to be sent by Figure 4C The controller 4230 in the embodiment of the present invention samples data once or less per minute. High-resolution data can be defined as data sampled more than once per minute. In such an example, the low and high-resolution data are the same type of sensing data, differing only in the rate at which the data is sampled from the patient. Of course, the high-resolution data can be sensing data of a different type than the low-resolution data. In this case, the high-resolution data is a type of data that is not typically sent by the central controller 4230 to an external device. Of course, the high-resolution data can also be a combination of low-resolution data at a higher sampling rate and additional types of data that are different from the low-resolution data.

[0223] Fig. 8A A block diagram of an example healthcare system 400 that collects operational data from an RPT device such as the RPT device 4000 used by the patient 1000 in FIG. 1 and provides healthcare services to the patient 1000 is shown. The healthcare system 400 may include multiple patients. Each patient may use an RPT device having similar functionality to the RPT device 4000, additional sensors such as the health monitoring device 120, and an associated mobile computing device. Collectively, the RPT devices, sensors, and mobile computing devices used for different patients may be shown as RPT systems 402 and 404. Such a system collects data from the respective patients of the healthcare system 400 who need respiratory therapy. The healthcare system 400 includes a data server 412, an electronic medical record (EMR) server 414, a health or home care provider (HCP) server 416, a supply and support server 418, and a payer data server 420. The data server 412 executes the healthcare analytics engine 130 and may access different databases, such as the patient information database 150 and other databases, such as the database 160. In system 400, these entities are all connected to a wide area network 140 (such as a cloud or the Internet) and are configured to communicate with each other over wide area network 140. The connection to wide area network 140 may be wired or wireless. Data server 412, EMR server 414, HCP server 416, support server 418, and payer server 420 may all be implemented on different computing devices at different locations, or any subset of two or more of these entities may be implemented together on the same computing device.

[0224] In this example, the RPT 4000 or a mobile device 110 associated with the patient is configured to interpose between the patient 1000 and the remotely located entity of the system 400 over the wide area network 140. In the embodiment of Figure 4, this intermediation is implemented by a software application 430 running on the mobile device 110 or RPT 4000. Such an application may be a dedicated application or a web browser that interacts with a website provided by a health or home care provider.

[0225] As described above, the data collected from the RPT 4000 can be provided for patient health status analysis of the patient 1000 by the healthcare analytics engine 130. The analysis can also include an application 1000 that monitors treatment or medication for that particular patient, as explained above. In the examples herein, the RPT 4000 or mobile device 110 is configured to send data collected from the RPT 4000 and other devices via a wireless protocol that receives data as part of an application run by a corresponding controller. The RPT 4000 or mobile device 110 sends data to the data server 412 according to a "pull or push" model. The data server 412 can receive data according to a "pull" model, whereby the RPT 4000 sends operational data in response to queries from the data server 412. Alternatively, the data server 412 can receive the collected data according to a "push" model, whereby the RPT device 4000 sends event data to the data server 412 when the event data is available. Additionally, the data server 412 may access the database 150 to store the collected and analyzed data related to the patient 1000 and other databases 160 of big data or other relevant data related to the population of patients.

[0226] The collected data received from the RPT device 4000 or the mobile device 110 is stored by the data server 412 and indexed into the database 150 so as to be uniquely associated with the patient 1000 and thus distinguishable from data collected from other devices in the system 400. In this regard, although only three RPT user systems are shown in FIG. 4 for ease of illustration, the system 400 may include more RPT user systems with corresponding RPT devices, sensors, mobile computing devices, and other components. The data server 412 may be configured to calculate summary data for each treatment session based on the data received from the RPT device 4000. The data server 412 may also be configured to receive data from the mobile device 110, including data input by the corresponding patient 1000, behavioral data or qualitative data about the patient.

[0227] The EMR server 414 contains electronic medical records (EMRs) that are specific to the patient of the system 400 and common to a larger group of patients with similar conditions as the patient 1000. An EMR, sometimes referred to as an electronic health record (EHR), typically contains a patient's medical history, including prior conditions, treatments, comorbidities, and current status. The EMR server 414 can be located, for example, at any hospital where the patient 1000 has previously been treated. The EMR server 414 is configured to send EMR data to the data server 412, possibly in response to a query received from the data server 412.

[0228] In this example, the HCP server 416 is associated with a health / home care provider (which may be an individual health care professional or an organization) responsible for the patient's respiratory therapy. The HCP may also be referred to as a DME or HME (home / home medical equipment provider). The HCP server 416 may host a process 432 described in more detail below. One function of the HCP server process 432 is to send data related to the patient to the data server 412, possibly in response to a query received from the data server 412.

[0229] In some embodiments, the data server 412 is configured to communicate with the HCP server 416 to trigger notifications or action recommendations to the HCP's agent (such as a nurse), or to support various reports. The details of the actions performed are stored by the data server 412 as part of the engagement data. The HCP server 416 hosts an HCP server process 432 that communicates with the analysis engine 130 and applications on the mobile device 110.

[0230] For example, the HCP server process 432 or a similar process on the data server 412 can provide compliance analysis based on the use of the RPT 4000 according to a compliance rule that specifies the required RPT usage within a compliance period, such as thirty (30) days, with a minimum duration of device usage per treatment course considered, such as four hours, for a certain minimum number of days within the compliance period (e.g., 21 days). If the duration of a treatment course exceeds the minimum duration, the treatment course is considered compliant. Post-processing of the usage data can determine whether the most recent treatment course was a compliant treatment course by comparing the duration of usage to the minimum duration from the compliance rule. The result of this post-processing is compliance data that forms part of the usage data, such as a Boolean compliance variable. Another example of multi-session usage data is a count of compliant treatment courses since the start of RPT treatment. The summary data post-processing can determine whether the most recent time period was a compliant treatment course by comparing the usage time to the minimum duration from the compliance rule. This adherence data can be used by health care providers to customize treatments that can include inhalers and other agents. Other actors, such as payers, can use the adherence data to determine whether a patient can be reimbursed.

[0231] The data may also be provided to a support server 418, which may run processes to ensure that the supply chain is alerted to provide replacement components or parts for the RPT 4000. The support server 418 may also alert a service provider to provide maintenance or repairs to the RPT 4000.

[0232] It will be appreciated that the data in the data server 412, the EMR server 414, the HCP server 416, and the support server 418 are typically confidential data related to the patient in the system 400. Typically, the patient must provide permission to send confidential data to another party. If the servers 412, 414, 416, and 418 are operated by different entities, these permissions may be required to send data between these servers.

[0233] System 400 combines Figure 1A1 . The system 400 may include an AR / VR (augmented reality / virtual reality) healthcare professional consultation based on detected patient issues from the health analytics engine 130. Such consultation may be provided by a patient-accessible device such as a mobile device 110 or other media device such as a smart TV. For planned registrations, the system 400 may provide healthcare providers with recent and trending data such as a physician and predictions of future changes (getting better, getting worse, stable) for the patient 1000. For unplanned registrations, the system 400 may summarize why the registration occurred (e.g., whether the registration was triggered by the system, the patient, or the physician / clinician / caregiver). Such information may be obtained from a network-enabled device that may be accessed by a physician / clinician / caregiver, such as the workstation 170 in FIG. 1 .

[0234] For real-time or near real-time intervention, appropriate processing and communications can be used. Technically, if new radio 5G is used, the deployment can include placing the device into the operator's network (edge ​​cloud processing) and / or "slicing" the fast path (logical separation) in the operator's network to ensure that critical care alerts are delivered to physicians / health care entities / first responders, etc. The data connection between the devices in Figure 4 can use slicing as part of the assurance around connectivity and information security.

[0235] In terms of service delivery, this may include automatically creating a health care facility appointment, and booking transportation to the health care facility (e.g., taxi, autonomous vehicle, ambulance). Such services may be provided by process 432 of HCP server 416 alone or in conjunction with processes executed by support server 418.

[0236] Figure 8B 100B, the RPT device 4000 communicates with the patient computing device 110 via a local (wired or wireless) communication protocol, such as a local network protocol (e.g., Bluetooth). Figure 4C The local external communication network 4284 is used to identify the local network and can be used Figure 4C The local external device 4288 of the patient computing device 110 is used to identify the patient computing device 110. In the alternative embodiment 7000B, the patient computing device 110 is configured via the patient program 430 to be between the patient 1000 and the data server 412 on the wide area network 140, and between the RPT device 4000 and the data server 412 on the wide area network 140.

[0237] Hereinafter, statements regarding the RPT system 400 may be understood to apply equally to the alternative embodiment 7000B unless otherwise expressly stated. For example, other servers such as the EMR server 414, the HCP server 416, the supply and support server 418, and the payer data server 420 may communicate with each other and with the patient computing device 110 via the network 140.

[0238] In this example, RPT device 4000 is configured to store therapy data from each RPT therapy session delivered to patient 1000 in memory 4260. The therapy data for an RPT phase includes settings for RPT device 4000 and therapy variable data representing one or more variables of respiratory pressure therapy throughout the RPT phase.

[0239] The RPT device 4000 is configured to send treatment data to the data server 7010. As described above, the sending of data is modulated based on different circumstances. In normal operation, only low resolution data is sent. High resolution data may be sent under different circumstances, as will be explained below. The data server 412 may receive treatment data from the RPT device 4000 according to a "pull" model, whereby the RPT device 4000 sends treatment data in response to a query from the data server 412. Alternatively, the data server 412 may receive treatment data according to a "push" model, whereby the RPT device 4000 sends the treatment data to the data server 412 as soon as possible after the RPT treatment session.

[0240] Therapy data received from the RPT device 4000 is stored and indexed by the data server 412 so as to be uniquely associated with the RPT device 4000 and, therefore, distinguishable from therapy data from any other RPT device participating in the RPT system 400 .

[0241] In this example, the data server 412 is configured to calculate different types of analytical data that can be used by the clinician. For example, usage data for each RPT session can be determined based on the treatment data received from the RPT device 4000. The usage data variables for the session contain summary statistics derived by a conventional scoring device from the treatment variable data that forms part of the treatment data. The usage data can include one or more of the following usage variables: a) usage time, i.e., the total duration of the RPT session; b) apnea-hypopnea index (AHI) for the time period; c) average leak flow rate for the session; d) average mask pressure for the session; e) the number of "sub-sessions" within the RPT time period, i.e., the number of intervals of RPT treatment between "mask on" and "mask off" events; and f) other statistical summaries of treatment variables, such as the 95th percentile pressure, median pressure, and histograms of pressure values. The usage variables can include multi-stage statistics, such as the mean, median, and variance of the AHI since the start of RPT treatment.

[0242] Other servers may be coupled to network 140 and acquire data based on the "push" or "pull" model described above. For example, a data server 420 operated by a payer may receive data for various purposes, such as determining adherence or predicting adherence for use in determining payment for treatment of patient 1000. Figure 1A The machine learning server of the machine learning engine 180 in the embodiment may also receive data for learning or refining a baseline for abnormal situations that require high-resolution data, as will be explained below. Alternatively, the machine learning server may learn the optimal response when an abnormal situation is detected, or learn the correct prediction data to be included in the high-resolution data in response to certain abnormal situations.

[0243] In an alternative embodiment, the RPT device 4000 calculates the usage variables at the end of each treatment session based on the treatment data stored by the RPT device 4000. The RPT device 4000 then sends the usage variables to the data server 7010 based on the "push" or "pull" model described above.

[0244] In another embodiment, the memory 4260 in which the RPT device 4000 stores the treatment / usage data for each RPT treatment session is in a removable form, such as an SD memory card. The removable memory 4260 can be removed from the RPT device 4000 and inserted into a card reader that communicates with the data server 412. The treatment / usage data is then copied from the removable memory 4260 to the memory of the data server 412.

[0245] In yet another embodiment of the alternative embodiment 7000B suitable for the RPT system, the RPT device 4000 is configured to transmit the therapy / usage data to the patient computing device 110 via a wireless communication protocol such as Bluetooth described above. The patient computing device 110 then transmits the therapy / usage data to the data server 412. The data server 412 may receive the therapy / usage data from the patient computing device 110 according to a "pull" model, whereby the patient computing device 110 transmits the therapy / usage data in response to a query from the data server 412. Alternatively, the data server 412 may receive the therapy / usage data according to a "push" model, whereby the patient computing device 110 transmits the therapy / usage data to the data server 412 as soon as it is available after the RPT session.

[0246] The data server 412 may also be configured to receive data from the patient computing device 110. This may include data entered into the patient program 430 by the patient 1000, or treatment / usage data in the alternative embodiment 7000B described above.

[0247] The data server 412 is also configured to send an electronic message to the patient computing device 110. The message may be in the form of an email, an SMS message, an automated voice message, or a notification within the patient program 430.

[0248] The RPT device 4000 may be configured such that its therapy mode or settings for a particular therapy mode may be changed upon receipt of a corresponding command via its wide-area or local-area network connection. In such an embodiment, the data server 412 may also be configured to send such commands directly to the RPT device 4000 (in embodiment 400) or indirectly to the RPT device 4000, relayed via the patient computing device 110 (in embodiment 7000B).

[0249] The data server 412 may host a process executed by the analysis engine 130, as described in detail below, that is configured to increase or maintain a patient's motivation to continue treatment. Broadly speaking, the process analyzes data from the RPT device 4000 and / or the patient computing device 110 to calculate a treatment quality indicator that indicates the quality of the most recent treatment session. The process then sends the treatment quality indicator to the patient 1000, for example, via a patient program 430 running on the patient computing device 110. The need to increase motivation may be detected by analyzing low-resolution data, and high-resolution data may be obtained to optimize methods of increasing or maintaining patient motivation.

[0250] The patient 1000 perceives the treatment quality indicator as a concise indicator of how their treatment is going. The patient 1000 is thereby motivated to stick with their therapy. It is known that tracking and measuring performance can be a strong motivation for people to achieve their goals, and the treatment quality indicator is used as such a performance measure in the case of respiratory pressure therapy.

[0251] Generally speaking, the level of data that is periodically / routinely sent to the data server 412 is summarized as sufficient to support the patient's information, however in some cases, a higher resolution of data is required to further drill into the problem for an actor such as a healthcare provider or payer, or to provide data back to the manufacturer regarding the performance of a machine. Therefore, the advantage of distinguishing between low resolution data and high resolution data transmission is to prevent data overload that is generally unnecessary, except in special circumstances. The ability to shift the amount of data sent allows the use of more efficient transmission components that do not require the highest level of bandwidth for the system.

[0252] Situations that may trigger higher data resolution may be predetermined by the manufacturer, payer, or healthcare provider. Such situations may also be determined using a rules engine executed by the controller 4230. The rules engine may be determined by a machine learning routine executed by the machine learning engine 180 to recognize when these situations have occurred and request that the relevant high resolution data be sent to a remote external device 4286 (such as a cloud) by the controller 4230.

[0253] The rules engine can perform simple analysis to identify negative trends, alerting the system when a threshold has been breached. Machine learning will be used to understand what a "normal" condition may be for a patient (generating a baseline) and to help identify anomalies in the operation of the RPT device 4000. In these cases, specific high-resolution data may be sent for a specified period of time, such as a few days, or until feedback data from the controller 4230 allows identification that the problem has been resolved. Examples and corresponding high-resolution data may include a high leak trend determined by low-resolution data. This trend exceeding the baseline may result in the sending of high-resolution leak data. Another case may be an increased respiratory rate determined by low-resolution data. Upon detecting an increased respiratory rate, the controller 4230 may send high-resolution respiratory rate, respiratory flow, pressure, and flow limitation data to the external device 4286.

[0254] Another case may be a continuous desaturation (e.g., a low SpO2 value) that can be detected from the low resolution data. Upon detecting an increased respiratory rate, the controller 4230 sends high resolution SpO2, pressure, and flow limitation data to the external device 4286. Another case may be a combination of increased cough, sputum, and respiratory rate that can be detected from the low resolution data. Upon detecting an increased cough, sputum, and respiratory rate, the controller 4230 sends high resolution respiratory rate SpO2 and pressure data to the external device 4286.

[0255] In this example, the low-resolution data that can be sampled by the controller 4230 and selected for low-frequency transmission to the external device 4286 can include SpO2, pulse rate, respiratory events, therapeutic pressure (IPAP), basal pressure (EPAP), leak, minute ventilation, tidal volume, respiratory rate, spontaneous trigger percentage, spontaneous cycle percentage, I: E ratio, inhaler events, sleep state detection, oral leak, last known exacerbation, dyspnea, activity level, sputum production / color, cough, oxygen level released, respiratory pattern, temperature, humidity, air quality, rescue medication use, body temperature, peak expiratory flow, FEV1, or vital capacity. As described above, any or all of the above data types can be set at a low sampling or transmission rate, such as once per minute. The high-resolution data can be the same data with a higher sampling rate (such as greater than once per minute).

[0256] As described above, high resolution data may be constructed in addition to low resolution data. High resolution data may also include types such as respiratory flow, pressure, trigger / cycle events, mask pressure, IPAP, EPAP, leak, respiratory rate, tidal volume, spontaneous trigger percentage, spontaneous cycle percentage, I:E ratio, snoring, flow limitation, pulse rate, SpO2, inspiratory time, average expiratory time of the last 5 breaths, cough, respiratory pattern, activity level, peak expiratory flow, FEV1, vital capacity, and sleep state detection.

[0257] Low or high resolution data may also be obtained by other therapy or sensor devices that may interface with the controller 4230 or the patient computer 110. This data may be combined with or included in the transmission from the device 4000.

[0258] Fig. 9 Shown by Figure 4C Flowchart of a routine executed by controller 4230 in for regulating data transmission. Fig.10 shows the collection used to determine Figure 1A Flowchart 1000 of a routine for collecting and analyzing data on a patient's health condition. Fig. 9 The flowchart in represents example machine-readable instructions for collecting and regulating the transmission of data. Fig. 9 The flowchart in represents example machine-readable instructions for collecting and regulating the transmission of data. Fig.10 The flowchart in represents exemplary machine-readable instructions for collecting and analyzing data based on triggering events for determining health conditions. In this example, the machine-readable instructions include an algorithm for performing the following steps: (a) a processor; (b) a controller; and / or (c) one or more other suitable processing devices. The algorithm can be implemented in software stored on a tangible medium, such as a flash memory, CD-ROM, floppy disk, hard drive, digital video (universal) disk (DVD), or other storage device. However, a person of ordinary skill in the art will readily appreciate that the entire algorithm and / or portions thereof may alternatively be executed by a device other than a processor and / or implemented in firmware or dedicated hardware in a known manner (e.g., by an application specific integrated circuit [ASIC], a programmable logic device [PLD], a field programmable logic device [FPLD], a field programmable logic device [FPLD], a programmable gate array [FPGA], discrete logic, etc.). For example, any or all components of the interface may be implemented by software, hardware, and / or firmware. Moreover, some or all of the machine-readable instructions represented by the flowchart may be implemented manually. In addition, although reference is made to Fig. 9 and 10 The flowchart shown in the embodiment of the present invention describes an exemplary algorithm, but it will be readily understood by those skilled in the art that many other methods of implementing the exemplary machine-readable instructions may be used alternatively. For example, the execution order of the blocks may be changed, and / or some of the blocks described may be changed, eliminated, or combined.

[0259] about Fig. 9 , the patient uses a connected device such as Fig. 8A The RPT device 4000 (900) in FIG. 4000 collects various data which may be low resolution data or high resolution data when in use. As described above, the collected data is stored in the local memory 4260 on the device 4000. The low resolution data and summary statistics compiled by the device are sent to an external system, such as Fig. 8A The low-resolution data is analyzed for trends and events using an external application that may be executed by a server on the cloud, such as server 412 or server 420 (904).

[0260] As described above, a trend or event can be identified by signaling an application of an abnormal event associated with a patient (906). Then, a request is sent to the device 4000 to send high-resolution data (908). In this example, the high-resolution data is defined based on the detected trend or event. Further, in this example, the high-resolution data is sent within a predetermined amount of time, such as a few days. The collected high-resolution data is sent to an external device, such as a server 412 (910). The cloud 7090 allows access to the high-resolution data from authorized actors, such as healthcare professionals or payers, through a web-based interface (912).

[0261] Fig.10 A flow chart of a collection and analysis routine performed by the system 100 for determining a health condition is shown. The system first monitors data collected from the RPT device 4000 in a low-resolution mode (1050). In this example, the data analysis engine 130 collects the low-resolution data and analyzes the data for a triggering event, such as a change in the patient's condition. As described above, the triggering event can be a predetermined rule or a machine learning-based model or algorithm. The analysis engine 130 determines whether a triggering event has occurred based on the data collected from the low-resolution mode (1052). If a triggering event is not detected, the routine continues to collect data at a low resolution (1050).

[0262] If a trigger event has been detected (1052), the health analysis engine 130 confirms the trigger event (1054). The confirmation of the trigger event may include collecting additional types of data or following set rules to cross-check the occurrence of the trigger event. Such collection may be performed on the application on the mobile device 110. The analysis engine 130 then determines whether the trigger event is confirmed (1056). If the trigger event is not confirmed, the routine continues to collect data at a low resolution (1052). If the trigger event is confirmed, the analysis engine 130 controls the RPT device 4000 and other related sources to increase data collection to a high resolution (1058). As described above, additional data may come from the patient health monitor 120, other sensors, and other databases. The data analysis engine 130 then analyzes the collected data to determine a health condition (1060). The health condition analysis may include determining the severity of the trigger condition. The collected analysis is then stored (1062) for further analysis and other purposes, such as building a training set for the machine learning engine 180. The health status analysis engine 130 then determines and implements a resolution to the detected triggering event (1064). For example, this may involve notifying the patient in a less severe triggering event or notifying a healthcare professional in a more severe triggering event. Other examples may be adjusting the settings of the RPT device 4000 and automatic adjustment of therapy or medication. Once the data analysis engine 130 determines that the triggering event has been resolved, it returns to collecting data at a low resolution (1050).

[0263] In terms of service delivery, this can include automatically creating a health care facility appointment, and booking transportation to the health care facility (e.g., taxi, autonomous vehicle, ambulance). Such services can be provided by process 432 of HCP server 416 alone or in conjunction with processes executed by support server 418.

[0264] A system that collects data from a respiratory therapy device to analyze health status has many benefits. Benefits to the exemplary patient 1000 include increased quality of life and reduced hospitalizations, maximizing long-term adherence (LTA), the ability to interface with applications executed by the mobile device 110, and the ability to contact emergency services if abnormal data is detected. Quality of life can include aspects of physical, mental, and social functioning, and can include a sense of overall life satisfaction (or lack thereof).

[0265] Benefits to healthcare providers, such as integrated care providers, include understanding the evolution of co-morbidities, thereby keeping patients out of the hospital, personalization of the therapy experience, and direct appeal to patients / customers for out-of-pocket purchases.

[0266] 4.11 Glossary

[0267] For purposes of this technical disclosure, one or more of the following definitions may apply in certain forms of the technology. In other forms of the technology, alternative definitions may apply.

[0268] Air: In some forms of the present technology, air may be considered to mean atmospheric air, and in other forms of the present technology, air may be considered to mean some other combination of breathable gases, such as atmospheric air enriched with oxygen.

[0269] Environment: In certain forms of the present technology, the term environment can have the meaning of (i) external to the treatment system or patient, and (ii) directly surrounding the treatment system or patient.

[0270] For example, the ambient humidity relative to the humidifier may be the humidity of the air directly surrounding the humidifier, such as the humidity within the room that the patient is sleeping in. This ambient humidity may be different from the humidity outside the room that the patient is sleeping in.

[0271] In another example, ambient pressure may be the pressure immediately surrounding or external to the body.

[0272] In some forms, ambient (e.g., acoustic) noise may be considered to be the background noise level in the room the patient is in, in addition to noise generated, for example, by the RPT device or from a mask or patient interface. Ambient noise may be generated by sound sources outside the room.

[0273] Automatic Positive Airway Pressure (APAP) Therapy: CPAP therapy in which therapy pressure is automatically adjusted between minimum and maximum limits, e.g., from breath to breath, based on the presence or absence of an indication of an SDB event.

[0274] Continuous Positive Airway Pressure (CPAP) therapy: A breathing pressure therapy in which the therapy pressure can be approximately constant throughout the patient's breathing cycle. In some forms, the pressure at the airway entrance will be slightly higher during exhalation and slightly lower during inspiration. In some forms, the pressure will vary between different breathing cycles of the patient, for example, increasing in response to detecting an indication of partial upper airway obstruction, and decreasing when there is no indication of partial upper airway obstruction.

[0275] Flow: The volume (or mass) of air delivered per unit time. Flow may refer to an instantaneous quantity. In some cases, reference to flow will be to a scalar quantity, i.e., a quantity having only magnitude. In other cases, reference to flow will be to a vector quantity, i.e., a quantity having both magnitude and direction. Flow may be given the symbol Q. "Flow" is sometimes shortened to simply "flow" or "airflow."

[0276] In the example of a patient breathing, the flow may be nominally positive for the inspiratory portion of the patient's breathing cycle, and therefore negative for the expiratory portion of the patient's breathing cycle. The device flow Qd is the flow of air leaving the RPT device. The total flow Qt is the flow of air and any supplemental gas that reaches the patient interface via the air circuit. The ventilation flow Qv is the flow of air leaving the vent to allow flushing of exhaled gases. The leakage flow Ql is the leakage flow from the patient interface system or elsewhere. The respiratory flow Qr is the flow of air received into the patient's respiratory system.

[0277] Humidifier: The term humidifier shall be deemed to refer to a humidifying device constructed and arranged or configured with a physical structure capable of providing therapeutically beneficial amounts of water (H2O) vapor to an air flow to improve a patient's medical respiratory condition.

[0278] Leakage: The term leakage is to be understood as undesired air flow. In an example, leakage may occur due to an incomplete seal between the mask and the patient's face. In another example, leakage may occur in the return bend to the surrounding environment.

[0279] Noise, conducted (acoustic): Conducted noise in this document refers to the noise brought to the patient through the pneumatic path (such as the air circuit and patient interface and the air therein). In one form, conducted noise can be quantified by measuring the sound pressure level at the end of the air circuit.

[0280] Noise, radiated (acoustic): Radiated noise in this document refers to the noise that is brought to the patient through the surrounding air. In one form, radiated noise can be quantified by measuring the sound power / pressure level of the object in question according to ISO 3744.

[0281] Noise, Ventilation (Acoustic): Ventilation noise in this document refers to the noise generated by the flow of air through any vent, such as the vent holes of a patient interface.

[0282] Patient: A person, whether or not they have a respiratory condition.

[0283] Pressure: Force per unit area. Pressure can be measured in a range of units, including cmH2O, gf / cm 2 and hectopascals. 1 cmH20 is equal to 1 g-f / cm2 and is approximately 0.98 hectopascals (1 hectopascal = 100 Pa = 100 N / m 2 =1 mbar-0.001 atm). In this specification, unless otherwise stated, pressure is given in cmH2O.

[0284] The pressure in the patient interface is given the symbol Pm, while the treatment pressure, which represents the target value achieved by the interface pressure Pm at the current moment, is given the symbol Pt.

[0285] Respiratory Pressure Therapy (RPT): The application of a supply of air to the airway entrance at a therapeutic pressure that is typically positive relative to atmosphere.

[0286] Ventilator: A mechanical device that provides pressure support to a patient to perform some or all of the work of breathing.

[0287] Silicone or Silicone Elastomer: Synthetic rubber. In this specification, references to silicone refer to liquid silicone rubber (LSR) or compression molded silicone rubber (CMSR). One form of commercially available LSR is SILASTIC (included in the range of products sold under this trademark), which is manufactured by Dow Corning. Another manufacturer of LSR is Wacker. Unless otherwise specified to the contrary, exemplary forms of LSR have a Shore A (or Type A) indentation hardness in the range of about 35 to about 45 as measured using ASTM D2240.

[0288] Polycarbonate: A transparent thermoplastic polymer of bisphenol A carbonate.

[0289] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent Office patent file or records, but otherwise reserves all copyright rights whatsoever.

[0290] Unless the context clearly indicates and provides a numerical range, it should be understood that each intervening value between the upper and lower limits of the range, to one-tenth of the unit of the lower limit, and any other such value or intervening value in the range are broadly included in the present technology. The upper and lower limits of these intermediate ranges may be independently included in the intermediate ranges and are also included in the present technology, but are subject to any explicitly excluded limits in the range. In the case where the range includes one or both of the limiting values, the present technology also includes ranges excluding either or both of those included limiting values.

[0291] Furthermore, where a value or values ​​are used herein as part of implementation as part of the present technology, it should be understood that such values ​​may be approximate unless otherwise indicated and that such values ​​may be used to any appropriate number of significant digits to the extent permitted or required by practical technical implementation.

[0292] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the invention belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present technology, a limited number of representative methods and materials are described herein.

[0293] When a specific material is identified for use in a component of construction, obvious alternative materials with similar properties are used as substitutes. In addition, unless otherwise specified, any and all components described herein are understood to be capable of being manufactured and thus can be manufactured together or separately.

[0294] It must be noted that as used herein and the appended claims, the singular forms "a," "an," and "the" include plural equivalents unless the context clearly dictates otherwise.

[0295] All publications mentioned herein are incorporated herein in their entirety by reference, to disclose and describe methods and / or materials as the subject of those publications. Providing the publications discussed herein is only for the disclosures before the filing date of the present application. Any content herein should not be construed as admitting that the present technology is not entitled to the priority of these publications due to previous inventions. In addition, the publication date provided may be different from the actual publication date, which may need to be confirmed separately.

[0296] The subject headings used in the detailed description are for the convenience of the reader and should not be used to limit the subject matter that can be found in the disclosure or claims as a whole. The subject headings should not be used to interpret the scope of the claims or the limitations of the claims.

[0297] Although the present technology has been described herein with reference to specific embodiments, it should be understood that these embodiments only illustrate the principles and applications of the present technology. In some cases, terms and symbols may imply specific details that are not required for practicing the present technology. For example, although the terms "first" and "second" may be used, unless otherwise specified, they are not intended to represent an arbitrary order, but may be used to distinguish different elements. In addition, although the process steps in the method may be described or illustrated in a certain order, this order is not required. Those skilled in the art will recognize that this order may be modified, and / or aspects of the order may be performed simultaneously or even synchronously.

[0298] It is therefore to be understood that numerous modifications may be made to the exemplary embodiments and that other arrangements may be devised without departing from the spirit and scope of the present technology.

Claims

1. A patient treatment device comprising: an air pressure generator for generating an air flow to provide respiratory pressure therapy to a patient; a controller coupled to the air pressure generator; Memory; a first sensor, wherein the first sensor is configured to collect a first type of data from the patient during normal operation of the air pressure generator and the collected data is stored in the memory; a transmitter, wherein the transmitter is controlled by the controller to transmit low-resolution data or high-resolution data to an external system, wherein the low-resolution data is generated during normal operation and transmitted to the external system; and a second sensor coupled to the controller, wherein the second sensor is configured to collect a second type of data different from the first type of data, and wherein the controller operates the second sensor based on the occurrence of an event detected based on the transmitted low-resolution data, wherein the transmitter is controlled by the controller to transmit high-resolution data including the first type of low-resolution data sampled at a higher rate and the second type of data based on the detected event.

2. A patient treatment device according to claim 1, wherein: The patient treatment device is a respiratory pressure therapy device.

3. A patient treatment device according to claim 2, wherein: The first sensor or the second sensor is one of a flow sensor or a pressure sensor.

4. A patient treatment device according to claim 2, wherein: The respiratory pressure therapy device is configured to store therapy data from a respiratory pressure therapy session delivered to a patient in the memory, wherein the therapy data for the respiratory pressure therapy session includes settings of the respiratory pressure therapy device and therapy variable data representing one or more variables of the respiratory pressure therapy during the entire respiratory pressure therapy session.

5. The patient treatment device of claim 2, wherein: The external system includes a data server, and wherein the respiratory pressure therapy device sends data according to a pull model, whereby the respiratory pressure therapy device sends the data in response to a query from the data server, or wherein the respiratory pressure therapy device sends the data according to a push model, whereby the respiratory pressure therapy device sends the data to the data server after a respiratory pressure therapy session.

6. The patient treatment device of claim 1, wherein: The external system includes a data server; wherein the patient treatment device is a respiratory pressure treatment device configured to send data to the data server via a patient computing device.

7. A patient treatment device according to claim 6, wherein: The data server is further configured to receive data entered by the patient into a patient program of the patient computing device.

8. The patient treatment device of claim 1, wherein: The external system is a personal computer, a mobile phone, a tablet computer or a remote control.

9. The patient treatment device of claim 5, wherein: The external system is configured to receive treatment data from a plurality of patient treatment devices, wherein the external system comprises a data server, and wherein the treatment data received from each of the patient treatment devices is stored and indexed by the data server so as to be uniquely associated with the corresponding patient treatment device.

10. The patient treatment device of claim 1, wherein: The detected events are based on long term analysis of collected low resolution data.

11. The patient treatment device of claim 1, wherein: The external system includes a health analysis engine operable to determine a severity of the detected event and adjust a response action to the patient based on the determined severity.

12. The patient treatment device of claim 1, wherein: Operation of the patient treatment device is adjusted in response to the detected event.

13. The patient treatment device of claim 11, wherein: The health analytics engine is operable to request subjective input data entered by the patient to verify detection of the detected event.

14. The patient treatment device of claim 1, wherein: The low-resolution data includes any one or any combination of SpO2, pulse rate, respiratory events, therapy pressure, basal pressure, leak, minute ventilation, tidal volume, respiratory rate, spontaneous trigger percentage, spontaneous cycle percentage, I:E ratio, inhaler events, sleep state detection, oral leak, last known exacerbation, dyspnea, activity level, sputum production / color, cough, released oxygen level, respiratory pattern, temperature, humidity, air quality, rescue medication use, body temperature, peak expiratory flow, FEV1 and vital capacity data types.

15. The patient treatment device of claim 1, wherein: The high-resolution data includes any one or any combination of respiratory flow, pressure, trigger / cycle events, mask pressure, therapy pressure, basal pressure, leak, respiratory rate, tidal volume, spontaneous trigger percentage, spontaneous cycle percentage, I:E ratio, snoring, flow limitation, pulse rate, SpO2, inspiratory time, average expiratory time of the last 5 breaths, cough, respiratory morphology, activity level, peak expiratory flow, FEV1, vital capacity and sleep state detection data types.

16. A method for modulating transmission of patient data from a patient treatment device to an external system, the patient treatment device comprising a first sensor coupled to a patient, a second sensor coupled to the patient, an air pressure generator for generating an air flow, and a transmitter, the method comprising: collecting a first type of data from the first sensor; transmitting low-resolution data to the external system via a transmitter during normal operation based on the first type of data collected by the first sensor during normal operation of the air pressure generator; determining an occurrence of an event based on the low-resolution data; Based on the determined event occurrence, operating the second sensor to collect a second type of data different from the first type of data; as well as The transmitter is changed to transmit high-resolution data based on the determined event, wherein the high-resolution data includes the first type of data sampled at a higher rate and the second type of data.

17. The method according to claim 16, wherein: The first sensor or the second sensor is inside or outside the respiratory pressure therapy device.

18. The method according to claim 16, wherein: The first sensor or the second sensor is a non-contact sensor.

19. The method according to claim 16, wherein: A controller is configured to receive an input signal from the sensor and provide an output signal to the transmitter.

20. The method according to claim 19, wherein: The low-resolution data and the high-resolution data are sampled by the controller.

21. The method according to claim 20, wherein: The low-resolution data is sampled once per minute or less, and the high-resolution data is sampled more than once per minute.

22. The method according to claim 19, wherein: The high resolution data is triggered using a rules engine executed by the controller.

23. The method according to claim 16, wherein: The low-resolution data includes any one or any combination of SpO2, pulse rate, respiratory events, therapy pressure, basal pressure, leak, minute ventilation, tidal volume, respiratory rate, spontaneous trigger percentage, spontaneous cycle percentage, I:E ratio, inhaler events, sleep state detection, oral leak, last known exacerbation, dyspnea, activity level, sputum production / color, cough, released oxygen level, respiratory pattern, temperature, humidity, air quality, rescue medication use, body temperature, peak expiratory flow, FEV1 and vital capacity data types.

24. The method according to claim 16, wherein: The high-resolution data includes any one or any combination of respiratory flow, pressure, trigger / cycle events, mask pressure, therapy pressure, basal pressure, leak, respiratory rate, tidal volume, spontaneous trigger percentage, spontaneous cycle percentage, I:E ratio, snoring, flow limitation, pulse rate, SpO2, inspiratory time, average expiratory time of the last 5 breaths, cough, respiratory morphology, activity level, peak expiratory flow, FEV1, vital capacity and sleep state detection data types.

25. The method of claim 16, wherein: The treatment device comprises a pre-processing module, a treatment engine module and a treatment control module, and wherein the data is generated by the pre-processing module or the treatment engine module.

26. The method of claim 16, wherein: The low resolution data is analyzed by an external application executed by the external system to determine the occurrence of the event.

27. A system for modulating the transmission of patient data to an external system, the system comprising: A patient treatment device comprising a controller, an air pressure generator for generating an air flow, a first sensor coupled to a patient, a second sensor coupled to the patient, a memory, and a transmitter, wherein the first sensor collects a first type of data from the patient during normal operation of the air pressure generator, and wherein the collected data is stored in the memory; and wherein the transmitter is configured by the controller to transmit low-resolution data or high-resolution data to the external system based on the first type of data collected by the first sensor, wherein the low-resolution data is transmitted during normal operation of the patient treatment device, and wherein the high-resolution data is transmitted based on the occurrence of an event detected based on the low-resolution data, and wherein the high-resolution data includes the first type of data sampled at a higher rate, and the second type of data is transmitted to the external system when the occurrence of an event is detected; and wherein the controller is further operable to control the air flow generator to generate air flow at a changed rate in response to a determined event determined based on the low-resolution data.