METHOD AND SYSTEM FOR DATA TRANSFER IN VENTILATION DEVICES

Description

[0001] The invention relates to a method for data transmission within a system comprising at least one ventilator.

[0002] Modern ventilators typically offer several ways to display or output data and information related to the user. A ventilator usually has a display that shows a certain amount of information directly on the device. Furthermore, some ventilators offer various methods for transferring data between the ventilator and external devices.

[0003] In the current state of the art, these possibilities are known in the form of connections for storage devices or connections to servers, enabling the transfer of data from the ventilator to other devices for display or further processing. In particular, connecting the ventilator to a server allows for remote monitoring of the user, known as telemonitoring. Telemonitoring also makes it possible to monitor multiple ventilators.

[0004] Current ventilators are constantly connected to servers for telemonitoring, exchanging data and information. This means that data is transmitted and stored even when no transmission is necessary. Consequently, this results in unnecessary energy costs and, for mobile devices, potentially also mobile data charges. Furthermore, this constant, unnecessary data transmission is problematic from a data privacy perspective.

[0005] US2003072424, CN109806499, US2012258756 and US2004259494 are relevant prior art documents that disclose regular and irregular data transmission between servers and medical devices.

[0006] The object of the present invention is therefore to provide a system for data transmission and a corresponding method which can reduce energy consumption and simplify the monitoring of multiple ventilators.

[0007] Summary of the invention: The problem is solved by the invention according to the method of claim 1, the system of claim 11, and the ventilator of claim 12. Summary of the related disclosure

[0008] A method for data transmission within a system, wherein the system comprises at least one ventilator and one server, the ventilator comprising at least one input unit and at least one communication unit, the input unit being configured and configured to provide input values ​​and information to the system, and the communication unit being configured and configured to establish at least one connection to at least one server and to transmit data between the server and the ventilator, i.e., to send data to and receive data from the server. The data transmission is terminated by the server, the termination of which is characterized by the fact that no further medical data is transmitted from the ventilator to the server.Data transmission can also be terminated by the server sending a corresponding command or request to the ventilator. This also includes situations where the server sends a request to the ventilator regarding the amount of data and / or transmission duration, and the ventilator terminates data transmission after the requested data has been transferred. The ventilator does not decide independently whether to terminate data transmission, but only after receiving a request and / or instructions (such as a data volume to be transferred or a timeframe for data transmission) from the server.

[0009] In some embodiments of the method, non-medical data is transmitted independently of the data transmission between the server and the ventilator.

[0010] In some embodiments of the method, after the data transmission by the server has ended, non-medical data is transferred between the server and the ventilator.

[0011] In some embodiments of the method, after the data transmission by the server has ended, data is transferred from the server to the ventilator.

[0012] In some embodiments of the method, after the data transmission between the server and the ventilator has ended, the connection between the server and the ventilator is disconnected.

[0013] In some embodiments of the method, the connection between the ventilator and the server is established exclusively via the communication unit. Establishing a connection between the ventilator and the server can also be triggered, for example, by a corresponding input at the input unit.

[0014] In some embodiments of the method, the communication unit connects to the server at time intervals when the connection is disconnected.

[0015] In some embodiments of the method, the connection is only established when the ventilator is in a connectable mode.

[0016] In some embodiments of the method, when a connection is re-established after a time interval between the communication unit of the ventilator and the server, initially only device information from the ventilator is transmitted to the server.

[0017] In some embodiments of the method, the server uses the transmitted device information from the ventilator to identify the ventilator and decides whether and which data should be transmitted from the ventilator to the server.

[0018] In some embodiments of the method, before the data transmission is completed and / or before the connection is disconnected, the server sends at least data relating to the time interval in which the ventilator connects to the server.

[0019] In some embodiments of the method, the ventilator automatically determines the time interval for the next connection to the server based on an analysis of the previously transmitted data.

[0020] In some embodiments of the method, the server transmits configuration data for communication to the ventilator, wherein the configuration data for communication includes settings for the amount of data to be sent from the ventilator to the server during the data transmission and / or the connection, as well as settings for the time intervals at which the ventilator should connect to the server.

[0021] In some embodiments of the method, no medical data is transmitted from the ventilator to the server unless this data is requested by the server.

[0022] In some embodiments of the method, the data transfer between the ventilator and the server is initiated by an action command from the server to the communication unit. This action command transmits, for example, a request for data transmission to the communication unit or the ventilator.

