Zio AT ECG Monitoring System, ZEUS System
iRhythm Technologies, Inc. • Cardiovascular • 08/29/2018
Device Purpose
The Zio AT ECG Monitoring System provides long-term, continuous ECG monitoring for adult patients to detect and report cardiac events, with its ZEUS System component utilizing an updated deep-learning algorithm for enhanced rhythm classification and analysis of single-lead ECG data. This modification aims to improve the accuracy and scope of arrhythmia detection for symptomatic and asymptomatic individuals in an ambulatory setting, facilitating clinician diagnosis.
Summary
The Zio AT ECG Monitoring System is designed for long-term cardiac monitoring in adult patients (18 years or older) who may be asymptomatic or experience transient symptoms like palpitations, dizziness, or syncope. It continuously captures, analyzes, and reports symptomatic and asymptomatic cardiac events using single-lead electrocardiogram (ECG) information. Patient-triggered and automatically-detected arrhythmia events are transmitted to a monitoring center, and a final comprehensive report, based on beat-to-beat analysis of the entire recording period, is generated for clinician review to aid in diagnosis. The system is intended for ambulatory, non-critical care patients. The key modification discussed pertains to the ZEUS System, the software component responsible for ECG analysis and reporting. This system, used by iRhythm’s Certified Cardiographic Technicians (CCTs) to generate reports, has updated its rhythm classification algorithm from a rule and machine-learning (ECGML) basis to a deep-learning (ECGDL) foundation. While the Zio AT Patch Recorder and Wireless Gateway Device components remain unchanged, the ZEUS System now integrates both ECGML and ECGDL labels. This update aims to enhance the processing and sorting of ECG data for improved rhythm detection, including an expanded list of rhythm types such as second-degree AV block type I and ectopic atrial rhythm, while maintaining its core function of enabling a complete ECG processing and analysis service.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the performance of the new deep-learning based rhythm classification algorithm in the ZEUS System compare to the previous rule and machine-learning implementation in terms of sensitivity and specificity for various arrhythmia types?; What specific architectural changes were made to the ZEUS System to accommodate the deep-learning algorithm, particularly concerning data processing and computational requirements?; Can the updated ZEUS System now identify or provide more nuanced classifications for the newly listed rhythm types (e.g., second degree AV block - type I, ectopic atrial rhythm) beyond what the original system could detect?; What were the key findings from the nonclinical verification and performance testing, specifically relating to the AAMI ANSI EC57:2012 and IEC 60601-2-47:2012 standards, that demonstrate the efficacy of the modified algorithm?; How does the integration of ECGML and ECGDL labels in the updated Result Integrator improve the accuracy or efficiency of the final report generation by Certified Cardiographic Technicians?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class C (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of SBOM, ML-BOM, SaaSBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Not detected in AI-generated device summary: HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly