Medical device with interface

Abstract

Ventilator (1) with at least a sensor for detecting at least one parameter of a breathing gas, a control device for specifying settings, a storage unit a control unit connected to the storage unit, a first computer program product for implementing the settings taking into account a specification and a second computer program product that regulates data transfer to and from the control unit via at least one interface (8); wherein the ventilator (1) is designed such that at least one interface allows for the mutual exchange of data between the ventilator (1) and external storage media and / or devices (12), the exchange of parameters, and the loading of parameters and / or a configuration of the ventilator from external storage media and / or devices, wherein the ventilator has at least two interfaces that support different standards and communication protocols, wherein one of the interfaces is designed as a radio interface and another of the interfaces is designed as a memory card interface, wherein the memory card interface is suitable for a Secure Digital card, a Multimedia card, a Memory Stick PRO card, an xD-Picture card, a SmartMedia card or a CompactFlash card, where data from the ventilator can be saved to an inserted memory card via the memory card interface, and data from an inserted memory card can be loaded into the ventilator, where, in the area of ​​the ventilator, a firmware or software is installed as the second computer program product, which runs as a client and enables a connection of the ventilator to the Internet, where the client is responsible for initiating contact during data transmission and is configured to determine the timing of the transmission, where reading or saving ventilation and usage information to the respective storage medium must be initiated by an event, and the event is the expiration of a specific period of time since the start or end of ventilation therapy, where, when reading usage data from the ventilator, an assignment to the correct patients is automatically performed via a stored database. wherein the ventilator contains relevant information about its setting parameters and their setting limits as well as its stored therapy information and is designed to make the relevant information available to a PC, wherein the ventilator is configured to provide, via the respective interface or storage medium, an application directly executable by a PC operating system, wherein the ventilator contains executable logic in non-volatile memory, wherein the executable logic is not executable by the ventilator itself but by the PC, thus enabling the installation of software on the PC without requiring a user to obtain the software directly from the ventilator manufacturer or a service provider via CD, download, or storage medium. wherein the ventilator further comprises a data cable as a data exchange means inserted into the respective interface, wherein the data cable is connected to an interface converter outside the ventilator, wherein the interface converter is designed to enable communication between the ventilator and another device via at least one transmission standard not provided in the ventilator itself, wherein at least one additional sensor in the form of a pulse oximeter and / or a sensor for CO2 measurement and / or a sensor for measuring respiratory effort and / or an ECG device and / or an EEG device is additionally connected to the ventilator via the interface converter.

Description

[0001] The present invention relates to a ventilator with an interface for data exchange.

[0002] If a doctor or medical supply store needs to check or change the settings of a ventilator, they currently need to have the device physically present. If a patient's ventilator settings need to be monitored or adjusted as continuously as possible, the patient must either remain in the hospital or visit a doctor regularly.

[0003] Similarly, if the software / firmware needs to be updated, the patient will have to go to the doctor, specialist retailer or hospital to have the update installed.

[0004] Even when a device is replaced, for example due to a defect, the new device currently needs to be reconfigured for the patient. This requires the settings to be adjusted by the doctor or specialist retailer.

[0005] The applicant's SOMNOcomfort or SOMNOvent CR ventilators, for example, use an RS 485 serial interface to read respiratory data from the device and, if necessary, visualize it on a PC. However, to adjust the ventilation parameters, the physician must change the settings directly on the device.

[0006] This increases the costs of healthcare and significantly restricts the daily lives of patients who either have to stay in hospital or need to see a doctor very frequently.

[0007] There is a need to simplify or eliminate the described processes in order to relieve the burden on doctors and specialist retailers and thus save costs.

[0008] German patent DE 10 2007 039 004 A1 discloses a medical device with at least one sensor for detecting at least one parameter of a respiratory gas. It uses an operating device for setting parameters. Furthermore, a control unit is used to implement these settings and to coordinate data transfer. US patent 6,558,321 B1 discloses a remote monitoring system that includes a medical device, a docking station, and a receiver. DE 103 50 538 A1 discloses a medical device that can communicate directly with a server. Further devices and methods for configuring medical devices are described in US patent 2007 / 0055799 A1, DE 165 580 A1, and DE 10 2004 042 797 A1.