[0023] In some embodiments of the method, the communication unit and / or the server generate or trigger an alarm signal when a certain number of unsuccessful or failed connections between the communication unit and the server are registered.

[0024] In some embodiments of the method, the data transmission from the communication unit to the server is automatically terminated by the server based on an analysis of the medical data previously transmitted by the ventilator.

[0025] In some embodiments of the method, the connection between the communication unit and the server is automatically disconnected by the server based on an analysis of the previously transmitted data.

[0026] In some embodiments of the method, the data transmission from the communication unit to the server is terminated by the server after an input is received on the server.

[0027] In some embodiments of the method, the connection between the communication unit and the server is disconnected by the server after an input is received on the server.

[0028] In some embodiments of the method, data is recorded by the ventilator and stored until the next connection to the server. In other embodiments, the recorded data is also stored after a connection to the server and / or after the stored data has been transferred to the server.

[0029] In some embodiments of the method, when disconnected from the server, the ventilator establishes a connection to the server based on an analysis of the recorded data and initiates a data transfer.

[0030] In some embodiments of the method, the ventilator evaluates and / or summarizes the stored data. This evaluated or summarized data is then transmitted to the server during a new data transmission.

[0031] In some embodiments of the method, the ventilator evaluates and / or summarizes the stored data. This evaluated or summarized data is transmitted to the server during a new data transmission, provided it is requested by the server.

[0032] In some embodiments of the method, the communication configuration data includes settings for whether data should be transmitted with a high level of detail.

[0033] In some embodiments of the method, the communication configuration data includes a setting to determine whether only evaluated and / or aggregated data should be transmitted.

[0034] In some embodiments of the method, the ventilator connects to the server at certain intervals, and data is transferred between the server and the ventilator.

[0035] In some embodiments of the method, the transmission of medical data is prevented after the data transmission by the server has ended.

[0036] The claimed device relates to a ventilator which is used in the described method according to the invention.

[0037] It should be noted that the features listed individually in the claims can be combined with one another in any technically meaningful way and demonstrate further embodiments of the invention. The description further characterizes and specifies the invention, particularly in conjunction with the figures.

[0038] It should also be noted that the conjunction "and / or" used herein, which stands between two features and links them together, is always to be interpreted in such a way that in a first embodiment of the object according to the invention only the first feature may be present, in a second embodiment only the second feature may be present, and in a third embodiment both the first and the second feature may be present.

[0039] A ventilator is any device that supports a user or patient in their natural breathing, takes over the ventilation of the user or patient, and / or serves for respiratory therapy and / or otherwise influences the user's or patient's breathing. This includes, but is not limited to, CPAP and BiPAP devices, anesthesia machines, respiratory therapy devices, (clinical, home, or emergency) ventilators, high-flow therapy devices, and cough machines. Ventilators can also be understood as diagnostic devices for ventilation. Diagnostic devices can generally be used to record a patient's medical parameters. This also includes devices that can record and optionally process medical parameters of patients in combination with, or exclusively related to, respiration.

[0040] An interface, in the broadest sense, can be understood as any type of device for communication – regardless of the connection type – between the ventilator and a counterpart or a person. An interface for communication between the ventilator and a person could, for example, be a user interface that enables interaction between the person and the ventilator directly on the ventilator itself.

[0041] Unless explicitly stated otherwise, a patient interface can be understood as any part or connected peripheral device of the ventilator intended for interaction with a patient, particularly for therapeutic or diagnostic purposes. Specifically, a patient interface can be understood as a ventilator mask or a mask connected to the ventilator. This mask can be a full-face mask, i.e., covering both the nose and mouth, or a nasal mask, i.e., covering only the nose. Tracheal tubes and nasal cannulas can also be used as masks.

[0042] For example, if data transmission between the ventilator and the server has ended, and consequently the connection between the ventilator and the server has been severed, the ventilator can be configured so that, if the connection between the ventilator and the server is broken, the communication unit will establish a connection to the server or attempt to do so within a specific time interval, which can be set on the ventilator and / or specified by the server. In some configurations, the connection is only established if the ventilator is capable of establishing a connection and transmitting data. This requires, for example, at least a power supply and a data connection (such as a mobile network or internet connection via LAN / WLAN).In some cases, an active wireless network connection (e.g., mobile network, WLAN / WiFi) is not desirable during ongoing sleep therapy. If a wired network connection or internet connection is unavailable, a connection from the ventilator to the server cannot be established in this case.

