TECHNIQUE FOR CONTROLLING OPERATION OF A USER ADJUSTABLE CARDIAC PACEMAKER OR A SOFTWARE MODEL THEREOF IN A TRAINING MODE

Abstract

A technique of controlling operation of a user-adjustable cardiac pacemaker, or a software model thereof, in a training mode is described. A method implementation of the technique comprises generating at least one cardiac event by a feedback-based heart simulator, wherein the cardiac event includes a pulse parameter set defining at least a pulse amplitude. The method further comprises transmitting the at least one cardiac event, or a first signal representation derived therefrom, to an electro cardiogram, ECG, generator configured to generate ECG graphics triggering a user to perform, in the training mode, one or more user adjustments at the cardiac pacemaker or its software model. Further still, the method comprises transmitting the at least one cardiac event, or a second signal representation derived therefrom, to the cardiac pacemaker or its software model, and acquiring stimulus information on one or more stimuli generated by the cardiac pacemaker or its software model. In the method presented herein, the stimulus information is fed back to the heart simulator for use in generation of one or more further cardiac events.

Claims

1. A method of controlling operation of a user-adjustable cardiac pacemaker, or a software model thereof, in a training mode, the method comprising: generating at least one cardiac event by a feedback-based heart simulator, wherein the cardiac event includes a pulse parameter set defining at least a pulse amplitude; transmitting the at least one cardiac event, or a first signal representation derived therefrom, to an electro cardiogram, ECG, generator configured to generate ECG graphics triggering a user to perform, in the training mode, one or more user adjustments at the cardiac pacemaker or its software model; transmitting the at least one cardiac event, or a second signal representation derived therefrom, to the cardiac pacemaker or its software model; acquiring stimulus information on one or more stimuli generated by the cardiac pacemaker or its software model; and feeding the stimulus information back to the heart simulator for use in generation of one or more further cardiac events.

2. The method of claim 1, further comprising: receiving, from the cardiac pacemaker or its software model thereof, adjustment information indicative of the one of more user adjustments.

3. The method of claim 2, wherein the stimulus information is acquired from analog stimuli output by the cardiac pacemaker; and the adjustment information is received as digital information from the cardiac pacemaker.

4. The method of claim 2, wherein the adjustment information is indicative of one or more adjustment parameters comprising a pacing rate, a capture threshold, a sensing threshold, an atrio-ventricular delay, and a pacing mode.

5. The method of claim 4, wherein the adjustment information comprises a time stamp.

6. The method of claim 2, further comprising: evaluating the adjustment information with respect to one or more of an expected user adjustment and the at least one cardiac event; and generating user training information indicative of a result of the evaluation.

7. The method of claim 1, wherein the at least one cardiac event is transmitted to at least one of a user training application and the ECG generator in association with a time stamp.

8. The method of claim 1, further comprising converting the pulse parameter set into at least one of the first and the second signal representation, wherein the respective signal representation is time-varying and representative of the pulse amplitude.

9. The method of claim 8, wherein the at least one of the first and the second signal representation is indicative of at least one of a pre-defined pulse duration and a pre-defined pulse shape.

10. The method of claim 1, further comprising generating by the heart simulator the at least one cardiac event so as to trigger the one or more user adjustments at the cardiac pacemaker or its software model.

11. The method of claim 10, wherein the at least one cardiac event is at least partially defined by a training program that controls operation of the heart simulator.

12. The method of claim 10, wherein the at least one cardiac event is at least partially defined by control information that is received via a control interface.

13. The method of claim 10, wherein the at least one cardiac event is at least partially generated or defined in response to the adjustment information.

14. The method of claim 1, wherein the pulse parameter set further defines an event type identifier associated with the pulse amplitude, wherein the event type identifier is indicative of the cardiac event being of a ventricular event type or an atrial event type.

15. The method of claim 1, wherein the stimulus information is indicative of one or more of a signal amplitude and/or an associated heart chamber identifier.

16. An apparatus for controlling operation of a user-adjustable cardiac pacemaker, or a software model thereof, in a training mode, the apparatus being configured to: generate at least one cardiac event by a feedback-based heart simulator, wherein the cardiac event includes a pulse parameter set defining at least a pulse amplitude; transmit the at least one cardiac event, or a first signal representation derived therefrom, to an electro cardiogram, ECG, generator configured to generate ECG graphics triggering a user to perform one or more user adjustments at the cardiac pacemaker or its software model in the training mode; transmit the at least one cardiac event, or a second signal representation derived therefrom, to the cardiac pacemaker or its software model; acquire stimulus information on one or more stimuli generated by the cardiac pacemaker or its software model; and feed the stimulus information back to the heart simulator for use in generation of one or more further cardiac events.

17. The apparatus of claim 16, further configured to: receive, from the cardiac pacemaker or its software model thereof, adjustment information indicative of the one or more user adjustments; evaluate the adjustment information with respect to one or more of an expected user adjustment and the at least one cardiac event; generate user training information indicative of a result of the evaluation; and generate by the heart simulator the at least one cardiac event so as to trigger the one or more user adjustments at the cardiac pacemaker or its software model.

18. A user-adjustable external cardiac pacemaker comprising: a first input interface configured to receive a signal representation of a cardiac event having a pulse amplitude; a first output interface configured to output one or more stimuli generated by the cardiac pacemaker; and a second output interface configured to output adjustment information indicative of a user adjustment.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Further aspects, details and advantages of the present disclosure will become apparent below from a detailed description of exemplary embodiments and from the drawings, wherein:

