Medscape Medical NewsAll articles

Biovitals Analytics Engine

Biofourmis Singapore Pte. Ltd • Cardiovascular • 08/15/2019

510(k)IEC 62304 Class C
FDA Summary PDF

Device Purpose

The Biovitals Analytics Engine is a cloud-based software system designed to continuously analyze heart rate, respiratory rate, and activity data from the VitalPatch wearable sensor, establishing a dynamically updated, individualized physiological baseline for adult patients during periods of minimal activity (activity count < 4). It employs a proprietary algorithm to compute a Biovitals Index (BI), a scalar (0-1) value displayed in 30-minute segments, that quantifies deviations from this baseline for retrospective review by clinicians as an adjunctive monitoring tool.

Summary

The Biovitals Analytics Engine (BA Engine) is a cloud-based software platform for monitoring adult patients by analyzing continuous heart rate, respiratory rate, and activity data from the compatible VitalPatch (K183078) wearable sensor. It is intended for use when patients exhibit minimal activity (activity count < 4), with the engine processing data to establish an individualized biometric signature. This baseline signature is initially formed using data from the first 24 hours (requiring 3 to 13 hours of actual processed data) and is dynamically updated, typically incorporating the last 9 to 45 hours of data that show low variability in vital sign relationships. The engine computes a Biovitals Index (BI), a scalar value (0-1) displayed in 30-minute segments if at least 10 minutes of valid minimal activity data are present in the segment. The BI quantifies deviations from the patient's dynamic baseline, with values ≤0.3 indicating little/no change, >0.3-≤0.7 moderate change, and >0.7 significant change. Intended for retrospective review by practitioners as an adjunctive tool, not for diagnosis or treatment decisions, its performance was validated in studies including one with 50 emergency department patients where BI correlated with physician-assessed changes in vital sign relationships (Positive Percent Agreement lower 95% CI bound > 0.7).

AI Regulatory Concerns

Powered byJev by TypeSafe AI

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

Keywords

Biovitals Analytics EngineBiovitals Index (BI)Remote Patient MonitoringPhysiological Data AnalysisIndividualized BaselineMachine LearningHeart RateRespiration RateActivity MonitoringCloud-Based Software

Device Metadata

Submission Number
K183282
Company
Biofourmis Singapore Pte. Ltd
Panel
Cardiovascular
Product Code
N/A
Data Type
Signals
Clinical Function
Assessment
AI Function
Analysis
AI Subclass
quantification/feature localization

Relevant Clinical Questions

  • Q1. How is "minimal activity (activity count < 4)" defined and validated to ensure robust data quality for Biovitals Index calculation when using the compatible VitalPatch sensor across diverse patient activities?; What is the typical timeframe and minimum data quantity required for the algorithm to establish a reliable, individualized biometric signature for a new patient, and how frequently is this baseline dynamically updated under various monitoring durations?; How does the algorithm differentiate between clinically significant physiological changes reflected in the Biovitals Index and benign variations or sensor-related artifacts, especially during prolonged ambulatory monitoring?; If additional FDA-cleared wearable biosensors for heart rate, respiration rate, and activity are to be integrated in the future, what would be the validation process and expected performance benchmarks to ensure compatibility with the Biovitals Analytics Engine?; Considering the Biovitals Index is an adjunctive tool, what specific guidance or thresholds are provided to clinicians for interpreting BI trends (e.g., sustained moderate BI versus acute significant BI) in conjunction with other clinical information for patient assessment?

Risk Classification

ESL Analysis
FDA Device ClassII

FDA 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.

Cyber Score50/100
SBOM Evidence⚠ Not mentioned in summary
Cyber Risk Assessment✓ Detected in Summary
Postmarket Plan✓ Detected in Summary
§524B ApplicableNo

Supply Chain BOM Evidence

Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.

SBOMSoftware Bill of Materials
- Not detected
ML-BOMMachine Learning Bill of Materials(machine learning, algorithm)
✓ Detected
SaaSBOMSoftware-as-a-Service Bill of Materials(cloud, remote, platform)
✓ Detected
HBOMHardware Bill of Materials(sensor)
✓ Detected
CBOMCryptography Bill of Materials
- Not detected
VDR/VEXVulnerability Disclosure Report / Vulnerability Exploitability eXchange
- Not detected
OBOMOperations Bill of Materials
- Not detected

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 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, 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
Biovitals Analytics Engine - Biofourmis Singapore Pte. Ltd | ESL FDA AI Device Intelligence