RX-1 Rhythm Express Remote Cardiac Monitoring System
VivaQuant Inc. • Cardiovascular • 09/02/2020
Device Purpose
The RX-1 Rhythm Express Remote Cardiac Monitoring System is designed for continuous, ambulatory ECG recording using standard electrodes, featuring an embedded algorithm for arrhythmia detection, ECG compression, and noise removal, with automated or manual event data transmission via cellular modem to a server for physician review. This system facilitates non-real-time cardiac monitoring for patients with suspected or known cardiac conditions, providing ECG data for subsequent professional analysis without offering direct diagnostic statements or alarms.
Summary
The RX-1 Rhythm Express Remote Cardiac Monitoring System is intended for patients weighing over 10 kg who have, or are at risk of, cardiac disease, or exhibit intermittent symptoms requiring continuous cardiac monitoring. Worn by the patient for a physician-prescribed period, typically 1 day to 4 weeks, the device connects to standard ECG electrodes to continuously capture 2-channel ECGs. It can function in three modes: Mobile Cardiac Telemetry (MCT), Event Recorder (ER), and Wireless Holter (WH). An embedded algorithm processes the acquired ECG to detect arrhythmias, compress the data, and remove most in-band noise without distorting ECG morphology. Upon detection of a cardiac event by the ECG analysis algorithm, or when manually initiated by the patient, the RX-1 system automatically transmits the recorded cardiac activity to a server via an integrated cellular modem. This data is then presented for review by a medical professional. The system communicates events from the patient to the monitoring center within one to seven minutes, assuming cell service availability, and is therefore not suitable for real-time arrhythmia event monitoring. The device does not sound alarms, deliver therapy, administer drugs, provide interpretive or diagnostic statements, or offer life support. Data received from the RX-1 can be used by other devices for arrhythmia analysis, reporting, and signal measurements.
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 (e.g., sensitivity, specificity, positive predictive value) of the embedded ECG analysis algorithm for detecting various types of arrhythmias?; How does the device's noise removal algorithm distinguish between physiological ECG signals and in-band noise, and what is its impact on ECG morphology integrity?; What are the data security and privacy measures implemented for the transmission and storage of patient ECG data via the cellular modem and RS-1 Web Service?; Can the system differentiate or prioritize events based on clinical severity before transmission to the server?; What is the typical battery life of the device under continuous use in each of its operational modes (MCT, ER, WH), and how does cellular signal strength affect power consumption?
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, HBOM, OBOM 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: SBOM, CBOM, VDR/VEX. 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