[0009] The object of the present invention is to provide a ventilator that enables data transfer between the ventilator and external storage media and / or devices, whereby data from the ventilator can be exchanged in a simplified and secure manner.

[0010] The problem is solved by the features of the claims of the present application.

[0011] The ventilator is designed to generate at least one inspiratory and one expiratory pressure profile in the patient's airways. These pressure profiles can be constant and identical (CPAP), constant and different (IPAP / EPAP), or time-varying. A pressure profile (e.g., a ramp) can also be predefined or stored in the device during the transition between the inspiratory and expiratory pressure profiles. In a preferred embodiment, the pressure profiles are automatically controlled by the device based on at least one of the following parameters: - Breathing phase - Respiratory rate - Lung volume - Maximum airflow - Oxygen saturation - CO2 or pH value - Breathing effort - Respiratory stability.

[0012] Regulating pressure patterns stabilizes breathing, meaning that both short-term breathing fluctuations (apneas, hypopneas, Cheyne-Stokes cycles) and long-term breathing fluctuations (hypoventilations, respiratory insufficiencies) are treated.

[0013] In a particularly preferred embodiment, the device also automatically determines the times for the transition from the inspiratory to the expiratory pressure profile, as well as from the expiratory to the inspiratory pressure profile. This is done either based on a signal related to the patient's airflow or after predefined times, or times automatically adapted to the patient's breathing, have elapsed since the last transition from the inspiratory to the expiratory or expiratory to the inspiratory phase.

[0014] At least one interface allows for the reciprocal exchange of device data between the ventilator and external storage media and / or devices. Furthermore, ventilation parameters can be exchanged reciprocally, and ventilation parameters and / or the ventilator configuration can be influenced by external storage media and / or devices.

[0015] Data exchange can be carried out, for example, using a data cable, a USB stick, a radio module or a memory card, which are inserted into the interface.

[0016] In addition to the data cable, an interface converter can be provided outside the ventilator, which is connected to the ventilator via the data cable. The interface converter enables communication between the device and another device and / or PC via at least one transmission standard not provided in the device itself, e.g.: analog signal channels, Ethernet, radio connection, USB, FireWire, storage medium, USB OTG, cellular communication (e.g., UMTS, GSM, HSDPA), eSATA, ExpressCard, PCMCIA, RS232, RS485. According to the invention, at least one of these interfaces can also be implemented in the ventilator itself. However, the interface converter allows for the expansion of communication options at a later stage after the device's production, without requiring medical or technical personnel.

[0017] Additional sensors can be connected to the ventilator via the interface converter, e.g. a pulse oximeter, CO2 measurement, a sensor for respiratory effort and / or an ECG / EEG.

[0018] The functionality of the device can also be extended by using a microcontroller or memory in the interface converter. In a preferred embodiment, the interface converter includes titration logic for a CPAP or BiLevel device.

[0019] It is advantageous to install firmware or software in the area of ​​the ventilator that runs as a server and enables the ventilator to be connected to the Internet.

[0020] In one embodiment, the server waits for a client program to initiate contact and exchanges data after establishing contact. This contact is typically triggered by an event. Triggering events can include, among others: - A data connection is being established - A preset or specified time interval has expired. - A therapy-related event is detected, e.g., the start or end of therapy, the occurrence of a breathing disorder or leakage. - Contact is initiated manually by the user.

[0021] Alternatively, firmware or software is installed on the ventilator that runs as a client and enables the ventilator to connect to the internet. In this case, the client is responsible for initiating contact and determining the timing of data transmission.

[0022] It is also intended that the client functions as a web browser, which contacts a web server and requests a website from it, and may display the requested website.

[0023] Furthermore, the ventilator is designed to contain relevant information about its settings and their limits, as well as its stored therapy information, and to make this information available to a display device (e.g., PC and / or PDA with a web browser). This eliminates the need to prepare the display device before its first use with the ventilator, for example, by installing software.