[0043] The connection and data transfer between the ventilator and the server are established regularly. The ventilator establishes a connection to the server as soon as a predefined time interval has elapsed and the ventilator is capable of doing so, i.e., when a power supply and data connection are available. Alternatively, the connection between the ventilator and the server can also be initiated manually by a user on the ventilator or a user on the server.

[0044] During data transmission, the server sends configuration data to the therapy device. This data includes medical configuration data (e.g., therapeutic settings), technical configuration data (e.g., firmware updates), and communication configuration data. The communication configuration data contains settings for the amount of data the ventilator should send to the server during data transmission, as well as, preferably, the time interval. The communication configuration can also be used to set, for example, the level of detail in the medical and technical data transmitted from the ventilator to the server.

[0045] During data transmission, the therapy device transmits technical data (for example, version status, settings, fill level / level or wear of consumables, occurrence of technical errors, etc.) and medical data (usage times of the ventilator, effectiveness of the ventilator / therapy, correct use of the ventilator, diagnostic data from the ventilator, pressure, flow, respiratory rate, volumes, O2 / CO2 saturation / content of the (exhaled) air, etc.) to the server.

[0046] The communication configuration settings allow the server, or a server user, to remotely configure, in particular, whether, at what interval, and with what level of detail medical data should be sent from the ventilator to the server. The medical data can be sent with varying levels of detail. The server can specify the level of detail for transmission. A server user can also remotely adjust the level of detail. In some configurations, the therapy device itself can also specify the level of detail. The data can include, for example, measured values ​​and / or outcome values. The data can also be transmitted in the form of signal curves. The data or values ​​can be transmitted as raw data or as parameters such as means, medians, or the like. The data resolution can also be specified by the server.The data can be sent at low, medium, or high resolution.

[0047] The communication configuration data can also include settings for whether continuous data transmission (i.e., the constant sending of recorded data) or the transmission of data packets (e.g., summarized medical data) should be used. Regarding continuous data transmission, the frequency of data transmission can also be configured, i.e., whether live transmission or a lower frequency (e.g., transmission every 1 to 60 minutes) should occur.

[0048] In this process, new configuration data for communication can be sent from the server to the ventilator with each data transmission or connection, which the ventilator then applies to current and / or future connections or data transmissions.

[0049] In some embodiments of the method, the ventilator first sends device information to the server with each new connection established. This information includes details such as device type, serial number, firmware version, etc. Based on this information, the server identifies the device and can then decide, individually for that device, whether and how much data should be sent from the ventilator to the server. This decision is then sent from the server to the ventilator, for example, as a communication configuration. Based on this communication configuration, the ventilator may then begin transmitting data. The server also decides whether and which other data and / or configurations, such as technical or medical settings, are sent to the ventilator.For example, the server can use the device information of the ventilator to decide that a new firmware version should be sent to the ventilator.

[0050] In some embodiments of the method, the ventilator's communication configuration also specifies the time interval after which it should reconnect to the server once data transmission is complete. Alternatively, the ventilator can be configured to determine the time interval itself based on the transmitted data. For example, if medical data has just been requested and sent from the ventilator to the server, the next connection from the ventilator to the server will occur after an interval of, for example, 24 hours. If no medical data has been requested, the time interval could also be, for example, 3, 5, or 7 days.

[0051] After the time interval for the next connection between the ventilator and the server has elapsed, both the ventilator and the server register whether a connection was successfully established. In some implementations of the method, the server, for example, counts the number of failed connections and generates an alarm message after a certain number of failed connections has been reached. This alarm message is then sent by the server and displayed to a user. Alternatively or additionally, the server can be configured to attempt a connection to the ventilator if a certain number of failed connections are detected. The number of failed connections between the ventilator and the server that triggers an alarm message depends, among other things, on the previously set time interval and the last data transmission.For example, if the set time interval is 24 hours, the server can generate an alarm message after two failed connections (i.e., 48 hours). Thresholds of just one failed connection or three or more failed connections are also conceivable and can be useful. If the last data transmission was a continuous, i.e., "live" transmission, or a transmission of data at short intervals (frequency of one data transmission every 1 to 360 minutes), it may be advisable to set a higher number of failed connections that trigger an alarm message. For example, the number can be chosen to be equivalent to 24 hours or two days or more. For instance, with a frequency of one connection or data transmission every 60 minutes, this would mean that the server would register 24 failed connections before generating an alarm message.The same rules can also apply to the ventilator. Additionally, the ventilator can be configured to automatically shorten the intervals between failed connection attempts to the server. For example, if a connection is supposed to be established after 24 hours, but this is not possible for unspecified reasons, the interval can initially be reduced to between 1 and 12 hours. If a connection to the server still cannot be established after a certain number of attempts, an alarm message is generated and displayed to the user on the ventilator. The number of unsuccessful connections by the ventilator that trigger an alarm message can, for example, range from 1 to 72.The alarm message may, for example, indicate that the last connection(s) have not been established, or it may also suggest that settings on the device need to be changed and / or that the service should be contacted.

