Treatment of repeated error messages from a dialysis machine

Abstract

Fault handling unit (20) for a medical device (D), in particular for a dialysis machine, wherein the fault handling unit (20) is configured to record a number of consecutive confirmation inputs (BE) as actual values ​​in response to each currently issued device fault message (GFM) representing a reportable condition (222) of the medical device (D), wherein the fault handling unit (20) comprises a memory (MEM) in which a preconfigured target value for the number of consecutive confirmation inputs is stored, and wherein the fault handling unit (20) comprises an evaluation unit (21) which is designed to compare the recorded actual value with the stored target value for conformity and, if the target value is exceeded, to initiate a modified device control (226), where several target values ​​are provided, defining different value ranges, where each value range is assigned a specific, configurable control procedure, wherein the fault handling unit (20) comprises an evaluation unit (21) which is designed to evaluate which operator has confirmed the currently issued device fault message (GFM) with a confirmation input (BE), and where a user identity (220), which is specific to each user, is captured, where the target value is configured depending on the captured user identity and where the modified control (226) depends on the range of values ​​into which the recorded actual value falls.

Description

[0001] The present invention relates to error handling in dialysis machines or other medical devices. It particularly relates to an error handling unit, a medical device with such an error handling unit, and a method for operating the dialysis machine when handling messages.

[0002] Today's modern medical devices, such as the 5008 hemodialysis system from Fresenius Medical Care, are generally equipped with a touchscreen for controlling and operating the device and for inputting and outputting messages.

[0003] In clinical practice, the fault-free functioning of medical devices is essential. For this reason, the device contains a large number of detectors (e.g. sensors) that detect the status of the device and, if necessary, report this to the user via the user interface. These messages can, for example, signal an error condition on the device. The messages must be acknowledged by the user. If the message is an error message, an action must usually be carried out on the device to return the status to a fault-free state. If, for example, the message indicates that cover doors on the device are open, these must first be closed before the device can be used again. The user will therefore first confirm or acknowledge the message and then close the doors. The device recognizes this and the message no longer appears.However, if the user does not close the doors and thus does not change the error status, the message will be displayed again.

[0004] In the prior art, this process of "error condition - message - message acknowledgement - no error correction on the device" occurred any number of times and was executed iteratively, always with the same message. This disadvantageously poses the risk that the error condition persists for too long, for example, because the user does not know which specific troubleshooting measures they need to perform on the device to resolve the error condition. This approach is not effective. The problem with known devices from the prior art is that it sometimes takes too long to resolve an error condition, which can lead to a delay in medical treatment. This is where the invention comes in.

[0005] DE 25 40 615 A1 relates to a vehicle monitoring device with sensors that monitor components or operating conditions of the vehicle and are operatively connected to a display device via an evaluation unit. Various sensors provide priority-rated error signals based on the order in which they are connected.

[0006] The publication DE 10 2012 009 517 A1 concerns a procedure for entering user information into medical devices. Preparation and the treatment itself require extensive operating steps and inputs into the dialysis machine, which are usually performed by trained medical personnel.

[0007] Publication WO 2015 / 186027 A1 discloses methods for supporting a user with appropriate assistance when using a patient monitor. The number of alarms can be set before assistance is offered.

[0008] Based on the known systems as the state of the art, the present invention therefore aims to improve the handling of device messages and shorten the time required to restore a fault-free operating state. Furthermore, the process for operating devices in the context of device messages is to be improved, which in turn increases the quality of device use.

[0009] This object is achieved according to the invention by an error handling unit, a medical device and a method according to the enclosed, mutually independent patent claims.

[0010] The invention is described below with reference to the device-based solution to the problem, and thus, among other things, with reference to the error-handling unit. Features, advantages, or alternative embodiments mentioned in this context are also applicable to the other claimed subject matter, and vice versa. In other words, the subject claims (which are directed, for example, to a system or a device) can also be developed with the features described or claimed in connection with the method. The corresponding functional features of the method are implemented by corresponding subject modules, in particular by electronic hardware modules or microprocessor modules, of the system or product, and vice versa.

