A monitoring report that tells you a patient had an AFib episode during their 14-day patch study is telling you something useful, but not the same thing as a report that characterizes the proportion of the total monitoring period spent in AFib. The distinction between episode detection and burden quantification is not semantic. It has direct clinical implications for anticoagulation risk stratification, ablation candidate selection, and longitudinal rhythm tracking.
What AFib Burden Means and Why It Is Measured
AFib burden is typically expressed as the percentage of total monitoring time in which the rhythm was classified as AFib. A patient with 14 days of continuous monitoring who spent 6.3 hours in AFib over that period has a burden of approximately 1.9 percent. A patient who spent 67 hours in AFib over the same period has a burden of approximately 20 percent.
These two patients may both be described as having "detected AFib" on their monitoring report. The clinical management implications are substantially different. CHA2DS2-VASc scoring for anticoagulation risk assessment relies on the presence of AFib, but the intensity of monitoring, the threshold for initiating anticoagulation in patients with subclinical AFib, and the urgency of follow-up are all influenced by burden magnitude in addition to episode presence.
The ACC/AHA guidelines and the growing literature on device-detected AFib have progressively recognized burden as a more clinically informative metric than binary presence/absence. Subclinical AFib detected on implantable devices is associated with increased stroke risk in a dose-response relationship with burden, with the relationship becoming clinically significant at thresholds that have been debated in the literature but generally cluster around 5 to 6 minutes of AFib per day as a minimum for sustained concern.
What Episode Detection Alone Tells You
An episode-detection result tells you that an AFib episode of at least a specified minimum duration occurred at some point during the monitoring window. For a screening application, that binary information may be sufficient. If the clinical question is "does this patient have any AFib?" and the answer is yes, the management pathway is defined by that binary result regardless of how long the episodes lasted.
Episode detection without burden quantification becomes limiting in several specific scenarios. A patient being evaluated for post-ablation recurrence assessment presents the most obvious example. A patient is 90 days post-pulmonary vein isolation. Their prior monitoring showed 18 percent burden. The new 14-day patch returns with detected AFib. Was the ablation partially effective (burden now 2 percent) or unsuccessful (burden 15 percent)? Episode detection alone cannot answer this question. Burden characterization can.
Similarly, for patients being managed with antiarrhythmic medications, serial monitoring to assess drug effect requires burden data. An antiarrhythmic that reduces AFib burden from 15 percent to 3 percent may represent significant clinical success even if episodes are still detected. An algorithm that only reports episode presence and count does not capture that signal.
What Your Monitoring Report Should Display
A well-structured ambulatory ECG patch report for AFib monitoring should include, at minimum: total monitoring duration, percentage of analyzable (non-artifact) recording time, total number of AFib episodes, total AFib time in hours and minutes, AFib burden as a percentage of total monitoring time, longest single AFib episode with start time, and heart rate during AFib. Reports that provide only a narrative statement ("AFib detected, multiple episodes") or only episode count without burden are providing incomplete information for clinical decision-making.
ElectroKare's alert and summary reporting is structured to surface burden metrics alongside episode data. When a priority AFib alert is generated, the alert includes the episode information (onset time, duration, maximum ventricular rate) that allows immediate clinical assessment. The monitoring summary provides burden calculation across the full recording period. For practices conducting serial monitoring for post-ablation or medication effect assessment, the burden comparison between monitoring periods is the primary data point driving management decisions.
The Limitation of Burden Calculation in Short or Artifact-Heavy Recordings
Burden as a percentage is mathematically sensitive to recording completeness. A patient who wore the patch for 8 of 14 days due to adhesive intolerance has a denominator of 192 hours rather than 336 hours. An AFib burden of 10 percent on an 8-day recording has wider confidence intervals than the same burden on a 14-day recording. A report that does not disclose the effective monitoring duration alongside the burden percentage is not interpretable.
Heavily artifact-contaminated recordings present a similar problem. If 30 percent of the recording was classified as uninterpretable due to motion artifact, the burden percentage is calculated on the 70 percent of interpretable data. Whether the contaminated segments were disproportionately AFib or non-AFib is unknowable. A transparent report should disclose the proportion of the recording that was used in the burden calculation and the proportion that was excluded due to artifact.
This is not a minor technical point. A practice making an anticoagulation decision or assessing ablation success based on a burden percentage needs to understand what denominator that percentage represents. Reports that are clear about recording completeness and artifact exclusion allow clinicians to calibrate their confidence in the burden number accordingly.
Serial Monitoring and Burden Trending
For patients with established AFib on long-term monitoring programs, the most clinically informative question is often not the current burden but how the burden has changed. A patient whose quarterly 14-day patch studies show burdens of 12 percent, 8 percent, and 4 percent is responding to an intervention, whether that is a medication titration, lifestyle change, or weight loss program. A patient whose burdens are 4 percent, 9 percent, and 14 percent over the same period has a trend that should prompt clinical reassessment regardless of whether any individual episode triggered an alert.
That longitudinal view requires that burden data be stored and comparable across monitoring periods, which in turn requires consistent methodology in how burden is calculated and reported. Practices that switch monitoring platforms between serial studies need to be cautious about comparing burden percentages across different platforms, as differences in artifact handling and minimum episode duration thresholds can produce materially different burden calculations from the same underlying rhythm behavior.
Episode detection and burden quantification are complementary, not competing, metrics. A monitoring report that provides both gives the cardiologist the information to answer the immediate clinical question (was AFib present?) and the management question (how much was present and how does that compare to before?). Both matter for running a complete cardiac monitoring program.