Data Consent Storage and Management System and Method

Abstract

A system and method for managing consent to share data from user devices is disclosed. In some embodiments, the system stores a user identifier referenced to the user's individual consent settings. The consent settings may include the type of data, the data-generating devices the user consents to, the types of third parties the user consents to sharing data with, and other consent settings. Third parties may communicate with the system to determine whether the user consented to sharing data.

Description

Technical Field

[0001] This technology relates to the sharing and consent of data and the management of data flows between various entities and devices.

Background Art

[0002] Devices such as various medical devices and wearables can generate user data. Since the user's data (or aggregating data for multiple users) can be valuable to third-party consumers, third parties or data consumers may be interested in obtaining that data. However, the user (or the patient described herein) needs to consent to their data being shared and used by third parties.

[0003] Devices that can generate user data include respiratory therapy devices, wearables, mobile devices, and other connected devices. These can include various respiratory therapy devices including CPAP devices and related software, as well as similar devices.

[0004] <The Human Respiratory System and Its Diseases> The body's respiratory system facilitates gas exchange. The nose and mouth form the entrance to the patient's airway.

[0005] These airways include a series of branching tubes that become narrower, shorter, and more numerous as they progress deeper into the lungs. The primary function of the lungs is gas exchange, taking oxygen from the air into the venous blood and expelling carbon dioxide. The trachea divides into the right and left main bronchi, which further divide and ultimately become the terminal bronchioles. The bronchioles constitute the airways for conduction and are not involved in gas exchange. As the airways further divide, they become respiratory bronchioles and ultimately alveoli. Gas exchange occurs in the alveolar region of the lungs, which is referred to as the respiratory region. See, e.g., "Respiratory Physiology," by John B. West, Lippincott Williams & Wilkins, 9th edition published 2012. See, e.g., "Respiratory Physiology," by John B. West, Lippincott Williams & Wilkins, 9th edition published 2012.

[0006] A range of respiratory diseases exist. Certain diseases can be characterized by specific symptoms (e.g., apnea, hypopnea, and hyperventilation).

[0007] Examples of respiratory diseases include obstructive sleep apnea (OSA), Cheyne-Stokes respiration (CSR), respiratory insufficiency, obesity hypoventilation syndrome (OHS), chronic obstructive pulmonary disease (COPD), neuromuscular disease (NMD), and chest wall disease.

[0008] <Therapy> A variety of therapies (e.g., continuous positive airway pressure (CPAP) therapy, non-invasive ventilation (NIV), and invasive ventilation (IV)) are used for the treatment of one or more of the above respiratory diseases.

[0009] <Respiratory pressure therapy> Continuous positive airway pressure (CPAP) therapy is used in the treatment of obstructive sleep apnea (OSA). As its mechanism of action, for example, by pushing the soft palate and tongue to advance or retract toward the posterior oropharyngeal wall, continuous positive pressure ventilation therapy functions as an air sprint, thereby preventing upper airway closure. Since the treatment of OSA by CPAP therapy can be spontaneous, if such a patient notices one or more of the following regarding the device used for treatment delivery, the patient may choose not to comply with the treatment: discomfort, difficulty of use, high cost, lack of aesthetic appeal.

[0010] Non-invasive ventilation (NIV) provides ventilation assistance to a patient through the upper airway and performs part or all of the respiratory function to assist the patient's breathing and / or maintain an appropriate oxygen level in the body. The ventilation assistance is provided via a non-invasive patient interface. NIV is used in the treatment of CSR and respiratory failure in forms such as OHS, COPD, NMD, and chest wall disorders. In some forms, the comfort and effectiveness of these treatments can be improved.

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

[0012] <Flow therapy> In all respiratory therapies, the delivery of a defined therapeutic pressure is not necessarily intended. In some respiratory therapies, perhaps the delivery of a defined respiratory volume is intended by targeting a flow profile over a target duration. In other cases, the interface to the patient's airway is "open" (seal released), and the respiratory therapy can only be used as an aid to the patient's own spontaneous breathing. In one embodiment, high-flow therapy (HFT) is the provision of a continuous, heated, humidified air stream at a "therapy flow rate" that is maintained substantially constant throughout the respiratory cycle through a non-sealed or open patient interface. The therapy flow rate is nominally set to exceed the patient's peak inspiratory flow rate. HFT is used for the treatment of OSA, CSR, COPD, and other respiratory disorders. As one mechanism of action, providing high-flow air to the airway inlet improves ventilation efficiency because it enables the flushing or washing out of CO2 exhaled from the patient's anatomic dead space. For this reason, HFT is sometimes referred to as dead space therapy (DST). In other flow therapies, the therapy flow rate can follow a profile that varies over the respiratory cycle.

[0013] Another form of flow therapy is long-term oxygen therapy (LTOT) or oxygen supplementation therapy. A physician may prescribe that a continuous flow of oxygen-enriched gas be delivered to the patient's airway at a specified flow rate (e.g., 1 liter per minute (LPM), 2 LPM, 3 LPM) at a specified oxygen concentration (oxygen fraction in ambient air is 21% - 100%).

[0014] <Supplemental Oxygen> In the case of certain patients, a combination of oxygen therapy and respiratory pressure therapy or HFT can be obtained by adding supplemental oxygen to a pressurized air stream. When oxygen is added to respiratory pressure therapy, this is called RPT with supplemental oxygen. When oxygen is added to HFT, the resulting therapy is called HFT with supplemental oxygen.

[0015] <Therapy System> These respiratory therapies can be provided by a treatment system or device. Such systems and devices can also be used for screening, diagnosing, or monitoring without treating the disease.

[0016] A respiratory treatment system can include a respiratory pressure treatment device (RPT device), an air circuit, a humidifier, a patient interface, an oxygen source for respiration, and data management.

[0017] <Patient interface> The patient interface can be used to provide an interface to the breathing apparatus to the wearer, for example, by providing an air flow to the airway inlet. The air flow can be provided via a mask to the nose and / or mouth, a tube to the mouth, or a tracheostomy tube to the patient's trachea. Depending on the therapy applied, the patient interface forms a seal with the area of the patient's face, thereby promoting gas delivery at a sufficient distributed pressure together with the ambient pressure for therapy execution (e.g., at a positive pressure of about 10 cmH2O relative to the ambient pressure). In other treatment modalities such as oxygen delivery, the patient interface may not include a seal sufficient to promote the delivery of gas supply to the airway at a positive pressure of about 10 cmH2O.

[0018] <Respiratory pressure treatment (RPT) device> The respiratory pressure treatment (RPT) device can be used individually for the delivery of one or more of the above-mentioned treatments, or as part of a system, for example, by operating the device to generate an air delivery flow to the interface to the airway. The air flow can be pressure-controlled (for respiratory pressure treatment) or flow-controlled (for flow treatment such as HFT). Therefore, the RPT device can also function as a flow treatment device. Examples of RPT devices include CPAP devices and ventilators.

[0019] Air pressure generators are known in a wide range of applications (e.g., industrial-scale ventilation systems). However, air pressure generators for medical use have specific requirements that cannot be satisfied by more general air pressure generators (e.g., the reliability, size, and weight requirements of medical devices). In addition, even devices designed for medical treatment may not be free from defects related to one or more of comfort, noise, ease of use, effectiveness, size, weight, manufacturability, cost, and reliability.

