Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Interpreting Ambulatory Monitoring

ASecurity

Structures Holter and event monitor interpretation with arrhythmia burden quantification. Use when reading Holter monitors, interpreting event recorders, or quantifying arrhythmia burden.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
developmentgonode

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill interpreting-ambulatory-monitoring --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Interpreting Ambulatory Monitoring?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Interpreting Ambulatory Monitoring
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-interpreting-ambulatory-monitoring/badge)](https://www.skillsdirectory.com/skills/lev-os-interpreting-ambulatory-monitoring)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: interpreting-ambulatory-monitoring
description: Structures Holter and event monitor interpretation with arrhythmia burden quantification. Use when reading Holter monitors, interpreting event recorders, or quantifying arrhythmia burden.
tags:
  - analysis
  - cardiology
metadata:
  author: casemark
  practice_areas:
    - Cardiology
    - Interventional Cardiology
    - Electrophysiology
  document_types:
    - Interpretation Report
  skill_modes:
    - Analysis
    - Interpretation
---

# Interpreting Ambulatory Monitoring

Structures Holter and event monitor interpretation with arrhythmia burden quantification.

## Why This Skill Exists

Ambulatory cardiac monitoring — Holter monitors, event recorders, mobile cardiac telemetry (MCT), and implantable loop recorders (ILRs) — is the primary diagnostic tool for arrhythmia detection in patients with palpitations, syncope, cryptogenic stroke, and AF burden assessment. The choice of monitoring device depends on symptom frequency, and mismatching device to clinical question wastes diagnostic opportunity. The HRS Expert Consensus on Ambulatory ECG Monitoring provides guidelines for device selection, interpretation standards, and clinically significant findings.

Structured interpretation must quantify arrhythmia burden (not just identify isolated events), correlate symptoms with rhythm, assess rate control adequacy, and identify high-risk findings requiring urgent action. Generic summaries like "occasional PVCs noted" fail the clinical standard.

---

## Checkpoint A: Pre-Draft Intake (Mandatory)

1. What is the clinical indication — palpitations, syncope, presyncope, cryptogenic stroke, AF burden assessment, rate control evaluation? (default: "Indication not specified")
2. What type of monitor was used — 24-hour Holter, 48-hour Holter, 7-day patch, event recorder, MCT, or ILR? (default: "Monitor type not specified")
3. What is the total recording duration and analyzable time? (default: "Duration not documented")
4. Did the patient keep a symptom diary? (default: "No diary available")
5. Is the patient on rate- or rhythm-control medications? (default: "Medication list not provided")
6. Is there a known arrhythmia being monitored or is this a diagnostic study? (default: "Diagnostic — no known arrhythmia")
7. Is there known structural heart disease or reduced LVEF? (default: "Structural heart disease status unknown")
8. Is there a prior monitoring study for comparison? (default: "No prior study available")

### Documents to Request

- Complete ambulatory monitoring report with all pages
- Representative rhythm strips (normal sinus, abnormal events, symptom-correlated events)
- Patient symptom diary with timestamps
- Full disclosure data access (if available for independent review)
- Prior ambulatory monitoring reports for comparison
- Current medication list
- Recent ECG for baseline comparison
- Echocardiogram (structural context)
- Sleep study results if sleep-related arrhythmia suspected

---

## Step 1: Device Selection Appropriateness Assessment

**Device-to-Indication Matching (HRS Consensus):**

| Symptom Frequency | Recommended Device | Duration |
|------------------|-------------------|----------|
| Daily | 24–48 hour Holter | 1–2 days |
| Several times/week | Extended Holter or patch monitor | 7–14 days |
| Weekly to monthly | Event recorder or MCT | 30 days |
| Infrequent (< monthly) | Implantable loop recorder (ILR) | Up to 3 years |
| Cryptogenic stroke (AF detection) | ILR preferred; MCT × 30 days as alternative | ILR: 6–36 months |
| Post-ablation AF recurrence | 7-day Holter or patch at set intervals | Per protocol |

**Document:** Was the selected device appropriate for the clinical question? If monitoring duration was insufficient to capture symptoms, recommend extended monitoring.

---

## Step 2: Baseline Rhythm and Rate Analysis

**Heart Rate Summary:**
- Minimum HR with time and rhythm at minimum
- Maximum HR with time, activity, and rhythm at maximum
- Average HR over the recording period
- Heart rate variability (SDNN if reported — reduced SDNN < 50 ms associated with increased cardiac mortality)

**Baseline Rhythm Assessment:**
- Predominant rhythm: normal sinus, sinus bradycardia, sinus tachycardia, atrial fibrillation, atrial flutter, paced
- Sinus node function: appropriate rate variability, chronotropic response to activity
- AV conduction: PR interval consistency, presence of AV block episodes (first-degree, Mobitz I, Mobitz II, complete)
- Pauses: longest R-R interval, duration, mechanism (sinus pause, sinus arrest, AV block)

**Pause Significance:**
| Duration | Clinical Significance |
|----------|----------------------|
| < 2.0 s | Normal (may occur during sleep) |
| 2.0–2.9 s | Borderline; correlate with symptoms |
| ≥ 3.0 s (awake) | Significant; evaluate for sinus node dysfunction or AV block |
| ≥ 3.0 s (sleep) | May be physiologic in young, athletic patients; correlate |

---

## Step 3: Arrhythmia Event Analysis and Quantification

**Supraventricular Events:**
- Isolated PACs: count total, calculate burden (% of total beats)
- PAC burden > 10,000/day or > 10% associated with increased AF risk and cardiomyopathy
- SVT episodes: number, duration, peak rate, mechanism if identifiable (AVNRT, AVRT, AT)
- Atrial fibrillation: total burden (hours or % of recording time), longest episode, average ventricular rate during AF
- Atrial flutter: episodes, rate, duration

**AF Burden Quantification:**

| Burden | Clinical Significance |
|--------|----------------------|
| < 0.5% | Minimal; reassess anticoagulation need based on CHA2DS2-VASc |
| 0.5–5% | Low-moderate; anticoagulation per CHA2DS2-VASc |
| 5–50% | Moderate-high; consider rhythm control |
| > 50% | High burden; persistent AF pattern |

**Ventricular Events:**
- Isolated PVCs: total count, burden (% of total beats)
- PVC burden > 10–15% associated with PVC-induced cardiomyopathy
- PVC morphology: uniform (single focus) vs. multiform
- Couplets: frequency
- NSVT episodes: number, duration (beats), rate
- Sustained VT (≥ 30 seconds or hemodynamically unstable): URGENT — report immediately
- R-on-T phenomenon: flag as high risk for VF

**PVC Burden Significance:**

| Burden | Recommendation |
|--------|---------------|
| < 5% | Typically benign; reassure |
| 5–10% | Monitor; echo if symptoms or concern for cardiomyopathy |
| 10–15% | Echo for cardiomyopathy screening; consider suppressive therapy |
| > 15% | High risk for cardiomyopathy; ablation evaluation |

---

## Step 4: Symptom-Rhythm Correlation

**Correlation Categories:**
1. **Positive correlation:** Symptom occurred simultaneously with arrhythmia → arrhythmia is the cause
2. **Negative correlation:** Symptom occurred during normal sinus rhythm → arrhythmia is NOT the cause (equally important diagnostically)
3. **Non-diagnostic:** Symptoms occurred but no interpretable rhythm at that time, or no symptoms occurred during monitoring

**Document for each diary entry:**
- Timestamp of symptom
- Rhythm at that exact time
- Heart rate at that time
- Correlation conclusion

**If no symptoms occurred during monitoring:** State explicitly — "No patient-activated events during the monitoring period; study non-diagnostic for symptom-rhythm correlation. Consider extended monitoring."

---

## Step 5: Structured Report and Recommendations

**Report Template:**
1. Indication for monitoring
2. Device type and total recording duration (analyzable %)
3. Predominant rhythm
4. Heart rate summary: minimum, maximum, average
5. Supraventricular events: PAC count/burden, SVT episodes (type, rate, duration), AF burden
6. Ventricular events: PVC count/burden, morphology, couplets, NSVT, sustained VT
7. Conduction abnormalities: AV block episodes, pauses (longest, mechanism)
8. ST-segment changes (if monitored)
9. Symptom-rhythm correlation
10. Comparison with prior study
11. Conclusions and recommendations

---

## Checkpoint B: Post-Draft Alignment (Mandatory)

1. Is the arrhythmia burden quantified (not just "present" or "absent")?
2. Is symptom-rhythm correlation addressed for every diary entry?
3. Are PVC and PAC burdens calculated as percentage of total beats?
4. Are high-risk findings (sustained VT, long pauses, high AF burden) flagged?
5. Is device appropriateness assessed for the clinical question?

---

## Quality Audit

- [ ] Device type and recording duration documented
- [ ] Analyzable time percentage reported
- [ ] Predominant rhythm identified
- [ ] Heart rate summary with minimum, maximum, and average
- [ ] Supraventricular event quantification (PAC count and burden %)
- [ ] AF burden calculated as hours and/or percentage of recording
- [ ] Ventricular event quantification (PVC count and burden %)
- [ ] PVC morphology described (uniform vs. multiform)
- [ ] NSVT episodes documented with rate and duration
- [ ] Pauses documented with duration and mechanism
- [ ] Symptom-rhythm correlation addressed for every diary entry
- [ ] High-risk findings flagged with urgency level
- [ ] Comparison with prior monitoring study if available
- [ ] Recommendations include next steps (extended monitoring, echo, ablation, device)

---

## Guidelines

1. Always quantify arrhythmia burden as a percentage of total beats — qualitative terms like "frequent" or "occasional" are clinically insufficient.
2. PVC burden > 10% warrants echocardiographic screening for PVC-induced cardiomyopathy, and burden > 15% should prompt ablation evaluation.
3. AF burden assessment requires documenting total AF duration as a proportion of recording time — single-episode duration alone does not capture intermittent burden.
4. Symptom-rhythm NEGATIVE correlation (symptoms during sinus rhythm) is diagnostically valuable and should be clearly reported.
5. Pauses ≥ 3 seconds during wakefulness require clinical evaluation for sinus node dysfunction or AV block regardless of symptoms.
6. When monitoring fails to capture symptoms (non-diagnostic study), recommend the appropriate next-step device based on symptom frequency.
7. In cryptogenic stroke patients, AF detection requires at least 30 seconds of continuous AF per current guidelines to warrant anticoagulation — shorter episodes remain an area of active study.
8. Heart rate variability metrics should be reported when available, as reduced SDNN is an independent predictor of cardiac mortality in post-MI and HF patients.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

281612 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2132 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Tanstack Start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per ...

9881 votes

Pentest

PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

5491 votes
View all in development →