Retrospective clinical data from 71 hospitalized patients and volunteers
Retrospective analysis of clinical data was used to validate the accuracy of the Respiration Rate algorithm against gold-standard comparators (end-tidal CO2 and ventilator output) to support substantial equivalence.
The Respiration Rate algorithm is intended for measurement of respiration rate in patients in environments where health care is provided by clinicians.
Device Story
Algorithm processes beat-to-beat parameters of arterial blood pressure (ABP) signal; captures respiratory modulation of ABP to compute respiration rate in breaths per minute (BPM). Inputs: ABP signals from Edwards' non-invasive finger cuffs (ClearSight, Acumen IQ, VitaWave) or minimally invasive sensors (TruWave, FloTrac, Acumen IQ). Used in clinical environments; operated by clinicians. Output: continuous respiration rate displayed to healthcare provider. Assists in patient monitoring; provides clinical decision support for respiratory status. Benefits: non-invasive or minimally invasive continuous RR monitoring without requiring additional pulse-oximetry sensors.
Clinical Evidence
Retrospective analysis of 71 hospitalized patients and volunteers (spontaneous and mechanically ventilated) across 6 sites. Gold standard: blinded, manually-counted end-tidal CO2 waveforms (spontaneous) and ventilator output (ventilated). Simulated ABP data used to cover 4-40 BPM range. Results: RMSE ≤ 3 BPM, Bias/Mean Error ± 1 BPM, 95% CI of LoA within ± 3 BPM. Performance consistent across demographics (age, gender, BMI, skin pigmentation, comorbidities).
Technological Characteristics
Software-based algorithm; processes ABP signals from non-invasive finger cuffs or minimally invasive sensors. Range: 4-40 BPM. Accuracy: RMSE ≤ 3 BPM, Bias ± 1 BPM. Connectivity: integrates with monitoring platforms. Software lifecycle: IEC 62304 compliant. Cybersecurity: includes architecture decomposition, threat analysis, SCA/SAST reports, and penetration testing.
Indications for Use
Indicated for continuous measurement of respiration rate in patients over 18 years of age using compatible non-invasive blood pressure finger cuffs or compatible minimally invasive blood pressure sensors during no motion conditions in environments where health care is provided by clinicians.
Regulatory Classification
Identification
A breathing (ventilatory) frequency monitor is a device intended to measure or monitor a patient's respiratory rate. The device may provide an audible or visible alarm when the respiratory rate, averaged over time, is outside operator settable alarm limits. This device does not include the apnea monitor classified in § 868.2377.
{0}
**FDA** **U.S. FOOD & DRUG**
ADMINISTRATION
June 11, 2026
Edwards Lifesciences, LLC
Manthan Damani
Senior Manager, Regulatory Affairs
One Edwards Way
Irvine, California 92614
Re: K251326
Trade/Device Name: Respiration Rate algorithm
Regulation Number: 21 CFR 868.2375
Regulation Name: Breathing Frequency Monitor
Regulatory Class: Class II
Product Code: BZQ
Dated: May 8, 2026
Received: May 8, 2026
Dear Manthan Damani:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled 'Deciding When to Submit a 510(k) for a Change to an Existing Device'
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K251326 - Manthan Damani
Page 2
(https://www.fda.gov/media/99812/download) and 'Deciding When to Submit a 510(k) for a Software Change to an Existing Device' (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ('UDI Rule'). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, 'Misbranding by reference to premarket notification' (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
{2}
K251326 - Manthan Damani
Page 3
Sincerely,
Binoy J.
Mathews -S
Digitally signed by
Binoy J. Mathews -S
Date: 2026.06.11
10:51:39 -04'00'
For
Rachana Visaria, Ph.D.
Assistant Director
DHT1C: Division of Anesthesia,
Respiratory, and Sleep Devices
OHT1: Office of Ophthalmic, Anesthesia,
Respiratory, ENT, and Dental Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
# Indications for Use
510(k) Number (if known)
K251326
Device Name
Respiration Rate (RR) algorithm
Indications for Use (Describe)
The Respiration Rate algorithm is indicated for continuous measurement of respiration rate in patients over 18 years of age using compatible non-invasive blood pressure finger cuffs or compatible minimally invasive blood pressure sensors during no motion conditions in environments where health care is provided by clinicians.
Type of Use (Select one or both, as applicable)
☑ 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."
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740 EF
{4}
K251326
# **510(k) Summary – Respiration Rate (RR) Algorithm**
**Sponsor:** Edwards Lifesciences, LLC
One Edwards Way
Irvine, CA 92614
**Establishment
Registration
Number:** 2015691
**Contact Person:** Manthan Damani
Senior Manager, Regulatory Affairs
One Edwards Way
Irvine, CA 92614
Phone: 949-628-0406
manthan.damani@bd.com
**Date:** June 5, 2026
**Trade Name:** Respiration Rate (RR) algorithm
**Regulation Name/
Number:** Breathing frequency monitor 21 CFR 868.2375
**Product Code:** BZQ, Class II
**Primary Predicate:** Covidien Nellcor Respiration Rate Software Application, K111933
(Breathing Frequency Monitor, 21 CFR 868.2375, BZQ, Class II)
**Reference Device:** HemoSphere Advanced Monitoring Platform, K223865 (Programmable
Diagnostic Computer, 21 CFR 870.1425, DQK, Class II)
{5}
K251326
**Device Description:**
The Respiration Rate (RR) algorithm is intended for continuous measurement of respiration rate in patients in environments where health care is provided by clinicians.
The Respiration Rate (RR) algorithm captures the respiratory modulation of the Arterial Blood Pressure (ABP) signal by processing specific beat-to-beat parameters of the ABP signal from which RR is then computed. The Respiration Rate (RR) algorithm quantifies respiration rate in breaths per minute (BPM) based on the ABP signal acquired from existing previously cleared Edwards' non-invasive blood pressure finger cuff: ClearSight™, Acumen IQ™, and VitaWave™, or minimally invasive blood pressure sensor: TruWave™, FloTrac™, and Acumen IQ™.
**Indications for Use:**
The Respiration Rate algorithm is indicated for continuous measurement of respiration rate in patients over 18 years of age using compatible non-invasive blood pressure finger cuffs or compatible minimally invasive blood pressure sensors during no motion conditions in environments where health care is provided by clinicians.
**Comparison to Predicate Device:**
The subject device and the primary predicate device, have the following key similarities:
- Both devices have similar intended use and indication for use for continuous measurement of respiration rate.
- Both devices have the same performance accuracy as it relates to measurement of respiration rate.
The subject device and the primary predicate, have the following key differences:
- Subject device technology is based on measurement of Respiration Rate using arterial blood pressure signal, while the primary predicate technology is based on measurement of Respiration Rate (RR) using photoplethysmography/ pulse-oximetry. However, the arterial blood pressure signal, indicating the pulsatile pressure in the blood vessel, and the photoplethysmography signal, indicating the changes of volume of the vessel as a result of the pulsating pressure in the vessel, are physiologically closely related. As such, Respiration Rate derived from either the arterial blood pressure signal or the photoplethysmography signal are very similar.
- The subject device utilizes the reference device, HemoSphere Advanced Monitoring Platform (K223865, cleared June 9, 2023) as support for the difference in technology used between the subject (arterial blood pressure signal acquired using existing non-invasive blood pressure finger cuffs, or
{6}
K251326
existing minimally invasive blood pressure sensors) and primary predicate device (pulse-oximetry based signal acquired using pulse-oximetry sensor).
The HemoSphere Advanced Monitoring Platform when used in conjunction with compatible non-invasive blood pressure finger cuffs (ClearSight™, Acumen IQ™, and VitaWave™) or with compatible minimally invasive blood pressure sensors (TruWave™, FloTrac™, and Acumen IQ™), is used to generate arterial blood pressure signals as part of the APCO (Arterial Pressure-based Cardiac Output) algorithm.
The subject respiration rate algorithm utilizes these APCO blood pressure signals as input to calculate the respiration rate. As such, the subject algorithm utilizes the same existing non-invasive blood pressure finger cuff and minimally invasive blood pressure sensor technology as well as the existing APCO algorithm as the HemoSphere Advanced Monitoring Platform for measurement of respiration rate. Successful performance testing results show no new or different concerns of safety and effectiveness for the measurement of Respiration Rate for the subject device which utilizes arterial blood pressure signal technology, and that the subject device performs as intended.
{7}
K251326
**Table 1** provides a comparison of the applicable features and specifications for the subject device, primary predicate device (Covidien Nellcor Respiration Rate Software Application, v1.0), and reference device (HemoSphere Advanced Monitoring Platform).
**Table 1.**
| Features | Subject Device (Respiration Rate algorithm) | Primary Predicate Device (Covidien Nellcor Respiration Rate Software Application, v1.0) | Substantial Equivalence |
| --- | --- | --- | --- |
| Name | Respiration Rate algorithm | Covidien Nellcor Respiration Rate Software Application, v1.0 | N/A |
| 510(k) | K251326 | K111933 (Cleared March 15, 2012) | N/A |
| FDA Product Code, Regulation Number | **BZQ, 21 CFR 868.2375** | **BZQ, 21 CFR 868.2375** DQA, 21 CFR 870.2700 DSA, 21 CFR 870.2900 | **SAME as the primary predicate device** |
| Device Classification | Class II | Class II | **SAME as the primary predicate** |
| Manufacturer | Edwards Lifesciences LLC One Edwards Way, Irvine, CA 92614 | Covidien 6135 Gunbarrel Ave, Boulder, CO 80301 | N/A |
| Intended Use | The Respiration Rate algorithm is **intended for measurement of respiration rate in patients** in environments where health care is provided by clinicians. | The Covidien Nellcor Respiration Rate Software Application, v1.0 is **intended for measurement of respiration rate in patients** in hospitals and hospital-type facilities. | **SAME** intended use as the primary predicate device (RR measurement) and **SIMILAR** use environments. |
| Indications for use | The Respiration Rate algorithm is **indicated for continuous measurement of respiration rate in patients over 18 years of age** using compatible non-invasive blood pressure finger cuffs or compatible minimally invasive blood pressure sensors during no motion conditions in environments where health care is provided by clinicians. | The Covidien Nellcor Respiration Rate Software, when used in conjunction with a Nellcor pulse oximeter and a Nellcor Respiration Rate Sensor, is **intended to be used for the continuous, non-invasive monitoring of respiration rate in adults** in hospitals and hospital-type facilities. | **SIMILAR to the primary predicate device** |
| Intended Use Population | Patient population over 18 years of age | Adults | **SIMILAR to the primary predicate device. The Substantial Equivalence in patients between 18 and 21 was supported by clinical validation.** |
{8}
K251326
| Features | Subject Device (Respiration Rate algorithm) | Primary Predicate Device (Covidien Nellcor Respiration Rate Software Application, v1.0) | Substantial Equivalence |
| --- | --- | --- | --- |
| Respiration Rate parameters measured | RR (arterial blood-pressure signal based) | RR (plethysmogram based) | DIFFERENT. The subject device measures RR via arterial blood pressure signals previously cleared in the reference device K223865. Testing against the gold standard demonstrated equivalent accuracy in the subject device. |
| Respiration Rate Range (measured in Breaths Per Minute (BPM)) | 4- 40 BPM | 4- 40 BPM | SAME as the primary predicate device |
| Respiration Rate Accuracy | ARMS / RMSE ≤ 3 BPM, Bias / Mean Error within ± 1 BPM Bland-Altman LoA 95% CI within ± 3 bpm | RMSD < 3 BPM, Mean Error of ± 1 BPM | SAME as the primary predicate device |
| Mode of Operation | Non-invasive, continuous measurements using compatible non-invasive blood pressure finger cuffs (ClearSight, Acumen IQ, VitaWave). Minimally invasive, continuous measurements using compatible minimally invasive blood pressure sensors (TruWave, FloTrac, Acumen IQ). | Non-invasive, continuous measurements using pulse-oximetry sensors | SAME as the primary predicate |
| Principle/ Method of Operation | Respiration Rate algorithm calculates Respiration Rate from arterial blood pressure signal obtained using compatible non-invasive blood pressure finger cuff sensors (ClearSight, Acumen IQ, VitaWave) or compatible minimally invasive blood pressure sensors (TruWave, FloTrac, Acumen IQ). | Respiration Rate calculated using photoplethysmography waveform obtained using compatible sensors. | DIFFERENT. The subject device has the same principle of operation (arterial blood pressure signal) previously cleared in reference device K223865. This does not raise new questions of safety and effectiveness. |
| Type of Sensor used | Non-invasive blood pressure finger cuffs (ClearSight, Acumen IQ, VitaWave). Minimally invasive blood pressure sensors (TruWave, FloTrac, Acumen IQ). | Non-invasive pulse oximetry sensor | DIFFERENT. The subject device has the same principle of operation (arterial blood pressure signal) previously cleared in reference device K223865. Testing against the gold standard demonstrated equivalent accuracy in the |
{9}
K251326
| Features | Subject Device (Respiration Rate algorithm) | Primary Predicate Device (Covidien Nellcor Respiration Rate Software Application, v1.0) | Substantial Equivalence |
| --- | --- | --- | --- |
| | | | subject device. This does not raise new questions of safety and effectiveness. |
### Performance Data (Bench and/or Clinical)
The following verification activities were performed for ensuring the safety and effectiveness of the subject Respiration Rate algorithm and to support substantial equivalence of the Respiration Rate algorithm to its primary predicate, Covidien Nellcor Respiration Rate Software Application v1.0, to the additional predicate, HemoSphere Advanced Monitoring Platform, and to reference data from: Capnostream 35 Portable Respiratory Monitor, Intellivue MX 750 with Microstream CO2 Extension, Aisys CS2, Primus US Apollo.
### Software Verification and Validation Testing
Software verification and validation was performed per IEC 62304, Medical Device Software - Software Life Cycle Processes, ISO 14971, Medical devices- Application of risk management to medical devices, and FDA's Guidance Document for Industry and FDA Staff on 'Content of Premarket Submissions for Device Software Functions' (issued June 14, 2023). The Respiration Rate algorithm was tested at the algorithm level to ensure the safety of the device. All tests passed.
Cybersecurity documentation and testing were performed for the Respiration Rate algorithm to address cybersecurity requirements in accordance with FDA Guidance Document 'Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions' (issued February 3, 2026). Cybersecurity documentation included cybersecurity architecture decomposition, cybersecurity threat analysis, cybersecurity requirements, cybersecurity controls, cybersecurity management plan, cybersecurity risk analysis, cybersecurity Software Bill of Materials, security SCA and SAST reports. Cybersecurity testing included security testing of software requirements, vulnerability assessment, third-party penetration testing, verification of control effectiveness. All cybersecurity risks were mitigated to an acceptable risk level based on the cybersecurity risk assessment.
### Clinical Performance Testing
Retrospective analyses were performed on human data collected from randomly selected 71 hospitalized patients and volunteers, under spontaneous breathing (breathing without any external mechanical support) and mechanically ventilated (breathing using a mechanical ventilator) across 6 US and EU sites, independent of the device development. Respiratory rate was derived from compatible, FDA-cleared non-invasive blood pressure finger cuffs and minimally invasive blood pressure sensors. The accepted gold standard - blinded, manually-counted end-tidal CO2
{10}
K251326
waveforms - was used for spontaneously breathing patients. Ventilator output was used as the gold standard comparator for ventilated patients. Simulated ABP data was performed to bridge the gap and cover the entire claimed RR range (4-40 bpm).
Accuracy of the Respiration Rate (RR) algorithm was calculated using the ground truth and Bland-Altman Analysis. The 95% Confidence Interval (CI) of the Limits of Agreement (LoA) was within ± 3 bpm. Additionally, the results demonstrated the subject device met acceptance criteria of ARMS / RMSE ≤ 3 BPM and Bias / Mean Error within ± 1 BPM (which is the same accuracy as that of the primary predicate) and performed equally well across the intended use population for different demographic factors (race, ethnicity, age, gender, BMI, skin pigmentation, comorbidities) and sites, thereby showing substantial equivalence to the predicate.
Algorithm performance testing for the subject Respiration Rate algorithm also included verification of RR algorithm specifications, RR algorithm code review, and RR algorithm software GUI display and integration on a laptop.
## Conclusion
The subject Respiration Rate (RR) algorithm has successfully passed functional and performance testing, including software and algorithm verification and validation. Completion of all performance verification and validation activities demonstrated that the subject device meets its predetermined design and performance specifications. Verification activities performed confirmed that the differences in the features did not adversely affect the safety and effectiveness of the subject device, and that the subject device performs as intended. The testing performed demonstrates that the Respiration Rate (RR) algorithm is substantially equivalent to its legally marketed 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.