K210543 · Implicity, Inc. · DQK · Nov 3, 2021 · Cardiovascular
Device Facts
Record ID
K210543
Device Name
IM007
Applicant
Implicity, Inc.
Product Code
DQK · Cardiovascular
Decision Date
Nov 3, 2021
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1425
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Asystole
—
—
—
—
—
—
—
Bradycardia
—
—
—
—
—
—
—
Atrial Tachycardia / Atrial Fibrillation
—
—
—
—
—
—
—
Ventricular Tachycardia
—
—
—
—
—
—
—
Normal Rhythm
—
—
—
—
—
—
—
Artifact
—
—
—
—
—
—
—
Indications for Use
IM007 is intended for use by qualified healthcare professionals for the assessment of arrhythmias in Insertable Cardiac Monitor (ICM) ECG data. IM007 supports downloading and analyzing data recorded in compatible formats from ICMs. This version of the IM007 only supports ECG data from Medtronic ICMs. IM007 is intended to be electronically interfaced with other computer systems (remote monitoring platform) that supply the ECG data to IM007, and receive the output of IM007 (analysis) for viewing by the healthcare professionals. IM007 provides ECG signal processing and analysis, to detect asystole, bradycardia, atrial tachycardia or atrial fibrillation, ventricular tachycardia, normal rhythm and artifact. IM007 is not for use in life supporting or sustaining systems or ECG monitor and Alarm devices. IM007 interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians 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
IM007 is a cloud-based software medical device (SaMD) that analyzes ECG signals from Medtronic Insertable Cardiac Monitors (ICMs). It functions as a server-side service accessed via an API by remote monitoring platforms. The device receives ECG files and parameters, processes them using a proprietary machine learning algorithm to detect arrhythmias (asystole, bradycardia, AT/AF, VT, normal rhythm, or artifact), and returns labeled waveform segments with timestamps to the remote platform. It is operated by healthcare professionals who review the advisory analysis alongside clinical history to aid in diagnosis. It does not provide a user interface or storage, relying on the integrated remote monitoring platform for these functions. It benefits patients by providing automated, supportive analysis of long-term cardiac monitoring data.
Clinical Evidence
Bench testing only. Algorithm performance was validated using ECG databases compliant with ANSI/AAMI EC57:2012 and proprietary Implicity databases. Results confirmed the device meets specifications and performs equivalently to the predicate device.
Technological Characteristics
Cloud-based server-side service; API-based communication (messaging queues); Machine Learning-based arrhythmia detection algorithm; interfaces with remote monitoring platforms; no client-side software or hardware; software-only device.
Indications for Use
Indicated for adults (over 18) with clinical syndromes or situations at increased risk of cardiac arrhythmias, or experiencing transient symptoms (dizziness, palpitation, syncope, chest pain) suggesting arrhythmia. Not tested for pediatric use.
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
November 3, 2021
Implicity, Inc. % Mark Johnson Regulatory Consultant MJ Medtech Consulting Services LLC 24125 Butteville Rd. NE Aurora, Oregon 97002
Re: K210543
Trade/Device Name: IM007 Regulation Number: 21 CFR 870.1425 Regulation Name: Programmable Diagnostic Computer Regulatory Class: Class II Product Code: DQK, DPS Dated: October 1, 2021 Received: October 4, 2021
Dear Mark Johnson:
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. 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 located 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.
{1}------------------------------------------------
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 of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 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-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/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-device-advice-comprehensive-regulatoryassistance/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).
Sincerely.
Jennifer Shih 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
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K210543
Device Name IM007
## Indications for Use (Describe)
IM007 is intended for use by qualified healthcare professionals for the assessment of arrhythmias in Insertable Cardiac Monitor (ICM) ECG data.
IM007 supports downloading and analyzing data recorded in compatible formats from ICMs. This version of the IM007 only supports ECG data from Medtronic ICMs.
IM007 is intended to be electronically interfaced with other computer systems (remote monitoring platform) that supply the ECG data to IM007, and receive the output of IM007 (analysis) for viewing by the healthcare professionals. IM007 provides ECG signal processing and analysis, to detect asystole, bradycardia, atrial tachycardia or atrial fibrillation, ventricular tachycardia, normal rhythm and artifact.
IM007 is not for use in life supporting or sustaining systems or ECG monitor and Alarm devices.
IM007 interpretation results are not intended to be the sole means of diagnosis. It is offered to physicians on an advisory basis only in conjunction with the physician's knowledge of ECG patterns, patient background, clinical history, symptoms, and other diagnostic information.
Type of Use (Select *one* or *both*, as applicable)X Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
## CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
## *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# 510(k) Summary
This summary of 510(k) substantial equivalence information is submitted in accordance with the requirements of 21 CFR 807.92
#### General Information 1
| Applicant | IMPLICITY INC<br>185 ALEWIFE BROOK PARKWAY - SUITE 210<br>CAMBRIDGE, MA 02138<br>USA<br>Phone: +33 6 76 731 731 |
|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact Person | David Perlmutter<br>Head of R&D<br>IMPLICITY INC<br>185 ALEWIFE BROOK PARKWAY - SUITE 210<br>CAMBRIDGE, MA 02138<br>USA<br>regulatory@implicity.com<br>Phone: +33 6 76 731 731 |
Assisted by Mark Johnson Regulatory consultant to Implicity Inc MJ Medtech Consulting Services LLC 3332 Rockwood circle Billings, Montana 59102
+1 (503) 575-5886
#### 2 Date prepared: November 2, 2021
#### Device Information 3
| Trade Name | IM007 Insertable Cardiac Monitor ECG Analysis System |
|----------------|-------------------------------------------------------------|
| Common Name | ICM ECG Analysis System |
| Classification | 21 CFR 870.1425, Programmable diagnostic computer, Class II |
| | 21 CFR 870.2340, Electrocardiograph, Class II |
| Product Code | DQK, DPS |
{4}------------------------------------------------
#### Predicate Device 4
The predicate and reference devices for IM007 Insertable Cardiac Monitor ECG Analysis System are:
Predicate Device CARDIOLOGS, Inc., CardioLogs ECG Analysis Platform, K170568
Reference Device MEDTRONIC, Inc., Reveal LINQ Insertable Cardiac Monitor, K163460
Table 1 provides device information for the subject device Implicity IM007 and compares it to the predicate and the reference devices listed.
| | Subject Device | Predicate Device | Reference Device | Comparison<br>to Predicate |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Device Name | IM007 | CardioLogs ECG<br>Analysis Platform | Reveal LINQ Insertable<br>Cardiac Monitor, Model<br>LNQ11 | |
| Manufacturer | IMPLICITY INC | CARDIOLOGS<br>TECHNOLOGIES | MEDTRONIC INC | |
| 510(k) # | K210543 | K170568 | K163460 | |
| Regulation<br>Number | 21 CFR 870.1425<br>21 CFR 870.2340 | 21 CFR 870.1425<br>21 CFR 870.2340 | 21 CFR 870.1025 | Same |
| Class | II | II | II | Same |
| Device Class /<br>Name | Programmable<br>diagnostic computer,<br>Electrocardiograph | Programmable<br>diagnostic<br>computer,<br>Electrocardiograph | Detector and Alarm,<br>Arrhythmia | Same |
| Product Code | DQK, DPS | DQK, DPS | DSI | Same |
| Level of<br>Concern | Major | Moderate | Major | Same |
| Table 2 Comparison between Subject, Predicate and Reference Devices indication for use | | | | |
| | Subject Device | Predicate Device | Reference<br>Device | Comparison to<br>Predicate Device |
| Indication<br>for Use | IM007 is intended for<br>use by qualified<br>healthcare<br>professionals for the<br>assessment of<br>arrhythmias in<br>Insertable Cardiac<br>Monitor (ICM) ECG<br>data. | The CardioLogs ECG<br>Analysis Platform is<br>intended for use by<br>qualified healthcare<br>professionals for the<br>assessment of<br>arrhythmias using ECG<br>data. | The Reveal LINQ<br>ICM is an<br>insertable<br>automatically<br>activated and<br>patient-activated<br>monitoring<br>system that<br>records<br>subcutaneous<br>ECG.<br><br>It is indicated in<br>the following<br>cases:<br>patients with<br>clinical<br>syndromes or<br>situations at<br>increased risk of | The Indication for Use<br>for the Subject Device<br>is focused on a subset<br>of ECG data which<br>specifically is<br>generated from ICM<br>devices. The<br>algorithm has been<br>developed for use<br>with all ECG<br>generating cardiac<br>monitors. Validation<br>of Implicity's first<br>generation system is<br>focused on ICM<br>outputs.<br><br>The safety and<br>performance of ECG<br>interpretation of ICM<br>devices is comparable<br>to that of the broader<br>array of ECG systems. |
| Subject Device | Predicate Device | Reference<br>Device | Comparison to<br>Predicate Device | |
| IM007 supports<br>downloading and<br>analyzing data<br>recorded in<br>compatible formats<br>from ICMs.<br>This version of the<br>IM007 only supports<br>ECG data from<br>Medtronic ICMs. | The product supports<br>downloading and<br>analyzing data<br>recorded in compatible<br>formats from any<br>device used for the<br>arrhythmia diagnostics<br>such as Holter, event<br>recorder, 12 lead<br>ambulatory ECG<br>devices, or other<br>similar devices when<br>assessment of the<br>rhythm is necessary. | cardiac<br>arrhythmias<br>● patients who<br>experience<br>transient<br>symptoms such<br>as dizziness,<br>palpitation,<br>syncope, and<br>chest pain that<br>may suggest a<br>cardiac<br>arrhythmia. | The Subject Device<br>takes ECG data only<br>from ICMs, and as in<br>the Predicate, use is<br>restricted to<br>compatible formats. | |
| IM007 is intended to<br>be electronically<br>interfaced with other<br>computer systems<br>(remote monitoring<br>platform) that supply<br>the ECG data to<br>IM007 and receive<br>the output of IM007<br>(analysis) for viewing<br>by the healthcare<br>professionals. | The Cardiologs ECG<br>Analysis Platform can<br>also be electronically<br>interfaced and perform<br>analysis with data<br>transferred from other<br>computer-based ECG<br>systems, such as an<br>ECG management<br>system.<br>The product can be<br>integrated into<br>computerized ECG<br>monitoring devices. | The device has<br>not been tested<br>specifically for<br>pediatric use. | Same | |
| Table 2 Comparison between Subject, Predicate and Reference Devices indication for use | | | | |
| | Subject Device | Predicate Device | Reference<br>Device | Comparison to<br>Predicate Device |
| | IM007 provides ECG<br>signal processing and<br>analysis, to detect<br>asystole, bradycardia,<br>atrial tachycardia or<br>atrial fibrillation,<br>ventricular<br>tachycardia, normal<br>rhythm and artifact. | The Cardiologs ECG<br>Analysis Platform<br>provides ECG signal<br>processing and<br>analysis, QRS and<br>Ventricular Ectopic<br>Beat detection, QRS<br>feature extraction,<br>interval measurement,<br>heart rate<br>measurement, and<br>rhythm<br>analysis. | | The Subject Device<br>uses equivalent signal<br>processing and<br>analysis methodology<br>as the Predicate.<br>The Subject Device<br>operates as a<br>software module<br>electronically<br>interfaced to another<br>computer system<br>that handles ECG<br>data, which is also<br>one of the modes of<br>operation of the<br>Predicate. |
| | IM007 is not for use<br>in life supporting or<br>sustaining systems or<br>ECG monitor and<br>Alarm devices. | The Cardiologs ECG<br>Analysis Platform is not<br>for use in life<br>supporting or<br>sustaining systems or<br>ECG monitor and<br>Alarm devices. | | Same |
| Table 2 Comparison between Subject, Predicate and Reference Devices indication for use | | | | |
| | Subject Device | Predicate Device | Reference<br>Device | Comparison to<br>Predicate Device |
| | IM007 interpretation<br>results are not<br>intended to be the<br>sole means of<br>diagnosis. It is offered<br>to physicians and<br>clinicians on an<br>advisory basis only in<br>conjunction with the<br>physician's<br>knowledge of ECG<br>patterns, patient<br>background, clinical<br>history, symptoms,<br>and other diagnostic<br>information. | CardioLogs ECG<br>Analysis Platform<br>interpretation results<br>are not intended to be<br>the sole means of<br>diagnosis. It is offered<br>to physicians and<br>clinicians on an<br>advisory basis only in<br>conjunction with the<br>physician's knowledge<br>of ECG patterns,<br>patient background,<br> | | Same |
{5}------------------------------------------------
The following Table 2 compares the Indication for Use of the Subject Device to the Predicate and the Reference Devices.
{6}------------------------------------------------
## Table 2 Comparison between Subject, Predicate and Reference Devices indication for use
{7}------------------------------------------------
{8}------------------------------------------------
{9}------------------------------------------------
| Table 2 Comparison between Subject, Predicate and Reference Devices indication for use | | | | |
|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Subject Device | Predicate Device | Reference Device | Comparison to Predicate Device |
| Patient<br>population | Adults (over 18) in<br>the following cases:<br>- patients with clinical<br>syndromes or<br>situations at<br>increased risk of<br>cardiac arrhythmias<br>- patients whosymptoms such as<br>dizziness, palpitation,<br>syncope, and chest<br>pain that may suggest<br>a cardiac arrhythmia.<br><br>The device has not<br>been tested<br>specifically for<br>pediatric use. | Adults (over 18). | - patients with<br>clinical<br>syndromes or<br>situations at<br>increased risk of<br>cardiac<br>arrhythmias<br>- patients who<br>experience<br>transient<br>symptoms such<br>as dizziness,<br>palpitation,<br>syncope, and<br>chest pain that<br>may suggest a<br>cardiac<br>arrhythmia<br><br>The device has<br>not been tested<br>specifically for<br>pediatric use. | Same.<br><br>The Subject Device<br>has also the same<br>target population of<br>the Reference Device,<br>which is a subset of<br>the target population<br>of the Predicate<br>Device. |
The Subject, Predicate, and Reference devices all provide output classifications in the analysis of ECG signals that are transmitted from compatible Insertable Cardiac Monitor (ICM) devices. Table 3 below compares the output classifications between these devices.
{10}------------------------------------------------
| Table 3 Comparison between Subject, Reference & Predicate Devices rhythm analysis outputs | | | | |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
| Subject Device<br>Output classification | Reference Device<br>Reveal LINQ | Predicate Device | Comparison with<br>Predicate Device | |
| Asystole (Ventricular<br>pause)<br>Absence of ventricular<br>contraction for a<br>duration equal or<br>superior to the asystole<br>programmable duration. | Pause (asystole)<br>No ventricular events<br>are sensed for a<br>programmable period<br>of time. | Ventricular pause<br>No ventricular<br>complex during at<br>least three seconds. | Same (except for the<br>programmable<br>duration) | |
| Bradycardia<br>Slow ventricular rate.<br>Lower than the<br>programmable brady<br>rate | Brady<br>(bradyarrhythmia)<br>The patient's heart rate<br>falls to a rate that is<br>lower than the<br>programmable brady<br>threshold. | Sinus bradycardia<br>(< 50 /min)<br>Sinus rhythm with<br>unusual or<br>abnormal slow rate. | Same | |
| AT/AF (Atrial<br>Tachycardia / Atrial<br>Fibrillation)<br>At least one of the<br>following:<br>- Atrial tachycardia<br>(ectopic)<br>- Atrial flutter<br>- Atrial fibrillation | AF only or AT/AF<br>(atrial fibrillation only<br>or atrial<br>tachyarrhythmia/atrial<br>fibrillation)<br>The patient has an<br>atrial tachyarrhythmia<br>or atrial fibrillation. The<br>clinician can also<br>choose to record atrial<br>fibrillation only. The<br>Reveal LINQ device<br>detects an episode of<br>conducted AT or AF by<br>analyzing the<br>irregularity of<br>ventricular rhythm<br>using an automatic<br>algorithm. | AF - Atrial<br>fibrillation<br>AF - Atrial<br>fibrillation or flutter<br>(uncertain)<br>Atrial flutter<br>Atrial tachycardia or<br>flutter<br>AF - Atrial<br>fibrillation, flutter<br>or atrial tachycardia<br>Atrial tachycardia,<br>ectopic<br>AT - Atrial<br>tachycardia - | Same<br>All classifications are<br>regrouped under one<br>because of the<br>clinical significance<br>and the fact that it is<br>often impossible to<br>distinguish with<br>certainty by<br>healthcare<br>professional. | |
| Table 3 Comparison between Subject, Reference & Predicate Devices rhythm analysis outputs | | | | |
| Subject Device<br>Output classification | Reference Device<br>Reveal LINQ | Predicate Device | Comparison with<br>Predicate Device | |
| | | short run(s) | | |
| VT Ventricular<br>Tachycardia<br>At least one of the<br>following:<br>-Tachycardia that<br>originates in a ventricle.<br>Sometimes life-<br>threatening.<br>NSVT - Non-sustained<br>ventricular tachycardia | Tachy (ventricular<br>tachyarrhythmia)<br>The patient's heart rate<br>increases to a rate that<br>is higher than the<br>programmable tachy<br>rate (interval)<br>threshold for the<br>programmable tachy<br>duration or higher than<br>231 bpm (intervals<br>lower than 260 ms) for<br>30 of the last 40 beats. | VT - Ventricular<br>tachycardia<br>Wide-QRS<br>tachycardia that<br>originates in a<br>ventricle.<br>Sometimes life-<br>threatening.<br>NSVT - Non-<br>sustained<br>ventricular<br>tachycardia<br>Run of ≥ 4<br>consecutive<br>premature<br>ventricular<br>complexes with a<br>heart rate ≥ 100<br>/min. | Same<br>All classifications are<br>regrouped under one<br>because of the<br>clinical significance<br>and the fact that it is<br>often impossible to<br>distinguish with<br>certainty by<br>healthcare<br>professional,<br>with the exception of<br>using the<br>programmable tachy<br>rate. | |
| Normal Rhythm<br>The ECG does not<br>present any significant<br>abnormality. | N/A (Normal rhythm is<br>absence of abnormal<br>classification).<br>Normal rhythm is<br>detected by the device<br>but not transmitted<br>through remote<br>monitoring. | Normal rhythm is<br>absence of<br>abnormal<br>classification. | Same | |
| Unspecified<br>abnormality<br>An abnormality is<br>detected in the signal,<br>but the abnormality is | N/A | N/A | This label is specific<br>to IM007<br>This output prompts<br>the healthcare | |
| Table 3 Comparison between Subject, Reference & Predicate Devices rhythm analysis outputs | | | | |
| Subject Device<br>Output classification | Reference Device<br>Reveal LINQ | Predicate Device | Comparison with<br>Predicate Device | |
| not classified as one of<br>the other abnormality<br>labels by the algorithm. | | | professional to<br>review the ECG | |
| Artifact<br>Presence of a non-<br>cardiac noise, which<br>distorts the signal and<br>prevents proper medical<br>interpretation of the<br>specified portion. | N/A | X - Pure noise<br>Tracing with only<br>noise and no ECG<br>data | Same | |
{11}------------------------------------------------
{12}------------------------------------------------
Table 4 provides a comparison of the features of the Subject and Predicate devices.
| Table 4 Comparison between Subject and Predicate Devices features | | | |
|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|--------------------------------------|
| Feature | Subject Device<br>IM007 | Predicate Device<br>CardioLogs ECG<br>Analysis Platform | Comparison to<br>Predicate<br>Device |
| Heart rate<br>determination for<br>non-paced adult | Yes | Yes | Same |
| QRS detection | Yes<br>This is not an output of the<br>Subject Device but is<br>calculated as an intermediate<br>value prior to generating the<br>output. | Yes | Same |
| Non-paced<br>arrhythmia<br>interpretation for<br>adult patients | Yes | Yes | Same |
{13}------------------------------------------------
| Table 4 Comparison between Subject and Predicate Devices features | | | |
|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------------|
| Feature | Subject Device<br>IM007 | Predicate Device<br>CardioLogs ECG<br>Analysis Platform | Comparison to<br>Predicate<br>Device |
| User interface to<br>view ECG data with<br>tools | No<br>IM007 does not include a user<br>interface for viewing ECG data,<br>as the viewing of ECG data<br>belongs to the "client"<br>application. | Yes<br>The user should only<br>use CardioLogs' user<br>interface to view<br>ECG data analysis. | not necessary<br>for the intended<br>use |
| Database to store<br>the results | No<br>Results are stored in the<br>"client application". | Yes | Not necessary<br>for the intended<br>use |
Table 5 provides a comparison of the technology of the Subject, Predicate, and Reference devices
| Table 5 Comparison between Subject, Reference, and Predicate Devices technology | | | |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Subject Device | Predicate Device…
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.