[0052] The invention is explained in more detail below with reference to exemplary embodiments shown in Figures 1 to 3.

[0053] The Figure 1 This shows an exemplary, schematic setup of the system with the ventilator 1 and the server 7.

[0054] The ventilator includes, for example, an input unit 2, a communication unit 3, a control unit 4, a user interface 5, a blower and / or valve unit 61, a sensor unit 62, a reprocessing unit 63, a storage unit 64 and a monitoring unit 65.

[0055] The blower and / or valve unit 61 is designed to generate a respiratory gas airflow for the ventilation or therapy of a patient and, if necessary, to direct it towards the patient.

[0056] The sensor unit 62 is designed to acquire measured values, in particular parameters related to airflow, tidal volume, respiratory rate, inhalation and exhalation duration, respiratory contour, leakage, or therapeutic pressure. Optionally, the sensor unit 62 can perform additional measurements of the components or temperature of the respiratory gas or blood. The sensor unit 62 transmits the acquired measured values ​​to the processing unit 63.

[0057] The processing unit 63 can process the acquired measured values. For example, the processing unit 63 can perform smoothing, artifact removal, or downsampling of the measured values. In some embodiments, the processing unit 63 is also designed as a combined processing, calculation, and recognition unit; alternatively or additionally, these units can also be designed as separate units. The calculation unit calculates signals and / or parameters, such as a mean, median, percentile, derivative, frequency distribution, duration, or the proportion of exceeding or falling below threshold values, from the measured values ​​acquired by the sensor unit and processed by the processing unit.The detection unit is designed to detect events / conditions such as alarms, pauses in breathing, artifacts, coughs, oxygen (de)saturations, asynchronous movements between device and user, inhalation, exhalation, or mandatory breaths.

[0058] The storage unit 64, which can also be configured as an intermediate storage unit, stores, among other things, the values / parameters acquired by the sensor unit 62 and / or the values, data, and / or information processed by the processing unit 63, or at least temporarily stores them. Intermediate storage means, for example, that the values, data, and / or information are stored until transmission and then, for example, deleted or made available for overwriting.

[0059] The monitoring unit 65 detects, for example, technical problems of the ventilator 1. Technical problems can include, for example, a low battery level, electronic faults, a defective battery, a defective component, a power outage, a malfunctioning accessory, an implausible reading, or a temperature deviation from the permitted range. Upon detecting a technical problem, the monitoring unit can display or transmit an alarm to the ventilator 1 via one of its interfaces. In some configurations, these technical problems may also be considered serious errors that, apart from a corresponding error message on the display (user interface), do not allow any data transmission.

[0060] In addition, the ventilator 1 includes connections not shown here, for example to connect a patient interface to the ventilator 1 via a hose.

[0061] The input unit 2 is configured and designed, for example, to provide data and / or information to the system, and in particular to the ventilator 1. The input unit 2 is connected to the communication unit 3 and the user interface 5 in such a way that the data and / or information entered by these units 3 and 5 is made available to the system, or to the ventilator 1.

[0062] The communication unit 3, for example, primarily serves to connect the ventilator 1 to the server 7.

[0063] The control unit 4 of the ventilator 1 is configured, by way of example, to control at least the blower or valve unit 61. In some exemplary embodiments, the control unit 4 is also configured to control the communication unit 3 and / or other or all further components of the ventilator 1. In some embodiments, a plurality of control units may also be used. As a rule, the control unit 4 controls the blower or valve unit 61 according to the configurations stored in the memory unit 64 and data determined by the sensor unit 62 and possibly processed / evaluated by the processing unit 63.If the processed / evaluated data exceed threshold values ​​for breathing pressures, gas flows and / or breathing frequencies, and this is detected by the processing unit 63 from the recorded values ​​of the sensor unit 62, the control unit 4 regulates the blower or valve unit 61 accordingly.

