physIQ Heart Rhythm and Respiratory Module
physIQ, Inc • Cardiovascular • 07/10/2019
Device Purpose
The physIQ Heart Rhythm and Respiration Module (Version 2.0) is a software library designed to analyze ambulatory single-lead ECG and triaxial accelerometer data for calculating heart rate, heart rate variability, respiration rate, and detecting atrial fibrillation in adult patients undergoing remote monitoring. Its methodology relies on a collection of Python-based algorithms processing data from compatible biosensors, with performance validated against industry standards and predicate devices to support its use in subacute clinical and non-clinical settings.
Summary
The physIQ Heart Rhythm and Respiration Module (Version 2.0) is a software-based medical device intended for use by physicians and other qualified medical professionals to analyze physiological data from adult patients in subacute clinical and non-clinical settings for remote patient monitoring. Its core functions include the calculation of heart rate and heart rate variability, the detection of atrial fibrillation, and the determination of respiration rate. The module is explicitly not designed for patients requiring life-supporting or life-sustaining systems or as a primary ECG or respiration alarm device, but rather to supplement standard care. The module operates as a callable function library developed in the Python programming language. It processes single-lead electrocardiogram (ECG) signals and triaxial accelerometer data acquired from compatible, commercially available FDA-cleared ECG biosensor devices that utilize "wet" electrode technology. Customer organizations integrate this module into their end-to-end systems, typically via middleware that retrieves sensor data, inputs it into the module for analysis by its specific algorithms (Heartbeat Detector, Heart Rate, Heart Rate Variability, Atrial Fibrillation, and Respiration Rate), and then relays the processed vital sign outputs to a downstream monitoring system for clinical use. Performance testing for heart rate, heart rate variability, and atrial fibrillation algorithms adhered to ANSI/AAMI EC572012 guidelines, while the respiration rate algorithm underwent clinical and bench testing, meeting internal acceptance criteria and showing comparable performance to a predicate device.
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 specific FDA-cleared ECG biosensor devices and "wet" electrode technologies are validated for compatibility with the physIQ Heart Rhythm and Respiration Module, and how does their variability impact algorithm performance?; Could the document provide more detailed quantitative performance data (e.g., sensitivity, specificity, accuracy) for the atrial fibrillation detection and respiration rate algorithms, especially in comparison to the predicate devices under various physiological conditions?; How does the module's triaxial accelerometer data processing specifically contribute to the accuracy of respiration rate determination, and are there mechanisms to mitigate motion artifacts?; What were the specific "internal acceptance criteria" for the respiration rate algorithm, and how do they align with established clinical standards or benchmarks for respiratory monitoring?; Given its integration via middleware, what are the technical requirements and potential challenges for customer organizations in integrating this Python library into their existing data collection and clinical display systems, particularly regarding data format compatibility and real-time processing capabilities?
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, HBOM 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: 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