[0011] According to a first aspect, the invention relates to an error handling unit or generally a message handling unit for a medical device, in particular for a dialysis machine, as claimed in claim 1.

[0012] The error handling unit / message handling unit is designed to record a number of consecutive confirmation inputs as an actual value in response to a currently output device message. The error handling unit comprises a memory in which a preconfigured target value for the number of consecutive confirmation inputs is stored, and an evaluation unit designed to compare the recorded actual value with the stored target value for consistency and to initiate modified device control if the target value is exceeded. The device message can be a device error message. For simplicity, the terms "error handling unit" and "device error message" are used below.

[0013] The error handling unit is an electronic component. It can be implemented in hardware and / or software and is used to handle device messages, e.g., error messages or status messages that are output on a user interface of the device (e.g., optically / graphically and / or acoustically). The messages relate to a status of the medical device and can, in particular, be error messages. The error handling unit is preferably assigned to a specific medical device. The error handling unit can exchange data with a central server that collects and evaluates data from all or selected error handling units (including other medical devices, e.g., from all dialysis machines in a dialysis station) (e.g., using statistical analysis).It is also possible to configure a single error handling unit for multiple medical devices, which can then resolve device messages based on the device's identity (e.g., using a corresponding identification code). It is also possible to configure multiple error handling units for one and the same medical device. The respective error handling units can be responsible for different technical device components.

[0014] In the following, the invention is described for a dialysis machine as an example of a medical device, e.g., a hemodialysis machine or a peritoneal dialysis machine. However, it will be obvious to those skilled in the art that the invention can also be applied or transferred to other medical, computer-controlled devices or (fluid management) machines or blood treatment devices that output device messages or device error messages via a user interface.

[0015] The confirmation input is an input made by the user on the device's user interface. The confirmation input can be entered on an input field (e.g. on a switch element of a graphical user interface / GUl). The confirmation input is made in response to a message from the device, in particular to a device error message. Preferably, the confirmation input can only be entered on the input field after a device error message has been issued. For example, it can be provided that the input field for recording the confirmation input is only displayed after a device error message has been issued for which no confirmation input has yet been recorded. The confirmation input can, for example, be entered on a field or button on a touchscreen. Alternatively, the confirmation input can also be recorded as an acoustic signal or by pressing a switch on the device or a switch element.

[0016] Consecutive confirmation inputs are confirmation inputs that are entered consecutively for the same message (different messages but with the same content). If, for example, an error message is output and the error state is not changed because no action is carried out on the device, the error state persists. In this case, even after the message has been confirmed by the confirmation input, the error message is output again, which then has to be confirmed again, and so on. The confirmation inputs that each relate to the same message are therefore referred to as consecutive. Confirmation inputs are consecutive if the state of the device has not changed in the meantime. However, if a first message relates to a first error state and is confirmed or canceled with a first confirmation input.is acknowledged and later, after the first error condition has been rectified, a second message relating to a second error condition is acknowledged with a second confirmation input, then the first and second confirmation inputs are not referred to as consecutive.

[0017] In a preferred development of the invention, all device error messages and all confirmation inputs are saved in a log file in a memory. It can then be configured so that a specific modified control procedure is triggered when device error messages with the same content follow one another. If, for example, a message is issued saying "Fluid level too low. Top up fluid" and this message condition is remedied by appropriate device operation (fluid is topped up) and the same message is issued within a configurable period of time thereafter, this situation could be evaluated and indicate that the fluid container may be leaking. Following this evaluation, modified device control is initiated and, for example, an additional message with the corresponding information (leak) is output on a graphical user interface.