[0020] As an example of the special requirements of certain RPT devices, there is acoustic noise.

[0021] One known RPT device used in the treatment of sleep apnea is the S9 sleep therapy system (manufacturer: ResMed Limited). Another example of an RPT device is a ventilator. In the case of ventilators (e.g., the ResMed Stellar® series of adult and pediatric ventilators), it can provide assistance for invasive and non-invasive dependent breathing for patients over a certain range for the treatment of multiple conditions (non-limiting examples include NMD, OHS, and COPD).

[0022] The ResMed Elisee® 150 ventilator and the ResMed VSIII® ventilator can provide assistance for invasive and non-invasive dependent breathing suitable for adult or pediatric patients for the treatment of multiple conditions. With these ventilators, volume ventilation modes and pressure ventilation modes using single or double limb circuits can be obtained. RPT devices typically include a pressure generator (e.g., an electric blower or a compressed gas reservoir) and are configured to supply an air flow to the patient's airway. In some cases, the air flow can be supplied to the patient's airway at positive pressure. The outlet of the RPT device is connected to the patient interface as described above via an air circuit.

[0023] <Data Management> For clinical reasons, data may be obtained to determine whether a patient for whom respiratory therapy has been prescribed is "compliant" (e.g., whether the patient is following one or more "compliance rules" with their RPT device). As an example of a compliance rule for CPAP therapy, for a patient to be considered compliant, the patient must use the RPT device for at least 4 hours per night for at least 21 days out of 30 consecutive days. To determine a patient's compliance, a provider of the RPT device (e.g., a healthcare provider) may obtain data describing the patient's treatment with the RPT device manually, calculate the usage rate over a given period, and compare this to the compliance rule. If the healthcare provider determines that the patient has used their RPT device in accordance with the compliance rule, the healthcare provider may notify a third party that the patient is compliant.

[0024] In a patient's treatment, there may be other ways to benefit from communicating treatment data to a third party or an external system.

[0025] In the case of existing processes for communicating and managing such data, one or more of high cost, time consumption, and susceptibility to errors may occur.

[0026] <Ventilation technology> Some forms of treatment systems may include a ventilation section for expelling exhaled carbon dioxide. This ventilation section may enable gas flow from the internal space (e.g., the plenum chamber) of the patient interface to the outside (e.g., the surroundings) of the patient interface.

[0027] <Screening, diagnostic systems, and monitoring systems> A polysomnogram (PSG) is a conventional system for the diagnosis and monitoring of cardiopulmonary diseases, and typically requires specialized clinical staff for system application in many cases. In PSG, typically 15 to 20 contact sensors are placed on the human body to record various body signals (e.g., electroencephalogram (EEG), electrocardiogram (ECG), electrooculogram recording (EOG), electromyography (EMG)). For PSG of sleep disordered breathing, patients had to be observed in a specialized hospital for two nights. That is, the first night was for pure diagnosis, and the second night was necessary for titration of treatment parameters by a clinician. Therefore, PSG is costly and has low convenience. Screening / diagnosis / monitoring of sleep disordered breathing is particularly unsuitable at home.

[0028] Generally, screening and diagnosis are to identify a disease based on its signs and symptoms. Usually, screening gives a true / false result indicating whether the patient's SDB warrants further investigation, while diagnosis often provides clinically actionable information. Screening and diagnosis tend to be one-time procedures, whereas monitoring the course of a disease can be continued indefinitely. Some screening / diagnosis systems are only suitable for screening / diagnosis, while some can also be used for monitoring.

[0029] Clinical experts can appropriately perform patient screening, diagnosis, or monitoring based on visual observation of PSG signals. However, there are situations where there is no clinical expert or payment to a clinical expert is not possible. Opinions of clinical experts may differ regarding a patient's condition. Furthermore, some clinical experts may apply different criteria depending on the time. Summary of the Invention Problems to be Solved by the Invention

[0030] This technology aims to manage a user's data and consent to a device for a third party.

Means for Solving the Problem

[0031] A first aspect of the present technology relates to various devices and software for generating user data that a user can consent to share. These include devices, methods, and software used for screening, diagnosing, monitoring, improving, treating, or preventing respiratory diseases.

[0032] One aspect of a particular form of the present technology is to manage consent and data flow for data related to methods and / or devices for improving patient compliance with respiratory therapy.

[0033] One form of the present technology includes a server, a database, and software for managing consent of a user device and data generated by the user device that can be sent to a third party. Currently, when a user signs up for a new service that requires sharing data to set up an account, the user needs to review and consent to a long agreement regarding sharing of their data. It is unlikely that users or patients will read these agreements, and once consented, there is little or no way to revoke it. Furthermore, since users have little or no way to monetize their valuable data, much of the data, such as valuable patient data of users, ultimately ends up not being shared without being monetized for the users. In addition, it is rare for users to understand the consent terms and they have no means to select the terms they consent to, or to select the parties, end users, or subset of methods to whom the data will be shared.

[0034] Therefore, there is no system and method that effectively manages user consent to share user data from devices, software programs, accounts, and other data sources with third-party data consumers. Thus, the inventor(s) have developed a system and method for assisting in the management of consent and / or data flow between a user's device and third-party data consumers.

[0035] In some embodiments, this may include a consent broker server and database that stores unique identifiers representing each user whose individual consent settings are referenced. This consent setting may include types of data, data generating devices the user consents to, types of third parties the user consents to share data with, and other consent settings. This enables a third party to communicate with the consent broker to determine whether the user has consented to share data. The third party can then save that consent and may be able to download data directly from the user and use that data based on the conditions to which the user has consented.

[0036] In another aspect of one form of this technology, the broker may be able to act as an intermediary for data transfers that occur between a third party and a user device. For example, the consent broker may present an API address to the third party receiving the data and may be able to manage the data flow between the user and the third party. This enables the consent broker to easily disconnect access to the API if the user decides to revoke consent.

[0037] In another aspect of one form of the present technology, a broker may download and store data from multiple different users to create a data warehouse and a data marketplace for third parties to download data. For example, a third party may send a request to the broker for a certain type of data for a certain application. The broker may then query the database to determine how much of that type of data is available for that application and may reply with the market price to that third party. In response, the third party may then agree to receive the data at that price, and the broker may be able to send that data to the third party.

[0038] The methods, systems, devices, and apparatuses described can be embodied to improve the functions in a processor (e.g., the functions of a processor of a special-purpose computer, a respiratory monitor, and / or a respiratory therapy device). Further, the methods, systems, devices, and apparatuses described enable improvements in the technical field of the automatic management, monitoring, and / or treatment of respiratory conditions (e.g., sleep disordered breathing).

[0039] Of course, some of the above aspects may form sub-aspects of the present technology. Also, various combinations of one of the diverse sub-aspects and / or aspects can be made, which may also constitute further aspects or sub-aspects of the present technology.

[0040] Other features of the present technology will become apparent in view of the information contained in the following detailed description, summary, drawings, and claims.

[0041] The present technology is illustrated, by way of example and not limitation, in the accompanying drawings. In the drawings, like reference numerals include the following like elements.

Brief Description of the Drawings

[0042] <Treatment System>

Figure 1A

Figure 1B

Figure 1C

Figure 2A

Figure 3A

Figure 4A

Figure 4B

Figure 5A

Figure 5B

Figure 6A

Figure 7A

Figure 7B

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

DETAILED DESCRIPTION OF THE INVENTION

[0043] Before further describing the present technology in detail, it should be understood that the present technology is not limited to the specific embodiments that may be described herein. It should also be understood that the terms used in the present disclosure are for the purpose of describing the specific embodiments described herein and are not limiting.

[0044] The following description is provided in relation to various embodiments that may share one or more common characteristics and / or features. It should be understood that one or more features of any one embodiment may be combined with one or more features of another embodiment or other embodiments. Additionally, any single feature or combination of features in any of these embodiments may constitute a further embodiment.

[0045] <Treatment method> In one form, the present technology includes a method for treating a respiratory disease. The method includes the step of applying positive pressure to the inlet of the airway of patient 1000.

[0046] In certain embodiments of the present technology, the air supply at positive pressure is provided to the nasal passage of the patient via one or both of the nostrils.

[0047] In certain embodiments of the present technology, mouth breathing is restricted, limited, or prevented.

[0048] <Treatment system> In one form, the present technology includes an apparatus or device for the treatment of a respiratory disorder. The apparatus or device may include an RPT device 4000 that supplies pressurized air to patient 1000 via the air circuit 4170 of patient interface 3000 or 3800.

[0049] <Patient interface> A non-invasive patient interface 3000 according to one aspect of the present technology includes a seal-forming structure 3100, a plenum chamber 3200, a positioning and stabilization structure 3300, a ventilation portion 3400, one form of connection port 3600 for connection to an air circuit 4170, and a functional aspect of a forehead support 3700. In some forms, the functional aspect 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 inlet of the patient's airway so as to facilitate the supply of air at positive pressure to the airway.

[0050] The non-sealing patient interface 3800 is in the form of a nasal cannula including nasal prongs 3810a and 3810b, which can deliver air to each nostril of the patient 1000. Such nasal prongs often do not form a seal with the inner or outer skin surface of the nostril. Air to the nasal prongs is delivered from one or more air supply lumens 3820a and 3820b. These are connected to the nasal cannula 3800. The lumens 3820a and 3820b extend from the nasal cannula 3800, and the nasal cannula 3800 extends to an RT device that generates an air flow at a high flow rate. The non-sealing patient interface 3800 is provided with a "ventilation portion" through which excess air flow escapes to the atmosphere. This "ventilation hole" is a passage between the ends of the prongs 3810a and 3810b of the cannula 3800 and extends to the atmosphere through the patient's nostrils.

[0051] <RPT device> An 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 (e.g., any of the methods described herein, whether in whole or in part). The RPT device 4000 may be configured to generate an air flow to be delivered to a patient's airway for the treatment of one or more of the respiratory states described anywhere in this document, for example.

[0052] <RPT Device Electrical Component> <Input Device> 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 that enable a human to interact with the device. The buttons, switches, or dials can be physical devices or software devices that can be accessed via a touch screen. The buttons, switches, or dials may be physically connected to the external housing 4010 in one form, or may wirelessly communicate with a receiver electrically connected to the central controller 4230 in another form.

[0053] In one form, the input device 4220 can be constructed and arranged to enable a human to select values and / or menu options.

[0054] <Central Controller> In one form of the present technology, the central controller 4230 is one or more processors suitable for controlling the RPT device 4000.

[0055] Suitable processors can include processors based on the ARM® Cortex®-M processors from ARM® Holdings, such as the x86 INTEL® processors (e.g., the STM32® series of microcontrollers from STMicroelectronics®). In certain alternative forms of the present technology, 32-bit RISC CPUs (e.g., the STR9® series of microcontrollers from STMicroelectronics®) or 16-bit RISC CPUs (e.g., processors from the MSP430® family of microcontrollers manufactured by TEXAS INSTRUMENTS®) may also be suitable.

[0056] In one form of the present technology, the central controller 4230 is a dedicated electronic circuit.

[0057] In one form, the central controller 4230 is an application specific integrated circuit. In another form, the central controller 4230 includes discrete electronic components.

[0058] The central controller 4230 may be configured to receive input signal(s) from one or more transducers 4270, one or more input devices 4220, and the humidifier 5000.

[0059] The central controller 4230 may be configured to provide output signal(s) to one or more of the output device 4290, the therapy device controller 4240, the data communication interface 4280, and the humidifier 5000.

