1. Home
  2. Features
  3. Tachy Episode Detection - ICM Feature
Indications, Safety, and Warnings

Tachy Episode Detection - ICM Feature

Tachy Episode Detection is an Insertable Cardiac Monitor (ICM) feature that detects fast heart rates. This feature is appropriate for patients experiencing, palpitations, dizziness or shortness of breath which may be symptoms associated with a fast heart rate and/or tachycardia.

This feature can be found in some Medtronic insertable cardiac monitor (ICM) devices. Please go to manuals.medtronic.com or consult with your local Medtronic representative regarding device models available in your geography.

All patient and clinical data on the screenshots in this document are fictitious and for demonstration purposes only
Print
6138

LINQ II™ ICM

  1. Tachy VT Interval (Rate): Programmable range of 270 – 520 msec, in 10 msec intervals. (Nominal is the closest value that is ≤ (230 bpm minus the Patient’s age). Patient age is based on the data entered in Patient Date of Birth
  2. Tachy VT Duration: Programmable number of beats (5,12,16,24,32,48)
  3. Tachy: Require Rapid Onset (On, Off)

Nominals are set based on the selected Reason for Monitoring.

Reason for Monitoring VT Duration VT Rate (bpm) Tachy: Require Rapid Onset FVT Intervals to Detect FVT Interval (rate)
Syncope, Cryptogenic Stroke, Palpitations, AF Management, Suspected AF, AF Ablation Monitoring, Seizures, Other 16 beats 230 - Patient Age On 30/40

260 ms (231 bpm)
Ventricular Tachycardia 16 beats 230 - Patient Age Off 30/40

260 ms (231 bpm)
 
Reveal LINQ™ ICM
  1. Tachy Interval (Rate): Programmable range of 270 – 520 msec, in 10 msec intervals. (Nominal is the closest value that is ≤ (230 bpm minus the Patient’s age). Patient age is based on the data entered in Patient Date of Birth
  2. Tachy Duration: Programmable number of beats (5,12,16,24,32,48)
Nominals are bolded.
 
Remote Programming Using the Medtronic CareLink™ network (LINQ II ONLY) 
To program Tachy Episode Detection remotely in LINQ II, go to Patient Details >Device Settings-> Tachy… Detection, which is nominally On.
 
 
Programming with the Reveal LINQ™ Mobile Manager (LMM) App 
To program Tachy Episode Detection in LINQ II and Reveal LINQ, go to Device & Patient Settings-> Tachy Detection, which is nominally On.

Programming with the CareLink  2090 Programmer
To program Tachy Episode Detection in Reveal LINQ and Reveal DX/XT, go to Params → Tachy Detection, which is nominally On.

The automatic detection and ECG storage of Tachy episodes is turned on when Device Data Collection is activated. 

Reveal™ DX/XT, Reveal LINQ, & LINQ II
 
The automatic detection and ECG storage of Tachy episodes is turned on when Device Data Collection is activated. The Tachy Detection Interval is programmed automatically to 230bpm minus the patient’s age and rounded to the nearest programmable value. This value is calculated from the information entered in Patient Date of Birth found in Patient Details, and for all Reasons for Monitoring located in Device Data Collection. For example, if the patient is 54 years of age, the Tachy Detect Interval would be calculated as 230bpm – 54 = 176bpm (340ms).

An automatically detected Tachy episode starts when: 
  1. The ventricular intervals are occurring at shorter intervals or a faster rate than the programmed Tachy interval or rate.
    AND
  2. The number of Tachy sensed events is greater than the programmed Tachy Duration and the ECG noise level is not excessive, a Tachy episode is marked and stored.

In addition, very fast rates will cause a Tachy episode to be stored when 30 of the last 40 ventricular events have an interval < 260 ms. These episodes are marked as Tachy. This is non-programmable in Reveal LINQ. If the noise level is excessive, as indicated by the presence of very short ventricular intervals and high frequency content in the ECG, the ventricular tachyarrhythmia is rejected.

Tachy Detection Noise Algorithm
Reveal LINQ uses a noise rejection algorithm to reduce the incidence of short or non-physiologic signals contributing to the detection of a tachy episode. When Tachy detection criteria is met, and at least one of the last 12 non-noisy R-R intervals is less than 220 ms, the device will "look back" and count the number of signal inflections in the 781 ms window preceding the Tachy Detection. If the number of inflections is > 20, a Tachy episode is not detected and the Tachy counter is reset.

Tachy Detection Noise Algorithm Example

Overrange interaction

If a noise interval occurs during the detection of a Tachy episode, the following occurs:

  • If the VT event counter is 0 and the FVT event counter is > than 0, then the FVT event counter is decremented by 1.
  • If the VT event counter is > 0, then this counter is decremented by 1 and the FVT event counter remains unchanged.
  • If both VT and FVT counters are 0, then both counters remain unchanged.

The Tachy episode ends when one of the following criteria is met:

  • Eight consecutive R-waves are detected with an interval ≥ the programmed Tachy interval.
  • The median ventricular interval is ≥ the programmed Tachy interval during a period of 20 seconds.
  • No R-wave is detected during a period of 10 seconds.

If Tachy detection is programmed Off, the device stops detection and recording of the episode is terminated.

LINQ II
 
In LINQ II™ a feature exits that allows for additional discrimination between tachy episodes with rapid vs gradual onset. The feature is called “Tachy:Require Rapid Onset”. 
 
 
When enabled, a rolling window of 8 sensed events will be analyzed. When the average of the most recent 4 beats (current average) is greater [slower] than the average of the first 4 beats (Prior Average) times 81%, the rhythm is considered to be gradual. In this case the sensed events would be marked with VS and not TS. If the current average is less [faster] than the prior average*81%, the rhythm is defined as rapid onset.
 
 
Programming considerations:
  1. Reveal LINQ allows for programming of one tachy detection zone but the device further separates VT from FVT based on non-programmable detection criteria stated above.
  2. The Noise Rejection Algorithm and Overrange Interaction work behind the scene in the device and are not programmable.
  3. No morphology algorithm (Wavelet) is used.
  4. Since there is no therapy delivery, there is no possibility of redetection, high-rate time-out, or other therapy-related interactions with detection.
  5. Select the length of the blanking period that is started after the detection of a sensed R-wave. During the blanking period, sensing is inhibited to prevent the multiple sensing of the R-wave due to a broad QRS complex. If the blanking period is programmed too long, tachy events may be blanked.
  6. A Tachy episode CareAlert™ notification may be enabled monitoring Reveal LINQ™ and LINQ II™ ICM patients remotely.
  • Reveal LINQ

The Reveal LINQ ICM sends a daily wireless audit transmission to the patient's MyCareLink™ monitor. When a Tachy episode is detected and transmitted to CareLink and the CareAlert notification for a Tachy episode is enabled on the CareLink® website, a CareAlert Notification will be generated. If the Tachy episode is the highest priority event of the day per the Wireless Data Priority setting, the Tachy event details will be sent to CareLink network in the daily wireless audit and displayed on the Event Report. The episode details include 30 seconds of the detected event's ECG. The clinician receives the CareAlert notification based on clinic defined methods.

  • LINQ II

The LINQ II ICM sends data to the patient's monitor (MyCareLink Relay™ or MyCareLink Heart™ mobile app) throughout the day. When a Tachy episode is detected and transmitted to CareLink and the CareAlert notification for a Tachy episode is enabled on the CareLink® website, a CareAlert Notification will be generated. CareAlerts are processed between 5-6am based on the local clinic time zone. The clinician receives the CareAlert notification based on clinic defined methods.

Viewing Episodes

Stored episodes can be viewed remotely on the CareLink™ network by navigating to the Episodes tab under Transmission Details.  For in-person follow-up stored episodes can be viewed using the 2090 Programmer (Reveal DX/XT and Reveal LINQ only) and LINQ Mobile Manager (LMM) by opening Episodes and selecting from the Arrhythmia Episodes log.
 
Reveal DX/XT, Reveal LINQ 
Up to 27 Tachy episodes with ECG will be stored when Tachy detection is programmed "On". For each Tachy episode, the ECG recording consists of 30 seconds of ECG prior to detection and up to 27 seconds of ECG before the episode ends. When memory is full, data from the most recent Tachy episode may overwrite the oldest stored Tachy or the oldest auto detected episode data. In addition to the episodes available with ECG up to 30 logs of VT and 30 logs of FVT will be stored. 
 
LINQ II
Up to 6 Tachy episodes, 3 VT and 3 FVT, with ECG and up to 7 additional episodes for each type without ECG (log only) will be stored per day when Tachy detection is programmed "On". The 3 episodes for each type will be as follows: The first 2 and the longest episode of the day (24hour day beginning at 12am). For each Tachy episode, the ECG recording consists of 30 seconds of ECG prior to detection and up to 27 seconds of ECG before the episode ends. When memory is full, data from the most recent Tachy episode may overwrite the oldest stored Tachy or the oldest auto detected episode data. In addition to the daily episode storage up to Tachy 30 logs for each type could be stored. 
 
The log includes the following summary information:
  • Type of episode – this will say "Tachy" for a Tachy event.
  • The date, time, and duration of the episode.
  • The highest ventricular rate (automatically detected episodes only).
  • The median ventricular rate at detection (automatically detected episodes only).
  • Whether ECG data is available for the episode.

For a particular episode, you can display the following information:

  • An interval (or rate) plot
  • A strip chart of the stored ECG (if available)
  • A text summary

Marker Channel Annotation for Tachy Episodes

Note: If the patient uses the Patient Assistant while an automatically detected episode is in progress, both episodes are stored. The device records "Symptom (Patient Activated) occurred during episode" in the text of the automatically detected episode.

The example below demonstrates an Event Report derived from a CareAlert Notification of a Symptomatic Tachy episode. The Tachy episode was automatically collected when the patient's heart rate increased above the programmed Tachy detect rate for the programmed duration of beats. Approximately 80 seconds after the rate increase occurred, the patient used their patient assistant to mark the event as symptomatic. The ECG from the Tachy event and the interval (rate) plot from the symptom event were transmitted wirelessly to the patient’s home monitor that night at the programmed wireless time. A CareAlert Notification was generated once the data was received by the CareLink network. The report shows 20 seconds of ECG at the time of Tachy episode detection and 10 seconds of ECG at the time of episode termination. The episode lasted nearly 2 minutes.

References

Sources: Medtronic Reveal LINQ™ LNQ11 Clinician Manual. Medtronic LINQ II™ LNQ22 Clinician Manual. TruRhythm™ Detection Algorithms. Medtronic data on file. 2017

Last updated: 
28 Oct 2020