[0018] In the preferred embodiment of the invention, the reportable state can be an error state of the medical device, which can be changed or canceled by manipulating the device or changing its state. The invention fundamentally distinguishes between two states: an error-free operating state (normal operation of the device), which is free of messages, and a message state in which messages are output. Messages can be output, for example, for errors that have occurred on the device, for information for the user (e.g. low fill level of a resource, exceeding or falling below normal values ​​for selected parameters, etc.), for alarms, or for emergency signals. It can be preset that the device is automatically transferred to the reportable state when the error-free operating state is exited.

[0019] A device error message will therefore primarily concern an error condition. However, it can also refer to a change in the device's state without there being a fault in the device (e.g., if the user is only supposed to be informed about a specific situation) and is thus, in fact, a device error message. For the purposes of this invention, however, it is uniformly referred to as a device error message. A device error message always requires user acknowledgment by entering a confirmation.

[0020] The device error message and the confirmation input are displayed on the user interface of the medical device, preferably on a graphical interface such as a touchscreen (of a monitor or display). Alternatively, the error handling unit can also have its own user interface, through which the messages are then displayed. The user interface—e.g., the touchscreen—can display interaction surfaces, switches, control fields, etc. for controlling the dialysis machine.

[0021] An essential idea of ​​the invention is that the number of repeatedly output device error messages of the same content (which therefore refer to the same state of the device) or the number of related consecutive confirmation inputs are recorded and evaluated in order to initiate a modified operation of the device.

[0022] In a preferred embodiment of the invention, the error handling unit comprises a memory in which a preconfigured target value for the number of consecutive confirmation inputs is stored. The target value indicates the number of repeated device error messages at which a modified device control or modified device operation (e.g., with modified control of the input / output interface and, in particular, fields / elements on the graphical user interface) should be executed.

[0023] In an advantageous embodiment of the invention, a plurality of target values ​​can be configured which define different value ranges, e.g., target values ​​3, 5, and 7. This defines a first value range between the first and third repeated input of the confirmation signal, a second value range between the third and fifth repeated input, and a third value range from the seventh input onwards. Each of the (in the example: three) value ranges is assigned a specific, configurable control procedure. In a configuration phase of the method, it is possible to configure which actions and measures are to be triggered by the respective control procedures, such as, for example, displaying different or additional input and output fields on the graphical user interface. This allows modified control of the device to take place depending on the value range into which the recorded actual value falls.In principle, a first device operation can be triggered after the first target value has been reached, and a second device operation after the second target value has been reached, etc. In the example described above, it could therefore be configured that an additional message is issued if the condition is repeated three times, an alarm signal is issued additionally or alternatively if the condition is repeated five times, and a message is automatically sent to a preconfigured instance (colleague or supervisor) if the condition is repeated seven times.

[0024] For example, with a preconfigured target value of 10, it can be defined that if an error message is "pushed away" 10 times (without correcting the error on the device), an escalation of the device response is initiated. However, this escalation does not have to occur if the error message is confirmed or acknowledged for the first time.

[0025] For example, if the target value is 3, then it can be configured that after three repeated device error messages, and thus after three repeated or consecutive confirmation inputs, a different device operation is initiated. For example, it can be configured that future device error messages include an additional note instructing the user on the exact steps to perform on the device and the instructions to follow to resolve the error.

[0026] To enable the error handling unit to compare the recorded number with the stored target value or to otherwise process the recorded number (e.g., using statistical methods), the error handling unit can include an evaluation unit. The evaluation unit is designed to compare the recorded actual value with the stored target value(s) for consistency and, if the target value is exceeded, to initiate modified device control (to output automated or alternative messages or to trigger modified device control).

[0027] The error handling unit or the evaluation unit can be configured to evaluate whether, how often, within what period of time, and / or by which operator the currently output device error message has been confirmed with a confirmation input. The evaluation unit can be provided in the form of an electronic processing unit (CPU or CPU component) or as a software module. The output device error messages, the recorded confirmation inputs, and / or the evaluations are stored in a LOG file, e.g., for further statistical analysis.

