K963633 · Puritan Bennett Corp. · MOD · Dec 16, 1996 · Anesthesiology
Device Facts
Record ID
K963633
Device Name
VENTNET; CENTRAL MONITORING STATION
Applicant
Puritan Bennett Corp.
Product Code
MOD · Anesthesiology
Decision Date
Dec 16, 1996
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 868.5895
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
VentNet’s intended use is to supplement the operation of dispersed or remotely located mechanical ventilators. VentNet allows the remote monitoring of multiple ventilators from a central station. VentNet displays ventilator settings, ventilator alarm status and physiological patient information as communicated from the monitored mechanical ventilator. VentNet also includes an optional feature which causes automatic notification, via paging system to defined users of certain ventilator alarms. VentNet is not intended to replace on-hand competent medical staff in monitoring for, or responding to ventilator alarms but is intended to support that staff by notifying other respiratory care staff or ventilator specialists in the event of certain alarm conditions. VentNet’s secondary intended use is the automation of some of the record keeping and reporting functions performed during mechanical ventilation.
Device Story
VentNet is a PC-based central monitoring station for remote observation of up to 24 mechanical ventilators (7200 Series). Inputs include ventilator settings, alarm status, and physiological data received via hardwire or wireless radio-link transceivers. The system processes these inputs to display real-time status, record chronological event logs (up to 1000 records), and trigger optional remote paging notifications via TAP protocol. Used in hospital environments by respiratory care staff or ventilator specialists; the system provides a graphical user interface (Windows 3.11) for monitoring, reporting, and data archiving. It does not replace bedside staff but supports them by alerting specialists to alarm conditions. Benefits include centralized oversight of dispersed ventilators, automated record-keeping, and improved response times to ventilator alarms.
Clinical Evidence
Bench testing only. Evidence includes EMI compatibility and susceptibility testing, environmental stress testing, and system-level software verification and validation.
Technological Characteristics
Pentium-100 MHz PC, 16 MB RAM, 1 GB HDD. Wireless communication via 902-928 MHz spread spectrum radio transceivers (100 mW output). Hardwire interface via EIA-232 or EIA-422. SVGA color monitor with touchscreen capability. Operating system: Microsoft Windows 3.11. Defibrillation protection on remote transceivers. Compliant with UL544 and CSA C22.2 No. 125.
Indications for Use
Indicated for patients being ventilated by the 7200 Series Ventilator in hospital or hospital-type environments.
Regulatory Classification
Identification
A continuous ventilator (respirator) is a device intended to mechanically control or assist patient breathing by delivering a predetermined percentage of oxygen in the breathing gas. Adult, pediatric, and neonatal ventilators are included in this generic type of device.
{0}
467
DEC 16 1996
K963633
# PREMARKET NOTIFICATION [510(k)] SUMMARY
August 12, 1996
| VitalCom Contact Person: | Mr. Ray Pizinger |
| --- | --- |
| Trade Name: | VentNet |
| Common Name: | Central Monitoring Station |
| Classification Name: | Monitor, breathing frequency |
| Trade Name: | NSMS-900 |
| Common Name: | Transmitters and Receivers |
| Classification Name: | Transmitters and Receivers, Physiological Signal, Radiofrequency |
| Substantially Equivalent to: | Spacelabs PCMS Monitor, Model 90845 (K913038)
Spacelabs Flexport Interface, Model 90436-01 (K903702) |
## SUMMARY OF VENTNET INTENDED USE
### 9A. PURPOSE AND FUNCTION OF DEVICE
The VentNet system consists of a PC based Central Monitoring Station and either a hardwire or wireless communication means allowing the remote monitoring of up to 24 continuous mechanical ventilators. VentNet further has a means of communication via paging system for the remote notification of alarms or changes in ventilator status. The VentNet automatically records ventilator setting changes and alarm events with patient physiological data from the monitored ventilators. The user may then review this information in a ventilator flowsheet format or print it as pre-formatted reports.
VentNet’s intended use is to supplement the operation of dispersed or remotely located mechanical ventilators. VentNet allows the remote monitoring of multiple ventilators from a central station. VentNet displays ventilator settings, ventilator alarm status and physiological patient information as communicated from the monitored mechanical ventilator. VentNet also includes an optional feature which causes automatic notification, via paging system to defined users of certain ventilator alarms. VentNet is not intended to replace on-hand competent medical staff in monitoring for, or responding to ventilator alarms but is intended to support that staff by notifying other respiratory care staff or ventilator specialists in the event of certain alarm conditions.
{1}
468
VentNet’s secondary intended use is the automation of some of the record keeping and reporting functions performed during mechanical ventilation.
## 9B. INTENDED PATIENT POPULATION
The intended population are those patients who are being ventilated by the 7200 Series Ventilator.
## 9C. INTENDED ENVIRONMENT OF USE
The VentNet is intended to be used in an environmentally controlled hospital and hospital type environment.
## 9D. DEVICE CLAIMS
### 9D1. ADVERTISING CLAIMS
9D1.1) VentNet can be installed as either a hardwire system which can monitor up to sixteen (16) 7200 Series Ventilators or an FCC approved radio system which can monitor up to twenty-four (24) 7200 Series Ventilators.
9D1.2) From a VentNet central monitoring station a user can remotely monitor ventilator settings, alarm status, and physiological patient information for up to 24 7200 Series Ventilators.
9D1.3) VentNet uses established graphical user interface conventions to improve ease of learning and operation for operators familiar with Windows software applications. The VentNet system can be installed to operate either with a mouse or with a touch screen.
9D1.4) VentNet is compatible with Nellcor Puritan-Bennett 7200 Series Ventilator supporting the host port or DCI communications option or with future Nellcor Puritan-Bennett continuous critical care ventilators which support the same communications protocols.
9D1.5) VentNet automatically records ventilator settings and ventilator alarm events for monitored ventilators and displays that information in a spreadsheet format for review. VentNet will record the most recent events, up to 1000 records, as they occur. The time and date of settings changes and alarm events are automatically recorded to allow a chronological history. Physiological patient information is recorded along with the alarm events to assist the user in understanding the alarm event.
{2}
469
9D1.6) VentNet has predefined report formats allowing the user to print reports of the system configuration, and monitored ventilator information. VentNet also provides means for archiving data and exporting that data to third party information systems.
9D1.7) VentNet displays the alarm status of the monitored ventilators which are indicated by color coded software buttons representing each ventilator. Each software button includes labels allowing the user to designate a patient identification and location. The user may further investigate the specific alarm codes which are active at each ventilator.
9D1.8) VentNet can optionally be configured to work with paging systems to allow the remote notification of certain alarm conditions. The user can designate where alarm messages are sent and can modify the conditions under which a ventilator alarm will result in a notice being sent. For each ventilator a primary and a secondary message path can be designated. The user can modify the conditions for notification individually for each monitored ventilator, and for each alarm condition of the ventilator.
9D1.9) VentNet incorporates passcode protection to restrict access to functions which interrupt ventilator monitoring or might cause the loss of data.
9D2. PRODUCT AND TECHNICAL SPECIFICATIONS
9D2.1 Central Station Compliance
9D2.2 Electrical
9D2.3 Physical Characteristics
9D2.4 Environmental
9D2.5 Operational Characteristics
9D2.7 Radio-Link Transceivers Operational Characteristics
9D2.8 Laser Printer Requirements
9D2.9 Component and System Labels
9D2.10 Central Station Compliance
This section contains specifications for components of the central station and the bedside station remote radio transceiver. Requirements for the facility provided laser printer are also provided.
{3}
470
## 9D.2.11 Electrical Characteristics
**Central Station External AC Input Voltage/Current**
115 Vac, 60 Hz, 5 A (maximum) or
230 Vac, 50 Hz, 2.6 A (maximum)
**Remote Radio Transceiver Defibrillation Protection**
The remote radio transceiver shall not be damaged by defibrillation and shall return to normal operation within 15 seconds of defibrillation.
## 9D.2.12 Physical Characteristics
**Dimensions**
**Computer:**
21 cm (8.3 in.) x 40.6 cm (16 in.) x 46 cm (18.1 in.)
**Monitor:**
38.2 cm (15 in.) or 43.2 cm (17 in.) diagonal screen
**Uninterruptible Power Supply:**
15.0 cm (6.0 in) x 9.0 cm (3.4 in.) x 33.0 cm (13.1 in)
**Bedside Station Radio Transceiver**
12.5 cm (4.92 in.) x 6.7 cm (2.64 in.) x 3.0 cm (1.18 in.)
**Weight**
**Computer**
29.5 kg (65 lbs)
**Monitor**
13.8 kg (30 lbs, 7 oz)
**Uninterruptible Power Supply**
8.2 kg (18 lbs)
**Bedside Station Radio Transceiver**
0.18 kg (6.6 oz)
## 9D.2.13 Environmental
**Temperature**
**Operating**
+10° C to +35° C (+50° F to +95° F)
**Shipping/Storage (In sealed shipping container)**
-40° C to +70° C (-40° F to +158° F)
{4}
471
## Relative Humidity
### Operating
30% RH to 80% RH (noncondensing)
### Shipping/Storage (In sealed shipping container)
95% (maximum)
## Central Station Ventilation and Cabling Requirements
All components of the central station should have a minimum of 1.5 inches clearance around top, sides, back, and front for ventilation. No central station component should be installed in an enclosed cabinet. A minimum of 4 inches is required behind the computer to accommodate cabling.
## 9D.2.14 Operational Characteristics
### Computer
- Pentium-100 MHz
- 16 MB RAM
- 1 GB Hard Drive
- 3.5-inch Floppy Drive
- Hercules Dynamite Video Board
- Serial Mouse
- 101-key Keyboard
### Monitor
- 15 inch or 17 inch diagonal screen
- Touchscreen hardware installed
- 800 x 600 pixel resolution
- 256 colors
## 9D.2.15 Hard-wired Interface Characteristics
- Selectable EIA-232 or EIA-422
- RJ45 interface connector at central station
- 9-pin D-connector at the bedside station
## Radio-Link Transceivers Characteristics
### Central Transceiver Transmitter
- Frequency 902 to 928 MHz
- RF Output Power +20 dBm (100 mW) minimum
- RF Power Adj. >20 dB range
{5}
472
Settling Time <100 usec
Frequency Stability ±0.001%
Modulation Type Direct FM, DDS Synthesized NRZ
Modulation Rate 62.5 kilobaud (nominal)
Antennas Omni-directional
Spectrum Usage Spread spectrum (IAW FCC Par. 15.247)
FCC CISPR 11 - Class A with exceptions for intentional
radiators covered by FCC Part 15, Section 247
Central Transceiver Receiver
Frequency 902 to 928 MHz
Frequency Spacing 1 kHz
Settling time 100 usec
Frequency Stability ±0.001%
Selectivity 180 kHz (3 dB) nominal
300 kHz (20 dB) nominal
Sensitivity: -80 dBm (minimum) in 180 kHz bandwidth for 10 dB SNR
Modulation Type Direct FM, DDS Synthesized NRZ
Modulation Rate 133 kilobaud
Diversity Full voting, 2 channels
Input impedance 2:1 VSWR maximum (50 ohm)
Host PC Interface Memory-mapped, dual port RAM
Antennas Omni-directional
Remote Transceiver Transmitter
Frequency 902 to 928 MHz
RF Output Power +15 dBm nominal, ±2.0 dB
RF Power Adj. >20 dB range
Settling Time <300 usec
Frequency Stability ±0.001%
Modulation Type Direct FM, DDS Synthesized NRZ
Modulation Rate 133 kilobaud (nominal)
Frame Length: 30 milliseconds
Data Rate Instantaneous bandwidth variability
FCC CISPR 11 - Class B with exceptions for intentional
radiators covered by FCC Part 15, Section 247
Remote Transceiver Receiver
Frequency 902 to 928 MHz
Settling time <300 usec
Frequency Stability ±0.001%
{6}
473
Selectivity 180 kHz (3 dB) nominal 300 kHz (20 dB) nominal
Sensitivity -90 dBm (minimum) in 180 kHz: bandwidth for 10 dB SNR
Spurious Rejection 50 dB nominal
Modulation Type 100 kHz deviation NRZ
Modulation Rate 133 kilobaud
Input impedance 2:1 VSWR maximum (50 ohm)
## Laser Printer Minimum Requirements
The VentNet monitoring system supports printers that are both HPGL/2 and PCL5 compatible with a minimum of 2 megabytes of printer memory such as the Hewlett-Packard LaserJet models 4, 4SI, 4L, 5, 5SI, and 5L printers.
## Component and System Labels
There are two labels on the rear panel of the central station computer described as follows.
An identification label showing product title, model, and serial numbers plus agency certifications is affixed on the rear panel of the central station computer by the original manufacturer. This label shows certification compliances at the time the computer was purchased from the manufacturer and is applicable to the computer only. This label also facilitates product traceability through the manufacturer’s product records system.
Another identification label showing the system model number is affixed on the rear panel of the central station computer by Nellcor Puritan Bennett. This label shows CSA/NRTL/C certification that is applicable to the VentNet monitoring system as a whole. This certification is based on the Canadian Standard for Electromedical Equipment, C22.2, No. 125 and the Underwriters Laboratories Standard for Medical and Dental Equipment, UL544.
{7}
# 9E. COMPARISON MATRIX
VentNet vs. Spacelabs PCMS and VitalCom Model 1100
NOTE: THE 7200 VENTILATOR CONNECTS TO THE SPACELABS PCMS VIA
THE FLEXPORT INTERFACE (90436-01)
| Characteristic | VentNet Central Monitoring Station | Spacelabs Patient Care Management System (PCMS) (K913038) | VitalCom Model 1100 Central Monitoring Station (K942147) |
| --- | --- | --- | --- |
| Display | SVGA Color Monitor with and without touchscreen | SVGA Color Monitor with and without touchscreen | SVGA Color Monitor with and without touchscreen |
| Channels | Up to 24 Patients (wireless)
Up to 16 Patients (hardwire) | Access of up to 16 Patients (telemetry or hardwire) | 8 independent with 2 waveforms per channel; (16 for remote displays) |
| Hardware | PC based, Pentium, 75 MHz or higher, 16 MB RAM, 1.2 GB HD | CPU based 80486, 50 MHz, 48 MB RAM, 700 MB HD | Mini-tower personal computer 486 or higher. |
| Hardwire Interface | RS232 or RS422 Interface | Spacelabs Flexport Interface (K903702) | RS232 |
| Radio Transmitter Interface (wireless) | 1. Remote Transceiver
- Frequency 903 - 920 MHz
- Output 50 mW (Max)
2. Central Transceiver
- Frequency 903 - 922 MHz
- Output 500 mW (Max) | Not Provided | Multiple, Applicable option:
1. Remote Transceiver
- Frequency 903 - 920 MHz
- Output 50 mW (Max)
2. Central Transceiver
- Frequency 903 - 922 MHz
- Output 500 mW (Max) |
| Software Operating System | Microsoft Window 3.11 | unknown | VRTX |
| Ventilator Settings | Provided by the 7200 Series Ventilator | Provided by the 7200 Series Ventilator | not applicable |
| Patient Data | Provided by the 7200 Series Ventilator | Provided by the 7200 Series Ventilator | not applicable |
| Ventilator Alarm Settings | Provided by the 7200 Series Ventilator | High/Low Limits Adjustable at the Bedside Monitor, a remote location and at the Central Monitor | not applicable |
| Individual patient real time alarm status | Status of the ventilator alarms for a selected patient as provided by the 7200 series ventilator. | Patient displayed status in the patient block | ECG, Arrhythmia, and Bedside Monitor alarm status for individual patients |
| Paging | User selectable for each patient, either no page, autopage to one number, or manual page to a preset number. VentNet uses a hospital paging system using the standard TAP protocol | Not provided | (Optional) Paging via user prompt to hospital paging system, including Zone paging. |
{8}
| Characteristic | VentNet Central Monitoring Station | Spacelabs Patient Care Management System (PCMS) (K913038) | VitalCom Model 1100 Central Monitoring Station (K942147) |
| --- | --- | --- | --- |
| Tabular Trends | Future Options | Tabular trends include both settings and monitored patient data | ST and others if available from the Bedside |
| Graphical Trends | Future Options | Graphical trends of tidal volume and respiratory rate | Pressure (NIBP), and Pleth and others if available from the Bedside |
| Waveforms | Future Options | Pressure and Flow waveforms are available if the ventilator provides them | ECG, Pressure (NIBP), and Pleth and others if available from the Bedside |
| Reports | Multiple available, user selectable intervals, automatic print on alarms, and manual requests | User selectable intervals, automatic print on alarms, and manual requests | Multiple available, user selectable intervals, automatic print on alarms, and manual requests |
| Ventilation Calculations | As provided by the 7200 Series Ventilator | Calculations for minute volume, dynamic & static compliance, dead space volume, dead space to tidal volume ratio, and alveolar ventilation | not applicable |
| Logs | Alarm, ventilator setting changes, and patient monitoring status | Events Logs | Events Logs |
{9}
476
## 9F. TECHNOLOGICAL CHARACTERISTIC REVIEW
The VentNet Central Monitoring Station is substantially equivalent to the Spacelabs PCMS Monitor, Model 90845 (K913038) with the use of the Spacelabs Flexport Interface, Model 90436-01(K903702). The VentNet uses a pentium based personal computer and offers both a hardwire interface and a wireless interface (radio transceivers). This technology is equivalent to the VitalCom Model 1100 systems provided to other manufacturers for communication from bedside monitors to a centralized monitoring station which was determined substantially equivalent in 1995 (K942147). VentNet also utilizes Microsoft Windows 3.11 as it's operating system which is currently being utilized through out the monitoring industry in a variety of products, including the Zymed Central Station Monitor System, Model T8010 (K951370), the Acuity Central Monitor (K935846) and the VMAX Pulmonary / Medabolic System, (K942211).
## 9G. NON-CLINICAL PERFORMANCE DATA REVIEW
The determination of substantial equivalence was based on an assessment of non-clinical performance data. The data includes testing for EMI compatibility and susceptibility, software verification and validation of both the system software performance as well as the operating system software performance, environmental testing and stress testing both at the integration level and the system level. The conclusion drawn from a review of the data indicates that the VentNet is substantially equivalent to the predicate devices.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
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.