K141747 · Davis Medical · BTR · Apr 20, 2015 · Anesthesiology
Device Facts
Record ID
K141747
Device Name
RHINOGUARD
Applicant
Davis Medical
Product Code
BTR · Anesthesiology
Decision Date
Apr 20, 2015
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 868.5730
Device Class
Class 2
Attributes
Pediatric
Indications for Use
The Rhinoguard is a nasal endotracheal tube introducer/dilator designed to allow the passage of a nasal endotracheal tube from the nares to the oropharynx. The device can be used with cuffed and non-cuffed nasal endotracheal tubes.
Device Story
Rhinoguard is a nasal endotracheal tube introducer/dilator; facilitates passage of nasal endotracheal tube from nares to oropharynx. Device consists of polyvinylchloride tube with hollow proximal end, tapered cylindrical body, and closed, rounded distal end. User selects appropriate size (small for 3.0-4.5 mm tubes; large for 5.0-8.0 mm tubes), cuts device at size-specific indices, and mates it to endotracheal tube. Device is inserted through naris into oropharynx; distal end is grasped and removed via laryngoscope and McGill forceps. Device does not enter trachea; does not maintain open airway. Used in clinical settings by healthcare providers. Benefits include eased nasal intubation; reduced risk of perforation compared to predicate.
Clinical Evidence
Bench testing only. Tests included kink, disconnection, and perforation resistance; biocompatibility (ISO 10993); sterility (ISO 11137); shelf life/packaging (ISO 11607); and simulated-use usability validation. All tests met pre-determined acceptance criteria.
Technological Characteristics
Polyvinylchloride (thermoplastic) construction. Curved form factor with closed, rounded distal tip. Sizes: small (3.0-4.5 mm tubes) and large (5.0-8.0 mm tubes). Sterile (radiation). Manual surgical accessory; no energy source or software.
Indications for Use
Indicated for adult and pediatric patients to aid in nasal intubation by facilitating the passage of a nasal endotracheal tube from the nares to the oropharynx.
Regulatory Classification
Identification
A tracheal tube is a device inserted into a patient's trachea via the nose or mouth and used to maintain an open airway.
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a circular seal with the words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" around the perimeter. Inside the circle is a stylized image of three human profiles facing right, with flowing lines beneath them.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
April 20, 2015
Davis Medical, LLC % Ms. Michelle Lott Owner (President) Lean RAQA Systems 12602 N. Summer Wind Drive Marana, AZ 85658
Re: K141747
> Trade/Device Name: Rhinoguard Regulation Number: 21 CFR 868.5730 Regulation Name: Tracheal Tube Regulatory Class: Class II Product Code: BTR Dated: March 19, 2015 Received: March 20, 2015
Dear Ms. Lott,
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food. Drug. and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA), You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{1}------------------------------------------------
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 devicerelated adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours,
*Tejashri Purohit-Sheth, M.D.*
Tejashri Purohit-Sheth, M.D. Clinical Deputy Director DAGRID/ODE/CDRH FOR
Erin I. Keith, M.S. Director Division of Anesthesiology, General Hospital, Respiratory, Infection Control, and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
### Indications for Use
510(k) Number (if known) K141747
Device Name Rhinoguard
Indications for Use (Describe)
The Rhinoguard is a nasal endotracheal tube introducer/dilator designed to allow the passage of a nasal endotracheal tube from the nares to the oropharynx.
The device can be used with cuffed and non-cuffed nasal endotracheal tubes.
Type of Use (Select one or both, as applicable)
| <span style="font-family: sans-serif;">☑</span> Prescription Use (Part 21 CFR 801 Subpart D) | <span style="font-family: sans-serif;">☐</span> Over-The-Counter Use (21 CFR 801 Subpart C) |
|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
|----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
## SECTION 5 510(K) SUMMARY
-
{4}------------------------------------------------
# 510(k) Summary
As required by 21 CFR 807.92, this "510(k) Summary" provides a basis for the substantial equivalence determination of the device listed below.
| General Information | |
|-----------------------|--------------------------------|
| Date Prepared: | June 27th, 2014 |
| 510(k) Submitter: | Davis Medical LLC |
| | 6112 Peters Creek Road |
| | Roanoke, VA 24019 |
| | Contact: John Davis, CEO |
| | (540) 492-0453 |
| | info@betternasalintubation.com |
| 510(k) Correspondent: | Lean RAQA Systems |
| | Attn: Michelle Lott |
| | 12602 N Summer Wind Drive |
| | Marana, AZ 85658 |
| | Contact: Michelle Lott, RAC |
| | (520) 275-9838 |
| | leanraqasystems@gmail.com |
#### Device Information
| Trade Name: | Rhinoguard |
|-----------------------|-------------------------------------------------------------------------|
| Common Name: | Endotracheal Tube Introducer |
| Classification Name: | Tubes, Tracheal (W/Wo Connector)<br>[21 CFR 868.5730, Product Code BTR] |
| Classification Panel: | Anesthesiology |
| Class: | Class II |
#### Predicate Device Information
| Trade Name: | Rusch Preformed AGT Nasal Endotracheal Tubes (cuffed & uncuffed) |
|-----------------------|------------------------------------------------------------------|
| Common Name: | Endotracheal Tube Introducer |
| Classification Name: | Tubes, Tracheal (W/Wo Connector) |
| | [21 CFR 868.5730, Product Code BTR] |
| Classification Panel: | Anesthesiology |
| Class: | Class II |
| 510(k) Number: | K931164 & K931165 |
#### Device Description
The Rhinoguard is a nasal endotracheal tube introducer/dilator designed to ease the passage of a nasal endotracheal tube from the nares to the oropharynx. The Rhinoguard device is constructed primarily of polyvinylchloride and consists of a tube with a hollow proximal end, a tapered cylindrical body and a closed, rounded distal end. The device has markings to indicate the approximate mating location for corresponding sizes of nasal endotracheal tubes. The device is provided in a small and large size. The small Rhinoguard is intended to mate with 3.0 to 4.5 mm nasal endotracheal tubes and the large
{5}------------------------------------------------
Rhinoguard is intended to mate with 5.0 to 8.0 mm nasal endotracheal tubes. The device can be used with cuffed and non-cuffed nasal endotracheal tubes. Prior to using the device, the desired size of the nasal endotracheal tube must be selected and then matched to corresponding Rhinoguard size (large or small). The device is then cut just above the indices (marks) corresponding to the selected endotracheal tube size and connected with the endotracheal tube. Once mated, the distal end of the device is introduced into the naris of choice and gently pushed forward into the oropharynx. Lastly, the distal end of Rhinoguard is grasped and removed from the mouth with the aid of a laryngoscope and McGill forceps.
#### Intended Use/Indications for Use
The Rhinoguard is a nasal endotracheal tube introducer/dilator designed to allow the passage of a nasal endotracheal tube from the nares to the oropharynx. The device can be used with cuffed nasal endotracheal tubes.
#### Technological Characteristics
The device comparison table below provides a general summary of the technological characteristics of the Rhinoguard device compared to the predicate device. The Rhinoguard was classified as a class II device because it is an accessory to class II nasal endotracheal tubes. For this reason, nasal endotracheal tubes were selected as the predicate to the Rhinoguard. Provided that the Rhinoguard is an accessory to nasal endotracheal tubes and to assist with the characterization of certain design features and performance characteristics of the Rhinoguard device, two other class I reference devices (Sun-med Endotracheal Tube Introducer and Pilling Bougie/Dilator) were also selected. The Rhinoguard device is similar in operation to the legally marketed class I reference devices. These similarities between the proposed and reference devices are identified to support safety and efficacy of the introducing and dilating features of the Rhinoguard.
#### Device Comparison
As explained in detail below, the Rhinoguard is substantially equivalent to other legally marketed Rusch Preformed AGT Nasal Endotracheal Tubes (Cuffed & Uncuffed (K931164 & K931165), Sun-Med Endotracheal Tube Introducer, and Pilling Bougie/Dilator. Specifically, the Rhinoguard is substantially equivalent to the predicate devices identified. Rhinoguard has the same general intended use and similar indications, technological characteristics, and principles of operation as the previously cleared predicate device(s). A substantial equivalence device comparing the similarities and differences between the Rhinoguard and its predicate and reference device(s) is provided below. Minor differences in the technological characteristics do not raise new questions of safety or efficacy. Performance (bench) testing demonstrates that the Rhinoguard is as safe and effective as its predicate devices. Because the proposed device functions as an accessory to an endotracheal tube, the Rusch Preformed AGT Nasal Endotracheal Tube was selected as the predicate device and supporting devices with introducer/dilator functionalities were selected as reference devices.
{6}------------------------------------------------
| Device Comparison Table | | | | |
|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
| | Rhinoguard | Rusch Preformed AGT Nasal | Sun-med Endotracheal | Pilling Bougie/<br>Dilator |
| | (Proposed device) | Endotracheal Tubes (cuffed<br>& uncuffed) | Tube Introducer | (Reference Device) |
| | | (Predicate Device) | (Reference Device)<br>Exempt | Exempt |
| | | K931164 & K931165 | | |
| FDA Class | Class II | Class II | Class I | Class I |
| FDA Product Code | BTR | BTR | KCD | KCD |
| FDA Regulation | 868.5730 – Tracheal Tube | 868.5730 – Tracheal Tube | 874.4420 - Ear, nose,<br>and throat manual<br>surgical instrument | 874.4420 - Ear, nose,<br>and throat manual<br>surgical instrument |
| 510k # | N/A | K931164 & K931165 | N/A - Class I, 510(k)<br>exempt | N/A - Class I, 510(k)<br>exempt |
| Indications | Indicated to aid in nasal<br>intubation | Indicated for nasal<br>intubation and for airway<br>management | Indicated to aid in oral<br>intubation | Indicated to aid in<br>oral intubation |
| User Population | Adult and pediatric | Adult and pediatric | Adult and pediatric | Adult and pediatric |
| Operating<br>principle | Device mates to tip of<br>nasal endotracheal tube<br>and enters through the<br>nostrils. Device is<br>advanced to the<br>oropharynx and then<br>separated from the<br>endotracheal tube. Device<br>exits the mouth prior to<br>entering trachea. | Device enters though the<br>nostrils and is advanced past<br>the vocal cords and finally<br>placed into the trachea. | Endotracheal tube is<br>inserted over the device.<br>Device enters the<br>trachea prior to the<br>endotracheal tube and<br>then the device is<br>removed after placing<br>the endotracheal tube<br>into the trachea. | Device enters airway<br>and then is removed<br>once airway is dilated. |
| Enters trachea | No | Yes | Yes | Yes |
| Maintains an<br>open airway | No | Yes | No | No |
| Materials | Polyvinyl Chloride<br>(thermoplastic) | Polyvinyl Chloride<br>(thermoplastic) | Low Density<br>Polyethylene<br>(thermoplastic) | Silicone and tungsten |
| Sterile | Yes (Radiation) | Yes (ETO) | Yes (ETO) | Meant for<br>sterilization by end<br>user |
| Closed tip | Yes | No | Yes | Yes |
| Rounded tip | Yes | No | Yes | Yes |
| Straight or curved | Curved | Curved | Both available<br>(for curved units, curve<br>is just in tip of the<br>device) | Straight |
| Sizes | Small and large sizes to<br>accommodate nasal<br>endotracheal tube sizes<br>3.0 – 8.0 mm | 3.0 – 8.0 mm | Small and large sizes to<br>accommodate<br>endotracheal tube sizes<br>4.0 – 11.0 mm | NA - dilates airway<br>rather than mates<br>with tube<br>Sizes available 20 FR |
| | Table 5.1 - Device Comparison Table | |
|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
| | | |
| Testing Completed | Testing Description | Standards Referenced |
| Kink Testing | The purpose of this test was to confirm that the Rhinoguard meets the pre-determined flexibility requirements and that device performance is equivalent to the predicate device. | N/A |
| Disconnection Testing | The purpose of this test was to confirm that the Rhinoguard meets the pre-determined flexibility requirements and that the device performance is equivalent to the predicate device. | N/A |
| Perforation Testing | The purpose of this test was to confirm that the Rhinoguard is less of a penetrator than the predicate device. | N/A |
| Biocompatibility<br>Testing<br>(to include<br>cytotoxicity, systemic<br>toxicity,<br>intracutaneous,<br>maximaization<br>sensitization) | The purpose of this test was to confirm that the Rhinoguard meets pre-determined biocompatibility requirements. | ISO 10993-1:2009<br>ISO 10993-5:2009<br>ISO 10993-10:2010<br>ISO 10993-11:2006 |
| Sterility Testing<br>(to include bioburden,<br>verification dose,<br>sterility,<br>bacteriostasis/<br>fungistasis | The purpose of this test was to confirm that the Rhinoguard can be sterilized to a Sterility Assurance Level (SAL) of 1.0 X 10-6. | ISO 11137-1:2006<br>ISO 11137-2:2012<br>ISO 11737-1:2006<br>ISO 11737-2:1995 |
| Shelf Life Testing<br>(Packaging - to<br>include label<br>retention, seal<br>strength, bubble leak<br>test, package drum<br>test, dye penetration) | The purpose of this test was to confirm that the device packaging functionality and performance is acceptable after the desired shelf life of the product. | ISO 11607-1:2006<br>ISO 11607-2:2006<br>D14169-09<br>F2096-11 |
| Shelf Life Testing<br>(Device — to include<br>kink, disconnection,<br>and perforation) | The purpose of this test was to confirm that the device functionality and performance is acceptable after the desired shelf life of the product. | N/A |
| Design (Usability)<br>Validation Testing | The purpose of this test was to confirm that the Rhinoguard meets the intended use, user needs, and usability requirements when tested under a simulated use environment. | N/A |
-
{7}------------------------------------------------
#### Performance Characteristics
Nonclinical testing was conducted for supporting substantial equivalence between the Rhinoguard and predicate device. The nonclinical tests addressed device performance characteristics such as flexibility, penetration force, biocompatibility, sterilization, packaging and shelf life. In conclusion, the proposed device performed equivalent to or better than the predicate device.
All performance testing met acceptance criteria defined in protocols.
{8}------------------------------------------------
#### Substantial Equivalence – Comparison to Predicate Device
Among the information and summary tables included in this 510(k) submission to support substantial equivalence of the Rhinoguard device to the legally marketed predicate device are: 1.) device description, 2.) indications for use, 3.) device comparison tables, 4.) material information, 5.) nonclinical (bench) test results, and 6.) labeling. In particular, nonclinical test results demonstrate that there were no differences that are critical to the intended use of the proposed device or that affect the safety and effectiveness of the proposed device when used as labeled.
The proposed and predicate devices have intended use, in as far as that both are used during nasal intubations, and similar indications, technological characteristics and principles of operation. The proposed device differs from the predicate device in certain design features, which are required to support aiding in nasal intubation (as do the reference devices) rather than in airway management (as does the predicate). The minor differences in technological characteristics have been identified and do not present any new issues of safety or effectiveness. Thus, the Rhinoguard device is substantially equivalent to the Rusch Preformed AGT Nasal Endotracheal Tubes (K931164 & K931165).
(End of Section)
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.