[0028] In a preferred embodiment of the invention, the error handling unit comprises an output unit. This can be designed as a separate monitor associated with the error handling unit, or it can be designed as a touch panel on the monitor of the medical device. The output unit serves to output the recorded actual value and—preferably, but not necessarily—the desired value.

[0029] In an advantageous development of the invention, the error handling unit is designed to reset the detected number of consecutive confirmation inputs if a change in the device state and / or an error correction has been carried out on the medical device, so that the medical device is in a message-free operating state (without errors).

[0030] In a further aspect, the invention relates to a medical device and in particular to a dialysis machine, with an error treatment unit as described above.

[0031] In yet another aspect, the invention relates to a method for operating a medical device, in particular a dialysis machine.

[0032] During operation of the medical device, a number of consecutive confirmation inputs in response to each issued device error message is recorded as an actual value. The process includes, among other things, the following steps: - Comparing the recorded actual value with at least one preconfigurable target value for the number of consecutive confirmation entries and if the at least one target value is exceeded in a preconfigurable time interval: - Modified control of the medical device by automatically issuing an additional message or by issuing a modified message based on the recorded actual value.

[0033] According to one variant, the device error message and / or the confirmation input are output or recorded on a monitor of the medical device, in particular on a touchscreen monitor.

[0034] According to another advantageous further development, the actual value is automatically reset if a device state (e.g. error state) that caused the issued device error message no longer exists.

[0035] According to another advantageous development, a modified control of the medical device can be activated and deactivated, or triggered automatically upon the occurrence of a predefined event. This has the advantage that the normal notification-confirmation-device response cycle can be maintained for training purposes or other specific applications.

[0036] In an advantageous variant, for all issued device error messages, the number of confirmation entries entered by each user and by each user is recorded and / or stored. For statistical analysis, the data set can be broken down by various parameters (e.g., by time period, user identity after authentication, type of message, etc.).

[0037] In another advantageous development of the invention, the method comprises the following method step: - Recording a user identity that is specific to a user of the medical device (e.g. by means of authentication) and - Modified control of the medical device in response to the detected actual value and the detected user identity.

[0038] For example, the alternative device response triggered according to the invention can also be determined depending on the user's qualifications. This qualification, in turn, can be recorded, for example, through prior user authentication on the dialysis machine. For this purpose, the user can be asked to enter a PIL code before operating the device, or an identifying smart card can be read. Alternatively, biometric data can also be used to authenticate the user. This means that, for example, trainees can be provided with more comprehensive assistance that is displayed on the graphical user interface when consecutive confirmation entries are recorded. The assistance can display instructions and concrete operating steps on how the device's error state that requires notification can be converted to error-free operating mode.

[0039] In another advantageous development of the invention, the target value is configured depending on the recorded user identity. This allows the qualifications of the device user to be directly incorporated into the determination of the target value. This has the advantage that, for example, a trainee can be provided with the necessary information to correct a device error earlier by setting the target value lower than for an experienced person.

[0040] A further solution to the problem consists in a computer program product that is loaded or loadable into a memory of a computer or an electronic or medical device with a computer program for carrying out the method described in more detail above when the computer program is executed on the computer or the electronic or medical device.

[0041] Another solution to the problem involves a computer program for carrying out all steps of the method described in more detail above, if the computer program is executed on a computer, an electronic device, or a medical device. It is also possible for the computer program to be stored on a medium readable by the computer or the electronic or medical device.

[0042] In the following detailed description of the figures, non-limiting embodiments with their features and further advantages are discussed with reference to the drawing. Short description of the characters Fig. 1 shows a schematic representation of a dialysis machine with an error treatment unit according to an advantageous embodiment of the invention. Fig. 2 is an example of a flowchart for an operating procedure of the dialysis machine. Fig. 3 shows a schematic, tabular representation of device states and an inventive change of an actual value during operation of a dialysis machine. Fig. 4 is an exemplary schematic representation of a data exchange of signals between the error handling unit and a user interface of the dialysis machine. Detailed description of the characters

