K241217 · Inmedix, Inc. · DPS · Jan 16, 2025 · Cardiovascular
Device Facts
Record ID
K241217
Device Name
CloudHRV™ System (100-01-001)
Applicant
Inmedix, Inc.
Product Code
DPS · Cardiovascular
Decision Date
Jan 16, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2340
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV). These measurements are not intended for any specific clinical diagnosis. The clinical significance of HRV must be determined by the physician.
Device Story
CloudHRV™ System acquires ~5 minutes of 3-lead ECG data via four electrodes on wrists/ankles; transmits raw signals to Inmedix cloud service. Proprietary algorithms calculate HRV indices (time-domain, geometric, frequency-domain). Output displayed on tablet for clinician use as aid in medical assessment. Used in physician offices/outpatient clinics; operated by healthcare staff. Clinicians interpret HRV data to inform medical decision-making; device does not provide diagnostic assessments of cardiovascular conditions or arrhythmias.
Clinical Evidence
Bench testing only. No clinical data provided. Verification and validation included design review against product requirements, human factors/usability engineering, and adherence to IEC/ANSI/AAMI standards (e.g., IEC 60601-1, IEC 60601-2-25, ANSI/AAMI EC57).
Technological Characteristics
3-lead ECG acquisition; 500 samples/sec; 16-bit bipolar resolution; 0.5-113 Hz frequency response. 4-lead wire assembly with 4 electrodes. Connectivity: Cloud-based processing via Inmedix service. Power: 100-240 VAC, 50-60 Hz; Lithium-ion battery. Class II, Type CF device. Standards: IEC 60601-1, IEC 60601-1-2, IEC 60601-2-25, IEC 62304, ANSI/AAMI EC57, ANSI/AAMI EC53.
Indications for Use
Indicated for adult patients (age 22+) with normal sinus rhythm and resting heart rate 40-110 bpm. Used in healthcare facilities (physician office/outpatient clinic) where patient remains supine and still. Not for surgical suites or transport. Not for diagnosing/monitoring cardiovascular conditions or assessing arrhythmias.
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.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo is a blue square with the letters "FDA" in white, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue.
January 16, 2025
Inmedix. Inc. % Michael Daniel Consultant Daniel & Daniel Consulting, LLC P.O. Box 129 Minden, Nevada 89423
Re: K241217
Trade/Device Name: CloudHRVTM System (100-01-001) Regulation Number: 21 CFR 870.2340 Regulation Name: Electrocardiograph Regulatory Class: Class II Product Code: DPS Dated: December 20, 2024 Received: December 20, 2024
Dear Michael Daniel:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{1}------------------------------------------------
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (OS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-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 Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-device-advicecomprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/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-regulatory
{2}------------------------------------------------
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
# Jennifer W. Shih -S
Jennifer Kozen Assistant Director Division of Cardiac Electrophysiology, Diagnostics, and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
# Indications for Use
510(k) Number (if known) K241217
Device Name CloudHRVTM System
#### Indications for Use (Describe)
The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV) in adult patients (age 22 or above) with normal sinus rhythm and resting heart rate within 40 - 110 bpm. These measurements are not intended for any specific clinical significance of HRV must be determined by the physician.
Assessment is indicated for patients in a healtheare facility including a physician office or a hospital outpatient clinic where the patient is able to remain supine and still. The CloudHRV™ System is not indicated for use in a surgical suite or during transport.
Normal sinus rhythm is determined by the physician. The ECG is not intended to be used to diagnose or monitor cardiovascular conditions. The device does not provide assessments of cardiovascular abnormalities/arthythmias.
| 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."
{4}------------------------------------------------
# Premarket Notification 510(k) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirements of SMDA 1990 and 21 CFR 807.92.
## 510(k) Number: K241217
# Applicant Information:
| Date Prepared: | April 29, 2024 |
|----------------|--------------------------------------------------------------------------------|
| Name: | Andrew Holman MD |
| Address: | Inmedix, Inc.<br>17837 First Avenue South, #6,<br>Normandy Park, WA 98148, USA |
| Contact Person: | Michael A. Daniel |
|-----------------|-------------------|
|-----------------|-------------------|
Email: madaniel@clinregconsult.com
# Device Information:
| Device Trade Name: CloudHRV™ System | |
|-------------------------------------|--------------------|
| Common Name: | CloudHRV™ System |
| Classification Name(s): | Electrocardiograph |
| Product Code/ Regulation: | DPS / 870.2340 |
Classification: 2
# Predicate Device:
ANSiscope™ ECG Monitoring System (K071168)
### Subject Device Description
The Inmedix® CloudHRV™ System acquires approximately 5 minutes of 3-lead electrocardioaraphic (ECG) data from a patient lying supine and at rest to measure heart rate variability (HRV). The raw cardiac electrical signals are detected using four standard ECG electrodes applied to the wrists and ankles of the patient and a custom 4-lead wire (one reference) ECG cable assembly.
The ECG data collected from the patient are transmitted to a cloud-based service hosted by Inmedix. where proprietary mathematical algorithms calculate HRV. The CloudHRV™ System outputs are used as an aid by clinicians who are accustomed to evaluating HRV as a part of their overall medical assessment.
{5}------------------------------------------------
# Subject Device Intended Use
The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV). These measurements are not intended for any specific clinical diagnosis. The clinical significance of HRV must be determined by the physician.
#### Subject Device Indications for Use
The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV) in adult patients (age 22 or above) with normal sinus rhythm and resting heart rate within 40 - 110 bpm. These measurements are not intended for any specific clinical diagnosis. The clinical significance of HRV must be determined by the physician.
Assessment is indicated for patients in a healthcare facility including a physician office or a hospital outpatient clinic where the patient is able to remain supine and still. The CloudHRV™ System is not indicated for use in a surgical suite or during transport.
Normal sinus rhythm is determined by the physician. The ECG is not intended to be used to diagnose or monitor cardiovascular conditions. The device does not provide assessments of cardiovascular abnormalities/arrhvthmias.
#### Predicate Device and Subject Device Comparison
The table below compares the CloudHRV to the predicate device.
| Aspect | Predicate Device | Subject Device | Comparison |
|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|
| Device Name | ANSiscope™ ECG Monitoring System | CloudHRV™ System | N/A |
| 510(k) Number | K071168 | K241217 | N/A |
| Manufacturer | DyAnsys, Inc. | Inmedix, Inc. | N/A |
| Product Code / Regulation | DPS / 870.2340 | DPS / 870.2340 | Same |
| Brief Description | The Portable ANSiscope™ is a device used for measuring heart rate variability (HRV). The device is designed to process raw ECG signals acquired from the patient in order to produce Heart Rate and other ancillary indices. The Portable ANSiscope™ includes an ECG Acquisition System that can digitize raw ECG signals, perform proprietary calculations from the HRV and then display the results utilizing a display unit. | The CloudHRV™ System is a device used for measuring heart rate variability (HRV). The device acquires ~5 minutes of 3-lead ECG data from a patient lying supine and at rest. ECG data is transmitted to a cloud-based service hosted by Inmedix, where proprietary mathematical algorithms calculate HRV and then display the results on the Tablet. The results are used as an aid by clinicians who are accustomed to evaluating HRV as a | Substantially Equivalent |
| Aspect | Predicate Device | Subject Device | Comparison |
| | | part of their overall medical<br>assessment. | |
| Intended Use | The DyAnsys, Inc. ANSiscope™ ECG Monitoring System and<br>accessories, is intended to acquire,<br>analyze, display and record<br>electrocardiographic information<br>and to measure-heart rate<br>variability. These and other<br>measurements are not intended for<br>any specific clinical diagnosis. The<br>clinical significance of HRV and<br>other parameters must be<br>determined by the physician. | The Inmedix® CloudHRV™ System<br>is intended to acquire, display, and<br>record electrocardiographic (ECG)<br>information to measure heart rate<br>variability (HRV). These<br>measurements are not intended for<br>any specific clinical diagnosis. The<br>clinical significance of HRV must be<br>determined by the physician. | Substantially<br>Equivalent |
| Indications for Use | The DyAnsys, Inc. ANSiscope™ ECG Monitoring System and<br>accessories, is intended to acquire,<br>analyze, display and record<br>electrocardiographic information<br>and to measure-heart rate<br>variability. These and other<br>measurements are not intended for<br>any specific clinical diagnosis. The<br>clinical significance of HRV and<br>other parameters must be<br>determined by the physician. | The Inmedix® CloudHRV™ System<br>is intended to acquire, display, and<br>record electrocardiographic (ECG)<br>information to measure heart rate<br>variability (HRV) in adult patients<br>(age 22 or above) with normal sinus<br>rhythm and resting heart rate within<br>40 - 110 bpm. These<br>measurements are not intended for<br>any specific clinical diagnosis. The<br>clinical significance of HRV must be<br>determined by the physician.<br>Assessment is indicated for patients<br>in a healthcare facility including a<br>physician office or a hospital<br>outpatient clinic where the patient is<br>able to remain supine and still. The<br>CloudHRV™ System is not<br>indicated for use in a surgical suite<br>or during transport.<br>Normal sinus rhythm is determined<br>by the physician. The ECG is not<br>intended to be used to diagnose or<br>monitor cardiovascular conditions.<br>The device does not provide<br>assessments of cardiovascular<br>abnormalities/arrhythmias. | Substantially<br>Equivalent |
| Displayed<br>Parameters - ECG<br>related | • Real-time ECG waveform<br>• Real-time heart rate<br>• ECG lead selection | • Real-time ECG waveform during<br>assessment | Substantially<br>Equivalent |
| Aspect | Predicate Device | Subject Device | Comparison |
| Displayed<br>Parameters – HRV<br>related | • Real-time sympathovagal balANS<br>(from -50 to 50) | • Statistical Time-Domain Indices:<br>SDNN, SDSD, RMSSD | Substantially<br>Equivalent |
| | • Real-time sympathetic ANSi index<br>(from -50 to 50) | • Geometric Time-Domain Indices:<br>DRR, AMO, Baevsky Index | |
| | • Real-time parasympathetic ANSi<br>index (from -50 to 50) | • Frequency Domain Indices: High<br>Frequency, Low Frequency, Total<br>power, LF/HF ratio | |
| | • Measurement of Dysfunction:<br>Static balANS, Percent of<br>dysfunction | | |
| Type of Analysis | Separation of sympathetic and<br>parasympathetic components of the<br>Autonomic Nervous System (ANS)<br>by scale covariance approach<br>Sympathetic response is real part of<br>complex wave function<br>Parasympathetic response is<br>imaginary part of complex wave<br>function | HRV indices calculated using ~5<br>minutes of RR interval series with<br>signal normalized and artifacts<br>removed. | Substantially<br>Equivalent |
| Number of<br>Electrodes | Three (3) for HRV<br>One (1) for grounding<br>Chest lead for ECG functionality | Three (3) for vectors I, II, III<br>One (1) for grounding (right leg<br>drive) | Substantially<br>Equivalent |
| Electrode location | Chest lead, torso, right ankle. | Left and right wrists, left and right<br>ankles | Substantially<br>Equivalent |
| Measurement | The initial ANSindex reading is<br>displayed after 60 R-R intervals<br>(approx 1 minute)<br>Subsequent readings are taken with<br>every heartbeat<br>The display is updated with every<br>heartbeat | Records five (5) minutes of ECG to<br>calculate all indices | Substantially<br>Equivalent |
| Standard leads<br>acquired | I, II, III, aVR, aVL, aVF, V1-6 | I,II,III | Substantially<br>Equivalent |
| Aspect | Predicate Device | Subject Device | Comparison |
| Digital sampling<br>rate | 200 samples/sec | 500 samples/sec | Substantially<br>Equivalent |
| DC offset capability | 300 mV DC | 280 mV DC | Substantially<br>Equivalent |
| Sampling<br>resolution | 16 bit, bipolar | 16 bit, bipolar | Same |
| Frequency<br>response | 0.5 Hz to 40 Hz | 0.5 Hz to 113 Hz | Substantially<br>Equivalent |
| Data Storage<br>Capability | · USB memory keys (Thumb drives)<br>can be used for data<br>storage/backup<br>· Also supports SCSI compatible<br>USB mass storage devices<br>· Data can be exported to a PC via<br>a USB memory key | Patient Health Information and<br>patient indices are stored in the<br>secure Inmedix Cloud. Data can be<br>made available as a PDF | Substantially<br>Equivalent |
| Electrical Safety<br>Classification | Class II - Type CF device as per<br>IEC requirements | Class II - Type CF device as per<br>IEC requirements | Same |
| AC adapter input | 100-240 VAC, 50-60 Hz | 100-240 VAC, 50-60 Hz | Same |
| AC adapter output | 12 VDC, 2 Amps max | 12 VDC, 2 Amps max | Same |
| Battery pack type | NiMH rechargeable battery | Lithium-ion | Substantially<br>Equivalent |
Table 1 - Comparison between subject and predicate device
{6}------------------------------------------------
{7}------------------------------------------------
{8}------------------------------------------------
# Testing Completed
Design verification testing included use of the following standards:
- IEC 60601-1: 2005+A1:2012+A2:2020 Medical equipment Part 1: General . requirements for basic safety and essential performance
- . IEC 60601-1-2:2014+A1:2020 Medical electrical equipment - Part 1-2: General requirements for basic safety and essential performance - Collateral Standard: Electromagnetic disturbances -Requirements and tests
- IEC 60601-2-25:2011/(R2016) Medical electrical equipment Part 2-25: Particular requirements . for the basic safety and essential performance of electrocardiographs
- IEC 60601-1-6:2010+AMD1:2013+AMD2:2020 Medical Electrical Equipment Part 1-6: General . requirements for basic safety and essential performance - Collateral standard: Usability
{9}------------------------------------------------
- . IEC 62366-1:2015, AMD1:2020 Medical devices -- Part 1: Application of usability engineering to medical devices
- . ANSI/AAMI EC57:2012 Testing and reporting performance results of cardiac rhythm and STsegment measurement algorithms.
- ANSI/AAMI EC53:2013/(R2020) ECG trunk cables and patient leadwires ●
- ASTM D4169-22 - Standard practice for performance testing of shipping containers and systems.
- . IEC 62304:2006 +AMD1:2015 Medical device software - Software life-cycle processes
Adherance to the following FDA Guidance Documents:
- . FDA Guidance - Content of Premarket Submissions for Device Software Functions. Issued June 14. 2023.
- FDA Guidance - Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions. Issued September 27, 2023.
Design validation testing included the following:
- . Design Validation by Design Review against the Product Requirements (User and Stakeholder Requirements)
- . Human Factors and Usability Engineering Report
The testing described in this 510(k) demonstrates that the design input requirements have been verified and all user requirements were validated.
### Conclusion
Verification and validation activities were conducted to establish the performance and safety characteristics of the Inmedix CloudHRV™ System. The results of these activities demonstrate that the CloudHRV™ System is as safe and effective as compared to the predicate when used in accordance with its intended use, indications for use and labeling. The CloudHRV™ System has similar intended use and technical characteristics to the predicate device. Therefore, it is substantially equivalent to the predicate device and does not raise any new questions regarding safety or effectiveness as compared to the predicate.
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.