[0040] FIG. 1 is a diagram illustrating a training system embodiment of the present disclosure;

[0041] FIG. 2 is a block diagram illustrating an apparatus embodiment in accordance with the present disclosure;

[0042] FIG. 3 is a flow diagram of a method embodiment of the present disclosure;

[0043] FIGS. 4-6 are schematic diagrams illustrating exemplary aspects of apparatus embodiments of the present disclosure;

[0044] FIGS. 7-9 are schematic illustrations of pulse shape embodiments;

[0045] FIG. 10 is a schematic diagram illustrating exemplary aspects of a more detailed apparatus embodiment of the present disclosure;

[0046] FIG. 11 is a schematic illustration of a heart simulator embodiment;

[0047] FIGS. 12-14 are schematic illustrations of training system set-ups according to embodiments of the present disclosure; and

[0048] FIG. 15 is a schematic illustration of a control interface for a heart simulator.

DETAILED DESCRIPTION

[0049] In the following description, for purposes of explanation and not limitation, specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent to one skilled in the art that the present disclosure may be practiced in other embodiments that depart from these specific details.

[0050] While, for example, some embodiments of the following description focus on an exemplary external cardiac pacemaker and an associated training system, the present disclosure is not limited in this regard. The present disclosure could also be implemented in regard to an internal cardiac pacemaker or in regard to a software model of an internal or external cardiac pacemaker.

[0051] Those skilled in the art will further appreciate that the steps, services and functions explained herein may be implemented using individual hardware circuits, using software functioning in conjunction with a programmed microprocessor or general purpose computer, using one or more application specific integrated circuits (ASICs) and/or using one or more digital signal processors (DSP). It will also be appreciated that when the present disclosure is described in terms of a method, it may also be embodied in one or more processors and one or more memories coupled to the one or more processors, wherein the one or more memories store one or more computer programs that cause the one or more processors to perform the steps, services and functions disclosed herein when executed by one or more processors.

[0052] In the following description of exemplary embodiments, the same reference numerals denote the same or similar components.

[0053] FIG. 1 illustrates an embodiment of a training system comprising an apparatus 100 for controlling operation of a user-adjustable cardiac pacemaker 200 that is also comprised by the training system. In the present embodiment, the pacemaker 200 is realized as an external or an internal pacemaker, although it could alternatively be implemented as a software model comprised by the apparatus 100 or another device that is coupled to the apparatus 100.

[0054] The training system further comprises an ECG generator 300 configured to generate a ECG graphics for presentation by an ECG display device 400 to a user 500 to be trained. In some variants, the ECG generator 300 is integrated into the apparatus 100. In other variants, the ECG generator 300 is a device co-located with the apparatus 100 or located remotely therefrom. The ECG generator 300 may in particular be configured to generate a surface ECG.

[0055] As illustrated in FIG. 1, the apparatus 100 comprises a heart simulator 110 that is configured to generate digital cardiac events. Each cardiac event may at least be indicative of a pulse amplitude and, optionally, one or more further pulse parameters. The pulse amplitude may be indicated in mV. In some implementations, the apparatus 100 is realized as an embedded platform into which the heart simulator 110 is integrated. The implementation as an embedded platform permits an efficient real-time operation of the apparatus 100 in an inner feedback loop 100A with the pacemaker 200 and an outer feedback loop 1006 with the user 500.

[0056] The heart simulator 110 may be implemented as a dedicated digital hardware component (e.g., with a dedicated processor and a dedicated memory that stores program code causing the processor to simulate certain functions of a human heart). The heart simulator 110 offers settings and configurations that can be controlled in run-time by one or both of a suitable training program and a control interface (not shown).

[0057] The apparatus 100 further comprises a digital output interface 120 configured to output the cardiac events generated by the heart simulator 110 to the ECG generator. The digital output interface 120 may conform to a Universal Serial Bus (USB) standard or any other standard for digital data communication. The apparatus 100 further comprises a digital/analog (D/A) converter 130 configured to convert the digital cardiac events generated by the heart simulator 110 into an analog signal representation in the form of time-varying cardiac pulses. Those cardiac pulses can be output via an analog output interface 140 of the apparatus 100 to the pacemaker 200. The analog output interface 140 can be realized using a mechanical plug connection.

[0058] The pacemaker 200 is configured to receive the cardiac pulses at an analog input interface 210. From the perspective of the pacemaker 200, those cardiac pulses are generated by a human heart and received via corresponding sensing leads that are normally electrically coupled to the analog interface 210 and configured to be suitably placed to detect a patient's heart activity. In case the pacemaker 200 is configured as an external pacing device, those sensing leads are commonly transvenous pacing leads or surgical pacing wires (also referred to as heart wires. In other variants, the sensing leads can be realized as patches configured to be placed on a patient's skin surface (e.g., in case of transthoracic pacing). The sensing leads may also serve as leads for stimulation. In the presently described training scenario, the sensing leads are coupled to the analog output interface 140 using an optional adapter (or replaced by a cable extending from the analog output interface 140 of the apparatus 100 to the analog input interface 210 of the pacemaker 200). In case the pacemaker 200 is an internal pacing device configured to be implanted, its sensing leads are configured to be implanted as well. In the presently described training scenario, such an internal pacemaker 200 will, of course, not be in an implanted state, so that its sensing leads can easily be coupled, optionally via a suitable adapter, to the analog output interface 140.