[0043] In the following, the invention is described in more detail using exemplary embodiments in conjunction with the figures.

[0044] The invention relates to the handling of messages from a medical device, in particular a dialysis machine D. During dialysis treatment of a patient, it is sometimes of life-saving importance to be able to ensure that the dialysis machine D functions flawlessly. Therefore, malfunctions and device errors must be reported immediately. In the event of a malfunction of the dialysis machine D, a message automatically appears on a graphical user interface (GUI) of the dialysis machine D, informing the user of the malfunction or error. The message can contain further information that provides the user with assistance in resolving the problem underlying the current message.

[0045] Investigations by the applicant have shown that when device error messages are issued in the hectic daily clinical routine, the user may be tempted to simply eliminate the device error message without making any concrete changes to the status of device D. In other words, there is a risk that the device error message will be attempted to be resolved by "pushing it away" without carrying out any concrete troubleshooting measures on the dialysis machine D. The problem therefore persists and the corresponding device error message must be issued repeatedly. This procedure has previously been repeated several times in known systems from the prior art without adjusting the content of the device error message. This is where the present invention comes in and is aimed at recording a number of consecutive confirmation inputs and further processing the number recorded in an evaluation unit.Consecutive confirmation entries are those confirmation entries that the user enters in response to the same device error message. This can refer to the second or multiple repetitions of a confirmation entry for the same device error message if the fault underlying the respective device error message has not been resolved and the dialysis machine D is still in a state requiring notification.

[0046] With reference to Fig. 1, essential components of the dialysis machine D according to a preferred embodiment are explained in more detail below. The dialysis machine D comprises the error handling unit 20 as a central unit, which is designed to record a number of consecutive confirmation inputs BE in response to a currently output device error message GFM representing a reportable condition of the dialysis machine D as an actual value. If, for example, corresponding sensors arranged on the device D or on the modules exchanged with the device D detect that a malfunction or problem has occurred, such as a problem with the device D or with the tubing system, this is signaled via the corresponding device error message GFM and displayed to the user on the graphical user interface GUI. The user can then press a button also displayed on the user interface GUI.This actuation serves as a confirmation input (BE) and refers to the device error message (GFM) that appeared immediately before and is still currently displayed. If the user does not resolve the problem with the device or the hose system, the error persists, and after a preset time, the same device error message (GFM) is displayed again. If the user again actuates the corresponding field and enters a confirmation input (BE), this is a consecutive confirmation input, which is recorded according to the invention. According to the invention, the actual value counter is incremented.

[0047] As in Fig. As further illustrated in Figure 1, the dialysis machine D and in particular the error handling unit 20 can comprise a memory MEM in which a preconfigurable target value for the (permissible) number of consecutive confirmation inputs BE is stored. The dialysis machine D and in particular the error handling unit 20 can further comprise an evaluation unit 21. The evaluation unit 21 is designed to compare the recorded actual value with the stored target value for agreement. If the actual value exceeds the target value, a modified device control 226 is triggered. The modified device control 226 can lead to the output of alternative device error messages GFM, or a modified device control of the dialysis machine can be initiated.If the target value is set to “3,” for example, it can be configured in one embodiment so that after a third consecutive confirmation input BE is recorded by the user on the graphical user interface GUI, another (new) information field appears with further measures and references that inform the user how to solve the respective fault or problem with the device D. The modified device control 226 can include further measures, such as forwarding a corresponding exceedance message to other computer-based instances. The error handling unit 20 can include an output unit 30 that is designed to display or output the recorded ACTUAL value alone or in combination with the respectively configured target value. The evaluation unit 21 and the output unit 30 can be part of the error handling unit 20. As shown in FIG. Fig. 1, the evaluation unit 21 and / or the output unit 30 can alternatively also be separate modules, some of which are arranged in the dialysis machine D. Preferably, the output unit 30 can be formed on a touchscreen monitor 11 of the dialysis machine D. The dialysis machine D generally comprises a touchscreen monitor 11, which is intended for the input and output of data. In other words, at least one element is provided on the touchscreen monitor 11, on which specific values ​​can be output (or input).