[0064] User interface 5, for example, is an interface that allows the user / patient to make settings, configurations, and inputs on the ventilator and, if necessary, to view messages (e.g., alarms), information, and data (e.g., medical and technical data). User interface 5 can be implemented as a touchscreen, enabling both input and display. Alternatively, the user interface can be a screen with additional buttons, switches, and / or rotary knobs for input. In some exemplary embodiments, the user interface consists only of one or more controls for basic operation (e.g., switching on / off) and optional indicator lights for status display.User interface 5 is also configured, for example, to input a request to connect the ventilator 1 to the server 7 via the communication unit 3. In some exemplary embodiments, user interface 5 is an interface for connecting to external display and output devices, such as a keyboard and an external monitor.

[0065] Server 7 is configured, among other things, to establish a connection between the communication unit 3 of the ventilator 1 and Server 7. In some exemplary embodiments, Server 7 also has a connected computer or is directly connected to at least one display unit and an input device (e.g., a keyboard). Furthermore, Server 7 is also configured, for example, to store, evaluate, process, forward, and / or interpret data and / or information received from the ventilator 1. Server 7 can also send information, data, and / or configurations to the ventilator 1. Inputs such as data, information, and configurations can be entered into Server 7 by a user via the computer and / or input device and then forwarded to the ventilator 1.

[0066] For a more detailed, exemplary explanation of the procedure, it is assumed that a connection already exists between the ventilator 1 and the server 7. Data is sent from the ventilator 1 to the server 7 via the communication unit 3. This data includes, for example, technical and medical data of the ventilator. Technical data can include, for example, the firmware version, ventilator settings, fill level and / or wear of consumables, occurrence of technical errors, etc. In some embodiments, this technical data is determined in particular by the monitoring unit 65. Medical data includes, for example, the usage times and duration of the ventilator, the effectiveness of the ventilator, its correct use, as well as diagnostic and / or therapy-related data, such as ventilation pressures, respiratory rate, flow data, and the temperature of the patient and / or the breathing air.In addition, further medical data, not mentioned here, can also be transferred from ventilator 1 to server 7.

[0067] Once all data requested by Server 7 has been transmitted and no further data and / or configurations are to be sent from Server 7 to the ventilator 1, Server 7 or a user / operator on Server 7 can decide to terminate the data transmission, at least of the medical data, and subsequently, if necessary, also disconnect the connection to the ventilator 1. Before Server 7 disconnects the connection to the ventilator 1, at least configuration data for communication is transmitted, which specifies at least the time interval after which the ventilator 1 should establish the next connection to Server 7. In an alternative or additional embodiment, the ventilator 1 can also automatically determine when to establish the next connection to Server 7, for example, based on an analysis of the medical data by the reprocessing unit or via input through the user interface 5.Server 7 and / or ventilator 1 decide, for example, based on the data or data volume sent from ventilator 1 to server 7 during the current connection, or the transmission time, the time interval until the next connection. With continuous data transmission of at least medical data, i.e., "live" monitoring of ventilator 1, the time interval until the next connection can range from 1 to 360 minutes or even up to 7 days. For example, server 7 can use the transmitted medical data to determine the quality of ventilation or the patient's condition with regard to ventilation and / or therapy, and then decide whether further continuous data transmission and thus monitoring of ventilator 1 is necessary.The shorter connection and data transfer intervals between ventilator 1 and server 7 can, for example, serve to avoid continuous monitoring while allowing for periodic checks of the patient's condition. It is also conceivable that, if the patient's condition remains good and / or ventilator 1 continues to be used, the connection and data transfer intervals could gradually increase until, for example, 1 to 7 days separate the connections. When transmitting a data packet, such as a summary of data from the period since the last connection, a time interval of 1 to 7 days could be specified. For instance, a daily or weekly summary of ventilator 1's data could be requested from and received by server 7.In some embodiments, for example, it is possible that data transmission can only be terminated properly by server 7. A non-proprietary way to terminate data transmission would be, for example, disconnecting the power supply to ventilator 1 or forcibly disabling the data connections of ventilator 1.