[0059] The pacemaker 200 is configured to generate electric stimuli. Those stimuli may at least in part be generated responsive to the cardiac pulses output by the apparatus 100 and sensed by the pacemaker 200. From the perspective of the pacemaker 200, those stimuli are output to a human heart via an analog output interface 212 to which corresponding stimulation leads can electrically be coupled. The simulation leads are configured to be suitably placed to stimulate a patient's heart activity. In case the pacemaker 200 is configured as an external pacing device, those stimulation leads are commonly transvenous pacing leads or surgical wires, but they may also be realized as patches configured to be placed on a patient's skin surface. The stimulation leads may also serve as leads for sensing. In the presently described training scenario, the stimulation leads are coupled to an analog input interface 150 of the apparatus 100 using an optional adapter (or replaced by a cable extending from the analog output interface 212 of the pacemaker 200 to the analog input interface 150 of the apparatus 100). In case the pacemaker 200 is an internal pacing device configured to be implanted, its stimulation leads are configured to be implanted as well. In the presently described training scenario, the internal pacemaker 200 will evidently not be in an implanted state, so that its stimulation leads can easily be coupled, optionally via a suitable adapter, to the analog input interface 150.

[0060] In some variants, the two analog interfaces 140, 150 on the side of the apparatus are integrated into a single analog input/output interface. In case the pacemaker 200 is realized as a software model external or internal to the apparatus 100, those analog interfaces 140, 150 can be replaced by at least one digital interface or an Application Programming Interface (API).

[0061] As illustrated in FIG. 1, the apparatus 100 comprises an analog/digital (ND) converter 160 coupled between the analog input interface 150 and the heart simulator 110 to close the feedback loop 100A. The ND converter 160 converts the analog electric stimuli output by the pacemaker 200 into a digital signal representation comprising stimulus information indicative of the electric stimuli. In general, the stimulus information will at least be indicative of a pulse amplitude per detected electric stimulus.

[0062] As has been explained above, the pacemaker 200 is adjustable by the user 500 to control pacemaker operation in accordance with a patient's needs. In the present training scenario, those needs may be indicated to the user 500 by one or more cardiac events generated by the heart simulator 110 and visualized at the display device 400 to trigger one or more user adjustments at the pacemaker 200 (see FIG. 1). Depending on the pacemaker type, exemplary user adjustments at the pacemaker 200 comprise, but are not limited to, one or more of a pacing rate adjustment, a capture threshold adjustment, a sensing threshold adjustment, an adjustment of an atrio-ventricular delay, and a pacing mode adjustment. A pacing mode adjustment comprises adjustment of a dedicated mode or switching form one mode to another mode (e.g., from an x-channel mode to an y-channel mode, with x≠y).

[0063] In the case of an external pacemaker 200, the user adjustments may directly be performed at a mechanical user interface of the pacemaker 200 (e.g., at one or more dials, one or more switches or one or more buttons). In the case of an internal pacemaker 200, the user adjustments may be performed at a dedicated control device (not shown in FIG. 1) and may wirelessly be communicated to the pacemaker 200. The control device may take the form of a computing device (e.g., a tablet or personal computer) having a graphical user interface permitting the user 500 to input the desired adjustments.

[0064] The pacemaker 200 may in some implementations be configured to generate adjustment information indicative of the user adjustments. The user adjustment information may take the form of a parameter set indicative of a parameter type and, optionally, an associated time stamp indicative of when the adjustment was made. The parameter set may further comprise a value indicative of (e.g., quantifying) the user adjustment. As such, the parameter set may for at least some user adjustments comprise a type/value (T/V) pair with an associated time stamp.

[0065] In the case of an external pacemaker 200, the adjustment information may be output, via an optional digital interface 214 of the pacemaker 200 to one or both of the apparatus 100 and the ECG generator 300 (or to a dedicated training sub-system), as indicated by dashed lines in FIG. 1. As also shown in dashed lines in FIG. 1, the apparatus 100 may comprise a dedicated digital interface 170 configured to receive the adjustment information from the external pacemaker 200. The adjustment information will thus be received by the apparatus 100 separately from the stimuli and the associated stimulus information. In the case of an internal pacemaker 200, the adjustment information may wirelessly be communicated from the internal pacemaker 200 to the dedicated control device that was used to input the user adjustments.

[0066] In the following, an exemplary implementation of the apparatus 100 of FIG. 1 will be described with reference to FIG. 2, and general operation of the apparatus 100 will be described with reference to a method embodiment illustrated in flow diagram 301 of FIG. 3.

[0067] In the apparatus embodiment illustrated in FIG. 2, the apparatus 100 comprises a processor 202 and a memory 204 coupled to the processor 202. The memory 204 stores program code (e.g., in the form of a set of instructions) that controls operation of the processor 202 so that the apparatus 100 is operative to perform any of the method aspects presented herein. As understood herein, a processor, such as processor 202, may be implemented using any processing circuitry and is not limited to, for example, a single processing core but may also have a distributed topology (e.g., using cloud computing resources).