[0048] In the following, the usual procedure according to the invention is described with reference to Fig. 3 explained in more detail. In Fig. 3 shows several different error handling routines and processes for a dialysis machine D as examples. As shown in the right Fig. According to the arrow shown in Figure 3, time runs from top to bottom. In the table on the left, device D is initially operated in normal mode NB, during which no messages are output and the user does not have to carry out any device malfunctions or troubleshooting; the ACTUAL value is 0. After an error has been detected, a device error message GFM is automatically output. The user must then acknowledge the respective device error message GFM by entering a confirmation signal BE via an appropriate input field. According to the invention, the ACTUAL value is incremented. If the user also carries out error correction measures on device D and can successfully resolve the problem, device D can be returned to normal mode NB. No further device error message is output and the ACTUAL value is decremented again or reset to zero.This returns the system to its initial state and allows it to be monitored for further faults.

[0049] In the Fig. 3 The table in the middle shows the same initial situation. In this case, however, the user does not carry out any error handling and the problem persists. So, after a first device error message GFM1 has already been issued, which was acknowledged with the confirmation input BE1, a second device error message GFM2 is later issued, which is acknowledged with a second confirmation input BE2. In this case, the ACTUAL value is incremented and in this case is 2. Of course, the problem can now be solved by the user and device D can then be transferred to normal operation NB. If this is not the case, however, further device error messages GFM may be issued.

[0050] Far right in Fig. Figure 3 shows the case in which the error persists even after a second device error message GFM2 is issued. In this case, a third device error message GFM3 is issued, which in turn is acknowledged by a third confirmation input BE3. In this case, the ACTUAL value is also incremented and is 3 in this case. If the comparison of the ACTUAL value with the TARGET value results in the TARGET value being exceeded, an alarm message can be triggered, for example. Furthermore, further actions can be initiated. The further actions can, for example, trigger the output of a corresponding warning message on the graphical user interface GUI of the dialysis machine D or on a server that is in data exchange with the dialysis machine D, namely that a confirmation input has already been entered for the third time without the device malfunction being rectified.It is also within the scope of the invention for a person skilled in the art to configure further measures and / or provide further iterations. The device error messages (GFM) output according to the invention can preferably differ from one another. In particular, it is possible for the second device error message and the third device error message to each have a different content than the first device error message. Furthermore, the subsequent device error messages (GFM) can provide the user with additional information on how to solve the specific problem. In particular, they can be given assistance, such as who to contact or where to obtain further information.

[0051] In the following, the operation of the error handling unit 20 in the event of an error is described with reference to Fig. 4. If a reportable condition, in particular a malfunction or error condition 222, has been detected, several signals are exchanged according to the invention between the error handling unit 20 and the graphical user interface GUI, which the user operates. After the error is detected, a first device error message GFM1 is displayed on the GUI, which the user can confirm via a confirmation input BE1. If the error persists and the problem is not resolved, and the dialysis machine D thus remains in a reportable condition 222, a second device error message GFM2 is displayed on the GUI at a later, configurable time, which the user can again confirm by entering a consecutive confirmation input BE2. After the second confirmation input BE2 is detected, the actual value is set to 2 according to the invention. In Fig. Figure 4 shows only two iterations of consecutive confirmation inputs. Of course, multiple iterations can be performed. The device error messages GFM1, GFM2, ...GFMi output can differ from each other. The subsequent device error messages generally contain additional information for the user to assist them in eliminating the fault underlying the device error message GFM or in solving the problem.