[0060] In some forms of the present technology, the central controller 4230 is configured to embody one or more of the methods described herein (e.g., one or more algorithms 4300 expressed as a computer program recorded in a non-transitory computer-readable recording medium (e.g., the 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 of the methods may be performed by remotely located devices. For example, a remotely located device may determine ventilator control settings or detect respiratory related events by analyzing recorded data (e.g., from any of the sensors described herein).

[0061] <Clock> The RPT device 4000 may include a clock 4232 connected to the central controller 4230.

[0062] <Therapy Device Controller> In one form of the present technology, the therapy device controller 4240 is the therapy control module 4330 and forms part of the algorithm 4300 executed by the central controller 4230.

[0063] In one form of the present technology, the treatment device controller 4240 is a dedicated motor control integrated circuit. For example, in one form, an MC33035 brushless DC motor controller manufactured by ONSEMI is used.

[0064] <Protection Circuit> One or more protection circuits 4250 according to the present technology may include an electrical protection circuit, a temperature and / or pressure safety circuit.

[0065] <Memory> According to one form of the present technology, the RPT device 4000 includes a memory 4260 (e.g., 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.

[0066] The memory 4260 may be disposed on the PCBA 4202. The memory 4260 may be in the form of an EEPROM or a NAND flash.

[0067] Additionally or alternatively, the RPT device 4000 includes a removable memory 4260 (e.g., a memory card manufactured according to the Secure Digital (SD) standard).

[0068] In one form of the present technology, the memory 4260 functions as a non-transitory computer-readable recording medium. On this recording medium, computer program instructions (e.g., one or more algorithms 4300) representing one or more of the methods described herein are recorded.

[0069] <Data Communication System> In one embodiment of the present technology, a data communication interface 4280 is provided and connected to a central controller 4230. The data communication interface 4280 may be connectable to a remote external communication network 4282 and / or a local external communication network 4284. The remote external communication network 4282 may be connectable to a remote external device 4286. The local external communication network 4284 may be connectable to a local external device 4288.

[0070] In one embodiment, the data communication interface 4280 is part of the central controller 4230. In another embodiment, the data communication interface 4280 is separate from the central controller 4230 and may include an integrated circuit or a processor.

[0071] In one embodiment, the remote external communication network 4282 is the Internet. The data communication interface 4280 may use wired communication (e.g., via Ethernet or fiber optic) or a wireless protocol (e.g., CDMA, GSM, LTE) to connect to the Internet.

[0072] In one embodiment, the local external communication network 4284 uses one or more communication standards (e.g., Bluetooth® or consumer infrared protocol).

[0073] In one embodiment, the remote external device 4286 is one or more computers (e.g., a cluster of networked computers). In one embodiment, the remote external device 4286 may be a virtual computer rather than a physical computer. In either case, such a remote external device 4286 may be accessible by appropriately authorized persons (e.g., clinicians).

[0074] The local external device 4288 may be a personal computer, a mobile phone, a tablet, or a remote control.

[0075] <RPT Device Algorithm> As described above, in some forms of the present technology, the central control device 4230 can be configured to embody one or more algorithms 4300 expressed as a computer program recorded in a non-temporary computer-readable recording medium (for example, the memory 4260). These algorithms 4300 are generally grouped into groups called modules.

[0076] <Preprocessing Module> The preprocessing module 4310 according to one form of the present technology receives a signal from the transducer 4270 (for example, the flow sensor 4274 or the pressure sensor 4272) as an input and performs one or more process steps for calculating one or more output values. These output values are used as inputs to another module (for example, the treatment engine module 4320).

[0077] In one form of the present technology, the output values include the interface pressure Pm, the respiratory flow rate Qr, and the leakage flow rate Ql.

[0078] In various forms of the present technology, the preprocessing module 4310 includes one or more of the algorithms for interface pressure estimation 4312, ventilation flow rate estimation 4314, leakage flow rate estimation 4316, and respiratory flow rate estimation 4318.

[0079] <Treatment Engine Module> In one form of the present technology, the treatment engine module 4320 receives one or more of the pressure Pm in the patient interface 3000 or 3800 and the air respiratory flow rate Qr to the patient as inputs and provides one or more treatment parameters as outputs.

[0080] In one form of the present technology, the treatment parameter is the treatment pressure Pt.

[0081] In one form of the present technology, the treatment parameter is one or more of the amplitude of the pressure change, the base pressure, and the target ventilation.

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

[0083] <Apnea and Hypopnea Determination> In one form of the technology, the central controller 4230 executes an apnea / hypopnea determination algorithm 4325 to determine the presence of apnea and / or hypopnea.

[0084] In one form, the apnea / hypopnea detection algorithm 4325 receives the respiratory flow signal Qr as an input and provides, as an output, a flag indicating whether apnea or hypopnea has been detected.

[0085] In one form, apnea is detected when a function of the respiratory flow Qr falls below a flow threshold over a predetermined period. This function may determine peak flow, relatively short-term average flow, or a flow intermediate value of relatively short-term average and peak flow (e.g., RMS flow). The flow threshold may be a relatively long-term measurement of flow.

[0086] In one form, hypopnea is detected when a function of the respiratory flow Qr falls below a second flow threshold over a predetermined period. This function may determine peak flow, relatively short-term average flow, or a flow intermediate value of relatively short-term average and peak flow (e.g., RMS flow). The second flow threshold may be a relatively long-term measurement of flow. The second flow threshold is higher than the flow threshold used for detecting apnea.

[0087] <Snore Determination> In one form of the technology, the central controller 4230 executes one or more snore determination algorithms 4326 to determine the snore range.

[0088] In one form, the snoring detection algorithm 4326 receives the respiratory flow signal Qr as an input and provides, as an output, measurements of the range in which snoring is present.

[0089] The snoring detection algorithm 4326 may include the step of determining the intensity of the flow signal within a range of 30 to 300 Hz. Further, the snoring determination algorithm 4326 may include the step of filtering the respiratory flow signal Qr to reduce background noise (e.g., airflow sounds in the system from a blower).

[0090] <Air circuit> An air circuit 4170 according to one aspect of the present technology is a conduit or tube constructed and arranged such that, in use, an air flow moves between two components (e.g., the RPT device 4000 and the patient interface 3000 or 3800).

[0091] <Humidifier> <Overview of the humidifier> In one form of the present technology, a humidifier 5000 is provided for varying the absolute humidity of air or gas to be delivered to a patient relative to ambient air (e.g., as shown in FIG. 5A). Typically, the humidifier 5000 is used to increase the absolute humidity (relative to ambient air) and increase the temperature of an air flow before delivery to a patient airway.

[0092] 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. In some forms, such as those shown in FIGS. 5A and 5B, the inlet and outlet of the humidifier reservoir 5110 may be the humidifier inlet 5002 and the humidifier outlet 5004, respectively. The humidifier 5000 may further include a humidifier base 5006. The humidifier base 5006 is adapted to receive the humidifier reservoir 5110 and may include a heating element 5240.

[0093] <Respiratory waveform> Figure 6A shows a model of a typical human respiratory waveform during sleep. The horizontal axis is time and the vertical axis is respiratory flow rate. Since the parameter values can vary, a typical respiration may have approximate values of tidal volume, Vt, 0.5 L, inspiratory time, Ti, 1.6 seconds, peak inspiratory flow rate, Qpeak, 0.4 L / second, expiratory time, Te, 2.4 s, peak expiratory flow rate, Qpeak, -0.5 L / second. The total duration of respiration Ttot is about 4 seconds. Humans typically breathe about 15 times per minute (BPM), and ventilation Vent is about 7.5 L / min. The ratio of a typical duty cycle, Ti to Ttot, is about 40%.

[0094] <Screening, diagnosis, monitoring system> <Sleep polygraph> Figure 7A shows a patient 1000 undergoing a sleep polygraph (PSG). The PSG system includes a head box 2000. The head box 2000 receives and records signals from sensors including EOG electrodes 2015, EEG electrodes 2020, ECG electrodes 2025, submental EMG electrodes 2030, snoring sensor 2035, respiratory inductance plethysmogram (respiratory effort sensor) 2040 on a chest belt, respiratory inductance plethysmogram (respiratory effort sensor) 2045 on an abdominal belt, a nasal cannula 2050 with an oral thermistor, a photoplethysmogram (pulse oximeter) 2055, and a body position sensor 2060. The electrical signals are referred to as a ground electrode (ISOG) 2010 positioned at the center of the forehead.

[0095] <Non - obstructive monitoring system> An example of a monitoring device 7100 for monitoring the respiration of a patient 1000 during sleep is shown in Figure 7B. The monitoring device 7100 includes a non - contact motion sensor mainly directed towards the patient 1000. This motion sensor is configured to generate one or more signals indicating the movement of the body of the patient 1000. From these signals, a signal indicating the respiratory movement of the patient is obtained.

[0096] <Respiratory polygraphy> Respiratory polygraphy (RPG) is a term that refers to a simple form of PSG and does not use electrical signals (EOG, EEG, EMG), snoring, or body position sensors. RPG includes at least a chest movement signal from a respiratory inductance plethysmogram (motion sensor) on a chest band (e.g., 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 the PSG headbox 2000.

[0097] In a particular configuration, since the shape of the nasal pressure signal is similar to the nasal flow signal, the nasal pressure signal is an excellent proxy for the nasal flow signal generated by a flow transducer in wired connection with a sealed nasal mask. As a result, when the patient's mouth remains closed (i.e., there is no leakage from the mouth), the nasal flow is equal to the respiratory flow.

[0098] FIG. 8 is a block diagram showing a screening / diagnosis / monitoring device 7200 that can be used when an RPG headbox is implemented within an RPG screening / diagnosis / monitoring system. The screening / diagnosis / monitoring device 7200 receives the above three RPG channels (a signal indicating chest movement, a signal indicating nasal flow, and a signal indicating oxygen saturation) at a data input interface 7260. The screening / diagnosis / monitoring device 7200 also includes a processor 7210 configured to execute encoded instructions. The screening / diagnosis / monitoring device 7200 also includes a non-transitory computer-readable memory / storage medium 7230.

[0099] Memory 7230 can be the internal memory (e.g., RAM, flash memory, or ROM) of the screening / diagnosis / monitoring device 7200. In some embodiments, memory 7230 may be a removable or external memory connected to the screening / diagnosis / monitoring device 7200 (e.g., an SD card, a server, a USB flash drive, or an optical disk). In other embodiments, memory 7230 can be a combination of external and internal memories. Memory 7230 includes stored data 7240 and processor control instructions (codes) 7250 adapted to the configuration of processor 7210 to cause processor 7210 to perform specific tasks. The stored data 7240 may include RPG channel data received by the data input interface 7260 and other data provided as component parts of the application. The processor control instructions 7250 may be provided as component parts of an application program. Processor 7210 is configured to read the codes 7250 from memory 7230 and execute the encoded instructions. Specifically, the codes 7250 may include instructions adapted to configure processor 7210 to cause processor 7210 to execute a method of processing the RPG channel data provided by the interface 7260. One such method can be to store the RPG channel data as data 7240 in memory 7230. Another such method can 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.

[0100] The screening / diagnosis / monitoring device 7200 may also include a communication interface 7220. The reference numeral 7250 may include instructions configured to enable 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 implementation, the processor 7210 may transmit the stored RPG channel data from the data 7240 to a remote computing device. In such an implementation, the remote computing device may be configured to analyze the received RPG data to extract features. In another such implementation, the processor 7210 may transmit the analysis results from the data 7240 to a remote computing device.

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

[0102] <Data Transmission> FIG. 8 shows a block diagram illustrating an embodiment of a data consent brokerage system according to the present technology. For example, the system may include one or more user devices 4000 that generate data, which may be associated with the account of a user or patient 1000. The account of the patient 1000 may be managed from a mobile device 120 or other computing device to log in to the user's account for services related to the device 4000.

[0103] The user device 4000 may then provide consent data 8000 to various third parties that wish to utilize the user's data. The consent data 8000 particularly includes · A date and time stamp · Conditions to which the user has consented · Third parties to whom the user has consented to share data · Types of data to which the user has consented to share · Time window during which the consent is valid · Other related data may be included.

[0104] Consent data may be provided by the user clicking on a commitment on the user interface, specifying the conditions to which the user commits by checking a checkbox on the user interface or other means on the computing device 120.

[0105] Examples of the user device 4000 that generates data include medical devices, mobile devices, personal computers, laptops, CPAP machines and related software, humidifiers, other devices disclosed in this specification, wearables, various servers 7100 and software services running on computing devices, smartwatches, smart scales, smart wristbands, gene data services, health data services, exercise equipment, and various other user devices.

[0106] Therefore, the user data 10000 generated by the device 4000 may include health data, gene data, location data, metadata, treatment data, treatment settings, exercise data, profile data, age, weight, data from the electronic medical record, sleep quality data, apnea data, hypopnea, date and time stamps, and other types of data. The user data 10000 may be transmitted in packets having metadata indicating the type of data being transmitted.

[0107] The consent management system may also include a consent system 8100 that includes a server 7100 and a database 7200. The database 7200 may include (1) the types of data that can be shared, (2) the types of data generation devices that can be the source of the data, and (3) the third parties with whom the user 1000 has consented to share the data 185, and may include a unique user identifier referenced to the conditions consented to by the user 1000. Further, the consent system 8100 may store additional data fields referenced to the unique user identifier, including all of the above-described related items regarding the user data 10000.

[0108] In addition, a third-party system 8200 that includes at least the server 7100 as a data consumer and the database 7200 may also be connected via the network 7090 to the consent system 8100 and the computing device 120 of the user 1000. The network 7090 may be a wide-area network 7090 such as the Internet, an intranet, a cloud, or the Internet. The connection to the network may be wired or wireless.

[0109] The patient computing device 120 may be a personal computer, a mobile phone, a tablet computer, or other device. The patient computing device 120 is configured to mediate between the patient 1000 and the data server 7100 via the wide-area network 7090.

[0110] In one implementation, this mediation is performed by a software application program running on the patient computing device 120. The patient program is a dedicated application called a "patient application" and interacts with a complementary process hosted by the data server 7100. In another implementation, the patient program is a web browser and interacts with a secure portal via a website hosted by the data server 7100. In yet another implementation, the patient program is an email client.

[0111] In other examples, the data generation device 4000 communicates with the patient computing device 120 via a local (wired or wireless) communication protocol (e.g., a local network protocol (e.g., Bluetooth®)). In an alternative implementation, the patient computing device 120 is configured via a patient program to mediate between the patient 1000 and the data server 7100 via the network 7090 and to mediate between the data generation device 4000 and the data server 7100 via the network 7090.

[0112] Consent data 8000 from the computing device 120 of the user 1000 is sent to the third - party system 8200 and stored in its database 7200. As a result, the third - party system 8200 can determine which devices 4000 it can download data from and what types of data can be used and stored, etc.

[0113] FIG. 9 is a flowchart showing an example method of managing consent. For example, first, the consent system 8100 may receive a request from a third - party asking for access to the user's data 9000. Thus, in this case, the third - party does not need to send a notification to the computing device 120 of the user 1000 to separately ask the user for consent. Instead, the third - party sends a data packet to the consent system 8100, and the consent system 8100 can respond based on whether the user 1000 has consented to share the data.

[0114] This request may include the type of data, user identifier, type of user device, or other parameters including a request for consent to download data from the user computing device 120 or the user data generation device 4000. In other embodiments, this request includes only the user identifier, and the consent system 8100 may return consent data 8000 having an overview of the consent conditions to which the user 1000 has already consented.

[0115] In some embodiments, after this request is received from third party 9000, system 8100 may query database 7200 to determine whether the user identifier exists in database 7200 and what kind of consent is associated with user identifier 9100. For example, consent system 8100 may obtain consent data 9100 associated with the user identifier, which includes data types 9450 that the user has consented to share, authorized third parties 9460, and authorized user devices 9470. The authorized user device 9470 may be specified by various addresses, MAC addresses, or other identifiers.

[0116] Next, system 8100 may respond 9200 to third party system 8200 by sending consent data 8000 from server 7200 of consent system 8100 to server 7100 of system party system 8200. This may simply return true or false as to whether it includes the type of consent the user has given and whether third party system 8200 can download and use data from user device 4000.

[0117] Therefore, after the consent is confirmed in various ways through network 7090, third party system 8200 may then download data from user device 4000. This may continue for a certain period of time, a predetermined time window, or indefinitely.

[0118] In some embodiments, user 1000 explicitly indicates on computing device 120 that they wish to revoke a previously given consent and transmits revocation consent data 8000 to consent system 8100. Thereafter, consent system 8100 may determine which third - party system 8200 to transmit the revocation consent data 8000 to. The revocation consent data 8000 may include any combination of data fields including a global revocation for that third - party 8200 and user data 10000, or may include a specific type or use of data 10000.

[0119] FIG. 10 shows a further system representing another embodiment of the present disclosure. In this embodiment, rather than user data 10000 being transferred directly from user computing device 120 or user data generation device 4000 to third - party 8200, it is delivered through consent system 8100. Thereby, in addition to the consent system 8100 being able to effectively manage the consent process, being able to more easily revoke consent by turning off the data flow, and enhancing the ability to anonymize the data source and the users associated with the data source, it is advantageous as the consent system 8100 can act as a market for selling data.

[0120] FIG. 11 shows a flowchart illustrating an example method of implementing the consent system of FIG. 10. For example, consent system 8100 may send a request to the user device asking to consent to the sharing of data 11000. This may be a global request including multiple types of data, data consumers, end - users, uses, data sources, data generation devices. In other embodiments, this request may include only the data consumers of one specific third - party 8200 or may be prompted by that consumer.

[0121] Subsequently, system 8100 may receive confirmation of consent for the sharing of data 11100 from user computing device 120, which may include data type 9450, time window 9470 during which the consent is valid, and in some cases other factors and information including specific requesting third-party system 8200. Subsequently, upon confirmation of consent, system 8100 may request login data for the user's third-party account 11200, for example, targeting data generation device 4000, and may receive such data.

[0122] Thereby, server 7100 of the system logs in and can receive data 11300 from data generation device 4000 or the associated account of data generation device 4000, or other services or software via network 7090. Additionally, other embodiments may be implemented that similarly verify the credentials of user 1000's account and download data 11300.

[0123] Next, system 8100 and its server 7100 may process the data to determine the type of data 11400 and other relevant characteristics of the data. This may include, for example, categories of data referenced in the type of consent, such as location data, profile data, medical history, etc. In some examples, this may be performed using machine learning or other algorithms that identify, for example, the format of GPS coordinates. In other examples, system 8100 processes header information or other metadata to determine the type of data.

[0124] Subsequently, this data is stored in consent database 7200, which in some examples is referenced by user identifier 11500 or only by the type of data or data source. In some cases, various other tags are applied to the data so that database 7200 can be queried like a marketplace, determining the types and amounts of data available to data consumers of third-party system 8200.

[0125] <Consent System as a Data Pipe> FIG. 12 shows a flowchart illustrating an example method of facilitating the transfer of data from user data generation device 4000 to a third - party data consumer when consent for a specific third - party has been granted and confirmed. For example, in some of the above embodiments, the consent system 8100 may simply manage consent, or the system may upload data 10000 obtained from multiple users 1000 in order to aggregate and enhance the value of the data.

[0126] However, if the system uploads data 10000 obtained from multiple users 1000, a relatively large amount of database 7200 storage space is required. Therefore, in other embodiments, the consent system 8100 may act as a pipe for facilitating the transfer of data from the data generation device 4000 to the third - party system 8200. In this embodiment, the consent system 8100 does not need to store large amounts of data, but can still strictly manage the data flow. When a user cancels consent, the consent can be easily cancelled, preventing further data transfer.

[0127] For example, the consent system 8100 may send an API address to a third - party to access data generated by the data device 12000. Thereafter, the system 8100 may facilitate the transfer of data generated by the data device to the third - party through the API 12100. For example, the third - party 8200 may periodically call the API address to request an update of the data, and then the system 8100 may send or request additional data from the data generation device 4000. In other embodiments, the system may periodically send data to the third - party 8200 through the API.

[0128] In some embodiments, system 8100 may process data 10000 to identify the type of data (e.g., from metadata or specific features of the data structure). In this case, the API of system 8100 or other internal processing software may screen all or part of the data generated by user device 4000 before sending it to third party 8200. In some embodiments, before sending the data, certain information may first be removed from the data. This may include the user name and other identifying information that may be useful for complying with the type of user consent or for complying with privacy laws related to patient data.

[0129] <Data Market> In some embodiments, system 8100 may create a data market and present the type of data and the price of that data to data consumers or third parties 8200. Thereafter, third party 8200 may be able to purchase multiple types and amounts of data, and in some cases, a portion of the purchase price may be paid to user 1000 for sharing data 10000. In some embodiments, system 8100 (1) The type of data (e.g., movement, location, etc.) (2) The data source (3) Profile characteristics (e.g., gender, age, etc.) (4) Consent characteristics associated with the data (5) Other characteristics aggregates or catalogs the types of data available for purchase, which may include, and determines the various characteristics of the data relevant to the data consumer to determine whether the data is valuable to them.

[0130] In some embodiments, a third party 8200 may send a data request that includes, for example, the type of data requested, the threshold amount of data required, and the price that the third party 8200 can pay for the data. The system 8100 may then query the database 7200 using the server 7100 to determine whether the request can be made and the type, amount, and price of any relevant data.

[0131] Subsequently, in some embodiments, the system 8100 may send a notification to the third party 8200 that includes the available data and prices. The third party 8200 may then accept or reject the request, and in other embodiments, if the data identified on the database 7200 meets the requirements of the third party 8200, the system 8200 may automatically send the data (or send an API for access as described above).

[0132] In some embodiments, the system 8100 saves an open request from the third party 8200 seeking data 10000 and determines whether the new data meets the requirements of any open requests each time a new user 1000 uploads or provides consent to share the data 10000. Subsequently, if any open request is satisfied, the new data 10000 can be sent to each third party 8200.

[0133] <Selected Embodiment> The above description and the appended claims disclose some embodiments of the present invention, but other alternative aspects of the present invention are disclosed in the following further embodiments.

[0134] [Embodiment 1] A system for managing consent, comprising: a consent database having a user ID with a unique identifier representing a referenced user account; a set of types of data to which the user has consented to share; a set of devices that are the source of the data generated by those devices and to which the user has consented to share the data; a set of consumers who are the parties to whom the user has consented to share the data; a memory including a machine-readable medium containing machine-executable code, the memory storing instructions for performing a method on the machine-executable code; and a control system coupled to the memory and including one or more processors, wherein the control system, by executing the machine-executable code, causes the control system to receive a request from a consumer asking to access data from the user, the request comprising a timestamp, a user ID associated with the account, and a first type of data, access the user ID, query the consent database to determine whether the user associated with the user ID has consented to share the first type of data, and send a response to the consumer indicating whether the consumer is granted permission to access the first type of data from the account referenced by the user ID. A system for managing consent.

[0135] [Embodiment 2] The system according to Embodiment 1, further configured such that the control system receives a request from the user indicating that the user has revoked consent to share the first type of data and sends a notification to the consumer indicating that the user has revoked consent to share the first type of data.

[0136] [Embodiment 3] The system according to Embodiment 2, further configured such that the control system sends a request to the user to update the consent, receives confirmation from the user to update the consent, and sends a notification to the consumer indicating that the user has updated the consent.

[0137] [Embodiment 4] The control system further configured to send to the consumer an address through which the consumer can access the first type of data, receive from the consumer a request for accessing the first type of data through the address, and establish a link between the consumer and a user database including the first type of data stored with reference to the user ID, and send a set of the first type of data to the consumer, the system according to Embodiment 1.

[0138] [Embodiment 5] The first type of data is profile data, mobile data, location data, health data, respiratory therapy data, vital sign data, wearable data, heart-related wearable data, step count data, genetic data, social media usage data, workout data, or fitness data, the system according to Embodiment 1.

[0139] [Embodiment 6] The type of device includes a mobile phone, a wearable fitness tracker, a heart rate monitoring watch, a pulse oximeter, or a respiratory therapy device, the system according to Embodiment 1.

[0140] [Embodiment 7] The consent database further includes market prices referenced to each type of data stored, the system according to Embodiment 1.

[0141] [Embodiment 8] Each of the set of consumers is respectively referenced to an address, the system according to Embodiment 1.

[0142] [Embodiment 9] A system for managing third - party data access, comprising: a consent database having a user ID with a unique identifier representing a referenced user account; a set of data comprising at least first and second types of data to which the user has consented to share; a set of devices that the user has consented to share the data generated by those devices; a memory including a machine - readable medium containing machine - executable code, wherein instructions for performing a method are stored on the machine - executable code; and a control system coupled to the memory and comprising one or more processors, wherein, by executing the machine - executable code, the control system causes the control system to send a request to a user device associated with the user ID to request consent for data sharing, receive from the user device a confirmation of consent to data sharing comprising consent to share the first type of data and a time window during which the shared consent is valid, receive from the user device the user ID and login information for a third - party account associated with a first data device, send a request to the first data device to obtain data, receive a first set of data from the first data device, process the first set of data to identify a set of the first type of data, and store the set of the first type of data in the consent database referenced by the user ID. A system for managing third - party data access.

[0143] [Embodiment 10] The system according to Embodiment 9, wherein processing the first set of data to identify a set of the first type of data further comprises processing the data to identify GPS coordinates.

[0144] [Embodiment 11] Processing the first set of data to identify a first type of data further includes processing the data to identify data output from an accelerometer, a gyroscope, or a magnetometer, the system of Embodiment 10.

[0145] [Embodiment 12] The system of Embodiment 10, further configured to query a consumer database that references a set of consumers and data reception addresses to a type of data that each consumer has agreed to receive within a threshold market price, to identify any one of the set of consumers who has agreed to receive the first type of data at the current market price for the first type of data, and to transmit the first type of data of the set to any one of the identified consumers at the referenced data reception address.

[0146] [Embodiment 13] The system of Embodiment 12, wherein the consumer database references specific characteristics of the type of data that must be included to receive the data at the market price.

[0147] [Embodiment 14] The system of Embodiment 13, wherein the characteristics include height, weight, and age.

[0148] [Embodiment 15] The system of Embodiment 13, wherein the characteristics include heart rate data.

[0149] [Embodiment 16] The system of Embodiment 14, wherein the characteristics include genetic data.

[0150] [Embodiment 17] The system of Embodiment 14, wherein the characteristics include a combination of genetic data and heart rate data.

[0151] [Embodiment 18] A system for managing consent, comprising: a consent database having a user ID with a unique identifier representing a referenced user account; a set of types of data to which the user has consented to share; a set of devices that are the source from which the user has consented to share the data generated by those devices; a set of consumer devices with which the user has consented to share the data; a memory including a machine-readable medium containing machine-executable code, the memory storing instructions for performing a method on the machine-executable code; and a control system coupled to the memory and comprising one or more processors, wherein the control system, by executing the machine-executable code, causes the control system to receive from the user a request for access to data including a timestamp, a user ID associated with an account, and a first type of data, access the user ID, query the consent database to determine whether the user associated with the user ID has consented to share the first type of data with the first of the set of consumer devices, and send to the first of the set of consumer devices a response indicating whether the first of the set of consumer devices has been granted permission to access the first type of data from the account referenced by the user ID. A system for managing consent.

[0152] [Embodiment 19] The system according to Embodiment 18, further configured such that the control system receives from the user a request indicating that the user has revoked consent to share the first type of data and sends to the first of the set of consumer devices a notification indicating that the user has revoked consent to share the first type of data.

[0153] [Embodiment 20] The control system of embodiment 19 is further configured to send a request for consent update to the user, receive confirmation of consent update from the user, and send a notification indicating that the user has updated the consent to the first of the set of consumer devices.

[0154] [Embodiment 21] The system of embodiment 20 is further configured to establish a link between the first of the set of consumer devices and a user database containing the first type of data stored with reference to the user ID, such that the control system sends an address to the first of the set of consumer devices through which the first of the set of consumer devices can access the first type of data, and receives a request from the first of the set of consumer devices of the first type to access the first type of data at the address, and then sends the first type of data to the first of the set of consumer devices.

[0155] [Embodiment 22] The system of embodiment 1, wherein the 20th type of data is profile data, mobile data, location data, health data, respiratory therapy data, vital sign data, wearable data, heart-related wearable data, step count data, genetic data, social media usage data, workout data, or fitness data.

[0156] [Embodiment 23] The system of embodiment 20 is further configured to store the first of the set of consumer devices in the consent database as an authorized data consumer referenced to the user ID and the consent time window, and to send a notification to the first of the set of consumer devices indicating that the consent has been cancelled when the time window expires.

[0157] [Embodiment 24] The system of embodiment 18, wherein the device of said type includes a mobile phone, a wearable fitness tracker, a heart rate monitoring watch, a pulse oximeter, or a respiratory therapy device.

[0158] [Embodiment 25] The system of embodiment 18, wherein the consent database further includes market prices referenced to each type of data stored.

[0159] [Embodiment 26] The system of embodiment 18, wherein each of said set of consumer devices is respectively referenced to an address.

[0160] [Embodiment 27] Receiving from a consumer a request from the user to access data including a timestamp, a user ID associated with an account, and a first type of data; accessing the user ID; querying the consent database to determine whether the user associated with the user ID has consented to share the first type of data; and sending to the consumer a response indicating whether the consumer is granted permission to access the first type of data from the account referenced to the user ID.

[0161] [Embodiment 28] The method of embodiment 27, further comprising receiving from the user a request indicating that the user has revoked consent to share the first type of data, and sending to the consumer a notification indicating that the user has revoked consent to share the first type of data.

[0162] [Embodiment 29] The method of embodiment 27, further comprising sending to the user a request to update consent, receiving from the user a confirmation to update consent, and sending to the consumer a notification indicating that the user has updated consent.

[0163] [Embodiment 30] Further including: sending to the consumer an address through which the consumer can access the first type of data; receiving from the consumer a request asking to access the first type of data through the address; establishing a link between the consumer and a user database including the first type of data stored with reference to the user ID; and sending a set of the first type of data to the consumer. The method according to Embodiment 27

[0164] [Embodiment 31] The method according to Embodiment 27, wherein the first type of data is profile data, mobile data, location data, health data, respiratory therapy data, vital sign data, wearable data, heart-related wearable data, step count data, genetic data, social media usage data, workout data, or fitness data

[0165] [Embodiment 32] Further including: storing the consumer in the consent database as an authorized data consumer referenced to the user ID and the time window of consent; and sending to the consumer a notification that the consent has been cancelled when the time window expires. The method according to Embodiment 27

[0166] [Embodiment 33] The method according to Embodiment 27, wherein the types of devices include mobile phones, wearable fitness trackers, heart rate monitoring watches, pulse oximeters, or respiratory therapy devices

[0167] [Embodiment 34] The method according to Embodiment 27, wherein the consent database further includes market prices referenced to each type of data stored

[0168] [Embodiment 35] The method according to embodiment 27, wherein each of the group of consumers is respectively referenced by an address.

[0169] [Embodiment 36] A computer program product including instructions which, when executed by a control system, cause the computer to execute the method according to any one of embodiments 27 to 35.

[0170] [Embodiment 37] The computer program product according to embodiment 36, which is a non-transitory computer-readable medium.

Claims

1. A system for managing consent, comprising: A set of types of data that the user has consented to share, A set of devices, a set of consumers who are the parties to whom the user has consented to share the data, and the price of the data, a consent database having a user ID with a unique identifier referring to a user account representing the set of devices that were the basis for the user's consent to share the data generated by those devices; A memory including a machine-readable medium containing machine-executable code, the machine-executable code having instructions for performing a method stored thereon; A control system coupled to the memory, the control system including one or more processors, the control system being configured to: By executing the machine-executable code, receive a request from a consumer seeking access to the user's data comprising a timestamp, a user ID associated with an account, and a first type of data; Access the user ID and query the consent database to determine whether the user associated with the user ID has consented to share the first type of data; Send a response to the consumer indicating whether the consumer is granted permission to access the first type of data from the account referenced by the user ID; In response to receiving a purchase request for the first type of data from the consumer, perform payment processing from the consumer and directly send the first type of data from the user device that stores the first type of data among the set of devices to the consumer, a system for managing consent.

2. The control system is configured to: Receive a request from the user indicating that the user has revoked consent to share the first type of data, Further configured to send a notice to the consumer indicating that the user has canceled the consent to share the first type of data. The system according to claim 1. **Claim 3** The control system sends a request to the user to request an update of the consent receives confirmation from the user to update the consent, and is further configured to send a notice to the consumer indicating that the user has updated the consent. The system according to any one of claims 1 to 2. **Claim 4** The control system sends the consumer an address through which the consumer can access the first type of data, receives from the consumer a request to access the first type of data at the address, and is further configured to establish a link between the consumer and a user database storing the first type of data associated with the user ID, and send a set of the first type of data to the consumer. The system according to claim 1. **Claim 5** The first type of data is profile data, mobile data, location data, health data, respiratory therapy data, vital sign data, wearable data, heart-related wearable data, step count data, genetic data, social media usage data, workout data, or fitness data. The system according to claim 1. **Claim 6** The control system stores the consumer in the consent database as an authorized data consumer referenced by the user ID and the time window of the consent, and Further configured to send a notification to the consumer that the consent has been revoked when the time window expires. The system according to claim 1.

7. The type of device includes a mobile phone, a wearable fitness tracker, a heart rate monitoring watch, a pulse oximeter, or a respiratory therapy device. The system according to any one of claims 1 to 6.

8. The consent database further includes market prices referenced to various types of data stored. The system according to any one of claims 1 to 6.

9. Each of the group of consumers is respectively referenced to an address. The system according to any one of claims 1 to 6.

10. A system for managing third-party data access, A consent database having a user ID with a unique identifier representing a set of data comprising at least first and second types of data to which the user has consented to share, a set of devices to which the user has consented to share the data generated by those devices, a user account referenced to the set of devices, and a first price associated with the first type of data and a second price associated with the second type of data; A memory including a machine-readable medium including machine-executable code, the machine-executable code having instructions for performing a method stored thereon, A control system coupled to the memory, the control system including one or more processors, The control system, by executing the machine-executable code, causes the control system to send a request for consent to share data to a user device associated with the user ID. Consent to share the first type of data, and a time window during which the sharing consent is valid, and cause the user device to receive a confirmation of consent to data sharing including the same, cause the user device to receive the user ID and login information of a third-party account associated with the first data device, cause a request to obtain data including the login information of the third-party account to be sent to the first data device, cause the first set of data to be received from the first data device by logging in to the third-party account using the login information of the third-party account, cause the first set of data to be processed to identify a set of the first type of data, cause the set of the first type of data to be stored in the consent database referenced by the user ID, perform payment processing from the third party in response to receiving a purchase request for the set of the first type of data from the third party, and send the set of the first type of data to the third party, A system.

11. Processing the first set of data to identify a set of the first type of data further includes processing the data to identify GPS coordinates, The system according to claim 10.

12. Processing the first set of data to identify a set of the first type of data further includes processing the data to identify data output from an accelerometer, a gyroscope, or a magnetometer, The system according to any one of claims 10 to 11.

13. The control system is To identify any one of a set of consumers who have agreed to receive the first type of data at the current market price for the first type of data, query a consumer database that associates a set of consumers with data reception addresses with respect to the type of data that each consumer has agreed to receive within a threshold market price, and further configured to transmit the first type of data of the set to any one of the identified consumers among the set of consumers at the referenced data reception address. The system according to any one of claims 10 to 11.

14. The consumer database references the specific characteristics of the type of data that must be included to receive the data at the market price. The system according to any one of claims 10 to 13.

15. The characteristics include height, weight, and age. The system according to claim 14.

16. The characteristics include heart rate data. The system according to claim 14.

17. The characteristics include genetic data. The system according to claim 14.

18. The characteristics include a combination of genetic data and heart rate data. The system according to claim 14.

19. Receiving a request from a consumer to access data including a timestamp, a user ID associated with an account, and a first type of data, accessing the user ID and querying an agreement database to determine whether the user associated with the user ID has agreed to share the first type of data. Sending a response to the consumer indicating whether the consumer is granted permission to access the first type of data from the account referenced by the user ID; In response to receiving a purchase request for the first type of data from the consumer, performing payment processing from the consumer, and causing the first type of data to be directly transmitted to the consumer from a user device that stores the first type of data among the set of devices; A method including the above.

20. Receiving a request from the user indicating that the user has canceled consent to share the first type of data; Further including sending a notice to the consumer indicating that the user has canceled consent to share the first type of data; The method according to claim 19.

21. Sending a request to the user for an update of consent; Receiving confirmation from the user to update the consent; Further including sending a notice to the consumer indicating that the user has updated the consent; The method according to claim 19.

22. Sending the address to the consumer through which the consumer can access the first type of data; Receiving a request from the consumer to access the first type of data at the address; Further including establishing a link between the consumer and a user database including the first type of data stored with reference to the user ID, and transmitting a set of the first type of data to the consumer; The method according to claim 19.

23. The first type of data is profile data, mobile data, location data, health data, respiratory therapy data, vital sign data, wearable data, heart-related wearable data, step count data, genetic data, social media usage data, workout data, or fitness data. The method according to any one of claims 19 to 22.

24. Storing the consumer in the consent database as an authorized data consumer referenced to the user ID and the time window of the consent; Further including, when the time window expires, sending a notification to the consumer that the consent has been revoked. The method according to claim 19.

25. The type of device includes a mobile phone, a wearable fitness tracker, a heart rate monitoring watch, a pulse oximeter, or a respiratory therapy device. The method according to any one of claims 19 to 23.

26. The consent database further includes a market price referenced to each type of stored data. The method according to any one of claims 19 to 23.

27. Each of a group of consumers is respectively referenced to an address. The method according to any one of claims 19 to 23.

28. A computer program including instructions to cause one or more processors to execute the method according to any one of claims 19 to 27.

29. A recording medium on which the computer program according to claim 28 is recorded, where the computer program is recorded on a non-transitory computer-readable medium.

Images