[0068] The apparatus 100 of FIG. 2 further comprises at least one input interface 206 and at least one output interface 208. The at least one input interface 206 may be configured to implement the interfaces 150, 170 described above with reference to FIG. 1. The at least one output interface 208 may be configured to implement the interfaces 120, 140 described above with reference to FIG. 1. In some variants, the apparatus 100 may further comprise analog electronics not illustrated in FIG. 2.

[0069] The heart simulator 110 described above with reference to FIG. 1 may be realized using program code stored in the memory 204 and executed by the processor 200, or may alternatively be realized on a dedicated sub-platform integrated into the apparatus 100.

[0070] Now referring to the flow diagram 301 of FIG. 3, operation of the apparatus 100 comprises a step 302 of generating at least one cardiac event by the feedback-based heart simulator 110. The cardiac event includes a pulse parameter set defining at least a pulse amplitude of a cardiac pulse to be output via the analog output interface 140 to the pacemaker 200. In some variants, the heart simulator 110 is configured to generate in parallel atrial cardiac events and ventricular cardiac events (in accordance with two dedicated logical event channels). In other variants, the heart simulator is configured to generate in parallel atrial cardiac events and ventricular cardiac events for the left ventricle and the right ventricle (in accordance with three dedicated logical event channels). The pulse parameter set will then further define an event type identifier associated with the pulse amplitude. The event type identifier is indicative of the cardiac event being of a ventricular event type or an atrial event type.

[0071] The method further comprises a step 304 of transmitting the at least one cardiac event, or a first signal representation derived therefrom (e.g., a time-varying signal representation), to the ECG generator 300. As explained above, the ECG generator 300 is configured to generate ECG graphics for visualization by the display device 400. The visualized ECG graphics trigger the user 500 to perform, in a training mode, one or more user adjustments at the cardiac pacemaker 200 (or its software model), such as one or more of a pacing rate adjustment, a capture threshold adjustment, a sensing threshold adjustment, and a pacing mode adjustment.

[0072] Further still, the method comprises a step 306 of transmitting the at least one cardiac event, for example in the form of an analog signal representation generated by the D/A converter 130, via the analog output interface 140 to the cardiac pacemaker 200. In the case a software model implementation of the pacemaker 200, no such D/A conversion will of course be required.

[0073] In step 308, the apparatus 100 acquires stimulus information on one or more electric stimuli generated by the cardiac pacemaker 200 (or its software model). Acquisition of the stimulus information comprises receipt of the stimuli in analog form by the apparatus 100 via the analog input interface 150 and conversion of the analog stimuli by the ND converter 160 into a digital format representative of the stimulus information. The stimulus information is indicative of at least one signal amplitude.

[0074] In a two channel scenario, the electric stimuli are generated separately by the pacemaker 200 for an atrium and a ventricle of a patient's heart to be applied via dedicated stimulation leads. In this case, the analog interface 150 may also include two dedicated channels (e.g., in the form of two dedicated electrical contacts). Similar considerations apply for a 3-channel or a 4-channel scenario. The stimulus information generated by the A/D converter 160 will thus comprise an associated heart chamber identifier per signal amplitude. The heart chamber identifier is indicative of a particular signal amplitude being intended to be applied to the atrium of the ventricle.

[0075] In step 310 of the method illustrated in FIG. 3, the stimulus information is fed back to the heart simulator 110 for use in generation of one or more further cardiac events. The heart simulator 110 is thus configured to process the stimulus information in a feedback-based manner in the cardiac event generation process.

[0076] In an optional step not illustrated in FIG. 3, the apparatus 100 further receives, via the optional digital interface 170, the adjustment information as generally described above with reference to FIG. 1 (see the dotted lines in FIG. 1). In certain variants, the adjustment information may additionally, or alternatively, be transmitted by the pacemaker 200 to any other system component illustrated (or not illustrated) in FIG. 1. In all those variants, the adjustment information thus received is generally processed to generate a feedback to the user 500 as to whether or not the user adjustments were successful in accordance with a pre-defined training objective (e.g., tackling simulated arrhythmia).

[0077] The (external or internal) cardiac pacemaker 200 presented herein may be configured to output the adjustment information in a push-based manner (e.g., in regular intervals or upon detection that a user adjustment has actually been performed). Additionally, or as an alternative, the adjustment information may be output by the pacemaker 200 in a pull-based manner (e.g., in a response message that is generated by the pacemaker 200 upon receipt of a request message). The adjustment information may comprise a data set generally indicative of the current setting(s) of one more adjustable parameters of the pacemaker 200 or specifically indicative of a particular parameter adjustment performed by the user 500. In the first case, a particular parameter adjustment may be derived from a change in the current parameter setting(s) from one data set to a subsequent data set.

[0078] FIG. 4 illustrates further aspects of the system illustrated in FIG. 1 and in particular of the apparatus 100. Most of the interfaces shown in FIG. 1 have been omitted for ease of illustration.

[0079] As shown in FIG. 4, the apparatus 100 comprises analog electronics 410 and digital electronics 420 powered by a power supply 430. The ECG generator 300 is exemplarily configured as a personal computer (PC) 300A coupled to the apparatus 100 via the interface 120 (here: a bi-directional USB interface that additionally powers the power supply 430). The PC 300A hosts a software application that is programmed to generate ECG graphics from cardiac events generated by and received from the apparatus 100. The ECG graphics will then be output to the user 500 via the display device 400 of FIG. 1.