[0068] After the connection between Server 7 and Ventilator 1 is interrupted, Ventilator 1 waits the specified time interval and then reconnects to Server 7. This connection is only established if Ventilator 1 is capable of doing so, meaning it has a power supply (e.g., from the local power supply) and a data connection. A distinction can therefore be made between connection-enabled and non-connection-enabled modes. A connection-enabled mode occurs, for example, when sufficient power is available (e.g., from a local power supply or a sufficiently charged battery) and a data connection is available. A non-connection-enabled mode occurs, for example, when Ventilator 1 is in so-called airplane mode, meaning all data connections are deactivated and unavailable.Such an airplane mode is activated during therapy, particularly during sleep therapy, to prevent the patient from being additionally affected by radio waves. In some cases, it may also be desirable to enable a data connection during therapy, for example, for live monitoring. This can be achieved using a wired data connection or by activating wireless data connections. In some models, the ventilator 1 also automatically detects whether sufficient power is available. For example, data connections can be restricted or deactivated as soon as the ventilator 1 is disconnected from the mains power supply. Additionally or alternatively, data connections can also be deactivated when the battery level is low (e.g., below 50%, 30%, or 15%).Depending on the quality of the data connection, it is conceivable, for example, that the amount of data to be transmitted is adjusted by ventilator 1 and / or server 7; for instance, less data is transmitted with weaker data connections. Furthermore, prioritizing the data to be transmitted according to the power supply and the data connection is also conceivable.

[0069] In some embodiments, establishing a connection between the ventilator 1 and the server 7 is only possible via the communication unit 3. Therefore, a connection can only be established if the ventilator 1 or a user / operator / patient at the ventilator 1 initiates a connection.

[0070] With each new connection established to server 7, ventilator 1 always sends basic information / device information, such as the device type, serial number, firmware version, and possibly other device information, to server 7. In addition to the described step for identifying ventilator 1, further procedures for authentication or securing the connection can also be performed before further data transmission between server 7 and ventilator 1 begins. In some embodiments, these additional authentication and security steps can also be performed before the basic information of ventilator 1 is transmitted to server 7.

[0071] Based on the transmitted basic information, Server 7 can recognize / identify ventilator 1 and decide individually whether and what type of data transmission is requested, as well as which specific data should be transmitted from ventilator 1 to Server 7. For this purpose, Server 7 stores, for example, for each individual ventilator (known to Server 7), the data to be requested, the configurations to be sent to the ventilator, and the time intervals at which the ventilator should connect to Server 7. Server 7 thus compares the identified ventilator 1 with the stored ventilators and sends the corresponding configuration data, as well as any data transmission request from ventilator 1 to ventilator 1.As requested, ventilator 1 begins transmitting data to server 7, at least until server 7 terminates the transmission. During data transmission, medical and / or technical configuration data, and / or communication configuration data, can also be transmitted to ventilator 1. Medical configuration data includes, for example, therapy settings such as ventilation pressures, flow rates, duration, and other parameters. Technical configuration data includes, for example, data relating to the technical function of ventilator 1 itself, such as a firmware update. Communication configuration data includes, for example, settings for the amount of data to be transmitted, data types, and / or time intervals at which ventilator 1 should connect to server 7.In some embodiments, server 7 always transmits at least the time interval after which the ventilator 1 should reconnect to server 7.

[0072] In some configurations, server 7 can automatically request data from ventilator 1, specifically requesting the transmission of medical data from the ventilator 1. For example, server 7 can automatically request medical data from ventilator 1 after a set time interval each time the ventilator 1 connects to it, without requiring any explicit prior configuration by a user on server 7. As described, server 7 can also automatically determine, based on the transmitted medical data, whether further medical data should be transmitted and / or when the next data transmission should occur. If server 7 does not request any medical data from ventilator 1, no medical data will be transmitted from ventilator 1 to server 7.While in some embodiments the Server 7 decides on the transmission of medical data completely automatically, in other embodiments it is provided that a user of the Server 7 can at least manually request individual data transmissions.

[0073] In some exemplary embodiments, data transmission between server 7 and ventilator 1 is terminated by an input on server 7 and / or an input on ventilator 1. It is also conceivable that a connection is established independently of the set time interval by inputs on both server 7 and ventilator 1. In some embodiments, ventilator 1 can also automatically establish a connection to server 7 and begin data transmission independently of the set time interval. This can occur, for example, if the measured values ​​and data acquired by sensor unit 62 and evaluated by processing unit 63 indicate a deterioration in the patient's condition and / or the quality of ventilation.This can be detected, for example, by exceeding or falling below threshold values ​​related to respiratory rate, pressures, and / or flows, and / or leakage, and / or therapy adherence, and / or a deterioration in synchronization between the device and the patient, and / or detection of intrinsic PEEP in the patient, and / or changes in CO2, SpO2, sleep quality, temperature, or patient activity. Server 7 can also automatically adjust the time intervals at which a connection should be established between ventilator 1 and Server 7 based on an analysis of the medical data transmitted by ventilator 1. For example, Server 7 might assess a substantially consistent quality of ventilation and increase the time intervals at which ventilator 1 establishes a connection to Server 7 and requests data transmission from Server 7.Server 7 can detect consistent ventilation quality based on the medical data transmitted by ventilator 1. Consistent ventilation quality can be detected, for example, if the respiratory parameters, such as pressure, flow, and / or frequency, show essentially no fluctuations and / or do not exceed or fall below threshold values. Conversely, if fluctuations or deviations in respiratory parameters and / or threshold values ​​are detected, then, in addition to the corresponding adjustment of the ventilation parameters by control unit 4, server 7 can also shorten the time intervals.On the one hand, it is conceivable that ventilator 1 has already evaluated the data through processing unit 63, so that the information on the quality of ventilation is sent directly to server 7, and server 7 can then decide on further data transmissions based on this information. On the other hand, it is also possible, for example, that server 7 itself evaluates the medical data from ventilator 1 with regard to the quality of ventilation and then decides on further data transmissions and connections.

[0074] If no connection is established between ventilator 1 and server 7 after the set time interval, this is registered by both ventilator 1 and server 7. After a certain number of failed connections, server 7 and / or ventilator 1 can generate an alarm message indicating the failed connections. Server 7 may also initiate a connection attempt to ventilator 1 if no connection has been established for an extended period.

[0075] In some configurations, the ventilator 1 automatically shortens the time interval until the next connection with server 7 if a connection cannot be established after the regular time interval. For example, if the original time interval is 24 hours, for instance, to transmit a usage summary of the previous day to the server, but the connection to server 7 fails after 24 hours, the ventilator 1 attempts to establish a connection again after a shortened time interval of, for example, 1 hour, before an alarm message is generated after a certain number of failed attempts.

[0076] If no continuous data transmission, i.e., "live" monitoring or real-time monitoring, takes place, the values ​​and data determined by the sensor unit 62 in the monitoring unit 65 and the data processed by the processing unit 63 are at least temporarily stored in the storage unit 64 and, if requested by the server 7, transmitted to the server with the next data transmission.

[0077] In some exemplary embodiments, the transmission of medical data only takes place if this data is explicitly requested by server 7.

[0078] It is also conceivable that the transmission is permanently terminated. This is advantageous if, for example, ventilator 1 changes users and is reconfigured or adjusted. In this case, it can be beneficial to permanently disconnect device 1 from server 7. Server 7 can permanently deactivate ventilator 1. For example, server 7 might deactivate a SIM card within device 1. Reference symbol list

[0079] 1 Ventilator 2 Input unit 3 Communication unit 4 Control unit 5 User interface 7 Server 61 Blower / valve unit 62 Sensor unit 63 Reprocessing unit 64 Storage unit 65 Monitoring unit

Claims

1. A method for data transmission within a system, wherein the system comprises at least one ventilator (1) and a server (7), wherein the ventilator (1) comprises at least one input unit (2) and at least one communication unit (3), wherein the input unit (2) is configured and designed to provide entered values and information to the system, and wherein the communication unit (3) is configured and designed to establish at least one connection to at least one server (7) and to transfer data between the server (7) and the ventilator (1), i.e. to send to the server (7) and to receive from the server (7), wherein the data transmission is terminated by the server (7) such that no further medical data are transmitted from the ventilator (1) to the server (7), wherein technical data of the ventilator (1) are transferred between the server (7) and the ventilator (1) independently of the data transmission of the medical data, wherein the data transmission from the communication unit to the server is automatically terminated by the server based on an analysis of the medical data previously transmitted by the ventilator, wherein the medical data comprise at least one of the following parameters: diagnostic data from the ventilator, pressure, flow, respiratory rate, volumes, O2 / CO2 saturation, O2 / CO2 content of the breathing air, usage times of the ventilator, effectiveness of the ventilator, effectiveness of the therapy, correct use of the ventilator, wherein, upon termination of the data transmission between the server (7) and the ventilator (1), the connection between the server (7) and the ventilator (1) is disconnected, wherein the server (7), prior to disconnection of the connection, transmits to the ventilator (1) at least configuration data for communication, which specify at least one time interval after which the ventilator (1) is to establish the next connection to the server (7), wherein the ventilator (1), also establishes a connection to the server (7), regardless of the preset time interval, and initiates data transmission when the measured values and data acquired by a sensor unit (62) of the ventilator (1) and evaluated by a processing unit (63) of the ventilator indicate a deterioration in the quality of the ventilation.

