K142732 · Etiometry, Inc. · MWI · Mar 4, 2015 · Cardiovascular
Device Facts
Record ID
K142732
Device Name
T3 Software
Applicant
Etiometry, Inc.
Product Code
MWI · Cardiovascular
Decision Date
Mar 4, 2015
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes: To remotely consult regarding a patient's status, and To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.
Device Story
T3 Software is a web-based data management solution for intensive care units; aggregates numeric physiologic data from bedside devices (e.g., blood pressure, heart rate, respiratory rate, CO2, temperature). System architecture includes a central Java-based web server and a browser-based user interface. Data is processed, cached, and stored in a relational database for visualization. Clinicians access the system via standard web browsers (Chrome, Firefox, Safari, IE) within the hospital or remotely via VPN. The device provides customizable displays of physiologic parameters and user-defined derived measures (e.g., percentage of time a variable exceeds a threshold). It does not provide alarms, waveforms, or device control. It serves as a supplementary tool for clinicians to review patient status and support clinical decision-making; it is not a replacement for active bedside monitoring systems.
Clinical Evidence
Bench testing only. No clinical data required. Software verification and validation included unit tests, automated integration testing, and manual performance testing. Testing confirmed system functionality against requirements and specifications.
Technological Characteristics
Web-based software architecture; Java-based web services; PostgreSQL 9.1 database; Red Hat Enterprise Linux 6 server. Client-side requires HTML5, Javascript, and web sockets. Connectivity via network (1000Mb/s server, 10Mb/s browser). No bedside hardware required. Moderate level of concern software.
Indications for Use
Indicated for adult, pediatric, and neonatal patients to record and display physiological parameters from bedside devices. Used by healthcare professionals for remote consultation and review of near real-time patient data to aid clinical decision-making. Not for alarm notification, waveform display, or device control. Not an active monitoring system.
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}------------------------------------------------
Image /page/0/Picture/1 description: The image contains the logo for the U.S. Department of Health and Human Services. The logo features the department's name in a circular arrangement around a symbol. The symbol is a stylized representation of a human figure, with three profiles overlapping to create a sense of depth and connection.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
March 4, 2015
Etiometry, Inc. % Pamela Weagraff Director And Practice Lead Quintiles Consulting 18 Bridie Lane Norfolk, Massachusetts 02056
Re: K142732
Trade/Device Name: T3 Software Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MWI Dated: January 29, 2015 Received: January 30, 2015
Dear Pamela Weagraff,
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.
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
{1}------------------------------------------------
related adverse events) (21 CFR 803): good manufacturing practice requirements as set forth in the quality systems (OS) 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.
Kenneth J. Cavanaugh -S
for
Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K142732
Device Name T3 Software Solution
#### Indications for Use (Describe)
The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected. T3 is intended to be used by healthcare professionals for the following purposes:
- · To remotely consult regarding a patient's status, and
· To remotely review other standard or critical near real-time patient data in order to aid in clinical decisions and deliver patient care in a timely manner.
T3 can display numeric physiologic data captured by other medical devices:
- · Airway flow, volume and pressure
- · Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
- · Bispectral index (BIS, signal quality index, suppression ratio)
- Cardiac Index
- · Cardiac output
- · Central venous pressure
- · Cerebral perfusion pressure
- · End-tidal CO2
- · Heart rate
- · Heart rate variability
- · Intracranial pressure
- · Left atrium pressure
- · Oxygen saturation (intravascular, regional, SpO2)
- · Premature ventricular counted beats
- · Pulmonary artery pressure (systolic, diastolic, and mean)
- · Pulse pressure variation
- · Pulse Rate
- · Respiratory rate
- · Right atrium pressure
- · Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
- · Umbilical arterial pressure (systolic, diastolic, and mean)
WARNING: T3 Software is not an active patient monitoring system; it is intended to supplement and not replace any part of the hospital's device monitoring. Do not rely on the T3 Software as the sole source of patient status information.
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.
{3}------------------------------------------------
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}------------------------------------------------
### 510(K) SUMMARY OF SAFETY AND EFFECTIVENESS - K142732
[Format according to Appendix C – "The 510(k) Program: Evaluating Substantial Equivalence in Premarket Notifications [510(k)]", July 28, 2014 to meet requirements of Title 21 CFR Part 807.92]
## 1) 510(k) Submitter:
- a) Company Name and Address:
Etiometry, Inc. 119 Braintree Street Boston, MA 02134
- b) Company Contact: Dimitar Baronov, PhD Chief Technology Officer Phone: 857.366.9333 ext. 2005 E-mail: baronov@etiometry.com
- c) Date Prepared: February 25, 2015
## 2) Device
- a) Device Trade Name: T3 Software
- b) Device Common/Usual Name: Data Management Software (without alarms)
- c) Classification Name: Cardiac monitor (including cardiotachometer and rate alarms
- d) Classification Number: 870.2300
- e) Regulatory Class: II
- Product Code: MWI; monitor, physiological, patient (without arrhythmia f) detection or alarms)
## 3) Predicate Device
- a) Vital Sync™ Informatics Manager has been cleared under K140339, K132604, K123002, and K093422.
- b) Vital Syncm Informatics Manager is subject of two software design-related recalls, Z-2234-2014 and Z-2235-2014.
{5}------------------------------------------------
## 4) Device Description
The Tracking, Trajectory, Trigger (73) intensive care unit software solution allows clinicians and quality improvement teams in the ICU to aggregate data from multiple sources, store it in a database for analysis, and view the streaming data in real-time. System features include:
- Customizable display of physiologic parameters over entire patient stay ●
- Configurable annotation ●
- Web-based visualization that may be used on any standard browser ●
- Minimal IT footprint ●
- Software-only solution no new bedside hardware required ●
- Highly reliable and robust operation ●
- Auditable data storage ●
The T3 Software is intended for the display and recording of multiple physiological parameters of adult, pediatric and neonatal patients. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected.
The T3 software can display user-defined, derived measures. These measures include the percentage of time within a time period that a particular variable is above or below a threshold. The user can configure the time period, threshold, and label of the resulting derived measure for ease of use considerations, only.
The T3 Software is not an active patient monitoring system. It is intended to supplement and not replace any part of the hospital's device monitoring.
T3 has a web architecture consisting of a user interface that runs in a browser, and a central web server. The T3 server, a set of cooperating web services written in Java, processes data as it is received, caches it in memory, and writes out copies of the data to a relational database and to the file system. In this manner, the data is available to the user interface to be visualized by the end user – a clinician.
Clinicians access the T3 user interface in a web browser. T3 runs in current browsers that support HTML5, Javascript and web sockets, such as Chrome, Firefox, Safari and Internet Explorer. The clinicians may be in the hospital, or may be outside the hospital accessing T3 over a Virtual Private Network (VPN). Clinicians use T3 in addition to the physiometric devices themselves and other information sources such as the electronic medical record to monitor the patient's condition.
## 5) Indications for Use
The T3 Software is intended for the recording and display of multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected.
{6}------------------------------------------------
T3 is intended to be used by healthcare professionals for the following purposes:
- To remotely consult regarding a patient's status, and
- . To remotely review other standard or critical near real-time patient data in order to utilize this information to aid in clinical decisions and deliver patient care in a timely manner.
T3 can display numeric physiologic data captured by other medical devices:
- Airway flow, volume and pressure
- Arterial blood pressure (invasive and non-invasive, systolic, diastolic, and mean)
- Bispectral index (BIS, signal quality index, suppression ratio)
- Cardiac Index
- I Cardiac output
- . Central venous pressure
- . Cerebral perfusion pressure
- End-tidal CO2
- Heart rate
- I Heart rate variability
- I Intracranial pressure
- . Left atrium pressure
- . Oxygen saturation (intravascular, regional, SpO2)
- Premature ventricular counted beats
- Pulmonary artery pressure (systolic, diastolic, and mean)
- Pulse pressure variation
- Pulse Rate
- Respiratory rate
- Right atrium pressure
- Temperature (rectal, esophageal, tympanic, blood, core, nasopharyngeal, skin)
- Umbilical arterial pressure (systolic, diastolic, and mean)
WARNING: T3 Software is not an active patient monitoring system; it is intended to supplement and not replace any part of the hospital's device monitoring. Do not rely on the T3 Software as the sole source of patient status information.
The T3 Software indications for use differ from the Vital Sync™ in that T3 Software does not interface to the EMR or CIS and does not display alarms or waveforms. As a result the T3 Software does not introduce differences which would result in a change in safety or effectiveness as compared to the predicate Vital Sync system.
The indications for use are the same with respect to the near real-time data recording and remote display capabilities. Neither the T3 Software nor the Vital Sync™ is intended to replace any part of the hospitals device monitoring systems; and are also not intended to be used as the sole source of information in the care of the patient.
{7}------------------------------------------------
## 6) Comparison of Technological Characteristics with the Predicate Device
The T3 Software has similar features and functionality as the predicate Vital Sync system with the exception of the differences noted above. The systems are web based and designed to acquire data from the network source and display the information remotely for clinicians to use in the care of their patients. The technological characteristics implemented in T3 software to achieve this interaction are similar to the predicate device as well. Please refer to Table 1 below:
| | T3 Software | Predicate - Vital Sync™ Informatics Manager |
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Regulation<br>Number /<br>Product Code | Cardiac monitor (including<br>cardiotachometer and rate alarm)<br>21 CFR 870.2300 / MWI | Cardiac monitor (including<br>cardiotachometer and rate alarm)<br>21 CFR 870.2300 / MWI |
| Server | » Server: 1<br>» CPU: 2x Intel Xeon E5649 or better (6<br>core 2.53GHz)<br>» RAM: 48 GB<br>» Hard Drive: 1 TB usable<br>» External Storage: per hospital policy<br>back-up policies and procedures<br>» OS: Red Hat Enterprise Linux 6 or<br>Higher<br>» Software: Installs and uses<br>PostgreSQL 9.1 | » Server: 1<br>» CPU: 1 – 3.46 GHz, 12M Cache, 6.40<br>GT/s QPI, 6 Core<br>» RAM: 4 GB<br>» Hard Drive: 500 GB<br>» External Storage: external tape back-<br>up for data archive<br>» OS: Windows® Server 2008 R2<br>Enterprise<br>» Software: IIS 7.0, Sql Server 2008 R2,<br>.Net 4.0, ReportViewer V10.0 |
| Remote<br>Viewing Device | » Software Browser: requires HTML5<br>support, such as Chrome, Internet<br>Explorer 11, Firefox 30, Safari 5<br>» CPU: 2.5 GHz Core 2 Duo Processor<br>or equivalent<br>» RAM: 2 GB<br>» Video Display: 1024 x 768 | Software Browser: Internet Explorer 9,<br>Firefox 10, Safari 5.1 |
| Network | Server Environment: 1000Mb/s Browser<br>connection to server: 10Mb/s | Server Environment: 100/1000 Mbps<br>Ethernet |
| Wireless<br>Network | Individual users require a rate of 10Mb/s | Minimum available bandwidth in Kbs:<br>$X*2.1+Y*148$ where<br>X = Number of active devices<br>Y = Number of active display devices<br>Any hardware purchased must be<br>supported by the hospital IS department<br>(Reference Recommended Wi-Fi Device<br>Specification). |
Table 1: Comparison of Technological Characteristics
{8}------------------------------------------------
| | T3 Software | Predicate - Vital Sync™ Informatics Manager |
|------------------------------|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Other | Uninterruptible power supply (one per server) | » Uninterruptible power supply (one per server)<br>» DVD reader is required for installation of SW on the server.<br>» Isolation transformer or a 60601 certified power strip is required to enable a single power connection from the ventilator to the power supply if a powered Wi-Fi device is used. |
| Use Environment | Hospital | Hospital |
| Displayed Parameters | All display parameters provided by Philips Intellibridge | All display parameters provided by Covidien bedside devices |
| Externally Supported Devices | Philips Intellibridge | Covidien bedside devices |
Table 1: Comparison of Technological Characteristics
### 7) Performance Data
In support of this 510(k) premarket notification, Etiometry has conducted software verification and validation testing. T3 Software documentation has been provided in accordance with FDA's "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices", May 11, 2005. T3 Software is considered a moderate level of concern since a malfunction of, or a latent design flaw in, the Software Device could lead to an erroneous diagnosis or a delay in delivery of appropriate medical care that would likely lead to minor injury.
{9}------------------------------------------------
Software verification and validation testing consisted of unit tests, integration and manual performance tests. Individual test cases were defined for each software requirement, including test execution steps, acceptance criteria and test methodology. Upon successful completion of unit testing, automated integration testing was performed followed by manual performance testing.
Unscripted exploratory testing was performed to confirm that the system responded as intended and met all performance specifications. Software verification and validation results confirmed that T3 Software functions as intended and meets all performance specifications.
T3 Software is a software medical device, therefore biocompatibility testing, electrical safety and electromagnetic compatibility (EMC) testing, sterilization, shelflife, animal testing and clinical testing were not required to demonstrate substantial equivalence.
## 8) Substantial Equivalence Conclusion
Substantial equivalence of the T3 Software is demonstrated through performance testing and shows that the T3 software solution is as safe and effective as Vital Sync TM Informatics Manager, cleared under K140339, K132604, K123002, and K093422. The T3 software solution has the same intended uses and similar indications, technological characteristics, and principle of operation as its predicate device.
The minor technological differences between the T3 Software and its predicate device do not raise any new safety or effectiveness questions. Performance data demonstrate that the T3 Software is safe and effective to perform its intended use to record and display multiple physiological parameters of adult, pediatric and neonatal patients from supported bedside devices. T3 is not intended for alarm notification or waveform display, nor is it intended to control any of the independent bedside devices to which it is connected.
WARNING: T3 Software is not a real-time patient monitoring system; it is intended to supplement and not replace any part of the hospital's active patient monitoring system. Do not rely on the T3 Software as the sole source of patient status information.
Therefore, T3 Software is substantially equivalent to its predicate device.
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.