[0080] The digital electronics 420 of FIG. 4 contain an embedded software-programmable microprocessor system or programmable digital logic implementing the heart simulator 110 of FIG. 1 to permit real-time operation of the heart simulator 110 in the feedback loop 100A with the cardiac pacemaker 200. This real-time operation permits a realistic simulation of a real heart based on feedback loop from a real pacemaker 200 and, thus, a more efficient user training.

[0081] The digital electronics 420 exchange digital signals with the analog electronics 410 (which, therefore, comprise the D/A converter 130 and the ND converter 160 of FIG. 1) and control operation thereof. The electronic signals comprise the signaling of cardiac events to the analog electronics 410 and the signaling of stimulus information to the digital electronics 420, as generally explained above. Control of the analog electronics 410 by the digital electronics 420 comprise electric load switching.

[0082] Now further referring to FIG. 5, central components of the analog electronics 410 are illustrated. The analog electronics 410 comprise the D/A converter 130 of FIG. 1 to convert a time-varying digital cardiac event signal (or a sequence of discrete cardiac event data sets) from the digital electronics 420 into the cardiac pulses (as time-varying analog signals). The analog electronics 410 further comprise the A/D converter 160 of FIG. 1 to convert a time-varying analog stimuli signal from the pacemaker 200 into the stimulus information (as sequence of discrete data sets). The analog electronics 410 also comprises a component 510 configured for load impedance matching between the pacemaker 200 on the one side and the apparatus 100 on the other side. As shown in FIG. 5, the load impedance matching component 510 is controllable by the digital electronics 420 (e.g., so that the apparatus 100 can be used with different types of pacemakers 200).

[0083] FIG. 5 exemplarily illustrates a 3-channel pacemaker 200 having dedicated sensing and stimulation leads for the atrium (A), the right ventricle (VR) and the left ventricle (VL). This means that dedicated cardiac events for the atrium, the left ventricle and the right ventricle are generated in parallel by the heart simulator 110 comprised by the digital electronics 420, as shown in FIG. 6, and corresponding stimuli are generated in parallel by the pacemaker 200.

[0084] FIG. 6 further illustrates that in a 3-channel scenario, the D/A converter 130 of FIGS. 1 and 5 comprises three dedicated D/A converters 130A, B, C (i.e., one per channel A, RF, LV). In a similar manner, the ECG generator 300 comprises three dedicated pulse generators 320A, B, C (i.e., one per channel A, RV, LV). Those pulse generators 320A, B, C will in parallel generate a dedicate ECG pulse per cardiac event and channel (in either parameterized form or as partial graphics). Those three individual “intercardial” ECG (IECG) pulses are then superimposed and modelled by a superposition component 330 to generate the ECG graphics (e.g., simulating a surface ECG) for a particular period of time (as defined, e.g., by a simulated heart rate). Successive ECG graphics for successive periods of time will then be continuously visualized on the display device 400. It will be appreciated that the scenario of FIG. 6 could easily be modified for a 2-channel scenario with an A channel and a V channel only, of for any other number of channels. In a similar manner, the scenario of FIG. 6 could easily be modified for a 3-channel scenario encompassing right atrium (AR), left atrium (AL) and a single ventricle (VR or VL), or for any other number of channels.

[0085] In some variants, each of the pulse generators 320A, B, C is configured to generate a geometrically defined pulse shape. A geometrically defined pulse shape may be characterized by a limited number of pulse parameters per cardiac event, including a pulse amplitude that may vary from one cardiac event to the subsequent cardiac event on the same channel. Compared to physiologically “correct” pulse shapes, geometrically defined pulse shapes can be generated faster by the ECG generator 300 and are easier to cognitively “process” by the user 500 when visualized on the display device 400. The latter aspect is particularly beneficial in the training scenario described herein.

[0086] The pulse shape may be triangular with a rising flank in a temporal direction towards a peak defined by the pulse amplitude and a falling flank behind that peak. In some variants, a temporal length of the pulse may be pre-defined (e.g., fixed), or it may alternatively be signaled as a further pulse parameter. In a similar manner, a temporal length of at least one of the rising flank and the falling flank may be pre-defined (e.g., fixed), or it may alternatively be signaled as a further pulse parameter.

[0087] An exemplary triangular pulse 700 with an overall duration T, a rising flank having a duration t, a peak defined by a pulse amplitude A.sub.T, and a falling flank having a duration T-t is illustrated in FIG. 7. The duration t of the rising flank and the overall duration T of the pulse are fixed in the millisecond regime, as indicated in FIG. 7. In this way, the number of pulse parameters to be communicated to the ECG generator 300 is reduced to the pulse amplitude, and ECG graphics generation by the ECG generator 300 can be accelerated. In some variants, the triangular pulse shape may conform to a test signal generator signal as defined in ISO 14708-2:2019-09.

[0088] FIG. 8 illustrates in a time diagram 800 the parallel generation of pulses by the ECG generator 300 in the 3-channel scenario of FIG. 6. As becomes apparent from FIG. 6, the individual pules have triangular pulse shapes.

