Vios Monitoring System(TM) Model 2050; Vios Central Station Monitor/Vios Central Server Software 2050
K241728 · Murata Vios, Inc. · DXN · Jan 23, 2025 · Cardiovascular
Device Facts
Record ID
K241728
Device Name
Vios Monitoring System(TM) Model 2050; Vios Central Station Monitor/Vios Central Server Software 2050
Applicant
Murata Vios, Inc.
Product Code
DXN · Cardiovascular
Decision Date
Jan 23, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1130
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
The Vios Monitoring System (VMS) is intended for use by medically qualified personnel for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. It is indicated for use in monitoring of 7-Lead ECG, heart rate, respiratory rate, pulse rate, functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure (NIBP) continuously, and patient posture and activity. VMS allows for the input of non-invasive blood pressure and body temperature and can display data from peripheral devices. VMS can generate alerts when rate-based cardiac arrhythmias are detected and when physiological vital signs fall outside of selected parameters. The non-invasive Blood Pressure Tracking feature is based on Pulse Arrival Time (PAT), which is obtained utilizing ECG and PPG signals following a calibration process using an FDA-cleared oscillometric blood pressure monitor. This feature is not intended for use in critical care environment. The Vios Central Station Monitor (CSM) and Central Server (CS) Software (SW) is indicated for use by healthcare professionals for the purpose of centralized monitoring of patient data within a healthcare facility. The Vios CSM SW and CS SW receives, stores, manages, and displays patient physiological and waveform data and alarms generated by Vios proprietary patient vitals monitoring software.
Device Story
Wireless mobile platform for healthcare facility patient monitoring; includes Chest Sensor, Finger Adapter, Central Server, and Central Station Monitor. Chest Sensor acquires 3-channel ECG, bioimpedance, 2-channel pulse oximetry, and tri-axial accelerometer data; transmits via Bluetooth to BSM software. NIBP tracking uses Pulse Arrival Time (PAT) derived from ECG and PPG signals; requires calibration via FDA-cleared oscillometric cuff. System generates alerts for arrhythmias and out-of-range vitals. Healthcare professionals use Central Station to view, manage, and store patient data. Enables continuous monitoring, facilitating clinical decision-making through real-time physiological data and alarm notifications.
Clinical Evidence
Clinical testing performed per ISO 81060-2, IEEE 1708, and ISO 81060-3 using radial artery invasive blood pressure as reference. Results met acceptance criteria and were similar to predicate. System validation testing and compliance testing per IEC 80601-2-30 conducted. Previous system performance verified via electrical safety (IEC 60601-1), EMC, biocompatibility (ISO 10993), and pulse oximetry/respiratory rate clinical testing.
Technological Characteristics
Wireless mobile system; Chest Sensor (rechargeable, multi-use); Bluetooth connectivity. Sensing: 3-channel ECG, bioimpedance, 2-channel PPG, tri-axial accelerometer. NIBP tracking via PAT algorithm. Software: VMS BSM SW (standalone, commercial IT platform). Standards: IEC 60601-1, IEC 60601-1-2, IEC 60601-1-8, IEC 60601-2-27, IEC 60601-2-49, EC53, ISO 10993, ISO 14971, EN 62304, EN 62366, ANSI C63.27.
Indications for Use
Indicated for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. Monitors 7-Lead ECG, heart rate, respiratory rate, pulse rate, SpO2, continuous NIBP, patient posture, and activity. NIBP tracking feature not for critical care use.
Regulatory Classification
Identification
A noninvasive blood pressure measurement system is a device that provides a signal from which systolic, diastolic, mean, or any combination of the three pressures can be derived through the use of tranducers placed on the surface of the body.
Vios Central Station Monitor/Central Server Software 2050 (K173107)
Submission Summary (Full Text)
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
January 23, 2025
Murata Vios, Inc.
John Lansdown
Director, Quality, Regulatory, & Compliance
700 Commerce Drive, #190
Woodbury, Minnesota 55125
Re: K241728
Trade/Device Name: Vios Monitoring System(TM) Model 2050;
Vios Central Station Monitor/Vios Central Server Software 2050
Regulation Number: 21 CFR 870.1130
Regulation Name: Noninvasive Blood Pressure Measurement System
Regulatory Class: Class II
Product Code: DXN, DRT, DQA, DPZ, DRG, DXJ, OUG
Dated: June 14, 2024
Received: June 14, 2024
Dear John Lansdown:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K241728 - John Lansdown
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K241728 - John Lansdown
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Stephen C. Browning -S
LCDR Stephen Browning
Assistant Director
Division of Cardiac Electrophysiology,
Diagnostics, and Monitoring Devices
Office of Cardiovascular Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 07/31/2026
See PRA Statement below.
Submission Number (if known)
k241728
Device Name
Vios Monitoring System(TM) Model 2050 (2050);
Vios Central Station Monitor/Vios Central Server Software 2050 (2050)
Indications for Use (Describe)
The Vios Monitoring System (VMS) is intended for use by medically qualified personnel for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. It is indicated for use in monitoring of 7-Lead ECG, heart rate, respiratory rate, pulse rate, functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure (NIBP) continuously, and patient posture and activity. VMS allows for the input of non-invasive blood pressure and body temperature and can display data from peripheral devices. VMS can generate alerts when rate-based cardiac arrhythmias are detected and when physiological vital signs fall outside of selected parameters.
The non-invasive Blood Pressure Tracking feature is based on Pulse Arrival Time (PAT), which is obtained utilizing ECG and PPG signals following a calibration process using an FDA-cleared oscillometric blood pressure monitor. This feature is not intended for use in critical care environment.
The Vios Central Station Monitor (CSM) and Central Server (CS) Software (SW) is indicated for use by healthcare professionals for the purpose of centralized monitoring of patient data within a healthcare facility. The Vios CSM SW and CS SW receives, stores, manages, and displays patient physiological and waveform data and alarms generated by Vios proprietary patient vitals monitoring software
Type of Use (Select one or both, as applicable)
☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C)
## CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
*DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
Department of Health and Human Services
Food and Drug Administration
Office of Chief Information Officer
Paperwork Reduction Act (PRA) Staff
PRAStaff@fda.hhs.gov
“An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number.”
{4}
# 510(k) Summary
| Submitter: | Murata Vios, Inc.
700 Commerce Drive, Suite 190
Woodbury, MN 55125 |
| --- | --- |
| Contact Person: | John Lansdown
Director, Quality, Regulatory, & Compliance
john.lansdown@murata.com
Mobile: 972-984-0977 |
| Date Prepared: | July 1, 2024 |
| Trade Names: | Vios Monitoring System™ Model 2050
Vios Central Station Monitor/Central Server Software 2050 |
| Common Name: | Vital Signs monitor |
| Regulation: | 21 CFR § 870.1130 Noninvasive blood pressure measurement system
21 CFR 870.2300 Cardiac Monitor (including cardiotachometer and rate alarm)
21 CFR 870.2910 Radiofrequency physiological signal transmitter and receiver
21 CFR 870.2700 Oximeter
21 CFR 870.2710 Ear oximeter
21 CFR 870.2450 Medical cathode-ray tube display
21 CFR 880.6310 Medical device data system |
| Classification: | Class II |
| Review Panels: | Cardiovascular, Anesthesiology |
| Product Codes: | DXN, DRT, DQA, DPZ, DRG, DXJ, OUG |
| Predicate Devices: | Primary Predicate:
ViSi Mobile Monitoring System (K130709)
Secondary Predicates:
Vios Monitoring System™ Model 2050 (K172586)
Vios Central Station Monitor/Central Server Software 2050 (K173107) |
| Device Description: | The Vios Monitoring System (VMS) Model 2050 is a wireless mobile medical device platform that allows caregivers in healthcare settings to monitor patient vitals.
The VMS includes a proprietary monitoring software, Chest Sensor, Finger Adapter and Central Server and Central Monitoring Station.
The VMS BSM SW Model B2050 is stand-alone software that can receive, analyze, and display physiological vitals data from one or more patient-worn sensors via standard communication protocols (Bluetooth™). It runs on a commercial IT platform and is intended to be used in conjunction with the Vios Chest Sensor and Vios Lead Adapters and can support peripheral, medical grade, Bluetooth™-enabled devices.
The VMS Chest Sensor Model CS2050 is a small, patient-worn, non-sterile multiple use, and rechargeable sensor that acquires 3-channel ECG, bioimpedance, 2-channel pulse oximetry, and tri-axial accelerometer data. The sensor contains signal acquisition firmware (embedded software) and wirelessly communicates acquired data via standard communication protocols (Bluetooth™) to the BSM SW for analysis and display. The Chest Sensor has a button that, when pressed, sends a patient call alert to the BSM SW.
VMS Chest Sensor Adapter Models L2050F (Pulse Ox Finger Adapter) are plastic, non-sterile, patient-worn, multiple use pulse oxygenation sensors that connect to the Vios Chest Sensor and are secured to the patient via medical grade ECG electrodes. |
Page 1 of 3
K241728
{5}
Page 2 of 3
K241728
| Indications for Use: | The Vios Monitoring System (VMS) is intended for use by medically qualified personnel for physiological vital signs monitoring of adult (18+) patients in healthcare facilities. It is indicated for use in monitoring of 7-Lead ECG, heart rate, respiratory rate, pulse rate, functional oxygen saturation of arterial hemoglobin, non-invasive blood pressure (NIBP) continuously, and patient posture and activity. VMS allows for the input of non-invasive blood pressure and body temperature and can display data from peripheral devices. VMS can generate alerts when rate-based cardiac arrhythmias are detected and when physiological vital signs fall outside of selected parameters.
The non-invasive Blood Pressure Tracking feature is based on Pulse Arrival Time (PAT), which is obtained utilizing ECG and PPG signals following a calibration process using an FDA-cleared oscillometric blood pressure monitor. This feature is not intended for use in critical care environment.
The Vios Central Station Monitor (CSM) and Central Server (CS) Software (SW) is indicated for use by healthcare professionals for the purpose of centralized monitoring of patient data within a healthcare facility. The Vios CSM SW and CS SW receives, stores, manages, and displays patient physiological and waveform data and alarms generated by Vios proprietary patient vitals monitoring software. |
| --- | --- |
| Summary of Substantial Equivalence | The subject device has been updated with software modifications (addition of algorithm for blood pressure tracking and supporting UI modifications) which has similar technological characteristics as that of primary predicate, K130709. The features other than blood pressure tracking and the physical components remain unchanged from the secondary predicates (K172586 and K173107).
Vios Central Station Monitor/Central Server essentially remains the same apart from UI modifications to support blood pressure tracking.
• Basic Principle: The subject device tracks blood pressure via PAT (Pulse Arrival Time) using the time delay between ECG measured from the chest and the pulsatile PPG waveform measured at the base of finger/thumb using the pulse oximeter of the subject device. The sensors unit for ECG and PPG remains the same as K172586 and for the blood pressure tracking, the same underlying principle is used by the primary predicate, Visi Mobile Monitoring System, K130709.
• Calibration (initialization): For tracking the blood pressure based on PAT, it requires coefficients from an input blood pressure for calibration. This characteristic is the same as the Visi Mobile Monitoring System (K130709). The predicate and the subject device are calibrated to a specific oscillometric cuff device. Both the subject and predicate devices can only be calibrated when the PAT is stable, and the calibration is achieved by pairing PAT during cuff inflation with the BP readings of the calibration device during the same cuff inflation period. Thus, the method of calibration remains the same between the subject device and the predicate.
• Device Performance: The clinical study was performed across a range of subjects, representative of the intended population, to validate this measured change. The results demonstrate the performance meeting the all consensus standards requirement and are substantially equivalent to the predicate device.
The subject device has been verified and clinically validated to meet the requirements of the recognized consensus standards. The results demonstrate that essential technological characteristics between the subject device and the predicate devices are the same, and do not raise new questions about safety or effectiveness, and testing establishes equivalent performance as compared to predicate devices. |
{6}
| Summary of Non-Clinical, Clinical, and Conformance Testing | The bench (non-clinical) testing for the addition of blood pressure tracking feature to the VMS Model 2050 is done using system validation testing and compliance testing for applicable clauses according to IEC 80601-2-30.
The clinical testing and analysis is performed according to applicable clauses from ISO 81060-2, IEEE 1708, and ISO 81060-3 for validation using reference invasive blood pressure measurement on the radial artery. The results were within the acceptance criteria, similar to the predicate device.
The other system performance remains unchanged from the predicate (K172586) and show conformance to:
- Electrical safety, EMC, and vitals sign monitoring standards (IEC 60601-1, IEC 60601-1-2, IEC 60601-1-8, IEC 60601-2-27, IEC 60601-2-49, EC53)
- Biocompatibility standards (ISO 10993)
- Transportation Simulation testing (ASTM D4169-16)
- Software development life cycle (EN 62304)
- Usability and human factors standards (EN 62366)
- Risk Management (ISO 14971)
- Pulse oximetry clinical testing (ISO 80601-2-61)
- Respiratory Rate clinical testing
- Standard for evaluation of Wireless Coexistence (ANSI C63.27) |
| --- | --- |
| Conclusions | Based on the results from the non-clinical and clinical tests, Murata Vios considers the Vios Monitoring System to be as safe, as effective and substantially equivalent to the legally marketed predicate devices. |
Page 3 of 3
K241728
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.