K250135 · Baxter Healthcare Corp/ Excel Medical · MWI · Jan 16, 2026 · Cardiovascular
Device Facts
Record ID
K250135
Device Name
WAVE Clinical Platform (2.0.000)
Applicant
Baxter Healthcare Corp/ Excel Medical
Product Code
MWI · Cardiovascular
Decision Date
Jan 16, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The WAVE Clinical Platform is software intended to route, store, and display data, alarms, results and diagnostic information from medical devices, Electronic Medical Records (EMR), and Clinical Information Systems (CIS). The WAVE Clinical Platform is a remote monitoring platform that displays physiological data, waveforms, alarms, results, diagnostic and operational information routed through the platform from devices and systems using supported protocols. The WAVE Clinical Platform is intended for use in hospital and hospital type environments or where clinical consultations are needed. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes: - To remotely consult regarding patients’ conditions and statuses; - To remotely review other standard or critical patient and operational data, waveforms, alarms, and results to utilize this information to aid in clinical decisions. Warning: The WAVE Clinical Platform is intended to supplement and not replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms.
Device Story
WAVE Clinical Platform is a remote monitoring software system; routes, stores, and displays physiological data, waveforms, alarms, and diagnostic results from connected medical devices (e.g., patient monitors, ventilators, infusion pumps), EMRs, and CIS. Operates on hospital networks using web-enabled devices; does not control connected medical devices. Used by healthcare professionals in hospital environments for remote patient consultation and review of critical data. Output serves as secondary means of annunciating patient events; aids clinical decision-making by providing centralized access to patient status. Intended to supplement, not replace, primary hospital monitoring or data management systems.
Clinical Evidence
No clinical data. Substantial equivalence established via bench testing, including system-level functional performance testing, safety testing based on hazard analysis, and software verification and validation.
Technological Characteristics
Software-based remote monitoring platform; utilizes standard hospital computers, network, and Wi-Fi infrastructure. Compatible with off-the-shelf operating systems. Complies with ISO 14971 (risk management), IEC 62366-1 (usability), and IEC 60601-1-8 (alarm systems).
Indications for Use
Indicated for in-hospital patients with physiological sensors attached. Used by healthcare professionals to remotely consult on patient status and review patient/operational data, waveforms, and alarms to aid clinical decision-making.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
January 16, 2026
Baxter Healthcare Corp./Excel Medical
Gena Wolfe
Manager, Regulatory Affairs
7111 Fairway Dr. Suite 205
Palm Beach Gardens, Florida 33418
Re: K250135
Trade/Device Name: WAVE Clinical Platform (2.0.000)
Regulation Number: 21 CFR 870.2300
Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm)
Regulatory Class: Class II
Product Code: MWI
Dated: January 9, 2026
Received: January 14, 2026
Dear Gena Wolfe:
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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K250135 - Gena Wolfe
Page 2
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 (QS) 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 (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 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-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.
{2}
K250135 - Gena Wolfe
Page 3
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).
Sincerely,
**STEPHEN C. BROWNING -S**
LCDR Stephen Browning
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}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
K250135
Device Name
WAVE Clinical Platform (2.0.000)
Indications for Use (Describe)
The WAVE Clinical Platform is software intended to route, store, and display data, alarms, results and diagnostic information from medical devices, Electronic Medical Records (EMR), and Clinical Information Systems (CIS). The WAVE Clinical Platform is a remote monitoring platform that displays physiological data, waveforms, alarms, results, diagnostic and operational information routed through the platform from devices and systems using supported protocols. The WAVE Clinical Platform is intended for use in hospital and hospital type environments or where clinical consultations are needed. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
- To remotely consult regarding patients’ conditions and statuses;
- To remotely review other standard or critical patient and operational data, waveforms, alarms, and results to utilize this information to aid in clinical decisions.
Warning: The WAVE Clinical Platform is intended to supplement and not replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms.
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.”
{4}
Baxter
# 510(k) Summary
January 6, 2026
## OWNER:
Baxter Healthcare Corporation
One Baxter Parkway
Deerfield, Illinois 60015
## CONTACT PERSON:
Gena Wolfe
Manager, Regulatory Affairs
Care and Connectivity Solutions Division
Baxter Healthcare Corporation/Excel Medical
7111 Fairway Drive, Suite 205
Palm Beach Gardens, FL 33418
Telephone: (816) 863-3370
## IDENTIFICATION OF THE DEVICE:
Common Name: "WAVE Clinical Platform; Data Management, Visualization and
Clinical Decision Support Software"
Trade/Device Name: "WAVE Clinical Platform"
Classification Panel: Cardiovascular
Regulation Number: 21 CFR 870.2300
Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm)
Regulatory Class: Class II
Product Code: MWI
Table 1. Version Number(s) for WAVE Clinical Platform
| Version Number | Name | Proposed Device 510k |
| --- | --- | --- |
| 2.0.000 | WAVE Clinical Platform | K250135 |
K250135
{5}
Baxter
# PREDICATE DEVICE:
Table 2. Predicate Device(s)
| Device | Company | Predicate 510(k) | Clearance Date |
| --- | --- | --- | --- |
| Version 1.0 WAVE Clinical Platform | EXCEL Medical | K171056 | January 2018 |
# DESCRIPTION OF THE DEVICE:
The WAVE Clinical Platform is a remote monitoring platform that displays physiological data, waveforms, alarms, results, diagnostic and operational information routed through the platform from devices and systems using supported protocols. The WAVE Clinical Platform can also route and forward this data to third party systems.
The WAVE Clinical Platform can utilize the hospital's existing network and hardware for installation and display on any device that is web-enabled. The WAVE Clinical Platform does not control any of the medical devices or systems it is connected with.
Medical devices and information systems are the predominant sources of data used in the WAVE applications. Data sources such as multi-parameter patient monitors, telemetry transmitters, vital sign monitors, ventilators, anesthesia machines, oximeters, hemodynamic monitors, oxygen saturation monitors, capnography monitors, sedation monitors, nurse call systems, smartphone mobile applications, smart beds, precision locating systems, cameras, variability indexes, hospital information systems, clinical information systems, electronic medical record systems, lab information systems, order systems, fluid delivery systems, medication delivery systems, infusion systems, clinical deterioration algorithm derivatives, gateway servers, etc. provide digital outputs acquired by WAVE and by Medical Device Data Systems that then transfer the data to WAVE.
# INTENDED USE:
The WAVE Clinical Platform is software intended to route, store, and display data, alarms, results and diagnostic information from medical devices, Electronic Medical Records (EMR), and Clinical Information Systems (CIS). The WAVE Clinical Platform is a remote monitoring platform that displays physiological data, waveforms, alarms, results, diagnostic and operational information routed through the platform from devices and systems using supported protocols. The WAVE Clinical Platform is intended for use in hospital and hospital type environments or where clinical consultations are needed. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
- To remotely consult regarding patients' conditions and statuses;
- To remotely review other standard or critical patient and operational data, waveforms, alarms, and results to utilize this information to aid in clinical decisions.
Warning: The WAVE Clinical Platform is intended to supplement and not replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms.
K250135
{6}
Baxter
Table 3. Device Comparison
| Features | Primary Predicate Device
Wave Clinical Platform cleared under K171056 | Proposed Device
WAVE Clinical Platform 2.0
K250135 | Assessment of Differences |
| --- | --- | --- | --- |
| Intended Use | The WAVE Clinical Platform is software intended to route, store, and display data, alarms, results and diagnostic information from medical devices, Electronic Medical Records (EMR), and Clinical Information Systems (CIS). The WAVE Clinical Platform is a remote monitoring platform that displays physiologic data, waveforms, alarms, results and diagnostic information routed through the platform from supported devices and systems. The WAVE Clinical Platform is intended for use in hospital or hospital type environments. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
• To remotely consult regarding patients’ statuses;
• To remotely review other standard or critical near real-time patient data, waveforms, alarms, and results in order to utilize this information to aid in clinical decisions.
Warning: The WAVE Clinical Platform is intended to supplement and not replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms. | The WAVE Clinical Platform is software intended to route, store, and display data, alarms, results and diagnostic information from medical devices, Electronic Medical Records (EMR), and Clinical Information Systems (CIS). The WAVE Clinical Platform is a remote monitoring platform that displays physiological data, waveforms, alarms, results, diagnostic and operational information routed through the platform from devices and systems using supported protocols. The WAVE Clinical Platform is intended for use in hospital and hospital type environments or where clinical consultations are needed. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
• To remotely consult regarding patients’ conditions and statuses;
• To remotely review other standard or critical patient and operational data, waveforms, alarms, and results to utilize this information to aid in clinical decisions
Warning: The WAVE Clinical Platform is intended to supplement and not replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms. | Same |
K250135
{7}
Baxter
Table 3. Device Comparison
| Features | Primary Predicate Device
Wave Clinical Platform cleared under K171056 | Proposed Device
WAVE Clinical Platform 2.0
K250135 | Assessment of Differences |
| --- | --- | --- | --- |
| Indications for Use | The WAVE Clinical Platform is a remote monitoring platform that displays physiologic data, waveforms, alarms, results and diagnostic information routed through the WAVE Clinical Platform from supported devices and systems. The WAVE Clinical Platform is intended for use in hospital or hospital type environments. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
- To remotely consult regarding patients’ statuses;
- To remotely review other standard or critical **near real-time** patient data, waveforms, alarms, and results in order to utilize this information to aid in clinical decisions.
Warning: The WAVE Clinical Platform is intended to supplement and not to replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms. | The WAVE Clinical Platform is a remote monitoring platform that displays physiologic data, waveforms, alarms, results and diagnostic information routed through the WAVE Clinical Platform from supported devices and systems. The WAVE Clinical Platform is intended for use in hospital or hospital type environments. The WAVE Clinical Platform is intended to be used by healthcare professionals for the following purposes:
- To remotely consult regarding patients’ conditions and statuses;
- To remotely review other standard or critical patient data, waveforms, alarms, and results in order to utilize this information to aid in clinical decisions.
Warning: The WAVE Clinical Platform is intended to supplement and not to replace any part of the hospital's device monitoring or electronic data management systems. Do not rely on the WAVE Clinical Platform product as the sole source of alarms. | Primary predicate stated “near real-time patient data”. This terminology was removed from proposed device submission at request of FDA reviewer. |
K250135
{8}
Baxter
Table 3. Device Comparison
| Features | Primary Predicate Device
Wave Clinical Platform cleared under K171056 | Proposed Device
WAVE Clinical Platform 2.0 K250135 | Assessment of Differences |
| --- | --- | --- | --- |
| Sterile | N/A; software | N/A; software | N/A; software |
| Non-Pyrogenic | N/A; software | N/A; software | N/A; software |
| Single Use | Yes | Yes | Same |
| Materials (List components in this column which are relevant to the type of contact, e.g. fluid path, direct contact with blood, patient) | N/A; software | N/A; software | N/A; software |
| Device Regulatory Classification | 21 CFR 870.2300;
Cardiac monitor (including cardiotachometer and rate alarm) | 21 CFR 870.2300;
Cardiac monitor (including cardiotachometer and rate alarm) | Same |
| Other Technology Used | Standard computers, network, and WIFI technology | Standard computers, network, and WIFI technology | Same |
| Host server | Uses hospital's existing server hardware or server pre-loaded with the WAVE Clinical Platform software and off-the-shelf operating system | Uses hospital's existing server hardware or server pre-loaded with the WAVE Clinical Platform software and off-the-shelf operating system | Same |
| Ability to View Data and Serves As Secondary Means Of Annunciating Patient Events | Yes | Yes | Same |
| Synopsis of Functionality | Store, route and display patient monitor, EMR and CIS data, alarms, and smart alarms remotely to aid in clinical decisions and deliver patient care in a timely manner | Store, route and display patient monitor, EMR and CIS data, alarms, and smart alarms remotely to aid in clinical decisions and deliver patient care in a timely manner | Same |
| Target Population/Demographics | In-hospital patients that have physiological sensors attached. | In-hospital patients that have physiological sensors attached. | Same |
K250135
{9}
Baxter
Table 3. Device Comparison
| Applications | PatientWatch
TeleTrend | PatientWatch
TeleTrend
AlarmView
AlarmNotification | WAVE 2.0.000 has an additional two applications for customer interface improvements.
Additional functionality in the subject device does not affect the intended use and fundamental scientific technology. |
| --- | --- | --- | --- |
K250135
{10}
Baxter
# DISCUSSION OF NONCLINICAL TESTS:
## Non-Performance Data:
The changes since the last 510(k) approval were evaluated to ensure that the change did not impact the integrity or performance of the product or raise different questions of safety and effectiveness.
Non-Performance testing was conducted on the WAVE Clinical Platform 2.0.000 to evaluate the functional performance of the device. Testing involved system level tests, performance tests and safety testing based on hazard analysis. Cybersecurity issues have been addressed and are included within the eSTAR attachments. Detailed summary information regarding the non-performance testing is supplied in Performance Testing: Bench and/or Performance Testing and the Software Documentation: Software Verification and Validation Testing within the eSTAR submission documentation. In addition to the verification and validation testing activities executed by Excel Medical Electronics, LLC to establish the performance and functionality of the WAVE Clinical Platform and the predicate device, several standards were utilized:
- ISO 14971 – Medical Devices – Application of Risk Management to Medical Devices
- IEC 62366-1 - Medical devices - Part 1: Application of usability engineering to medical devices
- IEC 60601-8 - Medical electrical equipment - Part 1-8: General requirements for basic safety and essential performance - Collateral Standard: General requirements tests and guidance for alarm systems in medical electrical equipment and medical electrical systems
Baxter/Excel Medical Electronics, LLC referred to the following documents:
- Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices
- General Principles of Software Validation; Final Guidance for Industry and FDA Staff
- Guidance for Industry – Applying Human Factors and Usability Engineering to Optimize Medical Device Design
K250135
{11}
Baxter
- Guidance for Industry – Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software
- Guidance for Industry - Off the Shelf Software Use in Medical Devices
**Biocompatibility:**
N/A
**CONCLUSION:**
The WAVE Clinical Platform 2.0.000 510(k) package and results on non-clinical testing demonstrates the WAVE Clinical Platform 2.0.000 is substantially equivalent and performs comparably to the predicate device, WAVE Clinical Platform that is currently marketed for the same intended use.
K250135
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.