Retrospective ambulatory ECG recordings from adult patients; FDA-cleared wearable ECG patch recorder data
Retrospective clinical data from wearable ECG patches were used to validate the algorithm's performance (beat detection, rhythm classification, and noise robustness) for the new single-lead, single-channel configuration and extended monitoring durations.
ZBPro Diagnostic v2.0 is a cloud-based medical device intended for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in ambulatory ECG data in the adult population. The product supports downloading and retrospectively analyzing single-lead ambulatory ECG data up to 14 days in duration, recorded with compatible 3-lead and 5-lead Holter and single-lead wearable ECG patch configurations that use wet gel electrodes. The device analyzes Lead II, CM5 (Ch 1), Modified-MLII (Ch 2+), or MLII (single lead) but does not perform multi-lead analysis. ZBPro is not intended for use with paced signals or recordings taken from pediatric patients. ZBPro Diagnostic v2.0 can also be electronically interfaced and perform analysis with data transferred from other computer-based ECG systems, such as an ECG management system. ZBPro Diagnostic v2.0 provides ECG signal processing and analysis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, R-R interval measurement, heart rate measurement, and rhythm analysis. ZBPro Diagnostic v2.0 is not for use in life-supporting or sustaining systems or ECG monitor and Alarm devices. The product can be integrated into computerized ECG monitoring devices. In this case, the medical device manufacturer will identify the indication for use depending on the application of their device. ZBPro Diagnostic interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians and clinicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information.
Device Story
Cloud-based SaMD for retrospective analysis of ambulatory ECG data; inputs include single-lead ECG recordings (Holter or wearable patch) via web browser/API; backend hosted on AWS; performs automated signal processing, QRS detection, ventricular ectopic beat detection, R-R interval/heart rate measurement, and rhythm analysis; output provided via web interface for clinician review; intended for use by qualified healthcare professionals as advisory support for diagnosis; does not perform real-time monitoring or life-support functions.
Clinical Evidence
Bench testing only. Performance validated against adjudicated databases per ANSI/AAMI EC57 and IEC 60601-2-47. Regression testing confirmed identical performance to v1.0 for beat/rhythm detection. Patch-specific validation used adjudicated data from adult, non-paced patients (3-14 days duration) across two wearable patch models. Noise robustness evaluated at four signal-to-noise levels. No clinical data required.
Technological Characteristics
Cloud-based SaMD; AWS-hosted backend; web-based UI. Analyzes single-lead ECG (Lead II, CM5, Modified-MLII, MLII). Compatible with 3/5-lead Holter and single-lead wearable patches using wet gel electrodes. Standards: AAMI ANSI IEC 62304, IEC 62366-1, AAMI ANSI EC57, AAMI ANSI IEC 60601-2-47.
Indications for Use
Indicated for detection and analysis of common cardiac arrhythmias in retrospective ambulatory ECG data in adult patients (22+ years). Contraindicated for paced signals and pediatric patients.
Regulatory Classification
Identification
A medical magnetic tape recorder is a device used to record and play back signals from, for example, physiological amplifiers, signal conditioners, or computers.
{0}
**U.S. FOOD & DRUG**
ADMINISTRATION
September 11, 2026
Zbeats, Inc.
% Christopher Ford
Consultant
Zaliance Medical Solutions, LLC
5153 W. Wooley Rd.
Oxnard, California 93035
Re: K261580
Trade/Device Name: ZBPro Diagnostic (Version 2.0)
Regulation Number: 21 CFR 870.2800
Regulation Name: Medical Magnetic Tape Recorder
Regulatory Class: Class II
Product Code: MLO
Dated: August 19, 2026
Received: August 19, 2026
Dear Christopher Ford:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device"
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K261580 - Christopher Ford
Page 2
(https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
{2}
K261580 - Christopher Ford
Page 3
Sincerely,
JENNIFER W. SHIH -S
Jennifer Kozen
Assistant Director
Division of Cardiac Electrophysiology,
Diagnostics, and Monitoring Devices
Office of Cardiovascular Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K261580/S001 | ? |
| Please provide the device trade name(s). | | ? |
| ZBPro Diagnostic (Version 2.0) | | |
| Please provide your Indications for Use below. | | ? |
| ZBPro Diagnostic v2.0 is a cloud-based medical device intended for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in ambulatory ECG data in the adult population.The product supports downloading and retrospectively analyzing single-lead ambulatory ECG data up to 14 days in duration, recorded with compatible 3-lead and 5-lead Holter and single-lead wearable ECG patch configurations that use wet gel electrodes. The device analyzes Lead II, CM5 (Ch 1), Modified-MLII (Ch 2+), or MLII (single lead) but does not perform multi-lead analysis.ZBPro is not intended for use with paced signals or recordings taken from pediatric patients.ZBPro Diagnostic v2.0 can also be electronically interfaced and perform analysis with data transferred from other computer-based ECG systems, such as an ECG management system.ZBPro Diagnostic v2.0 provides ECG signal processing and analysis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, R-R interval measurement, heart rate measurement, and rhythm analysis.ZBPro Diagnostic v2.0 is not for use in life-supporting or sustaining systems or ECG monitor and Alarm devices.The product can be integrated into computerized ECG monitoring devices. In this case, the medical device manufacturer will identify the indication for use depending on the application of their device.ZBPro Diagnostic interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians and clinicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information. | | |
| Please select the types of uses (select one or both, as applicable). | Prescription Use (21 CFR 801 Subpart D)Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
| Please select the age group(s) for which the device(s) is to be used. | Neonates/Newborns (Birth to < 29 days old)Infants (29 days old to < 2 years old)Children (2 years old to < 12 years old)Adolescents (12 years old to < 22 years old)Adults (22 years old and greater) | ? |
{4}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
# SECTION 5 : 510(K) Summary
## 5.1 Applicant/Submitter
| Company Name | : ZBeats, Inc |
| --- | --- |
| Street Address | : 25 Health Sciences Drive |
| City | : Stony Brook NY |
| State | : NY |
| Zip Code | : 11790 |
| Phone Number | : (631) 220-2463 |
## 5.2 Contact Person
| Full Name | : Bin Fang |
| --- | --- |
| Phone | : (631) 220-2463 |
## 5.3 Correspondent Information
| Full Name | : Christopher Ford |
| --- | --- |
| Phone | : (916) 612-9954 |
## 5.4 Date of Preparation
Date of Preparation : 05/11/2026
## 5.5 Device Information
| Device Name | ZBPro Diagnostic v2.0 |
| --- | --- |
| Model Number | |
K261580
Page 1 of 7
{5}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
| Common Name | ECG Analysis System |
| --- | --- |
| Regulation | 21 CFR 870.2800 |
| Product Code | MLO |
| Reviewing Panel/Branch | Cardiovascular |
| Submission Number | K261580 |
### 5.6 Predicate Device(s)
Table - 5.1 Predicate Device(s)
| Predicate Type | 510(k) Number | Device Name | Manufacturer | Product Code |
| --- | --- | --- | --- | --- |
| Primary | K243252 | ZBPro Diagnostic (v1.0) | ZBeats, Inc. | DPS, DQK |
### 5.7 Indications for Use
ZBPro Diagnostic v2.0 is a cloud-based medical device intended for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in ambulatory ECG data in the adult population.
The product supports downloading and retrospectively analyzing single-lead ambulatory ECG data up to 14 days in duration, recorded with compatible 3-lead and 5-lead Holter and single-lead wearable ECG patch configurations that use wet gel electrodes. The device analyzes Lead II, CM5 (Ch 1), Modified-MLII (Ch 2+), or MLII (single lead) but does not perform multi-lead analysis.
ZBPro is not intended for use with paced signals or recordings taken from pediatric patients.
ZBPro Diagnostic v2.0 can also be electronically interfaced and perform analysis with data transferred from other computer-based ECG systems, such as an ECG management system.
ZBPro Diagnostic v2.0 provides ECG signal processing and analysis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, R-R interval measurement, heart rate measurement, and rhythm analysis.
ZBPro Diagnostic v2.0 is not for use in life-supporting or sustaining systems or ECG monitor and Alarm devices.
The product can be integrated into computerized ECG monitoring devices. In this case, the medical device manufacturer will identify the indication for use depending on the application of their device.
ZBPro Diagnostic interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians and clinicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information.
### 5.8 Device Description
ZBPro is cloud-based Software as a Medical Device which aids healthcare professionals in interpreting ambulatory ECG recordings. The software comprises a secure web interface and a backend server hosted on Amazon Web Server (AWS). Authenticated users upload compatible ambulatory ECG recordings via a web browser through an Application Programming Interface (API). ZBPro's proprietary ECG interpretation algorithm analyzes and annotates ECGs to provide supportive information for ECG and arrhythmia analysis.
ZBPro provides beat-by-beat ECG signal processing and analysis, QRS detection, Ventricular Ectopic Beat detection, R-R interval measurement, heart rate and Heart Rate Variability measurement, and rhythm analysis.
K261580
Page 2 of 7
{6}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
ZBPro consists of:
1. A web interface which provides tools to upload data, measure, analyze and review numerous ECGs and patient diary logs, make manual annotation and generate ECG reports.
2. An automated proprietary ECG interpretation algorithm which measures and analyzes ECGs to provide adjunct information for ECG diagnosis.
The backend application is established in Amazon Web Services (AWS) and accessed through an Internet connection and a web browser to perform ECG analysis and generate reports.
## 5.9 Intended Use/Indications for Use Comparison
ZBPro Diagnostic v2.0 (K261580) and ZBPro Diagnostic (K243252) are both cloud-based ECG analysis platforms intended for retrospective review of ambulatory electrocardiogram (ECG) recordings to assist qualified healthcare professionals in detecting and analyzing cardiac arrhythmias. Both systems support integration with external ECG acquisition devices and provide core analytical functions including QRS detection, rhythm classification, ectopic beat detection, and heart rate trend analysis.
Both devices are intended for use by qualified healthcare professionals to detect and analyze common cardiac arrhythmias using retrospective ambulatory ECG data. The primary indication (arrhythmia assessment in ambulatory ECG recordings in adult patients) is identical in both devices, and both utilize well-established principles of signal processing, QRS detection, rhythm classification, and clinical data presentation.
Both devices support electronic interfacing with other ECG systems and offer nearly identical functional capabilities, including ECG signal processing, ventricular ectopy detection, interval and heart rate analysis, and comprehensive rhythm interpretation. Neither system is intended for use in life-sustaining applications or real-time monitoring, and both clearly state that their results are to be used in conjunction with clinician oversight, not as a standalone diagnostic decision-maker.
ZBPro Diagnostic v2.0 is substantially equivalent to its predecessor, ZBPro Diagnostic v1.0 (the predicate). The primary difference relates to recording source compatibility. ZBPro Diagnostic v1.0 compatibility is limited to 3-lead and 5-lead 24/48-hour Holter configurations, whereas ZBPro Diagnostic v2.0 includes a single-lead, single-channel ECG patch configuration and up to 14-day analysis duration. These differences reflect scope of validation rather than underlying technological capabilities and do not impact substantial equivalence.
Therefore, these distinctions do not impact the substantial equivalence of the two systems in their shared core function to provide automated ECG interpretation support for adult ambulatory ECG monitoring data.
## 5.10 Comparison of Technological Characteristics with Predicate
The subject device has the same intended use and substantially equivalent technological characteristics as compared to the predicate device that do not raise questions of safety or effectiveness. Table - 5.2 Feature Comparison: ZBPro Diagnostic to the predicate device illustrates a comparison of detection features between ZBPro Diagnostic and the cited predicate.
Table - 5.2 Feature Comparison: ZBPro Diagnostic to the predicate device
| Feature | ZBPro Diagnostic v2.0 | ZBPro Diagnostic K243252 |
| --- | --- | --- |
| Heart rate determination for non-paced adult | Yes | Yes |
| QRS Detection | Yes | Yes |
| Non-paced arrhythmia interpretation for adult patients | Yes | Yes |
| Non-paced ventricular arrhythmia calls | Yes | Yes |
| R-R Intervals measurements | Yes | Yes |
| Ventricular ectopic beat detection | Yes | Yes |
K261580
Page 3 of 7
{7}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
| Patient Population | Adult | Adult |
| --- | --- | --- |
Table - 5.3 Comparison of technological characteristics: ZBPro Diagnostic to the predicate device provides a comparison of the technological characteristics of the ZBPro Diagnostic with the cited predicate.
Table - 5.3 Comparison of technological characteristics: ZBPro Diagnostic to the predicate device
| | ZBPro Diagnostic v2.0 | ZBPro Diagnostic (v1.0) | Comparison to predicate device |
| --- | --- | --- | --- |
| Device Trade Name | ZBPro Diagnostic | ZBPro Diagnostic | N/A |
| Manufacturer | ZBeats, Inc. | ZBeats, Inc. | N/A |
| 510(K) No. | K261580 | K243252 | N/A |
| Regulation Number | 21 CFR 870.2800 | 21 CFR 870.2340 21 CFR 870.1425 | Same |
| Product Code | MLO | DQK, DPS | Same |
| Class | 2 | 2 | Same |
| Device Class/Name | Electrocardiograph, ambulatory, with analysis algorithm | Electrocardiograph | Same |
| Indications for Use | ZBPro Diagnostic v2.0 is a cloud-based medical device intended for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in ambulatory ECG data in the adult population. The product supports downloading and retrospectively analyzing single-lead ambulatory ECG data up to 14 days in duration, recorded with compatible 3-lead and 5-lead Holter and single-lead/single-channel wearable ECG patch configurations using wet gel electrodes. The device analyzes Lead II, CM5 (Ch 1), Modified-MLII (Ch 2+), or MLII (single lead) but does not perform multi-lead analysis. ZBPro is not intended for use with paced signals or recordings taken from pediatric patients. ZBPro Diagnostic v2.0 can also be electronically interfaced and perform analysis with data transferred from other computer-based ECG systems, such as an ECG management system. ZBPro Diagnostic v2.0 provides ECG signal processing and analysis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, R-R interval measurement, heart rate measurement, and rhythm analysis. | ZBPro Diagnostic is a cloud-based medical device intended for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in Holter ECG data in the adult, non-paced population. The product supports downloading and analyzing Lead II, CM5 (Ch 1), or Modified-MLII (Ch 2+) on retrospective 3-lead and 5-lead 24/48-hour Holter ECG recordings collected using standard Ag/AgCl wet electrodes in adult, non-paced patients. ZBPro is not intended for use with multi-lead analysis, wearable patches, or pediatric/paced recordings. ZBPro Diagnostic can also be electronically interfaced and perform analysis with data transferred from other computer-based ECG systems, such as an ECG management system. ZBPro Diagnostic provides ECG signal processing and analysis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, R-R interval measurement, heart rate measurement, and rhythm analysis. ZBPro Diagnostic is not for use in life-supporting or sustaining systems or ECG monitor and Alarm devices. The product can be integrated into computerized ECG monitoring | Both devices have the same intended use as cloud-based medical devices for use by qualified healthcare professionals in the detection and analysis of common cardiac arrhythmias in retrospective ambulatory ECG data in the adult, non-paced population. ZBPro Diagnostic v1.0 is limited to retrospective analysis of 24–48 hour Holter ECG recordings using 3-lead and 5-lead configurations. ZBPro Diagnostic v2.0 expands this capability to include single-lead, single-channel wearable ECG patch recordings and extended monitoring durations of up to 14 days. Both devices analyze a single ECG vector (Lead II or Lead II-equivalent configurations) and do not perform multi-lead analysis. Both devices exclude paced and pediatric populations and are not intended for real-time monitoring or life-supporting applications. These differences represent an expansion of supported input configurations and recording durations and do not alter the intended use or fundamental analytical function of the device. Therefore, these differences do not impact substantial equivalence. |
K261580
Page 4 of 7
{8}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
| | ZBPro Diagnostic v2.0 (this submission) | ZBPro Diagnostic (v1.0) | Comparison to predicate device |
| --- | --- | --- | --- |
| | ZBPro Diagnostic v2.0 is not for use in life-supporting or sustaining systems or ECG monitor and Alarm devices. The product can be integrated into computerized ECG monitoring devices. In this case, the medical device manufacturer will identify the indication for use depending on the application of their device. ZBPro Diagnostic interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians and clinicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information. | devices. In this case, the medical device manufacturer will identify the indication for use depending on the application of their device. ZBPro Diagnostic interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians and clinicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information. | |
| **Fundamental scientific technology** | ZBPro v2.0 consists of: A web interface which provides tools to upload data, measure, analyze and review numerous ECGs and patient diary logs, make manual annotation and generate ECG reports. An automated proprietary ECG interpretation algorithm which measures and analyzes ECGs to provide adjunct information for ECG diagnosis. The backend application is established in Amazon Web Services (AWS) and accessed through an Internet connection and a web browser to perform ECG analysis and generate reports. | ZBPro consists of: A web interface which provides tools to upload data, measure, analyze and review numerous ECGs and patient diary logs, make manual annotation and generate ECG reports. An automated proprietary ECG interpretation algorithm which measures and analyzes ECGs to provide adjunct information for ECG diagnosis. The backend application is established in Amazon Web Services (AWS) and accessed through an Internet connection and a web browser to perform ECG analysis and generate reports. | Same. |
ZBPro Diagnostic v2.0 and ZBPro Diagnostic v1.0 are based on the same fundamental scientific technology, software architecture, and analytical methodology. Both versions consist of a cloud-based Software as a Medical Device (SaMD) platform that includes a web-based user interface, a backend processing environment hosted on Amazon Web Services (AWS), and a proprietary ECG interpretation algorithm designed for retrospective analysis of ambulatory ECG recordings.
K261580
Page 5 of 7
{9}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
Both versions utilize the same core signal processing techniques, including QRS detection, ventricular ectopic beat detection, R-R interval measurement, heart rate calculation, and rhythm classification based on a single-channel ECG input. The algorithmic framework, rule-based logic, and clinical interpretation approach remain unchanged between versions.
The primary differences between ZBPro Diagnostic v2.0 and v1.0 relate to expanded input compatibility and validated use conditions. ZBPro Diagnostic v1.0 was limited to retrospective analysis of 24–48 hour Holter ECG recordings using 3-lead and 5-lead configurations. ZBPro Diagnostic v2.0 extends this capability to include:
- Single-lead, single-channel wearable ECG patch recordings
- Extended monitoring durations of up to 14 days
- Additional validated Lead II-equivalent input configurations
These modifications represent an expansion of validated input sources and use conditions rather than a change in the underlying technology or algorithmic function. ZBPro Diagnostic continues to analyze a single ECG channel using the same detection and classification methods as the predicate device.
The software architecture, user interface, data processing workflows, and reporting capabilities remain substantially unchanged. Any differences in system performance are attributable to the broader range of validated input configurations and have been addressed through additional performance validation and cross-device equivalence testing.
All identified differences between ZBPro Diagnostic v2.0 and v1.0 have been evaluated through design controls, risk management, and verification and validation activities. These differences do not impact substantial equivalence.
Therefore, ZBPro Diagnostic v2.0 is substantially equivalent to ZBPro Diagnostic v1.0 with respect to its technological characteristics.
### 5.11 Summary of Performance Data
Performance tests have been performed in compliance with the following recognized consensus standards:
- AAMI ANSI IEC 62304 2006 - Medical device software - Software life-cycle processes
- IEC 62366-1 Edition 1.0 2015-02 - Medical devices - Application of usability engineering to medical devices.
- AAMI ANSI EC57:2012 - Testing and Reporting Performance Results of Cardiac Rhythm And ST-Segment Measurement Algorithms
- AAMI ANSI IEC60601-2-47:2012 - Medical Electrical Equipment - Part 2-47: Particular Requirements For The Basic Safety And Essential Performance Of Ambulatory Electrocardiographic Systems
### 5.12 Software verification and validation
Testing described in this 510(k) consisted of verification of all design input requirements and product specifications. All clinical input requirements were validated against a gold standard. No residual anomalies were observed during verification and software validation testing. Certified cardiovascular technicians performed general usability tests to assess users' ability to import, display, store, analyze, distribute, and manage ECG data, and they met all requirements in ZBPro Diagnostic v1.0. All software validation testing was completed successfully and met all requirements.
ZBPro Diagnostic v2.0 uses the same user interface as ZBPro Diagnostic v1.0; therefore, additional user interface validation was not required. ZBPro v1.0 was tested throughout development, validating the effectiveness of risk control measures associated with the user interface. ZBeats conducted usability testing of the ZBPro user interface with Certified Cardiovascular Technicians to evaluate the effectiveness of the design, labeling, and associated risk controls. These evaluations addressed the testable technical requirements defined in the User Interface Specification.
Performance validation testing included comprehensive rhythm classification analyses on an adjudicated database in accordance with ANSI/AAMI EC57 and IEC 60601-2-47 reporting conventions, as detailed in the ZBPro Diagnostic v2.0 Performance Validation Report.
K261580
Page 6 of 7
{10}
ZBeats, Inc.
ZBPro Diagnostic
Traditional 510(K) Submission
To support adding compatibility with ML II configuration recordings obtained from wearable ECG patch devices, ZBeats performed algorithm regression testing, patch-specific performance validation, controlled noise-stress testing, and device and ECG input-configuration equivalence testing.
Regression testing repeated the applicable ZBPro Diagnostic v1.0 performance tests using public reference databases, methods, exclusions, label mappings, and performance metrics. All 42 applicable tests passed, and ZBPro Diagnostic v2.0 produced results identical to the v1.0 baseline for beat detection, rhythm classification, atrial fibrillation/flutter detection, heart-rate measurement, heart-rate variability, and shutdown/failure detection.
Patch-specific performance validation was conducted using adjudicated ECG data from adult, non-paced patient samples collected with two FDA-cleared wearable ECG patch recorder models in the 1L/1C, ML II configuration. The source recordings represented monitoring durations of 3 to 14 days. Testing evaluated beat detection, ventricular beat classification, heart-rate and RR-interval accuracy, supported rhythm classification, and handling of unclassified rhythms. Noise robustness was additionally evaluated using noise-stressed ECG samples derived from adjudicated patch recordings and tested at four prescribed signal-to-noise levels.
Device and ECG input-configuration equivalence testing compared performance of the added 1L/1C patch configuration with the previously validated 3L/1C, 3L/3C, and 5L/2C Holter configurations. Performance was evaluated at the configuration, source-device, and overall population levels. No unresolved finding demonstrated a clinically meaningful device-specific or configuration-specific performance limitation, and the expanded v2.0 validation population remained consistent with the previously established v1.0 performance basis. The testing therefore supports use of ZBPro Diagnostic v2.0 with the added ML II-equivalent wearable ECG patch configuration.
### 5.13 Conclusion
Based upon the Intended Use, Indications for Use, product technical information, performance evaluation, and standards compliance provided in this premarket notification, ZBPro Diagnostic v2.0 has been shown to be substantially equivalent to the cited predicate.
K261580
Page 7 of 7
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Guidance alerts
New and changed FDA guidance documents, emailed as a daily digest.
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the ? button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only Software as a Medical Device, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (Software as a Medical Device), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.