[0052] In the following, with reference to Fig. 2 a sequence of the method according to the invention according to a preferred embodiment is explained in more detail. After the start of the method, the user identity can be recorded in step 220. This can be done, for example, by means of authentication or by entering biometric data or a PIN number. In step 221, the dialysis machine D can be operated in normal mode NB. In this state, there are no messages. In step 222, a state requiring notification is recorded, for example a malfunction of the dialysis machine. Subsequently, a device error message GFM is output in step 223. Furthermore, in step 223, the output device error message GFM is acknowledged by entering a confirmation input BE. In step 224, the ACTUAL value is recorded. In this case, the counter for the confirmation inputs BE is incremented beforehand. In step 225, the currently recorded ACTUAL value is compared with the preconfigured TARGET value.If the comparison shows that the ACTUAL value is below the TARGET value, another device error message GFM (with the same content as the first) can be output, causing the system to return to step 223. However, this is only the case if the problem underlying the respective device error message has not been resolved by the user. Otherwise, if the fault could be rectified, the ACTUAL value is decremented again and normal operation NB of the dialysis machine can be continued at step 221. If the comparison between the ACTUAL value and TARGET value shows that the ACTUAL value is above the TARGET value, a modified device control is automatically initiated according to the invention. This is shown in . Fig.2 with the reference numeral 226. The modified device control can include a modified output of a new, additional device error message GFM, or the device error message GFM can be enhanced with additional, further information that characterizes the current situation and its genesis or history with the previous error handling. Furthermore, further measures and actions can be triggered. For example, it is possible for the target value exceedance to be represented on the graphical user interface as a warning. Furthermore, the target value exceedance can also be forwarded as a data record to other computer-based instances. Furthermore, a note can be issued that this target value exceedance is being tracked and stored in a memory and is thus available for statistical evaluations.This makes it transparent for the user that his consecutive confirmation entries BE are subjected to statistical evaluation and storage.

[0053] Essentially, the error handling unit 20 according to the invention is intended to automatically evaluate whether and, if so, within what period of time and how often the currently output device error message GFM has already been confirmed by the user. Starting from a certain number of consecutive confirmation inputs BE per configurable time unit, a preconfigured modified device response 226 is automatically triggered. The modified device response 226 is preferably a modified control of the user interface GUI or a modified screen response. The modified device response 226 can be used to inform the user that they must perform actions on the device D so that the device state (for example, the error state) can be changed in order to resume normal operation NB of the medical device as quickly as possible.In other words, the user can carry out the necessary manipulations on the device or on connected technical equipment, such as a hose set, more quickly for the benefit of the patient.

[0054] With the modified device response 226, it can be provided that a corresponding help text for the GFM error message is displayed automatically (and not only upon a corresponding user action, for example, pressing a help button on the GUI). It is also possible for an additional, separate message with a different appearance to be displayed, informing the user that previous GFM device error messages have been acknowledged with the number corresponding to the actual value without triggering a device response or without having any effect on device D. The user can then be provided with suggestions as to where to look up further information.To alert the user to the modified GFM device error message, it is also possible to retain the text itself but position the message output at a different location on the GUI or format it differently (for example, in a different color, font, size, and / or display type). Furthermore, an additional alarm signal can be output alternatively or cumulatively. The alarm signal can be provided, for example, acoustically or visually on an input / output interface.

[0055] Finally, it should be noted that the description of the invention and the exemplary embodiments are fundamentally not to be understood as restrictive with regard to a specific physical implementation of the invention. All features explained and shown in connection with individual embodiments of the invention can be provided in different combinations in the subject matter according to the invention in order to simultaneously realize their advantageous effects. It is therefore also within the scope of the invention, for example, to provide other operating or control elements of the medical device for entering the confirmation input BE as an alternative or in addition to the graphical user interface. These can be, for example, manually operated operating elements, joysticks, a mouse, a conventional keyboard or the like.It is particularly obvious to a person skilled in the art that the invention can be applied not only to dialysis machines, but also to other medical devices D where GFM messages must be acknowledged by a confirmation input BE. The GFM messages can be error messages, but also other messages related to a device status.