[0024] This can preferably be achieved by the device providing its therapy information or setting parameters via the interface, storage medium, or interface converter in a data format understood by computers with standard office configurations, e.g., XML, HTML, CSV. Alternatively, this can be achieved by the ventilator providing an application via the interface or storage medium that can be executed directly by the operating system of a PC or PDA. According to the invention, the ventilator contains executable logic in non-volatile memory that can be executed not by the ventilator itself, but by a PC. In a preferred embodiment, this is a plug-in for PC software, a configuration file, or a Windows or .NET application.This allows the ventilator to install software on the PC without the user having to obtain it directly from the ventilator manufacturer or a service provider via CD, download or storage medium.

[0025] It is also conceivable that the ventilator is supplied as a client by an access point in a wireless network.

[0026] In one implementation, communication between server and client takes place according to the peer-to-peer principle.

[0027] According to the invention, data is transferred using the Hypertext Transfer Protocol (HTTP) or HTTPS, or using FTP or SFTP or SMTP or ESMTP or POP3 or IMAP or TCP / IP or standardized USB standards.

[0028] Remote data is processed via a client using NFS (Network File System) or SMB.

[0029] Data can also be transferred from the ventilator to a printer via LPR (Line Printer Protocol) or LPD (LPD Protocol) or PictBridge or IrDA or XHTML or Bluetooth Basic Printing Profile or DPOF or UPnP and printed immediately.

[0030] Alternatively, the interface or interface converter can be configured as a USB slave / device interface and, for example, support the USB mass storage protocol.

[0031] In a preferred embodiment, the device is provided to support various services or protocols via the interface or interface converter, which can be selected by the user, e.g. at the human-machine interface of the ventilator, or which are automatically selected by the ventilator depending on the communication counterpart.

[0032] According to the invention, it is also provided that the ventilator or the interface converter has at least two interfaces that support different standards and communication protocols, e.g. USB and Ethernet or USB host and device or USB and memory card or mobile communication and USB.

[0033] According to the invention, at least one interface is designed as a memory card interface suitable for an SD (Secure Digital) card, micro SD card, an MMC (MultiMedia) card, an MS PRO (Memory Stick PRO) card, an XD (eXtreme Digital Picture) card, an SM (SmartMedia) card, or a CF (CompactFlash) transfer interface. Data from the ventilator can be saved to the memory card via this interface, and conversely, data can also be loaded from an inserted memory card into the ventilator.

[0034] The data preferably represents the configuration information for the ventilator, whereby the configuration information is transferable to and executable on a ventilator. The configuration information contains at least one of the following parameters: - Patient identification (e.g., name, date of birth, identification key) - Device (type) identification (e.g. serial number) - Ventilation pressure (IPAP, EPAP, EEPAP, CPAP, ...) - Limits for ventilation pressures that are automatically set by the device - Background ventilation rate - I:E ratio - Minimum breathing volume - Ventilation mode - Settings for a breathing humidifier - Time intervals for maintenance or therapy monitoring - Logic for the permissible combinations and value ranges of ventilation parameters - Logic for device control, e.g., the transfer of new program parts or the entire device software as an update to the device, is a special case of device configuration according to the invention.

[0035] The interface is preferably implemented as a USB interface, Ethernet interface, radio interface or a storage medium.

[0036] To prevent injuries to the user due to electrical voltage, the ventilator or interface converter incorporates galvanic isolation of the signal lines. The ventilator or interface converter is powered during data transmission either by at least one medically approved power supply or a portable energy storage device (e.g., rechargeable battery, battery, capacitor).

[0037] If configuration information is read in via a storage medium, additional backup mechanisms are required to prevent misconfigurations.

[0038] Preferably, it is checked whether the respective user is allowed to make the configuration at the respective time and whether a second configuration is taking place simultaneously via another interface.

[0039] The integrity of the configuration information is also preferably checked. This includes at least one of the following checks: - Is the configuration information usable for the type of ventilator? - Is the configuration information intended for the specific device and / or patient? - Is the configuration information complete, undamaged, untampered with, consistent, and does it contain no impermissible value combinations?

