K191406 · AliveCor, Inc. · DXH · Jan 24, 2020 · Cardiovascular
Device Facts
Record ID
K191406
Device Name
KardiaMobile, KardiaStation
Applicant
AliveCor, Inc.
Product Code
DXH · Cardiovascular
Decision Date
Jan 24, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2920
Device Class
Class 2
Attributes
Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K191406 · Jan 24, 2020
KardiaMobile, KardiaStation
AliveCor, Inc.
Historical real-world use data from previously cleared KardiaMobile devices (K182396 and prior)
Real-world use data from the predicate device's history was used to support the clinical performance of the hardware in acquiring ECG signals of sufficient quality for display and analysis.
Historical Real-World Use of KardiaMobile Hardware; Retrospective analysis of historical device performance; Follow-up/Duration: Long history of use; Study Period: Prior to January 2020
Users of previously cleared KardiaMobile devices
Not applicable for this study
ECG signal quality equivalent to 12-lead ECG
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Atrial Fibrillation detection
—
—
—
—
—
—
—
Normal Sinus Rhythm detection
—
—
—
—
—
—
—
Bradycardia detection
—
—
—
—
—
—
—
Tachycardia detection
—
—
—
—
—
—
—
Indications for Use
The KardiaMobile System is intended to record, store and transfer single-channel electrocardiogram (ECG) rhythms. The KardiaMobile System also displays ECG rhythms and output of ECG analysis from AliveCor's KardiaAI platform including detecting the presence of normal sinus rhythm, atrial fibrillation, bradycardia, and others. The KardiaMobile System is intended for use by healthcare professionals, patients with known or suspected heart conditions and health conscious individuals. The device has not been tested and is not intended for pediatric use.
Device Story
KardiaMobile is a trans-telephonic single-channel ECG event recorder; consists of hardware electrodes and Kardia phone app on iOS/Android smartphones (Mobile Computing Platforms). User initiates contact with electrodes; device records ECG signal; transmits to app for analysis and display. KardiaAI platform processes signal to detect atrial fibrillation, normal sinus rhythm, bradycardia, and tachycardia. Used in ambulatory settings by patients or healthcare professionals. Output displayed on smartphone; allows independent evaluation by physicians (e.g., via PDF). Enables remote monitoring and arrhythmia detection; facilitates clinical decision-making by providing actionable ECG data without requiring initial clinician overread.
Clinical Evidence
Bench and clinical performance testing conducted. Algorithm validated against ANSI/AAMI EC57:2012 and proprietary databases. Human factors usability testing (per IEC 62366-1:2015) demonstrated that representative users can correctly acquire ECGs, interpret device outputs, and understand when to seek medical care without clinician overread. No new clinical trials were required for this modification.
Technological Characteristics
Single-channel ECG recorder; hardware electrodes interface with iOS/Android smartphones via app. Principle of operation: trans-telephonic ECG acquisition. Software-based analysis (KardiaAI) for arrhythmia detection. Connectivity: smartphone-based. Sterilization: not specified. Software class: algorithm-based analysis.
Indications for Use
Indicated for healthcare professionals, patients with known or suspected heart conditions, and health-conscious individuals to record, store, and transfer single-channel ECG rhythms and detect normal sinus rhythm, atrial fibrillation, bradycardia, and tachycardia. Not for pediatric use.
Regulatory Classification
Identification
A telephone electrocardiograph transmitter and receiver is a device used to condition an electrocardiograph signal so that it can be transmitted via a telephone line to another location. This device also includes a receiver that reconditions the received signal into its original format so that it can be displayed. The device includes devices used to transmit and receive pacemaker signals.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left, there is a symbol representing the Department of Health & Human Services - USA. To the right of this symbol, there is a blue square with the letters "FDA" in white. Next to the blue square, the words "U.S. FOOD & DRUG ADMINISTRATION" are written in blue.
January 24, 2020
AliveCor, Inc. Saket Bhatt Senior Manager, Regulatory Affairs 444 Castro Street. Suite 600 Mountain View, California 94041
Re: K191406
Trade/Device Name: KardiaMobile, KardiaStation Regulation Number: 21 CFR 870.2920 Regulation Name: Telephone electrocardiograph transmitter and receiver Regulatory Class: Class II Product Code: DXH, DPS, QDA Dated: December 20, 2019 Received: December 23, 2019
Dear Saket Bhatt:
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.
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
{1}------------------------------------------------
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,
Hetal Patel 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) K191406
Device Name KardiaMobile System
#### Indications for Use (Describe)
The KardiaMobile System is intended to record, store and transfer single-channel electrocardiogram (ECG) rhythms. The KardiaMobile System also displays ECG rhythms and output of ECG analysis from AliveCor's KardiaAl platform including detecting the presence of normal sinus rhythm, atrial fibrillation, bradycardia, and others. The KardiaMobile System is intended for use by healthcare professionals, patients with known or suspected heart conditions and health conscious individuals. The device has not been tested and is not intended for pediatric use.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------|--|
|-------------------------------------------------|--|
Prescription Use (Part 21 CFR 801 Subpart D)
X 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) Notification K191406
#### GENERAL INFORMATION [807.92(a)(1)]
#### Applicant:
AliveCor, Inc. 444 Castro Street, Suite 600 Mountain View, CA 94041 Phone: 650-396-8553 Fax: 650-282-7932
#### Contact Person:
Saket Bhatt Vice President, Regulatory Affairs AliveCor, Inc. 444 Castro Street, Suite 600 Mountain View, CA 94041 Phone: 650-396-8553 Email: RA@alivecor.com
Date Prepared: January 22, 2020
DEVICE INFORMATION [807.92(a)(2)]
Trade/Proprietary Name: KardiaMobile System
# Generic/Common Name:
Telephone electrocardiograph transmitter and receiver
#### Classification:
21 CFR §870.2920, Telephone electrocardiograph transmitter and receiver, Class II
Product Code: DXH, DPS, QDA
Establishment Registration: 3009715978
#### PREDICATE DEVICE(S) [807.92(a)(3)]
K182396 - AliveCor KardiaMobile System (Primary predicate) DEN180044 - Apple Inc. ECG App (Secondary predicate)
{4}------------------------------------------------
# DEVICE DESCRIPTION [807.92(a)(4)]
The KardiaMobile System is a trans-telephonic (transmission by telephone) ECG (electrocardiogram) event recorder that records, stores and transfers single-channel electrocardiogram rhythms. The device utilizes the computing power of Apple iOS- and Google Android-based smartphones to obtain and analyze single-channel ECG. These smartphones are termed Mobile Computing Platforms (MCPs). The device consists of the hardware (that has the electrodes), and the Kardia phone app (installed on an MCP). The same software is implemented in the iOS and Android MCP. In either configuration, the same hardware is used to sense the ECG. The KardiaMobile Hardware transmits the ECG signal from the electrode to the Kardia phone app on the MCP to be analyzed and presented to the user. All ECGs are synced with the user's account.
# INDICATIONS FOR USE [807.92(a)(5)]
#### Indications for Use:
The KardiaMobile System is intended to record, store and transfer single-channel electrocardiogram (ECG) rhythms. The KardiaMobile System also displays ECG rhythms and output of ECG analysis from AliveCor's KardiaAI platform including detecting the presence of normal sinus rhythm, atrial fibrillation, bradycardia, and others. The KardiaMobile System is intended for use by healthcare professionals, patients with known or suspected heart conditions and health conscious individuals. The device has not been tested and is not intended for pediatric use.
Type of Use:
Over-The-Counter Use (21 CFR 801 Subpart C)
#### Comparison with Predicate Devices:
The proposed device and both predicate devices have the same intended use of recording, displaying, analyzing, storing, and transferring single-lead ECG rhythms in an ambulatory setting. As such, the proposed device and its predicates are substantially equivalent with respect to intended use.
The proposed device and primary predicate device have similar Indications for Use which fall within the scope of the same intended use. The Indications for Use between the proposed device and primary predicate device (K182396) are highly similar and vary solely with respect to removal of the requirement for use under supervision of a clinician. The proposed device and secondary predicate device's (DEN180044) Indications for Use statements describe the same range of functionality with respect to ECG recording, display, and analysis; and neither device includes an unlock mechanism for access to any functionality or requires use "under the care of the physician," as is the case with the primary predicate device.
{5}------------------------------------------------
#### 510(K) SUMMARY (CONT.)
The KardiaMobile System has undergone evaluation in accordance to the Special Controls associated with 21CFR§ 870.2345, Electrocardiograph Software for Over-the-Counter Use. Specifically, human factors usability testing was conducted, where lay users have demonstrated the ability to both correctly use the device and understand the output of the device as designed when relying on only labeling. The evidence with the study results demonstrates that the removal of overread function brings the OTC use of the proposed device to be consistent with the secondary predicate device.
### TECHNOLOGICAL CHARACTERISTICS OF THE DEVICE COMPARED WITH THE PREDICATE DEVICE [807.92(a)(6)]
The proposed KardiaMobile System device is highly similar to the primary predicate device with respect to technological characteristics, in terms of principle of operation, technological and performance characteristics (mechanism of action, environmental specifications, dimensional specifications, ergonomics of patient-user interface, packaging, sterilization and shelf life), materials, software and anatomical site. No modifications were made to the device hardware or to the Kardia app software's clinical functionalities with respect to ECG acquisition, display, and analysis as a result of this change.
The minor change which prompted this 510(k) is a change in the first-use onboarding procedure when the device is used in an OTC setting for new patients. While the predicate KardiaMobile System device required ECG review by a professional (i.e., "unlock overread") prior to a consumer patient gaining access to first-time ECG data analysis, the proposed KardiaMobile System device does not require the unlock overread. This onboarding step, without unlock overread, for the proposed KardiaMobile System device is similar to the secondary predicate device, the Apple Inc. ECG App (DEN180044), with respect to the lack of any unlocking requirements prior to access of ECG display and recording functions, therefore prompting its inclusion as a secondary predicate device. Specifically:
- . With respect to the OTC Use Model, the primary predicate device's OTC use requires clinician overread, whereas the proposed device does not. in order to reduce the patient's burden of onboarding prior to use of the device and to improve AliveCor's operational efficiency. The removal of overread function does not add risk or remove mitigations of risk as compared with the primary predicate device as it only required a single time clinician interpretation of the patient's ECG. after which patients use the predicate device in the same manner as they would the proposed device. This updated OTC use case is further consistent with that of the ECG app secondary predicate device with respect to direct ECG display/analysis access without any "unlock" mechanisms.
- . With respect to ECG recording and display, the ECG recording procedure of the proposed device is identical to that of the predicate devices, in which the user initiates contact with the electrodes of the device's hardware (the identical KardiaMobile hardware in the case of the proposed and primary predicate device, and consumer Apple Watch hardware in the case of the secondary predicate device), upon which ECG signal is recorded and processed by software. In all three (3) devices, the ECG recording is processed and displayed regardless of the ECG analysis outcomes, which allows the ECG signal to be evaluated independently by a trained physician (e.g., via sending an e-mailed PDF report). There are minor differences between the proposed and predicate devices with respect to the specific method of ECG display. In both the proposed and secondary
{6}------------------------------------------------
predicate devices, the ECG reading is displayed to the user via the associated software after the recording is complete. In the primary predicate device, the recording is similarly displayed for the user after recording completion under normal use, but for first-time use, the ECG recording is withheld from the user upon completion until the ECG signal recorded is reviewed by a board-certified cardiologist under the "overread unlock" mechanism.
- With respect to ECG analysis, after acquisition and initial processing of ECG signals, the ● proposed device and both predicate devices also include algorithms for filtering and analysis of ECG signals for arrhythmia. Specifically, all three (3) devices detect the presence of atrial fibrillation and Normal Sinus Rhythm. The proposed and primary predicate devices also detect the presence of two additional arrythmia conditions bradycardia and tachycardia – which are within the shared intended use of the proposed and both predicate devices. All three (3) devices further provide outputs for nondeterminative cases, i.e., in which the quality of the ECG may not enable the algorithmic determination, or in cases where the ECG may exhibit an arrhythmia other than those detectable by the algorithm. As such, the ECG algorithm outputs are similar between the proposed and predicate devices.
The removal of the unlock overread function does not introduce new risks or significantly modify existing risks, nor does it remove mitigations of risk as compared with the primary predicate device. The removal of overread function brings the OTC use of the product to be consistent with the secondary predicate device. Through human factors usability testing, it is demonstrated that users can use the device correctly solely based on labeling, and that the device labeling provides sufficient information to allow users to appropriately interpret the device output with respect to understanding the analysis output as well as when to seek medical attention.
Therefore, the proposed device and the predicate device share key technological characteristics, especially in reference to those associated with the key clinical functionalities of ECG recording, display, and analysis.
# PERFORMANCE DATA [807.92(b)]
Performance testing of the proposed device was conducted in compliance to the special controls associated with Electrocardiograph Software for Over-the-Counter Use (Product Code: ODA), as demonstrated further within the table below. A further discussion of the testing conducted specifically to support the removal of "unlock overread" follows this Special Controls table.
{7}------------------------------------------------
| Special Control | Summary of Conformance |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. Clinical performance testing under anticipated<br>conditions of use must demonstrate the following:<br>(a) The ability to obtain an ECG of sufficient<br>quality for display and analysis; and | The KardiaMobile device has demonstrated its ability to<br>obtain ECGs of sufficient quality for display and analysis<br>through both bench and clinical performance testing. |
| (b) The performance characteristics of the<br>detection algorithm as reported by<br>sensitivity and either specificity or positive<br>predictive value. | The KardiaMobile System leverages the KardiaAI SaMD<br>(K181823) for ECG analysis. KardiaAI is validated in a<br>dataset representative of the patient population of the<br>proposed device. KardiaAI algorithm suite ECG detection<br>algorithm outputs of Atrial Fibrillation, Normal,<br>Bradycardia, Tachycardia, and Noise as well as the heart<br>rate calculations were tested to meet the system<br>requirements for sensitivity and specificity. Testing was<br>conducted to ANSI/AAMI EC57:2012 databases and<br>AliveCor's proprietary databases. |
| 2. Software verification, validation, and hazard<br>analysis must be performed.<br>Documentation must include a characterization of<br>the technical specifications of the software,<br>including the detection algorithm and its inputs<br>and outputs. | Software documentation for the KardiaMobile software was<br>prepared and provided in accordance with FDA's Guidance<br>titled, Guidance for the Content of Premarket Submissions<br>for Software Contained in Medical Devices (May 11, 2015). |
| 3. Non-clinical performance testing must validate<br>detection algorithm performance using a<br>previously adjudicated data set | KardiaAI algorithm suite ECG detection algorithm outputs<br>of Atrial Fibrillation, Normal, Bradycardia, Tachycardia,<br>and Noise as well as the heart rate calculations were tested<br>to meet the system requirements for sensitivity and<br>specificity. Testing was conducted to ANSI/AAMI<br>EC57:2012 databases and AliveCor's proprietary databases.<br>These validation datasets are representative of the patient<br>population of the proposed device. |
| 4. Human factors and usability testing must<br>demonstrate the following:<br>(a) The user can correctly use the device based<br>solely on reading the device labeling; and | Human factors evaluation was performed in accordance<br>with recommendations in IEC62366-1:2015 and FDA's<br>Guidance Document; Applying Human Factors and<br>Usability Engineering to Medical Devices: |
| (b) The user can correctly interpret the device<br>output and understand when to seek medical<br>care. | With respect to ECG acquisition, the proposed device uses the same hardware as the cleared KardiaMobile device (K182396 and prior clearances), which has a long history of real-world use. This real-world use data supports that representative users can record ECG of equivalent quality to 12-lead ECG. With respect to ECG display and analysis, AliveCor has conducted an additional human factors usability study which specifically evaluated whether users can safely and effectively use the proposed device to view ECG signals and their analysis. The study found that the user can correctly use the device solely based on on-screen guidance and the users understand the device output. The study also found that users understand |
| Special Control | Summary of Conformance |
| | when to seek care regardless of the output of the device. |
| Labeling must include:<br>(a) Hardware platform and operating system requirements<br>(b) Situations in which the device may not operate at an expected performance level<br>(c) A summary of the clinical performance testing conducted with the device; | Provided within applicable sections of the KardiaMobile Instructions for Use and User Manual documents. |
| (d) A description of what the device measures and outputs to the user; and<br>(e) Guidance on interpretation of any results. | Provided within on-screen instructions to the user within the software, as well as applicable sections of the KardiaMobile Instructions for Use and User Manual documents. |
{8}------------------------------------------------
Specifically to support the removal of "unlock overread," AliveCor has conducted software verification and validation testing in accordance to FDA's guidance titled, General Principles of Software Validation (January 11, 2002), which demonstrated that the minor software revisions to enable the change in the onboarding procedure is successfully implemented within the Kardia app. In addition, human factors usability testing was conducted to additionally confirm that representative users can use the device safely and effectively without supervision from a healthcare professional, and, furthermore, that the users understand when to seek medical help. This testing was performed in accordance with recommendations in FDA's Guidance Document titled, Applying Human Factors and Usability Engineering to Medical Devices (February 03, 2016), and IEC 62366-1:2015, Medical devices - Part 1: Application of usability engineering to medical devices.
The results of the collective testing demonstrated that the proposed KardiaMobile device is substantially equivalent to the predicate devices.
#### SUMMARY
AliveCor, Inc. considers the proposed KardiaMobile System device to be substantially equivalent to the legally marketed primary predicate KardiaMobile System (K182396) and the secondary predicate Apple Inc ECG App (DEN180044). Human factors usability testing, performed in agreement with recommendations in relevant FDA guidance documents and compliance standards, demonstrates that the removal of overread function brings the OTC use of the proposed device to be consistent with the secondary predicate device. The proposed KardiaMobile device is substantially equivalent to the predicate devices for its intended use.
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.