RhythmAnalytics
Biofourmis Singapore Pte. Ltd. • Cardiovascular • 03/07/2019
Device Purpose
RhythmAnalytics is a software system employing a web API and a proprietary algorithm to analyze single-lead ECG data from adults for cardiac irregularities, including heart rate, RR intervals, QRS complexes, and ventricular ectopic beats. Its purpose is to provide supportive analytical information for review and confirmation by qualified healthcare professionals, aiding in the assessment of cardiac arrhythmias.
Summary
RhythmAnalytics is a software application designed for the assessment of cardiac arrhythmias using single-lead electrocardiogram (ECG) data from adult patients (over 18 years old). It comprises a web application programming interface (API) allowing authenticated users to upload ECG data, and an automated proprietary algorithm that measures and analyzes this data. The system is intended for use by healthcare solution integrators to develop web or mobile applications, enabling qualified healthcare professionals to review and confirm the analytical results. RhythmAnalytics processes digital ECG files, detects cardiac beats/arrhythmias, determines heart rate, measures RR intervals and QRS complexes, identifies non-paced arrhythmias, non-paced ventricular arrhythmia calls, and ventricular ectopic beats, returning these interpretation results for professional review. The device's functionality relies on its proprietary algorithm for ECG signal processing, QRS and Ventricular Ectopic Beat detection, feature extraction, interval measurement, and rhythm analysis. It is compatible with data from various FDA-cleared devices like Holters and event recorders, and can interface with other computer-based ECG systems. Importantly, RhythmAnalytics is not intended for life-supporting systems or as a standalone diagnostic tool; its interpretations are advisory, meant to be used in conjunction with a physician's comprehensive clinical judgment. Performance testing for the software, classified as a 'major level of concern,' involved verification of design inputs, product specifications, and evaluation of sensitivity, specificity, and predictive values against a gold standard, with successful completion of software validation and usability tests according to standards like IEC 62304 and AAMI/ANSI EC57.
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 are the specific performance metrics (sensitivity, specificity, PPV, NPV) of the proprietary algorithm for various types of non-paced arrhythmias and ventricular ectopic beats when benchmarked against standard annotated ECG databases?; How does RhythmAnalytics handle ECG signal noise or artifacts, and what is its performance impact in such scenarios?; What are the integration requirements and security protocols for healthcare solution integrators wishing to utilize the RhythmAnalytics API within their web or mobile applications?; Can the system differentiate or flag ECG recordings of insufficient quality for reliable automated analysis?; What specific data from the 'gold standard' validation was used, and what was the range of arrhythmias present in this dataset?
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 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, SaaSBOM, 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