2. The method according to at least one of the preceding claims, characterized in that the connection between the ventilator (1) and the server (7) is established exclusively by means of the communication unit (3), wherein, when the connection is disconnected, the communication unit (3) connects to the server (7) at time intervals.

3. The method according to at least one of the preceding claims, characterized in that the server (7) transmits configuration data for communication to the ventilator (1), wherein the configuration data for communication comprise settings relating to the amount of data that are to be sent from the ventilator (1) to the server (7) during the data transmission and / or during the connection, and settings relating to the time periods at which the ventilator (1) is to connect to the server (7).

4. The method according to at least one of the preceding claims, characterized in that no medical data are transmitted from the ventilator (1) to the server (7) unless said medical data are requested by the server (7), wherein the transmission of the data between the ventilator (1) and the server (7) is initiated by an action command from the server (7) to the communication unit (3).

5. The method according to at least one of the preceding claims, characterized in that the communication unit (3) and / or the server (7) generate or trigger an alarm signal when a determined number of connections of the communication unit (3) to the server (7) that fail to occur within the specified time intervals or are unsuccessful are registered.

6. The method according to at least one of the preceding claims, characterized in that the connection of the communication unit (3) to the server (7) is automatically disconnected by the server (7) based on an analysis of the previously transmitted data.

7. The method according to at least one of the preceding claims, characterized in that the data transmission from the communication unit (3) to the server (7) is terminated by the server (7) after an input at the server (7) and the connection of the communication unit (3) to the server (7) is disconnected by the server (7) after an input at the server (7).

8. The method according to at least one of the preceding claims, characterized in that data from the ventilator (1) are recorded and stored until the next connection to the server (7).

9. The method according to at least one of the preceding claims, characterized in that the ventilator (1) evaluates and / or aggregates the stored data, and wherein said evaluated or else aggregated data are transmitted in the course of a new transmission of data to the server (7) to the extent that said data are requested by the server (7).

10. The method according to at least one of the preceding claims, characterized in that the configuration data for communication comprise settings as to whether data are to be transmitted with a high level of detail or whether exclusively evaluated and / or aggregated data are to be transmitted.

11. A system comprising at least one ventilator (1) and a server (7), wherein the ventilator (1) comprises at least one input unit (2) and at least one communication unit (3), wherein the input unit (2) is configured and designed to provide entered values and information to the system, and wherein the communication unit (3) is configured and designed to establish at least one connection to at least one server (7) and to transfer data between the server (7) and the ventilator (1), i.e. to send to the server (7) and to receive from the server (7), wherein the data transmission is terminated by the server (7) such that no further medical data are transmitted from the ventilator (1) to the server (7), wherein technical data of the ventilator (1) are transferred between the server (7) and the ventilator (1) independently of the data transmission of the medical data, wherein the data transmission from the communication unit to the server is automatically terminated by the server based on an analysis of the medical data previously transmitted by the ventilator, wherein the medical data comprise at least one of the following parameters: diagnostic data from the ventilator, pressure, flow, respiratory rate, volumes, O2 / CO2 saturation, O2 / CO2 content of the breathing air, usage times of the ventilator, effectiveness of the ventilator, effectiveness of the therapy, correct use of the ventilator, wherein, upon termination of the data transmission between the server (7) and the ventilator (1), the connection between the server (7) and the ventilator (1) is disconnected, wherein the server (7), prior to disconnection of the connection, transmits to the ventilator (1) at least configuration data for communication, which specify at least one time interval after which the ventilator (1) is to establish the next connection to the server (7), wherein the ventilator (1), also establishes a connection to the server (7), regardless of the preset time interval, and initiates data transmission when the measured values and data acquired by a sensor unit (62) of the ventilator (1) and evaluated by a processing unit (63) of the ventilator indicate a deterioration in the quality of the ventilation.

12. A ventilator (1) of the system according to claim 11 configured according to the method of claim 1.