[0056] Furthermore, the components of the medical system for message handling or error handling can be distributed across several physical products.

[0057] The scope of the present invention is given by the claims and is not limited by the features explained in the description or shown in the figures.

Claims

[1] Error handling unit (20) for a medical device (D), in particular for a dialysis machine, wherein the error handling unit (20) is designed to record a number of consecutive confirmation inputs (BE) in response to a currently output device error message (GFM) representing a reportable condition (222) of the medical device (D), as an actual value, wherein the error handling unit (20) comprises a memory (MEM) in which a preconfigured target value for the number of consecutive confirmation inputs is stored, and wherein the error handling unit (20) comprises an evaluation unit (21) which is designed to compare the recorded actual value with the stored target value for agreement and to initiate a modified device control (226) if the target value is exceeded, where several target values ​​are provided, which define different value ranges, where each value range is assigned a specific, configurable control procedure, wherein the error handling unit (20) comprises an evaluation unit (21) which is designed to evaluate by which operator the currently output device error message (GFM) has been confirmed with a confirmation input (BE), and wherein a user identity (220) which is specific to a user is recorded, where the target value is configured depending on the recorded user identity and where the modified control (226) is carried out depending on the value range in which the recorded actual value falls. [2] Error handling unit (20) according to one of the preceding claims, characterized bythat the evaluation unit (21) is designed to evaluate whether and / or how often and in what period of time the currently output device error message (GFM) has been confirmed with a confirmation input (BE). [3] Error handling unit (20) according to one of the preceding claims, characterized by that the error handling unit (20) comprises an output unit (30) which is designed to output the detected actual value and the desired value. [4] Error handling unit (20) according to one of the preceding claims, characterized by in that the error handling unit (20) is designed to reset the detected number of consecutive confirmation inputs (BE) if a state change on the medical device (D) has been carried out and detected, so that the medical device (D) is in a message-free operating state. [5] Medical device (D), in particular dialysis machine, with an error treatment unit (20) according to one of the preceding claims. [6] Method for operating a medical device (D), in particular a dialysis machine, wherein during the operation of the medical device (D) for each issued device error message (GFM) a number of consecutive confirmation inputs (BE) in response to the currently issued device error message is recorded as an actual value, the method comprising the following method steps: - detecting a user identity (220) which is specific to a user of the medical device, and - Configuring a target value depending on the recorded user identity, whereby several target values ​​can be configured, which define different value ranges and each value range is assigned a specific, configurable control procedure, - comparing (225) the detected actual value with the preconfigurable target value for the number of consecutive confirmation inputs (BE), and wherein the modified control (226) is carried out depending on the value range in which the detected actual value falls, and if a target value is exceeded in a preconfigurable time interval: - Modified control (226) of the medical device (D) by automatically outputting a modified message based on the recorded actual value. [7] Method according to one of the preceding method claims, characterized by that the device error message (GFM) and / or the confirmation input (BE) are output or recorded on a monitor of the medical device, in particular on a touchscreen monitor (11). [8] Method according to one of the preceding method claims, characterized bythat the actual value is automatically reset if it is detected that a reportable condition causing the issued device error message (GFM) no longer exists. [9] Method according to one of the preceding method claims, characterized by that a modified control (226) of the medical device (D) can be activated and deactivated or is triggered automatically after the occurrence of a predefined event. [10] Method according to one of the preceding method claims, characterized by that for all issued device error messages (GFM) the number of confirmation entries (BE) is saved and / or output for each user. [11] Method according to one of the preceding method claims, characterized by that the procedure comprises the following procedural step: - Modified control (226) of the medical device (D) in response to the detected actual value and the detected user identity.

Images