[0089] In the simulated atrial signal (A) of FIG. 8, each peak represents a so-called P wave pulse amplitude. The atrial pulse rate is Rate.sub.A=60/PP_Interval (in bpm), wherein the PP_Interval is the interval between successive P waves due to atrial depolarization. In the simulated right ventricular signal (VR), each peak represents a so-called R wave pulse amplitude, and similar for the left ventricular signal (VL). The ventricular pulse rate is Rate.sub.v =60/RR_Interval (in bpm), wherein the RR_Interval is the interval between successive R waves. The ventricular pulse rate Rate.sub.v may be equal to the atrial pulse rate Rate.sub.A or less in case of a so-called 2:1 block. An AV interval is defined as the delay between the atrial signal and the ventricular signal (in FIG. 8: for the right ventricle). A VV interval is defined as the delay between the signal of the right ventricle and the signal of the left ventricle.

[0090] FIG. 9 illustrates the resulting superposition of triangular pulses as visualized by the display device 400 for a 2-channel scenario. The smaller triangular pulses visualize P waves, whereas the larger triangular pulses visualize R waves. Also the heart rate will be visualized by the display device (as a numerical value in bpm). The heart rate will be calculated by the ECG generator 300 based on the cardiac events and the associated time stamps. A similar superposition and visualization as shown in FIG. 9 will be obtained in the 3-channel scenario of FIGS. 6 and 8.

[0091] For properly visualizing the temporal relationship of the pulses on each channel and across different channels, the cardiac events are communicated from the apparatus 100 to the ECG generator 300 together with associated time stamps. The ECG generator 300 is configured to evaluate the time stamps associated with the cardiac events so as to properly align same in time in the dynamically generated ECG graphics (see FIG. 8). The time stamps may be generated by the apparatus 100 in different ways, for example by “packaging” a cardiac event output by the heart simulator 100 together with a time stamp freshly generated by the apparatus 100 (e.g., by a local clock operating on a millisecond scale) into a cardiac event message output to the ECG generator 300 (e.g., to an external computing device such as PC 300A programmed to emulate the ECG generator 300). In a 2-channel scenario, the cardiac event message will further comprise an event type identifier indicative of the cardiac event being of a ventricular event type or an atrial event type. In a 3-channel scenario (see FIGS. 6 and 8), the ventricular event type will further distinguish between a left ventricle and a right ventricle. The event type identifier thus serves as a channel identifier for the ECG generator 300.

[0092] FIG. 10 is a schematic diagram illustrating a more detailed apparatus embodiment of the present disclosure. The following description of FIG. 10 will focus on some additional system components such as a controller 515 as part of the digital electronics 420 of the apparatus 100.

[0093] The controller 515 interfaces the heart simulator 110 as well as the PC 300A with the ECG generator 300. The controller 515 is in charge of generating the cardiac event messages. To this end, the controller 515 associates each cardiac event output as pulse parameter set by the heart simulator 110 with a time stamp and, optionally, an event type identifier (i.e., channel identifier) and packages those data into the cardiac event message that is then output to the PC 300A. In one implementation, the pulse parameter set as generated by the heart simulator 110 will only include a single parameter indicative of a pulse amplitude (e.g., in mV). In another implementation, the pulse parameter set additionally comprises the event type identifier (so it will not need to be attributed by the controller 515).

[0094] The controller 515 in some variants also offers a control interface of the apparatus 100 for receiving, from the PC 300A or another computer operated by a trainer, control information. The control information controls operation of the heart simulator 110 (e.g., in reals time). As an example, the control information may be indicative of parameter settings to be applied by the heart simulator 110 for generation of the cardiac events.

[0095] As illustrated in FIG. 10, the digital electronics 420 further comprise a heart model database 520 with settings or configurations that define one or more training programs to control the heart simulator 110 in run-time. Possible control parameters that can be set or configured in this regard define a sinus rhythm, the AV block explained above with reference to FIG. 8, atrial fibrillation, and so on.

[0096] Still further, the digital electronics 420 comprise a pacemaker stimulus detector 530 coupled between A/D converter(s) 150 on the one hand and the heart simulator 110 on the other hand. It will be appreciated that there will generally be one A/D converter per pacemaker output channel (in a similar manner as illustrated for the three D/A converters 130A-C in FIG. 6). In some variants, the pacemaker stimulus detector 530 may be integrated into the heart simulator 110.

[0097] The pacemaker stimulus detector 530 is configured apply per channel one or multiple sensing thresholds to the digital output signals of the A/D converter(s) 150. A first sensing threshold per channel may relate to a minimum stimulus pulse amplitude (e.g., in terms of a measured voltage). An optional second sensing threshold may relate to a minimum stimulus pulse duration (e.g., in milliseconds). Both threshold types may be adjustable. The pacemaker stimulus detector 530 will only signal a stimulus included in the digital output signal of the A/D converter(s) 160 to the heart simulator 110 in case that stimulus is detected to satisfy the thresholding condition(s). Otherwise, the heart simulator 110 is not notified thereof. The stimulus information signaled to the heart simulator 100 for a detected stimulus include a detected stimulus pulse amplitude (e.g., in V) and an associated heart chamber identifier. In a 2-channel scenario, the heart chamber identifier is indicative of an atrium or of a ventricle. In a 3-channel scenario, the heart chamber identifier will additionally distinguish between a left ventricle and a right ventricle.

[0098] Further still, the digital electronics 420 comprise a cardiac pulse generator 540 coupled between the heart simulator 110 on the one hand and the D/A converter(s) 130 on the other hand. It will be appreciated that there will generally be one D/A converter 130 per pacemaker input channel (see the exemplary three D/A converters 130A-C in FIG. 6). In some variants, the cardiac pulse generator 540 may be integrated into the heart model 110.

