AliveCor QT Service
AliveCor, Inc. • Cardiovascular • 04/26/2022
Device Purpose
The AliveCor QT Service is a cloud-based software utilizing deep neural networks to analyze previously recorded 6-lead ECGs from adult patients with normal sinus rhythm, providing QT and QTc interval measurements for healthcare professionals. Its methodology involves sophisticated algorithms trained and validated on diverse datasets to ensure accurate cardiac interval assessment based on Bazett's and Fridericia's correction formulas.
Summary
The AliveCor QT Service is a cloud-based software as a medical device (SaMD) designed for use by qualified healthcare professionals in medical facilities. Its purpose is to measure the QT interval and heart rate corrected QT (QTc) intervals from 30-second electrocardiograms (ECGs) previously recorded from adult patients (older than 22 years) using AliveCor 6-lead ambulatory ECG devices. A prerequisite for analysis is that the ECG must have been classified as Normal Sinus Rhythm by KardiaAI. The service, accessed via a REST-based API, provides QT interval measurements and QTc values using both Bazett's and Fridericia's formulas. The technology relies on internal algorithms, including deep neural networks (DNNs), to analyze ECGs and compute the QT and RR intervals. These algorithms were developed using extensive datasets: training involved over 25,000 ECGs from more than 600 patients, and validation was performed on two distinct datasets, one with over 2,000 ECGs and another with approximately 100 ECGs, ensuring representation of diverse patient demographics. Non-clinical bench performance testing aimed to verify that the estimated QT and QTc intervals achieve a mean interval difference of ≤ 5 ms and a standard deviation of interval difference of ≤ 15 ms when compared to expert-annotated reference intervals from 12-lead ECGs. The results of this testing confirmed that the device performs according to its specifications.
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. What is the specific performance of the deep neural network in identifying T-wave offset across various morphologies, especially in borderline cases or when U-waves are present?; How does the algorithm's accuracy for QT/QTc measurement vary with different heart rates within the normal sinus rhythm classification, particularly at the extremes of this range?; What are the detailed demographic breakdowns (age, sex, ethnicity, comorbidities) of the >600 patients in the training dataset and the >2000 ECGs in the primary validation dataset, and how do these reflect the intended patient population?; Beyond Bazett's and Fridericia's formulas, were other QTc correction formulas considered or tested, and what was the rationale for selecting these two specific formulas?; What are the system's error handling mechanisms and reported failure rates when encountering ECGs that, despite initial classification as Normal Sinus Rhythm, contain significant noise or artifact that could impede accurate QT measurement?
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 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.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, 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