[0040] It is also preferred that the user can and / or must confirm or trigger the transfer of the configuration information to the device.

[0041] It is also preferably provided that in the event of errors or an interruption during the reading of the configuration information, the ventilator continues to have a suitable configuration, preferably the one before the start of the reading of the configuration information.

[0042] It is also preferred that the ventilator generate a visual or audible message indicating the occurrence of an error during the configuration process, in order to alert the user. It is provided that different error types can be distinguished and that, depending on the error type, the device can generate at least two different messages.

[0043] It is also preferred that, in the event of errors during the configuration process, the ventilator sends at least one piece of information about the occurrence and type of error via at least one interface or interface converter.

[0044] It is also preferably provided that, if an error occurs during the configuration process, the ventilation therapy can only be continued once the user has confirmed, through interaction with the device, that they have perceived the occurrence of the error. According to the invention, this can be achieved by pressing a button on the device or by receiving information via at least one interface or the interface converter.

[0045] It is also preferred that the user be informed about changes to the ventilation configuration via at least one interface and that the change be stored in at least one data storage device.

[0046] It is also preferred that the configuration information on the storage medium be deleted after being read by the ventilator. This prevents the configuration for a specific patient from being unintentionally transferred to other patients' ventilators, or from being transferred again to the patient's ventilator at a later time if it has already been deliberately changed by the user via a different interface, storage medium, or device controls.

[0047] It is also preferred that the configuration information on the storage medium is not deleted after being read by the ventilator, but can be used for several ventilators successively without the need to connect the devices or storage medium to a PC and / or PDA. This allows, for example, specific initial configurations for particular use cases to be easily copied to a large number of devices.

[0048] Therefore, according to the invention, the configuration contains information about whether it is intended for only one specific ventilator of a patient or for at least two ventilators.

[0049] Furthermore, according to the invention, at least one parameter of the device configuration contains information about whether the parameter may be changed after transmission of the device configuration by certain users, e.g., by the patient himself, via an interface or controls of the device or a storage medium.

[0050] According to the invention, the configuration contains information about whether it was created by the patient or other laypersons, or by medical or technical personnel, or whether it was written to the storage medium or sent to the ventilator via the interface or interface converter. At least one ventilation parameter is accepted by the ventilator only if its value was entered by medical or technical personnel.

[0051] Furthermore, the invention provides that the device configuration can not only be read from the storage medium by the ventilator, but that the ventilator can also save a device configuration to the storage medium. This allows another ventilator to be configured identically, for example, if the patient's ventilator needs to be replaced.

[0052] The interface is preferably implemented as a USB or Ethernet interface, which, together with a memory card interface, is located within the ventilator. An interface circuit provides a function for transferring data between multiple storage devices within the ventilator. Specifically, data is transferred from the storage media (USB and memory card) to the ventilator and vice versa.

[0053] The device contains at least 3 different storage units: - An internal, volatile memory (RAM) - An internal, non-volatile memory (program, data, and configuration memory) - An optional, removable, non-volatile storage device (memory card, USB stick)

[0054] In at least one operating mode, data is redundantly stored on several of these three storage units. A microcontroller ensures that the contents of the three storage units are synchronized. In particular, the goal is to ensure that the data is consistent and free of contradictions at all times.

[0055] An interface circuit switches between the memories via a manual mode of the circuit and / or switches automatically via an installed control chip.

[0056] The ventilation and usage data stored in the device, which can be read out via one of the aforementioned interfaces, contains at least one of the following parameters: - Usage time in general and in certain modes - Respiratory events - Indices or numbers of breathing events - Accessories used - Used setting parameters of device and accessories - Times - Leaks - Sleep stages - SpO2 and / or CO2 - Arousals - Breathing volume and / or breath flow - Information related to the breathing phase trigger - Respiratory rate - ECG signals or parameters calculated from them - Pulse wave signals or parameters calculated from them - Heart rate - Signals related to respiratory effort - Signals related to airway compliance and resistance - Snoring - User input, e.g. regarding therapy quality

[0057] The ventilator according to the invention can save all settings relating to ventilation parameters or device configuration in at least one file. This allows the settings to be quickly and easily restored at a later time, for example, in the event of a power outage or if the settings need to be transferred to a different ventilator. This may be necessary, for example, when the current device is being serviced and the patient receives a replacement device.

[0058] The saved settings can also be transferred and loaded directly onto another ventilator, particularly via an infrared interface, near-field communication, or a data cable. For this to work, the hardware and firmware of both devices must be compatible.

[0059] Wireless communication between an external device and the ventilator is preferred.

[0060] According to the invention, it is possible to read data from the ventilator and configure the ventilator without needing to connect it to the power grid.

[0061] This is solved according to the invention by the fact that the device contains an energy storage device (e.g. battery, accumulator, capacitor) which supplies energy to the at least 2 storage units, the interface used and at least one microcontroller during data communication.

[0062] Alternatively, it is envisaged that the data cable could supply power to at least two storage units, the interface used, and at least one microcontroller during data communication. This is possible, for example, via the USB standard or through additional power supply wires in the data cable.

[0063] Alternatively, it is envisioned that energy can be supplied to at least two storage units, the interface used, and at least one microcontroller during data communication via contactless energy input (electromagnetic radiation). The energy required for communication can also be generated from a combination of energy storage, data cable, and electromagnetic radiation.

[0064] The invention also provides for the automatic assignment of usage data or biosignals from the device or accessories – e.g., using a PC – to the correct patient via a stored database. This simplifies processes and prevents mix-ups.

[0065] The invention also provides for the wireless retrieval of usage data or biosignals from the device or accessories – and even without a mains power supply. This saves time, as the device or accessories can be read directly from their carrying case without opening, removing, or connecting power and data cables.

[0066] The invention is not only relevant for accessories and sensors, but also for therapy and diagnostic devices, for example, in simplified logistics during warehousing. Device type and serial number can be read contactlessly. The advantage over barcodes is that devices can be identified even when carried in a pocket. This simplifies processes and prevents mix-ups if the device is accidentally swapped between pockets.

[0067] RFID is just one conceivable embodiment. Others would be Z-Wave or Zigbee. Each of the radio transmission methods used in the invention requires little energy to send information, so that either no power supply is necessary at all or a mobile power supply (battery, battery, button cell, capacitor, fuel cell) is sufficient for a very long period of time.

[0068] According to the invention, the reading and saving of ventilation and usage information to the storage medium must be triggered by an event. Possible events include: - Pressing a button (or touching a display) on the device or on the interface converter - Start or end of ventilation therapy - Expiration of a specific period of time since the start or end of ventilation therapy - Occurrence of a specific time or date - Occurrence of a specific therapeutic event - Connecting the device to a power supply - Connecting the device to a storage medium - Voice input on the device - Connecting the device to a counterpart via the interface or interface converter - Triggering data transmission at the remote location

[0069] According to the invention, it is also intended that the reading out of the ventilation and usage information or the saving of the ventilation and usage information on the storage medium can be terminated or interrupted by an event of the aforementioned type.

[0070] According to the invention, it is also intended that the device can distinguish at least 2 different levels of detail in ventilation and usage information and, depending on the event of the aforementioned type, selects a specific level of detail for sending the information via at least one interface or interface converter or for storing the information on the storage medium.

[0071] Preferably, the ventilator generates a visual or audible message indicating an error when transmitting or saving ventilation and usage information, in order to alert the user. It is intended that different error types can be distinguished and that the device can generate at least two different messages depending on the error type.

[0072] The drawings schematically illustrate exemplary embodiments of the invention. They show: Fig. 1. a basic structure of a device for ventilation, Fig. 2. A schematic representation of the data transfer process, Fig. 3a a flowchart for storing and transferring settings and Fig. 3b a representation accordingly Fig. 3a regarding the storage and transmission of ventilation and therapy data.

