Medical device with state-dependent dynamic actuation of light-emitting diodes
By dynamically manipulating the light-emitting diodes according to the state of the medical equipment and the surrounding environment, the problem of lack of dynamism in the control of light-emitting strips in the prior art is solved, and the flexibility and effectiveness of information transmission are realized.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-19
- Publication Date
- 2026-03-13
AI Technical Summary
The current methods for controlling luminescent strips in medical devices lack dynamism and cannot effectively transmit important information to operators.
By dynamically determining the light emission state through control equipment and utilizing state information from medical devices and the surrounding environment, the output of light-emitting diodes can be individually manipulated to achieve information transmission.
It enables the luminous strips to change dynamically under different states, improving the flexibility and effectiveness of information transmission, and can display different light signals to convey important information as needed.
Smart Images
Figure CN223993753U_ABST
Abstract
Description
Technical Field
[0001] This utility model is based on a medical device.
[0002] -The medical device has multiple luminescent strips.
[0003] -Each light-emitting strip has multiple individually controllable light-emitting diodes.
[0004] -The medical device has a control device for manipulating the luminescent strip. Background Technology
[0005] Medical equipment is common knowledge.
[0006] In such medical devices, the luminescent strip is typically manipulated statically. Purely time-controlled manipulation of the luminescent strip is also conceivable. However, regardless of the method of manipulation, the control of the luminescent strip does not convey any important information to the operator. Utility Model Content
[0007] The purpose of this invention is to achieve the following feasible solution: by means of the feasible solution, an luminous strip can be used to transmit information to the operator.
[0008] The stated objective is achieved by a medical device having the features of embodiments of the present invention. Advantageous designs of the medical device are the subject of embodiments of the present invention.
[0009] According to this utility model, the medical device of the type mentioned at the beginning is designed in such a way that the control device dynamically determines the corresponding light emission state when using the state of the medical device and / or when using the state of the surrounding environment from the medical device, the light emission state includes sub-states for each light-emitting diode, the corresponding light-emitting diode should be operated according to the sub-state, and the control device transmits the corresponding light emission state to the light-emitting strip.
[0010] The sub-state of a single LED does not correspond to the control of the corresponding LED (i.e., its input), but rather to the light signal emitted by the corresponding LED (i.e., its output). Correspondingly, the corresponding light-emitting state corresponds to the overall sub-state of the LED.
[0011] One state of a medical device could be, for example, being put into operation, which means the device has completed its startup process. Another state could be, for example, identifying a malfunction or a fault in a component of the medical device. This malfunction can be detected, for example, directly through a corresponding signal or indirectly through frequency analysis of acoustic signals.
[0012] Another possible state for a medical device is, for example, that it is currently operating (as opposed to standby operation, in which the device is ready to operate but not in a therapeutic sense or in the sense of data detection for diagnostic purposes, etc.). Another feasible state could be, for example, a defined degree of examination progress. For instance, there could be manipulation based on the patient's lying position as they are moved through the examination aisle of the medical device.
[0013] The state of the surrounding environment from a medical device can be, for example, acoustic signals. For instance, it can detect whether a patient, who is fully or partially within the examination area of the medical device, is speaking or calling out. Volume can be indicated, for example, by using an luminous strip. Another possible state of the surrounding environment from a medical device is the patient's movement. The latter is particularly important when patient movement is not permitted during the diagnostic process in order to detect the correct signals.
[0014] Another feasible approach is to position the luminous strip within the patient's field of vision and control it according to the operator's presets. These presets can be, for example, input via a keyboard or mouse, or voice input. In the latter case, permitted voice input is preferably limited to a few key terms (e.g., "inhale," "hold your breath," "continue breathing," etc.).
[0015] The method of manipulating the luminous strip can be determined according to requirements. Examples of feasible manipulation include flashing, flow patterns, color changes, and light intensity.
[0016] Typically, routines are stored on the control device. Each routine contains code that can be directly processed by the control device and defines a sequence of light-emitting states determined by the corresponding routine, to which the light-emitting diodes of the corresponding light-emitting strip should exhibit said light-emitting state. In this case, the control device can determine, using the state of the medical device and / or the state of the surrounding environment of the medical device, which routine it should execute.
[0017] In existing technology, routines are self-contained. That is, they are machine code that is processed when the corresponding routine is called, or more precisely, they exist as machine code. Therefore, routines do not continue to be modified, parameterized, or otherwise changed or adjusted. Compared to conventional programming: a do loop from 1 to 100 with a step size of 1. In this case, the do loop is processed 100 times.
[0018] The establishment of such routines by programmers or similar personnel and the determination of the luminous state of individual LEDs in the luminous strip require very detailed knowledge of the specific control equipment used and the specific LEDs used, and furthermore, it also requires a great deal of effort.
[0019] Preferably, a program file is stored on the control device—in addition to routines. In this case, the program file contains a sequence of instructions that can be processed by the control device through interpretation by means of an interpreter stored on the control device. The instructions at least determine which routines should be processed. In this case, the control device can determine, using the state of the medical device and / or using the state of the surrounding environment of the medical device, which instruction in the program file triggers the interpretation of the instructions.
[0020] This results in significantly greater flexibility.
[0021] On the one hand, it is possible to change which routine is executed in a given state by modifying only the program file afterward. Therefore, users can change the correspondence between possible states and their respective completed routines.
[0022] Furthermore—and this is typically the case when interpreting program instructions—the interpreter transitions to the next instruction after processing the previous one (except for stop instructions). Therefore, the instructions in a program file are processed step-by-step and sequentially by the interpreter.
[0023] This allows for the invocation of a sequence of routines defined by the program file through a single state. For example, five instructions (five being purely illustrative) can be executed sequentially, each invoking another routine, followed by a stop instruction. Furthermore, loops, conditions, and many others can be implemented—especially through conditional instructions (if...then...else...) and jump instructions (goto...).
[0024] Program files can be written in a high-level language, that is, in a form of code that is (to some extent) understandable to humans. This contrasts with conventional programming, which may use, for example, a programming language similar to BASIC.
[0025] As already mentioned, routines are self-contained in the prior art. These methods are also feasible within the scope of this invention. In this case, the routine to be processed is not directly determined by the corresponding state in this invention. Instead, the following section is determined in the instructions of the program file, which controls the interpretation of the device start instruction. However, the routine can remain unchanged relative to the prior art. But it can be determined which routine is executed in which state. The order in which the routines are executed can also be determined, for example.
[0026] Alternatively, it is feasible to configure the routine as a parameterizable routine and the instructions in the program file include the determination of the parameters of the routine, such that the routine is executed in accordance with the determination of the parameters of the routine given by the instructions in the program file when it is executed.
[0027] In this scenario, the following feasible approach can be achieved: The routines are parameterized post-processed. The control device generates the corresponding illumination state by executing the corresponding parameterized routines. Therefore, it is also possible to determine the manner and method of executing the defined routines. For example, in the "blinking" routine, it can be determined what intensity, frequency, and / or duty cycle the flashing should have, or how frequently it should flash. In the "traversal" routine, for example, it can be determined how large the luminous area of the luminous strip should be and at what speed that area should move along the luminous strip. Other parameterizations are also feasible.
[0028] The method is similar to that known in the framework of conventional programming for subroutines (subroutines).
[0029] This also contrasts with conventional programming: Existing "rigid" routines may, for example, contain loops in which a defined calculation rule should be performed for each number from 1 to 100. Thus, the loop might be "do n = 1, 100, 1.....enddo". In this instruction, the preceding 1 represents the initial value of the exponent n, by which the loop should be traversed for the first time; the middle 100 represents the ending value of the exponent n, by which the loop should be traversed for the last time; and the following 1 represents the step size, by which the exponent n should be incremented after the corresponding traversal of the loop. The dots ("...") should indicate the calculation rule to be performed.
[0030] Within the framework of "conventional" programming, it is known that the previously mentioned and described instruction "do n = 1, 100, 1.....enddo" is set in a parameterized form, i.e., in the form "do n = initial value, termination value, step size.....enddo". In this case, the initial value, termination value, and step size can be determined at a later time, i.e., not at the time the program is created. In particular, they can even be preset during program runtime. Similarly, the values used within the loop can also be preset as parameters.
[0031] The instructions described first are applied to control devices and correspond to existing technical routines. The instructions described last are also applied to control devices and correspond to parameterizable routines.
[0032] With the help of these parameters, corresponding routines can be preset, such as how strongly a certain LED should be controlled, at what duty cycle the LED should be controlled, at what clock rate the LED should be controlled, and many other things.
[0033] In addition to determining which routines among those routines should be processed, the aforementioned parameterization can be performed.
[0034] According to the present invention, the control device is configured, and in particular programmed, in such a way that it operates the medical device according to the operating method. Attached Figure Description
[0035] The features, characteristics, and advantages of this invention described above, and the ways and methods of achieving these features, characteristics, and advantages, become clearer and easier to understand in conjunction with the following description of the embodiments, which are illustrated in detail with reference to the accompanying drawings. These are shown in the schematic diagrams herein:
[0036] Figure 1 Showing medical equipment,
[0037] Figure 2 A block diagram showing the luminous strip and control device is provided.
[0038] Figure 3 The flowchart is shown.
[0039] Figure 4 The storage device is shown.
[0040] Figure 5 The flowchart is shown.
[0041] Figure 6 The sequence of instructions is shown.
[0042] Figure 7 Show the routine,
[0043] Figure 8 The sequence of instructions is shown, and
[0044] Figure 9 A set of light-emitting diodes is shown. Detailed Implementation
[0045] Figure 1 Medical device 1 is schematically shown. Medical device 1 has a passageway 2 through which a patient (not shown) can be moved while lying on an examination bed. Passageway 2 is typically present if medical device 1 is a CT or MR facility. In other designs of medical device 1, passageway 2 is not necessary.
[0046] Device 1 has at least one luminous strip 3. According to... Figure 1 There may even be multiple such luminescent bands 3. The luminescent bands 3 can be straight or—as in… Figure 1 As shown—arched or curved. Its length and width can be determined according to requirements. The following combines… Figure 2 The principle of the circuit technology for the light-emitting strip 3 is explained.
[0047] according to Figure 2 The light-emitting strip 3 has multiple light-emitting diodes 4 and a controller 5 for the light-emitting diodes 4. The light-emitting diodes 4 can be individually controlled by the controller 5. Regarding data communication between the controller 5 and the light-emitting diodes 4, the light-emitting diodes 4 can correspond to... Figure 2 The diagram is directly controlled by controller 5. Alternatively, they can be connected in series and set up sequentially. Combinations of the methods described are also feasible.
[0048] The controller 5 has an interface 6. Through interface 6, the controller 5 dynamically receives the required light emission state Z* from the control device 7 of the medical device 1. Therefore, the control device 7 presets the required light emission state Z* for the controller 5, thereby (even indirectly) controlling the light-emitting diode 4. For example, in... Figure 2 As indicated by the summation symbol, the corresponding required light emission state Z* includes sub-light emission states z* for each of the light-emitting diodes 4 in the corresponding light-emitting strip 3. Interface 6 is typically a serial interface. The corresponding sub-light emission state z* corresponds to the state that the corresponding light-emitting diode 4 should exhibit, i.e., the luminous flux (= output) that the corresponding light-emitting diode 4 should emit. The corresponding sub-light emission state z* is the result of the corresponding control c* (= input) of the corresponding light-emitting diode 4.
[0049] If necessary, controller 5 may have an additional interface 8, and interface 6 of controller 5 for the additional light-emitting strip 3 can be connected to said additional interface. The additional light-emitting strip 3 and its components are... Figure 2 It was not shown together with the text.
[0050] Controller 5 can be configured as a microcontroller that executes a program. Regardless of the specific design of controller 5, controller 5 dynamically receives the required light emission state Z* via interface 6. For the light-emitting diodes 4 of the corresponding light-emitting strip 3, it individually determines the corresponding control c* using the corresponding sub-light emission state z*, and controls the corresponding light-emitting diodes 4 of the corresponding light-emitting strip 3 according to the determined control c*. The control c* is determined in such a way that the actual light emission state z of the corresponding light-emitting diode 4 corresponds to the corresponding sub-light emission state z* of the light-emitting diode 4.
[0051] The light-emitting strip 3 is also connected to a supply device, light-emitting diode 4, and controller 5, so that the light-emitting strip 3 as a whole is supplied with electrical energy via the supply device. The supply device... Figure 2 Not shown together.
[0052] Control device 7 is also a component of medical device 1. The control device, corresponding to the above embodiment, is used to manipulate the luminescent strip 3. Control device 7 is configured such that it operates according to the following combination... Figure 3The detailed operating method for operating medical device 1 is described. Control device 7 can be particularly effective in... Figure 2 The control device 7 is controlled by a microprocessor and processes a control program 9, as indicated by the label "μP" within the control device 7, which is programmed using the control program. In this case, the control program 9 includes machine code 10, which can be processed by the control device 7. Furthermore, in this case, the control device 7 is configured using the control program 9 through programming.
[0053] according to Figure 3 In step S1, control device 7 receives status ST. Status ST is received by means of sensor 11 (see...). Figure 1 ) detection.
[0054] Sensor 11 can be, for example, an acoustic sensor. In this case, acoustic signals are detected. The acoustic signal could be the sound emitted by the patient or the voice of the operator. In this case, the state ST of the surrounding environment from the medical device 1 is detected. By means of sensor 11, operating noise generated by the medical device 1 during operation can also be detected as an acoustic signal. As a result, the state ST of the surrounding environment from the medical device 1 is also detected in this case.
[0055] Furthermore, sensor 11 can be, for example, a motion sensor, by means of which motion signals are detected. Thus, for example, it can be detected whether a patient being processed by medical device 1 is moving. The term "processing" in this context also includes pure data detection prior to diagnosis, such as the detection of X-ray images or MR signals. Monitoring of "critical" areas can also be performed to determine if personnel are moving into such critical areas. Consequently, the state ST of the surrounding environment from medical device 1 is also detected in this case.
[0056] Alternatively, sensor 11 can be—for example—a displacement sensor, by means of which it detects the position of an examination bed (not shown), which is manually or electrically transported through the channel 2 of medical device 1. Sensor 11 can also detect electrical or magnetic signals, such as voltage, current intensity, or magnetic field. It can also detect the operation of actuators. Even more feasible is that sensor 11 is configured as a data interface, which receives status reports from the control unit of medical device 1. In this case, the status ST of medical device 1 is detected.
[0057] In step S2, the control device 7 dynamically determines the light emission state Z*. Step S2 is determined using the state ST detected in step S1. The light emission state Z* includes sub-states z* for each light-emitting diode 4, each sub-state indicating which output signal should be provided by the corresponding light-emitting diode 4.
[0058] In step S3, the control device 7 transmits the light emission state Z* to the light emission strip 3. In the case of multiple light emission strips 3, the control device 7—at least in some cases—transmits only the portion of the light emission state Z* that pertains to each light emission strip 3.
[0059] Control device 7 repeats processing steps S1 to S3. Therefore, control device 3 always detects state ST, and based on the detected state ST, always determines the light emission state Z* and transmits the determined light emission state Z* to the light emission strip 3. The light emission state Z* can be dynamically changed in this way. Furthermore, the light emission state Z* is transmitted to the light emission strip 3 sequentially.
[0060] The control device 7 also includes a storage device 12. The storage device is in... Figure 4 It is shown separately again in the text.
[0061] In storage device 12, corresponding to Figure 4 The diagram first stores the control program 9. Additionally, routines R are typically stored in the storage device 12. Each routine R contains code that can be directly processed by the control device 7. The corresponding routine R defines a defined sequence of light emission states Z*, and the light-emitting diodes 4 of the corresponding light-emitting strip 3 should exhibit said light emission state. Such routines R are known to those skilled in the art. Routine R in... Figure 4 The numbers are supplemented by numbers, i.e., labeled R1, R2, etc., so that they can be distinguished from each other when needed.
[0062] In the simplest case, the control device 7 determines, using the state ST of the medical device 1 and / or the state ST of the surrounding environment of the medical device 1, which routine in the routine R the control device executes.
[0063] The storage device 12 preferably also stores a program file 13. The program file 13 contains a sequence of instructions A, which can be processed by the control device 7. Instruction A... Figure 3 In the middle—similar to routine R—they are supplemented by numbers, i.e., labeled A1, A2, etc., so that they can be distinguished from each other when needed.
[0064] Unlike routines R containing machine code, instruction A must first be interpreted by control device 7 before execution. For this purpose, a corresponding interpreter 14 is stored on control device 7. Therefore, instruction A is processed by control device 7 by means of interpretation by interpreter 14. Interpreter 14... Figure 4 It is also stored in storage device 12. The interpreter may alternatively be stored independently or as part of control program 9.
[0065] With regard to control program 9, routine R, and interpreter 14 if necessary, storage device 12 is typically a fixed component of control device 7. For example, the processor and associated memory of control device 7 may be components of an ASIC. The same may be true for program file 13. However, storage device 12 may also be a separate component of control device 7 for program file 13. This separate component may be a unit that is permanently connected to control device 7 if necessary, or releasably connected to control device 7.
[0066] As long as program file 13 and interpreter 14 are present, control device 7 is configured such that it conforms to the following combination Figure 5 The detailed operating method for operating medical device 1 is as follows: As long as control device 7 is controlled by a microprocessor, control device 7 is configured through programming using control program 9.
[0067] according to Figure 4 In step S11, control device 7 receives status ST.
[0068] In step S12, the control device 7 determines which instruction in instruction A of the program file 13 the control device 7 will begin interpreting instruction A. This determination is made using state ST. Therefore, based on state ST, the control device 7 can determine, for example, instruction A1, instruction A3, or another instruction A in step S12.
[0069] In step S13, the control device 7 interprets the instruction A determined in step S3 using the interpreter 14. Therefore, the control device 7 determines the corresponding executable code.
[0070] The following implementation for other sequences is slightly simplified but illustrates the principle.
[0071] After step S14, control device 7 checks whether the interpreted instruction A is a stop instruction. If so, control device 7 terminates the processing of instruction A and returns to step S11. Therefore, the control device receives the next state ST. Otherwise, control device 7 transitions to step S15. In step S15, control device 7 executes the last interpreted instruction A. During step S15, the light emission state Z* is also determined and transmitted to the light emission strip 3.
[0072] Then, in step S15, control device 7 selects another instruction A. Normally, this—corresponding to the sequence of instructions A in program file 13—is the next instruction A. However, it is also possible that the instruction A just explained is a jump instruction. In this case, the jump proceeds to the instruction A described in the jump instruction. It is also further possible that the instruction A just explained is a check. In this case, which instruction A is selected depends on the result of the check. Then, control device 7 returns to step S13.
[0073] Regardless of other facts, instruction A at least determines which routines in routine R should be processed. This is exemplarily illustrated in the following combination: Figure 6 A detailed explanation is provided.
[0074] according to Figure 6 Program file 13 (in addition) includes instructions A14 to A20. Instructions A14 to A19 determine which routine R should be executed. Instruction A20 is a stop instruction. If control device 7 determines value 3 based on state ST, instruction A14 is executed first. Therefore, instructions A14 to A20 are executed sequentially, thus executing routines R1, R4, R3, R1, R2, and R3. Conversely, if control device 7 determines value 4 based on state ST, instruction A18 is executed first. Therefore, only instructions A18 to A20 are executed sequentially, thus executing routines R3 and R2.
[0075] According to Figure 6 In this method, instruction A only determines which routines in routine R should be processed. Routine R itself remains unchanged. However, it is also possible, additionally, to parameterize routine R. This is illustrated in the following example. Figure 7 and 8 The implementation scheme is described for routine R1. A similar implementation scheme applies to other routines R.
[0076] according to Figure 7 R1 can be parameterized using parameter P. This parameterization is well known to those skilled in the art within the scope of conventional programming.
[0077] according to Figure 8 Instruction A of program file 13 (in addition) includes the determination of parameter P for routine R1. If state ST is thus triggered, instructions A31 and A32 are executed (alone or in addition), and parameter P (or at least one of the parameters P) can be determined, for example, within the scope of instruction A31. When routine R1 is subsequently called in instruction A32, parameter P is transferred to routine R1 along with it. Therefore, routine R1 executes in accordance with the determination of parameter P during its execution, as determined by instruction A31.
[0078] The particular advantage of the method and means of controlling the light-emitting diode 4 of the light-emitting strip 3 according to this utility model is that, corresponding to... Figure 9 The diagram shows multiple light-emitting diodes (LEDs) 4 combined into corresponding groups 15. The LEDs 4 in each corresponding group 15 emit light at different wavelengths. This is in... Figure 9 The groups 15 are represented by the letters R, G, and B, which represent the colors red, green, and blue. The corresponding group 15 is further typically associated with control logic 16. The light-emitting diodes 4 of the corresponding group 15—typically including control logic 16—are housed in a common housing 17. Within the scope of this invention, "housing" signifies the corresponding mounting unit disposed on the corresponding light-emitting strip 3.
[0079] A supply voltage U is provided to control logic 16 and the corresponding LEDs 4 of group 15. Furthermore, control logic 16 is connected to the fundamental potential GND. Control logic 16 is supplied with a control signal D, which includes manipulation c* for the LEDs 4 of the corresponding group 15. Control logic 16 then accordingly manipulates the LEDs 4 of the corresponding group 15. If necessary, control logic 16 also outputs an additional control signal D', which is assigned to LEDs 4 of other groups 15.
[0080] In the case of group 15 forming LED 4, Figure 2 The boxes shown in the figure, which are marked with reference numeral 4 (for light-emitting diodes), represent such groups 15 of light-emitting diodes 4.
[0081] In summary, this utility model therefore relates to the following facts:
[0082] Medical device 1 has multiple light-emitting strips 3 and a control device 7 for manipulating the light-emitting strips 3, each of which has multiple individually operable light-emitting diodes 4. The control device 7 dynamically determines a corresponding light-emitting state Z* based on the state ST of medical device 1 and / or the state ST of the surrounding environment of medical device 1. Each light-emitting state includes a sub-state z* for each light-emitting diode 4, and the corresponding light-emitting diode 4 should be operated accordingly. The control device 7 transmits the corresponding light-emitting state Z* to the light-emitting strips 3.
[0083] This invention has numerous advantages. In particular, the luminescent strip 3 can be used in an efficient manner to convey information to operators and / or patients.
[0084] Although the details of the present invention have been described in detail through preferred embodiments, the present invention is not limited to the disclosed examples, and other variations can be derived by those skilled in the art without departing from the protection scope of the present invention.
[0085] List of reference numerals
[0086] 1. Medical equipment
[0087] 2 channels
[0088] 3. Emitting strips
[0089] 4. Light Emitting Diode
[0090] 5 Controllers
[0091] 6 Interfaces
[0092] 7. Control equipment
[0093] 8. Other interfaces
[0094] 9. Control Procedure
[0095] 10 Machine Code
[0096] 11 Sensors
[0097] 12 Storage devices
[0098] 13 Program Files
[0099] 14. Interpreter
[0100] 15. Groups of light-emitting diodes
[0101] 16 Control Logic
[0102] 17. Casing
[0103] A instruction
[0104] c* control
[0105] D, D' control signals
[0106] GND fundamental potential
[0107] P parameter
[0108] R routines
[0109] Steps S1 to S16
[0110] U Supply Voltage
[0111] V Preset
[0112] The required luminescence state of Z*
[0113] z* Sub-luminescent state
[0114] z Actual luminous state
Claims
1. Medical device (1) with a plurality of light strips (3) and a control device (7) for manipulating the light strips (3), the light strips (3) each having a plurality of individually manipulable light diodes (4), wherein the control device (7) dynamically determines a respective light state (Z*) with the state (ST) of the medical device (1) and / or with the state (ST) from the surroundings of the medical device (1), the light state (Z*) comprising for the light diodes (4) respectively a substate (z*) to which the respective light diode (4) should correspond in its operation, and the control device (7) communicates the respective light state (Z*) to the light strips (3).
2. Medical device (1) according to claim 1, characterized in that the control device (7) uses the state (ST) from the surroundings of the medical device (1) and the state (ST) is an acoustic signal or a motion signal.
3. Medical device (1) according to claim 1 or 2, characterized in that - routines (R) are stored on the control device (7), - the respective routine (R) contains a code which can be directly processed by the control device (7) and which defines a sequence of light states (Z*) determined by the respective routine (R), which the light diodes (4) of the respective light strip (3) should assume, and - the control device (7) determines, with the state (ST) of the medical device (1) and / or with the state (ST) from the surroundings of the medical device (1), which of the routines (R) the control device executes.
4. Medical device (1) according to claim 3, characterized in that - a program file (13) is also stored on the control device (7), - the program file (13) contains a sequence of instructions (A) which can be processed by the control device (7) by means of an interpreter (14) stored on the control device (7) by interpretation, - the instructions (A) determine at least which of the routines (R) should be processed, and - the control device (7) determines, with the state (ST) of the medical device (1) and / or with the state (ST) from the surroundings of the medical device (1), with which of the instructions (A) of the program file (13) the control device (7) starts the interpretation of the instructions (A).
5. Medical device (1) according to claim 4, characterized in that the instructions (A) determine only which of the routines (R) should be processed.
6. Medical device (1) according to claim 4, characterized in that The routine (R) is configured as a routine (R) which can be parameterized by means of a parameter (P) and the instructions (A) of the program file (13) comprise a determination of the parameter (P) of the routine (R) such that the routine (R) when executed corresponds to the determination of the parameter (P) of the routine (R) given by the instructions (A) of the program file (13).