[0099] The cardiac pulse generator 540 translates each cardiac event (i.e., each pulse parameter set) output by the heart simulator 110 into a time-varying digital signal indicative of a dedicated pulse shape. In this regard, a dedicated time-varying signal will be generated per channel (i.e., per D/A converter, see FIG. 6). The pulse shape may in particular be triangular, as illustrated in FIG. 7. The pulse shape generated by the cardiac pulse generator 540 need, however, not necessarily be the same pulse shape as the one that is to be visualized.

[0100] In case of a triangular pulse shape with a pre-defined pulse duration T and a pre-defined duration t of the rising flank (see FIG. 7), the pulse parameter set may just include the pulse amplitude A.sub.T (and, optionally, the event type identifier) as input information for the cardiac pulse generator 540. In a 3-channel scenario, the digital output of the cardiac pulse generator 540 may have a temporal appearance similar to the scenario illustrated in FIG. 8. In view of the real-time operation of the apparatus 100, no time stamping is needed for continuous operation of the cardiac pulse generator 540.

[0101] The digital output generated by the cardiac pulse generator 540 per channel will not only be fed to the one or more D/A converters 130, but in parallel to an optional—ECG generator 300B coupled to a likewise optional ECG monitor 400B. The ECG monitor 400B is the “real” display device that will typically be used in connection with the “real” pacemaker 200 for patient treatment by the user 500 to be trained. Since the ECG monitor 400B typically has an analog input interface, the mock-up ECG generator 300B comprises one D/A converter per channel to convert the digital signal output by the cardiac pulse generator 540 into an analog ECG graphics signal the will trigger the ECG monitor 400B to display the ECG graphics to the user 500 that is to be trained. It will be appreciated that the mock-up ECG generator 300B and the ECG monitor 400B could be used in addition or as an alternative to the PC 300A and the display device 400A for user training. For example, in the scenario of FIG. 1, the mock-up ECG generator 300B and the ECG monitor 400B could be used to implement the ECG generator 300 and the display device 400, respectively.

[0102] FIG. 11 is a schematic illustration of a 2-channel heart simulator embodiment. The heart simulator 110 has two logical inputs and two logical outputs differentiated based on the heart chamber identifier and event type identifier, respectively. As such, the heart simulator 110 of FIG. 11 has one input and one output per channel (atrial or “A” vs. ventricular or “V”). The inputs “A STIM” and “V STIM” are coupled to the cardiac stimulus detector 530, while the outputs “A SENSE” and “V SENSE” are coupled to the cardiac pulse generator 540. The respective input and output information will generally be indicative of a respective pulse amplitude in combination with a channel identifier, as generally explained above.

[0103] The main operational mechanism of the heart simulator 110 is to produce atrial and/or ventricular heart muscle depolarizations (depicted by the round circles A and V; see reference numeral A1 and V1, respectively). For each channel, the depolarization is transformed into a pulse parameter indicative of voltage value that represents a pulse amplitude peak, which then may be detected by the attached pacemaker 200 as atrial or ventricular sense event, respectively. Optionally noise events A2, V2 can be added (e.g., at a certain interval per channel).

[0104] Each depolarization starts the absolute refractory period for the atrium (ARP) A7 and the ventricle (VRP) V7. As long as the absolute refractory period is not expired, all triggers (from whatever source) are ignored at an associated refractory gate A3, V3. The main heart oscillators are a PP timer A5 (aka. sinus node) and an RR timer V5. These timers realize what is known as heart rate. The heart simulator 110 can be triggered by the pacemaker output (A STIM or V STIM). However, any incoming pacemaker stimulation must pass the capture gate A3, A7. This means that the stimulation voltage must be above a capture threshold as defined by the cardiac stimulus detector 530. This capture threshold may be partly constant or may also depend on the time since the recent depolarization (by means of relative refractory period A6, V6). The atrial channel is linked with the ventricular channel by means of AV conduction AV7 which includes a certain delay (AV Delay).

[0105] The heart simulator 110 of FIG. 11 thus comprises multiple heart parameters that can be adjusted, for example to generate one or more cardiac events indicative of a pathologic symptom. Such cardiac events may be defined, via the heart parameters, using a training program (that may, e.g., be stored in the heart model database 520 of FIG. 10). Additionally, or as an alternative, such cardiac events may be defined, via the heart parameters, by control information manually configured by a human trainer via an external control interface (e.g., during run-time). As understood herein, the capture threshold(s) applied by the cardiac stimulus detector 530, and thus the cardiac stimulus detector 530 itself, are logically also comprised by the heart simulator 110.

[0106] FIGS. 12 to 15 are schematic illustrations of training system set-ups according to embodiments of the present disclosure.