[0073] Fig. Figure 1 shows the basic structure of a ventilation device. A breathing gas pump is arranged inside a device housing (1) with a control panel (2) and display (3). A connecting hose (5) is attached via a coupling (4). The device housing (1) has an interface (8) to enable data transmission. An exhalation element (6) is arranged in the area of ​​an extension of the connecting hose (5) facing away from the device housing (1).

[0074] Fig. Figure 1 further shows a user interface (7) designed as a nasal mask. It can be secured to the user's head using a head covering (10). The ventilation mask (7) has a connection port (11) on the side facing the connecting tube (5).

[0075] To transfer energy through the space, a reader (not shown) is integrated into the breathing gas delivery device. To prevent the airways from drying out, humidifying the breathing air is particularly advantageous during prolonged ventilation. Such humidification of the breathing air can also be implemented in other applications. For humidification, adaptable breathing air humidifiers (9) are typically inserted into the airway of the device that delivers fresh breathing gas to the nasopharynx and oral cavity of the user.

[0076] Fig. Figure 2 schematically illustrates the data transfer process from the ventilator (1) via at least one interface (8) to external storage media and / or devices (12). Ventilation parameters and / or the device configuration can be stored. Ventilation parameters and / or the ventilator configuration can also be loaded from external storage media and / or devices. This enables bidirectional data exchange.

[0077] In addition, patient data not directly related to device configuration can be stored on the storage medium and read into the therapy device. This data can include patient information (age, address, name, gender) that facilitates easier and more accurate identification of retrieved usage data later on. Alternatively, it is also possible to store findings and diagnostic data that are helpful for follow-up examinations and evaluating therapy success.

[0078] Fig. Figure 3 shows a flowchart for saving / transferring settings. According to Fig. 3. The user proceeds as follows: 1. In the user interface, select the menu item "Data Transfer". 2. Then, select which data should be transferred: ventilation settings, device configuration, patient data, compliance data. 2. Next, the destination is selected: memory card, USB, floppy disk, CD, other ventilator, PC, data server 3. If applicable, the transmission method is set: Infrared, Near Field Radio, (W)LAN, Data Cable 4. Finally, the user confirms their selection "Save settings" and the data transfer or saving of the data begins. 5. Alternatively, data transfer can also be started automatically as soon as a device is connected or a storage medium is inserted.

[0079] To implement / access settings, the user proceeds as follows: 1. In the user interface, select the menu item "Load data". 2. Then, select which data should be loaded: ventilation settings, device configuration, patient data, compliance data. 3. Next, the source is selected: memory card, USB, floppy disk, CD, other ventilator, PC, data server 4. If necessary, the transmission method is set: Infrared, Near Field Radio, (W)LAN, Data Cable 5. Finally, the user confirms their selection "Load data" and the data is loaded.

[0080] Standard settings for specific recurring ventilation situations are stored in the ventilator's memory. For example, the physician can select ventilation settings that are typically suitable for the therapy of their diagnosis. The physician can also save and recall their own custom settings, which can then be transferred.

[0081] Further, more specialized settings are stored securely, for example, on an external FTP server. These settings can be loaded into the ventilator's memory after it connects to the server.

[0082] The current configuration is also stored in the ventilator's memory. When changes are made to the configuration, a prompt appears asking whether the changes should be saved.

Claims

