K122632 · Cardiocomm Solutions, Inc. · DPS · Feb 11, 2014 · Cardiovascular
Device Facts
Record ID
K122632
Device Name
GUAVA II
Applicant
Cardiocomm Solutions, Inc.
Product Code
DPS · Cardiovascular
Decision Date
Feb 11, 2014
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2340
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
Guava II is intended to be used by cardiologists, general practitioners, cardiac or ECG technicians, nurses, monitoring service technicians, and other cardiac related institutions or care givers to store, retrieve, communicate and report ECG and ECG data acquired from a variety of ECG sources including single and multilead ECG devices. Guava II is intended to be electronically interfaced, and perform analysis with data transferred from other computer based ECG systems. Guava II includes an algorithm that will analyze the 12 Lead ECG and produce measurements of the ECG recording as well as textual interpretation. The product also includes an automatic analysis and interpretation software library that provides ECG signal processing and analysis on a beat by beat basis. QRS and Ventricular Ectopic Beat detection, QRS feature extraction, interval measurement, heart rate measurement, and rhythm analysis for up to twelve (12) leads of historic ambulatory ECG data. The Guava II algorithm analysis can detect and classify arrhythmias and may be used to triage data, however, Guava II is not intended to offer independent diagnosis or provide medical alarms. Clinical judgment and experience are used to check and interpret the data as part of a diagnosis. Guava II is not for use in lifesupporting or sustaining systems or EGG monitoring devices. Guava II is intended for use in clinics, hospitals, physician's offices, or anywhere a medical doctor deems appropriate.
Device Story
Guava II is medical device software with an API for capturing, storing, retrieving, viewing, and analyzing 1-, 2-, 3-channel, and 12-lead ECGs and biosignals. Used in clinics, hospitals, and physician offices by cardiologists, technicians, and nurses. Inputs include ECG data from external computer-based systems; outputs include ECG measurements, textual interpretations, and arrhythmia classifications. The device utilizes the Monebo Automated ECG Analysis and Interpretation Software Library and the QRS Louvain Algorithm to perform beat-by-beat signal processing, QRS feature extraction, interval/heart rate measurement, and rhythm analysis. It functions as a triage tool; clinical judgment is required for diagnosis. It does not provide medical alarms or independent diagnosis. Benefits include streamlined ECG data management and automated analysis of historic ambulatory data.
Clinical Evidence
Bench testing only. Verification and validation activities included scenario validations, algorithm confirmation testing, and device functional testing. The device complies with AAMI EC11 and AAMI EC38 standards. No clinical data was required for this submission.
Technological Characteristics
Medical device software with formal API. Features include ECG signal processing, QRS feature extraction, and arrhythmia classification. Complies with AAMI EC11 and AAMI EC38 standards. Utilizes the Monebo Automated ECG Analysis and Interpretation Software Library and QRS Louvain Algorithm (identical to predicate). Supports storage of raw input data and multi-language UI. Operates on current software platforms.
Indications for Use
Indicated for use by clinicians to store, retrieve, communicate, and analyze ECG data from single and multilead sources. Supports analysis of historic ambulatory ECG data for arrhythmia detection and triage. Not for life-supporting/sustaining systems or real-time ECG monitoring.
Regulatory Classification
Identification
An electrocardiograph is a device used to process the electrical signal transmitted through two or more electrocardiograph electrodes and to produce a visual display of the electrical signal produced by the heart.
Monebo Automated ECG Analysis and Interpretation Software Library (K062282)
Submission Summary (Full Text)
{0}------------------------------------------------
K122632
Pg. 1 of 3
# 510(k) SUMMARY (as required by 807.92(c))
FEB 1 1 2014
| Regulatory Correspondent: | AJW Technology Consultants, Inc.<br>445 Apollo Beach Blvd.<br>Apollo Beach, FL 33572<br>Jon Ward<br>wardjp@ajwtech.com<br>Phone: 813-645-2855<br>Fax: 813-677-4787 |
|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Submitter of 510(k): | CardioComm Solutions, Inc.<br>919 Fort St. Suite 203<br>Victoria, BC V8V 3K3<br>Mona Palfreyman<br>mona@cardiocomm.com<br>Phone: 250-744-1122<br>Fax: 250-744-1866 |
| Date of Summary: | January 31, 2014 |
| Trade/Proprietary Name: | Guava II |
| Classification Name: | Class II |
| Product Code: | DPS and DSH |
| Regulation: | 870.2340 |
#### Intended Use:
Guava II is intended to be used by cardiologists, general practitioners, cardiac or ECG technicians, nurses, monitoring service technicians, and other cardiac related institutions or care givers to store, retrieve, communicate and report ECG and ECG data acquired from a variety of ECG sources including single and multilead ECG devices. Guava II is intended to be electronically interfaced, and perform analysis with data transferred from other computer based ECG systems. Guava II includes an algorithm that will analyze the 12 Lead ECG and produce measurements of the ECG recording as well as textual interpretation. The product also includes an automatic analysis and interpretation software library that provides ECG signal processing and analysis on a beat by beat basis. QRS and Ventricular Ectopic Beat detection, QRS feature extraction, interval measurement, heart rate measurement, and rhythm analysis for up to twelve (12) leads of historic ambulatory ECG data. The Guava II algorithm analysis can detect and classify arrhythmias and may be used to triage data, however, Guava II is not intended to offer independent diagnosis or provide medical alarms. Clinical judgment and experience are
{1}------------------------------------------------
Pg. 2 of 3
used to check and interpret the data as part of a diagnosis. Guava II is not for use in lifesupporting or sustaining systems or EGG monitoring devices. Guava II is intended for use in clinics, hospitals, physician's offices, or anywhere a medical doctor deems appropriate.
## Device Description:
The Guava II is a medical device software with a formal Application Programming Interface (API). The API can be invoked from Host Applications to provide services for capturing, storing, retrieving, viewing, editing, and analyzing ECGs (1-, 2-, 3-Channel and 12-Lead) and other Biosignals. Guava II may also be licensed to 3rd party organizations interested in embedding the capabilities within their own products. When the Guava II is used in other medical products, manufacturers will identify the indications for use depending on the application of their device.
The Guava II is not a life-supporting or life-sustaining system. It is intended that competent human intervention be involved before any impact on health occurs. Clinical judgment and experience are used to check and interpret the data.
| Predicate Device(s): | GlobalCardio (K111320)<br>Monebo Automated ECG Analysis and<br>Interpretation Software Library (K062282) |
|----------------------|----------------------------------------------------------------------------------------------------------|
|----------------------|----------------------------------------------------------------------------------------------------------|
Guava II has the same classification information, the same performance safety, the same design principle, similar intended use and technological characteristics, similar product design and specifications. similar effectiveness. and similar function as compared to the predicate devices.
Guava II represents, specifically, the subset of the functionality embedded within the predicate GlobalCardio (K111320) - Guava, the predecessor of Guava II, which is the subject of this 510(k) application.
GlobalCardio makes full use of the Guava functionality to capture and manage ECG's the same functionality found in Guava II. Beyond that, GlobalCardio contains additional functionality outside the scope of ECG processing such as Patient Management, System Administration, Device Inventory Control, Cardiac Rehabilitation Data Management, etc. These are capabilities of the predicate device that are not contained in Guava II.
Guava II extends its predecessor, Guava, through the inclusion of features such as;
- . The integration of the Monebo Automated ECG Analysis and Interpretation Software Library (K062282) for use in analysis and triage.
- Technological enhancements such as a "globalization" capability to simplify . the translation of the software user interface into other languages.
- . The ability to run on current software platforms.
- . Incremental features such as the storage of the raw input data (e.g. audio waveform) into the ECG representation.
- And support for additional annotation types. .
{2}------------------------------------------------
The Guava II also contains a version of the QRS Louvain Algorithm; which is also embedded within the GlobalCardio predicate. The Guava II Louvain Data Processor performs automated ECG analysis and interpretation in the same manner as GlobalCardio. The two products use the identical machine code library (DLL) to perform the analysis, and testing demonstrates the ORS Algorithm embedded in the Guaya II Louvain Data Processor is identical in function to the QRS Algorithm embedded in GlobalCardio.
All other features of Guava II are present in at least one of the predicate devices. Therefore, the proposed Guava II device is substantially equivalent to GlobalCardio (K111320) and Monebo Automated ECG Analysis and Interpretation Software Library (K062282).
# Performance Testing:
The device complies with AAMI EC11 and AAMI EC38 standards. Verification and validation activities related to the device modification were performed on the applicant device, and the predetermined acceptance criteria were met in all cases. The activities included scenario validations, algorithm confirmation testing, and device functional testing.
### Conclusion:
The proposed device is substantial equivalent to the GlobalCardio (K111320) Monebo Automated ECG Analysis and Interpretation Software Library (K062282) devices. The proposed device has a similar intended use, technological, and design characteristics as the predicate device. Any minor differences do not introduce new issues of safety or effectiveness.
{3}------------------------------------------------
#### DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-002
Image /page/3/Picture/11 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a circular seal with the text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" arranged around the perimeter. Inside the circle is a stylized symbol that resembles a person embracing or being embraced, represented by three curved lines.
February 11, 2014
Cardiocomm Solutions, Inc. Jonathan Ward 962 Allegro Lane Apollo Beach, FL 33572 US
Re: K122632
> Trade/Device Name: Guava II Regulation Number: 21 CFR 870.2340 Regulation Name: Electrocardiograph Regulatory Class: Class II Product Code: DPS, DSH Dated: October 25, 2013 Received: August 29, 2012
### Dear Jonathan Ward:
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 (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. 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.
{4}------------------------------------------------
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 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHOffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. Also, please note the regulation entitled, Misbranding by reference to premarket notification (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htmfor the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638 2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours,
Owen-Paris-S
for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
{5}------------------------------------------------
Indications for Use
. . . . ......
510(k) Number (if known): K122632
Device Name: Guava II
Guava II is intended to be used by cardiologists, general practitioners, cardiac or ECG technicians, nurses, monitoring service technicians, and other cardiac related institutions or care givers to store, retrieve, communicate and report ECG and ECG data acquired from a variety of ECG sources including single and multilead ECG devices. Guava II is intended to be electronically interfaced, and perform analysis with data transferred from other computer based ECG systems. Guava II includes an algorithm that will analyze the 12 Lead ECG and produce measurements of the ECG recording as well as textual interpretation. The product also includes an automatic analysis and interpretation software library that provides ECG signal processing and analysis on a beat by beat basis, QRS and Ventricular Ectopic Beat detection, QRS feature extraction, interval measurement, heart rate measurement, and rhythm analysis for up to twelve (12) leads of historic ambulatory ECG data. The Guava II algorithm analysis can detect and classify arrhythmias and may be used to triage data, however, Guava II is not intended to offer independent diagnosis or provide medical alarms. Clinical judgment and experience are used to check and interpret the data as part of a diagnosis. Guava II is not for use in lifesupporting or sustaining systems or EGG monitoring devices. Guava II is intended for use in clinics, hospitals, physician's offices, or anywhere a medical doctor deems appropriate.
Prescription Use X Prescription Ose A
(Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE OF NEEDED)
| Concurrence of CDRH, Office of Device Evaluation (ODE) |
|--------------------------------------------------------|
| Digitally signed by |
| Owen P. Faris -S |
Digitally signed By
Owen P. Faris -S
Date: 2014.02.11
16:23:45'-05'00'
Page 1 of 1
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 Tutorial 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-only devices, 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-only devices), 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.