The Daylink 112 Monitor ("DLM112") is for use in non-clinical settings (such as the home), as an accessory device that is intended to be a communication tool to enable health care providers to receive historical patient information. It is intended to be used in combination with a variety of external devices. The DLM112 serves as the remote communication link between compatible external devices, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center or with the healthcare/wellness provider or other out of hospital caregivers. The purpose is to collect and transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line. The DLM112 Monitor does not measure, interpret or make any decisions on the vital data that it conveys.
Device Story
DLM112 is a telemedicine hub/gateway device for home use. It collects physiological data (weight, blood pressure, blood glucose, ECG) from compatible external patient monitors via wireless (Bluetooth) or cabled connections. The device features a display and push buttons for patient interaction and data entry. It transmits collected information to a remote healthcare facility server over a standard residential telephone line using an internal modem. The device does not measure, interpret, or make clinical decisions; it serves solely as a communication link. Healthcare providers receive the transmitted data to assist in patient management. The device is not intended for emergency use or real-time monitoring.
Clinical Evidence
No clinical data. The device underwent bench testing and verification/validation activities to establish performance and reliability. Compliance with IEC 60601-1, IEC 60601-1-2, FCC Part 15, and FCC Part 68 was demonstrated.
Technological Characteristics
Hub/gateway device for home use. Connectivity: Bluetooth wireless and cabled interfaces to external monitors; internal modem for PSTN transmission. User interface: display and push buttons. Standards: IEC 60601-1 (safety), IEC 60601-1-2 (EMC), FCC Part 15/68 (radio/telecom). Risk management per ISO 14971:2000.
Indications for Use
Indicated for use in non-clinical settings (home) as a communication tool to collect and transmit historical patient medical information (e.g., weight, blood pressure, blood glucose) from compatible external monitors to a healthcare facility. Not for emergency calls, real-time alarms, time-critical data, or as a substitute for medical care or professional judgment. Not for patients requiring direct medical supervision.
Regulatory Classification
Identification
A radiofrequency physiological signal transmitter and receiver is a device used to condition a physiological signal so that it can be transmitted via radiofrequency from one location to another, e.g., a central monitoring station. The received signal is reconditioned by the device into its original format so that it can be displayed.
{0}------------------------------------------------
K062304-
pi/5
Image /page/0/Picture/1 description: The image shows the logo for RTX Healthcare. The logo consists of the letters "RTX" in a bold, sans-serif font, with a stylized arrow pointing to the right. Below the letters is the word "Healthcare" in a smaller, sans-serif font. The logo is black and white.
## 510(k) Summary
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirement of 21 CFR 807.92
SEP 2 9 2006
| Submitter: | Bjarne Flou<br>Managing Director<br>RTX Healthcare<br>Stroemmen 6<br>DK-9400 Noerresundby<br>Denmark<br>Tel: +45 96322300<br>Fax: +45 96322310<br>Email: bf@rtx.dk |
|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact person: | Niels Ole Andersen<br>Engineering Manager<br>Email: noa@rtx.dk |
| Date of summary: | 07/07/2006 |
| Common Name: | Physiological Transmitter and Receiver |
DLM112 Daylink Monitor Trade name:
Classification name:21 CFR 870.2910 Physiological Signal Transmitter And Receiver. Classification no: DRG
## Predicate Device:
| 510(k) number: | K041816 |
|----------------|--------------------------------------------------------------|
| Device name: | RTX3320 Wireless Telehealth Gateway |
| Applicant: | RTX Healthcare |
| 510(k) number: | K023749 |
| Device name: | M3810A Philips Telemonitoring System with M3812B TeleStation |
| Applicant: | Philips Medical Systems. |
| 510(k) number: | K042273 |
| Device name: | Health Buddy with Device Connectivity. |
| Applicant: | Health Hero Network |
## Submission Device Description:
The DLM112 telemedicine device performs transmission of physiological patient information to and from wireless, infrared and cabled patient monitors, and a remote data server healthcare facility using standard digital communication technologies and protocols. The DLM112, with its build-in modem, transmits data using the public switched telephone network.
The DLM112 screen, displays the information or questions about vital signs, symptoms and behaviors sent by the patient's healthcare provider, and allows the patient to respond via four large buttons
The DLM112 device is not used directly on a patient, and poses no significant risk to the patient or other people within the patient's home.
{1}------------------------------------------------
## Intended use and indications for use:
The Daylink 112 Monitor ("DLM112") is for use in non-clinical settings (such as the home), as an accessory device that is intended to be a communication tool to enable health care providers to receive historical patient information. It is intended to be used in combination with a variety of external devices. The DLM112 serves as the remote communication link between compatible external devices, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center or with the healthcare/wellness provider or other out of hospital caregivers. The purpose is to collect and transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line.
The DLM112 Monitor does not measure, interpret or make any decisions on the vital data that it conveys.
| Item | Submission<br>device | Predicate<br>device<br>K041816<br>(RTX<br>Healthcare) | Predicate<br>device<br>K023749<br>(Philips) | Predicate<br>device<br>K042273<br>(Health Hero) | |
|------|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | Intended use /<br>Indication for use | See section 2 | See section 6 | See section 7 | See section 8 |
| 2 | Intended users | Home users and<br>healthcare<br>providers. | Home users and<br>healthcare<br>providers. | Home users and<br>healthcare<br>providers. | Home users and<br>healthcare<br>providers. |
| 3 | Site of use | Typically for use<br>in patient's<br>home, placed on<br>a normal table. | Typically for use<br>in patient's<br>home, placed on<br>a normal table. | Typically for use<br>in patient's<br>home, placed on<br>a normal table. | Typically for use<br>in patient's<br>home, placed on<br>a normal table. |
| 4 | System<br>description | Telemedicine<br>device that is<br>working as<br>hub/gateway<br>sending<br>measured data<br>from compatible<br>patient monitors<br>to a compatible<br>data server. | Telemedicine<br>device that is<br>working as<br>hub/gateway<br>sending<br>measured data<br>from compatible<br>patient monitors<br>to a compatible<br>data server. | Telemedicine<br>system<br>consisting of a<br>device that is<br>working as<br>hub/gateway<br>sending data<br>measured by<br>the system<br>patient monitors<br>to a system data<br>server. | Telemedicine<br>system<br>consisting of a<br>device that is<br>working as<br>hub/gateway<br>sending data<br>measured by<br>the system<br>patient monitors<br>to a system data<br>server. |
| 5 | Connection to<br>patient monitors | Wireless<br>connection<br>between the<br>patient monitors<br>and the<br>hub/gateway. | Wireless and<br>cable<br>connection<br>between the<br>patient monitors<br>and the<br>hub/gateway. | Wireless and<br>cable<br>connection<br>between the<br>patient monitors<br>and the<br>hub/gateway. | Cable<br>connection<br>between the<br>patient monitors<br>and the<br>hub/gateway. |
| 6 | Transmission | Residential<br>telephone line | Residential<br>telephone line | Residential<br>telephone line | Residential<br>telephone line |
| 7 | Patient<br>Interactions | Display and<br>push buttons for<br>collection of | No patient<br>interaction. | Display and<br>push buttons for<br>collection of | Display and<br>push buttons for<br>collection of |
| | | patient typed<br>data | | patient typed<br>data | patient typed<br>data |
| 8 | Measurements<br>taken | Blood pressure,<br>weight, ECG,<br>Blood glucose<br>and other<br>measurements<br>provided from<br>compatible<br>monitor devices. | Blood pressure,<br>weight, ECG,<br>Blood glucose<br>and other<br>measurements<br>provided from<br>compatible<br>monitor devices. | Blood pressure,<br>weight, ECG<br>and Blood<br>glucose | Blood pressure,<br>weight, Blood<br>glucose, Peak<br>Flow and others. |
| 9a | Contra indications<br>and warnings | The device is<br>not for<br>emergency<br>calls, and may<br>not be used to<br>send any real-<br>time alarms or<br>time-critical<br>data. | The device is<br>not for<br>emergency<br>calls, and may<br>not be used to<br>send any real-<br>time alarms or<br>time-critical<br>data. | The device does<br>not send any<br>real time alarms. | The device does<br>not send any<br>real time alarms. |
| 9b | Contra indications<br>and warnings | All patient<br>medical<br>diagnosis and<br>treatment are to<br>be performed<br>under the<br>supervision and<br>oversight of an<br>appropriate<br>healthcare<br>professional. | Clinical<br>judgment and<br>experience are<br>required to<br>check and<br>interpret the<br>measurements<br>that are taken,<br>collected, and<br>delivered by<br>systems using a<br>RTX3320<br>device. | Clinical<br>judgment and<br>experience are<br>required to<br>check and<br>interpret the<br>information<br>delivered. | All patient<br>medical<br>diagnosis and<br>treatment are to<br>be performed<br>under the<br>supervision and<br>oversight of an<br>appropriate<br>healthcare<br>professional. |
| 9c | Contra indications<br>and warnings | The device is<br>not for use in<br>systems which<br>substitute for<br>medical care. | The device is<br>not for use in<br>systems which<br>substitute for<br>medical care. | The device is<br>not intended as<br>a substitute for<br>medical care. | The device is<br>not to be used<br>as a substitute<br>for a<br>professional<br>healthcare<br>judgment. |
| 9d | Contra indications<br>and warnings | The device is<br>not for use in<br>systems set up<br>for patients who<br>need direct<br>medical<br>supervision or<br>who might need<br>emergency<br>intervention. | The device is<br>not for use in<br>systems set up<br>for patients who<br>need direct<br>medical<br>supervision or<br>who might need<br>emergency<br>intervention. | The device is<br>not for use in<br>systems set up<br>for patients who<br>need direct<br>medical<br>supervision | -No statement- |
| 10 | Wireless link<br>between patient<br>monitors and the<br>gateway | Short range<br>radio system<br>using Bluetooth<br>technology. | Short range<br>radio system<br>using Bluetooth<br>technology. | Short range<br>proprietary radio<br>system. | No wireless<br>connectivity |
| 11 | Device<br>specifications | See section 5 | See section 17 | Proprietary<br>information | Proprietary<br>information |
## Substantial Equivalence Comparison table:
{2}------------------------------------------------
-
{3}------------------------------------------------
# Discussion on differences:
Item 1: The intended use / Indications for use for the predicate devices and the submission device are generally the same. The exact use are for all devices limited to be within the same intended use and with respect to the contra indications and warnings which are also generally the same for all three devices.
Item 2: The user of the predicate devices and the submission device is the same. The requirements to the user and skills that the users need to have are the same.
Item 3: Both the predicate devices and the submission device are for use in patient's home, The requirement specifications and the used performance standards for the submission device are defined based on using the device in a home environment.
Item 4: The predicate devices K023749 (Philips) and K042273 (Health Hero) are systems consisting of patient monitor devices, a hub/gateway device and a system server software. The Submission device and the Predicate device K041816 (RTX Healthcare) are a hub/gateway devices with a specified generic protocol interface to a list of compatible patient monitors, and with a specified generic protocol interface to any compatible system server. The protocols for the Submission device and the Predicate device K041816 (RTX Healthcare) are validated against existing compatible patient monitors and servers, and in the labeling it is stated that only compatible patient monitors and servers must be used with the hub/gateway.
Item 5: Two of the predicate devices and the submission device uses wireless communication between the patient monitors and the hub/gateway device. The third predicate device use cable connection which is also available on the submission device. Item 6: Both the predicate devices and the submission device use a residential telephone line for data communication.
Item 7: The predicate devices K023749 (Philips) and K042273 (Health Hero) are fitted with a display and a few push buttons for patient interaction. The purpose is to interact with the patient to collect additional information. The submission device is also fitted with a display and a few push buttons, and with the same purpose as on the predicate devices.
Item 8: For the predicate devices K023749 (Philips) and K042273 (Health Hero) the measurements taken are defined by the patient monitors that are a part of the system. For the submission device and the predicate device K041816 (RTX Healthcare), the
measurements taken are defined by the compatible patient monitors. Because of the similar intended use and indication for use for both the predicate devices and the submission device, the type of measurements will be the same.
Ifem 9a: Neither the predicate or submission devices may be used to send real time alarms.
Ifem 9b: Both the predicate and submission devices defines that all patient medical diagnosis and treatment are to be performed under the supervision and oversight of an appropriate healthcare professional.
Item 9c: Both the predicate and submission devices defines that it is not intended as a substitute for medical care or healthcare judgment.
Item 9d: Two of the predicate devices and the submission device state that it is not for use in systems set up for patients who need direct medical supervision.
Item 10: Two of the predicate devices use wireless connectivity like the submission device. One of the predicate devices and the submission device use the Bluetooth wireless technology that are known within medical devices, like the A&D Blood Pressure Meter
{4}------------------------------------------------
(FDA- K043217 ). The general radio signal safety requirements and FCC Part 15 rules are regulatory requirements that are equal for all devices containing radio transmitter. Item 11: Detailed environmental specifications are available for one of the predicate devices, but not for the two others since that is proprietary information not available for RTX Healthcare. This is evaluated not to add any additional risks to the patient since both the predicate devices and the submission device, according to the intended use, are designed for use by patients at home. The environmental specifications for the submission device are defined according to IEC/UL 60601-1 and specifications available for other medical devices for home use.
# Performance data:
The DLM112 device has been tested to meet the requirements of the following standards and requlations used as acceptance criteria:
IEC 60601-1, IEC 60601-1-2, FCC part 15 and FCC Part 68.
Risk management is performed according to ISO14971:2000.
Based on the fact that the performance comparison of the predicate device and the submission device show that the differences are minor and causes no harm to the user, and the fact that the intended use and indication for use is the same, it was early in the project decided to focus on verification and internal validation instead of large scale validation in form of clinical investigation.
Verification and validation testing activities is conducted to establish performance and reliability characteristics of the device.
# Conclusion
The DLM112 is substantially equivalent to the predicate devices cleared by FDA.
{5}------------------------------------------------
Public Health Service
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
2007 8 8 2006
RTX Healthcare c o Ms. Elizabeth A. Rosenfeld Administrative Coordinator KEMA Quality B.V. 4377 County Line Road Chalfont. PA 18914
Re: K062304
Trade Name: DLM112 Daylink Monitor Regulation Number: 21 CFR 870.2910 Regulation Name: Physiological Signal Transmitter and Receiver Regulatory Class: Class II (two) Product Code: DRG Dated: September 14, 2006 Received: September 18, 2006
Dear Ms. Rosenfeld:
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.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to such 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.
{6}------------------------------------------------
Page 2 - Ms. Elizabeth A. Rosenfeld
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); 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. This letter will allow you to begin marketing your device as described in your Section 510(k) premarket notification. The FDA finding of substantial equivalence of your device to a legally marketed predicate device results in a classification for your device and thus, permits your device to proceed to the market.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Office of Compliance at (240) 276-0120. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (240) 276-3150 or at its Internet address.
Sincerely yours,
Bfmtmtmorfr
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{7}------------------------------------------------
# 3. Indications for use statement
# Indication for Use Statement
### 510(k) Number (if known):
Device name: DLM112 Daylink Monitor
The Daylink 112 Monitor ("DLM112") is for use in non-clinical settings (such as the home), as an accessory device that is intended to be a communication tool to enable health care providers to receive historical patient information. It is intended to be used in combination with a variety of external devices. The DLM112 serves as the remote communication link between compatible external devices, and the compatible healthcare facility at another location. The healthcare facility could be at a disease management center or with the healthcare/wellness provider or other out of hospital caregivers. The purpose is to collect and transmit selected medical information (such as weight, blood pressure, blood glucose) over a normal residential telephone line.
The DLM112 Monitor does not measure, interpret or make any decisions on the vital data that it conveys.
Prescription Use × (Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 807 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Blummunon
(Division Sign-Off) Division of Cardiovascular Deyices 510(k) Number
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.