[1] Ventilator (1) with at least a sensor for detecting at least one parameter of a breathing gas, a control device for specifying settings, a storage unit a control unit connected to the storage unit, a first computer program product for implementing the settings taking into account a specification and a second computer program product that regulates data transfer to and from the control unit via at least one interface (8); wherein the ventilator (1) is designed such that at least one interface allows for the mutual exchange of data between the ventilator (1) and external storage media and / or devices (12), the exchange of parameters, and the loading of parameters and / or a configuration of the ventilator from external storage media and / or devices, wherein the ventilator has at least two interfaces that support different standards and communication protocols, wherein one of the interfaces is designed as a radio interface and another of the interfaces is designed as a memory card interface, wherein the memory card interface is suitable for a Secure Digital card, a Multimedia card, a Memory Stick PRO card, an xD-Picture card, a SmartMedia card or a CompactFlash card, where data from the ventilator can be saved to an inserted memory card via the memory card interface, and data from an inserted memory card can be loaded into the ventilator, where, in the area of ​​the ventilator, a firmware or software is installed as the second computer program product, which runs as a client and enables a connection of the ventilator to the Internet, where the client is responsible for initiating contact during data transmission and is configured to determine the timing of the transmission, where reading or saving ventilation and usage information to the respective storage medium must be initiated by an event, and the event is the expiration of a specific period of time since the start or end of ventilation therapy, where, when reading usage data from the ventilator, an automatic assignment to the correct patients is performed via a stored database. wherein the ventilator contains relevant information about its setting parameters and their setting limits as well as its stored therapy information and is designed to make the relevant information available to a PC, wherein the ventilator is configured to provide, via the respective interface or storage medium, an application directly executable by a PC operating system, wherein the ventilator contains executable logic in non-volatile memory, wherein the executable logic is not executable by the ventilator itself but by the PC, thus enabling the installation of software on the PC without requiring a user to obtain the software directly from the ventilator manufacturer or a service provider via CD, download, or storage medium. wherein the ventilator further comprises a data cable as a data exchange means inserted into the respective interface, wherein the data cable is connected to an interface converter outside the ventilator, wherein the interface converter is designed to enable communication between the ventilator and another device via at least one transmission standard not provided in the ventilator itself, wherein at least one additional sensor in the form of a pulse oximeter and / or a sensor for CO2 measurement and / or a sensor for measuring respiratory effort and / or an ECG device and / or an EEG device is additionally connected to the ventilator via the interface converter. [2] Method for operating a ventilator (1) with at least a sensor for detecting at least one parameter of a breathing gas, a control device for specifying settings, a storage unit a control unit connected to the storage unit, a first computer program product for implementing the settings taking into account a specification and a second computer program product that regulates data transfer to and from the control unit via at least one interface (8); wherein at least one interface allows for the mutual exchange of data between the ventilator (1) and external storage media and / or devices (12), parameters are exchanged, and parameters and / or a configuration of the ventilator are loaded from external storage media and / or devices, wherein the ventilator has at least two interfaces that support different standards and communication protocols, wherein one of the interfaces is designed as a radio interface and another of the interfaces is designed as a memory card interface, wherein the memory card interface is suitable for a Secure Digital card, a Multimedia card, a Memory Stick PRO card, an xD-Picture card, a SmartMedia card or a CompactFlash card, where data from the ventilator is saved to an inserted memory card via the memory card interface, and data from an inserted memory card is loaded into the ventilator, where, in the area of ​​the ventilator, a firmware or software is installed as the second computer program product, which runs as a client and enables a connection of the ventilator to the Internet, where the client is responsible for initiating contact during data transmission and determines the timing thereof, where reading or saving ventilation and usage information to the respective storage medium must be initiated by an event, and the event is the expiry of a specific period of time since the start or end of ventilation therapy, where, when reading usage data from the ventilator via a stored database, an automatic assignment to the correct patients takes place. wherein the ventilator contains relevant information about its setting parameters and their setting limits as well as its stored therapy information and makes the relevant information available to a PC, wherein the ventilator further provides, via the respective interface or storage medium, an application that can be directly executed by a PC operating system, wherein the ventilator contains executable logic in non-volatile memory, wherein the executable logic is not executed by the ventilator itself but by the PC, thus enabling the installation of software on the PC without requiring a user to obtain the software directly from the ventilator manufacturer or a service provider via CD, download or storage medium, wherein the ventilator further comprises a data cable as a data exchange means inserted into the respective interface, wherein the data cable is connected to an interface converter outside the ventilator, wherein the ventilator communicates via the interface converter with another device via at least one transmission standard not provided in the ventilator itself, wherein at least one additional sensor in the form of a pulse oximeter and / or a sensor for CO2 measurement and / or a sensor for measuring respiratory effort and / or an ECG device and / or an EEG device is additionally connected to the ventilator via the interface converter,

Images