[0107] According to the set-up 1200 of FIG. 12, the PC 300A (see FIG. 10) or, alternatively, a workstation hosts a simulator application with the ECG generator 300 and, additionally, a control interface (implemented, e.g., as GUI) that permits a real-time training control by a trainer 600. In more detail, the control interface stretches from the PC 300A via the controller 515 to one or both of the heart simulator 110 and the heart model database 520 to allow an trainer adjustment of parameter settings or parameter configurations that control operation of the heart simulator 110 (see, e.g., the parameters discussed above in the context of FIG. 11). Moreover, the simulator application also permits an evaluation of user adjustments actually performed at the pacemaker 200. As explained above, corresponding user adjustment information may be received by the simulator application directly from the pacemaker 200 or from the apparatus 100 (see also dashed lines in FIGS. 1 and 4). In this regard, the simulator application may evaluate the optionally time stamped user adjustments received from the pacemaker 200 with one or both of the optionally time stamped (i) information on expected user adjustments and (ii) cardiac events generated by the heart simulator 110 to check if the actual user adjustments correspond to a training goal.

[0108] The PC 300A comprises a user management application that can be configured by an administrator 700 via a suitable interface. An exemplary configuration includes an update of the simulator application or of its features. The user management application is also in charge of access control in regard to both the user 500 and the trainer 600 (e.g., by checking corresponding credentials that need to be input by the user 500 and the trainer 600).

[0109] According to the set-up 1300 of FIG. 13, the PC 300A (see FIG. 10) or, alternatively, a workstation hosts a simulator application with the ECG generator 300. The user management application is hosted by a separate PC or server 300C connected to the PC 300A or workstation via the Internet or an intranet.

[0110] According to the set-up 1400 of FIG. 14, the heart simulator 110 and the pacemaker 200 are configured as software models running on the PC 300A (see FIG. 10), a tablet computer or a smartphone. This means that all the central training services are provided by a single platform.

[0111] FIG. 15 illustrates a GUI 1500 that serves as an external control interface for controlling, by the trainer 600, the heart simulator 110. The GUI 1500 as external control interface may be coupled by the controller 515 to the heart simulator 100 as described above with reference to FIG. 10.

[0112] The GUI 1500 may be generated by the simulator application illustrated in FIGS. 12 and 14. Via the GUI 1500, the trainer 600 may vary one, two or more parameters of a set of simulated heart parameters to prompt a reaction by the user 500 to be trained. Such a heart parameter set may include, but is not limited to, sinus rate, ventricular rate, AV interval, P wave amplitude, R wave amplitude, atrial capture threshold, and ventricular capture threshold. Furthermore, electrical properties of the stimulation lead systems may be altered (such as atrial lead impedance and ventricular load impedance, see also the component 510 for load impedance matching in FIGS. 5 and 10). Another embodiment (not shown) provides controls to setup “pathologic” scenarios such as, but not limited to, atrial fibrillation, AV- Block, and intentionally adverse settings the user 500 to be trained needs to address via suitable user adjustments. Another embodiment (not shown) may differentiate between “patient” scenarios to practice and play with and “patient” scenarios of evaluation and testing.

[0113] The training program or the trainer 600 may configure the heart simulator 110 to generate cardiac events that are indicative of a pathologic behavior of the simulated heart, such as conduction abnormalities or irregular heart beats. As understood herein, conduction abnormalities include all forms of AV blocks, and irregular heart beats include atrial fibrillation.

[0114] An exemplary training scenario comprises evaluating the adjustment information. The evaluation may be performed by the training program or by a separate evaluation program hosted externally to the apparatus 100 (e.g., on the PC 300A). Additionally, or in the alternative, the evaluation may be performed by the trainer 600 to whom the adjustment information is presented via a dedicated GUI (e.g., generated by the PC 300A or an another computer operated by the trainer 600).

[0115] One goal of the evaluation is to determine (e.g., in real-time or at least in a close temporal relationship to a user adjustment) whether a certain user adjustment performed at the pacemaker, possibly in response to a set of cardiac events indicative of a pathologic behavior of the heart, will therapeutically be effective. A result of this determination may be output as user training information (indicating, e.g., that the training was successful or giving the user feedback about missing adjustments or adjustments that were performed improperly).

[0116] As an example, it may be determined if the user 500 has operated a certain control button or control wheel of an external pacemaker correctly, incorrectly or erroneously not at all. As such, the adjustment information may also be indicative of an adjustment that has erroneously not been performed. The adjustment information may generally be indicative of current settings of adjustable pacemaker parameters. In such a case, (lack of) a user adjustment can be determined by a (missing) change of the pacemaker settings over a period of time (e.g., from one parameter setting data set output by the pacemaker to the next such data set).

[0117] Various training scenarios may be defined that each comprises a dedicated (lack of) generation of cardiac events to trigger an associated user adjustment. In a first training scenario, the capture threshold is to be determined by the user 500, but the adjustment information indicates that the user 500 has forgotten to adjust the stimulation rate to be higher than the intrinsic rate. In a second training scenario, the adjustment information indicates that the user 500 is further increasing the sensing threshold although the intrinsic activities are no longer detected. In a third training scenario, the adjustment information indicates that the user 500 is further decreasing the sensing threshold although in addition to intrinsic activities, noise or other signal artifacts are already detected. In a fourth training scenario, the pacemaker is to be operated in a demand mode (e.g., detect intrinsic ventricular activities), but the adjustment information indicates that the user 500 has missed to select the AV delay to be longer than the intrinsic AV interval.

[0118] In all those training scenarios, an automatic (e.g., program-based) feedback or a feedback from the trainer 600 may be given to the user 500, for example at a GUI (only) presented to the user 500. As such, user training can efficiently be performed in a largely automated way, which increases the user's ability of proper patient treatment.